March 17, 20242 yr Hi im in the process of upgrading the server. New 16 port SATA controller, all new cables, external enclosure etc. I’ve got errors on 3 drives (out of 16) that occurs whenever I try and run a read check or parity sync as below. The common demoniator is that these 3 disks are the only WD Ultrastar HE10 disks in the array, the rest are all Seagate Barracuda drives and don’t appear to be giving me any issue. This only seems to occur when putting the array under a lot of stress (checks etc), otherwise it all runs without error. Mar 17 21:57:34 UNRAID kernel: ata38: limiting SATA link speed to 3.0 Gbps Mar 17 21:57:34 UNRAID kernel: ata38.00: exception Emask 0x0 SAct 0x7f0000 SErr 0x0 action 0x6 frozen Mar 17 21:57:34 UNRAID kernel: ata38.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata38.00: cmd 60/40:80:c0:7f:13/05:00:00:00:00/40 tag 16 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata38.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata38.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata38.00: cmd 60/40:88:00:85:13/05:00:00:00:00/40 tag 17 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata38.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata38.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata38.00: cmd 60/40:90:40:8a:13/05:00:00:00:00/40 tag 18 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata38.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata38.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata38.00: cmd 60/80:98:80:8f:13/00:00:00:00:00/40 tag 19 ncq dma 65536 in Mar 17 21:57:34 UNRAID kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata38.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata38.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata38.00: cmd 60/40:a0:00:90:13/05:00:00:00:00/40 tag 20 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata38.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata38.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata38.00: cmd 60/40:a8:40:95:13/05:00:00:00:00/40 tag 21 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata38.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata38.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata38.00: cmd 60/40:b0:80:9a:13/05:00:00:00:00/40 tag 22 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata38.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata38: hard resetting link Mar 17 21:57:34 UNRAID kernel: ata35.00: exception Emask 0x0 SAct 0x7f000000 SErr 0x0 action 0x6 frozen Mar 17 21:57:34 UNRAID kernel: ata35.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata35.00: cmd 60/40:c0:c0:7f:13/05:00:00:00:00/40 tag 24 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata35.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata35.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata35.00: cmd 60/40:c8:00:85:13/05:00:00:00:00/40 tag 25 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata35.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata35.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata35.00: cmd 60/40:d0:40:8a:13/05:00:00:00:00/40 tag 26 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata35.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata35.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata35.00: cmd 60/80:d8:80:8f:13/00:00:00:00:00/40 tag 27 ncq dma 65536 in Mar 17 21:57:34 UNRAID kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata35.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata35.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata35.00: cmd 60/40:e0:00:90:13/05:00:00:00:00/40 tag 28 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata35.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata35.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata35.00: cmd 60/40:e8:40:95:13/05:00:00:00:00/40 tag 29 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata35.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata35.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata35.00: cmd 60/40:f0:80:9a:13/05:00:00:00:00/40 tag 30 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 17 21:57:34 UNRAID kernel: ata35.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata35: hard resetting link Mar 17 21:57:34 UNRAID kernel: ata36.00: exception Emask 0x10 SAct 0xfc000 SErr 0x0 action 0x6 frozen Mar 17 21:57:34 UNRAID kernel: ata36.00: irq_stat 0x08800000, interface fatal error Mar 17 21:57:34 UNRAID kernel: ata36.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata36.00: cmd 60/40:70:00:85:13/05:00:00:00:00/40 tag 14 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:00:80:9a:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Mar 17 21:57:34 UNRAID kernel: ata36.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata36.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata36.00: cmd 60/40:78:40:8a:13/05:00:00:00:00/40 tag 15 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:00:80:9a:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Mar 17 21:57:34 UNRAID kernel: ata36.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata36.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata36.00: cmd 60/80:80:80:8f:13/00:00:00:00:00/40 tag 16 ncq dma 65536 in Mar 17 21:57:34 UNRAID kernel: res 40/00:00:80:9a:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Mar 17 21:57:34 UNRAID kernel: ata36.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata36.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata36.00: cmd 60/40:88:00:90:13/05:00:00:00:00/40 tag 17 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:00:80:9a:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Mar 17 21:57:34 UNRAID kernel: ata36.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata36.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata36.00: cmd 60/40:90:40:95:13/05:00:00:00:00/40 tag 18 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:00:80:9a:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Mar 17 21:57:34 UNRAID kernel: ata36.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata36.00: failed command: READ FPDMA QUEUED Mar 17 21:57:34 UNRAID kernel: ata36.00: cmd 60/40:98:80:9a:13/05:00:00:00:00/40 tag 19 ncq dma 688128 in Mar 17 21:57:34 UNRAID kernel: res 40/00:00:80:9a:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Mar 17 21:57:34 UNRAID kernel: ata36.00: status: { DRDY } Mar 17 21:57:34 UNRAID kernel: ata36: hard resetting link I’ve tried replacing cables, no difference, if I move the disks around the error follows, the common link is the disk model? Any suggestions please? SATA controller is this one https://amzn.to/3TFlzb9 Thanks
March 17, 20242 yr Run this command: Quote lsscsi -sigN Then run this command on your specific disks to get the full firmware version: Quote hdparm -I /dev/sdk |grep Firmware I have 4 of the He10, one failed a few months ago after 4 years of usage. Quote lsscsi -sigN |grep 1010 [36:0:3:0] disk ATA HGST HUH721010AL T384 /dev/sdk - /dev/sg11 10.0TB [36:0:5:0] disk ATA HGST HUH721010AL T384 /dev/sdm - /dev/sg13 10.0TB [36:0:7:0] disk ATA HGST HUH721010AL T384 /dev/sdo - /dev/sg15 10.0TB [36:0:8:0] disk ATA HGST HUH721010AL T384 /dev/sdp - /dev/sg16 10.0TB Mine are all on firmware 'LHGNT384': Quote hdparm -I /dev/sdk |grep Firmware Firmware Revision: LHGNT384 Are yours on this firmware also? Also, are there any jumpers on the drive? It's odd the drives downgrade to SATA2 (3gbps) instead of SATA3 (6gbps). What happens when you connect only the He10 on the same controller?
March 18, 20242 yr Author Cheers. one (6TB) is on APGNT7J0 and the other two (10TB) are on LHACW38Q ill have to look at the disks tomorrow for any jumpers. i can try to move all the other disks onto another controller and leave these 3 as is to see if that makes any difference, and vice versa I guess.
March 18, 20242 yr Run the commands so we can see the exact models you have. Here's a good thread for flashing hdd firmwares: https://forums.servethehome.com/index.php?threads/updating-the-hgst-hdd-ssd-firmware.22381/page-9 Here's a link to Hitachi firmwares: https://files.hddguru.com/download/Software/
March 18, 20242 yr Community Expert You can also try swapping those disks to a different controller and re-test.
March 18, 20242 yr Author @shpitz461 - results below - I was on the iPad last night so wasn't easy to copy/paste it all lsscsi -sigN [0:0:0:0] disk SanDisk' Cruzer Fit 1.00 /dev/sda SanDisk__Cruzer_Fit_4C530000240609101454-0:0 /dev/sg0 15.3GB [1:0:0:0] disk ATA CT480BX500SSD1 052 /dev/sdb - /dev/sg1 480GB [2:0:0:0] disk ATA SPCC Solid State 61.3 /dev/sdc - /dev/sg2 128GB [3:0:0:0] disk ATA CT240BX500SSD1 R013 /dev/sdd - /dev/sg3 240GB [9:0:0:0] disk ATA ST6000DM003-2CY1 0001 /dev/sde - /dev/sg4 6.00TB [10:0:0:0] disk ATA ST6000DM003-2CY1 0001 /dev/sdf - /dev/sg5 6.00TB [11:0:0:0] disk ATA ST6000DM003-2CY1 0001 /dev/sdg - /dev/sg6 6.00TB [27:0:0:0] disk ATA ST6000DM003-2CY1 0001 /dev/sdh - /dev/sg7 6.00TB [28:0:0:0] disk ATA ST6000DM003-2CY1 0001 /dev/sdi - /dev/sg8 6.00TB [30:0:0:0] disk ATA ST6000DM003-2CY1 0001 /dev/sdj - /dev/sg9 6.00TB [31:0:0:0] disk ATA ST6000DM003-2CY1 0001 /dev/sdk - /dev/sg10 6.00TB [32:0:0:0] disk ATA ST6000DM003-2CY1 0001 /dev/sdl - /dev/sg11 6.00TB [33:0:0:0] disk ATA ST6000DM003-2CY1 0001 /dev/sdm - /dev/sg12 6.00TB [34:0:0:0] disk ATA ST6000DM003-2ZD1 0002 /dev/sdn - /dev/sg13 6.00TB [35:0:0:0] disk ATA HGST HUS726060AL T7J0 /dev/sdo - /dev/sg14 6.00TB [36:0:0:0] disk ATA HGST HUH721010AL W38Q /dev/sdp - /dev/sg15 10.0TB [38:0:0:0] disk ATA HGST HUH721010AL W38Q /dev/sdq - /dev/sg16 10.0TB root@UNRAID:~# hdparm -I /dev/sdo |grep Firmware Firmware Revision: APGNT7J0 root@UNRAID:~# hdparm -I /dev/sdp |grep Firmware Firmware Revision: LHACW38Q root@UNRAID:~# hdparm -I /dev/sdq |grep Firmware Firmware Revision: LHACW38Q
March 18, 20242 yr Author 7 minutes ago, JorgeB said: You can also try swapping those disks to a different controller and re-test. I will try this at some point today.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.