Hi all, I'm trying to setup unraid for the first time but WebGUI isn't available.

 

In normal boot mode, I get to the CLI login prompt, there aren't any obvious errors in the output, and I can login to the shell with "root" and no password. But I can't connect to the WebGUI from my laptop. Going to http(s)://tower.local shows DNS_PROBE_FINISHED_NXDOMAIN, and http(s)://10.0.0.12 shows ERR_CONNECTION_REFUSED. I also can't SSH with `ssh [email protected]`, that also shows "ssh: connect to host 10.0.0.12 port 22: Connection refused".

 

In GUI boot mode it's a similar story. Boots into the OS and launches the browser, but connecting to http(s)://localhost causes the same ERR_CONNECTION_REFUSED (the error isn't displayed in Firefox but I checked in dev tools). The browser can access the internet fine.

 

Given this, my assumption is that some or all of unraid isn't starting up successfully after OS boot.

 

Troubleshooting steps I've tried so far:

• Clean wipe of USB before setting up again with Unraid USB Creator
• Creating the bootable USB on both Mac and Windows
• Trying multiple USB sticks
• Using a new Samsung Bar Plus USB stick as recommended by this thread
• Booting into Safe Mode and Safe Mode with GUI
• Ensuring USB stick is plugged into USB 2.0 port
• Waiting ~15 min after boot before trying to connect again

 

All of the above steps have resulted in the exact same behaviour.

 

System info:

• Unraid v6.12.14
• Motherboard: ASRock Z790 Lightning Wifi
• CPU: Intel Core i5 13600K
• RAM: Corsair Vengeance 32GB (2x16GB) C40 UDIMM 5200MHz DDR5
• Connected disks:
  • Samsung 970 EVO Plus 1TB PCIe Gen3 M.2 2280 NVMe SSD
  • Crucial P3 Plus 1TB CT1000P3PSSD8 PCIe Gen4 M.2 2280 NVMe SSD
  • 3x Seagate Barracuda Pro 12TB (Manufacturer Recertified)

 

Thanks in advance for your help!

tower-diagnostics-20241215-1705.zip

Dec 15 17:04:20 Tower emhttpd: Unregistered Flash device error (ENOFLASH4)

 

No flash drive is being detected, try a different port or a different flash drive, could also be related to USB settings in the BIOS.

On 12/16/2024 at 9:20 PM, JorgeB said:

Dec 15 17:04:20 Tower emhttpd: Unregistered Flash device error (ENOFLASH4)

 

No flash drive is being detected, try a different port or a different flash drive, could also be related to USB settings in the BIOS.

I've tried three different flash drives, and different USB ports. Also tried a bunch of BIOS settings and nothing has helped so far, such as legacy USB support, XHCI handoff, power saving settings, secure boot, etc.

 

Also, the flash drive is visible to the OS, I can see its contents mounted at `/boot` after logging in as root.

 

Is there anything else I can try? Once booted are there commands I can run to try manually starting unraid?

 

Edit: I've also tried updating the BIOS to the latest version as well.

Edited December 17, 20241 yr by commscheck

Definitely something strange going on as the syslog shows:

Dec 15 17:04:20 Tower emhttpd: shcmd (6): /sbin/modprobe md-mod super=/boot/config/super.dat
Dec 15 17:04:20 Tower emhttpd: Unregistered Flash device error (ENOFLASH4)
Dec 15 17:04:20 Tower kernel: md: unRAID driver 2.9.27 installed
Dec 15 17:04:20 Tower kernel: read_file: /e..t/...
Dec 15 17:04:20 Tower kernel: md: could not read superblock from /boot/config/super.dat
Dec 15 17:04:20 Tower kernel: md: initializing superblock
Dec 15 17:04:20 Tower emhttpd: Device inventory:
Dec 15 17:04:20 Tower emhttpd: CT1000P3PSSD8_24434BBBF4D3 (nvme1n1) 512 1953525168
Dec 15 17:04:20 Tower emhttpd: ST12000DM0007-2GR116_ZJV1DZ0H (sdd) 512 23437770752
Dec 15 17:04:20 Tower emhttpd: ST12000DM0007-2GR116_ZJV439Q2 (sdb) 512 23437770752
Dec 15 17:04:20 Tower emhttpd: ST12000DM0007-2GR116_ZJV43AEL (sdc) 512 23437770752
Dec 15 17:04:20 Tower emhttpd: Samsung_SSD_970_EVO_Plus_1TB_S4EWNS0X106903E (nvme0n1) 512 1953525168
Dec 15 17:04:20 Tower emhttpd: Samsung_Flash_Drive_0376924070001324-0:0 (sda) 512 125313283
Dec 15 17:04:20 Tower emhttpd: Error: () not present

That is despite the fact it appears to have mounted at /boot:

 

can you confirm that the drive is formatted as FAT32, and that the licence key is in the ‘config’ folder on the flash drive?

Last user who had a similar error fixed it after enabling "USB power delivery in S5 State", of course, this could have been a specif issue with that hardware, but still worth looking for something similar.

18 hours ago, itimpi said:

can you confirm that the drive is formatted as FAT32, and that the licence key is in the ‘config’ folder on the flash drive?

Can confirm the drive is FAT32. There's no licence key in the config folder, I'm trying to run it for the first time with the 30 day trial.

 

18 hours ago, JorgeB said:

Last user who had a similar error fixed it after enabling "USB power delivery in S5 State"

I saw that thread, unfortunately my BIOS doesn't seem to have an equivalent option.

After a lot of trial-and-error, I've made some progress.

 

tldr: On two different motherboards, Unraid fails to start if two M.2 SSDs are attached.

 

I tried booting the Unraid USB on my gaming PC and it loaded WebUI fine, so I was certain it wasn't the USB. Looking at threads about similar issues, I was pretty sure it was the motherboard but had gotten nowhere playing with the BIOS settings. I ended up swapping the motherboards between the gaming and server rigs. The CPUs and RAM sticks were swapped as well as they were both different socket types. But after swapping them out (reattaching heat sinks and all that as well) then trying to boot up Unraid, it still wouldn't start!!

 

The main differences left between the two rigs were that:

1. the gaming rig had a GPU, and
2. the server rig had two M.2 SSDs attached where the gaming rig only had one.

I tried removing one of the SSDs from the server rig, and Unraid started working! Testing it on the other motherboard (now in the gaming rig but also with only one M.2 SSD attached) also worked.

 

Kinda odd that the second M.2 is causing USB issues, without knowing much about it I guess it could be from the PCIe lanes being used? But both SSDs were visible and bootable in BIOS, and I'm fairly sure both were mounted in the OS after boot (not 100% sure on that though, I'd need to re-test).

 

I should probably swap the motherboards & CPUs back to their original rigs, but it took me ~2 hours last time so not feeling super motivated right this second. Anyway, needed to get it all written down, bit annoyed I can't use 2 M.2 drives since I was going to use them as a mirrored pool, but mostly happy I've got a working system now!

Edited January 2, 20251 yr by commscheck

Hey, I'm back with an update after giving this another go. Turns out all it took was force-erasing the 2nd NVMe SSD:

# ⚠️ WARNING: Will cause data loss!! ⚠️
#
# zeroes out the first 100MB of nvme1:
dd if=/dev/zero of=/dev/nvme1n1 bs=1M count=100 oflag=direct

I'm certain I'd already tried formatting both SSDs, but maybe I hadn't done it correctly. After running the above command and rebooting, unraid started normally, and the 2nd SSD appeared as an unassigned disk.

 

So it was nothing to do with the boot USB, or PCIe lanes. Just something about the way the 2nd SSD was formatted was breaking unraid's startup process!

Do you mean that erasing the SSD allowed Unraid to correctly detect the flash drive? That should not be needed.