From: Tejun Heo <htejun@gmail.com>
To: "0602@eq.cz" <0602@eq.cz>
Cc: linux-kernel@vger.kernel.org, Linux-ide <linux-ide@vger.kernel.org>
Subject: Re: totally random "VFS: Cannot open root device"
Date: Wed, 30 Nov 2005 13:35:37 +0900 [thread overview]
Message-ID: <438D2C19.3030008@gmail.com> (raw)
In-Reply-To: <438B6E05.8070009@eq.cz>
0602@eq.cz wrote:
> Hi!
>
> (Please CC me your answers as I am not subscribed.)
>
> I have a problem with 2.6.14.3 kernel (but this probably isn't too
> version-specific). I have a kernel which succesfully boots on totally
> random basis (cca 70% is success). My root partition resides on a SATA
> disc connected to a controller on Intel 6300ESB ICH southbridge (mb
> Intel se7320vp2). There is a reiserfs 3 filesystem on my root partition.
> Without any changes to configuration (os or bios or whatever) I
> sometimes get:
>
> VFS: Cannot open root device "801" or unknown block(8,1)
>
> Could this be some timeout issue, or indication of crappy hw? I've tried
> this about 10 times (immediately ctrl+alt+del on successfull boot or
> reset button on aforementioned panic) and I saw no regularities in this
> misbehaviour.
>
> I sincerely appreciate any advice anyone can give.
>
[CC'ing linux-ide]
Hello, 0602. :-)
Can you please post dmesg of a successful booting? That will tell us
which SATA controller/disks you are using. Also, the boot log of a
failed boot will be very helpful - the best way to get this is via
serial console. If you don't have access to serial console, taking note
/ picture of the part where SATA detection fails will do too.
Also, when the machine boots successfully, does it work without
generating disk related kernel logs? Just perform any IO-heavy
operations - cp'ing directories which contain large files,
tar/untarring... - and see if the kernel complains about anyting.
--
tejun
next parent reply other threads:[~2005-11-30 4:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <438B6E05.8070009@eq.cz>
2005-11-30 4:35 ` Tejun Heo [this message]
2005-11-30 9:05 ` totally random "VFS: Cannot open root device" Jean-François Stenuit
2005-11-30 16:30 ` Randy.Dunlap
2005-12-01 9:42 ` Jean-François Stenuit
2005-12-01 11:20 ` Jean-François Stenuit
2005-11-30 13:07 ` 0602
2005-11-30 22:05 ` Keith Mannthey
2005-12-01 9:40 ` Jean-François Stenuit
2005-12-01 11:20 ` Tejun Heo
2005-12-01 12:59 ` Jean-François Stenuit
2005-12-01 13:29 ` Tejun Heo
2005-12-01 15:34 ` 0602
2005-12-02 1:53 ` Jeff Garzik
2005-12-02 3:00 ` Tejun Heo
2005-12-02 3:26 ` [PATCH] ata_piix: ignore all zero PCS value on ICH5's Tejun Heo
2005-12-02 12:40 ` 0602
2005-12-05 10:07 ` Jean-François Stenuit
2005-12-05 10:17 ` Tejun Heo
2006-01-29 5:22 ` Jeff Garzik
2006-02-01 2:01 ` Tejun Heo
2006-02-09 9:23 ` Jeff Garzik
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=438D2C19.3030008@gmail.com \
--to=htejun@gmail.com \
--cc=0602@eq.cz \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).