Re: [gentoo-user] Issuses with partition

["Joshua Murphy" <poisonbl@gmail.com>]

On Thu, Nov 20, 2008 at 12:17 PM, Юрий Дмитришин <admin@art-fm.com.ua> wrote:
> Hi.
>
> I've resized my /home (/dev/sda7) with gparted and now I can't mount it. The
> filesystem was ext3.
>
> The output of `mount -t ext3 /dev/sda7 /home` or `mount -t
> ext2 /dev/sda7 /home`is:
> wrong fs type, bad option, bad superblock on /dev/sda7.
>
> The output of `fsck -y /dev/sda7` is:
> fsck 1.41.2 (02-Oct-2008)
> e2fsck 1.41.2 (02-Oct-2008)
> fsck.ext3: Group descriptors look bad... trying backup blocks...
> Superblock has an invalid ext3 journal (inode 8).
> Clear? yes
>
> *** ext3 journal has been deleted - filesystem is now ext2 only ***
>
> Corruption found in superblock.  (inodes_count = 0).
>
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
>    e2fsck -b 32768 <device>
>
> The ouput of `dumpe2fs /dev/sda7` is:
> dumpe2fs 1.41.2 (02-Oct-2008)
> Filesystem volume name:   <none>
> Last mounted on:          <not available>
> Filesystem UUID:          72c8beda-d12e-41d3-91f9-ed97c9c6486d
> Filesystem magic number:  0xEF53
> Filesystem revision #:    1 (dynamic)
> Filesystem features:      has_journal dir_index filetype sparse_super
> large_file
> Filesystem flags:         signed_directory_hash
> Default mount options:    (none)
> Filesystem state:         clean with errors
> Errors behavior:          Continue
> Filesystem OS type:       Linux
> Inode count:              8241152
> Block count:              16472641
> Reserved block count:     824289
> Free blocks:              3285006
> Free inodes:              6202803
> First block:              0
> Block size:               4096
> Fragment size:            4096
> Blocks per group:         32768
> Fragments per group:      32768
> Inodes per group:         16384
> Inode blocks per group:   512
> Filesystem created:       Tue Feb 19 15:48:22 2008
> Last mount time:          Wed Nov 19 21:15:08 2008
> Last write time:          Thu Nov 20 19:15:07 2008
> Mount count:              7
> Maximum mount count:      35
> Last checked:             Wed Nov 19 15:47:53 2008
> Check interval:           15552000 (6 months)
> Next check after:         Mon May 18 16:47:53 2009
> Reserved blocks uid:      0 (user root)
> Reserved blocks gid:      0 (group root)
> First inode:              11
> Inode size:               128
> Journal inode:            8
> Default directory hash:   tea
> Directory Hash Seed:      2c2a57d9-9804-450f-8db8-e7c0c706b975
> Journal backup:           inode blocks
> dumpe2fs: A block group is missing an inode table while reading journal inode
>
> Thanks for your help.
>
> --
> Best, Yuriy A. Dmitrishin.

Just a quick guess off the top of my head... when you resized... did
you add or remove space, and did you make the change at the start or
end of the partition?

-- 
Poison [BLX]
Joshua M. Murphy