?
Solved

Hard drive problems

Posted on 1997-03-27
1
Medium Priority
?
204 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 300 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

Why Off-Site Backups Are The Only Way To Go

You are probably backing up your data—but how and where? Ransomware is on the rise and there are variants that specifically target backups. Read on to discover why off-site is the way to go.

Question has a verified solution.

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

Using 'screen' for session sharing, The Simple Edition Step 1: user starts session with command: screen Step 2: other user (logged in with same user account) connects with command: screen -x Done. Both users are connected to the same CLI sessio…
Setting up Secure Ubuntu server on VMware 1.      Insert the Ubuntu Server distribution CD or attach the ISO of the CD which is in the “Datastore”. Note that it is important to install the x64 edition on servers, not the X86 editions. 2.      Power on th…
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
Suggested Courses
Course of the Month7 days, 21 hours left to enroll

765 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