Disk error - why is my syslog telling me? - General Support

December 20, 201510 yr

unRAID just disabled a disk in my array. Parity was checked yesterday and there were no errors. As far as I can remember, that disk had zero reallocated sectors and appeared to be perfectly health last time I checked (maybe a week ago) although it is an old WD 500G disk that is around 6 years old... I tried the "spinup" button but that didn't do anything.

My syslog shows the following... what does this mean? Is this a cable/power issue or is the disk really failed?

Dec 20 14:39:45 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

Dec 20 14:40:21 Tower kernel: mdcmd (49): spinup 8

Dec 20 14:40:21 Tower kernel: md: disk8: ATA_OP e3 ioctl error: -5

Dec 20 14:40:22 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

Dec 20 14:41:48 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

Dec 20 14:46:01 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

Quote

December 20, 201510 yr

Author

Disk log shows the following:

Dec 19 09:15:20 Tower kernel: ata17: SATA max UDMA/133 abar m2048@0xfdbff000 port 0xfdbff100 irq 27

Dec 19 09:15:20 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 09:15:20 Tower kernel: ata17.00: HPA detected: current 976771055, native 976773168

Dec 19 09:15:20 Tower kernel: ata17.00: ATA-7: WDC WD5000AAKS-00TMA0, WD-WMAPW1396640, 12.01C01, max UDMA/133

Dec 19 09:15:20 Tower kernel: ata17.00: 976771055 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

Dec 19 09:15:20 Tower kernel: ata17.00: configured for UDMA/133

Dec 19 09:15:20 Tower kernel: sd 16:0:0:0: [sdj] 976771055 512-byte logical blocks: (500 GB/465 GiB)

Dec 19 09:15:20 Tower kernel: sd 16:0:0:0: [sdj] Write Protect is off

Dec 19 09:15:20 Tower kernel: sd 16:0:0:0: [sdj] Mode Sense: 00 3a 00 00

Dec 19 09:15:20 Tower kernel: sd 16:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Dec 19 09:15:20 Tower kernel: sdj: sdj1

Dec 19 09:15:20 Tower kernel: sd 16:0:0:0: [sdj] Attached SCSI disk

Dec 19 09:15:34 Tower emhttp: WDC_WD5000AAKS-00TMA0_WD-WMAPW1396640 (sdj) 488385527

Dec 19 09:15:34 Tower kernel: md: import disk8: [8,144] (sdj) WDC_WD5000AAKS-00TMA0_WD-WMAPW1396640 size: 488385492

Dec 19 09:15:35 Tower emhttp: shcmd (16): /usr/local/sbin/set_ncq sdj 1 &> /dev/null

Dec 19 12:50:33 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 19 12:50:33 Tower kernel: ata17.00: failed command: IDENTIFY DEVICE

Dec 19 12:50:33 Tower kernel: ata17.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 13 pio 512 in

Dec 19 12:50:33 Tower kernel: ata17.00: status: { DRDY }

Dec 19 12:50:33 Tower kernel: ata17: hard resetting link

Dec 19 12:50:34 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 12:50:39 Tower kernel: ata17.00: qc timeout (cmd 0xec)

Dec 19 12:50:39 Tower kernel: ata17.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Dec 19 12:50:39 Tower kernel: ata17.00: revalidation failed (errno=-5)

Dec 19 12:50:39 Tower kernel: ata17: hard resetting link

Dec 19 12:50:39 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 12:50:39 Tower kernel: ata17.00: configured for UDMA/133

Dec 19 12:50:39 Tower kernel: ata17: EH complete

Dec 19 13:26:23 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 19 13:26:23 Tower kernel: ata17.00: failed command: SMART

Dec 19 13:26:23 Tower kernel: ata17.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 24 pio 512 in

Dec 19 13:26:23 Tower kernel: ata17.00: status: { DRDY }

Dec 19 13:26:23 Tower kernel: ata17: hard resetting link

Dec 19 13:26:24 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 13:26:24 Tower kernel: ata17.00: configured for UDMA/133

Dec 19 13:26:24 Tower kernel: ata17: EH complete

Dec 19 13:51:07 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 19 13:51:07 Tower kernel: ata17.00: failed command: IDENTIFY DEVICE

Dec 19 13:51:07 Tower kernel: ata17.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 9 pio 512 in

Dec 19 13:51:07 Tower kernel: ata17.00: status: { DRDY }

Dec 19 13:51:07 Tower kernel: ata17: hard resetting link

Dec 19 13:51:08 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 13:51:08 Tower kernel: ata17.00: configured for UDMA/133

Dec 19 13:51:08 Tower kernel: ata17: EH complete

Dec 19 14:28:23 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 19 14:28:23 Tower kernel: ata17.00: failed command: IDENTIFY DEVICE

Dec 19 14:28:23 Tower kernel: ata17.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 7 pio 512 in

Dec 19 14:28:23 Tower kernel: ata17.00: status: { DRDY }

Dec 19 14:28:23 Tower kernel: ata17: hard resetting link

Dec 19 14:28:24 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 14:28:24 Tower kernel: ata17.00: configured for UDMA/133

Dec 19 14:28:24 Tower kernel: ata17: EH complete

Dec 19 14:59:22 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 19 14:59:22 Tower kernel: ata17.00: failed command: SMART

Dec 19 14:59:22 Tower kernel: ata17.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 2 pio 512 in

Dec 19 14:59:22 Tower kernel: ata17.00: status: { DRDY }

Dec 19 14:59:22 Tower kernel: ata17: hard resetting link

Dec 19 14:59:23 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 14:59:23 Tower kernel: ata17.00: configured for UDMA/133

Dec 19 14:59:23 Tower kernel: ata17: EH complete

Dec 19 15:51:44 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 19 15:51:44 Tower kernel: ata17.00: failed command: IDENTIFY DEVICE

Dec 19 15:51:44 Tower kernel: ata17.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in

Dec 19 15:51:44 Tower kernel: ata17.00: status: { DRDY }

Dec 19 15:51:44 Tower kernel: ata17: hard resetting link

Dec 19 15:51:45 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 15:51:50 Tower kernel: ata17.00: qc timeout (cmd 0xec)

Dec 19 15:51:50 Tower kernel: ata17.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Dec 19 15:51:50 Tower kernel: ata17.00: revalidation failed (errno=-5)

Dec 19 15:51:50 Tower kernel: ata17: hard resetting link

Dec 19 15:51:50 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 15:51:50 Tower kernel: ata17.00: configured for UDMA/133

Dec 19 15:51:50 Tower kernel: ata17: EH complete

Dec 19 17:33:22 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 19 17:33:22 Tower kernel: ata17.00: failed command: SMART

Dec 19 17:33:22 Tower kernel: ata17.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 2 pio 512 in

Dec 19 17:33:22 Tower kernel: ata17.00: status: { DRDY }

Dec 19 17:33:22 Tower kernel: ata17: hard resetting link

Dec 19 17:33:23 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 17:33:23 Tower kernel: ata17.00: configured for UDMA/133

Dec 19 17:33:23 Tower kernel: ata17: EH complete

Dec 19 18:22:57 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 19 18:22:57 Tower kernel: ata17.00: failed command: IDENTIFY DEVICE

Dec 19 18:22:57 Tower kernel: ata17.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 3 pio 512 in

Dec 19 18:22:57 Tower kernel: ata17.00: status: { DRDY }

Dec 19 18:22:57 Tower kernel: ata17: hard resetting link

Dec 19 18:22:58 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 18:23:03 Tower kernel: ata17.00: qc timeout (cmd 0xec)

Dec 19 18:23:03 Tower kernel: ata17.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Dec 19 18:23:03 Tower kernel: ata17.00: revalidation failed (errno=-5)

Dec 19 18:23:03 Tower kernel: ata17: hard resetting link

Dec 19 18:23:03 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 18:23:03 Tower kernel: ata17.00: configured for UDMA/133

Dec 19 18:23:03 Tower kernel: ata17: EH complete

Dec 19 19:23:31 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 19 19:23:31 Tower kernel: ata17.00: failed command: IDENTIFY DEVICE

Dec 19 19:23:31 Tower kernel: ata17.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 21 pio 512 in

Dec 19 19:23:31 Tower kernel: ata17.00: status: { DRDY }

Dec 19 19:23:31 Tower kernel: ata17: hard resetting link

Dec 19 19:23:32 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 19:23:32 Tower kernel: ata17.00: configured for UDMA/133

Dec 19 19:23:32 Tower kernel: ata17: EH complete

Dec 19 21:24:34 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 19 21:24:34 Tower kernel: ata17.00: failed command: IDENTIFY DEVICE

Dec 19 21:24:34 Tower kernel: ata17.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 29 pio 512 in

Dec 19 21:24:34 Tower kernel: ata17.00: status: { DRDY }

Dec 19 21:24:34 Tower kernel: ata17: hard resetting link

Dec 19 21:24:35 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 21:24:40 Tower kernel: ata17.00: qc timeout (cmd 0xec)

Dec 19 21:24:40 Tower kernel: ata17.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Dec 19 21:24:40 Tower kernel: ata17.00: revalidation failed (errno=-5)

Dec 19 21:24:40 Tower kernel: ata17: hard resetting link

Dec 19 21:24:40 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 19 21:24:50 Tower kernel: ata17.00: qc timeout (cmd 0xec)

Dec 19 21:24:50 Tower kernel: ata17.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Dec 19 21:24:50 Tower kernel: ata17.00: revalidation failed (errno=-5)

Dec 19 21:24:50 Tower kernel: ata17: limiting SATA link speed to 1.5 Gbps

Dec 19 21:24:50 Tower kernel: ata17.00: limiting speed to UDMA/133:PIO3

Dec 19 21:24:50 Tower kernel: ata17: hard resetting link

Dec 19 21:24:51 Tower kernel: ata17: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 19 21:25:21 Tower kernel: ata17.00: qc timeout (cmd 0xec)

Dec 19 21:25:21 Tower kernel: ata17.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Dec 19 21:25:21 Tower kernel: ata17.00: revalidation failed (errno=-5)

Dec 19 21:25:21 Tower kernel: ata17.00: disabled

Dec 19 21:25:21 Tower kernel: ata17: hard resetting link

Dec 19 21:25:21 Tower kernel: ata17: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 19 21:25:21 Tower kernel: ata17: EH complete

Dec 19 21:25:21 Tower kernel: sd 16:0:0:0: [sdj] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00

Dec 19 21:25:21 Tower kernel: sd 16:0:0:0: [sdj] Sense not available.

Dec 19 21:25:21 Tower kernel: sd 16:0:0:0: [sdj] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00

Dec 19 21:25:21 Tower kernel: sd 16:0:0:0: [sdj] Sense not available.

Dec 19 21:25:21 Tower kernel: sdj: detected capacity change from 500106780160 to 0

Quote

December 20, 201510 yr

Author

I just stopped the array, powered down and replaced it with another identical spare drive I had. Assigned it to the array and am rebuilding contents onto it now. I didn't want to take any chances with the disabled disk so all is good but if anyone has any insight into those logs they can share I'd like to know what happened! Thanks!

Quote

December 21, 201510 yr

It might be a bad SATA cable. See how the controller keeps resetting the link and after several attempts at communicating at 3 Gb/s it tries at 1.5 Gb/s a couple of times before giving up. I guess it could equally well be a bad controller port or bad drive electronics (damaged by static, perhaps?) but simply reseating the cable (as you did when you replaced the drive) might well have fixed it. I've come to the conclusion that SATA connectors are not the best designed in the world and the general stiffness of the standard red cables doesn't help.

Quote

December 21, 201510 yr

Author

Thanks... I interpreted the logs the same way. However when I went to replace the disk, both the SATA and power cables were still securely connected. I did not replace any cables when I put in the replacement disk nor did I move the SATA to a different controller port and unRAID successfully re-built the data onto that new disk so I doubt it was the cable.

I'll be putting the old disk in my PC soon to check and see if it really went bad... after all it is 6 years old so its days were probably numbered but I was keeping a close eye on it lately given its age and the SMART reports have been nothing but consistent showing a perfectly healthy disk. Weird.

Thanks for your help.

Quote

December 21, 201510 yr

It happened the same to me lately with a Seagate Drive (2 years) and a WD drive (4 years old).

My server underwent some major changes but I never had so many strange problems all at once.

I reaseated drive cables and everything and the drives went back to normal but I don't feel too confident about my hardware configuration at the moment.

Quote

Disk error - why is my syslog telling me?

Featured Replies

Archived

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)