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.

New to UNRAID Server keeps crashing

Featured Replies

Hi, I just installed Unraid to a NAS I built out of old components, for some reason the PC just becomes unresponsive after about 10-20 mins of usage, haven't really been able to finish setup yet. I tried a couple fixes I found online, but nothing is currently working.

Seemingly for no reason the online GUI will become unresponsive, as if the web page stopped loading. When checking with a monitor the output on the NAS, nothing is displaying and I'm unable to do anything other than a forced shuttdown by holding the power button for 4s.

 

Edit: added logs

 

syslogsyslogpizza-server-diagnostics-20231217-1217.zip

 

Edited by PizzaDude

  • Community Expert

The syslogs you attached all seem the same and are after reboot.

 

Setup syslog server.

 

Have you done memtest?

  • Author
Quote

Have you done memtest?


Yes, I left Memtest all night and it said PASSED.

 

Quote

The syslogs you attached all seem the same and are after reboot.

 

Setup syslog server.

 

I had already done that, but I'll check the config again.

 

I changed the syslog and it crashed right after, I'm not entirely sure if it worked, here are the files.

syslog syslog-previous pizza-server-diagnostics-20231217-1217.zip

  • Author

Update, created new USB for UNRAID install, same issues.

 

The error appear to be something related to DMAR Write NO_PASID

 

Quote

Dec 17 16:43:41 Pizza-Server root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped
Dec 17 16:43:41 Pizza-Server root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon:  /usr/sbin/avahi-dnsconfd -D
Dec 17 16:43:41 Pizza-Server avahi-dnsconfd[14033]: Successfully connected to Avahi daemon.
Dec 17 16:43:41 Pizza-Server emhttpd: shcmd (308): smbcontrol smbd close-share 'NAS_Storage'
Dec 17 16:43:42 Pizza-Server avahi-daemon[14022]: Server startup complete. Host name is Pizza-Server.local. Local service cookie is 2904258618.
Dec 17 16:43:43 Pizza-Server avahi-daemon[14022]: Service "Pizza-Server" (/services/ssh.service) successfully established.
Dec 17 16:43:43 Pizza-Server avahi-daemon[14022]: Service "Pizza-Server" (/services/smb.service) successfully established.
Dec 17 16:43:43 Pizza-Server avahi-daemon[14022]: Service "Pizza-Server" (/services/sftp-ssh.service) successfully established.
Dec 17 16:56:42 Pizza-Server kernel: veth650ab40: renamed from eth0
Dec 17 16:56:42 Pizza-Server kernel: docker0: port 1(vethd58a4fb) entered disabled state
Dec 17 16:56:42 Pizza-Server kernel: docker0: port 1(vethd58a4fb) entered disabled state
Dec 17 16:56:42 Pizza-Server kernel: device vethd58a4fb left promiscuous mode
Dec 17 16:56:42 Pizza-Server kernel: docker0: port 1(vethd58a4fb) entered disabled state
Dec 17 16:59:17 Pizza-Server kernel: docker0: port 1(veth91afc92) entered blocking state
Dec 17 16:59:17 Pizza-Server kernel: docker0: port 1(veth91afc92) entered disabled state
Dec 17 16:59:17 Pizza-Server kernel: device veth91afc92 entered promiscuous mode
Dec 17 16:59:17 Pizza-Server kernel: docker0: port 1(veth91afc92) entered blocking state
Dec 17 16:59:17 Pizza-Server kernel: docker0: port 1(veth91afc92) entered forwarding state
Dec 17 16:59:17 Pizza-Server kernel: docker0: port 1(veth91afc92) entered disabled state
Dec 17 16:59:17 Pizza-Server kernel: eth0: renamed from veth9ea40d0
Dec 17 16:59:17 Pizza-Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth91afc92: link becomes ready
Dec 17 16:59:17 Pizza-Server kernel: docker0: port 1(veth91afc92) entered blocking state
Dec 17 16:59:17 Pizza-Server kernel: docker0: port 1(veth91afc92) entered forwarding state
Dec 17 16:59:49 Pizza-Server kernel: DMAR: DRHD: handling fault status reg 3
Dec 17 16:59:49 Pizza-Server kernel: DMAR: [DMA Write NO_PASID] Request device [00:02.0] fault addr 0x0 [fault reason 0x05] PTE Write access is not set
Dec 17 16:59:49 Pizza-Server kernel: DMAR: DRHD: handling fault status reg 3
Dec 17 16:59:49 Pizza-Server kernel: DMAR: [DMA Write NO_PASID] Request device [00:02.0] fault addr 0x0 [fault reason 0x05] PTE Write access is not set
Dec 17 16:59:49 Pizza-Server kernel: DMAR: DRHD: handling fault status reg 3
Dec 17 16:59:49 Pizza-Server kernel: DMAR: [DMA Write NO_PASID] Request device [00:02.0] fault addr 0x0 [fault reason 0x05] PTE Write access is not set
Dec 17 16:59:49 Pizza-Server kernel: DMAR: DRHD: handling fault status reg 3
Dec 17 17:00:44 Pizza-Server kernel: dmar_fault: 50 callbacks suppressed
Dec 17 17:00:44 Pizza-Server kernel: DMAR: DRHD: handling fault status reg 3
Dec 17 17:00:44 Pizza-Server kernel: DMAR: [DMA Write NO_PASID] Request device [00:02.0] fault addr 0x0 [fault reason 0x05] PTE Write access is not set
Dec 17 17:00:44 Pizza-Server kernel: DMAR: DRHD: handling fault status reg 3
Dec 17 17:00:44 Pizza-Server kernel: DMAR: [DMA Write NO_PASID] Request device [00:02.0] fault addr 0x0 [fault reason 0x05] PTE Write access is not set
Dec 17 17:00:44 Pizza-Server kernel: DMAR: DRHD: handling fault status reg 3
Dec 17 17:00:44 Pizza-Server kernel: DMAR: [DMA Write NO_PASID] Request device [00:02.0] fault addr 0x0 [fault reason 0x05] PTE Write access is not set
Dec 17 17:00:44 Pizza-Server kernel: DMAR: DRHD: handling fault status reg 3

 

syslog syslog-previous pizza-server-diagnostics-20231217-1726.zip

  • Community Expert
Dec 17 16:59:49 Pizza-Server kernel: DMAR: DRHD: handling fault status reg 3
Dec 17 16:59:49 Pizza-Server kernel: DMAR: [DMA Write NO_PASID] Request device [00:02.0] fault addr 0x0 [fault reason 0x05] PTE Write access is not set

 

This is the iGPU, look for a BIOS update or try blacklisting the driver.
 

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

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.