I had some kind of error that ended up disabling my parity disk (I think maybe my PSU died but can't check that out till tomorrow).  Anyway, I rebooted the machine and after doing that the machine refuses to boot and one of my data disks is constantly beeping and the only way I can boot is to unplug that disk. 

 

While I'm hoping a new PSU solves these issues, how do I go about forcing it to trust the parity to recover some of this data if I have to replace both disks?  Whenever I boot I get a blue dot telling me that the parity drive is new and don't see a "Trust parity" option anywhere though maybe this will show up if I had replaced the failed disk. (I'm using 5.0beta14 I believe).

 

Thanks

I had some kind of error that ended up disabling my parity disk (I think maybe my PSU died but can't check that out till tomorrow).  Anyway, I rebooted the machine and after doing that the machine refuses to boot and one of my data disks is constantly beeping and the only way I can boot is to unplug that disk. 

 

While I'm hoping a new PSU solves these issues, how do I go about forcing it to trust the parity to recover some of this data if I have to replace both disks?  Whenever I boot I get a blue dot telling me that the parity drive is new and don't see a "Trust parity" option anywhere though maybe this will show up if I had replaced the failed disk. (I'm using 5.0beta14 I believe).

 

Thanks

Contact Tom @ lime-tech.  trusting parity ONLY works if you have all working data drives and do not wish to re-calculate parity.  You need a different procedure that will force the one defective data disk to be recognized as defective and the parity disk to be considered valid.    it is similar, but instead of forcing parity to be valid, you are forcing a different disk to be invalid.    DO NOT USE THE New-Config button on the user  interface as it will cause the array to forget the defective disk exists.

 

Joe L.

Yes, it's rather more complex then trust my parity. As far as I know, you can't put the array back into disk simulation mode because you will need a disk in the failed location. You basically need to replace the drive and then force unRAID to rebuild onto that drive.

 

1. Create an unRAID partition on the replacement disk.

2. Use the New-Config util to re-initialize the array.

3. Assign all the drives back to the proper disk spots and assign the replacement to the failed spot.

4. Type "mdcmd set invalidslot ##" at the command prompt, where ## is the disk number of the replaced disk. This tells unRAID which disk to rebuild.

5. Start the array.

6. I believe you also have to click a button to start the actual rebuild.

 

I'm not positive if #1 is required. However, there was a case or 2 on 4.x versions of unRAID where this was attempted without creating a partition and the rebuilt drive didn't have one after which required extra work to attempt recovery. You can do a new-config and asign just the replacement drive to say disk1 and start and stop the array and the disk will have the partition written.

 

Thank you both for your help.  It appears my fears may have been unnecessary.  With a new power supply I have all working drives now, just need to rebuild parity.