From: gaxt <gaxt@rogers.com>
To: Yifang Dai <daiy@attbi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2 - VFS: Cannot open root device "NULL" or sda1
Date: Mon, 28 Jul 2003 00:23:36 -0400 [thread overview]
Message-ID: <3F24A548.2040202@rogers.com> (raw)
In-Reply-To: <20030728022818.GA7221@yahoo.com>
Yifang Dai wrote:
> On Sun, Jul 27, 2003 at 08:42:13PM +0000, Henrik Storner wrote:
>
>>So I know 2.6.0-test1 works for me. But 2.6.0-test2 with the same
>>configuration (just a "make oldconfig" in between) stops during boot
>>with:
>>
>>VFS: Cannot open root device "NULL" or sda1
>>Please append a correct "root=" boot option
>>Kernel panic: Unable to mount root fs on sda1
>>
>
>
> I've got the same error, except my root device is /dev/hda3. It also
> worked in 2.6.0-test1 :)
>
I believe you need to change in your grub.conf file the root=/dev/hda3
to a root=### ie root=0307
The number is composed of 3 pieces
(a) major device number ie. 3 above (leading zero is ignored)
(b) minor device number ie. 0 above
(c) partition on device ie. 7 above
I use hdb. hda and hdb are both major device number 3
hda is minor device number 0
hdb is minor device number 64
BUT minor device number is in base 16
so in base 16, hda is 0 (0x16=0) and hdb is 4 (4x16=64)
THUS
my root=/dev/hdb4 becomes root=344 (ie. maj device 3, minor device 64
(4x16) and partition #4.
Examples:
hda1 = 301
hda3 = 303
hdb1 = 341
hdb4 = 344 etc.
Pardon if this is obvious. To determine linux device numbers, google.
there's a list out there. I found a list below:
http://www.lanana.org/docs/device-list/devices.txt
next prev parent reply other threads:[~2003-07-28 3:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 20:42 2.6.0-test2 - VFS: Cannot open root device "NULL" or sda1 Henrik Storner
2003-07-28 2:28 ` Yifang Dai
2003-07-28 4:23 ` gaxt [this message]
2003-07-28 22:46 ` Henrik Storner
2003-07-28 19:42 ` 2.6.0-test2 - Strange Terminal Problems- Gramofile gaxt
2003-07-28 19:48 ` 2.6.0-test2 - Strange Terminal Problems- Gramofile UPDATE - Scheduler? gaxt
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=3F24A548.2040202@rogers.com \
--to=gaxt@rogers.com \
--cc=daiy@attbi.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;
as well as URLs for NNTP newsgroup(s).