I can boot into unraid, but GUI mode or via the network the GUI won't come up. Trying to figure out how to debug this.

 

This is a rebuilt server (same array, same flash, new cache drive). All drives appear to show and I can SSH into it, I just can't view the UI at all. Any thoughts or tips or how to even get logs via ssh would be much appreciated

 

3 minutes ago, wickedathletes said:

I can SSH into it

Try this first:

 

https://forums.unraid.net/topic/92462-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/page/265/?tab=comments#comment-1068461

 

If that doesn't fix it, then from the command prompt

diagnostics

and upload the resulting zip file from the flash drive here.

2 minutes ago, Squid said:

Try this first:

 

https://forums.unraid.net/topic/92462-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/page/265/?tab=comments#comment-1068461

 

If that doesn't fix it, then from the command prompt

diagnostics

and upload the resulting zip file from the flash drive here.

 

Guess I don't have that installed?

plugin: updating: unassigned.devices.plg
plugin: unassigned.devices.plg not installed

 

Then diagnostics  

@Squid, log attached. thank you as well.

hades-diagnostics-20211212-1229.zip

I remember this from v5 and unMenu, but why is this line in your go file?

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c 

 

Delete this line from the /config/go on the flash drive  It's a remnant from unmenu

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c 

 

What is this in the same file?

unraid_notify start

 

If this stuff doesn't work, what happens if you boot in safe mode?

1 minute ago, trurl said:

I remember this from v5 and unMenu, but why is this line in your go file?

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c 

 

probably legacy? Its been upgraded since v4. Should I remove it?

 

Also, I noticed disk1 and disk11 are "missing" so I will take a look at that, however I am unsure why that would mess up the GUI.

Dec 12 12:29:14 Hades kernel: mdcmd (1): import 0 sdd 64 13672382412 0 WDC_WD140EDFZ-11A0VA0_Y5HL6U8C
Dec 12 12:29:14 Hades kernel: md: import disk0: (sdd) WDC_WD140EDFZ-11A0VA0_Y5HL6U8C size: 13672382412 
Dec 12 12:29:14 Hades kernel: mdcmd (2): import 1 sdf 64 3907018532 0 WDC_WD40EFRX-68WT0N0_WD-WCC4E3FVYAK2
Dec 12 12:29:14 Hades kernel: md: import disk1: (sdf) WDC_WD40EFRX-68WT0N0_WD-WCC4E3FVYAK2 size: 3907018532 
Dec 12 12:29:14 Hades kernel: mdcmd (3): import 2
Dec 12 12:29:14 Hades kernel: md: import_slot: 2 missing
Dec 12 12:29:14 Hades kernel: mdcmd (4): import 3 sdi 64 7814026532 0 WDC_WD80EMAZ-00WJTA0_7PJALG2C
Dec 12 12:29:14 Hades kernel: md: import disk3: (sdi) WDC_WD80EMAZ-00WJTA0_7PJALG2C size: 7814026532 
Dec 12 12:29:14 Hades kernel: mdcmd (5): import 4 sdm 64 7814026532 0 WDC_WD80EFAX-68LHPN0_7SGLZ6YC
Dec 12 12:29:14 Hades kernel: md: import disk4: (sdm) WDC_WD80EFAX-68LHPN0_7SGLZ6YC size: 7814026532 
Dec 12 12:29:14 Hades kernel: mdcmd (6): import 5 sdg 64 3907018532 0 WDC_WD40EZRZ-00WN9B0_WD-WCC4E2ZKC4UH
Dec 12 12:29:14 Hades kernel: md: import disk5: (sdg) WDC_WD40EZRZ-00WN9B0_WD-WCC4E2ZKC4UH size: 3907018532 
Dec 12 12:29:14 Hades kernel: mdcmd (7): import 6 sdj 64 7814026532 0 WDC_WD80EMAZ-00WJTA0_7SGMNZRC
Dec 12 12:29:14 Hades kernel: md: import disk6: (sdj) WDC_WD80EMAZ-00WJTA0_7SGMNZRC size: 7814026532 
Dec 12 12:29:14 Hades kernel: mdcmd (8): import 7 sdh 64 7814026532 0 WDC_WD80EMAZ-00WJTA0_7JK8BBKC
Dec 12 12:29:14 Hades kernel: md: import disk7: (sdh) WDC_WD80EMAZ-00WJTA0_7JK8BBKC size: 7814026532 
Dec 12 12:29:14 Hades kernel: mdcmd (9): import 8 sdk 64 7814026532 0 WDC_WD80EMAZ-00WJTA0_1SH10EUZ
Dec 12 12:29:14 Hades kernel: md: import disk8: (sdk) WDC_WD80EMAZ-00WJTA0_1SH10EUZ size: 7814026532 
Dec 12 12:29:14 Hades kernel: mdcmd (10): import 9 sdl 64 3907018532 0 Hitachi_HDS5C4040ALE630_PL1321LAGA673H
Dec 12 12:29:14 Hades kernel: md: import disk9: (sdl) Hitachi_HDS5C4040ALE630_PL1321LAGA673H size: 3907018532 
Dec 12 12:29:14 Hades kernel: mdcmd (11): import 10 sdb 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K7TXCL9Y
Dec 12 12:29:14 Hades kernel: md: import disk10: (sdb) WDC_WD40EFRX-68N32N0_WD-WCC7K7TXCL9Y size: 3907018532 
Dec 12 12:29:14 Hades kernel: mdcmd (12): import 11 sde 64 3907018532 0 HGST_HDS5C4040ALE630_PL2331LAGN8KEJ
Dec 12 12:29:14 Hades kernel: md: import disk11: (sde) HGST_HDS5C4040ALE630_PL2331LAGN8KEJ size: 3907018532 
Dec 12 12:29:14 Hades kernel: mdcmd (13): import 12
Dec 12 12:29:14 Hades kernel: md: import_slot: 12 missing
Dec 12 12:29:14 Hades kernel: mdcmd (14): import 13 sdc 64 13672382412 0 WDC_WD140EDGZ-11B1PA0_Y6GEA80D
Dec 12 12:29:14 Hades kernel: md: import disk13: (sdc) WDC_WD140EDGZ-11B1PA0_Y6GEA80D size: 13672382412

 

@Squid, here is a cleaner log with my driveshades-diagnostics-20211212-1301.zip fixed (they appreciate being plugged in I guess haha) and the go fixed. Same issue though, I will try safe mode next.

Edited December 12, 20214 yr by wickedathletes

so GUI safe mode loads, so that means i have a bad plugin right? My cache drive has not been setup yet, as its new (from old ssd to new NVMe drive). I just want to make sure that wouldn't cause it? I had planned to boot up and then create the cache from backup via ca.backup2.plg.

 

plugins I have:

 

could it be user.scripts since I don't have nvidia gpu anymore? Just guessing at this point.

 

Possible.  Change the extension on user.scripts.plg to be something else and reboot.

 

My next guess would be dynamix.unraid.net.plg

2 hours ago, Squid said:

Possible.  Change the extension on user.scripts.plg to be something else and reboot.

 

My next guess would be dynamix.unraid.net.plg

 

still no go, I renamed both .plg files to .plg1 as well. Do you know how to disable the unraid.net one specifically? My browser is still redirecting to XXXX.unraid.net which i assume is a piece of the plugin no? Latest logs attached as well.

hades-diagnostics-20211212-1555.zip

@Squid, could it be docker? I noticed in the logs my docker config is set to enabled but i dont have a cache drive setup yet.

That shouldn't matter.   The only thing is to try and wait a couple of minutes longer than what you've been doing.  Quirk of the GUI is that until everything is started up it won't respond.  Myself, I've got user scripts installed with a script set to run at array start that is nothing but 

beep
beep
beep

so that I know after a reboot when the system "thinks" it's up and running and then I know to wait a minute or two after those beeps before trying the WebUI

 

 

The troubleshooting from here is a pita, but it's renaming all the .plg files to be .plg1, reboot, then rename one of them back to .plg and reboot until the problems start again.  The last one renamed is the culprit.

 

(It's on a mental todo list to kinda automate this via a plugin at some point)

SSD Trim was the culprit. Thank you everone!

5 hours ago, wickedathletes said:

SSD Trim was the culprit. Thank you everone!

That is a major surprise