Disk Recovery suggestions welcomed...

[lug at the-leveys.us (Don Levey)]

dsr wrote:
> On Thu, Dec 15, 2005 at 02:46:13PM -0500, Don Levey wrote:
>
>> [root at davinci log]# e2fsck -c /dev/hda3
>> e2fsck 1.35 (28-Feb-2004)
>> /home1: Attempt to read block from filesystem resulted in short read
>> while reading block 524
>
> See if this works:
>
> e2fsck -b 32768 /dev/hda3
>
> Use e2fsck -n to see where extra superblocks would be stored,
> and pass those locations on to -b.
>

OK, here's what I did:

-----------------------------
[root at davinci root]# mke2fs -n /dev/hda3
mke2fs 1.35 (28-Feb-2004)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
6406144 inodes, 12799788 blocks
639989 blocks (5.00%) reserved for the super user
First data block=0
391 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, 11239424

[root at davinci root]# e2fsck -b 32768 /dev/hda3
e2fsck 1.35 (28-Feb-2004)
/home1: Attempt to read block from filesystem resulted in short read while
reading block 524
/home1: Attempt to read block from filesystem resulted in short read reading
journal superblock
e2fsck: Attempt to read block from filesystem resulted in short read while
checking ext3 journal for /home1

----------------------------

I got the same output from e2fsck regardless of the alternate superblock I
provided.  Looks like I'll be pulling off the data using dd, and then
working with a utility such as spinrite.  Interestingly, I saw no problems
in the logs at all from smartd, so it looks like the rest of the drive
should be OK, right?  Or should I just replace the whole thing?
 -Don