May 3May 3 Community Expert 6 minutes ago, jparrott3 said:swapped the Barracuda out for an 8TB Exos and once that process was doneParity rebuilt to new parity disk.7 minutes ago, jparrott3 said:added a second 8TB Exos data driveDid you preclear the new data disk? Or did you let Unraid clear the new data disk? Or did you New Config and rebuild parity again?
May 3May 3 Author Just now, trurl said:Parity rebuilt to new parity disk.Correct.1 minute ago, trurl said:Did you preclear the new data disk? Or did you let Unraid clear the new data disk? Or did you New Config and rebuild parity again?I did not preclear the new disk. I don't remember if I did a New Config at that point but I've had to do a couple after reboots. Rebooted just now and Disk 2 is again showing errors. For some reason Disk 1is also spun down and won't spin up. unraid-diagnostics-20260503-1626.zip Edited May 3May 3 by jparrott3 Added diagnostics
May 3May 3 Community Expert Did you shutdown or try to fix it "hot"?Shutown, unplug DAS from PC and unplug both from power before trying again.
May 3May 3 Author OK. Shutdown, DAS and PC powered off and disconnected from each other. Everything plugged back in and powered back up. It is very upset.
May 3May 3 Community Expert USB is the reason it can't identify the drives. The USB interface is adding characters to the serial.And USB is probably the reason for the read errors we were having on disk2 earlier.You will have to New Config everything again. This time, in addition to checking the Parity Valid box, also check the Maintenance mode box. Then start the array. That will get all drives accepted again without altering any of them in any way since they won't be mounted in Maintenance mode.Then you can stop the array, unassign disk1.Then start the array with nothing assigned as disk1. Might as well start in Maintenance mode so no drives will be changed. That will disable disk1 again so we can try rebuild again. We won't be able to see if emulated disk1 is mountable in Maintenance mode, but at this point that would be the least of our concerns.Then stop the array, reassign disk1, start the array to try rebuild again. If there are any errors in the ERRORS column for any drive post new diagnostics.No guarantees anything will be recoverable. You would at least have the added expense of UFS Explorer Standard Edition.Might be simpler to just start over1 hour ago, jparrott3 said:I still have the DVD/Blu-Rays in storage.after you get a working setup.
May 3May 3 Author OK, I've followed the steps you gave and it's started rebuilding again. I really appreciate all your help so far. If I do start over, I don't suppose you have any recommendations on how to best use a Minisforum NAB9?
May 3May 3 Community Expert You could run Dockers/VMs from the SSD and have additional storage with USB as Unassigned Devices. Or even an array without parity. No parity would mean the array can't be out of sync so nothing would need rebuild. Of course no parity also means nothing can be rebuilt.
May 3May 3 Community Expert If you have to constantly New Config parity isn't doing anything for you anyway.
May 4May 4 Author Rebuild finished after about 13 hours without error. At this point if I want to try the UFS recovery (mainly to avoid re-ripping everything) is there anything else I need to do in Unraid before shutting down and pulling Disk 1?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.