I've got linux installed on a laptop, and it has just die. When I start it
up, it tells me I have to do a manual fsck; when I do so, it comes to one
particularly problematic line:
Error reading block 32770 (Attempt to read block from filesystem resulted in
short read) while reading inode and block bitmaps. Ignore error<y>?
If I hit 'y', it just starts spewing random crap on the screen, and my only
choice is to restart. If I hit 'n', it tells me:
e2fsck: Can't read an block bitmap while retrying to read bitmaps for
/dev/hda11
(My root on hda11.) Now, that sentence isn't exactly grammatical, and, on top
of that, I can't totally figure out what's happening. Worse, googling for
that phrase yeilds *nothing* -- and I mean *nothing* -- so it appears that no
one else in the history of the planet has ever had this problem. I've got my
machine dual booting, and the other OS works fine, so I've ruled out any
serious hard drive issues. I found an old post from a redhat list that
suggested running e2fsck -c to mark the sector as bad, and then e2fsck -cc to
remap the drive, but I tried both of these to no avail -- i.e., the same thing
happens as just running e2fsck.
Other than that, though I have no ideas. None. If anyone has any ideas of
things to try, that would be great. Thanks.
Chris St. Pierre
*******************************************************
"We can all love everything, without ever knowing why."
--David Pomeranz, as sung by John Denver
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
