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 UI Not Fully Loading - 6.9.2

Featured Replies

Not sure what I've changed ( haven't updated/installed anything in about 3 days ) but all of a sudden I'm having immense difficulties accessing the Unraid UI. No issues loading Main, Shares, Users, Settings, Plugins (feels a bit slower than normal and cannot update plugins, script wont run when I hit the button), Apps, and Tools. The Dashboard won't load completely (screenshot below), VM (sometimes loads, sometimes won't) and Docker tabs (will not load anything below the navigation bar at all) are all causing me a major headache. If there are any other logs (sys log below) or diagnostics I can generate, please let me know. I have tried a server restart to no avail. Just want to get back to my data hording at this point!!

 

image.thumb.png.e433004799d506ac2c3677b4a81da441.png

image.thumb.png.f59be6d3acdd08ec5b7069ec3d550a8e.png

 

syslog (2)

mediaserv-diagnostics-20210504-1535.zip

Edited by jakeslominski
Add Diagnostics Zip

Python3 (from the bazaar app) was at one point having an absolute conniption on the server.

 

But, it looks like the btrfs driver crashed and is part of the problem.  I would start by running a memtest on the system.

  • Author
42 minutes ago, Squid said:

Python3 (from the bazaar app) was at one point having an absolute conniption on the server.

I ended up nuking my docker.img to start fresh wondering if it was one of my containers too. Seemed to fix things for awhile. Managed to reinstall plex till the server locked up again while scanning my libraries.

 

46 minutes ago, Squid said:

But, it looks like the btrfs driver crashed and is part of the problem.  I would start by running a memtest on the system.

Was planning on running memtest overnight/all day tomorrow since I work all day and won't need access to anything on their at the moment. Will update here with any results.

  • Author

UPDATE: So wasn't able to run memtest last night because I didn't realize it needed BIOS and not UEFI, so that will be run tonight I guess. Left it sitting running a parity check since this server has gone through alot in the last couple days and wanted to be safe. Its at 0 errors for 1.5TB right now so I'm not sure if this is related to parity or something else, but I am seeing alot of BTRFS errors in my log this morning. They came in right after log in and was going to check share sizes just out of curiosity. Logs below because incase it has any more meaning. Looks like the cache drive if I'm not mistaken.

 

May 5 08:28:01 MediaServ webGUI: Successful login user root from 192.168.50.51
May 5 08:30:15 MediaServ emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/share_size appdata ssz1 cache
May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:21 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): error loading props for ino 7314709 (root 5): -117
May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)
May 5 08:30:22 MediaServ kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=45910523904 parent_transid=218206 key expected=(7314709,12,281474984017009) has=(7314709,12,7306353)

  • Community Expert

RAM is way over max supported for that CPU/RAM combo, and a known stability issue with Ryzen, respect max RAM speeds here, btrfs file system should be recreated.

  • Community Expert
Just now, JorgeB said:

btrfs file system should be recreated.

After the problem is fixed.

  • Author
28 minutes ago, JorgeB said:

RAM is way over max supported for that CPU/RAM combo, and a known stability issue with Ryzen, respect max RAM speeds here

Crucial Ballistix 2666 MHz DDR4 DRAM Desktop Gaming Memory Kit 32GB (16GBx2) CL16 BL2K16G26C16U4B (BLACK)

 

So as far as I can tell, running at 2666 is within spec. Are you referring to how much RAM in terms of GB and if so, what would you recommend for my Ryzen 1700x.

7 minutes ago, jakeslominski said:

Crucial Ballistix 2666 MHz DDR4 DRAM Desktop Gaming Memory Kit 32GB (16GBx2) CL16 BL2K16G26C16U4B (BLACK)

 

So as far as I can tell, running at 2666 is within spec. Are you referring to how much RAM in terms of GB and if so, what would you recommend for my Ryzen 1700x.

 

You have 4 DIMMs of double rank memory running at 2746MT/s on a first gen Ryzen.

 

So you are above the memory spec (2666 apparently) and CPU spec (should be 1866 from the FAQ).

  • Community Expert
11 minutes ago, jakeslominski said:

So as far as I can tell, running at 2666 is within spec.

Why do I bother if people don't even read the link?

Archived

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

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.