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

unraid crashed : "DMAR: DRHD: handling fault status reg 2"

sorg
in General Support

Featured Replies

Hello,

 

Last night, my unraid machine crashed during the parity check.
The last log messages are the following:
  

Oct 23 22:06:01 unraid kernel: ata5.00: failed to read SCR 1 (Emask=0x40)
Oct 23 22:06:01 unraid kernel: ata5.01: failed to read SCR 1 (Emask=0x40)
Oct 23 22:06:01 unraid kernel: ata5.02: failed to read SCR 1 (Emask=0x40)
Oct 23 22:06:01 unraid kernel: ata5.02: exception Emask 0x100 SAct 0x3e0 SErr 0x0 action 0x6 frozen
Oct 23 22:06:01 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:06:01 unraid kernel: ata5.02: cmd 60/40:28:c0:f4:4c/05:00:97:00:00/40 tag 5 ncq dma 688128 in
Oct 23 22:06:01 unraid kernel:         res 40/00:30:00:fa:4c/00:00:97:00:00/40 Emask 0x100 (unknown error)
Oct 23 22:06:01 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:06:01 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:06:01 unraid kernel: ata5.02: cmd 60/40:30:00:fa:4c/05:00:97:00:00/40 tag 6 ncq dma 688128 in
Oct 23 22:06:01 unraid kernel:         res 40/00:30:00:fa:4c/00:00:97:00:00/40 Emask 0x100 (unknown error)
Oct 23 22:06:01 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:06:01 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:06:01 unraid kernel: ata5.02: cmd 60/40:38:40:ff:4c/05:00:97:00:00/40 tag 7 ncq dma 688128 in
Oct 23 22:06:01 unraid kernel:         res 40/00:30:00:fa:4c/00:00:97:00:00/40 Emask 0x100 (unknown error)
Oct 23 22:06:01 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:06:01 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:06:01 unraid kernel: ata5.02: cmd 60/40:40:80:04:4d/05:00:97:00:00/40 tag 8 ncq dma 688128 in
Oct 23 22:06:01 unraid kernel:         res 40/00:30:00:fa:4c/00:00:97:00:00/40 Emask 0x100 (unknown error)
Oct 23 22:06:01 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:06:01 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:06:01 unraid kernel: ata5.02: cmd 60/c0:48:c0:09:4d/04:00:97:00:00/40 tag 9 ncq dma 622592 in
Oct 23 22:06:01 unraid kernel:         res 40/00:30:00:fa:4c/00:00:97:00:00/40 Emask 0x100 (unknown error)
Oct 23 22:06:01 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:06:02 unraid kernel: ata5.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 23 22:06:03 unraid kernel: ata5.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Oct 23 22:06:03 unraid kernel: ata5.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Oct 23 22:06:03 unraid kernel: ata5.02: hard resetting link
Oct 23 22:06:04 unraid kernel: ata5.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Oct 23 22:06:04 unraid kernel: ata5.00: configured for UDMA/133
Oct 23 22:06:04 unraid kernel: ata5.01: configured for UDMA/133
Oct 23 22:06:04 unraid kernel: ata5.02: configured for UDMA/133
Oct 23 22:06:04 unraid kernel: ata5: EH complete
Oct 23 22:07:20 unraid kernel: ata5.00: failed to read SCR 1 (Emask=0x40)
Oct 23 22:07:20 unraid kernel: ata5.01: failed to read SCR 1 (Emask=0x40)
Oct 23 22:07:20 unraid kernel: ata5.02: failed to read SCR 1 (Emask=0x40)
Oct 23 22:07:20 unraid kernel: ata5.02: exception Emask 0x100 SAct 0xe00 SErr 0x0 action 0x6 frozen
Oct 23 22:07:20 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:07:20 unraid kernel: ata5.02: cmd 60/40:48:80:9a:b3/05:00:97:00:00/40 tag 9 ncq dma 688128 in
Oct 23 22:07:20 unraid kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 23 22:07:20 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:07:20 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:07:20 unraid kernel: ata5.02: cmd 60/40:50:c0:9f:b3/05:00:97:00:00/40 tag 10 ncq dma 688128 in
Oct 23 22:07:20 unraid kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 23 22:07:20 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:07:20 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:07:20 unraid kernel: ata5.02: cmd 60/80:58:00:a5:b3/00:00:97:00:00/40 tag 11 ncq dma 65536 in
Oct 23 22:07:20 unraid kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 23 22:07:20 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:07:22 unraid kernel: ata5.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 23 22:07:22 unraid kernel: ata5.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Oct 23 22:07:22 unraid kernel: ata5.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Oct 23 22:07:22 unraid kernel: ata5.02: hard resetting link
Oct 23 22:07:23 unraid kernel: ata5.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Oct 23 22:07:23 unraid kernel: ata5.00: configured for UDMA/133
Oct 23 22:07:23 unraid kernel: ata5.01: configured for UDMA/133
Oct 23 22:07:23 unraid kernel: ata5.02: configured for UDMA/133
Oct 23 22:07:23 unraid kernel: ata5: EH complete
Oct 23 22:24:34 unraid kernel: ata5.00: failed to read SCR 1 (Emask=0x40)
Oct 23 22:24:34 unraid kernel: ata5.01: failed to read SCR 1 (Emask=0x40)
Oct 23 22:24:34 unraid kernel: ata5.02: failed to read SCR 1 (Emask=0x40)
Oct 23 22:24:34 unraid kernel: ata5.02: exception Emask 0x100 SAct 0x60000000 SErr 0x0 action 0x6 frozen
Oct 23 22:24:34 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:24:34 unraid kernel: ata5.02: cmd 60/40:e8:58:ad:9a/05:00:a1:00:00/40 tag 29 ncq dma 688128 in
Oct 23 22:24:34 unraid kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 23 22:24:34 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:24:34 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:24:34 unraid kernel: ata5.02: cmd 60/10:f0:98:b2:9a/00:00:a1:00:00/40 tag 30 ncq dma 8192 in
Oct 23 22:24:34 unraid kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 23 22:24:34 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:24:36 unraid kernel: ata5.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 23 22:24:36 unraid kernel: ata5.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Oct 23 22:24:37 unraid kernel: ata5.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Oct 23 22:24:37 unraid kernel: ata5.02: hard resetting link
Oct 23 22:24:37 unraid kernel: ata5.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Oct 23 22:24:37 unraid kernel: ata5.00: configured for UDMA/133
Oct 23 22:24:37 unraid kernel: ata5.01: configured for UDMA/133
Oct 23 22:24:37 unraid kernel: ata5.02: configured for UDMA/133
Oct 23 22:24:37 unraid kernel: ata5: EH complete
Oct 23 22:54:45 unraid kernel: ata5.00: failed to read SCR 1 (Emask=0x40)
Oct 23 22:54:45 unraid kernel: ata5.01: failed to read SCR 1 (Emask=0x40)
Oct 23 22:54:45 unraid kernel: ata5.02: failed to read SCR 1 (Emask=0x40)
Oct 23 22:54:45 unraid kernel: ata5.02: exception Emask 0x100 SAct 0xf80 SErr 0x0 action 0x6 frozen
Oct 23 22:54:45 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:54:45 unraid kernel: ata5.02: cmd 60/40:38:70:f2:0a/05:00:b3:00:00/40 tag 7 ncq dma 688128 in
Oct 23 22:54:45 unraid kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 23 22:54:45 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:54:45 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:54:45 unraid kernel: ata5.02: cmd 60/40:40:b0:f7:0a/05:00:b3:00:00/40 tag 8 ncq dma 688128 in
Oct 23 22:54:45 unraid kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 23 22:54:45 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:54:45 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:54:45 unraid kernel: ata5.02: cmd 60/40:48:f0:fc:0a/05:00:b3:00:00/40 tag 9 ncq dma 688128 in
Oct 23 22:54:45 unraid kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 23 22:54:45 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:54:45 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:54:45 unraid kernel: ata5.02: cmd 60/40:50:30:02:0b/05:00:b3:00:00/40 tag 10 ncq dma 688128 in
Oct 23 22:54:45 unraid kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 23 22:54:45 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:54:45 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED
Oct 23 22:54:45 unraid kernel: ata5.02: cmd 60/80:58:70:07:0b/00:00:b3:00:00/40 tag 11 ncq dma 65536 in
Oct 23 22:54:45 unraid kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 23 22:54:45 unraid kernel: ata5.02: status: { DRDY }
Oct 23 22:54:47 unraid kernel: ata5.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 23 22:54:47 unraid kernel: ata5.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Oct 23 22:54:48 unraid kernel: ata5.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Oct 23 22:54:48 unraid kernel: ata5.02: hard resetting link
Oct 23 22:54:48 unraid kernel: ata5.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Oct 23 22:54:48 unraid kernel: ata5.00: configured for UDMA/133
Oct 23 22:54:48 unraid kernel: ata5.01: configured for UDMA/133
Oct 23 22:54:48 unraid kernel: ata5.02: configured for UDMA/133
Oct 23 22:54:48 unraid kernel: ata5: EH complete
Oct 23 23:36:58 unraid kernel: DMAR: DRHD: handling fault status reg 2
Oct 23 23:36:58 unraid kernel: DMAR: [DMA Write NO_PASID] Request device [04:1a.0] fault addr 0x0 [fault reason 0x02] Present bit in context entry is clear

 

It looks like i have SATA issues (how can i check which controller/drives is ata5.xx ?)
Based on the last line, the PCI device 04:xx is my additional SATA controller 04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02).

I can't find any obvious description of what may cause this DMAR fault reg 2.

Any pointers ?

 


I have attached my diagnostics files.

 

unraid-diagnostics-20231024-0737.zip

  • Quote

    • Solved by JorgeB

    Go to solution
    • Community Expert
    • Solution

    Avoid controllers with SATA port multipliers, see here:

     

  • Quote
    • Author

    I use an ASM1062 card. How can i know if i have a port multiplier ?

  • Quote
    • Community Expert

    If there are more than two ports.

  • Quote
    • Author
    On 10/24/2023 at 1:54 PM, JorgeB said:

    If there are more than two ports.

    I have 4 ports. :(

  • Quote
    • Author

    Last night, i had another crash but with a different error in the log:

      

    Oct 26 02:45:48 unraid kernel: pcieport 0000:00:1c.3: AER: Uncorrected (Non-Fatal) error received: 0000:00:1c.3
Oct 26 02:45:48 unraid kernel: pcieport 0000:00:1c.3: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 26 02:45:48 unraid kernel: pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00200000/00010000
Oct 26 02:45:48 unraid kernel: pcieport 0000:00:1c.3:    [21] ACSViol                (First)
Oct 26 02:45:48 unraid kernel: ahci 0000:04:00.0: AER: can't recover (no error_detected callback)
Oct 26 02:45:48 unraid kernel: pcieport 0000:00:1c.3: AER: device recovery failed

     

    once again, this is about my SATA controller.
      

    root@unraid:/mnt/user/logs# lspci -k
[...]
00:1c.3 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #4 (rev f0)
        Subsystem: ASUSTeK Computer Inc. Device 8694
        Kernel driver in use: pcieport
[...]
04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
        Subsystem: ASMedia Technology Inc. ASM1062 Serial ATA Controller
        Kernel driver in use: ahci
        Kernel modules: ahci
[...]


    I guess i need to stop using this sata card urgently :(

  • Quote
    • Community Expert

    You should, though it may not be the only problem, it is a problem.

  • Quote
    • 2 weeks later...
    • Author

    I replaced my SATA card with a chinese clone of LSI2208 : no more errors, and parity check rate has increased from 80 to 240 Mb/s. 
    Super Happy ! Thanks :)

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