March 5, 20233 yr Upgraded my server a few months back and have had this happen maybe 5 times. The server becomes completely unresponsive and this is what the display output shows. I tired setting up the syslog server to get details there but it didn't seem to contain any relevant info. My understanding is diagnostics are reset on reboot so not sure if they'll help but I can grab them if needed. It looked to be something network related so I did switch from the dragon lan to the Intel lan on the MB but just had the issue so not sure where to go from here. Any help would be greatly appreciated!
March 6, 20233 yr Author 5 hours ago, JorgeB said: Please post the diagnostics mostly to see the hardware used. Attached and just for good measure this is what I get in the syslog. Nothing after a 2am email sent until 9:55 when I had to hard shutdown and reboot. Mar 4 02:00:09 unGEO crond[1545]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Mar 4 05:00:01 unGEO kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 1 Mar 4 05:00:01 unGEO kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 2 Mar 4 05:00:49 unGEO kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 2 with status: 0 Mar 4 05:00:51 unGEO kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 1 with status: 0 Mar 5 00:20:02 unGEO sSMTP[30925]: Creating SSL connection to host Mar 5 00:20:02 unGEO sSMTP[30925]: SSL connection using TLS_AES_256_GCM_SHA384 Mar 5 00:20:04 unGEO sSMTP[30925]: Sent mail for [email protected] Mar 5 02:02:54 unGEO crond[1545]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Mar 5 09:55:34 unGEO root: Delaying execution of fix common problems scan for 10 minutes Mar 5 09:55:34 unGEO unassigned.devices: Mounting 'Auto Mount' Devices... Mar 5 09:55:34 unGEO unassigned.devices: Mounting partition 'sdh1' at mountpoint '/mnt/disks/WDBlueVMDrive'... Mar 5 09:55:34 unGEO unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime,discard '/dev/sdh1' '/mnt/disks/WDBlueVMDrive' Mar 5 09:55:34 unGEO kernel: XFS (sdh1): Mounting V5 Filesystem Mar 5 09:55:34 unGEO kernel: XFS (sdh1): Starting recovery (logdev: internal) Mar 5 09:55:34 unGEO kernel: XFS (sdh1): Ending recovery (logdev: internal) Mar 5 09:55:34 unGEO unassigned.devices: Successfully mounted 'sdh1' on '/mnt/disks/WDBlueVMDrive'. Mar 5 09:55:34 unGEO unassigned.devices: Unassigned Devices are not set to be shared with SMB. Mar 5 09:55:34 unGEO unassigned.devices: Unassigned Devices are not set to be shared with NFS. Mar 5 09:55:34 unGEO emhttpd: Starting services... Mar 5 09:55:34 unGEO emhttpd: shcmd (63): /etc/rc.d/rc.samba restart Mar 5 09:55:34 unGEO wsdd2[4872]: 'Terminated' signal received. Mar 5 09:55:34 unGEO winbindd[4877]: [2023/03/05 09:55:34.159001, 0] ../../source3/winbindd/winbindd_dual.c ungeo-diagnostics-20230306-0838.zip
March 6, 20233 yr Community Expert No known issues with that hardware AFAIK, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
March 6, 20233 yr Author 1 minute ago, JorgeB said: No known issues with that hardware AFAIK, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. It's so random I don't know what would tell me anything. The last one was 2/21 and the time before was 2/15. So anywhere between 6 and 12 days from one occourance to the next. Not on the same day of the week or time either so it doesn't seem to be triggered by any scheduled event.
March 27, 20233 yr Author Had a faulty nvme drive. Replaced over the weekend. Maybe that was contributing? Time will tell
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.