lost a drive?

[Tony Nelson]

At 12:54 PM -0700 9/24/06, Dave Stevens wrote:
>Quoting Jay Cliburn <jacliburn at bellsouth.net>:
>
>thanks, Jay. See below please...
>
>  > Dave Stevens wrote:
>  > > Quoting Tony Nelson <tonynelson at georgeanelson.com>:
>  > >
>  > > Thanks, Tony, see below...
>
>snip!
>
>  > >
>  > > Ideas? further suggestions? reading I can do online on this?
>  >
>  > First, unmount the partition.
>  >
>  > Then, to find the location of all backup superblocks, run
>  >
>  > mke2fs -n /dev/hda2
>  >
>  > Pick one, then run
>  >
>  > e2fsck -b <your_picked_superblock> /dev/hda2
>
>
>linux:/sbin # umount /dev/hda2
>umount: /dev/hda2: not mounted
>linux:/sbin # mke2fs -n /dev/hda2
>mke2fs 1.35 (28-Feb-2004)
>Filesystem label=
>OS type: Linux
>Block size=4096 (log=2)
>Fragment size=4096 (log=2)
>4882432 inodes, 9753463 blocks
>487673 blocks (5.00%) reserved for the super user
>First data block=0
>298 block groups
>32768 blocks per group, 32768 fragments per group
>16384 inodes per group
>Superblock backups stored on blocks:
>         32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
>2654208,
>         4096000, 7962624
>
>linux:/sbin # e2fsck -b 32768 /dev/hda2
>e2fsck 1.35 (28-Feb-2004)
>e2fsck: Bad magic number in super-block while trying to open /dev/hda2
>
>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
>
>and so on for all superblock values given when running mke2fs -n /dev/hda2
>
>so I got a bit further. Still open to suggestion....

It is likely that either the disk is the wrong disk, or completely 
hosed, or you have guessed wrong about its format or block size. 
Take a look at the data and see if it makes sense as being your disk. 
dd is your friend.
-- 
____________________________________________________________________
TonyN.:'                       <mailto:tonynelson at georgeanelson.com>
       '                              <http://www.georgeanelson.com/>