[NTLUG:Discuss] EXT3-fs: group descriptors corrupted!

[Leroy Tennison]

m m wrote:
> No response?
>  
> Or any one just tell me how to get/copy  the file to other drive?
> just text and image files. All about 30 G. 
> please tell me mount to linux os, because it's the problem I have. (see below)
>  
> It is ext3 file system. Have no ideal how it will do with Windoz. 
>  
> still looking ways to get the file back. or even just fix the group descriptors.
>  
> Thanks.
> 
> 
> 
>> From: llliiilll at hotmail.com> To: discuss at ntlug.org> Date: Mon, 23 Jul 2007 06:10:27 +0000> Subject: [NTLUG:Discuss] EXT3-fs: group descriptors corrupted!> > All:> > when try to mount an existing ext3 HD the Frdora 7 box, get this (EXT3-fs: group descriptors corrupted!) error. > see below I did:> > # mount /dev/sdb /wwwmount: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so> > # dmesg | taildevice peth0 entered promiscuous modeeth0: port 1(peth0) entering learning stateeth0: topology change detected, propagatingeth0: port 1(peth0) entering forwarding statepeth0: no IPv6 routers presenteth0: no IPv6 routers presentEXT3-fs error (device sdb): ext3_check_descriptors: Block bitmap for group 880 not in group (block 0)!EXT3-fs: group descriptors corrupted!EXT3-fs error (device sdb): ext3_check_descriptors: Block bitmap for group 880 not in group (block 0)!EXT3-fs: group des
criptors corrupted!> > # fsck.ext3 /dev/sdbe2fsck 1.39 (29-May-2006)Group descriptors look bad... trying backup blocks...fsck.ext3: Bad magic number in super-block while trying to open /dev/sdb> The superblock could not be read or does not describe a correct ext2filesystem. If the device is valid and it really contains an ext2filesystem (and not swap or ufs or something else), then the superblockis corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>> > # fsck.ext3 -b 8193 /dev/sdbe2fsck 1.39 (29-May-2006)fsck.ext3: Bad magic number in super-block while trying to open /dev/sdb> The superblock could not be read or does not describe a correct ext2filesystem. If the device is valid and it really contains an ext2filesystem (and not swap or ufs or something else), then the superblockis corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>> > (i also tried other numbers, something > 8193, no work) 
> > # fdisk -l> Disk /dev/sda: 13.5 GB, 13578485760 bytes255 heads, 63 sectors/track, 1650 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes> Device Boot Start End Blocks Id System/dev/sda1 * 1 13 104391 83 Linux/dev/sda2 14 1650 13149202+ 8e Linux LVM> Disk /dev/sdb: 300.0 GB, 300069052416 bytes255 heads, 63 sectors/track, 36481 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes> Device Boot Start End Blocks Id System/dev/sdb1 1 36481 293033601 83 Linux> > # fdisk /dev/sdb> The number of cylinders for this disk is set to 36481.There is nothing wrong with that, but this is larger than 1024,and could in certain setups cause problems with:1) software that runs at boot time (e.g., old versions of LILO)2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)> > I have googled about this problem. no luck.> > I use to mount it on the Fedora 6, it worked. > > > Can anyone help!?> > Thanks.> > ___________________________________________________
______________> See what you’re getting into…before you go there.> http://newlivehotmail.com> _______________________________________________> http://www.ntlug.org/mailman/listinfo/discuss
> _________________________________________________________________
> Missed the show?  Watch videos of the Live Earth Concert on MSN.
> http://liveearth.msn.com
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
> 
I assume you tried e2fsck without success (if not - try).

No promises but a couple of ideas:  Can you mount it on Fedora 6 using 
Rescue Mode (maybe Fedora 7 has a driver problem)?  If so and you can 
use the network card then use something like ftp to send it elsewhere.

As a very last resort try converting back to ext2 and removing other 
features.