DivideBy0 Posted April 4, 2021 Share Posted April 4, 2021 (edited) I just rebooted my unRaid like I always do and it came back like it was some kind of unclean shutdown and now is forcing a parity check. What happened here? Everything was running normal before the reboot. What could cause this? Edited April 4, 2021 by johnwhicker Quote Link to comment
Squid Posted April 4, 2021 Share Posted April 4, 2021 Without the diagnostics from /config/logs (on the flash drive) generated when the system forced a shutdown, it's impossible to know. Quote Link to comment
DivideBy0 Posted April 4, 2021 Author Share Posted April 4, 2021 (edited) 10 minutes ago, Squid said: Without the diagnostics from /config/logs (on the flash drive) generated when the system forced a shutdown, it's impossible to know. Good point Sir. I hope the diagnostic is still relevant as is been almost 24 hours since the reboot and still doing parity check right now. See attached please The syslog shows this: Apr 3 09:49:39 NAS-UNRAID emhttpd: Unraid(tm) System Management Utility version 6.9.1 Apr 3 09:49:39 NAS-UNRAID emhttpd: Copyright (C) 2005-2021, Lime Technology, Inc. Apr 3 09:49:39 NAS-UNRAID emhttpd: unclean shutdown detected nas-unraid-diagnostics-20210404-0940.zip Edited April 4, 2021 by johnwhicker Quote Link to comment
Squid Posted April 4, 2021 Share Posted April 4, 2021 Is that the last one in the logs folder? Strangely, it doesn't show any attempt to shut down, but it start up with an unclean shutdown detected Quote Link to comment
DivideBy0 Posted April 4, 2021 Author Share Posted April 4, 2021 4 minutes ago, Squid said: Is that the last one in the logs folder? Strangely, it doesn't show any attempt to shut down, but it start up with an unclean shutdown detected These are my last 2 before March nas-unraid-diagnostics-20210404-0940.zip nas-unraid-diagnostics-20210403-0946.zip Quote Link to comment
Squid Posted April 4, 2021 Share Posted April 4, 2021 20210403. Looks like you had a shell open with the system on a cwd to /mnt/user/.... That prevents the system from unmounting the drives since it's in use. Maybe install Dynamix Stop Shell to help alleviate that. Quote Link to comment
DivideBy0 Posted April 4, 2021 Author Share Posted April 4, 2021 Hmm something was going on with /mnt/user if you look at the April 3 log file Apr 3 09:45:09 NAS-UNRAID shutdown[399]: shutting down for system reboot Apr 3 09:45:10 NAS-UNRAID init: Switching to runlevel: 6 Apr 3 09:45:10 NAS-UNRAID init: Trying to re-exec init Apr 3 09:45:11 NAS-UNRAID nginx: 2021/04/03 09:45:11 [alert] 9363#9363: *1104470 open socket #20 left in connection 12 Apr 3 09:45:11 NAS-UNRAID nginx: 2021/04/03 09:45:11 [alert] 9363#9363: *1104467 open socket #36 left in connection 28 Apr 3 09:45:11 NAS-UNRAID nginx: 2021/04/03 09:45:11 [alert] 9363#9363: aborting Apr 3 09:45:13 NAS-UNRAID kernel: mdcmd (38): nocheck cancel Apr 3 09:45:14 NAS-UNRAID emhttpd: Spinning up all drives... Apr 3 09:45:14 NAS-UNRAID emhttpd: spinning up /dev/sdk Apr 3 09:45:14 NAS-UNRAID emhttpd: spinning up /dev/sdg Apr 3 09:45:14 NAS-UNRAID emhttpd: spinning up /dev/sdd Apr 3 09:45:14 NAS-UNRAID emhttpd: spinning up /dev/sdc Apr 3 09:45:14 NAS-UNRAID emhttpd: spinning up /dev/sdi Apr 3 09:45:23 NAS-UNRAID emhttpd: read SMART /dev/sdj Apr 3 09:45:23 NAS-UNRAID emhttpd: read SMART /dev/sdk Apr 3 09:45:23 NAS-UNRAID emhttpd: read SMART /dev/sdh Apr 3 09:45:23 NAS-UNRAID emhttpd: read SMART /dev/sdg Apr 3 09:45:23 NAS-UNRAID emhttpd: read SMART /dev/sdd Apr 3 09:45:23 NAS-UNRAID emhttpd: read SMART /dev/sde Apr 3 09:45:23 NAS-UNRAID emhttpd: read SMART /dev/sdb Apr 3 09:45:23 NAS-UNRAID emhttpd: read SMART /dev/sdf Apr 3 09:45:23 NAS-UNRAID emhttpd: read SMART /dev/sdc Apr 3 09:45:23 NAS-UNRAID emhttpd: read SMART /dev/sdi Apr 3 09:45:23 NAS-UNRAID emhttpd: read SMART /dev/sda Apr 3 09:45:23 NAS-UNRAID emhttpd: Stopping services... Apr 3 09:45:23 NAS-UNRAID emhttpd: shcmd (19102): /etc/rc.d/rc.libvirt stop Apr 3 09:45:24 NAS-UNRAID root: Waiting on VMs to shutdown Apr 3 09:45:24 NAS-UNRAID root: Stopping libvirtd... Apr 3 09:45:24 NAS-UNRAID dnsmasq[8822]: exiting on receipt of SIGTERM Apr 3 09:45:24 NAS-UNRAID kernel: device virbr0-nic left promiscuous mode Apr 3 09:45:24 NAS-UNRAID kernel: virbr0: port 1(virbr0-nic) entered disabled state Apr 3 09:45:24 NAS-UNRAID avahi-daemon[7215]: Interface virbr0.IPv4 no longer relevant for mDNS. Apr 3 09:45:24 NAS-UNRAID avahi-daemon[7215]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Apr 3 09:45:24 NAS-UNRAID avahi-daemon[7215]: Withdrawing address record for 192.168.122.1 on virbr0. Apr 3 09:45:24 NAS-UNRAID root: Network 2214f59d-018d-4270-9f9c-550be516a722 destroyed Apr 3 09:45:24 NAS-UNRAID root: Apr 3 09:45:27 NAS-UNRAID root: Stopping virtlogd... Apr 3 09:45:28 NAS-UNRAID root: Stopping virtlockd... Apr 3 09:45:29 NAS-UNRAID emhttpd: shcmd (19103): umount /etc/libvirt Apr 3 09:45:29 NAS-UNRAID root: Stopping docker_load Apr 3 09:45:29 NAS-UNRAID emhttpd: shcmd (19105): /etc/rc.d/rc.docker stop Apr 3 09:45:34 NAS-UNRAID kernel: docker0: port 1(veth24b78e5) entered disabled state Apr 3 09:45:34 NAS-UNRAID kernel: veth6b1bf0f: renamed from eth0 Apr 3 09:45:34 NAS-UNRAID avahi-daemon[7215]: Interface veth24b78e5.IPv6 no longer relevant for mDNS. Apr 3 09:45:34 NAS-UNRAID avahi-daemon[7215]: Leaving mDNS multicast group on interface veth24b78e5.IPv6 with address fe80::b83a:efff:fe57:e5f4. Apr 3 09:45:34 NAS-UNRAID kernel: docker0: port 1(veth24b78e5) entered disabled state Apr 3 09:45:34 NAS-UNRAID kernel: device veth24b78e5 left promiscuous mode Apr 3 09:45:34 NAS-UNRAID kernel: docker0: port 1(veth24b78e5) entered disabled state Apr 3 09:45:35 NAS-UNRAID avahi-daemon[7215]: Withdrawing address record for fe80::b83a:efff:fe57:e5f4 on veth24b78e5. Apr 3 09:45:41 NAS-UNRAID root: stopping dockerd ... Apr 3 09:45:42 NAS-UNRAID root: waiting for docker to die ... Apr 3 09:45:43 NAS-UNRAID avahi-daemon[7215]: Interface docker0.IPv6 no longer relevant for mDNS. Apr 3 09:45:43 NAS-UNRAID avahi-daemon[7215]: Leaving mDNS multicast group on interface docker0.IPv6 with address fe80::42:c9ff:fe6e:fd76. Apr 3 09:45:43 NAS-UNRAID avahi-daemon[7215]: Interface docker0.IPv4 no longer relevant for mDNS. Apr 3 09:45:43 NAS-UNRAID avahi-daemon[7215]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Apr 3 09:45:43 NAS-UNRAID avahi-daemon[7215]: Withdrawing address record for fe80::42:c9ff:fe6e:fd76 on docker0. Apr 3 09:45:43 NAS-UNRAID avahi-daemon[7215]: Withdrawing address record for 172.17.0.1 on docker0. Apr 3 09:45:43 NAS-UNRAID emhttpd: shcmd (19106): umount /var/lib/docker Apr 3 09:45:45 NAS-UNRAID root: Stopping CA Turbo Mode Apr 3 09:45:45 NAS-UNRAID root: Terminating 7480 Apr 3 09:45:45 NAS-UNRAID unassigned.devices: Unmounting All Devices... Apr 3 09:45:46 NAS-UNRAID unassigned.devices: Remote SMB/NFS share '//NAS-UNRAID-BKP/RAID-2' is not mounted. Apr 3 09:45:46 NAS-UNRAID unassigned.devices: Remote SMB/NFS share '//NAS-UNRAID-BKP/PLEX' is not mounted. Apr 3 09:45:47 NAS-UNRAID emhttpd: shcmd (19108): /etc/rc.d/rc.samba stop Apr 3 09:45:47 NAS-UNRAID nmbd[31019]: [2021/04/03 09:45:47.313461, 0] ../../source3/nmbd/nmbd.c:59(terminate) Apr 3 09:45:47 NAS-UNRAID nmbd[31019]: Got SIGTERM: going down... Apr 3 09:45:47 NAS-UNRAID nmbd[31019]: [2021/04/03 09:45:47.313635, 0] ../../source3/libsmb/nmblib.c:922(send_udp) Apr 3 09:45:47 NAS-UNRAID nmbd[31019]: Packet send failed to 172.17.255.255(138) ERRNO=Network is unreachable Apr 3 09:45:47 NAS-UNRAID nmbd[31019]: [2021/04/03 09:45:47.313754, 0] ../../source3/libsmb/nmblib.c:922(send_udp) Apr 3 09:45:47 NAS-UNRAID nmbd[31019]: Packet send failed to 172.17.255.255(138) ERRNO=Network is unreachable Apr 3 09:45:47 NAS-UNRAID nmbd[31019]: [2021/04/03 09:45:47.313946, 0] ../../source3/libsmb/nmblib.c:922(send_udp) Apr 3 09:45:47 NAS-UNRAID nmbd[31019]: Packet send failed to 192.168.122.255(138) ERRNO=Network is unreachable Apr 3 09:45:47 NAS-UNRAID nmbd[31019]: [2021/04/03 09:45:47.314035, 0] ../../source3/libsmb/nmblib.c:922(send_udp) Apr 3 09:45:47 NAS-UNRAID nmbd[31019]: Packet send failed to 192.168.122.255(138) ERRNO=Network is unreachable Apr 3 09:45:47 NAS-UNRAID wsdd[31082]: udp_send: Failed to send udp packet with Network is unreachable Apr 3 09:45:47 NAS-UNRAID wsdd[31082]: udp_send: Failed to send udp packet with No such device Apr 3 09:45:47 NAS-UNRAID wsdd[31082]: udp_send: Failed to send udp packet with Network is unreachable Apr 3 09:45:47 NAS-UNRAID wsdd[31082]: Failed to send bye with Network is unreachable Apr 3 09:45:47 NAS-UNRAID winbindd[31146]: [2021/04/03 09:45:47.319313, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler) Apr 3 09:45:47 NAS-UNRAID winbindd[31146]: Got sig[15] terminate (is_parent=1) Apr 3 09:45:47 NAS-UNRAID winbindd[31152]: [2021/04/03 09:45:47.320034, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler) Apr 3 09:45:47 NAS-UNRAID winbindd[31152]: Got sig[15] terminate (is_parent=0) Apr 3 09:45:47 NAS-UNRAID winbindd[32132]: [2021/04/03 09:45:47.320421, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler) Apr 3 09:45:47 NAS-UNRAID winbindd[32132]: Got sig[15] terminate (is_parent=0) Apr 3 09:45:47 NAS-UNRAID emhttpd: shcmd (19109): rm -f /etc/avahi/services/smb.service Apr 3 09:45:47 NAS-UNRAID avahi-daemon[7215]: Files changed, reloading. Apr 3 09:45:47 NAS-UNRAID avahi-daemon[7215]: Service group file /services/smb.service vanished, removing services. Apr 3 09:45:47 NAS-UNRAID emhttpd: Stopping mover... Apr 3 09:45:47 NAS-UNRAID emhttpd: shcmd (19111): /usr/local/sbin/mover stop Apr 3 09:45:47 NAS-UNRAID root: mover: not running Apr 3 09:45:47 NAS-UNRAID emhttpd: Sync filesystems... Apr 3 09:45:47 NAS-UNRAID emhttpd: shcmd (19112): sync Apr 3 09:45:47 NAS-UNRAID emhttpd: shcmd (19113): umount /mnt/user0 Apr 3 09:45:49 NAS-UNRAID emhttpd: shcmd (19114): rmdir /mnt/user0 Apr 3 09:45:49 NAS-UNRAID emhttpd: shcmd (19115): umount /mnt/user Apr 3 09:45:49 NAS-UNRAID root: umount: /mnt/user: target is busy. Apr 3 09:45:49 NAS-UNRAID emhttpd: shcmd (19115): exit status: 32 Apr 3 09:45:49 NAS-UNRAID emhttpd: shcmd (19116): rmdir /mnt/user Apr 3 09:45:49 NAS-UNRAID root: rmdir: failed to remove '/mnt/user': Device or resource busy Apr 3 09:45:49 NAS-UNRAID emhttpd: shcmd (19116): exit status: 1 Apr 3 09:45:50 NAS-UNRAID emhttpd: shcmd (19118): /usr/local/sbin/update_cron Apr 3 09:45:50 NAS-UNRAID emhttpd: Retry unmounting user share(s)... Apr 3 09:45:55 NAS-UNRAID emhttpd: shcmd (19119): umount /mnt/user Apr 3 09:45:55 NAS-UNRAID root: umount: /mnt/user: target is busy. Apr 3 09:45:55 NAS-UNRAID emhttpd: shcmd (19119): exit status: 32 Apr 3 09:45:55 NAS-UNRAID emhttpd: shcmd (19120): rmdir /mnt/user Apr 3 09:45:55 NAS-UNRAID root: rmdir: failed to remove '/mnt/user': Device or resource busy Apr 3 09:45:55 NAS-UNRAID emhttpd: shcmd (19120): exit status: 1 Apr 3 09:45:55 NAS-UNRAID emhttpd: shcmd (19122): /usr/local/sbin/update_c Quote Link to comment
DivideBy0 Posted April 4, 2021 Author Share Posted April 4, 2021 3 minutes ago, Squid said: 20210403. Looks like you had a shell open with the system on a cwd to /mnt/user/.... That prevents the system from unmounting the drives since it's in use. Maybe install Dynamix Stop Shell to help alleviate that. LOL, note to self. No shells open during reboot I mean unRaid is smart enough to kill existing shells right? Just a simple line in run level 6 will do Quote Link to comment
DivideBy0 Posted April 4, 2021 Author Share Posted April 4, 2021 Well THANKS you Sir as always. Team work Quote Link to comment
Recommended Posts
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.