[Parity orange after replacing dead disk]

After 5 minutes of idling after a reboot to obtain the information needed for this post.

 

Syslog had been written to again.

 

Nov 19 03:18:47 SALLY kernel: ata8: hard resetting link

Nov 19 03:18:49 SALLY kernel: ata8: SATA link down (SStatus 0 SControl 300)

Nov 19 03:18:49 SALLY kernel: ata8.00: link offline, clearing class 1 to NONE

Nov 19 03:18:49 SALLY kernel: ata8: EH complete

Nov 19 03:18:49 SALLY kernel: ata8.00: detaching (SCSI 8:0:0:0)

Nov 19 03:18:49 SALLY kernel: sd 8:0:0:0: [sdk] Synchronizing SCSI cache

Nov 19 03:18:49 SALLY kernel: sd 8:0:0:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00

Nov 19 03:18:49 SALLY kernel: sd 8:0:0:0: [sdk] Stopping disk

Nov 19 03:18:49 SALLY kernel: sd 8:0:0:0: [sdk] START_STOP FAILED

Nov 19 03:18:49 SALLY kernel: sd 8:0:0:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00

Nov 19 03:18:49 SALLY kernel: ata8: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen

Nov 19 03:18:49 SALLY kernel: ata8: irq_stat 0x00000040, connection status changed

Nov 19 03:18:49 SALLY kernel: ata8: SError: { CommWake DevExch }

Nov 19 03:18:49 SALLY kernel: ata8: hard resetting link

Nov 19 03:18:50 SALLY kernel: ata8: SATA link down (SStatus 0 SControl 300)

Nov 19 03:18:50 SALLY kernel: ata8.00: link offline, clearing class 1 to NONE

Nov 19 03:18:50 SALLY kernel: ata8: EH complete

Nov 19 03:18:50 SALLY kernel: ata8: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Nov 19 03:18:50 SALLY kernel: ata8: irq_stat 0x00000040, connection status changed

Nov 19 03:18:50 SALLY kernel: ata8: SError: { DevExch }

Nov 19 03:18:50 SALLY kernel: ata8: limiting SATA link speed to 1.5 Gbps

Nov 19 03:18:50 SALLY kernel: ata8: hard resetting link

 

[Parity orange after replacing dead disk]

Unraid version 4.7

 

I am having a rather strange problem after replacing a dead disk.

 

I replaced a 1.5tb drive with a 2tb drive recently. After powering the machine down and then booting it back up expecting to just be able to format the drive and then check the box to do a parity rebuild. Instead, both the new drive and the parity are showing as orange with the new disk showing as "unformatted" (shown in main.png).

 

When I check the the box to confirm that I want to do this and attempt to format the new disk it appears to start formatting and then immediately after clicking refresh it is back at the same prompt as main.png. In that time, various errors have been output to syslog (syslog-error.txt).

 

I have tried doing a pre-clear on /dev/sda.. the new disk but the status of the main page has not changed afterwards. The array comes online but I am unable to bring the new 2tb drive into the array and too scared to write any more data to it with the parity drive in its current state. My understanding is that orange on a parity drive means that a parity rebuild is in place... Not really sure how to proceed here since the drive has been in this state for a week now.

 

Any help is appreciated

 

Thanks.

 

Al.

 

syslog-error.txt