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

failed: READ DMA

foo_fighter
in General Support (V5 and Older)

Featured Replies

Could this be caused by a bad cable, or is it perhaps a bad sata channel on the MB?

I tried 3 drives on that slot and all give the same failed READ DMA symptoms. When I tried to preclear a drive, it was spewing failed DMA reads into the syslog and also dropping down to UDMA/33, umda2.

Moved the new drive to a different port and it's preclearing at 130MB/s to 150MB/s

 

BIOS and unraid does detect the correct drive parameters on the bad port though, so maybe it's just spotty or a bad connection.

 

root@Tower:/var/log# grep -i ata2.01 syslog

Sep 24 21:03:08 Tower kernel: ata2.01: ATA-8: ST32000542AS,            6XW1LFNB, CC35, max UDMA/133

Sep 24 21:03:08 Tower kernel: ata2.01: 3907029168 sectors, multi 16: LBA48 NCQ (depth 0/32)

Sep 24 21:03:08 Tower kernel: ata2.01: configured for UDMA/133

Sep 24 21:03:33 Tower kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6

Sep 24 21:03:33 Tower kernel: ata2.01: BMDMA stat 0x66

Sep 24 21:03:33 Tower kernel: ata2.01: failed command: READ DMA

Sep 24 21:03:33 Tower kernel: ata2.01: cmd c8/00:20:00:00:00/00:00:00:00:00/f0 tag 0 dma 16384 in

Sep 24 21:03:33 Tower kernel: ata2.01: status: { DRDY ERR }

Sep 24 21:03:33 Tower kernel: ata2.01: error: { ICRC ABRT }

Sep 24 21:03:33 Tower kernel: ata2.01: configured for UDMA/133

root@Tower:/var/log# grep -i ata1.01 syslog

Sep 24 21:03:08 Tower kernel: ata1.01: ATA-8: ST4000DM000-1F2168,            W3009RHV, CC52, max UDMA/133

Sep 24 21:03:08 Tower kernel: ata1.01: 7814037168 sectors, multi 16: LBA48 NCQ (depth 0/32)

Sep 24 21:03:08 Tower kernel: ata1.01: configured for UDMA/133

root@Tower:/var/log# grep -i ata1.00 syslog

Sep 24 21:03:08 Tower kernel: ata1.00: ATA-8: Hitachi HDS5C3020ALA632,      ML0220F30N84ED, ML6OA580, max UDMA/133

Sep 24 21:03:08 Tower kernel: ata1.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 0/32)

Sep 24 21:03:08 Tower kernel: ata1.00: configured for UDMA/133

root@Tower:/var/log# grep -i ata1.01 syslog

Sep 24 21:03:08 Tower kernel: ata1.01: ATA-8: ST4000DM000-1F2168,            W3009RHV, CC52, max UDMA/133

Sep 24 21:03:08 Tower kernel: ata1.01: 7814037168 sectors, multi 16: LBA48 NCQ (depth 0/32)

Sep 24 21:03:08 Tower kernel: ata1.01: configured for UDMA/133

root@Tower:/var/log# tail syslog

Sep 24 21:04:13 Tower ntpd[1040]: new interface(s) found: waking up resolver

Sep 24 21:04:21 Tower kernel: NTFS driver 2.1.30 [Flags: R/W MODULE].

Sep 24 21:04:54 Tower in.telnetd[4775]: connect from 192.168.0.100 (192.168.0.100)

Sep 24 21:04:56 Tower logger: s3_sleep: Disk activity detected. Reset all counters

Sep 24 21:04:56 Tower login[4776]: ROOT LOGIN  on '/dev/pts/0' from '192.168.0.100'

Sep 24 21:05:56 Tower logger: s3_sleep: Disk activity detected. Reset all counters

Sep 24 21:06:56 Tower logger: s3_sleep: Disk activity detected. Reset all counters

Sep 24 21:07:56 Tower logger: s3_sleep: Disk activity detected. Reset all counters

Sep 24 21:08:01 Tower login[4464]: ROOT LOGIN  on '/dev/tty1'

Sep 24 21:08:28 Tower kernel:  sdc: unknown partition table

 

  • Quote

    It could be the cable, or the sata channel or both.

     

    Maybe it's because of the bios settings. Be sure all the 'smart' stuff is disabled like RAID and JBOD. It's also better to have AHCI enabled.

  • Quote
    • Author

    I ordered a bunch of locking cables from monoprice so we'll see.

     

    It could also be the backplane(It's in an Icydock 5in3 enclosure, so if the cable swap doesn't work I'll swap locations in the cage)

     

    It's one of the 4 MB sata ports on an old Asus P5LD2-VM R2.0. It doesn't even have an AHCI setting. At least it wasn't the drive(s) I was trying to preclear. That's still going fine so far on the other port.

     

     

     

     

     

  • Quote
    • Author

    So the verdict is....Bad backplane channel. Swapped cables and it didn't work.

    Swapped locations in the 5in3 and it's working.

    It's really odd, since in all cases the drive was identified by bios but either had failed DMA read or wasn't even detected once Unraid boot. If it was a hardware issue, I would have thought it wouldn't even have been detected by BIOS.

  • Quote

    Don't put too much trust into BIOS detection of your hard drives. I have a malfunctioning sata port on the motherboard which gets detected by both BIOS and Unraid.

     

    Good you were able to isolate the origin of the issue.

  • Quote
    • Author

    Actually spoke too soon!

     

    It went through the read stage of preclear fine ~130-150MB/s but when it got to the write stage it went crazy. It's bizarre. I guess it's back to being a bad sata channel on the MB:

     

    Sep 30 04:40:01 Tower syslogd 1.4.1: restart.

    Sep 30 04:40:02 Tower kernel: ata4.00: configured for UDMA/133

    Sep 30 04:40:02 Tower kernel: ata4.01: configured for UDMA/33

    Sep 30 04:40:02 Tower kernel: ata4: EH complete

    Sep 30 04:40:02 Tower kernel: ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6

    Sep 30 04:40:02 Tower kernel: ata4.01: BMDMA stat 0x66

    Sep 30 04:40:02 Tower kernel: ata4.01: failed command: WRITE DMA EXT

    Sep 30 04:40:02 Tower kernel: ata4.01: cmd 35/00:00:00:68:6b/00:04:00:00:00/f0 tag 0 dma 524288 out

    Sep 30 04:40:02 Tower kernel:          res 51/84:d1:2f:68:6b/84:03:00:00:00/f0 Emask 0x30 (host bus error)

    Sep 30 04:40:02 Tower kernel: ata4.01: status: { DRDY ERR }

    Sep 30 04:40:02 Tower kernel: ata4.01: error: { ICRC ABRT }

    Sep 30 04:40:02 Tower kernel: ata4: soft resetting link

    Sep 30 04:40:02 Tower kernel: ata4.00: configured for UDMA/133

    Sep 30 04:40:02 Tower kernel: ata4.01: configured for UDMA/33

    Sep 30 04:40:02 Tower kernel: ata4: EH complete

    Sep 30 04:40:02 Tower kernel: ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6

    Sep 30 04:40:02 Tower kernel: ata4.01: BMDMA stat 0x66

    Sep 30 04:40:02 Tower kernel: ata4.01: failed command: WRITE DMA EXT

    Sep 30 04:40:02 Tower kernel: ata4.01: cmd 35/00:00:00:68:6b/00:04:00:00:00/f0 tag 0 dma 524288 out

    Sep 30 04:40:02 Tower kernel:          res 51/84:e1:1f:68:6b/84:03:00:00:00/f0 Emask 0x30 (host bus error)

    Sep 30 04:40:02 Tower kernel: ata4.01: status: { DRDY ERR }

    Sep 30 04:40:02 Tower kernel: ata4.01: error: { ICRC ABRT }

    Sep 30 04:40:02 Tower kernel: ata4: soft resetting link

    Sep 30 04:40:02 Tower kernel: ata4.00: configured for UDMA/133

    Sep 30 04:40:02 Tower kernel: ata4.01: configured for UDMA/33

    Sep 30 04:40:02 Tower kernel: ata4: EH complete

    Sep 30 04:40:02 Tower kernel: ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6

    Sep 30 04:40:02 Tower kernel: ata4.01: BMDMA stat 0x66

    Sep 30 04:40:02 Tower kernel: ata4.01: failed command: WRITE DMA EXT

    Sep 30 04:40:02 Tower kernel: ata4.01: cmd 35/00:00:00:68:6b/00:04:00:00:00/f0 tag 0 dma 524288 out

    Sep 30 04:40:02 Tower kernel:          res 51/84:e1:1f:68:6b/84:03:00:00:00/f0 Emask 0x30 (host bus error)

    Sep 30 04:40:02 Tower kernel: ata4.01: status: { DRDY ERR }

    Sep 30 04:40:02 Tower kernel: ata4.01: error: { ICRC ABRT }

    Sep 30 04:40:02 Tower kernel: ata4: soft resetting link

    Sep 30 04:40:02 Tower kernel: ata4.00: configured for UDMA/133

    Sep 30 04:40:03 Tower kernel: ata4.01: configured for UDMA/33

    Sep 30 04:40:03 Tower kernel: sd 4:0:1:0: [sde]

    Sep 30 04:40:03 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08

    Sep 30 04:40:03 Tower kernel: sd 4:0:1:0: [sde]

    Sep 30 04:40:03 Tower kernel: Sense Key : 0xb [current] [descriptor]

    Sep 30 04:40:03 Tower kernel: Descriptor sense data with sense descriptors (in hex):

    Sep 30 04:40:03 Tower kernel:        72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00

    Sep 30 04:40:03 Tower kernel:        00 6b 68 1f

    Sep 30 04:40:03 Tower kernel: sd 4:0:1:0: [sde]

    Sep 30 04:40:03 Tower kernel: ASC=0x47 ASCQ=0x0

    Sep 30 04:40:03 Tower kernel: sd 4:0:1:0: [sde] CDB:

    Sep 30 04:40:03 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 00 6b 68 00 00 00 04 00 00 00

    Sep 30 04:40:03 Tower kernel: end_request: I/O error, dev sde, sector 7038976

    Sep 30 04:40:03 Tower kernel: quiet_error: 374 callbacks suppressed

    Sep 30 04:40:03 Tower kernel: Buffer I/O error on device sde, logical block 879872

    Sep 30 04:40:03 Tower kernel: lost page write due to I/O error on sde

    Sep 30 04:40:03 Tower kernel: Buffer I/O error on device sde, logical block 879873

    Sep 30 04:40:03 Tower kernel: lost page write due to I/O error on sde

    Sep 30 04:40:03 Tower kernel: Buffer I/O error on device sde, logical block 879874

    Sep 30 04:40:03 Tower kernel: lost page write due to I/O error on sde

    Sep 30 04:40:03 Tower kernel: Buffer I/O error on device sde, logical block 879875

    Sep 30 04:40:03 Tower kernel: lost page write due to I/O error on sde

    Sep 30 04:40:03 Tower kernel: Buffer I/O error on device sde, logical block 879876

    Sep 30 04:40:03 Tower kernel: lost page write due to I/O error on sde

     

  • Quote

    ICRC Abort errors are those where the checksum on the communications to/from the drive are incorrect.

     

    This is MOSTLY caused either by a poorly shielded SATA cable being used, or them being bundled closely with other cables.

    Tie-wrapping the cables to make them look neat and parallel is the WORST thing you can do, unless the cables are shielded they should have some distance between them.

     

    Are your SATA cables neatly bundled to each other..  (or even worse, bundled with power cables) ??

     

  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    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.