Bad Stuff from fsck

Bad Stuff from fsck

Post by John Carrol » Sat, 02 May 1998 04:00:00

Turned on my trusty linux box this morning, expecting all to go well,
as it always has.  Surprise.  During bootup, got the following messages
(approximately): Unexpected inconsistency.  Run fsck manually
fsck returned error code -- Reboot Now.  Error reading block 49188 (attempt
to read block from filesystem resulted in short read) while doing inode

  The prompt had gone from myname# to  (none)#

I tried fsck, but just got a short message (a version number, I think).
I tried running shutdown -r now, and got: Cannot create /etc/initrunlevel

Actually, I'm not sure which actions gave which results, having been in a bit
of a panic at the time.  In desperation, I typed "exit," at which point the
system seems to have remounted the file system, the prompt took on its normal
appearance, I logged on as root, and everything seemed to work normally.  
However, on the suspicion that something was definitely wrong and might get
worse if I didn't find and fix it, I shut down the system, scratched my head,
and didn't come up with any answers I liked.  Obviously I'm no guru.  My
question to those who are is, can the problem be corrected, and if so, how do
I go about it?

Thanks in advance.

John Carroll


Bad Stuff from fsck

Post by Jim Buchan » Sat, 02 May 1998 04:00:00

: (approximately): Unexpected inconsistency.  Run fsck manually
: fsck returned error code -- Reboot Now.  Error reading block 49188 (attempt
: to read block from filesystem resulted in short read) while doing inode
: scan.

Have you seen any errors on the console (or the log files) (during
normal use) that say something like "DriveSeekNotReady",
"unrecoverable IO error"? I paraphrased those, since I don't have the
exact wording handy.

When I've seen just the error you have, I think (it's been a while)
that I managed to fix the problem with badblocks and debugfs. There
was a good article on how to do this in a January issue of the Linux
Journal. I forget which year, it's been a while.

When I've gotten the second error (the real one, not my paraphrased
version), it's been worse. I fixed two WD drives with this problem
using a program from the Western Digital web site. It does destroy all
data, requiring a reload from backup, but both those drives still work
well more than a year later (more than two for one of them).

I had a similar problem with a Maxtor this year, and some similar
software from Maxtor seemed to help at first, but the problem kept
coming back worse than before. They cheerfully replaced the drive
under warranty. The new one died in a week. They cheerfully replaced
that one, and the replacement has been holding up well for a few
months now.

I'm really happy with the customer service at least. Friendly,
efficient people, some of whom were familiar with Linux. Cool.


================= ====================
"When the stars threw down their spears, And water'd heaven with their
 tears, Did he smile his work to see? Did he who made the Lamb make thee?"
==================== ========================


1. Good stuff Bad Stuff

Oh look its that bloke again, posting via OE what a c*nt!

I was thinking what I liked first time I used a system:

1.VMS back in the 80's--Every time you edited in that sh*theap ed at least
it made a back-up and incremented the version number, you could then "purge"
by typing the word purge <filename> and it would delete all but the most

2. Apple Mac 80's again--Clipboard, "F*ing hell" I fort- Thats bloody good,
oh and this mouse menu thing sure saves me from having to learn a load of
CLI crap

2.5 DOS 3 - Oh its almost like a proper OS

2.75 Atari- This is great, I turn it off, put the disk in, turn it on and
after a short while Im playing what ever game this is. Oh yeah and the mouse
keeps getting fluff on the rollers

3. Windows 3.x early 90's The help files would you belive, why? Becuase you
had that bookmark function back then, as you fliped around a manual you
could keep track of intresting pages other than the last one you read. Why
M$ got rid of that in HTMLHelp I will never know

4.*NIX The child like ease of sendmails config files, nah sorry it was
rc.conf but thats not Linux is it, no thats a proper OS

5. Linux-Yeah what did I like about Linux? Was it the info help system-Oh no
hang on that aint nothing to do with Linux. Was it the way when you asked
"How do I configure <insert package name here>" you would get a flood of
pus, with one poor bloke who knew what he was on about buryed in a sea of
No I know what I like about Linux, its the friendly people who advocate it!
Oh and NATs is handy got to admit that, oh no hang on did that in *BSD.
Er I know make menuconfig oooh big geeky hardon from that ocean of options

(Bit of an aquatic theme there..)

2. Booting questions

3. fsck, raid reconstruction & bad bad 2.4.3

4. Not Found

5. bad partition on good disk won't mount or fsck (bad magic number/superblock)

6. Linux META-FAQ

7. fsck fsck fsck say I

8. Linux on the AMiga (???)

9. Bad block in /var,fsck fails.

10. Bad Blocks on IDE drive, fsck doesn't fix it

11. How can I fsck a HD with bad super block

12. Bad block ,restore , fsck ...