November 11, 201312 yr Good day Unraid Community! I've been using this product for a few years now, upgrading along the way from 4.7 to most of the 5.0 betas to finally upgrade to 5.0 final about 5 days ago. To be real honest though, I've mainly built my server once and haven't played much with it after that other than adding new drives. My server being almost full, I've went ahead and purchased a new 4TB WD Red HDD to replace my current parity and take the current 3TB parity and use it as a storage disk in my array. For months/years, I've never had any parity errors when doing the monthly checks. Using Unmenu, I've noticed that a few months ago, my 2TB drive started having lots of erros on it (by looking into MyMain and checked Smart properties). I thought about changing it but noticed the montly check would show up normal every month; therefore, I've decided to wait a little longer. Today, I've went ahead upgrading my parity. Here's what I've done: Stop my Unraid server Shut it down Plug in the new 4TB HDD on the main motherboard (to do this, I've moved that failing 2TB drive HDD from the motherboard to an external Monoprice SATA controller and plugged the new 4TB onto the motherboard for better speed) Boot up the server Assign the new parity Start the array Rebuilding parity started During the rebuild, I've noticed millions of errors showing up onto that "failing" 2TB drive and I got scared; hence why I'm writing this! On top of that, my disk #1 which was running flawlessly also started having errors for an unknown reason. After almost 24h of rebuild letting the erros accumulate, I got to around 75% of rebuild. Suddenly, my server was unaccessible. I couldn't ping it, couldn't access it... but it was still running. I had no choice to force reboot it. Then, I've restared the array and got into the parity-sync check. Same business again, tons of errors showing up on my 2TB drive... Here was my setup before attempting to upgrade the parity: Unraid 5.0 Final Before parity upgrade: ============================================================================================================================================ Parity Hitachi_HDS5C3030ALA630_MJ1311YNG377DA (sde) 2930266584 3 TB Disk 1 Hitachi_HDS5C3030ALA630_MJ1311YNG4K90A (sdc) 2930266532 31 °C 3 TB 2.98 TB 22.0 GB 6552 15 0 Browse /mnt/disk1 Disk 2 Hitachi_HDS5C3030ALA630_MJ1311YNG4JXHA (sdd) 2930266532 31 °C 3 TB 2.98 TB 24.7 GB 13,741 15 0 Browse /mnt/disk2 Disk 3 WDC_WD30EZRX-00MMMB0_WD-WCAWZ2804777 (sdf) 2930266532 39 °C 3 TB 2.99 TB 15.3 GB 97,040 15 0 Browse /mnt/disk3 Disk 4 WDC_WD20EARS-00MVWB0_WD-WMAZ20280672 (sdi) 1953514552 30 °C 2 TB 1.98 TB 23.8 GB 5970 15 0 Browse /mnt/disk4 Disk 5 WDC_WD30EZRX-00DC0B0_WD-WMC1T0134962 (sdg) 2930266532 36 °C 3 TB 2.96 TB 40.2 GB 4370 15 0 Browse /mnt/disk5 Disk 6 WDC_WD30EZRX-00DC0B0_WD-WMC1T0590261 (sdh) 2930266532 36 °C 3 TB 2.96 TB 38.6 GB 4367 15 0 Browse /mnt/disk6 ============================================================================================================================================ Total Array size of disks (including parity) 35.3 °C 21 TB 16.8 TB 163 GB 191,146 5172 1,236,450 After parity upgrade: ============================================================================================================================================ Parity WDC_WD40EFRX-68WT0N0_WD-WCC4E0099957 (sdb) 3907018532 39 °C 4 TB - - 1 1351 0 Disk 1 Hitachi_HDS5C3030ALA630_MJ1311YNG4K90A (sdc) 2930266532 31 °C 3 TB 2.98 TB 22.0 GB 6552 15 0 Browse /mnt/disk1 Disk 2 Hitachi_HDS5C3030ALA630_MJ1311YNG4JXHA (sdd) 2930266532 31 °C 3 TB 2.98 TB 24.7 GB 13,741 15 0 Browse /mnt/disk2 Disk 3 WDC_WD30EZRX-00MMMB0_WD-WCAWZ2804777 (sdf) 2930266532 39 °C 3 TB 2.99 TB 15.3 GB 97,040 15 0 Browse /mnt/disk3 Disk 4 WDC_WD20EARS-00MVWB0_WD-WMAZ20280672 (sdi) 1953514552 30 °C 2 TB 1.98 TB 23.8 GB 5970 15 0 Browse /mnt/disk4 Disk 5 WDC_WD30EZRX-00DC0B0_WD-WMC1T0134962 (sdg) 2930266532 36 °C 3 TB 2.96 TB 40.2 GB 4370 15 0 Browse /mnt/disk5 Disk 6 WDC_WD30EZRX-00DC0B0_WD-WMC1T0590261 (sdh) 2930266532 36 °C 3 TB 2.96 TB 38.6 GB 4367 15 0 Browse /mnt/disk6 ============================================================================================================================================ Total Array size of disks (including parity) 35.3 °C 21 TB 16.8 TB 163 GB 191,146 5172 1,236,450 +++ Hitachi_HDS5C3030ALA630_MJ1311YNG377DA (sde) 2930266584 3 TB You'll notice the Hitachi not on the array. That's my old parity which I haven't touched yet because I'm wondering if I couldn't use it to restore my 2TB drive... Basically, I'm wondering what do I need to do at this point. Will I lose any data? If I let my parity rebuild fully, will I lose everything onto that 2TB drive? Is there a way to make sure I do not lose anything? Can I use that old parity to rebuild that old 2TB (I'll buy a new HDD to make sure everything is ok) Here are some smart reports from all my drives (include in attachment) The syslog file is too big to fit in attachment so I might need to find another way to inlucde it. I'll update my following post with it. Thanks a lot for your help and have a good day! smart.txt
November 11, 201312 yr I'm no expert.... but why not hold off on the 4TB rebuild for now and put your old parity back in. Since you have to replace the failing Disk(Disk #4) anyway, just go grab a new Disk and have the old parity rebuild it. Once you are set with the new data Disk rebuilt and all Disks green balled, then you should proceed to rebuild 4TB parity. Downside though.. If your disk#1 is showing errors at the same time, you may be in for an unsurmoutable challenge. I dont think the failure of two drives at the same time can be recovered. It may be that your Disk one errors are not an indication of failure, but maybe a power issue or an unsecure cable, no matter, I would still plan to either rebuild Disk#1 with the current disk or a new one. But, if you can rebuild Disk#4 with no issue, then you can proceed to rebuild Disk#1 as well. I would stop trying to replace/rebuild parity until your Server is 100%. Tough break, but hopfully you can get back up and running soon!
November 11, 201312 yr Author Thanks cpthook for your reply. Yeah, I think it makes a lot of sense to wait for the parity rebuild at that point. I'll order a new drive in the meantime. My main concern at that point is how to put back my old parity and make sure everything is ok? Right now, if I attempt to put back my old parity, it'll say it's invalid... How can I make it trust my old HDD as the parity? Thanks again and have a good day!
November 11, 201312 yr I'm not an expert either but I think as long as you haven't written anything else to the array since trying to replace the parity drive that when you try to swap back the old parity drive then you'll have to "force" the array to trust parity from the old 3TB drive. I'm not sure of the exact steps but since I'm in the process of preclearing and upgrading my parity drive, I asked a similar "hypothetical" quesiton in another thread and it was reported that I could definitely use the old parity drive to fix a failed drive while parity was rebuilding on the new drive. I think you'll want to take this slow though and get some step by step advice from some of the more experienced members. Good luck!
November 11, 201312 yr Author Thanks betaman for the info. I've ordered a new 3TB WD Red HDD to replace my failing 2TB and I'll definitely take this slow because I definitely do not want to lose 2TB of data. Any expert on the matter could point me out in the right direction, please? Thanks a bunch!
November 12, 201312 yr See here: http://lime-technology.com/forum/index.php?topic=30009.0 What an informative post, saving to my favorites..ThankYou!! Successful troubleshooting tips like this just reinforces my confidence trusting my data to unRAID. @AlexRitcher.. I hope this works for you too!!
November 12, 201312 yr Author Good day guys! Thanks for the link dgaschk! Much appreciated! Funny thing happened on my end. I had stopped the parity-sync to shut down the server and check the cabling of that faulty HDD. I changed the port on the SATA card where it was hooked to and restarted the parity-sync and no errors this time I'm a bit confused as to why so I'm guessing all those errors were probably because the SATA port was not doing its job properly. Should I trust the parity at this point? Nonetheless, I've restarted a parity-check to make sure it doesn't find any errors but is it safe to assume that if I do not get any errors on the parity-check, the parity is fine and all my data is protected?
Archived
This topic is now archived and is closed to further replies.