ullibelgie

Ich höre, daß manche Leute auf die Idee gekommen sind, um aus externen USB Harddisks (ab 4 TB) die HDDs auszubauen, um diese dann als Data oder gar als Parity Disk im Unraid server zu verwenden. Man soll dadurch die gleichen Produkte viel preisgünstiger erwerben.. Da ich dringend meine Parity Disk (z.Zt 1Tb) und auch mindestens eine Datadisk (1Tb) gegen grössere Disks wechseln möchte, wäre ich für TIpps dankbar. Was ist von der Idee zu halten die HDDs aus ext. Disks auszubauen ? Weiss man was da wirklich für Harddisks drin sind ? Gibt es aktuelle Angebote ? Wenn man so einen Ausbau machen will - welche externe Platte sollte man dann kaufen, um halbwegs sicher zu sein, was da drin ist ? Danke für Infos.

Inzwischen habe ich zum Glück mein Array wieder reparieren können: werde mich jetzt um die Backups kümmern und dann so schnell wie möglich grössere Parity Disk rein und die zweifelhafte Disk 1 auswechseln...

I found indeed for some reason the I/O settings in BIOS was set to AHCI disabled. I don't know, if this was set ealier to enabled or not, when installing Unraid. Additionally I found (with AHCI disabled mode) that when I changed the cables to use different SATA ports on the X7DVL-e Motherboard different HDD got disabled. But as I managed to get 2 (out of 3) data disks enabled plus one parity drive, I was able to repair the XFS file system with the steps explained in the unraid wiki (look in the manual under trouble shooting) After that I could also mount the remaining 3rd data disk Then the rebuild process started... It looks to me, that the rebuild process was successful (look at the screenshot below) However there were 180 errors of a different data disk! Are these new errors ? Or errors which occurred sometimes during the total life time of the HDD - even years ago, when I started to use it in my old windows machine. Total lifetime is now almost 1600h Better to exchange the disk 1 ? As my parity disk is also only 1Tb... better to buy a bigger parity drive also for the future possible expansion... Many thanks for the people who helped me with this problem.

Thanks for replies ! Indeed I do not think, that there is any fault of the HDD's itself, but the Sata-controller (on motherboard) Because by using different sata ports on the Supermicro X7DVL-E board for the 4 HDDs, I could manage to see 3 disks in the array - so only one missing. However the fourth disk I cannot get visible. The check routine of Unraid to check the file system doesn't repond anything.... I guess, because of a hardware fault of the Sata controller itself - so there is no data connection at all to the missing 4th HDD. I will tomorrow check, if I see anything strange in the BIOS - I thought I had enabled AHCI... Will check it tomorrow, after a good sleep..... many thanks. If I cannot find anything, I think I have a broken motherboard and I simply need to build new hardware. In that case, I will keep the HDDs to transfer everything on the new hardware, when it is ready.... however it will be hard to find budget immediately for a new server...but that is a different story.

Hallo Marc, Danke für die schnelle Antwort - deutlich! Leider habe ich jetzt aber ein ganz anderes fundamentales Problem: hier: und bei der Vorbereitung der Backup versuche heute vormittag: Es scheint als ob ich hier am laufenden Band die HDDs schreddere..... aufräumen hatte ich mir leider anders vorgestellt. Es wird also noch eine Weile dauern bis ich Dein rsync script weiter verwenden kann... Unraid ist jetzt erstmal komplett down mit dem vielen HD-crashs von heute Beste Grüsse..

I rebooted the Unraid server - the failed disks do not even appear in Unassigned disks any more: However I can see them as missing in the array: Is there a realistic chance to recover the data on disk2 and disk 3 ? They could not be mounted earlier and now disappeared. What should be the next step ? Some sort of checkdisk outside of Unraid ?!

As I have 2 (out of 3) array disks failing, the array configuration is signed invalid and I cannot restart it in maintenance mode. According to the 'lost array configuration' advice in the Unraid wiki https://wiki.unraid.net/Manual/Troubleshooting#Lost_Array_Configuration the data should not be lost. I also have a flash drive back-up from some hours ago, with no re-assignment of disks Also I still have a parity disk, which is not disappeared... So because I still have the parity disk and the recent flash back-up, is there are more easy, but still save way for recover the both disks and rebuild the array configuration, so I can start it up (in maintenance mode to check file systems of the two disks) Screenshots of the array from UD main page attached. Thanks for help

As a new user of Unraid, I was busy to build my server with all the data... finally it is finished for a couple of days and I am now about to make my first backup: - 1 parity disk (1Tb) - 3 Array HDDs (1Tb each) about 55% of space used by data No Cache drives or any pools Apps : Paperless ng, Calibri But now I have a fundamental problem: 2 of the data disks are suddenly unmountable only one disk remaining plus the parity disk So most of the data not accessible.... I have found some information in the Unraid Docs https://wiki.unraid.net/Manual/Troubleshooting#Unmountable_Disk.28s.29 However what to do, if not only one, but two disks become unmountable (2/3 of all data ) Any advice, what to do to recover the data ? Thank you Diagnostic file attached... tower-diagnostics-20210807-1443.zip

Here is the Diagnostics file: Diagnostics.zip

Noch ein Zusatzfrage zu dem tollen Back-up script von MGutt: Wie Marc angibt, möchte ich das Script über das User-script Plug-in ausführen. Das hat ja den Vorteil, das man verschiedene Backups machen kann und dann einfach nur die vorkonfigurierten Scripts wählen muss. Jetzt frage ich mich aber, wie ich das Scheduling von dem Plug-in einstellen muss - das ist ja auch für beliebige andere Scripts zusätzlich zu Backup's hilfreich: - im Code von Marc ist ja das tägliche/wöchentliche ... Zeitschema schon realisiert. - Wie muss ich dann das User-script Plug-in einstellen damit der im Script von Marc codierte Zeitplan nicht durcheinander kommt oder gar ausgeschaltet wird ? - irgendwo gab es auch mal einen TIp, wie man die Urzeit für die täglichen Backup's einstellen kann - wie funktionierte das dann nochmal ?! Danke...

Hallo zusammen, nachdem ich im englischen Teil des Forums den Experten schon auf den Keks gegangen bin mit meinen Anfängerfragen melde ich mich auch hier mal.... (alle Mann in Deckung...lol) Aber erstmal ein Kompliment (auch) and die deutschsprachige community - ausgezeichnet was Aktivität und Qualität betrifft... Folgendes: Ich bin am Anfang meines Serveraufbaus und will nun mein erstes Backup machen mit dem Script vom Marc Gutt. Ich habe gelesen, daß es notwendig ist auf dem Zielrechner sogenannte Unix-Extensions installiert zu haben, weil sonst das Script nicht funktioniert - ist das richtig ? Ich will zum Anfang erstmal das Script testen mit kleinen Foldern und uber SMB von Unraid auf eine HDD eines anderen Rechners ubertragen mit rsync Der andere Rechner hat ein Ubuntu 20.04LTS installiert Was sind die Unix-extensions die ich da noch auf dem Ubuntu-client installieren muss ?! Im Internet habe ich unter "Unix-extensions" nix gefunden.... Oder habe ich was missverstanden und ich brauche gar nix weiter zu installieren ? Die Zielplatte im Ubuntu Rechner hat ext4 Fileformat (frisch formatiert) Schönen Gruss...

It seams, I need to be more patient...hi As I wrote my previous post, the formatting seemed to be repaired ?! I could also mount the USB disk now The log shows now: So , I believe the issue is solved and I can start the backup on this USB disk , right ? Can someone explain to me what happened before - why the format procedere throwed the alert pop-up "FAIL" before?

While preparing for a backup, I pre-cleared a 1Tb external USB-Harddisk with unassigned disk plug-in After 18hours it was finished successfully... Now I format the disk XFS with unassigned disk plug-in - however after short time a "FAIL" pop-up window appears and the UD-log shows: ------------------------------ FS: xfs /sbin/xfs_repair -n /dev/sdf1 2>&1 Phase 1 - find and verify superblock... bad primary superblock - filesystem mkfs-in-progress bit set !!! attempting to find secondary superblock... ----------------------------- It already runs for half an hour... What to do ? just wait .... The number of reads and writes is still growing - so there is something running in the background.... Thanks for advice

Yes, indeed - mounting is not automatically process - it needs manual click... may be there is something wrong with the old shared folder... will check the syslog... I think it works now ! "Waiter, could you please bring two more beer for the experts how helped me..." .....;-)

Now I found the following: - the original shared folder "backup' can be SMB imported with green dot, but not mounted - I made additional folder 'another' which can also be Smb imported with green dot and also mounted.... So the newly written folder another works perfectly - I have just tried that... Difference: 'backup' contains zip-file of a database 'another' contains only simple txt file I have no problems to erase 'backup' folder, as it was only a test with a just formatted FAT32 disk on the Ubuntu server... But why this happened ? I have no idea...

whow, this works indeed: input manually the Ubuntu-client IP-adress: 192.168.1.120 then input smb user registered at the Ubuntu-client then input passwd for that user then manually input the shared folder name.... Bingo! A green smb unassigned disk shows up However it cannot be mounted....;-( response from the UD-terminal: root@Tower:~# cat /var/state/unassigned.devices/ping_status.json {"ON5KQ-X8DA3":{"timestamp":1628176963,"no_pings":0,"online":"no","changed":"no"},"192.168.1.120":{"timestamp":1628178231,"no_pings":0,"online":"yes","changed":"no"}}root@Tower:~#

here is the result from UD-terminal: root@Tower:~# cat /var/state/unassigned.devices/ping_status.json {"ON5KQ-X8DA3":{"timestamp":1628176963,"no_pings":0,"online":"no","changed":"no"},"192.168.1.120":{"timestamp":1628177166,"no_pings":0,"online":"yes","changed":"yes"}}root@Tower:~# ^C I used both: At first tried at first with just the found servername... - no shares could be found from the wizard Then I tried again with the IP-adres 192.168.1.120 (the Ubuntu-client) - at least the $print share could be found at the end, but not the shared folders.... see above result from terminal

just rebooted Try to call the unassigned (and shared) Ubuntu disk.... Unfortunately - no change... UD sees the Ubuntu machine - I log in with the smb username and password (different than passwd of local machine user) - then domain (I leave that open) then shares...... UD cannot find any share. Windows 10 finds the share immediately and can open the folder Greyed out in Unraid... Are there perhaps other issues within unraid, which might be misconfigured ?

Just to clearify: In Unraid settings I have Enabled smb with YES (workgroup) but disabled NetBios, as I only want to use SMB 2 or later... I have WSD enabled Dotfiles and MacOS is disabled (no Apple in house...hi) Under workgroup settings Local master is Yes.... Ok - now rebooting Unraid...

here is the Ubuntu client response from the UD-Terminal request: root@Tower:~# /bin/ping -c 1 -W 1 192.168.1.120 PING 192.168.1.120 (192.168.1.120) 56(84) bytes of data. 64 bytes from 192.168.1.120: icmp_seq=1 ttl=64 time=0.215 ms --- 192.168.1.120 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.215/0.215/0.215/0.000 ms root@Tower:~# It seems there should be a connection...

Thank you, for the advice to change the passwd of the samba user - I had indeed set the same username and password, which had been accepted by Ubuntu without any complain... Now I have changed the passwd to a different one. Result: Now I can see the shared folder at the Ubuntu client from another client computer running windows 10. But that is not, what I want to do ... I want to connect with Unraid However Unraid still do not see the shared folder - no change to my above posted Unraid screenshot. I believe the connection between Unraid and Ubuntu is via samba, isn't it ?! That is why I installed Samba... Perhaps Samba is only for networking Unraid with windows systems and not for Linux (Ubuntu) at all ?! Do I need to install NFS and share via that system with Unraid as Samba will not work between two Linux machines....

Thank you for your quick answer dlandon I tested ping from Unraid terminal window with command: "ping Ip-adress-of-Ubuntu-client" ... and there is a response within less than 1msec So it must be a different issue... Are there other things to check - it must be something switched off, which prevents any communication other than ping...;-(

May I get some advice please ? I am a new user of unraid and have started with two dockers: - Paperless ng (already containing about 300 documents) - Calibri with Calibri web (to read books via the home network on my tablet - about 200documents and some really large pdf files) Now I wonder how to best backup the application data folder and the databases of these applications. I have no cache drives in the server (just starting) - only the array itself (3x HDD plus 1 parity). I am therefore not sure if the Backup-restore plug-in is the right way for the backup. It seems that it is made a nice backup for people using cache drives (SSD) for speed up their dockers/VM and which are concerned of the the data outside their array. So may be I should do the backups in my case different ? Best, I would build a backup scheme following the 3-2-1 rule, to do the things right from beginning. (3 copies, 2 different media and 1 different location) The Calibri database seem to be stored outside of application data folder, but in the media share (where also all the e-books are). I was thinking to backup this folder with the script of Marc Gutt. (user script plug-in.... great explanation Marc in the German forum!) The question is however remaining, how to backup the application folder ?! And is it enough in case of fatal crash ? How about the dockers themselves ?! Sorry for my stupid questions and thanks for chance to learn from experts.

I have also a similar problem with a client computer running Ubuntu 20.04: Just formatted one of the HDDs in the Ubuntu client (FAT format) and after that created a folder "test-backup". I put one small file in the folder for testing the connection to unraid. Within Ubuntu I shared the folder with full write/read permissions. I also can see the shared of Unraid from the Ubuntu client. But when I want to connect and mount this disk on the Unraid server as unassigned disk, it doesn't work... All I get is this: The smb disk from Ubuntu is greyed out and obviously mounting is impossible... What could be a reason ? Originally I had the disk formatted in ext4 (native Ubuntu), then thought this format might be not supported and reformat in FAT, but still no success... I have tried everything I could think of... (but I am at the beginning of the lerning curve...) Thanks for advice.

Learning more details of Unraid as a newcomer, I start using the plug-in ca-fix-common-problems to optimize my installation: After having run it for the first time I notice this warning: -CPU possibly will not throttle down frequency at idle and -Your CPU is running constantly at 100% and will not throttle down when its idle (to save heat / power). This is because there is currently no CPU Scaling Driver Installed. Seek assistance on the unRaid forums with this issue I am using an old Supermicro tower with Dual Xeon E 5405 Harpertown @ 2Ghz The mainboard is the X7DVL I guess the CPU is that old that there is no way to optimize and make the warning disappear ? What is that CPU scaling Driver - do I need to get it from Intel or Supermicro ? Or just keep it as it is and wait until there is budget for new hardware (could take 2 years - servers are so expensive here...) Thanks for info.