Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

SATA Drives Fail (burst of R&W errors)

DaBeek
in General Support

Featured Replies

When TWO parity drives are configured in the array, a parity drive fails with a catastrophe sequence in syslog during the mover operation. Sometimes a data drive simultaneously fails. This happens consistently after a few minutes into the mover operation.  This occurs as soon as I can preclear/rebuild/parity-sync the array and try again with my latest attempt at changes. (more than 1x/week)  Multiple different drives failed.  Due to the "yard-sale" of errors across drives and using cables from the same pedigree as two solid builds over 10 years each,  I believe I have good SATA cables. I tried 2 new power supplies, but my next configuration will be using all of the power supply outputs to minimize the number of devices on each output (I have little hope this fixes anything but I always blame power first and until I hear from the community or Unraid)

 

During the move operation, files are moved from the nVME cache to the hard drives. This includes writing to 3 drives "at once" when 2 parity drives are in operation.

 

From the online forums I read, other manufacturers who have the same syslog errors below required a BIOS fix.  ASRock does not support Linux drivers.  When I submitted this to their Customer Support, they tried to offer the latest Windows SATA drivers.

 

Additionally, I see walking (single) UDMA CRC error counts (1-2 per week?) across all of my drives, including one I took (6TB) from unassigned from my 10+ year full time NAS Unraid.  I have never seen UDMA CRC error count errors before this current rig I built.  I included a separate syslog for the UDMA CRC error count way below. It also starts with exeption...frozen but with different values.  I am keeping up with Unraid versions although I need 6.12.8.

 

HW config is below the syslog

 

The syslog below depicts when Parity 2 (ata4/sdd) gets removed with 660 errors.  Then the unassigned drive gets picked on too (ata3/sdc).

 

Note: the syslog below has been edited in two places with lines with <<< >>> to summarize multiple copy or error lines.

 

<begin syslog>

Mar  5 03:40:01 rotator24 root: mover: started

Mar  5 03:40:02 rotator24 root: file: /mnt/cache_nvme_990pro_4t_a/rpi/redpi2/website/cj/200_funtime_video/20231113_Mon_Ally_mp4lowres.mp4

Mar  5 03:40:02 rotator24 root: move_object: /mnt/cache_nvme_990pro_4t_a/rpi/redpi2/website/cj/200_funtime_video/20231113_Mon_Ally_mp4lowres.mp4 File exists

Mar  5 03:40:02 rotator24 root: file: /mnt/cache_nvme_990pro_4t_a/users/rpi_eraseme_20240304/redpi2/website/cj/200_funtime_video/20231113_Mon_Ally_mp4lowres.mp4

Mar  5 03:40:02 rotator24 root: file: /mnt/cache_nvme_990pro_4t_a/users/rpi_eraseme_20240304/redpi2/website/cj/200_funtime_video/20240208_Thu_GuestRoom_mp4lowres.mp4

<<< 2398 files moved >>

Mar  5 03:55:18 rotator24 root: file: /mnt/cache_nvme_990pro_4t_a/users/rpi_eraseme_20240304/redpi2/website/cj/200_funtime_video/20230616_Fri_Ally_mp4.mp4

Mar  5 03:55:43 rotator24 root: file: /mnt/cache_nvme_990pro_4t_a/users/rpi_eraseme_20240304/redpi2/website/cj/200_funtime_video/20230616_Fri_Ally_mp4lowres.mp4

Mar  5 03:56:17 rotator24 kernel: ata4.00: exception Emask 0x52 SAct 0x800f00 SErr 0xffffffff action 0xe frozen

Mar  5 03:56:17 rotator24 kernel: ata4: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }

Mar  5 03:56:17 rotator24 kernel: ata4.00: failed command: WRITE FPDMA QUEUED

Mar  5 03:56:17 rotator24 kernel: ata4.00: cmd 61/28:40:90:91:c6/00:00:20:02:00/40 tag 8 ncq dma 20480 out

Mar  5 03:56:17 rotator24 kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x56 (ATA bus error)

Mar  5 03:56:17 rotator24 kernel: ata4.00: status: { DRDY }

Mar  5 03:56:17 rotator24 kernel: ata4.00: failed command: WRITE FPDMA QUEUED

Mar  5 03:56:17 rotator24 kernel: ata4.00: cmd 61/08:48:b8:91:c6/00:00:20:02:00/40 tag 9 ncq dma 4096 out

Mar  5 03:56:17 rotator24 kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)

Mar  5 03:56:17 rotator24 kernel: ata4.00: status: { DRDY }

Mar  5 03:56:17 rotator24 kernel: ata4.00: failed command: WRITE FPDMA QUEUED

Mar  5 03:56:17 rotator24 kernel: ata4.00: cmd 61/08:50:c0:91:c6/00:00:20:02:00/40 tag 10 ncq dma 4096 out

Mar  5 03:56:17 rotator24 kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)

Mar  5 03:56:17 rotator24 kernel: ata4.00: status: { DRDY }

Mar  5 03:56:17 rotator24 kernel: ata4.00: failed command: WRITE FPDMA QUEUED

Mar  5 03:56:17 rotator24 kernel: ata4.00: cmd 61/10:58:c8:91:c6/00:00:20:02:00/40 tag 11 ncq dma 8192 out

Mar  5 03:56:17 rotator24 kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)

Mar  5 03:56:17 rotator24 kernel: ata4.00: status: { DRDY }

Mar  5 03:56:17 rotator24 kernel: ata4.00: failed command: READ FPDMA QUEUED

Mar  5 03:56:17 rotator24 kernel: ata4.00: cmd 60/00:b8:80:14:c6/01:00:92:00:00/40 tag 23 ncq dma 131072 in

Mar  5 03:56:17 rotator24 kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)

Mar  5 03:56:17 rotator24 kernel: ata4.00: status: { DRDY }

Mar  5 03:56:17 rotator24 kernel: ata4: hard resetting link

Mar  5 03:56:17 rotator24 kernel: ahci 0000:4d:00.0: AHCI controller unavailable!

Mar  5 03:56:21 rotator24 kernel: ata4: failed to resume link (SControl FFFFFFFF)

Mar  5 03:56:23 rotator24 kernel: ata4: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF)

Mar  5 03:56:29 rotator24 kernel: ata4: hard resetting link

Mar  5 03:56:29 rotator24 kernel: ahci 0000:4d:00.0: AHCI controller unavailable!

Mar  5 03:56:33 rotator24 kernel: ata4: failed to resume link (SControl FFFFFFFF)

Mar  5 03:56:36 rotator24 kernel: ata4: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF)

Mar  5 03:56:37 rotator24 kernel: ata4: limiting SATA link speed to <unknown>

Mar  5 03:56:42 rotator24 kernel: ata4: hard resetting link

Mar  5 03:56:42 rotator24 kernel: ahci 0000:4d:00.0: AHCI controller unavailable!

Mar  5 03:56:46 rotator24 kernel: ata4: failed to resume link (SControl FFFFFFFF)

Mar  5 03:56:49 rotator24 kernel: ata4: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF)

Mar  5 03:56:50 rotator24 kernel: ata4.00: disable device

Mar  5 03:56:50 rotator24 kernel: ahci 0000:4d:00.0: AHCI controller unavailable!

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=63s

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#8 Sense Key : 0x5 [current] 

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#8 ASC=0x21 ASCQ=0x4 

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#8 CDB: opcode=0x8a 8a 00 00 00 00 02 20 c6 91 90 00 00 00 28 00 00

Mar  5 03:56:50 rotator24 kernel: I/O error, dev sdd, sector 9139818896 op 0x1:(WRITE) flags 0x0 phys_seg 5 prio class 2

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139818832

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139818840

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139818848

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139818856

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139818864

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=63s

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#9 Sense Key : 0x5 [current] 

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#9 ASC=0x21 ASCQ=0x4 

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#9 CDB: opcode=0x8a 8a 00 00 00 00 02 20 c6 91 b8 00 00 00 08 00 00

Mar  5 03:56:50 rotator24 kernel: I/O error, dev sdd, sector 9139818936 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139818872

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=63s

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#10 Sense Key : 0x5 [current] 

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#10 ASC=0x21 ASCQ=0x4 

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#10 CDB: opcode=0x8a 8a 00 00 00 00 02 20 c6 91 c0 00 00 00 08 00 00

Mar  5 03:56:50 rotator24 kernel: I/O error, dev sdd, sector 9139818944 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139818880

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=63s

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#11 Sense Key : 0x5 [current] 

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#11 ASC=0x21 ASCQ=0x4 

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#11 CDB: opcode=0x8a 8a 00 00 00 00 02 20 c6 91 c8 00 00 00 10 00 00

Mar  5 03:56:50 rotator24 kernel: I/O error, dev sdd, sector 9139818952 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 2

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139818888

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139818896

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=63s

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#23 Sense Key : 0x5 [current] 

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#23 ASC=0x21 ASCQ=0x4 

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] tag#23 CDB: opcode=0x88 88 00 00 00 00 00 92 c6 14 80 00 00 01 00 00 00

Mar  5 03:56:50 rotator24 kernel: I/O error, dev sdd, sector 2462454912 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 2

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454848

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454856

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454864

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454872

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454880

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454888

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454896

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454904

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454912

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454920

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454928

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454936

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454944

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454952

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454960

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454968

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454976

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454984

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462454992

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455000

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455008

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455016

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455024

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455032

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455040

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455048

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455056

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455064

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455072

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455080

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455088

Mar  5 03:56:50 rotator24 kernel: md: disk29 read error, sector=2462455096

Mar  5 03:56:50 rotator24 kernel: ata4: EH complete

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: rejecting I/O to offline device

Mar  5 03:56:50 rotator24 kernel: ata4.00: detaching (SCSI 4:0:0:0)

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139819224

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139819232

<<< 519 write errors >>>

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139823576

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139823584

Mar  5 03:56:50 rotator24 kernel: md: disk29 write error, sector=9139823592

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] Synchronizing SCSI cache

Mar  5 03:56:50 rotator24 kernel: sd 4:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK

Mar  5 03:57:07 rotator24 kernel: ahci 0000:4d:00.0: AHCI controller unavailable!

Mar  5 03:57:10 rotator24 kernel: ata3: failed to resume link (SControl FFFFFFFF)

Mar  5 03:57:13 rotator24 kernel: ata3: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF)

Mar  5 03:57:14 rotator24 root: file: /mnt/cache_nvme_990pro_4t_a/users/rpi_eraseme_20240304/redpi2/website/cj/200_funtime_video/20230616_Fri_Knight_mp4.mp4

Mar  5 03:57:19 rotator24 kernel: ahci 0000:4d:00.0: AHCI controller unavailable!

Mar  5 03:57:23 rotator24 kernel: ata3: failed to resume link (SControl FFFFFFFF)

Mar  5 03:57:25 rotator24 kernel: ata3: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF)

Mar  5 03:57:26 rotator24 kernel: ata3: limiting SATA link speed to <unknown>

Mar  5 03:57:27 rotator24 root: file: /mnt/cache_nvme_990pro_4t_a/users/rpi_eraseme_20240304/redpi2/website/cj/200_funtime_video/20230616_Fri_Knight_mp4lowres.mp4

Mar  5 03:57:32 rotator24 kernel: ahci 0000:4d:00.0: AHCI controller unavailable!

Mar  5 03:57:34 rotator24 root: file: /mnt/cache_nvme_990pro_4t_a/users/rpi_eraseme_20240304/redpi2/website/cj/200_funtime_video/20230616_Fri_GuestRoom_mp4.mp4

Mar  5 03:57:36 rotator24 kernel: ata3: failed to resume link (SControl FFFFFFFF)

Mar  5 03:57:38 rotator24 kernel: ata3: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF)

Mar  5 03:57:39 rotator24 kernel: ata3.00: disable device

Mar  5 03:57:39 rotator24 kernel: ahci 0000:4d:00.0: AHCI controller unavailable!

Mar  5 03:57:39 rotator24 kernel: ata3.00: detaching (SCSI 3:0:0:0)

Mar  5 03:57:40 rotator24 kernel: sd 3:0:0:0: [sdc] Synchronizing SCSI cache

Mar  5 03:57:40 rotator24 kernel: sd 3:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK

Mar  5 03:57:55 rotator24 root: file: /mnt/cache_nvme_990pro_4t_a/users/rpi_eraseme_20240304/redpi2/website/cj/200_funtime_video/20230616_Fri_GuestRoom_mp4lowres.mp4

Mar  5 03:58:01 rotator24 sSMTP[7044]: Creating SSL connection to host

Mar  5 03:58:02 rotator24 sSMTP[7044]: SSL connection using TLS_AES_128_GCM_SHA256

Mar  5 03:58:04 rotator24 root: file: /mnt/cache_nvme_990pro_4t_a/users/rpi_eraseme_20240304/redpi2/website/cj/200_funtime_video/20230618_Sun_Ally_mp4.mp4

Mar  5 03:58:05 rotator24 sSMTP[7044]: Sent mail for m****@blahblahh.com (221 Service Closing transmission) uid=0 username=root outbytes=758

Mar  5 03:58:05 rotator24 sSMTP[7123]: Creating SSL connection to host

Mar  5 03:58:05 rotator24 sSMTP[7123]: SSL connection using TLS_AES_128_GCM_SHA256

Mar  5 03:58:07 rotator24 sSMTP[7123]: Sent mail for m****@*******.com (221 Service Closing transmission) uid=0 username=root outbytes=785

Mar  5 03:58:20 rotator24 root: file: /mnt/cache_nvme_990pro_4t_a/users/rpi_eraseme_20240304/redpi2/website/cj/200_funtime_video/20230618_Sun_Ally_mp4lowres.mp4

Mar  5 03:58:26 rotator24 root: file: /mnt/cache_nvme_990pro_4t_a/users/rpi_eraseme_20240304/redpi2/website/cj/200_funtime_video/20230619_Mon_Ally_mp4.mp4

<end of syslog>

 

From this point on, one of two parity drives is disabled and the array runs without error until the array is rebuilt with two parity drives.

 

HW CONFIG:.I was future-proofing, but this completely depresses me after the 10+ solid Unraid starter NAS I have:

MOTHERBOARD: X670E Taichi Carrara 2.08.AS01

CPU: AMD RyzenTM 9 7950X3D 16-Core

RAM: 96GB, 2x 48GB, G.SKILL Trident F5-6400J3239F48GX2-TZ5RS

Drives:

  • Parity: 22TB WD Red Pro NAS (new) [SATA3_A2] (ata1, sdb)
  • Parity 2: 22TB WD Red Pro NAS (new) [SATA3_A3] (ata4, sdd)
  • Disk 1: 22TB WD Red Pro NAS (new) [SATA3_1] (ata5, sde) {xfs}
  • Disk 2: 6TB WD (old, high hours) [SATA3_4] (ata7, sdg) {xfs}
  • Disk 3: 2TB WD (old, low hours) [SATA3_2] (ata6, sdf) {xfs}
  • Unassigned: 2TB WD (old, high hours) [SATA3_A4] (ata3, sdc)
  • Cache: 2x 4T Samsung 990 PRO w/ heatsink {btrfs RAID 1} 

 

UnRaid Version: 6.12.6

 

Seasonic Focus GX-850, 850W

  • SATA DC PORT 1: 22T - NC - 22T - 22T 
  • SATA DC PORT 2: 2T - 2T - 6T - LanLi All-in-one cooler controller
  • SATA DC PORT 3: Not used
  • SATA DC PORT 4: Not Used

 

Next rebuild will be more power divided maybe like this:

  • SATA DC PORT 1: NC - NC - NC - 22T 
  • SATA DC PORT 2: NC - NC - 6T - LanLi All-in-one cooler controller 
  • SATA DC PORT 3: Molex to 2-way SATA 2T - 2T
  • SATA DC PORT 4: 22T - 22T (disk 1 - parity)

 

Fail History:

2024_02_12 1458:

    Disk 2 (errors 1380)

    Parity 2 (errors 1718)

 

2024_02_17 0426:

    Parity disk (errors 377)

 

2024_02_23 0431:

    Disk 2 (errors 59404)

    Parity 2 (errors 281)

 

2024_02_28 0408 (2.02 BIOS):

     Parity disk (errors 460)

 

2024_03_05 0358 (2.06 Beta BIOS):

    Parity 2 (errors 660)  (THIS IS THE SYSLOG ABOVE)

 

UDMA CRC Error:

Mar  5 16:53:16 rotator24 kernel: ata6.00: exception Emask 0x11 SAct 0xb0000078 SErr 0x680100 action 0x6 frozen

Mar  5 16:53:16 rotator24 kernel: ata6.00: irq_stat 0x48000008, interface fatal error

Mar  5 16:53:16 rotator24 kernel: ata6: SError: { UnrecovData 10B8B BadCRC Handshk }

Mar  5 16:53:16 rotator24 kernel: ata6.00: failed command: READ FPDMA QUEUED

Mar  5 16:53:16 rotator24 kernel: ata6.00: cmd 60/38:18:c8:08:3a/05:00:e3:00:00/40 tag 3 ncq dma 684032 in

Mar  5 16:53:16 rotator24 kernel:         res 40/00:28:40:13:3a/00:00:e3:00:00/40 Emask 0x10 (ATA bus error)

Mar  5 16:53:16 rotator24 kernel: ata6.00: status: { DRDY }

Mar  5 16:53:16 rotator24 kernel: ata6.00: failed command: READ FPDMA QUEUED

Mar  5 16:53:16 rotator24 kernel: ata6.00: cmd 60/40:20:00:0e:3a/05:00:e3:00:00/40 tag 4 ncq dma 688128 in

Mar  5 16:53:16 rotator24 kernel:         res 40/00:28:40:13:3a/00:00:e3:00:00/40 Emask 0x10 (ATA bus error)

Mar  5 16:53:16 rotator24 kernel: ata6.00: status: { DRDY }

Mar  5 16:53:16 rotator24 kernel: ata6.00: failed command: READ FPDMA QUEUED

Mar  5 16:53:16 rotator24 kernel: ata6.00: cmd 60/40:28:40:13:3a/05:00:e3:00:00/40 tag 5 ncq dma 688128 in

Mar  5 16:53:16 rotator24 kernel:         res 40/00:28:40:13:3a/00:00:e3:00:00/40 Emask 0x10 (ATA bus error)

Mar  5 16:53:16 rotator24 kernel: ata6.00: status: { DRDY }

Mar  5 16:53:16 rotator24 kernel: ata6.00: failed command: READ FPDMA QUEUED

Mar  5 16:53:16 rotator24 kernel: ata6.00: cmd 60/40:30:80:18:3a/05:00:e3:00:00/40 tag 6 ncq dma 688128 in

Mar  5 16:53:16 rotator24 kernel:         res 40/00:28:40:13:3a/00:00:e3:00:00/40 Emask 0x10 (ATA bus error)

Mar  5 16:53:16 rotator24 kernel: ata6.00: status: { DRDY }

Mar  5 16:53:16 rotator24 kernel: ata6.00: failed command: READ FPDMA QUEUED

Mar  5 16:53:16 rotator24 kernel: ata6.00: cmd 60/40:e0:c0:fd:39/05:00:e3:00:00/40 tag 28 ncq dma 688128 in

Mar  5 16:53:16 rotator24 kernel:         res 40/00:28:40:13:3a/00:00:e3:00:00/40 Emask 0x10 (ATA bus error)

Mar  5 16:53:16 rotator24 kernel: ata6.00: status: { DRDY }

Mar  5 16:53:16 rotator24 kernel: ata6.00: failed command: READ FPDMA QUEUED

Mar  5 16:53:16 rotator24 kernel: ata6.00: cmd 60/40:e8:00:03:3a/05:00:e3:00:00/40 tag 29 ncq dma 688128 in

Mar  5 16:53:16 rotator24 kernel:         res 40/00:28:40:13:3a/00:00:e3:00:00/40 Emask 0x10 (ATA bus error)

Mar  5 16:53:16 rotator24 kernel: ata6.00: status: { DRDY }

Mar  5 16:53:16 rotator24 kernel: ata6.00: failed command: READ FPDMA QUEUED

Mar  5 16:53:16 rotator24 kernel: ata6.00: cmd 60/88:f8:40:08:3a/00:00:e3:00:00/40 tag 31 ncq dma 69632 in

Mar  5 16:53:16 rotator24 kernel:         res 40/00:28:40:13:3a/00:00:e3:00:00/40 Emask 0x10 (ATA bus error)

Mar  5 16:53:16 rotator24 kernel: ata6.00: status: { DRDY }

Mar  5 16:53:16 rotator24 kernel: ata6: hard resetting link

Mar  5 16:53:16 rotator24 kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Mar  5 16:53:16 rotator24 kernel: ata6.00: configured for UDMA/133

Mar  5 16:53:16 rotator24 kernel: ata6: EH complete

Mar  5 16:54:01 rotator24 sSMTP[27219]: Creating SSL connection to host

Mar  5 16:54:02 rotator24 sSMTP[27219]: SSL connection using TLS_AES_128_GCM_SHA256

Mar  5 16:54:04 rotator24 sSMTP[27219]: Sent mail for

Edited by mguydish

  • Quote
    • Author

    Stay tuned at least 3 days.    I went to bed after posting afraid you'd ask that.  I had mover logging enabled.  In addition to not being anonymized, The Diagnostic tool chokes repeatedly; it is sed'ing over 600k syslog lines (from the mover history), which eventually hangs the process/BUI.  I use a syslog server, but it seems like I need to rebuild and crash the system again with mover logging disabled, then post diagnostics.  Will do. 

     

  • Quote
    • 1 month later...
    • Community Expert 
    May  7 04:47:33 rotator24 kernel: ahci 0000:4c:00.0: AHCI controller unavailable!

     

    Controller problem.

  • Quote
    • 4 weeks later...
    • Author

    All 3 drives related to ASMedia ASM1061 chip are the harddrives that consistently fail.  The other 3 drives on the ASRock X670E Taichi Carrara chipset are fine. Thank you.  That was a great clue.

     

    Replaced motherboard. Same problem, and I'm back to the download hangs when attempting to collect Diagnostics. (The .zip processing seems to hang)

     

    Is there something in the unRAID kernel that can work better with the ASMedia ASM1061 chip?  At one point ASRock wanted me to "update the Windows driver", indicating to me there might be a workaround for their hardware.  unRAID would need to match the Windows driver update for whatever ASRock was trying to make me do otherwise.

     

    Or, do I need to NOT use those 3 ASMedia ASM1061 ports and waste a PCI slot with a SATA card?  Is there a good card that has proven itself for unRAID performance? 

  • Quote
    • Community Expert

    Asmedia controllers usually work fine, and they use the standard AHCI driver, so nothing to updated, but try for example JMB based controllers, in case they work better with your board, see here for the recommended models:

     

     

     

  • Quote

    • 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.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.