Hello,

 

After running pre-clear on a new parity disk, I am now getting an error on one of my data disks that the drive is unmountable, and when I start the array, it is asking me to format the drive.  Is there anyway I can save or recover the data on this disk?

 

tower-diagnostics-20151004-2101.zip

Since you just swapped out drives, it would be prudent to check the cabling (power and sata) to all the drives and the motherboard (unplug and replug in)  Right before unRaid tries to mount the drive, you've got a ton of errors:

 

Oct  3 09:09:11 Tower kernel: ata8.00: limiting speed to UDMA/100:PIO4
Oct  3 09:09:11 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x1c00000 action 0x6
Oct  3 09:09:11 Tower kernel: ata8.00: BMDMA stat 0x24
Oct  3 09:09:11 Tower kernel: ata8: SError: { Handshk LinkSeq TrStaTrns }
Oct  3 09:09:11 Tower kernel: ata8.00: failed command: WRITE DMA
Oct  3 09:09:11 Tower kernel: ata8.00: cmd ca/00:10:a8:9b:00/00:00:00:00:00/e0 tag 0 dma 8192 out
Oct  3 09:09:11 Tower kernel:         res 51/84:01:b6:9b:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Oct  3 09:09:11 Tower kernel: ata8.00: status: { DRDY ERR }
Oct  3 09:09:11 Tower kernel: ata8.00: error: { ICRC ABRT }
Oct  3 09:09:11 Tower kernel: ata8: hard resetting link
Oct  3 09:09:11 Tower kernel: ata8: nv: skipping hardreset on occupied port
Oct  3 09:09:11 Tower kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct  3 09:09:11 Tower kernel: ata8.00: configured for UDMA/100
Oct  3 09:09:11 Tower kernel: ata8: EH complete
Oct  3 09:09:11 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x6
Oct  3 09:09:11 Tower kernel: ata8.00: BMDMA stat 0x24
Oct  3 09:09:11 Tower kernel: ata8: SError: { Handshk }
Oct  3 09:09:11 Tower kernel: ata8.00: failed command: WRITE DMA
Oct  3 09:09:11 Tower kernel: ata8.00: cmd ca/00:10:a8:9b:00/00:00:00:00:00/e0 tag 0 dma 8192 out
Oct  3 09:09:11 Tower kernel:         res 51/84:01:b6:9b:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Oct  3 09:09:11 Tower kernel: ata8.00: status: { DRDY ERR }
Oct  3 09:09:11 Tower kernel: ata8.00: error: { ICRC ABRT }
Oct  3 09:09:11 Tower kernel: ata8: hard resetting link
Oct  3 09:09:11 Tower kernel: ata8: nv: skipping hardreset on occupied port
Oct  3 09:09:12 Tower kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct  3 09:09:12 Tower kernel: ata8.00: configured for UDMA/100
Oct  3 09:09:12 Tower kernel: ata8: EH complete
Oct  3 09:09:12 Tower kernel: ata8.00: limiting speed to UDMA/33:PIO4
Oct  3 09:09:12 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x6
Oct  3 09:09:12 Tower kernel: ata8.00: BMDMA stat 0x24
Oct  3 09:09:12 Tower kernel: ata8: SError: { Handshk }
Oct  3 09:09:12 Tower kernel: ata8.00: failed command: WRITE DMA
Oct  3 09:09:12 Tower kernel: ata8.00: cmd ca/00:10:a8:9b:00/00:00:00:00:00/e0 tag 0 dma 8192 out
Oct  3 09:09:12 Tower kernel:         res 51/84:01:b6:9b:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Oct  3 09:09:12 Tower kernel: ata8.00: status: { DRDY ERR }
Oct  3 09:09:12 Tower kernel: ata8.00: error: { ICRC ABRT }
Oct  3 09:09:12 Tower kernel: ata8: hard resetting link
Oct  3 09:09:12 Tower kernel: ata8: nv: skipping hardreset on occupied port
Oct  3 09:09:12 Tower kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct  3 09:09:12 Tower kernel: ata8.00: configured for UDMA/33
Oct  3 09:09:12 Tower kernel: ata8: EH complete
Oct  3 09:09:12 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x6
Oct  3 09:09:12 Tower kernel: ata8.00: BMDMA stat 0x24
Oct  3 09:09:12 Tower kernel: ata8: SError: { Handshk }
Oct  3 09:09:12 Tower kernel: ata8.00: failed command: WRITE DMA
Oct  3 09:09:12 Tower kernel: ata8.00: cmd ca/00:10:a8:9b:00/00:00:00:00:00/e0 tag 0 dma 8192 out
Oct  3 09:09:12 Tower kernel:         res 51/84:01:b6:9b:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Oct  3 09:09:12 Tower kernel: ata8.00: status: { DRDY ERR }
Oct  3 09:09:12 Tower kernel: ata8.00: error: { ICRC ABRT }
Oct  3 09:09:12 Tower kernel: ata8: hard resetting link
Oct  3 09:09:12 Tower kernel: ata8: nv: skipping hardreset on occupied port
Oct  3 09:09:13 Tower kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct  3 09:09:13 Tower kernel: ata8.00: configured for UDMA/33
Oct  3 09:09:13 Tower kernel: ata8: EH complete
Oct  3 09:09:13 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x6
Oct  3 09:09:13 Tower kernel: ata8.00: BMDMA stat 0x24
Oct  3 09:09:13 Tower kernel: ata8: SError: { Handshk }
Oct  3 09:09:13 Tower kernel: ata8.00: failed command: WRITE DMA
Oct  3 09:09:13 Tower kernel: ata8.00: cmd ca/00:10:a8:9b:00/00:00:00:00:00/e0 tag 0 dma 8192 out
Oct  3 09:09:13 Tower kernel:         res 51/84:01:b6:9b:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Oct  3 09:09:13 Tower kernel: ata8.00: status: { DRDY ERR }
Oct  3 09:09:13 Tower kernel: ata8.00: error: { ICRC ABRT }
Oct  3 09:09:13 Tower kernel: ata8: hard resetting link
Oct  3 09:09:13 Tower kernel: ata8: nv: skipping hardreset on occupied port
Oct  3 09:09:13 Tower kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct  3 09:09:13 Tower kernel: ata8.00: configured for UDMA/33
Oct  3 09:09:13 Tower kernel: ata8: EH complete
Oct  3 09:09:13 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x6
Oct  3 09:09:13 Tower kernel: ata8.00: BMDMA stat 0x24
Oct  3 09:09:13 Tower kernel: ata8: SError: { Handshk }
Oct  3 09:09:13 Tower kernel: ata8.00: failed command: WRITE DMA
Oct  3 09:09:13 Tower kernel: ata8.00: cmd ca/00:10:a8:9b:00/00:00:00:00:00/e0 tag 0 dma 8192 out
Oct  3 09:09:13 Tower kernel:         res 51/84:01:b6:9b:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Oct  3 09:09:13 Tower kernel: ata8.00: status: { DRDY ERR }
Oct  3 09:09:13 Tower kernel: ata8.00: error: { ICRC ABRT }
Oct  3 09:09:13 Tower kernel: ata8: hard resetting link
Oct  3 09:09:13 Tower kernel: ata8: nv: skipping hardreset on occupied port
Oct  3 09:09:14 Tower kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct  3 09:09:14 Tower kernel: ata8.00: configured for UDMA/33

which could be consistent with bad cabling.

 

Opened up the case and re-confirmed all of the cable connections.  When I power up the server and hover over the drive I see a message 'Device is disabled, contents emulated'.

Opened up the case and re-confirmed all of the cable connections.  When I power up the server and hover over the drive I see a message 'Device is disabled, contents emulated'.

So is this different than your OP? Is the array started? Post another screenshot.

Thanks for the reply.  I will upload a screen shot when I get to the machine later.  The drive that reported the issue has an X next to it and when i hover over it I see the message I mentioned in the previous message.  I did not want to start the array until I received confirmation that it was OK to do so.

As requested.  I have a picture of the error I am seeing on screen, and a new diagnostic report.

tower-diagnostics-20151005-1723.zip

According to the legend in Help, the parity drive is also emulated, which is nonsense.

 

Will it let you start the array? If so then the way forward would seem to be to rebuild the drive then try to recover the filesystem on it, but it's unclear what it thinks the state of parity is. Do you have another drive you could rebuild to?

This is the problem.  There is no parity drive to rebuild from.  The parity drive was just pre-cleared to add to the array.  It was after or during the preclear when the error started.  The drive is ready to run the parity sync, but now one of the data drives is showing errors.  The timing is horrible.

Was the drive reiserfs? You might be able to recover some of its data using reiserfsck.

OK I see some instructions regarding that. I will give it a try.