hey, i just loged into the server config page just wanted to check my current free space available and noticed the parity drive has gone red  , and shows 688 errors.

 

the severs still up and running sharing everything fine. so not sure if i should just do a restart and parity sync to see if it works itself out or not?

 

system log attached

 

hey, i just loged into the server config page just wanted to check my current free space available and noticed the parity drive has gone red  , and shows 688 errors.

 

the severs still up and running sharing everything fine. so not sure if i should just do a restart and parity sync to see if it works itself out or not?

 

system log attached

 

Your parity drive was taken out of service because it was determined to be un-writable. 

First error was a Un-recoverable handshake. It tried to reset itself a few times.

Nov 29 17:45:32 Server kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6
Nov 29 17:45:32 Server kernel: ata4.00: BMDMA stat 0x66
Nov 29 17:45:32 Server kernel: ata4: SError: { UnrecovData Handshk }
Nov 29 17:45:32 Server kernel: ata4.00: cmd ca/00:08:3f:00:d8/00:00:00:00:00/e7 tag 0 dma 4096 out
Nov 29 17:45:32 Server kernel:          res 51/84:03:44:00:d8/00:00:00:00:00/e7 Emask 0x30 (host bus error)
Nov 29 17:45:32 Server kernel: ata4.00: status: { DRDY ERR }
Nov 29 17:45:32 Server kernel: ata4.00: error: { ICRC ABRT }
Nov 29 17:45:32 Server kernel: ata4: hard resetting link
Nov 29 17:45:32 Server kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 29 17:45:33 Server kernel: ata4.00: NODEV after polling detection
Nov 29 17:45:33 Server kernel: ata4.00: revalidation failed (errno=-2)
Nov 29 17:45:33 Server kernel: ata4: failed to recover some devices, retrying in 5 secs
Nov 29 17:45:38 Server kernel: ata4: hard resetting link
Nov 29 17:45:38 Server kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 29 17:45:38 Server kernel: ata4.00: configured for UDMA/133
Nov 29 17:45:38 Server kernel: ata4.01: configured for UDMA/133
Nov 29 17:45:38 Server kernel: ata4: EH complete

 

That was followed by a series of similar errors:

Nov 29 17:47:11 Server kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen
Nov 29 17:47:11 Server kernel: ata4: SError: { UnrecovData Handshk }
Nov 29 17:47:11 Server kernel: ata4.00: cmd 35/00:90:c7:b3:79/00:01:42:00:00/e0 tag 0 dma 204800 out
Nov 29 17:47:11 Server kernel:          res 40/00:03:44:00:d8/00:00:00:00:00/e7 Emask 0x14 (ATA bus error)
Nov 29 17:47:11 Server kernel: ata4.00: status: { DRDY }

 

Then a series of errors exist in the log as it tried to write to the drive.

ov 29 17:47:12 Server kernel: ata4: EH complete
Nov 29 17:47:12 Server kernel: md: disk0 write error
Nov 29 17:47:12 Server kernel: handle_stripe write error: 1115272072/0, count: 1
Nov 29 17:47:12 Server kernel: md: disk0 write error
Nov 29 17:47:12 Server kernel: handle_stripe write error: 1115272080/0, count: 1
Nov 29 17:47:12 Server kernel: md: disk0 write error
Nov 29 17:47:12 Server kernel: handle_stripe write error: 1115272088/0, count: 1
Nov 29 17:47:12 Server kernel: md: disk0 write error
...
...

 

I would stop the array, power down, UN-PLUG from the AC Outlet, open the case, check the cable to the parity drive to be sure it is plugged in securely. 

(Can you tell I don't like working on stuff while it is still plugged into the wall outlet?)

 

If the drive comes back to life, and it will let you rebuild parity onto it, cool...  If not, time to replace it. 

You may need to un-assign the parity drive, then reboot, then re-assign it as parity to get the unRAID software to take it back into the array and re-build parity onto it.

 

Joe L.

all good, was pretty sure thats what i needed to do. but thought i had better double check before i do something i might of regreted