v6.9.2: Hard Freezes on new AMD B450 200GE system

[dominicm]

I have a new system running on temporary hardware while I migrate data from ext4 drives one by one and add them into the array. I am having hard freezes occasionally, so far approx once a day. No console access, blank monitor. keyboard num lock doesn't work so its completely frozen. Sometimes after and hour sometimes after a day or so. I have all VMs and dockers diabled except krusader to copy data. Only mouse, keyboard, monitor, boot usb connected nothing else, using integrated sata ports.

 

I do not see C6 states option in bios but did change power current option which did not fix an issue as system crashed last night again. Very little in the logs, here is the section before crash.

 

Anyone have any clue what is causing this or what I can try?

 

May  1 22:50:46 Unraid emhttpd: Starting services...
May  1 22:50:46 Unraid emhttpd: shcmd (1079): /etc/rc.d/rc.samba restart
May  1 22:50:46 Unraid nmbd[29502]: [2021/05/01 22:50:46.985123,  0] ../../source3/nmbd/nmbd.c:59(terminate)
May  1 22:50:46 Unraid nmbd[29502]:   Got SIGTERM: going down...
May  1 22:50:46 Unraid winbindd[29514]: [2021/05/01 22:50:46.986500,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
May  1 22:50:46 Unraid winbindd[29514]:   Got sig[15] terminate (is_parent=0)
May  1 22:50:46 Unraid winbindd[29512]: [2021/05/01 22:50:46.987365,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
May  1 22:50:46 Unraid winbindd[29512]:   Got sig[15] terminate (is_parent=1)
May  1 22:50:49 Unraid root: Starting Samba:  /usr/sbin/smbd -D
May  1 22:50:49 Unraid root:                  /usr/sbin/nmbd -D
May  1 22:50:49 Unraid smbd[30174]: [2021/05/01 22:50:49.182566,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
May  1 22:50:49 Unraid smbd[30174]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
May  1 22:50:49 Unraid root:                  /usr/sbin/wsdd
May  1 22:50:49 Unraid nmbd[30179]: [2021/05/01 22:50:49.191552,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
May  1 22:50:49 Unraid nmbd[30179]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
May  1 22:50:49 Unraid root:                  /usr/sbin/winbindd -D
May  1 22:50:49 Unraid winbindd[30189]: [2021/05/01 22:50:49.236433,  0] ../../source3/winbindd/winbindd_cache.c:3203(initialize_winbindd_cache)
May  1 22:50:49 Unraid winbindd[30189]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
May  1 22:50:49 Unraid winbindd[30189]: [2021/05/01 22:50:49.237512,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
May  1 22:50:49 Unraid winbindd[30189]:   daemon_ready: daemon 'winbindd' finished starting up and ready to serve connections
May  1 22:51:12 Unraid nmbd[30179]: [2021/05/01 22:51:12.223350,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
May  1 22:51:12 Unraid nmbd[30179]:   *****
May  1 22:51:12 Unraid nmbd[30179]:   
May  1 22:51:12 Unraid nmbd[30179]:   Samba name server UNRAID is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
May  1 22:51:12 Unraid nmbd[30179]:   
May  1 22:51:12 Unraid nmbd[30179]:   *****
May  1 22:51:12 Unraid nmbd[30179]: [2021/05/01 22:51:12.223520,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
May  1 22:51:12 Unraid nmbd[30179]:   *****
May  1 22:51:12 Unraid nmbd[30179]:   
May  1 22:51:12 Unraid nmbd[30179]:   Samba name server UNRAID is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1
May  1 22:51:12 Unraid nmbd[30179]:   
May  1 22:51:12 Unraid nmbd[30179]:   *****
May  2 03:40:16 Unraid crond[1696]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
May  2 06:40:13 Unraid kernel: ahci 0000:01:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0008 address=0x4073190000608040 flags=0x0030]
May  2 06:40:13 Unraid kernel: ahci 0000:01:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0008 address=0x4073190000608080 flags=0x0030]
May  2 06:40:13 Unraid kernel: ahci 0000:01:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0008 address=0x4073190000608024 flags=0x0030]
May  2 06:40:43 Unraid kernel: ata6.00: exception Emask 0x0 SAct 0x20008 SErr 0x0 action 0x6 frozen
May  2 06:40:43 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED
May  2 06:40:43 Unraid kernel: ata6.00: cmd 60/00:18:00:17:73/02:00:47:02:00/40 tag 3 ncq dma 262144 in
May  2 06:40:43 Unraid kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May  2 06:40:43 Unraid kernel: ata6.00: status: { DRDY }
May  2 06:40:43 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED
May  2 06:40:43 Unraid kernel: ata6.00: cmd 60/00:88:00:19:73/02:00:47:02:00/40 tag 17 ncq dma 262144 in
May  2 06:40:43 Unraid kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
May  2 06:40:43 Unraid kernel: ata6.00: status: { DRDY }
May  2 06:40:43 Unraid kernel: ata6: hard resetting link
May  2 06:40:44 Unraid kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May  2 06:40:44 Unraid kernel: ata6.00: configured for UDMA/133
May  2 06:40:44 Unraid kernel: sd 6:0:0:0: [sde] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=30s
May  2 06:40:44 Unraid kernel: sd 6:0:0:0: [sde] tag#3 Sense Key : 0x5 [current]
May  2 06:40:44 Unraid kernel: sd 6:0:0:0: [sde] tag#3 ASC=0x21 ASCQ=0x4
May  2 06:40:44 Unraid kernel: sd 6:0:0:0: [sde] tag#3 CDB: opcode=0x88 88 00 00 00 00 02 47 73 17 00 00 00 02 00 00 00
May  2 06:40:44 Unraid kernel: blk_update_request: I/O error, dev sde, sector 9788659456 op 0x0:(READ) flags 0x80700 phys_seg 37 prio class 0
May  2 06:40:44 Unraid kernel: sd 6:0:0:0: [sde] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=30s
May  2 06:40:44 Unraid kernel: sd 6:0:0:0: [sde] tag#17 Sense Key : 0x5 [current]
May  2 06:40:44 Unraid kernel: sd 6:0:0:0: [sde] tag#17 ASC=0x21 ASCQ=0x4
May  2 06:40:44 Unraid kernel: sd 6:0:0:0: [sde] tag#17 CDB: opcode=0x88 88 00 00 00 00 02 47 73 19 00 00 00 02 00 00 00
May  2 06:40:44 Unraid kernel: blk_update_request: I/O error, dev sde, sector 9788659968 op 0x0:(READ) flags 0x80700 phys_seg 64 prio class 0
May  2 06:40:44 Unraid kernel: ata6: EH complete
May  2 07:48:57 Unraid kernel: ahci 0000:01:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0008 address=0x40c80d0000608040 flags=0x0030]
May  2 07:48:57 Unraid kernel: ahci 0000:01:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0008 address=0x40c80d0000608024 flags=0x0030]
May  2 08:51:21 Unraid kernel: Linux version 5.10.28-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Wed Apr 7 08:23:18 PDT 2021
May  2 08:51:21 Unraid kernel: Command line: BOOT_IMAGE=/bzimage pcie_acs_override=downstream,multifunction initrd=/bzroot

 

 

The sata errors were not here in the last freeze log but AMD-Vi lines were there also just before the freeze. sde drive is the ext4 disk mounted as unassigned and crashes happened with previous 2 drives too so I doubt its ext4 disk related.

 

 

System information:
 

M/B: ASRock B450M-HDV R4.0 Version - s/n: xxxxxxxxxxxxxxxxx
BIOS: American Megatrends Inc. Version P4.50. Dated: 03/12/2021
CPU: AMD Athlon 200GE with Radeon Vega Graphics @ 3200 MHz
HVM: Enabled
IOMMU: Enabled
Cache: 192 KiB, 1 MB, 4 MB
Memory: 8 GiB DDR4 (max. installable capacity 128 GiB)
Network: bond0: fault-tolerance (active-backup), mtu 1500
 eth0: 1000 Mbps, full duplex, mtu 1500
Kernel: Linux 5.10.28-Unraid x86_64
OpenSSL: 1.1.1j

 

Edited May 2, 2021 by dominicm
minor

[JorgeB]

1 hour ago, dominicm said:

May 2 06:40:13 Unraid kernel: ahci 0000:01:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0008 address=0x4073190000608024 flags=0x0030]

This is a problem with the onboard SATA controller and quite common with some Ryzen boards, look for a BIOS update, if that doesn't help best be other then using different hardware is to use an add-on controller, but this doesn't explain the freezing.

[dominicm]

The bios is already latest, not really worried about non-critical errors for now. I don't get how else to troubleshoot this as the logs don't seem to have any relevant errors.