I'm getting random lockups (with no webui or ssh access), I/O errors, and hanging at boot. While I think part of my boot issue is BIOS related (likely necessitating an update), I'm curious if the cause of the lockups is identifiable via my syslog or the diagnostics (attached).

 

I don't think my docker image is full and it doesn't appear that my disks are bad. During this most recent reboot (around 2 per day), my cache drive didn't automatically mount, which seems like it may be a clue. Is my Unraid USB dying? I have it plugged into my only USB2 port FWIW.

 

I'm using an X11SCA-f motherboard and a 4tb M.2 cache drive, in case anybody has any related tips.

tower-diagnostics-20250505-1430.zip syslog-192.168.88.225.log

Edited May 5, 20251 yr by that_was_easy

May  4 20:45:56 Tower kernel: usb 2-5: USB disconnect, device number 2
May  4 20:45:56 Tower kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May  4 20:45:56 Tower kernel: device offline error, dev sda, sector 7705058 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
May  4 20:45:56 Tower kernel: device offline error, dev sda, sector 7705058 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
May  4 20:45:56 Tower kernel: I/O error, dev loop1, sector 182560 op 0x0:(READ) flags 0x800 phys_seg 10 prio class 2
May  4 20:45:56 Tower kernel: SQUASHFS error: Failed to read block 0x59243a0: -5
May  4 20:45:56 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [59243a0]
May  4 20:45:56 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [59243a0]

 

Flash drive is dropping offline, try a different USB port, if the same, replace the flash drive.

Quote

On 5/5/2025 at 11:49 PM, JorgeB said:

May  4 20:45:56 Tower kernel: usb 2-5: USB disconnect, device number 2
May  4 20:45:56 Tower kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
May  4 20:45:56 Tower kernel: device offline error, dev sda, sector 7705058 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
May  4 20:45:56 Tower kernel: device offline error, dev sda, sector 7705058 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
May  4 20:45:56 Tower kernel: I/O error, dev loop1, sector 182560 op 0x0:(READ) flags 0x800 phys_seg 10 prio class 2
May  4 20:45:56 Tower kernel: SQUASHFS error: Failed to read block 0x59243a0: -5
May  4 20:45:56 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [59243a0]
May  4 20:45:56 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [59243a0]

 

Flash drive is dropping offline, try a different USB port, if the same, replace the flash drive.

 

This was helpful, and resulted in a few days of uptime. I'm not sure why a different USB port was the solution after all this time, but great. I think I'm still going to look into a DOM USB setup just in case.

 

However, now, with minimal other changes made (I've been tinkering unsuccessfully with telegraf, influxdb, and grafana configs trying to get things to work), I can't access my server either from the webgui or ssh. Luckily, I use a motherboard with a BMC and I can run commands via KVM, but nothing I've tried (including querying ChatGPT) has helped.   I can login to Unraid and see that docker services, nginx, etc. are all running normally it seems, among a few other things I've checked. I was also able to pull diagnostics, again. I'm a bit at a loss as the logs don't reveal anything to me.

tower-diagnostics-20250509-2105.zip

Edited May 10, 20251 yr by that_was_easy

Try booting in safe mode to rule out a plugin issue, e.g., Tailscale.

On 5/9/2025 at 11:57 PM, JorgeB said:

Try booting in safe mode to rule out a plugin issue, e.g., Tailscale.

I may not have tried everything I should while in safe mode, but I'm getting the same behavior. No SSH/webgui access is possible.

 

I manually started ssh both in safe mode and after a normal boot and it worked. During the default boot the logs indicate the ssh service should have already started.  GUI is still inaccessible after default boot and also not after booting in Safe Mode. Using the guid start command results in a notification that it's already started but still no access at its ip:port.

By searching the logs I do see that I'm getting socket errors, but I'm not sure if that's the issue. At a total loss here. Could this still be my USB? Attached are the diagnostics pulled during the safe mode boot.

tower-diagnostics-20250510-2241.zip

Edited May 13, 20251 yr by that_was_easy

You can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.    

Thanks for your replies JorgeB. I will attempt this when I get home tonight. 

 

However, I just noticed, that I can still apparently access Vaultwarden using the client browser plugin. I'm curious as to how this could be possible and whether it sheds any light on the inaccessibility of all my other dockers and the webgui. To be clear, I can't access the docker directly, using it's url (reverse proxied via NPM docker and Cloudflare domain), but the browser plugin still works and is processing my credential request. 

10 hours ago, that_was_easy said:

access Vaultwarden

Sorry, don't know what that is, also not familiar with reverse proxies.