| 1 |
On Thu, Nov 20, 2008 at 12:17 PM, Юрий Дмитришин <admin@××××××××××.ua> wrote: |
| 2 |
> Hi. |
| 3 |
> |
| 4 |
> I've resized my /home (/dev/sda7) with gparted and now I can't mount it. The |
| 5 |
> filesystem was ext3. |
| 6 |
> |
| 7 |
> The output of `mount -t ext3 /dev/sda7 /home` or `mount -t |
| 8 |
> ext2 /dev/sda7 /home`is: |
| 9 |
> wrong fs type, bad option, bad superblock on /dev/sda7. |
| 10 |
> |
| 11 |
> The output of `fsck -y /dev/sda7` is: |
| 12 |
> fsck 1.41.2 (02-Oct-2008) |
| 13 |
> e2fsck 1.41.2 (02-Oct-2008) |
| 14 |
> fsck.ext3: Group descriptors look bad... trying backup blocks... |
| 15 |
> Superblock has an invalid ext3 journal (inode 8). |
| 16 |
> Clear? yes |
| 17 |
> |
| 18 |
> *** ext3 journal has been deleted - filesystem is now ext2 only *** |
| 19 |
> |
| 20 |
> Corruption found in superblock. (inodes_count = 0). |
| 21 |
> |
| 22 |
> The superblock could not be read or does not describe a correct ext2 |
| 23 |
> filesystem. If the device is valid and it really contains an ext2 |
| 24 |
> filesystem (and not swap or ufs or something else), then the superblock |
| 25 |
> is corrupt, and you might try running e2fsck with an alternate superblock: |
| 26 |
> e2fsck -b 32768 <device> |
| 27 |
> |
| 28 |
> The ouput of `dumpe2fs /dev/sda7` is: |
| 29 |
> dumpe2fs 1.41.2 (02-Oct-2008) |
| 30 |
> Filesystem volume name: <none> |
| 31 |
> Last mounted on: <not available> |
| 32 |
> Filesystem UUID: 72c8beda-d12e-41d3-91f9-ed97c9c6486d |
| 33 |
> Filesystem magic number: 0xEF53 |
| 34 |
> Filesystem revision #: 1 (dynamic) |
| 35 |
> Filesystem features: has_journal dir_index filetype sparse_super |
| 36 |
> large_file |
| 37 |
> Filesystem flags: signed_directory_hash |
| 38 |
> Default mount options: (none) |
| 39 |
> Filesystem state: clean with errors |
| 40 |
> Errors behavior: Continue |
| 41 |
> Filesystem OS type: Linux |
| 42 |
> Inode count: 8241152 |
| 43 |
> Block count: 16472641 |
| 44 |
> Reserved block count: 824289 |
| 45 |
> Free blocks: 3285006 |
| 46 |
> Free inodes: 6202803 |
| 47 |
> First block: 0 |
| 48 |
> Block size: 4096 |
| 49 |
> Fragment size: 4096 |
| 50 |
> Blocks per group: 32768 |
| 51 |
> Fragments per group: 32768 |
| 52 |
> Inodes per group: 16384 |
| 53 |
> Inode blocks per group: 512 |
| 54 |
> Filesystem created: Tue Feb 19 15:48:22 2008 |
| 55 |
> Last mount time: Wed Nov 19 21:15:08 2008 |
| 56 |
> Last write time: Thu Nov 20 19:15:07 2008 |
| 57 |
> Mount count: 7 |
| 58 |
> Maximum mount count: 35 |
| 59 |
> Last checked: Wed Nov 19 15:47:53 2008 |
| 60 |
> Check interval: 15552000 (6 months) |
| 61 |
> Next check after: Mon May 18 16:47:53 2009 |
| 62 |
> Reserved blocks uid: 0 (user root) |
| 63 |
> Reserved blocks gid: 0 (group root) |
| 64 |
> First inode: 11 |
| 65 |
> Inode size: 128 |
| 66 |
> Journal inode: 8 |
| 67 |
> Default directory hash: tea |
| 68 |
> Directory Hash Seed: 2c2a57d9-9804-450f-8db8-e7c0c706b975 |
| 69 |
> Journal backup: inode blocks |
| 70 |
> dumpe2fs: A block group is missing an inode table while reading journal inode |
| 71 |
> |
| 72 |
> Thanks for your help. |
| 73 |
> |
| 74 |
> -- |
| 75 |
> Best, Yuriy A. Dmitrishin. |
| 76 |
|
| 77 |
Just a quick guess off the top of my head... when you resized... did |
| 78 |
you add or remove space, and did you make the change at the start or |
| 79 |
end of the partition? |
| 80 |
|
| 81 |
-- |
| 82 |
Poison [BLX] |
| 83 |
Joshua M. Murphy |
Archives