February 21, 201313 yr I had a powerfailure yesterday. After I powered the server back on I did the following: Ran a parity check = no errors Disabled all plugins rebooted from unraid main menu I am left with the array starting but no shares, the disks or disk? isnt mounting. The message at the bottom of my screen says: "Spinning up all drives...Start array...Mounting disks..." And just sits there. I read that after an event like I had the drives can take a while to spin up. I saw 20 - 30 minutes or longer. I left it for hours and it didnt mount. Any suggestions? I attached my log. I dont really know what to look for that isnt a glaring error in red. Please let me know if you would like to see anything else. Thanks
February 21, 201313 yr I had a powerfailure yesterday. After I powered the server back on I did the following: Ran a parity check = no errors Disabled all plugins rebooted from unraid main menu I am left with the array starting but no shares, the disks or disk? isnt mounting. The message at the bottom of my screen says: "Spinning up all drives...Start array...Mounting disks..." And just sits there. I read that after an event like I had the drives can take a while to spin up. I saw 20 - 30 minutes or longer. I left it for hours and it didnt mount. Any suggestions? I attached my log. I dont really know what to look for that isnt a glaring error in red. Please let me know if you would like to see anything else. Thanks You still have add-ons being loaded. Odds are one or more are keeping the array from starting properly. as an example: 10:27:55 nas sudo: root : TTY=console ; PWD=/tmp ; USER=nobody ; COMMAND=/usr/bin/python yes/CouchPotato.py --daemon --config_file /boot/config/plugins/couchpotato_v2/settings.conf --pid_file /var/run/couchpotato_v2/couchpotato_v2.pid Joe L.
February 21, 201313 yr And since that used to work I would advise giving your usb drive a chkdsk from windows... It might have gotten damaged in the power failure. If that is ok then just start without plugins and add them one-by-one to see where the issue lies.
Archived
This topic is now archived and is closed to further replies.