gerhard911

I have replaced / rebuilt a data disk three times now and after each parity sync which appears to run successfully I end up with a message after starting the array that the disk is unmountable with no file system. This all started with data disk5 showing a lot of read errors. It was an older 8TB HGST drive so I swapped in a newer Segate 8TB and synched parity. That rebuild worked fine but the new drive also experienced read errors. Having planned to increase this server's capacity anyway, I purchased a pair of Segate 14TB drives and replaced the 10TB parity drive with a 14TB drive and rebuilt parity. That appeared to run without issues so I swapped out the Seagate 8TB disk5 for the previous parity 10TB drive and rebuilt data. That resulted in my first unmountable disk. I stopped the array, unassigned the 10TB disk and moved it to a previously unused SATA port. Restart the server, assign the 10TB disk to disk5 and rebuild data. Again, after appearing to rebuild successfully I end up with an unmountable drive. So I swap the SATA port & cable between disk5 and a cache pool drive and rebuild a third time. Same result with disk5 (unmountable) but now the cache drive is also unmountable. I downloaded diagnostics after each step and am attaching those .zip files. I also took screen captures of the Main page after each step in the parity sync / restart process and will attach those .jpg files. I realize now I should have probably saved the original 10TB parity drive intact and rebuilt disk5 on the other new 14TB. I am concerned that the unmountable disk issue is due to something happening with the 14TB parity drive swap. So I am tempted to rebuild parity with the original 8TB drive but need to know if I can trust the original 8TB disk5's data. Is there a way I can check that drive to see if it's data is intact? I have the Unassigned Devices plugin but don't know if / how it can be used to do this. Many thanks for any advice or assistance. unraid2-diagnostics-Parity sync done.zip unraid2-diagnostics-Parity sync stopped.zip unraid2-diagnostics-Post parity sync unmountable.zip

OK, thanks for the followup. We are assuming that even though disk13 had a bunch of read errors and got disabled, that the data on it will be fine if it mounts with UD in read only mode.

OK, I apologize I don't know what 'with UD in read-only mode' means. Is that starting the array in 'Maintenance Mode'? How do I confirm it has mounted correctly? I'm also a bit confused about the details of the new config process. Please bear with me and confirm I have this right. I replace the improperly rebuilt 14TB with the original 10TB. Then I do a New Config using what 'Preserve current assignments' ? It seems I would check both Parity slots and Data slots. I follow the New Config by rebuilding data on disk6. Is this what you referred to as a parity resync? Following that I can reattempt my 10TB to 14TB upgrade. Thanks for your expertise!

After reboot disk13 still disabled. I did not restart the array. I know my original disk6 has all data intact and parity should be in sync with that disk. Again, is there a way (new config ?) to rebuild disk13 from parity with my original disk6 ? unraid1-diagnostics-reboot-20200907-1104.zip

Here is the syslog during the rebuild. unraid1-14TB rebuild disk errors-syslog-20200904-1817.zip

unraid1-diagnostics-disk13 disabled-20200907-1014.zip

I was upgrading a 10TB disk to a 14TB disk (#6) and during the rebuild hundreds of thousands of read errors were reported on a 4TB disk (#13). The rebuild seemed to complete successfully but I can see that the rebuilt drive is missing most of the data it should have. Additionally, disk13 is now in a disabled state. I have the original 10TB disk6 intact. No data has been written to the array since the rebuild so parity should reflect the state of the array before rebuilding. So it seems to me that there should be some way to put the original disk6 back in and tell unRaid to rebuild disk13. Can this be accomplished or am I going to lose data? TIA for any advice or assistance.

I have now been running on dual power supplies for several days. I have started and stopped the array several times without any unclean shutdowns. Thanks to Constructor I'm going to mark this thread 'solved'.

So after the parity check completed, I carefully spun up the drives one at a time before stopping the array. All good! I attempted to replace the PS with an Antec 620W but because HP, the PCIe MB connector was non standard. So I hot wired a 480W Seasonic and am running dual PS. The MB, 1x10TB and 2 cache drives on the HP PS and all of the other drives on the Seasonic (5 each on two different rails). Fingers crossed.

The server is an HP Proliant ML150G6. The power supply is a Delta Electronics DPS-480DB-2A. Specs listed on the label are Max power 480W at 12Va and Max Combined power 385W. 10 data drives (6x8 + 4x10TB) 2x1TB SSD cache and 10TB parity. Guess I need to check power requirements and add them all up. Thanks

I have an unRAID server that has been plagued with unclean shutdowns for quite a while now. Initially it would only happen occasionally when a seemingly normal shutdown was performed. Now it happens with every shutdown. I have scoured syslogs finding nothing abnormal to my eye. I have also tried to determine a pattern of circumstance. This led me to suspect it was due to open files but using the Open Files tool to close suspect files would often cause an unclean shutdown itself. Making sure there were no open files from the client end did not help either. So today I had just completed a replace / rebuild of a data drive and clicked on the 'done' button. I then clicked on 'spin up all drives' and boom it triggered an unclean shutdown. syslog attached plus a screen capture of the flash drive showing no diagnostics log file. TIA for any advice or assistance. unraid2-mystery stop-syslog-20200901-1400.zip

Thank you very much itimpi !

Looking at my server's Main page, I just realized that the "All existing data on this device will be OVERWRITTEN when array is Started" warning appears to be associated with just my parity drive. I had been spooked that it meant that all data on the whole array would be overwritten. If I start my server as is, with 20 data drives can someone confirm that parity will be rebuilt based on the data on those drives? TIA

OK, I may have messed up in my attempt to shrink my 23 drive array down to 20. I cleared all data from the 3 drives I wanted to remove by moving it to two drives I was retaining that had sufficient space. I then physically removed the three drives and went to Tools and did a New Config with the default of 'retain none'. I had all of my drive assignments so I manually defined those on the Main page moving data drives up in the order to replace those removed. I now have parity and 20 data drives assigned but there is a warning that "All existing data on this device will be OVERWRITTEN when array is Started" ! I now realize that I missed the step of unassigning the three drives I was removing after doing a New Config and that I should have selected the 'retain all' option. So I'm pretty sure I don't want to start my array as it stands based on the warning but I do have the three drives that I removed and all of my data resides on the other 20 drives. Is there any way to get my array restarted, retain my data and rebuild parity? Ver 6.6.6 by the way. Thanks in advance for any help.

Thanks for confirming my understanding of the New Configuration tool. I have parity rebuilding now with the original disk 21. Unfortunately that will take ~ a day and a half. I also appreciate the SATA / USB docking station suggestion. My experience with those units, however has been poor. I have owned and used several, from multiple brands. Every single one eventually failed, some quite quickly. I suspected some cheap common chipset or other component was used in them all and gave up on the whole concept. I should put in a single port external SATA controller card so I can attach an external drive bay for such purpose in the future. Thanks again for your help itimpi !