April 12, 201412 yr Author OK got it ... at the end it says Set flags in SB: Mount count: 1 Maximum mount count: 30 Last fsck run: Fri Apr 11 20:12:24 2014 Check interval in days: 180 Is this ok ? (y/n)[n]: y The fs may still be unconsistent. Run reiserfsck --check. I guess I should follow your pust bjp right? run this? reiserfsck –scan-whole-partition –rebuild-tree /dev/md1
April 12, 201412 yr Author Then I did this: root@Tower:~# reiserfsck –scan-whole-partition –rebuild-tree /dev/md1 Usage: reiserfsck [mode] [options] device Modes: --check consistency checking (default) --fix-fixable fix corruptions which can be fixed without --rebuild-tree --rebuild-sb super block checking and rebuilding if needed (may require --rebuild-tree afterwards) --rebuild-tree force fsck to rebuild filesystem from scratch (takes a long time) --clean-attributes clean garbage in reserved fields in StatDatas Options: -j | --journal device specify journal if relocated -B | --badblocks file file with list of all bad blocks on the fs -l | --logfile file make fsck to complain to specifed file -n | --nolog make fsck to not complain -z | --adjust-size fix file sizes to real size -q | --quiet no speed info -y | --yes no confirmations -f | --force force checking even if the file system is marked clean -V prints version and exits -a and -p some light-weight auto checks for bootup -r ignored Expert options: --no-journal-available do not open nor replay journal -S | --scan-whole-partition build tree of all blocks of the device root@Tower:~# What now?
April 12, 201412 yr Author based on this: Usage: reiserfsck [mode] [options] device should it be as follows? reiserfsck --rebuild-tree -S | --scan-whole-partition /dev/sdc1
April 12, 201412 yr Wasn't the command you tried to run ... reiserfsck –scan-whole-partition –rebuild-tree /dev/md1 So now I think you need to run .. reiserfsck –scan-whole-partition –rebuild-tree /dev/sdc1 This is not my specialty, I should not have answered. I know the device is /dev/sdc1 but not sure of the command line, but I think this is correct.
April 12, 201412 yr Author I ran both and got the same thing. check my previous post about the order as per the report it gives
April 12, 201412 yr How about ... reiserfsck –rebuild-tree -scan-whole-partition /dev/sdc1 (The -S | -scan-whole-partition means you enter one or the other)
April 12, 201412 yr Author How about ... reiserfsck –rebuild-tree -scan-whole-partition /dev/sdc1 (The -S | -scan-whole-partition means you enter one or the other) It does not work either
April 12, 201412 yr reiserfsck -–rebuild-tree -scan-whole-partition /dev/sdc1 or reiserfsck -–rebuild-tree --scan-whole-partition /dev/sdc1
April 12, 201412 yr Author reiserfsck -–rebuild-tree -scan-whole-partition /dev/sdc1 or reiserfsck -–rebuild-tree --scan-whole-partition /dev/sdc1 nada
April 12, 201412 yr Are you running this in a screen session? This thing is going to run forever if we can ever get it to work. If you run in a putty session it is going to time out and kill the process in the middle.
April 12, 201412 yr I don't know what syntax it is after. Here is the manpage i found. Seems the syntax I gave is correct (2nd form). http://www.novell.com/documentation/suse91/suselinux-adminguide/html/apd.html You could try ... reiserfsck --rebuild-tree -S /dev/sdc1
April 12, 201412 yr According to this site: http://www.cyberciti.biz/tips/repairing-reiserfs-file-system-with-reiserfsck.html The correct syntax would be: reiserfsck --scan-whole-partition --rebuild-tree /dev/sdc1
April 12, 201412 yr Author According to this site: http://www.cyberciti.biz/tips/repairing-reiserfs-file-system-with-reiserfsck.html The correct syntax would be: reiserfsck --scan-whole-partition --rebuild-tree /dev/sdc1 That worked Thank you
April 12, 201412 yr Author Could it be that it does not work from putty? I was doing it from putty before you warned me and entered the same exact syntax and it gave me the error...look root@Tower:~# reiserfsck --scan-whole-partition –-rebuild-tree /dev/sdc1 Usage: reiserfsck [mode] [options] device Modes: --check consistency checking (default) --fix-fixable fix corruptions which can be fixed without but now it is doing its job...lets cross fingers.....and toes....I will post the results tomorrow. Have a good night. Thank you all
April 12, 201412 yr When you check you should be able to do an "ls -la /dev/sdc1". My experience was that the drive was empty (I did my reiserfsck while the disk was still in the array). I was devastated. I don't remember if I rebooted or just stopped and started the array, but after that the disk was not empty. The root directory was a mess, with a bunch of randomly named files and subdirectories. Long series of random digits. Some of the files were huge. I looked in random directory after random directory at first finding junk but finally starting to see a few things that looked familiar. Most of my files were in one specific subdirectory, and I finally found that and it was intact. Many of the files were .zips and I ran integrity checks and they tested valid. Afterwards I copied everything I wanted to save off of that disk to another disk, and reformatted the recovered disk (a few days later) before adding it back to the array. If the command line is cumbersome (which it is), I might suggest putting this disk in the array's cache slot. This will let you access the disk over the network as //tower/cache. It will make it easier to hunt around. (Make sure you are in maintenance mode and that the mover script is not going to try to do anything with the files on the disk). You may run into security issues with 5.0. Not 100% sure. I would try it and you can always go back to the command line if the permissions restrict your ability to see the files. Putting it in the cache slot will not cause any writes to the disk. Let us know how it goes ...
April 12, 201412 yr Author OK, I have around 30 minutes only for today to work with this. reiserfsck is finished..... I stopped the array, re-assigned the disk as disk1 but... Blue dot next to it....next to START button, this is the wording: "Start will bring the array on-line, start Data-Rebuild, and then expand the file system (if possible)." How do I proceed? I do not want another parity running now..... Maintenance mode??? will not mount disks... Put it in the cache drive??? OMG dont scare me, I do not want any more trouble jeje What do I do?
April 12, 201412 yr OK, I have around 30 minutes only for today to work with this. reiserfsck is finished..... I stopped the array, re-assigned the disk as disk1 but... Blue dot next to it....next to START button, this is the wording: "Start will bring the array on-line, start Data-Rebuild, and then expand the file system (if possible)." How do I proceed? I do not want another parity running now..... Maintenance mode??? will not mount disks... Put it in the cache drive??? OMG dont scare me, I do not want any more trouble jeje What do I do? DO NOT START THE ARRAY!!!
April 12, 201412 yr OK, I have around 30 minutes only for today to work with this. reiserfsck is finished..... I stopped the array, re-assigned the disk as disk1 but... Blue dot next to it....next to START button, this is the wording: "Start will bring the array on-line, start Data-Rebuild, and then expand the file system (if possible)." How do I proceed? I do not want another parity running now..... Maintenance mode??? will not mount disks... Put it in the cache drive??? OMG dont scare me, I do not want any more trouble jeje What do I do? DO NOT START THE ARRAY!!! Did you read my post just before yours? If you start the array you will loose the recovery that you did. You should remove the drive from the array, and load it in the cache slot. But even in the cache slot you may not be able to see the files due to permission issues, so you may be stuck with the telnet interface to check things out initially.
April 12, 201412 yr You should remove the drive from the array, and load it in the cache slot. I wouldn't do that either. You do NOT want to put that drive back in your array UNTIL you've verified what's on it. It's interesting that UnRAID now wants to do a data rebuild. WHAT does it show for the status of all of your other drives? [As bjp999 already said, do NOT Start the array] If all the drives show Blue, it's not clear which drive UnRAID plans to re-build. Post a picture of what your Web GUI looks like now. Next, BEFORE even thinking about starting the array, I'd attach the drive in question to another PC and look at what it now shows for its file structure. If you attach it to a Windows PC, download & install the free Linux Reader and you'll be able to see the file structure on the drive. http://www.diskinternals.com/linux-reader/ While you've got it attached to your PC, COPY and backup your important data (assuming it was indeed recovered okay). DO NOT do ANY WRITES to the disk -- just read from it and copy what you want to backup. Note that when you attach this drive back to the UnRAID server, if you Start the array, UnRAID is going to rebuild ONE of your disks. It's NOT clear at this point WHICH drive that is -- the picture of your Web GUI I asked you to post will hopefully show that. Check the disk, and post the Web GUI, before you do ANYTHING on your UnRAID server.
April 12, 201412 yr It's probably showing blue because I bet he reassigned it to disk1. razr: People have been trying to show you how to view the file system that got recovered. If you just assign this disk now as "disk1" then system will think you installed a new drive and it will proceed to rebuild the drive - but we already know the parity is not correct in your array so this will only result in clobbering your disk yet again.
April 12, 201412 yr razr: Here's probably the easiest way to get on with things. Let's do this: 1. Stop array, got to Utils/New Config and run that utility. This will completely clear out the disk config. 2. Go back to Main and assign disk1, disk2, disk3, and cache the way you had them. DO NOT assign parity, just leave unassigned. 3. Now Start the array. You should be able to browse the disk shares on your network. Take a look at disk1 and let's see how much got recovered. Depending on how messed up this file system is will dictate probably how to proceed to restore your server back to something useful again.
Archived
This topic is now archived and is closed to further replies.