From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: IDE BUG REPORT: 2.5.45 killed my / partition
Date: Sun, 03 Nov 2002 19:47:37 -0500 [thread overview]
Message-ID: <3DC5C3A9.3060608@nortelnetworks.com> (raw)
duron, kt133 motherboard, ide disks, new clean mandrake 9 install with
ext3, running fine over several boots
Yesterday I compiled 2.5.45 after working around some build glitches,
booted fine and ran it for several hours. I just turned on your basic
generic IDE stuff and the VIA ide controllers, nothing fancy or (at
least so I thought) dangerous.
Today I booted but it wouldn't let me log in as normal user (error
message flashed too quickly for me to be able to read it, looked like it
began with "critical") but I could log in as root so I did. I poked
around and didn't see anything odd, so I went to reboot onto the
mandrake kernel.
I boot up, and it gets to the point where it checks the root filesystem
and it halts with an error:
Checking root filesystem
fsck.ext3/dev/hdb9:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
: No such file or directory while trying to open /dev/hdb9
Failed to check filesystem. Do you want to repair the errors? (Y/N)
(beware, you can lose data)
A bit worried, I rebooted with the rescue disk and ran fsck.ext3, which
found a bunch of errors that I told it to clean. Still on my rescue
kernel/ramdisk I mounted the filesystem and tried listing a few files
and everything was fine. I then rebooted and the boot-time fsck gave me
the same error as above.
I thought that 2.5.45 wasn't supposed to have ide problems like this
anymore...
Anyways, the only thing left that I can see is to re-install--anyone
else have a better idea? I'll hold off on doing that for a few days in
case someone wants more information on the system.
Any ideas why the rescue fsck passes but boot-time fails?
Thanks,
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next reply other threads:[~2002-11-04 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 0:47 Chris Friesen [this message]
2002-11-04 3:19 ` IDE BUG REPORT: 2.5.45 killed my / partition -- partially recovered Chris Friesen
2002-11-04 9:48 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DC5C3A9.3060608@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox