December 31, 201015 yr Author It appears you've got some type of disk error happening. At least open the syslog and see what drive is having the errors. Delete the old syslog to save a new one. Worst case is you have to give up and you have likely lost the data on disk9 and disk13. It would be really good to know if there is another disk having trouble right now. Peter There is NO syslog for today. The last syslog is 12-20> Does it only create the log on power down or was it unable to create one because the flash was full?
January 1, 201115 yr It appears you've got some type of disk error happening. At least open the syslog and see what drive is having the errors. Delete the old syslog to save a new one. Worst case is you have to give up and you have likely lost the data on disk9 and disk13. It would be really good to know if there is another disk having trouble right now. Peter There is NO syslog for today. The last syslog is 12-20> Does it only create the log on power down or was it unable to create one because the flash was full? The syslog is in /var/log/syslog it is not saved to the flash drive unless you save it, or it is is saved for you by the add-on powerdown script.
January 1, 201115 yr Author The syslog is in /var/log/syslog it is not saved to the flash drive unless you save it, or it is is saved for you by the add-on powerdown script. Joe what do I do now (syslog seems unimportant since disk9 is obviously the problem)? Let it contenue to "rebuild" or Cancel? What are my future options (reading my previos post questions)?
January 1, 201115 yr William, Don't panic. More than one unRAID user has managed to reclaim files that seemed to be lost. Let the rebuild continue if it is still working. Post a syslog when you get a chance.
January 1, 201115 yr Author Let it finish and the results are: disk13 shows as blank (no (itunes) files, folders, no Music Share and all free space) but after hitting Stop (more on that below) now shows as unformatted and says unformatted disk(s) present with the Format button but the ball is still green. disk9 is red ball (no temp reading and 237,356,349 errors) but I was able to look at the files on it and took screen shots for future reference. Does this mean that the files are safely in parity and when I change out the disk it will rebuild them (FAT CHANCE)? When I try to copy a file it says "The operation can't be completed because an unexpected error occurred (error code -51)". This is probably an OS X message code and I'm just seeing the (corrupt?) folder system but the files are gone. Can't Stop unRAID (take array off-line) as before. When I hit Stop it stay Started and if disks are spun down it spins them all up. Also Power Down script doesn't work when I use the Power button on my unRAID. On the Consol screen I get the following messages repeated for each disk: unmount: /mnt/disk#: device is busy rmdir: /mnt/disk#: Device or resource is busy Last Line is: HDIO_DRIVE_CMD(standby) failed: Input/output busy Was going to post syslog but can't find /var/log/syslog. EDIT search WIKI and found instructions. At console I typed cp /var/log/syslog /boot and it makes a file named syslog that is listed as a program file (Unix Executable File)and is 1.9GB in size. No way to post this. Now my flash drive is completely full (again) with 0KB space available. Do I need to delete this file?
January 1, 201115 yr Let it finish and the results are: disk13 shows as blank (no (itunes) files, folders, no Music Share and all free space) but after hitting Stop (more on that below) now shows as unformatted and says unformatted disk(s) present with the Format button but the ball is still green. disk9 is red ball (no temp reading and 237,356,349 errors) but I was able to look at the files on it and took screen shots for future reference. Does this mean that the files are safely in parity and when I change out the disk it will rebuild them (FAT CHANCE)? When I try to copy a file it says "The operation can't be completed because an unexpected error occurred (error code -51)". This is probably an OS X message code and I'm just seeing the (corrupt?) folder system but the files are gone. Can't Stop unRAID (take array off-line) as before. When I hit Stop it stay Started and if disks are spun down it spins them all up. Also Power Down script doesn't work when I use the Power button on my unRAID. On the Consol screen I get the following messages repeated for each disk: unmount: /mnt/disk#: device is busy rmdir: /mnt/disk#: Device or resource is busy Last Line is: HDIO_DRIVE_CMD(standby) failed: Input/output busy Was going to post syslog but can't find /var/log/syslog. EDIT search WIKI and found instructions. At console I typed cp /var/log/syslog /boot and it makes a file named syslog that is listed as a program file (Unix Executable File)and is 1.9GB in size. No way to post this. Now my flash drive is completely full (again) with 0KB space available. Do I need to delete this file? Yes, you can delete the file on the flash drive. It is just massive amounts of repeated errors. Type rm /boot/syslog to remove it. The disk that is "busy" is not able to be un-mounted. It is because a file on it is open, OR it is because you've changed directory onto it while looking for files on it, or you started a process while cd'd to it and it is the current directory for that process. You'll never be able to stop unRAID if it has disks that are busy. (not with the unRAID "Stop" button.) If you see those messages in the system log you'll need to identify and terminate the processes keeping the disk busy before the array will stop. The easiest way to identify those processes is to type: fuser -mv /mnt/disk* /mnt/user/* Joe L.
January 1, 201115 yr Author ...The easiest way to identify those processes is to type: fuser -mv /mnt/disk* /mnt/user/* Joe L. It says for each disk (and the numbers are different): /mnt/disk#: root 5147..c.. cache_dirs root 32414..c.. sleep
January 1, 201115 yr ...The easiest way to identify those processes is to type: fuser -mv /mnt/disk* /mnt/user/* Joe L. It says for each disk (and the numbers are different): /mnt/disk#: root 5147..c.. cache_dirs root 32414..c.. sleep cache_dirs will usually stop itself when it sees the messages in the syslog describing the attempt to un-mount the disk. It has a "sleeping process" whose "current" directory is on each disk. It monitors the system log and terminates those processes when you attempt to stop the array. The "minbers" are the process IDs. (unique per running process on the server) You can simply invoke cache_dirs -q to remove the lock file being monitored by cache_dirs ifit does not stop itself.
January 1, 201115 yr Author ...You can simply invoke cache_dirs -q to remove the lock file being monitored by cache_dirs ifit does not stop itself. Joe, I get command not found. Believe I'm in the root directory [email protected] first change directory to where you put the cache_dirs program or invoke it with the full path. If you want, you can just remove the file it uses as a lock-file and cache_dirs will shut down as soon as it notices it has been removed (that's what the -q option does anyway) To remove the lock-file, type: rm /var/lock/cache_dirs.LCK quote] Also here is what I want to do since I have been down almost 3 weeks. I give up on disk9 and disk13. It's a lost cause and no use waisting more time and stress on trying to walk on water. I just want to get the unRAID working again and will re-rip all my music and about 30 Blu-ray's (will lose some recorded HDTV but...). So is this what I do: 1. Hit Format (again) for disk13? How and why did it become unformatted?It is shown as unformatted because it cannot be mounted. That might be because the file-system on it is corrupted. 2. Remove old disk7 and replace with new HD and let it go through a fruitless rebuild? 3. Delete any corrupt file/folders related to disk9 (if they show up)? 4. Please tell me the easiest way to get this thing up and running correctly again before I go postal and chunk it out the window. Easiest way. (see if you think it might work) Copy any data you can off of any "defective" drive to working drives. Stop the array. Un-assign ANY and ALL drives that are showing as un-formatted or where you suspect the files are corrupted, or where the physical disk might be bad. Leave assigned the parity drive, and any other data drives that are working. Set a new initial disk configuration based on the assigned and WORKING drives. This would be the "initconfig" command on recent versions of unRAID, the button labeled as "restore" on older ones such as yours. this time don't force any drive to be invalid as all the drives should be working. Start the array and let unRAID calculate parity. Let it complete. Then, for each data drive you un-assigned, we can work on it with the remainder of your array online. That can be in a new thread if you like. We can attempt to recover to some of your files on the drive with the corruption, or wipe them and start with them new if you fell the drive itself is not physically defective. Joe L.
January 1, 201115 yr Author What happen to my post? It looks like it's been on my unRAID . Did you edit it Joe? It's very confusing looking and not what I typed with added info. It looks like you edited and answered my questions in places with quotes and no quotes. Hard to tell what I wrote and what you wrote. I think this is the way it should look. I get command not found. Believe I'm in the root directory Root@Tower. Then first change directory to where you put the cache_dirs program or invoke it with the full path. If you want, you can just remove the file it uses as a lock-file and cache_dirs will shut down as soon as it notices it has been removed (that's what the -q option does anyway) To remove the lock-file, type: rm /var/lock/cache_dirs.LCK So is this what I do: 1. Hit Format (again) for disk13? How and why did it become unformatted? It is shown as unformatted because it cannot be mounted. That might be because the file-system on it is corrupted. 2. Remove old disk7 and replace with new HD and let it go through a fruitless rebuild? 3. Delete any corrupt file/folders related to disk9 (if they show up)? 4. Please tell me the easiest way to get this thing up and running correctly again before I go postal and chunk it out the window. Easiest way. (see if you think it might work) Copy any data you can off of any "defective" drive to working drives. Stop the array. Un-assign ANY and ALL drives that are showing as un-formatted or where you suspect the files are corrupted, or where the physical disk might be bad. Leave assigned the parity drive, and any other data drives that are working. Set a new initial disk configuration based on the assigned and WORKING drives. This would be the "initconfig" command on recent versions of unRAID, the button labeled as "restore" on older ones such as yours. this time don't force any drive to be invalid as all the drives should be working. Start the array and let unRAID calculate parity. Let it complete. Then, for each data drive you un-assigned, we can work on it with the remainder of your array online. That can be in a new thread if you like. We can attempt to recover to some of your files on the drive with the corruption, or wipe them and start with them new if you fell the drive itself is not physically defective. Joe L.
January 1, 201115 yr Author Then first change directory to where you put the cache_dirs program or invoke it with the full path. If you want, you can just remove the file it uses as a lock-file and cache_dirs will shut down as soon as it notices it has been removed (that's what the -q option does anyway) To remove the lock-file, type: rm /var/lock/cache_dirs.LCK I don't know or remember anything about installing or putting the cache_dirs program on my unRAID (it's something I did?). I ran rm /var/lock/cache_dirs.LCK and the unRAID will now Stop. Is it gone for good? Easiest way. (see if you think it might work) Copy any data you can off of any "defective" drive to working drives. Stop the array. Un-assign ANY and ALL drives that are showing as un-formatted or where you suspect the files are corrupted, or where the physical disk might be bad. Leave assigned the parity drive, and any other data drives that are working. Set a new initial disk configuration based on the assigned and WORKING drives. This would be the "initconfig" command on recent versions of unRAID, the button labeled as "restore" on older ones such as yours. this time don't force any drive to be invalid as all the drives should be working. Start the array and let unRAID calculate parity. Let it complete. Then, for each data drive you un-assigned, we can work on it with the remainder of your array online. That can be in a new thread if you like. We can attempt to recover to some of your files on the drive with the corruption, or wipe them and start with them new if you fell the drive itself is not physically defective. Joe L. So in a nut shell: Un-assign disk9 and disk13 hit Restore (this won't delete all my Shares?) and then hit Start and it will do a parity check and set array to having 11 dives instead of 13 I have now. Then after it's finished and stable, cut off unRAID, remove old disk9 and replace with new. Cut on unRAID add back the disk9 and disk 13 as new drives increasing the array from 11 to 13 drives.
January 1, 201115 yr Yes, just take disk9 and disk13 out of the array and hit Restore. Start the array and let the parity build complete. Do at least one more Parity Check to confirm the rest of your system is working OK. Then, you can add the 2 new disks again. I would actually suggest you look up the preclear script and run that on the new disks before installing them. It will perform a very good burn-in on the drives. Peter
January 1, 201115 yr Then first change directory to where you put the cache_dirs program or invoke it with the full path. If you want, you can just remove the file it uses as a lock-file and cache_dirs will shut down as soon as it notices it has been removed (that's what the -q option does anyway) To remove the lock-file, type: rm /var/lock/cache_dirs.LCK I don't know or remember anything about installing or putting the cache_dirs program on my unRAID (it's something I did?). I ran rm /var/lock/cache_dirs.LCK and the unRAID will now Stop. Is it gone for good?You did install it, and there is probably a lin in your config/go script to start it every time you reboot. Therefore, it is not "gone for good" but gone until you reboot (unless you stop it from being started) Easiest way. (see if you think it might work) Copy any data you can off of any "defective" drive to working drives. Stop the array. Un-assign ANY and ALL drives that are showing as un-formatted or where you suspect the files are corrupted, or where the physical disk might be bad. Leave assigned the parity drive, and any other data drives that are working. Set a new initial disk configuration based on the assigned and WORKING drives. This would be the "initconfig" command on recent versions of unRAID, the button labeled as "restore" on older ones such as yours. this time don't force any drive to be invalid as all the drives should be working. Start the array and let unRAID calculate parity. Let it complete. Then, for each data drive you un-assigned, we can work on it with the remainder of your array online. That can be in a new thread if you like. We can attempt to recover to some of your files on the drive with the corruption, or wipe them and start with them new if you fell the drive itself is not physically defective. Joe L. So in a nut shell: Un-assign disk9 and disk13 hit Restore (this won't delete all my Shares?) and then hit Start and it will do a parity check and set array to having 11 dives instead of 13 I have now. Then after it's finished and stable, cut off unRAID, remove old disk9 and replace with new. Cut on unRAID add back the disk9 and disk 13 as new drives increasing the array from 11 to 13 drives. You can still use some file-system repair tools on disk 9 and 13 once they are no longer part of the array to attempt to recover what is on them before you re-allocate them. (if you care to try) You'll just need to reference the partitions by their native partition name at that point. First, let's get parity re-established on the other drives.
January 3, 201115 yr Author Up and running. Happy to be back on track, sad that ripping all my CD is a real PItA but.... Just a quick ? Will look at updating to 4.5 but must devote all spare time to CD & BD ripping for now (and about the next 4 to 8 weeks). Thanks
Archived
This topic is now archived and is closed to further replies.