VFS: Unable to mount root fs on unknown-block(1,0)

VFS: Unable to mount root fs on unknown-block(1,0)

[Eric S. Johansson]

google yields nothing except for indicating that it is a boot loader 
problem.

my dom0 partition is on a 9 GB SCSI disk drive.  I have a raid1 device 
(md0) which I have created a series of partitions via lvm2. on boot,

xm create /etc/xen/xm-single -c

I get what looks like a normal boot until

TCP: Hash tables configured (established 4096 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(1,0)
  <0>Rebooting in 1 seconds..

the configuration file defines the disk as:

disk = [ 'phy:bigraid/root_harvee,sda1,w' ]

I've tried root definitions

root = "/dev/sda1 ro"

and no root definitions.

a pointer to the documentation I should be reading would be helpful.

---eric

-- 
http://www.salon.com/books/review/2004/12/18/heloise/index.html

The basis of Abelard's philosophy, which he taught to Heloise, was
that logic had to be applied to religion in order to arrive at the
truth.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: VFS: Unable to mount root fs on unknown-block(1,0)

[Mark Williamson]

What distro are you running in the domain?

Cheers,
Mark

On Tuesday 22 February 2005 05:17, Eric S. Johansson wrote:
> google yields nothing except for indicating that it is a boot loader
> problem.
>
> my dom0 partition is on a 9 GB SCSI disk drive.  I have a raid1 device
> (md0) which I have created a series of partitions via lvm2. on boot,
>
> xm create /etc/xen/xm-single -c
>
> I get what looks like a normal boot until
>
> TCP: Hash tables configured (established 4096 bind 8192)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(1,0)
>   <0>Rebooting in 1 seconds..
>
> the configuration file defines the disk as:
>
> disk = [ 'phy:bigraid/root_harvee,sda1,w' ]
>
> I've tried root definitions
>
> root = "/dev/sda1 ro"
>
> and no root definitions.
>
> a pointer to the documentation I should be reading would be helpful.
>
> ---eric


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: VFS: Unable to mount root fs on unknown-block(1,0)

[Mark Williamson]

Are you building DevFS into the XenU kernel?  If so, don't...  If not, are you 
using the Gentoo initrd so that udev will work?

Cheers,
Mark

On Tuesday 22 February 2005 15:35, Eric S. Johansson wrote:
> Mark Williamson wrote:
> > What distro are you running in the domain?
>
> gentoo.  same as dom0. I used the instructions in the documentation to
> make a clone of the base system on the lvm partition.
>
> just a little bit more information when I actually have the root =
> /dev/sda1 in place, the failure is:
>
> VFS: Cannot open root device "sda1" or unknown-block(8,1)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(8,1)
>
> I am assuming that since root is a command line option for a kernel
> invocation, that the path it refers to is from the perspective of inside
> the kernel which means the disk translation is in place.
>
> ---eric


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: VFS: Unable to mount root fs on unknown-block(1,0)

[Eric S. Johansson]

Mark Williamson wrote:
> What distro are you running in the domain?

gentoo.  same as dom0. I used the instructions in the documentation to 
make a clone of the base system on the lvm partition.

just a little bit more information when I actually have the root = 
/dev/sda1 in place, the failure is:

VFS: Cannot open root device "sda1" or unknown-block(8,1)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(8,1)

I am assuming that since root is a command line option for a kernel 
invocation, that the path it refers to is from the perspective of inside 
the kernel which means the disk translation is in place.

---eric


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: VFS: Unable to mount root fs on unknown-block(1,0)

[Pat Lynch]

On Tue, 22 Feb 2005, Eric S. Johansson wrote:

> VFS: Cannot open root device "sda1" or unknown-block(8,1)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(8,1)
>
> I am assuming that since root is a command line option for a kernel 
> invocation, that the path it refers to is from the perspective of inside the 
> kernel which means the disk translation is in place.
>
> ---eric
>
>

Are you using the initrd image for the kernel so udev can load correctly?

Thats what I had to do to get past this point, admittedly I'm fairly new 
to Xen, but this issue seemed to be that the device node or driver didn't 
exist, and since udev handles the files in /dev, even under the 
xenoserver, then you would have to load the initrd image as well.

-Pat

-- 
Pat Lynch					   plynch@bsdunix.net


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: VFS: Unable to mount root fs on unknown-block(1,0)

[Eric S. Johansson]

Mark Williamson wrote:
> Are you building DevFS into the XenU kernel?  If so, don't... 

ok I will change that.  Maybe I should just convert the entire system to 
udev

> If not, are you 
> using the Gentoo initrd so that udev will work?

not yet but I'm sure I will have more questions by then.

---eric

-- 
http://www.salon.com/books/review/2004/12/18/heloise/index.html

The basis of Abelard's philosophy, which he taught to Heloise, was
that logic had to be applied to religion in order to arrive at the
truth.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: VFS: Unable to mount root fs on unknown-block(1,0)

[M.A. Williamson]

> > Are you building DevFS into the XenU kernel?  If so, don't... 
> 
> ok I will change that.  Maybe I should just convert the entire system to 
> udev

You definitely need to avoid DevFS in domUs - the Xen virtual device 
drivers don't support DevFS (nor are they likely to, since DevFS is now 
deprecated). It works OK in dom0 because dom0 doesn't rely on the virtual 
device drivers to operate.

> > If not, are you 
> > using the Gentoo initrd so that udev will work?
> 
> not yet but I'm sure I will have more questions by then.

Ask away!

Good luck,
Mark

> ---eric
> 
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click