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.

Server crashes just about everyday

Featured Replies

The longest it has went without crashing has been about 48 hours, this has been happening since day one. From looking at the log it always start here Tower kernel: pcieport 0000:03:06.0: Unable to change power state from D3hot to D0, device inaccessible.

 

I have tried running it was just the ADATA RAM and just with the Oloy RAM.

I switched from ipvlan to macvlan

Disabled C state in BIOS

Tried removing the GPU

 

How do I fix this?

 

Spec:

Ryzen 3200G

ASUS Prime B450 Motherboard

RTX 3060TI

2x8GB ADATA RAM and 1x8GB Oloy

 

Dockers Currently Running:

binhex-delugevpn

binhex-prowlarr

immich

lidarr

Plex-Media-Serve

postgresql14

radarr

Redis

sonarr

syslog-previous

Edited by Brock25

  • Community Expert
3 hours ago, Brock25 said:

switched from ipvlan to macvlan

I assume this is a typo as you WANT to use ipvlan if possible.

  • Author

I was originally using ipvlan however I was told to try macvlan and see what happens.

  • Community Expert
Jun  5 15:00:30 Tower kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

 

NIC troubles, try using an ad-don NIC, ideally from Intel.

 

In case you missed it you are also having issues with multiple disks, but that should be unrelated to the crashing.

  • Author
On 6/8/2024 at 3:52 AM, JorgeB said:
Jun  5 15:00:30 Tower kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

 

NIC troubles, try using an ad-don NIC, ideally from Intel.

 

In case you missed it you are also having issues with multiple disks, but that should be unrelated to the crashing.

The OS doesn't actually crash, basically the networking and sata ports stop working and I've noticed it always happen after the change Tower kernel: pcieport 0000:03:06.0: Unable to change power state from D3hot to D0, device inaccessible.

 

Could it be a bad motherboard?

Edited by Brock25

  • Community Expert

Could be, that is happening to multiple devices, and just before the NIC issue:

 

Jun  5 15:00:24 Tower kernel: pcieport 0000:03:06.0: Unable to change power state from D3hot to D0, device inaccessible
Jun  5 15:00:24 Tower kernel: pcieport 0000:03:05.0: Unable to change power state from D3hot to D0, device inaccessible
Jun  5 15:00:24 Tower kernel: pcieport 0000:03:04.0: Unable to change power state from D3hot to D0, device inaccessible
Jun  5 15:00:24 Tower kernel: pcieport 0000:03:00.0: Unable to change power state from D3hot to D0, device inaccessible
Jun  5 15:00:30 Tower kernel: ------------[ cut here ]------------
Jun  5 15:00:30 Tower kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

 

Post the complete diags to see the PCI IDs.

  • Author
45 minutes ago, JorgeB said:

Could be, that is happening to multiple devices, and just before the NIC issue:

 

Jun  5 15:00:24 Tower kernel: pcieport 0000:03:06.0: Unable to change power state from D3hot to D0, device inaccessible
Jun  5 15:00:24 Tower kernel: pcieport 0000:03:05.0: Unable to change power state from D3hot to D0, device inaccessible
Jun  5 15:00:24 Tower kernel: pcieport 0000:03:04.0: Unable to change power state from D3hot to D0, device inaccessible
Jun  5 15:00:24 Tower kernel: pcieport 0000:03:00.0: Unable to change power state from D3hot to D0, device inaccessible
Jun  5 15:00:30 Tower kernel: ------------[ cut here ]------------
Jun  5 15:00:30 Tower kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

 

Post the complete diags to see the PCI IDs.

 

Is this what you are talking about?

tower-diagnostics-20240609-1240.zip

  • Community Expert

Yes, and those are all PCIe ports:

 

03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
    Subsystem: ASMedia Technology Inc. 400 Series Chipset PCIe Port [1b21:3306]
    Kernel driver in use: pcieport
03:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
    Subsystem: ASMedia Technology Inc. 400 Series Chipset PCIe Port [1b21:3306]
    Kernel driver in use: pcieport
03:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
    Subsystem: ASMedia Technology Inc. 400 Series Chipset PCIe Port [1b21:3306]
    Kernel driver in use: pcieport
03:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
    Subsystem: ASMedia Technology Inc. 400 Series Chipset PCIe Port [1b21:3306]
    Kernel driver in use: pcieport

 

Look for a BIOS update, or try toggling some PCIe related settings in the BIOS, failing that I would try a different bard.

  • Author
32 minutes ago, JorgeB said:

Yes, and those are all PCIe ports:

 

03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
    Subsystem: ASMedia Technology Inc. 400 Series Chipset PCIe Port [1b21:3306]
    Kernel driver in use: pcieport
03:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
    Subsystem: ASMedia Technology Inc. 400 Series Chipset PCIe Port [1b21:3306]
    Kernel driver in use: pcieport
03:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
    Subsystem: ASMedia Technology Inc. 400 Series Chipset PCIe Port [1b21:3306]
    Kernel driver in use: pcieport
03:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
    Subsystem: ASMedia Technology Inc. 400 Series Chipset PCIe Port [1b21:3306]
    Kernel driver in use: pcieport

 

Look for a BIOS update, or try toggling some PCIe related settings in the BIOS, failing that I would try a different bard.

I forgot to mention BIOS has been updated to the latest.

 

I will look for some PCIe toggles and see what I can find.

  • Author
On 6/9/2024 at 5:15 PM, JorgeB said:

Yes, and those are all PCIe ports:

 

03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
    Subsystem: ASMedia Technology Inc. 400 Series Chipset PCIe Port [1b21:3306]
    Kernel driver in use: pcieport
03:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
    Subsystem: ASMedia Technology Inc. 400 Series Chipset PCIe Port [1b21:3306]
    Kernel driver in use: pcieport
03:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
    Subsystem: ASMedia Technology Inc. 400 Series Chipset PCIe Port [1b21:3306]
    Kernel driver in use: pcieport
03:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
    Subsystem: ASMedia Technology Inc. 400 Series Chipset PCIe Port [1b21:3306]
    Kernel driver in use: pcieport

 

Look for a BIOS update, or try toggling some PCIe related settings in the BIOS, failing that I would try a different bard.

 

I use Plex every night and the server would stop working, the last 2 nights I have had Plex disable and the server hasn't had any issues. Any ideas now?

  • Community Expert

It's not uncommon to see users with Plex crashing a server, possibly for various reasons, including hardware issue or Plex bugs, but can't help with that since I've never used it.

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.