Hi there,

 

I'm currently using 4 HDDs. One of them is a shucked WD 14 TB drive. All of them go to sleep when unused, yet the 14TB one keeps waking up without Unraid realizing it - it neither shows the temperature nor turns the grey circle green.

 

This is what shows up in the log every time the drive wakes up (which is irregular - sometimes it stays asleep for multiple hours, sometimes it wakes up every 30 minutes):

 

Dec 12 19:03:20 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 12 19:03:20 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 12 19:03:25 Tower kernel: ata3.00: qc timeout (cmd 0x47)
Dec 12 19:03:25 Tower kernel: ata3.00: READ LOG DMA EXT failed, trying PIO
Dec 12 19:03:25 Tower kernel: ata3.00: failed to get NCQ Send/Recv Log Emask 0x40
Dec 12 19:03:25 Tower kernel: ata3.00: NCQ Send/Recv Log not supported
Dec 12 19:03:25 Tower kernel: ata3.00: ATA Identify Device Log not supported
Dec 12 19:03:25 Tower kernel: ata3.00: Security Log not supported
Dec 12 19:03:25 Tower kernel: ata3.00: failed to set xfermode (err_mask=0x40)
Dec 12 19:03:26 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 12 19:03:26 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 12 19:03:30 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 12 19:03:30 Tower kernel: ata3.00: configured for UDMA/133

To me this looks like the connection to the drive resets.

 

I already changed the SATA port and the SATA cable.

 

I've attached the diagnostics file. Maybe somebody can help me out here.

 

Cheers

tower-diagnostics-20201212-1923.zip

Yes, spinup due to link reset. Later will check the diagnostics.

 

Edit : Pls try disable NCQ

Edited December 12, 20205 yr by Vr2Io

I didn't find NCQ as a setting for the individual disk, so I went ahead and disabled it for all disks in the general disk settings. I'll get back to you after a reboot and spindown

 

EDIT:

 

This can't be a coincidence, can it? The system runs for two hours without the drive waking up. I open up the Web Interface, check the log and suddenly the drive spins up:

 

Dec 13 00:18:37 Tower webGUI: Successful login user root from 192.168.178.21
Dec 13 00:19:00 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 13 00:19:00 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 00:19:05 Tower kernel: ata3.00: qc timeout (cmd 0x2f)
Dec 13 00:19:05 Tower kernel: ata3.00: failed to get NCQ Send/Recv Log Emask 0x4
Dec 13 00:19:05 Tower kernel: ata3.00: NCQ Send/Recv Log not supported
Dec 13 00:19:05 Tower kernel: ata3.00: ATA Identify Device Log not supported
Dec 13 00:19:05 Tower kernel: ata3.00: Security Log not supported
Dec 13 00:19:05 Tower kernel: ata3.00: failed to set xfermode (err_mask=0x40)
Dec 13 00:19:06 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 13 00:19:06 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 00:19:10 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 00:19:10 Tower kernel: ata3.00: configured for UDMA/133

Did I somehow wake it up without even doing so?

Edited December 12, 20205 yr by Pillendreher

hdparm shows me this after the drive wakes up:

 

root@Tower:~# hdparm -C /dev/sdd

/dev/sdd:
 drive state is:  unknown

 

Edited December 13, 20205 yr by Pillendreher

Strange, all disk use onboard SATA port, could you try swap port.

4 hours ago, Vr2Io said:

Strange, all disk use onboard SATA port, could you try swap port.

Already done this as well. Issues happened on port 4, I switched to port 3.

 

I was away for a couple of hours and the resets keep happening:

 

Dec 13 14:36:00 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 13 14:36:00 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 14:36:05 Tower kernel: ata3.00: qc timeout (cmd 0x2f)
Dec 13 14:36:05 Tower kernel: ata3.00: failed to get NCQ Send/Recv Log Emask 0x4
Dec 13 14:36:05 Tower kernel: ata3.00: NCQ Send/Recv Log not supported
Dec 13 14:36:05 Tower kernel: ata3.00: ATA Identify Device Log not supported
Dec 13 14:36:05 Tower kernel: ata3.00: Security Log not supported
Dec 13 14:36:05 Tower kernel: ata3.00: failed to set xfermode (err_mask=0x40)
Dec 13 14:36:05 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 13 14:36:05 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 14:36:10 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 14:36:10 Tower kernel: ata3.00: configured for UDMA/133
Dec 13 15:18:40 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 13 15:18:40 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 15:18:40 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 15:18:40 Tower kernel: ata3.00: configured for UDMA/133
Dec 13 15:54:40 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 13 15:54:40 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 15:54:40 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 15:54:40 Tower kernel: ata3.00: configured for UDMA/133
Dec 13 16:25:50 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 13 16:25:50 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 16:25:50 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 16:25:50 Tower kernel: ata3.00: configured for UDMA/133
Dec 13 17:10:10 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 13 17:10:10 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 17:10:10 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 17:10:10 Tower kernel: ata3.00: configured for UDMA/133
Dec 13 18:53:00 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 13 18:53:00 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 18:53:00 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Dec 13 18:53:00 Tower kernel: ata3.00: configured for UDMA/133

 

hdparms shows me a different output now though:

 

root@Tower:~# hdparm -C /dev/sdd

/dev/sdd:
 drive state is:  active/idle

 

Edited December 13, 20205 yr by Pillendreher