Hi,

 

Received worrisome messages (via prowl) that my parity disk was in an error state so remote desktop'ed into a machine on that LAN and had a look, sure enough had a red X for the parity disk.

 

Ran the diagnostics (couldn't attach as it's 210kb and limit here is 192kb) and it looks to have been unable to get any SMART data for that disk (an Seagate 8TB archive disk).

Attached is the disk error report obtained by clicking on the drive from the MAIN window.

 

Reading some of the help docs I have brought the array down and rebooted it in the hope of being able to get a SMART report, however there's no disk showing against the parity slot now, and there is none that can be selected from the dropdown - presumably this means a catastrophic failure of the disk or a cable issue.

 

I won't be able to get to the server until late Friday so trying to work out what to do next.

(I will buy another drive to take home with me just in case)

 

As I have backups of everything important on other disks / servers, and working on the assumption that one way or another parity is going to have to be rebuilt anyway, is it an option to bring the array back online and run unprotected for a few days ?

 

Thanks in advance for any wisdom you care to share.

 

Cheers,

Shane.

disk_error.pdf

You can start the array without parity, a parity sync will be needed when you add the parity disk, be it a new one or the old.

Feel the need to just make sure you know that you are running unprotected if you start the array without the parity drive. You probably know but can never be too safe.

Feel the need to just make sure you know that you are running unprotected if you start the array without the parity drive. You probably know but can never be too safe.

 

Thanks for checking, I realise the risk.

Cheers,

Shane.

config_folder.zip

system_folder.zip

SMART_folder.zip

You can start the array without parity, a parity sync will be needed when you add the parity disk, be it a new one or the old.

 

Thanks - up and running (albeit in risky mode)

Without the syslog we can't easily identify which of the drives in your SMART is the parity drive, but after looking at them I would guess it is ST8000AS0002-1NA17Z_Z8408EA6 since that one is not really reporting its SMART for us. Have you checked your connections?

Without the syslog we can't easily identify which of the drives in your SMART is the parity drive, but after looking at them I would guess it is ST8000AS0002-1NA17Z_Z8408EA6 since that one is not really reporting its SMART for us. Have you checked your connections?

 

I've attached the syslog, and can confirm you're correct about the disk in question.

Not able to get to the server until Friday so can't check any connections at the moment - that will be more of a re-seat than anything as it's a HP N54L microserver with drive bays (drive bolted into a cage which seats into the bay)

syslog.txt.zip