[6.8.3] Server refused to reboot / services became unresponsive


MvL

4 posts in this topic Last Reply

Recommended Posts

Hi,

 

I had some problems yesterday with my unRAID server. I think it started when mounting a NFS share via unassigned devices for some reason it failed.

 

Quote

Mar 27 21:10:47 Tower unassigned.devices: Mount NFS command: /sbin/mount -t nfs -o rw,hard,timeo=600,retrans=10 '192.168.100.20:/volume1/downloads' '/mnt/disks/192.168.100.20_downloads'
Mar 27 21:10:47 Tower rpcbind[25869]: connect from 127.0.0.1 to getport/addr(status)
Mar 27 21:10:47 Tower unassigned.devices: NFS mount failed: mount.nfs: access denied by server while mounting 192.168.100.20:/volume1/downloads .
Mar 27 21:10:47 Tower unassigned.devices: Mount of '192.168.100.20:/volume1/downloads' failed. Error message: 'mount.nfs: access denied by server while mounting 192.168.100.20:/volume1/downloads '.
Mar 27 21:11:14 Tower unassigned.devices: Mount NFS command: /sbin/mount -t nfs -o rw,hard,timeo=600,retrans=10 '192.168.100.20:/volume1/downloads' '/mnt/disks/192.168.100.20_downloads'
Mar 27 21:11:14 Tower rpcbind[26320]: connect from 127.0.0.1 to getport/addr(status)
Mar 27 21:12:08 Tower unassigned.devices: Mount NFS command: /sbin/mount -t nfs -o rw,hard,timeo=600,retrans=10 '192.168.100.20:/volume1/downloads' '/mnt/disks/192.168.100.20_downloads'
Mar 27 21:12:08 Tower rpcbind[27009]: connect from 127.0.0.1 to getport/addr(status)
Mar 27 21:12:53 Tower unassigned.devices: Mount NFS command: /sbin/mount -t nfs -o rw,hard,timeo=600,retrans=10 '192.168.100.20:/volume1/downloads' '/mnt/disks/192.168.100.20_downloads'
Mar 27 21:12:53 Tower rpcbind[27602]: connect from 127.0.0.1 to getport/addr(status)
Mar 27 21:13:05 Tower unassigned.devices: Removing configuration '192.168.100.20:/volume1/downloads'.
Mar 27 21:16:00 Tower sshd[26889]: Received disconnect from 192.168.100.103 port 49414:11: disconnected by user
Mar 27 21:16:00 Tower sshd[26889]: Disconnected from user root 192.168.100.103 port 49414
Mar 27 21:16:00 Tower sshd[26889]: syslogin_perform_logout: logout() returned an error
Mar 27 21:16:14 Tower sshd[29323]: Accepted password for root from 192.168.100.103 port 49931 ssh2
Mar 27 21:26:08 Tower sshd[29323]: Received disconnect from 192.168.100.103 port 49931:11: disconnected by user
Mar 27 21:26:08 Tower sshd[29323]: Disconnected from user root 192.168.100.103 port 49931
Mar 27 21:26:27 Tower kernel: mdcmd (121): nocheck cancel

 

Then I decided to restart the server because some services became unresponsive.  Then the whole server became unresponsive and doesn't want to reboot.

 

Quote

Mar 27 21:49:48 Tower root: /mnt/cache:          root     kernel mount /mnt/cache
Mar 27 21:49:48 Tower root: /mnt/disk1:          root     kernel mount /mnt/disk1
Mar 27 21:49:48 Tower root: /mnt/disk2:          root     kernel mount /mnt/disk2
Mar 27 21:49:48 Tower root: /mnt/disk21:         root     kernel mount /mnt/disk21
Mar 27 21:49:48 Tower root: /mnt/disk22:         root     kernel mount /mnt/disk22
Mar 27 21:49:48 Tower root: /mnt/disk4:          root     kernel mount /mnt/disk4
Mar 27 21:49:48 Tower root: /mnt/disk5:          root     kernel mount /mnt/disk5
Mar 27 21:49:48 Tower root: /mnt/disk6:          root     kernel mount /mnt/disk6
Mar 27 21:49:48 Tower root: /mnt/disk7:          root     kernel mount /mnt/disk7
Mar 27 21:49:48 Tower root: /mnt/disk8:          root     kernel mount /mnt/disk8
Mar 27 21:49:48 Tower root: /mnt/disk9:          root     kernel mount /mnt/disk9
Mar 27 21:49:48 Tower root: /mnt/disks:          root     kernel mount /mnt/disks
Mar 27 21:49:48 Tower root: /mnt/user:           root     kernel mount /mnt/user
Mar 27 21:49:48 Tower root: /mnt/user0:          root     kernel mount /mnt/user0
Mar 27 21:49:48 Tower root: Active pids left on /dev/md*
Mar 27 21:49:48 Tower root:                      USER        PID ACCESS COMMAND
Mar 27 21:49:48 Tower root: /dev/md1:            root     kernel mount /mnt/disk1
Mar 27 21:49:48 Tower root: /dev/md2:            root     kernel mount /mnt/disk2
Mar 27 21:49:48 Tower root: /dev/md21:           root     kernel mount /mnt/disk21
Mar 27 21:49:48 Tower root: /dev/md22:           root     kernel mount /mnt/disk22
Mar 27 21:49:48 Tower root: /dev/md4:            root     kernel mount /mnt/disk4
Mar 27 21:49:48 Tower root: /dev/md5:            root     kernel mount /mnt/disk5
Mar 27 21:49:48 Tower root: /dev/md6:            root     kernel mount /mnt/disk6
Mar 27 21:49:48 Tower root: /dev/md7:            root     kernel mount /mnt/disk7
Mar 27 21:49:48 Tower root: /dev/md8:            root     kernel mount /mnt/disk8
Mar 27 21:49:48 Tower root: /dev/md9:            root     kernel mount /mnt/disk9
Mar 27 21:49:48 Tower root: Generating diagnostics...

 

I think the "Mar 27 21:49:48 Tower root: Active pids left on /dev/md*" was the reason why the server didn't want to reboot, but I like some assistance from some more experienced person! I like to prevent this in the future.

 

I also attached the diagnostic file.

 

 

 

 

tower-diagnostics-20200327-2149.zip

Edited by MvL
Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.