Jump to content
LAST CALL on the Unraid Summer Sale! 😎 ⌛ ×

(Solved) Unraid stuck at mounting drives


chuffs97

Recommended Posts

Hi all,

 

My unraid box seems to just stop when I try to start the array. My specs are as follows: i5-4670, 16GB RAM, 128GB Cache and a 4TB Seagate Ironwolf.

 

I've attempted to run the xfx_repair command on disk 1, as per this thread;

 

I've attached my diagnostics too. Any help would be greatly appreciated. Thanks in advance :)

tower-diagnostics-20180622-1851.zip

 

EDIT: Thanks for helping me. The issue was one of my scripts added through the user scripts plugin was causing it to hang at mounting. Disabled the autostart of scripts and it mounted fine.

Link to comment
10 minutes ago, johnnie.black said:

 

So I restarted my unraid box, and started the array in maintenance mode. Logged in via bash on windows and ssh and ran "xfx_repair -v /dev/md1', it seemed to complete without any errors (Screenshot of terminal). But then when I took the array offline and attempted to start it normally, it still seems to hanging at mounting disks.

Link to comment

Disk1 mounted normally now, but there's an NGINX error, so try rebooting.

 

Jun 22 22:18:31 Tower nginx: 2018/06/22 22:18:31 [error] 3107#3107: *41 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.119, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "tower", referrer: "http://tower/Main"

 

 

 

Link to comment
9 minutes ago, johnnie.black said:

Disk1 mounted normally now, but there's a NGINX error, so try rebooting.

 


Jun 22 22:18:31 Tower nginx: 2018/06/22 22:18:31 [error] 3107#3107: *41 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.119, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "tower", referrer: "http://tower/Main"

 

 

Rebooted the server, and then tried to start the array. It's been 5 mins and hasn't gotten past mounting the disks... I guess upload my diagnostics again?

 

also 192.168.0.119 is my desktop PC.

 

 

tower-diagnostics-20180622-2243.zip

Link to comment

No errors, everything looks normal to me, and all disk are mounted, maybe someone else has an idea.:

 

Filesystem      Size  Used Avail Use% Mounted on
rootfs          7.8G  757M  7.0G  10% /
tmpfs            32M  176K   32M   1% /run
devtmpfs        7.8G     0  7.8G   0% /dev
tmpfs           7.9G     0  7.9G   0% /dev/shm
cgroup_root     8.0M     0  8.0M   0% /sys/fs/cgroup
tmpfs           128M  1.7M  127M   2% /var/log
/dev/sda1        15G  373M   15G   3% /boot
/dev/loop0      7.5M  7.5M     0 100% /lib/modules
/dev/loop1      4.5M  4.5M     0 100% /lib/firmware
/dev/md1        3.7T  2.2T  1.5T  61% /mnt/disk1
/dev/sdb1       120G   37G   83G  31% /mnt/cache
shfs            3.7T  2.2T  1.5T  61% /mnt/user0
shfs            3.8T  2.3T  1.6T  60% /mnt/user

 

Link to comment

You have the user.scripts plugin installed... is there something custom running there that might be causing this?  You could reboot and select 'safe mode' to boot and that would prevent all installed plugins from loading.

 

Edit: Yes, it looks like it's hung up on this user script: /tmp/user.scripts/tmpScripts/Deluge_Collector/script

Link to comment
19 hours ago, eschultz said:

You have the user.scripts plugin installed... is there something custom running there that might be causing this?  You could reboot and select 'safe mode' to boot and that would prevent all installed plugins from loading.

 

Edit: Yes, it looks like it's hung up on this user script: /tmp/user.scripts/tmpScripts/Deluge_Collector/script

 

That was the issue. I disabled the schedule for the "Deluge_Collector" script and it mounted the array and started services properly. 

 

Any idea why that would have caused it to hang at mounting disks? Where did you find that in the logs?

 

Thank you so much for your help :)

Link to comment

If the script never finishes (or takes an hour to complete), then the array startup procedure doesn't finish for the duration

 

You should be able to run your script if you choose as something like this via user scripts to spawn a background process instead

 

echo "/pathTo/Script/script.sh" | at NOW -m

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...