Hi Guys,

 

I am running 6.1.3 and moved to a new mobo+cpu+ram. Upon boot, my parity drive became unmountable due to a bad sata cable. I changed out the cable but unraid has marked the parity as invalid with new SMART errors. On top of this, I have another disk which has been failed as is marked as unmountable, plus a hot spare which is also unmountable. Interestingly all 3 disks are Seagate 8TB, although different revisions.

 

I have dealt with bad disks, replacements and rebuilds in the past, but always when my parity was good. I am worried about rebuilding the parity now when I still have a disk offline.

 

I need some advice on how to proceed. Is it worthwhile picking up another disk to replace the failed data disk and hotspare? Should I rebuild parity then replace data disks?

 

Attached is the array view plus smart on all 3 disks.

 

Thanks!

 

ST8000AS0002-1NA17Z_Z8406LG8-20170805-1441.txt

ST8000AS0002-1NA17Z_Z840QBMT-20170805-1441.txt

ST8000AS0002-1NA17Z_Z8410JC7-20170805-1441.txt

Edited August 7, 20178 yr by swinkl3

Quote

my parity drive became unmountable due to a bad sata cable

 

I'm guessing you mean disable? You have both an invalid parity and disk2 with single parity, so disk2 can't be emulated, do a new config with only the data disks, if all 3 mount add a new parity disk, since current parity doesn't look very healthy and syn parity.

 

Tools -> New config -> Retain current config: All

 

Then unassign parity and start the array, if all 3 mount assign a new parity, if disk2 is still unmountable post the diagnostics.

 

2 hours ago, swinkl3 said:

plus a hot spare which is also unmountable

 

Is this a spare or does it have data? if it's a spare you can use it to replace parity, thought SMART also shows some issues, it's in better shape than current parity.

 

Edited August 5, 20178 yr by johnnie.black

Thanks for the feedback.

 

Quote

You have both an invalid parity and disk2 with single parity, so disk2 can't be emulated

 

I would agree, however, the console shows that disk2 is emulated - not sure how this is working though...

 

Considering parity was valid before the move, was marked invalid straight after and no data has been written to the array since - is there any way to remark the parity as valid?

 

The hotspare was actually a brand new disk that was used to rebuild the array but then unraid marked it faulty. This was one of the catalysts for the new hardware move as it looked like the motherboard was failing.

 

 

It shows emulated but it can't emulate the contents.

It's possible to mark parity as valid but unless disk2 was disabled prior to the move and data added to it since, that wouldn't be my recommendation, you can still do what I suggested and if it doesn't work try the parity option, just don't make any changes to the array data.

Ok cool. Disk 2 was already failed before the move, even though I have been able to get it back online previously by powercycling the machine. I would presume that the data is ok on the disk but i'm not 100% confident. The only option I have for new config is just new config - not to retain current config. I've got a screenshot. Is this still correct?

You're using an older version, you can still do it but you'll need to reassign all data disks after the new config.

Started a new config and all 3 data disks mounted ok. After checking it was ok, I shut down the array and reassigned one of the spares as a new parity and it's doing a parity rebuild on it. Hopefully it will be stable enough for me to go and get new disks or have them replaced under rma if they fail again.

 

Thanks so much for your help!