Hard drive problems

This isn't exactly a setup problem, but this seems to be the closest forum.

I was setting up a new hard drive last night and apparently knocked around one of my old drives a little too hard.  When I tried booting of the old drive I got a kernel panic (with a message I didn't write down).  I booted from floppy
and ran e2fsck.  I saw the following:

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

/dev/hda2 contains a file system with errors, check forced.

Error reading block 64734 (attempt to read block from filesystem resulted in short read) while reading indirect blocks at inode 14317.  Ignore error <y>?
------------------

to which I responded 'y'.  Then I got:

------------------
Inode 14317, i-blocks wrong 1056 (counted 1338).  Set i-blocks to to
counted <y>?
------------------

to which I responded 'n'.  After this I got many, many repeats of the first message and a couple repeats of the second, but with different numbers.  I eventually got tired of typing responses, so I gave up and tried to mount
the drive read-only just to see what would happen.  After successfully mounting I typed 'ls' and got:

------------------
Kernel panic: EXT2-fs panic (device 3/2): ext2_read_inode: unable to read i-node block - inode = 124442, block = 499719.
------------------

Whatever is wrong with the drive is probably localized since I can boot to DOS with the same drive and don't see any problems.  I realize the drive is history, but I have some data I'd like to recover if at all possible.  Any ideas on how I might accomplish this?

Thanks,
Rich

holmes032797Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ggeensCommented:
I think you have some bad sectors on the disk. Try running badblocks, possibly followed by fcsk again.
Or maybe it is just a corrupted superblock. e2fsck -b 8193 could help in this case.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.