Stuck on 6.10.3, no GUI when I update

[trwolff04]

Been having this issue for months ... 6.10.3 works fine, but anytime I upgrade the server does it's thing, restarts, and I cannot get a GUI on local lan.  It loads and loads and loads.  All of my docker stuff works.  If I visit port localserver:8181, for instance, I can access tautulli.  Plex is working.  The only docker container that doesn't work is my hexbin qtorrent.  Additionally, if I restart and select "UNRAID GUI" from a monitor on my server I am able to enter the gui and downgrade back to 6.10.3.  It is very frustrating.  I have seen a few threads similar to this -- are there any solutions yet?  I'm running a repurposed HP industrial server ...

[JorgeB]

Try booting in safe mode, if that doesn't work create a new Unraid stock install with a different flash drive, no key needed, just to see if that one boots.

[trwolff04]

Thanks for the reply.  Just upgraded again with "Safe Mode w/ GUI" selected.  Yes, I can access unraid now over lan.  Thoughts?  Should I downgrade again and wait it out?

[JorgeB]

That's suggest you have a plugin problem, remove/disable them all then re-install/enable.

[trwolff04]

Is there a common plugin that has been presenting issues like this?  Trying to figure out where to start rather than rebooting 20 times.. I only encountered this issue when I attempted upgrading.  Stable on 6.10.3

Edited February 28, 2023 by trwolff04

[itimpi]

Several plugins are now deprecated on the 6.11+ releases as being incompatible.    An obvious candidate is NerdPack but I think there are others as well.

[trwolff04]

Is there any way I can remove them from safe mode?

[JorgeB]

Yes, rename/delete all /boot/config/plugins/*.plg files

[trwolff04]

Nvm, SSH'd into /boot/config/plugins and deleted nerdpack.  Thanks again.

[trwolff04]

Meh, logging in today the prompt screen comes up real fast but then when I enter user/password it hangs again just like before.  Only difference is I can reach the login screen.  Any ideas?

[JorgeB]

This is in safe mode?

[trwolff04]

~24hrs booted in regular mode.

[JorgeB]

And in safe mode works?

[trwolff04]

Seeming so at this point but I didn't realize regular mode gui didn't work until 24 hrs later.  Should be noted all my docker ports were accessible and apps running fine.  Just couldn't access unraid itself.  Is there a list of plugins that are deprecated in the most recent unraid version?  Thinking I can check them one by one ... I already uninstalled nerdpacks.

 

Thanks

[JorgeB]

Re-test in safe mode and if no issues like that install the plugins one at at time.

[trwolff04]

Ran for 8 days in safe mode then crashed again.  All docker containers were still working except haugene transmission.  Downgraded back to 10.6.3 ... booted without safe mode, no issues yet. Seems there is definitely some type of bug present. 

[JorgeB]

Enable the syslog server and post that after a crash.

[trwolff04]

Okay, 7 days running on the newest unraid version in safe mode and I've had a partial crash.  The docker page won't even load, some of my containers have stopped running including, once again, qbittorrent.  I had enabled the syslog server in anticipation of this.  Do I have to shutdown before I download and upload the syslog or will it be functional for you if I upload it now while the server is still running?

 

File attached.  Please let me know if this is enough info for you to resolve this issue.  I see the one auth problem filling up the log but I think that is a separate issue.  See this part:

 

Apr  8 01:32:12 BEAST kernel: BUG: kernel NULL pointer dereference, address: 0000000000000036
Apr  8 01:32:12 BEAST kernel: #PF: supervisor read access in kernel mode
Apr  8 01:32:12 BEAST kernel: #PF: error_code(0x0000) - not-present page
Apr  8 01:32:12 BEAST kernel: PGD 0 P4D 0
Apr  8 01:32:12 BEAST kernel: Oops: 0000 [#1] PREEMPT SMP PTI
Apr  8 01:32:12 BEAST kernel: CPU: 26 PID: 21942 Comm: qbittorrent-nox Not tainted 5.19.17-Unraid #2
Apr  8 01:32:12 BEAST kernel: Hardware name: Dell Inc. PowerEdge R720/0H5J4J, BIOS 2.9.0 12/06/2019
Apr  8 01:32:12 BEAST kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
Apr  8 01:32:12 BEAST kernel: Code: e8 9d fd 67 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 c1 35 69 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
Apr  8 01:32:12 BEAST kernel: RSP: 0000:ffffc9000a433cc0 EFLAGS: 00010246
Apr  8 01:32:12 BEAST kernel: RAX: 0000000000000002 RBX: 0000000000000002 RCX: 0000000000000002
Apr  8 01:32:12 BEAST kernel: RDX: 0000000000000001 RSI: ffff8885700cdda8 RDI: 0000000000000002
Apr  8 01:32:12 BEAST kernel: RBP: 0000000000000000 R08: 0000000000000004 R09: ffffc9000a433cd0
Apr  8 01:32:12 BEAST kernel: R10: ffffc9000a433cd0 R11: ffffc9000a433d48 R12: 0000000000000000
Apr  8 01:32:12 BEAST kernel: R13: ffff888648b9e3f8 R14: 000000000000f3c6 R15: ffff888648b9e400
Apr  8 01:32:12 BEAST kernel: FS:  000015448e8ed6c0(0000) GS:ffff88880fb40000(0000) knlGS:0000000000000000
Apr  8 01:32:12 BEAST kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr  8 01:32:12 BEAST kernel: CR2: 0000000000000036 CR3: 00000008e34f0003 CR4: 00000000000606e0
Apr  8 01:32:12 BEAST kernel: Call Trace:
Apr  8 01:32:12 BEAST kernel: <TASK>
Apr  8 01:32:12 BEAST kernel: __filemap_get_folio+0x98/0x1ff
Apr  8 01:32:12 BEAST kernel: ? _raw_spin_unlock+0x14/0x29
Apr  8 01:32:12 BEAST kernel: filemap_fault+0x6e/0x524
Apr  8 01:32:12 BEAST kernel: __do_fault+0x30/0x6e
Apr  8 01:32:12 BEAST kernel: __handle_mm_fault+0x9a5/0xc7d
Apr  8 01:32:12 BEAST kernel: handle_mm_fault+0x113/0x1d7
Apr  8 01:32:12 BEAST kernel: do_user_addr_fault+0x36a/0x514
Apr  8 01:32:12 BEAST kernel: exc_page_fault+0xfc/0x11e
Apr  8 01:32:12 BEAST kernel: asm_exc_page_fault+0x22/0x30
Apr  8 01:32:12 BEAST kernel: RIP: 0033:0x1544a7ab90c1
Apr  8 01:32:12 BEAST kernel: Code: 48 01 d0 eb 1b 0f 1f 40 00 f3 0f 1e fa 48 39 d1 0f 82 83 63 07 00 0f 1f 00 f3 0f 1e fa 48 89 f8 48 83 fa 10 0f 82 af 00 00 00 <0f> 10 06 48 83 fa 20 0f 87 0f 01 00 00 0f 10 4c 16 f0 0f 11 07 0f
Apr  8 01:32:12 BEAST kernel: RSP: 002b:000015448e8eb2c8 EFLAGS: 00010206
Apr  8 01:32:12 BEAST kernel: RAX: 0000154340028d70 RBX: 000015448e8ec308 RCX: 000015448e8eb500
Apr  8 01:32:12 BEAST kernel: RDX: 0000000000004000 RSI: 0000153bebfc6000 RDI: 0000154340028d70
Apr  8 01:32:12 BEAST kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
Apr  8 01:32:12 BEAST kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
Apr  8 01:32:12 BEAST kernel: R13: 0000154344045bb0 R14: 0000000000000000 R15: 0000564d584635f0
Apr  8 01:32:12 BEAST kernel: </TASK>
Apr  8 01:32:12 BEAST kernel: Modules linked in: af_packet tcp_diag udp_diag inet_diag macvlan tun xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc tg3 mgag200 drm_shmem_helper i2c_algo_bit drm_kms_helper drm ipmi_ssif backlight x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd mpt3sas rapl intel_cstate i2c_core nvme ahci raid_class syscopyarea input_leds sysfillrect sysimgblt intel_uncore nvme_core libahci joydev led_class cdc_acm fb_sys_fops scsi_transport_sas wmi ipmi_si acpi_power_meter button unix [last unloaded: tg3]
Apr  8 01:32:12 BEAST kernel: CR2: 0000000000000036
Apr  8 01:32:12 BEAST kernel: ---[ end trace 0000000000000000 ]---
Apr  8 01:32:12 BEAST kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
Apr  8 01:32:12 BEAST kernel: Code: e8 9d fd 67 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 c1 35 69 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
Apr  8 01:32:12 BEAST kernel: RSP: 0000:ffffc9000a433cc0 EFLAGS: 00010246
Apr  8 01:32:12 BEAST kernel: RAX: 0000000000000002 RBX: 0000000000000002 RCX: 0000000000000002
Apr  8 01:32:12 BEAST kernel: RDX: 0000000000000001 RSI: ffff8885700cdda8 RDI: 0000000000000002
Apr  8 01:32:12 BEAST kernel: RBP: 0000000000000000 R08: 0000000000000004 R09: ffffc9000a433cd0
Apr  8 01:32:12 BEAST kernel: R10: ffffc9000a433cd0 R11: ffffc9000a433d48 R12: 0000000000000000
Apr  8 01:32:12 BEAST kernel: R13: ffff888648b9e3f8 R14: 000000000000f3c6 R15: ffff888648b9e400
Apr  8 01:32:12 BEAST kernel: FS:  000015448e8ed6c0(0000) GS:ffff88880fb40000(0000) knlGS:0000000000000000
Apr  8 01:32:12 BEAST kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr  8 01:32:12 BEAST kernel: CR2: 0000000000000036 CR3: 00000008e34f0003 CR4: 00000000000606e0

 

Thoughts?  Looks like another user with a similar system (R710 vs my R720) is having a similar issue here:

syslog-192.168.1.60.log

Edited April 9, 2023 by trwolff04

[JorgeB]

That looks like this issue:

 

[trwolff04]

Thank you!  I will look into this in the morning.  Happy Easter.

[trwolff04]

7 days still no issues.  Thank you.  Marked resolved unless anything else comes up.