tillkrueger Posted October 28, 2010 Share Posted October 28, 2010 something just went wrong (unRAID 5 beta2)... during a backup operation to the unRAID, a file stopped copying, and trying to look at the share i was copying to in the Finder showed that it did not allow me to look at the contents of the drive, or mount any other of the drives...i tried to stop the array, so that i could do a clean reboot, but it just endlessly shows a "Unmounting disks...Retry unmounting disk share(s)..." cycle...trying to ssh into the server gets me a "ssh: connect to host 192.168.2.201 port 22: Connection refused" message...now what? i am about to go on a 8 month USA teaching assignment, and had to back terrabytes of data to it with only 3 days left to do all this...in order to even make that possible, i had to take the parity drive out of the equation to allow for much faster copying...so now i am afraid to do anything that could harm the array. anybody has some advice? Link to comment
Joe L. Posted October 28, 2010 Share Posted October 28, 2010 A disk can not be un-mounted if it is "busy" unRAId, if you use its interface to stop the array, will wait for all disks to not be busy before stopping the array. A disk is busy if a file on it is open for reading or writing by a program OR if a directory on it is the current working directory for any process. If you log in via telnet you can usually kill the process holding the disk busy by typing: fuser -k /mnt/disk1 fuser -k /mnt/disk2 fuser -k /mnt/disk3 etc... Link to comment
tillkrueger Posted October 28, 2010 Author Share Posted October 28, 2010 Joe, what would we do without your knowledge and generosity? not that i'm quite there yet, but i did what you said, and unmounted each disk number one by one...all disks were already unmounted, except for disk3 (which unmounted properly it seems), and disk6, which posted the following string to the terminal "/mnt/disk6: 5778c 5940c 5941c 5942c 5943c 5944c"...what does that mean? am i now "safe" to hard-reboot the unRAID (pushing in the reset button for 5-10secs or turning the PSU off and on)? EDIT 1: well, i issued the "reboot" command, and it's doing it now...crossing my fingers. EDIT 2: aha! i'm back up and running...what a freakin' relief!! Joe, if i could, i'd give you a big ole' bear-hug...you've saved my a** and that of others here so many times, there should be a "God Status" for people like you. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.