Solved

Hard drive problems

Posted on 1997-03-27
1
202 Views
Last Modified: 2013-12-15
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

0
Comment
Question by:holmes032797
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 1

Accepted Solution

by:
ggeens earned 100 total points
ID: 1627022
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

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Network Interface Card (NIC) bonding, also known as link aggregation, NIC teaming and trunking, is an important concept to understand and implement in any environment where high availability is of concern. Using this feature, a server administrator …
The purpose of this article is to demonstrate how we can use conditional statements using Python.
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question