Hey there.
My fedora core 3 system recently got stuck and so I had to do a hard reset of my computer.
When booting up the next time, the system tells me that it is unable to read the superblock information.
Knoppix helped me to at least boot up a linux.
This is my current situation:
fsck and e2fsck both resign to work with a corrupted superbock and don't accept my specification of the backup superblocks (using the "-b" argument)
Only dumpe2fs was helpful. This is its output:
dumpe2fs 1.35-WIP (07-Dec-2003)
Filesystem volume name: /
Last mounted on: <not available>
Filesystem UUID: b516fe67-d65b-4058-810b-b50f32b1c57f
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr filetype sparse_super
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 930240
Block count: 1857507
Reserved block count: 92875
Free blocks: 350664
Free inodes: 761639
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16320
Inode blocks per group: 510
Filesystem created: Tue Oct 19 19:57:19 2004
Last mount time: Tue Nov 9 16:56:00 2004
Last write time: Tue Nov 9 16:56:00 2004
Mount count: 81
Maximum mount count: -1
Last checked: Tue Oct 19 19:57:19 2004
Check interval: 0 (<none>)
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: accabd87-90a9-4639-b437-f115c4476e17
Journal backup: inode blocks
ext2fs_read_bb_inode: invalid argument
Any suggestions of how to recover my hda7?
Thanks in Advance.
poly
Linear Mode
