May 30, 20179 yr I am running unRAID Server Pro version: 5.0-rc4, and I have single parity drive, single cache drive, and 5 data drives. The scenario is such: Noticed I had a disk with some errors on it (disk4), and ran a parity check. During the parity check I heard some not normal drive noises so I opened up the case to see if I could pinpoint if it was the same drive or another (bad move). During that I must have bumped the cables enough to cause another drive (disk5) to disconnect, which then caused it to get a ton of errors, and to go redball, I made sure everything was snugly connected, then I ran SMART short test on disk5 and there where no errors or discernible issues from the output. I disabled the array, removed disk5, enabled the array, then disabled and re-added disk5. This then kicked off a data rebuild, and I've now noticed that disk4 is really failing (SMART shows a bunch of errors, errors on power on, Seek_Errors, Command timeouts, etc). Can do to stop the rebuild of disk4, and instead use a new disk to replace disk5 and build parity, or will I lose data off BOTH drives (disk4 and disk5) by doing this? Do I need to allow the data-rebuild to complete (currently estimated at ~18-30 days due to the failing disk4) prior to doing this? What happens if disk4 completely fails and stops working all together? I have pulled off the most important data, but I still have a lot of files on there I would prefer not to lose. Let me know what additional information may be needed and I will see if I can provide it. Thanks in advance.
May 30, 20179 yr Community Expert If I correctly understand what's happening you don't have a good chance of recovering both disks, cancel the rebuild and post syslog.
May 31, 20179 yr Author Well I may have lucked out, seems that the rebuild completed by the time I got back from work last night. I was then able to swap out the failed drive and then rebuild onto a new drive, and I am performing a parity check now with the new drive in place. Is there anything else I should check? Syslog has been clean since I removed the failed drive from the array.
May 31, 20179 yr Community Expert Most likely it rebuilt a corrupt disk, syslog would tell the story.
Archived
This topic is now archived and is closed to further replies.