Hi! I'm new to the list. I have a problem with mounting my home directory since my PC crashed. I hope that I can get some help on this list as I don't know much of ext3 myself. The mount command for my /home gives me the following output: # mount /dev/sda6 /mnt/tmp/ mount: wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so The partition /dev/sda6 is an ext3 file system. It also tried to specify the file system type with -text3 and to use a backup superblock with the sb option but it does not help. I tried to run fsck but it does not fix the problem either. Here is the output of fsck: # fsck.ext3 /dev/sda6 e2fsck 1.39 (29-May-2006) Group descriptors look bad... trying backup blocks... Inode bitmap for group 522 is not in group. (block 3271884801) Relocate<y>? yes fsck.ext3: e2fsck_read_bitmaps: illegal bitmap block(s) for /home I searched the Internet and I found a small Windows application that could see my /home partition and files. So I can't beleive there is nothing under Linux to recover my files. I'll appreciate any help on this topic because I tried anything I could think of by myself and I still can't mount my home. Any suggestions? Best wishes! Cd -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20070110/534f0469/attachment.htm>
On Wed, 10 Jan 2007, Nickel Cadmium wrote:> # fsck.ext3 /dev/sda6 > e2fsck 1.39 (29-May-2006) > Group descriptors look bad... trying backup blocks... > Inode bitmap for group 522 is not in group. (block 3271884801) > Relocate<y>? yes > > fsck.ext3: e2fsck_read_bitmaps: illegal bitmap block(s) for /home...and after this message, fsck.ext3 just stops? What's the exit code of fsck.ext3? (e.g. 'fsck.ext3 /dev/sda6; echo $?'). Try "fsck.ext3 -v" for more details. Is there anything related in your syslog? Can you dd(1) the device (read! not write! :)) without errors? Which kernel/arch are you running? Christian. -- BOFH excuse #99: SIMM crosstalk.
fsck can't help you because bitmaps are damaged, but there is a way to recover your files. 1. Prepair enough space on another partition and create directory where to put recovered files. 2. Boot linux. (for example use Rescue CD or Knoppix Live CD) 3. Run debugfs in catastrophic mode (-c option) : debugfs -c /dev/hdaX catastrophic mode does not read inode and group bitmaps if your superblock is damaged consider using -s (superblock) and -b (block size) options to specify backup superblock (the block size and superblock locations can be found by dumpe2fs) 4. Inside debugfs shell run: rdump directory_to_recover directory_for_recovered_files directory_to_recover is in damaged partition directory_for_recovered_files is in your active partition (from step 1 above) for example: rdump /home /tmp/recovery This will copy /home directory and all it's content including subdirectories and files to /tmp/recovery. -- View this message in context: http://www.nabble.com/Can%27t-mount--home-anymore-tf2951542.html#a8691524 Sent from the Ext3 - User mailing list archive at Nabble.com.
Hi! Thanks a lot for your mail: I managed to recover my files! I don't really know how debugfs works but with the rdump command it could copy all my files to a new partition. Cheers, Cd On 1/29/07, Evgeni <evgeni at scientist.com> wrote:> > > fsck can't help you because bitmaps are damaged, > but there is a way to recover your files. > > 1. Prepair enough space on another partition > and create directory where to put recovered files. > > 2. Boot linux. > (for example use Rescue CD or Knoppix Live CD) > > 3. Run debugfs in catastrophic mode (-c option) : > debugfs -c /dev/hdaX > catastrophic mode does not read inode and group bitmaps > if your superblock is damaged consider using -s (superblock) and -b (block > size) options > to specify backup superblock > (the block size and superblock locations can be found by dumpe2fs) > > 4. Inside debugfs shell run: > rdump directory_to_recover directory_for_recovered_files > directory_to_recover is in damaged partition > directory_for_recovered_files is in your active partition (from step 1 > above) > > for example: > rdump /home /tmp/recovery > This will copy /home directory and all it's content including > subdirectories > and files to /tmp/recovery. > -- > View this message in context: > http://www.nabble.com/Can%27t-mount--home-anymore-tf2951542.html#a8691524 > Sent from the Ext3 - User mailing list archive at Nabble.com. > > _______________________________________________ > Ext3-users mailing list > Ext3-users at redhat.com > https://www.redhat.com/mailman/listinfo/ext3-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20070206/058dd186/attachment.htm>