Confession - I did a rather stupid thing and accidentally disconnected an external USB drive from my unraid and stop / started the array - This caused the array to think the drive is missing, then went to new device.

 

In turn the above caused the array to go into rebuilding (which i can deal with although seriously annoying as it will take 5 days to rebuild - 10tb array @20mbps (can this be sped up?)), but during this the shares have gone to "no exportable shares available", I'm assuming I have to wait for the array to rebuild before the shares will be available (and as a result my docker instances / VMWare spin up).

 

 

Edited December 17, 20196 yr by Uk_tomcat_fan
update to speeds

Post your diagnostics

Attached - Anonymized

tower-diagnostics-20191217-1423.zip

Wondering if there are any updates / suggestions for this

First off, massive amounts of login attempts from around the world.

 

You should take your server out of the DMZ or stop forwarding ssh ports.  Use a reverse proxy / VPN if you need to access your server remotely

 

ec 17 04:39:19 Tower in.telnetd[19758]: connect from 14.55.142.160 (14.55.142.160)
Dec 17 04:39:21 Tower in.telnetd[19828]: connect from 186.179.253.232 (186.179.253.232)
Dec 17 04:39:22 Tower sshd[19793]: Failed password for root from 222.186.175.163 port 24522 ssh2
Dec 17 04:39:24 Tower sshd[19793]: Received disconnect from 222.186.175.163 port 24522:11:  [preauth]
Dec 17 04:39:24 Tower sshd[19793]: Disconnected from authenticating user root 222.186.175.163 port 24522 [preauth]
Dec 17 04:39:33 Tower sshd[20197]: Invalid user bruscino from 178.62.90.135 port 48534
Dec 17 04:39:33 Tower sshd[20197]: error: Could not get shadow information for NOUSER
Dec 17 04:39:33 Tower sshd[20197]: Failed password for invalid user bruscino from 178.62.90.135 port 48534 ssh2
Dec 17 04:39:33 Tower sshd[20197]: Received disconnect from 178.62.90.135 port 48534:11: Bye Bye [preauth]
Dec 17 04:39:33 Tower sshd[20197]: Disconnected from invalid user bruscino 178.62.90.135 port 48534 [preauth]
Dec 17 04:39:34 Tower in.telnetd[20242]: connect from 68.190.218.211 (68.190.218.211)
Dec 17 04:39:35 Tower in.telnetd[20269]: connect from 170.238.126.136 (170.238.126.136)
Dec 17 04:39:39 Tower sshd[20372]: Invalid user azzuolo from 45.55.177.170 port 45122
Dec 17 04:39:39 Tower sshd[20372]: error: Could not get shadow information for NOUSER
Dec 17 04:39:39 Tower sshd[20372]: Failed password for invalid user azzuolo from 45.55.177.170 port 45122 ssh2
Dec 17 04:39:39 Tower sshd[20372]: Received disconnect from 45.55.177.170 port 45122:11: Bye Bye [preauth]
Dec 17 04:39:39 Tower sshd[20372]: Disconnected from invalid user azzuolo 45.55.177.170 port 45122 [preauth]
Dec 17 04:39:40 Tower in.telnetd[20440]: connect from 14.55.142.160 (14.55.142.160)
Dec 17 04:39:42 Tower in.telnetd[20510]: connect from 186.179.253.232 (186.179.253.232)
Dec 17 04:39:47 Tower sshd[20611]: Failed password for root from 112.85.42.189 port 16628 ssh2
### [PREVIOUS LINE REPEATED 2 TIMES] ###
Dec 17 04:39:48 Tower sshd[20611]: Received disconnect from 112.85.42.189 port 16628:11:  [preauth]
Dec 17 04:39:48 Tower sshd[20611]: Disconnected from authenticating user root 112.85.42.189 port 16628 [preauth]
Dec 17 04:39:53 Tower sshd[20846]: Failed password for root from 51.15.87.74 port 44280 ssh2
Dec 17 04:39:53 Tower sshd[20846]: Received disconnect from 51.15.87.74 port 44280:11: Bye Bye [preauth]
Dec 17 04:39:53 Tower sshd[20846]: Disconnected from authenticating user root 51.15.87.74 port 44280 [preauth]
Dec 17 04:39:55 Tower in.telnetd[20916]: connect from 170.238.126.136 (170.238.126.136)
Dec 17 04:39:55 Tower in.telnetd[20950]: connect from 68.190.218.211 (68.190.218.211)

The actual problem though is that it looks like you've got file system corruption on disk 1.  You need to https://wiki.unraid.net/Check_Disk_Filesystems

Thanks, I took it out of DMZ once i grabbed the logs whilst i was out the house.

 

I will take a look at the link shortly.

looks like I cannot stop the array and drop into maintenance mode, is it safe to reboot the machine whilst its doing the rebuild?

 

You'll have to start it over