May 26, 201016 yr It is giving you the correct advice... Now, run it with the --rebuild-tree option. It might take a while for a large disk, so don't expect it to finish instantly... It just depends on how many files and directories are involved. Joe L.
May 27, 201016 yr Did you get the chance to run the "--rebuild-tree" yet? I'm hoping it resolves the problems in the syslog. It is very likely it will create a lost+found folder at the root of the drive. In it will be the files and directories it was able to recover. They will have numeric names, so you'll need to figure out what they were originally named and re-name them. Hopefully, there will be very little there and you'll be able to figure out what they are. From your screen shot, it looks like most of the disk has files on it, as there was not that much free space. Joe L.
May 27, 201016 yr it has been running for a couple hours now... at 20% I figured it would take a while, but I had no way to know how many files on your disk. Just let it run. It is doing what it can. As it is working fixing things, it is also keeping the parity disk in sync with the fixes, so you should be in pretty good shape once it is done. Depending on where you live, you might need to just let it work while you sleep (unless you really want to stay up all night and watch it) Joe L.
May 27, 201016 yr Author So this is done now. the --rebuild-tree finished I remounted the drive and it all seems good, I can see all my shares and get to all my data as far as I can tell. The Lost and found folder had two files, one of which was 2.6 gigs the other one was quite small. Thanks again for all your help.
May 27, 201016 yr So this is done now. the --rebuild-tree finished I remounted the drive and it all seems good, I can see all my shares and get to all my data as far as I can tell. The Lost and found folder had two files, one of which was 2.6 gigs the other one was quite small. Thanks again for all your help. The 2.6Gig one was probably a VOB or ISO The other could be anything. They could even be files you intended to delete. While it is fresh in your mind, it would not hurt to run reiserfsck --check on the other data drives in your array. Now... update to 4.5.4 so that darned button labeled as "restore" will not exist. (I'll stop pestering you to not press it, I promise... ) Then, all I'll have to do it to keep reminding you to not run the initconfig command when you are trying to get your array to start after a disk failure. Joe L.
Archived
This topic is now archived and is closed to further replies.