Invalid Parity

[newskin]

Woke up this morning to find the gui showing my parity 'invalid' . Not sure how long it has been that way, but did a full reboot expecting at worse case I would have to simply rebuild it. On reboot unRaid insists it is invalid and offers no recovery options.

 

I have ssh'd onto my nas and manually run smartctl on the device in question which passes, telling me the device is up and running as far as Linux is concerned. What is the best way to proceed from here? Can I just blow away the partitions and will unRaid rebuild for me, should I rebuild myself or is there a better way?

 

Thanks!

[itimpi]

Woke up this morning to find the gui showing my parity 'invalid' . Not sure how long it has been that way, but did a full reboot expecting at worse case I would have to simply rebuild it. On reboot unRaid insists it is invalid and offers no recovery options.

 

I have ssh'd onto my nas and manually run smartctl on the device in question which passes, telling me the device is up and running as far as Linux is concerned. What is the best way to proceed from here? Can I just blow away the partitions and will unRaid rebuild for me, should I rebuild myself or is there a better way?

It would be useful to show a screenshot of exactly what you mean.

 

It almost might be worth posting diagnostics (Tools->Diagnostics) to see if anyone can spot an issue.

 

[newskin]

The device is question is sdc (id ending WMC4N0F79CZW). Unraid has marked it as faulty (red x in dashboard). Logs show status is DISK_DSBL. In the attached files, the output of 'smartctrl -s on --test=short /dev/sdc' is a result of a test I ran from the shell, the GUI options were ghosted.

 

I don't know what test unRAID does to flag a disk as DISK_DSBL, but I can't see anything physically wrong with the device.

 

Logs attached.

 

nas-diagnostics-20151003-0913.zip

[itimpi]

I don't know what test unRAID does to flag a disk as DISK_DSBL, but I can't see anything physically wrong with the device.

A disk is marked as disabled when a  write to it fails (whatever the reason).  The only way to clear that state is to rebuild the drive.

[newskin]

OK, started the process - rebuilt the GPT hoping that would kick unRAID into recognising an unformatted disk and then I could format via gui. But it is still showing as invalid with no option to format. I am hesitant to format the xfs partition manually as I don't know what flags unRAID sets and assume that all drives need to be identical. Can I just mkfs.xfs /dev/sdc1 ?

[newskin]

OK, got it sorted. For anyone coming across this in a similar situation re their parity disk, I set the 'invalid' parity disk as a new array member which caused unRAID to format it. Then assign it back to parity. This will cause an error due to missing disks, but then via tools/new config you can reset it.

 

Thanks itimpi for the guidance.

[trurl]

OK, got it sorted. For anyone coming across this in a similar situation re their parity disk, I set the 'invalid' parity disk as a new array member which caused unRAID to format it. Then assign it back to parity. This will cause an error due to missing disks, but then via tools/new config you can reset it.

 

Thanks itimpi for the guidance.

For anyone that does come across this, this is totally wrong. There is no reason to format the parity disk or rebuild the GPT. The parity disk is never formatted since it doesn't have a filesystem.

 

Glad you got it sorted, but don't know why you didn't (or couldn't) just rebuild parity.

 

*edit*

 

Probably all you needed to do was unassign parity, start the array, stop the array, reassign parity, start the array and unRAID would rebuild. The unassignment is necessary whenever you want unRAID to use the same disk that it has disabled, whether parity or a data disk.