For the past 3 days, every morning when I wake up the server has to be rebooted. Containers like plex and others are still working but I just cannot login via ssh, the browser, or from the server directly and I have to do a hard reboot to regain access.

 

It may be my USB drive as I'm seeing the error below in the logs but would love it if someone could take a quick look and see if you could see if there's anything else going on.

 

I've managed to get diagnostics during one of the failures just before I rebooted (attached). I also attached syslogs for past few days.

 

Thank you.

 

eb 19 08:50:40 pumbaa kernel: usb 1-6.3: reset high-speed USB device number 6 using xhci_hcd
Feb 19 08:50:40 pumbaa kernel: sd 4:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s
Feb 19 08:50:40 pumbaa kernel: sd 4:0:0:0: [sde] tag#0 CDB: opcode=0x28 28 00 00 73 ae ce 00 00 10 00
Feb 19 08:50:40 pumbaa kernel: I/O error, dev sde, sector 7581390 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2

 

pumbaa-diagnostics-20250219-0927.zip syslog_last3days.log.zip

That looks more like a USB reset, try connecting the flash drive to a different USB port, but if you continue to see errors, better to replace it.

New one gets here on Saturday, thanks @JorgeB. So you would agree that this looks like a kernel panic or something due to issues with the USB device? You don't see any other relevant issues?

 

When you say USB reset, try a different USB port...are you thinking that the server usb port is losing power momentarily or something? Sorry, not entirely sure what a "usb reset" means.

 

Thanks again.

22 minutes ago, geeksheikh said:

try a different USB port...are you thinking that the server usb port is losing power momentarily or something?

Something like that, or just a USB disconnect, that sometimes just happens with USB.

All these issues started after I upgraded to 7.0.0 a few days ago. Now I cannot connect again but my open shell is working but is very laggy (even typing is laggy).

 

I have a home assistant VM, is there some kind of conflict that is borking my connectivity to Unraid? I cannot create new ssh session or get to web ui but existing shell session still active.

 

Update:

All my docker containers and the Home assistant VM (webui) are all still working fine and allowing connections. 

 

Feb 20 16:38:57 pumbaa nmbd[3057]: [2025/02/20 16:38:55.495353,  0] ../../source3/nmbd/nmbd_incomingrequests.c:116(process_name_release_request)
Feb 20 16:38:57 pumbaa nmbd[3057]:   process_name_release_request: Attempt to release name WORKGROUP<1d> from IP 10.10.80.193 on subnet 10.10.80.175
 being rejected as it is one of our names.
Feb 20 16:39:55 pumbaa nmbd[3057]: [2025/02/20 16:39:53.786888,  0] ../../source3/nmbd/nmbd_incomingrequests.c:116(process_name_release_request)
Feb 20 16:39:55 pumbaa nmbd[3057]:   process_name_release_request: Attempt to release name WORKGROUP<1d> from IP 10.10.80.193 on subnet 10.10.80.175
 being rejected as it is one of our names.
Feb 20 16:42:00 pumbaa nmbd[3057]: [2025/02/20 16:41:59.956165,  0] ../../source3/nmbd/nmbd_incomingrequests.c:116(process_name_release_request)
Feb 20 16:42:00 pumbaa nmbd[3057]:   process_name_release_request: Attempt to release name WORKGROUP<1d> from IP 10.10.80.193 on subnet 10.10.80.175
 being rejected as it is one of our names.
Feb 20 16:42:00 pumbaa nmbd[3057]: [2025/02/20 16:42:00.628106,  0] ../../source3/nmbd/nmbd_incomingrequests.c:116(process_name_release_request)
Feb 20 16:42:00 pumbaa nmbd[3057]:   process_name_release_request: Attempt to release name WORKGROUP<1d> from IP 10.10.80.193 on subnet 10.10.80.175
 being rejected as it is one of our names.
Feb 20 16:42:03 pumbaa nmbd[3057]: [2025/02/20 16:42:02.903949,  0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce)
Feb 20 16:42:03 pumbaa nmbd[3057]:   process_local_master_announce: Server HOMEASSISTANT at IP 10.10.80.193 is announcing itself as a local master b
rowser for workgroup WORKGROUP and we think we are master. Forcing election.
Feb 20 16:49:42 pumbaa php-fpm[8268]: [WARNING] [pool www] child 1888456 exited on signal 9 (SIGKILL) after 39.173931 seconds from start
Feb 20 16:50:55 pumbaa php-fpm[8268]: [WARNING] [pool www] child 1889596 exited on signal 9 (SIGKILL) after 61.052363 seconds from start
Feb 20 16:51:17 pumbaa nmbd[3057]: [2025/02/20 16:51:16.993274,  0] ../../source3/nmbd/nmbd_incomingrequests.c:116(process_name_release_request)
Feb 20 16:51:17 pumbaa nmbd[3057]:   process_name_release_request: Attempt to release name WORKGROUP<1d> from IP 10.10.80.193 on subnet 10.10.80.175
 being rejected as it is one of our names.
Feb 20 16:51:17 pumbaa nmbd[3057]: [2025/02/20 16:51:17.257120,  0] ../../source3/nmbd/nmbd_incomingrequests.c:116(process_name_release_request)
Feb 20 16:51:17 pumbaa nmbd[3057]:   process_name_release_request: Attempt to release name WORKGROUP<1d> from IP 10.10.80.193 on subnet 10.10.80.175
 being rejected as it is one of our names.
Feb 20 16:51:17 pumbaa nmbd[3057]: [2025/02/20 16:51:17.257966,  0] ../../source3/nmbd/nmbd_incomingrequests.c:116(process_name_release_request)
Feb 20 16:51:17 pumbaa nmbd[3057]:   process_name_release_request: Attempt to release name WORKGROUP<1d> from IP 10.10.80.193 on subnet 10.10.80.175
 being rejected as it is one of our names.
Feb 20 16:51:17 pumbaa nmbd[3057]: [2025/02/20 16:51:17.258010,  0] ../../source3/nmbd/nmbd_incomingrequests.c:116(process_name_release_request)
Feb 20 16:51:17 pumbaa nmbd[3057]:   process_name_release_request: Attempt to release name WORKGROUP<1d> from IP 10.10.80.193 on subnet 10.10.80.175
 being rejected as it is one of our names.
Feb 20 16:51:17 pumbaa nmbd[3057]: [2025/02/20 16:51:17.258127,  0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce)
Feb 20 16:51:17 pumbaa nmbd[3057]:   process_local_master_announce: Server HOMEASSISTANT at IP 10.10.80.193 is announcing itself as a local master b
rowser for workgroup WORKGROUP and we think we are master. Forcing election.
Feb 20 17:30:07 pumbaa sshd-session[1986160]: Connection from 10.10.81.243 port 56098 on 10.10.80.175 port 22 rdomain ""
Feb 20 17:30:45 pumbaa nmbd[3057]: [2025/02/20 17:30:44.801571,  0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce)
Feb 20 17:30:45 pumbaa nmbd[3057]:   process_local_master_announce: Server HOMEASSISTANT at IP 10.10.80.193 is announcing itself as a local master b
rowser for workgroup WORKGROUP and we think we are master. Forcing election.

 

Edited February 20, 20251 yr by geeksheikh

9 hours ago, geeksheikh said:

Feb 20 16:49:42 pumbaa php-fpm[8268]: [WARNING] [pool www] child 1888456 exited on signal 9 (SIGKILL) after 39.173931 seconds from start
Feb 20 16:50:55 pumbaa php-fpm[8268]: [WARNING] [pool www] child 1889596 exited on signal 9 (SIGKILL) after 61.052363 seconds from start

In my experience these usually mean the server memory is close to exhaustion, the GUI can still work but becomes extra slow, like 1 minute to open the dashboard.

@JorgeB I just got my new drive, I moved the Pro.key file (and the rest of the config) to the new drive but I cannot get the "replace key" function to work. The first time I tried it I forgot to switch to the DNS server to one that worked so it probably couldn't resolve. Switched that in networking and tried again but it's still giving me the same problem.

 

I replaced the Pro.key file again, rebooted, tried to "Replace Key" again and it's still not working. I get a pop up in the top right corner that just says, "Error attempting to replace key". Suggestions? I'm dead in the water right now.

 

Thanks.

Ok nvm, I was able to get it fixed by downloading the key file from unraid.net account management.