On 4/14/05, Dave <[EMAIL PROTECTED]> wrote:
> I need some links and/or pointers on recovering files from a corrupted
> partition.
>
> I'm getting a bad super block message when trying to mount a
> partition in a Knoppix CD. I was able to mount it earlier before I ran
> fsck.ext3 -y there were tons of error message btw. I tried debugfs,
> but i'm not sure if i'm using it correctly or if fsck may have made
> the drive worse. any help appreciated.
>
> It started with this below and when I tried reboot or init 6 I would
> get segfaults.
> Apr 13 20:19:55 case kernel: hda2: rw=0, want=20144277112, limit=311853780
> Apr 13 20:19:55 case kernel: attempt to access beyond end of device
> Apr 13 20:19:55 case kernel: hda2: rw=0, want=21970726864, limit=311853780
> Apr 13 20:19:55 case kernel: attempt to access beyond end of device
> Apr 13 20:19:55 case kernel: hda2: rw=0, want=9867253392, limit=311853780
Look at the following:
option to mount(1)
sb=n Instead of block 1, use block n as superblock. This could
be useful when the filesystem has been damaged.
option to e2fsck(1):
-b superblock
Instead of using the normal superblock, use an
alternative superblock specified by superblock. This option is
normally used when the primary superblock has been corrupted. The
location of the backup superblock is dependent on the filesystem's
blocksize.
For filesystems with 1k blocksizes, a backup
superblock can be found at block 8193; for filesystems with 2k
blocksizes, at block 16384; and for 4k blocksizes, at block 32768.
Additional backup superblocks can be determined by
using the mke2fs program using the -n option to print out
where the superblocks were created. The -b option to
mke2fs, which specifies blocksize of the filesystem must be specified
in order for the superblock locations that are printed out to be
accurate.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
