Hard drive spinning up every minute

[stephan_str]

Hey guys,

I hope, I will find some help here. I couldn't find any information for exactly this problem online.

My parity drive is spinning up ~ every minute. I can hear it.

This is the disk log. You can see, its reconfigured every minute, but theres no link hard reset or something similar (found similar problems, that had all link resets).

Sep 3 15:06:35 Tower kernel: ata1: SATA max UDMA/133 abar m2048@0xf5132000 port 0xf5132100 irq 26
Sep 3 15:06:35 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 3 15:06:35 Tower kernel: ata1.00: ATA-10: WDC WD40EFAX-68JH4N0, WD-WX12D10E034Z, 82.00A82, max UDMA/133
Sep 3 15:06:35 Tower kernel: ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Sep 3 15:06:35 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 15:06:35 Tower kernel: sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Sep 3 15:06:35 Tower kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Sep 3 15:06:35 Tower kernel: sd 1:0:0:0: [sdb] Write Protect is off
Sep 3 15:06:35 Tower kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Sep 3 15:06:35 Tower kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 3 15:06:35 Tower kernel: sdb: sdb1
Sep 3 15:06:35 Tower kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Sep 3 15:06:57 Tower emhttpd: WDC_WD40EFAX-68JH4N0_WD-WX12D10E034Z (sdb) 512 7814037168
Sep 3 15:06:57 Tower kernel: mdcmd (1): import 0 sdb 64 3907018532 0 WDC_WD40EFAX-68JH4N0_WD-WX12D10E034Z
Sep 3 15:06:57 Tower kernel: md: import disk0: (sdb) WDC_WD40EFAX-68JH4N0_WD-WX12D10E034Z size: 3907018532
Sep 3 15:07:23 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 3 15:07:23 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 15:09:29 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 3 15:09:29 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 15:10:33 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 3 15:10:33 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 15:11:32 Tower kernel: ata1: limiting SATA link speed to 3.0 Gbps
Sep 3 15:11:36 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Sep 3 15:11:36 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 15:12:39 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Sep 3 15:12:39 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 15:36:19 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Sep 3 15:36:19 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 15:37:23 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Sep 3 15:37:23 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 15:38:26 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Sep 3 15:38:26 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 15:39:25 Tower kernel: ata1: limiting SATA link speed to 1.5 Gbps
Sep 3 15:39:29 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 15:39:29 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 15:40:33 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 15:40:33 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 15:41:36 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 15:41:36 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 15:42:40 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 15:42:40 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 17:51:46 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 17:51:46 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 17:53:58 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 17:53:58 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 17:55:01 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 17:55:01 Tower kernel: ata1.00: configured for UDMA/133
Sep 3 17:56:00 Tower kernel: ata1.00: limiting speed to UDMA/100:PIO4
Sep 3 17:56:05 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 17:56:05 Tower kernel: ata1.00: configured for UDMA/100
Sep 3 17:57:08 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 17:57:08 Tower kernel: ata1.00: configured for UDMA/100
Sep 3 17:58:07 Tower kernel: ata1.00: limiting speed to UDMA/33:PIO4
Sep 3 17:58:11 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 17:58:11 Tower kernel: ata1.00: configured for UDMA/33
Sep 3 17:59:15 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 17:59:15 Tower kernel: ata1.00: configured for UDMA/33
Sep 3 18:00:18 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 18:00:18 Tower kernel: ata1.00: configured for UDMA/33
Sep 3 18:01:22 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 18:01:22 Tower kernel: ata1.00: configured for UDMA/33
Sep 3 18:02:25 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 18:02:25 Tower kernel: ata1.00: configured for UDMA/33
Sep 3 18:03:29 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 18:03:29 Tower kernel: ata1.00: configured for UDMA/33
Sep 3 18:04:32 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 18:04:32 Tower kernel: ata1.00: configured for UDMA/33
Sep 3 18:05:35 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 18:05:35 Tower kernel: ata1.00: configured for UDMA/33
Sep 3 18:06:39 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 18:06:39 Tower kernel: ata1.00: configured for UDMA/33
Sep 3 18:07:42 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 18:07:42 Tower kernel: ata1.00: configured for UDMA/33
Sep 3 18:08:46 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 18:08:46 Tower kernel: ata1.00: configured for UDMA/33
Sep 3 18:09:49 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 3 18:09:49 Tower kernel: ata1.00: configured for UDMA/33

What did I do already? So, I replaced the sata cable and changed the power supply cable.

 

Thanks in advance!

 

tower-diagnostics-20200903-1810.zip

[JorgeB]

Try swapping both cables with another disk (so that this disk starts using a different SATA port) and post new diags if it still happens.

 

FYI these disks as SMR, just in case you notice write performance isn't as good as expected.

[stephan_str]

1 minute ago, JorgeB said:

Try swapping both cables with another disk (so that this disk starts using a different SATA port) and post new diags if it still happens.

 

FYI these disks as SMR, just in case you notice write performance isn't as good as expected.

Yeah, I know these are SMR. It is not that big of a problem for me personally.

 

Does Unraid recognize the drive if its attached to another SATA port? 

[ChatNoir]

Unraid does not use the SATA port as a reference but the disk S/N. Will be just fine on that front.

[stephan_str]

Changed SATA port, it still happens with the same drive.

tower-diagnostics-20200903-1908.zip

[stephan_str]

Even after swapping power cables again, the problem is still present.

Has someone an idea what I can do?

[JorgeB]

If the problem follows the drive the drive itself is likely the issue.

[stephan_str]

I unplugged everything again and now the error does not occur anymore. I have no idea why. Used the same power cables, the same sata cables.

Thanks anyways!

[konman]

I had a similar issue when I saw "DMA/133" zip by as I watched a Dell booting up. I looked in the logs and saw that it was an occasional thing that corrected itself by the time the boot was complete. I freaked out and cloned the drive but I left the old one in so I could beat up on it a little.

 

I've been a Linux guy since Jessie and I was hoping Buster would take care of an ACPI issue that's been bugging me from the start. But that's another story.

 

I started playing with BIOS settings @ Raid / AHCI / ATA. I knocked the setting down to RAID / ATA and that whispered message turned into yelling. The messages were pretty much the same as the OP's. It got worse on subsequent boots so I toggled the setting back to AHCI and it settled down after a few more reboots.

 

Then original UDMA warning came back and I got the feeling that it was associated with cold booting. I swapped out the SATA cables and that seems to have done the trick. The data cable that I removed looked pretty beat up so you may want give that a try. Reseating them might help.

 

This is a small sample of what came pouring out while it was set for ATA.

 

Sep 10 01:00:09 localhost vmunix: [52183.926487] sd 0:0:0:0: [sda] tag#8 Sense Key : Illegal Request [current]
Sep 10 01:00:09 localhost vmunix: [52183.926490] sd 0:0:0:0: [sda] tag#8 Add. Sense: Unaligned write command
Sep 10 01:00:09 localhost vmunix: [52183.926493] sd 0:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 00 80 12 18 00 00 08 00
Sep 10 01:00:09 localhost vmunix: [52183.926495] blk_update_request: I/O error, dev sda, sector 8393240
Sep 10 01:00:09 localhost vmunix: [52183.926502] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 10 01:00:09 localhost vmunix: [52183.926505] sd 0:0:0:0: [sda] tag#9 Sense Key : Illegal Request [current]
Sep 10 01:00:09 localhost vmunix: [52183.926508] sd 0:0:0:0: [sda] tag#9 Add. Sense: Unaligned write command
Sep 10 01:00:09 localhost vmunix: [52183.926511] sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 00 80 12 20 00 00 08 00
Sep 10 01:00:09 localhost vmunix: [52183.926513] blk_update_request: I/O error, dev sda, sector 8393248
Sep 10 01:00:09 localhost vmunix: [52183.926520] sd 0:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 10 01:00:09 localhost vmunix: [52183.926523] sd 0:0:0:0: [sda] tag#10 Sense Key : Illegal Request [current]
Sep 10 01:00:09 localhost vmunix: [52183.926526] sd 0:0:0:0: [sda] tag#10 Add. Sense: Unaligned write command
Sep 10 01:00:09 localhost vmunix: [52183.926529] sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 00 80 12 28 00 00 08 00
Sep 10 01:00:09 localhost vmunix: [52183.926531] blk_update_request: I/O error, dev sda, sector 8393256
Sep 10 01:00:09 localhost vmunix: [52183.926589] ata1: EH complete
Sep 10 01:00:10 localhost vmunix: [52185.280029] ata1.00: exception Emask 0x50 SAct 0x8000 SErr 0x4090800 action 0xe frozen
Sep 10 01:00:10 localhost vmunix: [52185.280035] ata1.00: irq_stat 0x00400040, connection status changed
Sep 10 01:00:10 localhost vmunix: [52185.280039] ata1: SError: { HostInt PHYRdyChg 10B8B DevExch }
Sep 10 01:00:10 localhost vmunix: [52185.280043] ata1.00: failed command: READ FPDMA QUEUED
Sep 10 01:00:10 localhost vmunix: [52185.280050] ata1.00: cmd 60/08:78:70:df:c6/00:00:00:00:00/40 tag 15 ncq dma 4096 in
Sep 10 01:00:10 localhost vmunix: [52185.280050]          res 40/00:7c:70:df:c6/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
Sep 10 01:00:10 localhost vmunix: [52185.280054] ata1.00: status: { DRDY }
Sep 10 01:00:10 localhost vmunix: [52185.280058] ata1: hard resetting link
Sep 10 01:00:15 localhost vmunix: [52190.840054] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 10 01:00:15 localhost vmunix: [52190.841404] ata1.00: configured for UDMA/133
Sep 10 01:00:15 localhost vmunix: [52190.841420] ata1: EH complete

 

For the record ....

I also toggled the MEB-x and Intel Virtualization settings in the BiOS settings. I have 4 similar Dell Optiplexes and they all boot with same ACPI errors. I was hopeful that Buster had addressed that issue and it didn't so I started spit wadding. Totally unrelated, I know. But what I wanted to do was rearrange the IRQ's. With older BIOS there were certain peripherals that I didn't like sharing with each other but I haven't found the key to that hidden door yet. I'll probably s look into Dell's Management portal. (Too many managers.)

 

k