Xen users - Apr 2007 - mount: could not find filesystem ''/dev/root''

Hi there. I got a kernel panic caused by <mount: could not find
filesystem ''/dev/root''> when I tried to install xen from
the sources
(to compile modules on my own).

Now I have installed in my system Fedora Core 5 the following kernels:

2.6.20
2.6.20-1 xen0
2.6.16 xen
2.6.18-1 xen0
2.6.15

All of the kernels run ok except the 2.6.16 xen kernel, it causes the
kernel panic on boot. I downloaded this from the repositories in
http://xenbits.xensource.com/, the xen-3.0.3-testing.hg; I used
mercurial to get a copy.

I followed the Readme so I did

make world
make install

Then I had in my /boot what we ned to boot except the initrd. I made
it twice and none of them worked:

-mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod
initrd-2.6.16.29-xen.img 2.6.16.29-xen      -> that''s the Readme way
-mkinitrd initrd-2.6.16.29-xen.img 2.6.16.29-xen       -> when the
Readme didn''t work

I have no idea what the problem can be, if something similar occured
to anyone or anyone can give me a light about this problem it would be
a great help.

If someone needs more details about my configuration or else just ask me please.

One last thing, before the kernel panic occurs a warning appears. This
is about "unsupported acesses", it sais that there is a problem with
the /lib/tls and that because of this the system may run slow. If
someone believe that this is important I can copy here the exact
message.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 4/7/07, Ismael Hasan Romero <kraziest@gmail.com>
wrote:
> Hi there. I got a kernel panic caused by <mount: could not find
> filesystem ''/dev/root''> when I tried to install xen
from the sources
> (to compile modules on my own).
The key error is probably in the drivers loaded prior to the above message...
> -mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod
> initrd-2.6.16.29-xen.img 2.6.16.29-xen      -> that''s the
Readme way
On a whim, try "--preload=aacraid"?
Is aacraid the scsi_hostadapter in /etc/modules.conf, and used by the
other /etc/grub.conf sections that work correctly?
> One last thing, before the kernel panic occurs a warning appears. This
> is about "unsupported acesses", it sais that there is a problem
with
> the /lib/tls and that because of this the system may run slow. If
> someone believe that this is important I can copy here the exact
> message.
Hmm, that''s "normal", but usually independent of the
filesystem error.
That may play in, though, as you''ve compiled from source? I''m
not
sure...

jerry

-- 
"Oh joy! Rapture! I''ve got a brain"
-Scarecrow

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Can you please post your grub.conf section for this kernel? I think the
initrd you are specifying in your grub.conf doesnt have the drivers to mount
your root fs. Try creating the mkinitrd the README way, except dont put the
aacraid part in the command.

-prabhakar


On 4/7/07, Ismael Hasan Romero <kraziest@gmail.com>
wrote:
>
> Hi there. I got a kernel panic caused by <mount: could not find
> filesystem ''/dev/root''> when I tried to install xen
from the sources
> (to compile modules on my own).
>
> Now I have installed in my system Fedora Core 5 the following kernels:
>
> 2.6.20
> 2.6.20-1 xen0
> 2.6.16 xen
> 2.6.18-1 xen0
> 2.6.15
>
> All of the kernels run ok except the 2.6.16 xen kernel, it causes the
> kernel panic on boot. I downloaded this from the repositories in
> http://xenbits.xensource.com/, the xen-3.0.3-testing.hg; I used
> mercurial to get a copy.
>
> I followed the Readme so I did
>
> make world
> make install
>
> Then I had in my /boot what we ned to boot except the initrd. I made
> it twice and none of them worked:
>
> -mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod
> initrd-2.6.16.29-xen.img 2.6.16.29-xen      -> that''s the
Readme way
> -mkinitrd initrd-2.6.16.29-xen.img 2.6.16.29-xen       -> when the
> Readme didn''t work
>
> I have no idea what the problem can be, if something similar occured
> to anyone or anyone can give me a light about this problem it would be
> a great help.
>
> If someone needs more details about my configuration or else just ask me
> please.
>
> One last thing, before the kernel panic occurs a warning appears. This
> is about "unsupported acesses", it sais that there is a problem
with
> the /lib/tls and that because of this the system may run slow. If
> someone believe that this is important I can copy here the exact
> message.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

That''s my grub.conf for this systems:

title Fedora Core (2.6.16.29.fc5xen)
        root (hd0,1)
        kernel /boot/xen-3.0.3-0.gz
        module /boot/vmlinuz-2.6.16.29-xen ro root=LABEL=/1 rhgb quiet
        module /boot/initrd-2.6.16.29-xen.img
title Fedora Core (2.6.16.38.fc5xen)
        root (hd0,1)
        kernel /boot/xen-3.0.4-1.gz
        module /boot/vmlinuz-2.6.16.38-xen ro root=LABEL=/1 rhgb quiet
        module /boot/initrd-2.6.16.38-xen.img
title Fedora Core (2.6.16.38.fc5xen0)
        root (hd0,1)
        kernel /boot/xen-3.0.4-1.gz
        module /boot/vmlinuz-2.6.16.38-xen0 ro root=LABEL=/1 rhgb quiet
        module /boot/initrd-2.6.16.38-xen0.img
title Fedora Core (2.6.16.29.fc5xen0)
        root (hd0,1)
        kernel /boot/xen-3.0.3-0.gz
        module /boot/vmlinuz-2.6.16.29-xen0 ro root=LABEL=/1 rhgb quiet
        module /boot/initrd-2.6.16.29-xen0.img


I tried installing the xen3.0.4, the 3.0.4 dom0 and the 3.0.3 dom0. I
did what you say about initrd (without aacraid option). With both dom0
it can start, but it cannot run the graphical mode and in the logs
appears a "failed to initialize core devices", so I''m
begining to
think that I can have a wrong .config. Any suggestion is well
received.

Thanks for answering

On 4/8/07, Prabhakar Chaganti <pchaganti@gmail.com>
wrote:
> Can you please post your grub.conf section for this kernel? I think the
> initrd you are specifying in your grub.conf doesnt have the drivers to
mount
> your root fs. Try creating the mkinitrd the README way, except dont put the
> aacraid part in the command.
>
> -prabhakar
>
>
> On 4/7/07, Ismael Hasan Romero <kraziest@gmail.com> wrote:
> >
> > Hi there. I got a kernel panic caused by <mount: could not find
> > filesystem ''/dev/root''> when I tried to install
xen from the sources
> > (to compile modules on my own).
> >
> > Now I have installed in my system Fedora Core 5 the following kernels:
> >
> > 2.6.20
> > 2.6.20-1 xen0
> > 2.6.16 xen
> > 2.6.18-1 xen0
> > 2.6.15
> >
> > All of the kernels run ok except the 2.6.16 xen kernel, it causes the
> > kernel panic on boot. I downloaded this from the repositories in
> > http://xenbits.xensource.com/, the xen-3.0.3-testing.hg; I used
> > mercurial to get a copy.
> >
> > I followed the Readme so I did
> >
> > make world
> > make install
> >
> > Then I had in my /boot what we ned to boot except the initrd. I made
> > it twice and none of them worked:
> >
> > -mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod
> > initrd-2.6.16.29-xen.img 2.6.16.29-xen      -> that''s the
Readme way
> > -mkinitrd initrd-2.6.16.29-xen.img 2.6.16.29-xen       -> when the
> > Readme didn''t work
> >
> > I have no idea what the problem can be, if something similar occured
> > to anyone or anyone can give me a light about this problem it would be
> > a great help.
> >
> > If someone needs more details about my configuration or else just ask
me
> please.
> >
> > One last thing, before the kernel panic occurs a warning appears. This
> > is about "unsupported acesses", it sais that there is a
problem with
> > the /lib/tls and that because of this the system may run slow. If
> > someone believe that this is important I can copy here the exact
> > message.
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I tried also installing the xen3.0.4, the 3.0.4 dom0 and the 3.0.3
dom0. With both dom0 it can start, but it cannot run the graphical
mode and in the logs appears a "failed to initialize core devices", so
I''m begining to think that I can have a wrong .config. Any suggestion
is well received.

On 4/8/07, Jerry Amundson <jamundso@gmail.com>
wrote:
> On 4/7/07, Ismael Hasan Romero <kraziest@gmail.com> wrote:
> > Hi there. I got a kernel panic caused by <mount: could not find
> > filesystem ''/dev/root''> when I tried to install
xen from the sources
> > (to compile modules on my own).
>
> The key error is probably in the drivers loaded prior to the above
message...
I searched and before the /dev/root problem happens a cannot load lib/sd_mod.ko

>
> > -mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod
> > initrd-2.6.16.29-xen.img 2.6.16.29-xen      -> that''s the
Readme way
>
> On a whim, try "--preload=aacraid"?
> Is aacraid the scsi_hostadapter in /etc/modules.conf, and used by the
> other /etc/grub.conf sections that work correctly?
>
I tried this (--preload) but it doesn''t change the problem. I have no
> > One last thing, before the kernel panic occurs a warning appears. This
> > is about "unsupported acesses", it sais that there is a
problem with
> > the /lib/tls and that because of this the system may run slow. If
> > someone believe that this is important I can copy here the exact
> > message.
>
> Hmm, that''s "normal", but usually independent of the
filesystem error.
> That may play in, though, as you''ve compiled from source?
I''m not
> sure...
I did what the warning says (mv /lib/tsl) and the warning still appears.
> jerry
>
> --
> "Oh joy! Rapture! I''ve got a brain"
> -Scarecrow
>
Thanks for answering

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

So everything works but X? I remember seeing a similar issue with X not
working when you compile Xen 3.0.4 from source on Fedora Core 6. You may
want to check the fedora-xen mailing list archive to see if anyone else as
reported this issue with X.


On 4/8/07, Ismael <kraziest@gmail.com> wrote:
>
> That''s my grub.conf for this systems:
>
> title Fedora Core (2.6.16.29.fc5xen)
>         root (hd0,1)
>         kernel /boot/xen-3.0.3-0.gz
>         module /boot/vmlinuz-2.6.16.29-xen ro root=LABEL=/1 rhgb quiet
>         module /boot/initrd-2.6.16.29-xen.img
> title Fedora Core (2.6.16.38.fc5xen)
>         root (hd0,1)
>         kernel /boot/xen-3.0.4-1.gz
>         module /boot/vmlinuz-2.6.16.38-xen ro root=LABEL=/1 rhgb quiet
>         module /boot/initrd-2.6.16.38-xen.img
> title Fedora Core (2.6.16.38.fc5xen0)
>         root (hd0,1)
>         kernel /boot/xen-3.0.4-1.gz
>         module /boot/vmlinuz-2.6.16.38-xen0 ro root=LABEL=/1 rhgb quiet
>         module /boot/initrd-2.6.16.38-xen0.img
> title Fedora Core (2.6.16.29.fc5xen0)
>         root (hd0,1)
>         kernel /boot/xen-3.0.3-0.gz
>         module /boot/vmlinuz-2.6.16.29-xen0 ro root=LABEL=/1 rhgb quiet
>         module /boot/initrd-2.6.16.29-xen0.img
>
>
> I tried installing the xen3.0.4, the 3.0.4 dom0 and the 3.0.3 dom0. I
> did what you say about initrd (without aacraid option). With both dom0
> it can start, but it cannot run the graphical mode and in the logs
> appears a "failed to initialize core devices", so I''m
begining to
> think that I can have a wrong .config. Any suggestion is well
> received.
>
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 4/8/07, Ismael <kraziest@gmail.com> wrote:
> I tried also installing the xen3.0.4, the 3.0.4 dom0 and the 3.0.3
> dom0. With both dom0 it can start, but it cannot run the graphical
> mode and in the logs appears a "failed to initialize core
devices", so
> I''m begining to think that I can have a wrong .config. Any
suggestion
> is well received.
Ok, maybe one problem is your question...
http://www.catb.org/~esr/faqs/smart-questions.html

Generally, there are four (4) options for you , yet you seem to have
done about seven (7) different things. :-)
> > The key error is probably in the drivers loaded prior to the above
message...
> I searched and before the /dev/root problem happens a cannot load
lib/sd_mod.ko
Well, you think that might be a problem? (hint: answer "yes, that
would be a problem")
> > On a whim, try "--preload=aacraid"?
> > Is aacraid the scsi_hostadapter in /etc/modules.conf, and used by the
> > other /etc/grub.conf sections that work correctly?
> >
> I tried this (--preload) but it doesn''t change the problem. I have
no
What of, do you "have no"?

> I did what the warning says (mv /lib/tsl) and the warning still appears.
Then you didn''t do what the warning says.

Back to your four (4) options:
1. Xen and kernel from Fedora
2. Xen and kernel from XenSource
3. Stable source
4. Unstable source

I all cases, the initrd image needs to work with your hardware.
Maybe start from the beginning with 1. - and "yum update", as none of
the grub entries above are even current.

jerry

-- 
"Oh joy! Rapture! I''ve got a brain"
-Scarecrow

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 4/8/07, Prabhakar Chaganti <pchaganti@gmail.com>
wrote:
> So everything works but X? I remember seeing a similar issue with X not
> working when you compile Xen 3.0.4 from source on Fedora Core 6. You may
> want to check the fedora-xen mailing list archive to see if anyone else as
> reported this issue with X.
>
>
Ok, I''ll do, thanks a lot

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 4/8/07, Jerry Amundson <jamundso@gmail.com>
wrote:
> On 4/8/07, Ismael <kraziest@gmail.com> wrote:
> > I tried also installing the xen3.0.4, the 3.0.4 dom0 and the 3.0.3
> > dom0. With both dom0 it can start, but it cannot run the graphical
> > mode and in the logs appears a "failed to initialize core
devices", so
> > I''m begining to think that I can have a wrong .config. Any
suggestion
> > is well received.
>
> Ok, maybe one problem is your question...
> http://www.catb.org/~esr/faqs/smart-questions.html
>
> Generally, there are four (4) options for you , yet you seem to have
> done about seven (7) different things. :-)
>
> > > The key error is probably in the drivers loaded prior to the
above message...
> > I searched and before the /dev/root problem happens a cannot load
lib/sd_mod.ko
>
> Well, you think that might be a problem? (hint: answer "yes, that
> would be a problem")
>
I was surprised when I saw it, I didn''t remember seeing it the first
time. Another person answered here that when making the initrd image I
just try to ignore the aacraid option; so I was making the latest init
images with this:

mkinitrd -v -f --with=sd_mod --with=scsi_mod
initrd-2.6.16.29-xen.img 2.6.16.29-xen

instead of :
mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod
initrd-2.6.16.29-xen.img 2.6.16.29-xen

When I use mkinitrd just as the readme says (the second way) there is
no error loading lib/sd_mod.ko
> > > On a whim, try "--preload=aacraid"?
> > > Is aacraid the scsi_hostadapter in /etc/modules.conf, and used by
the
> > > other /etc/grub.conf sections that work correctly?
> > >
> > I tried this (--preload) but it doesn''t change the problem. I
have no
>
> What of, do you "have no"?
>
I eat some words here, I don''t know why. I have no a /etc/modules.conf
archive.
>
> > I did what the warning says (mv /lib/tsl) and the warning still
appears.
>
> Then you didn''t do what the warning says.
>
I eat words again here, sorry. I did <mv /lib/tsl /lib/tsl.disabled>.
> Back to your four (4) options:
> 1. Xen and kernel from Fedora
> 2. Xen and kernel from XenSource
> 3. Stable source
> 4. Unstable source
>
> I all cases, the initrd image needs to work with your hardware.
> Maybe start from the beginning with 1. - and "yum update", as
none of
> the grub entries above are even current.
>
> jerry
>
I tried to download Xen sources from Fedora page but I didn''t find it,
so I''ll use the second option
> --
> "Oh joy! Rapture! I''ve got a brain"
> -Scarecrow
>
thanks for answering

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 4/8/07, Ismael <kraziest@gmail.com> wrote:
> I tried to download Xen sources from Fedora page but I didn''t find
it,
> so I''ll use the second option
The first option didn''t mention sources. Just try "yum upgrade
kernel-xen xen".

jerry

-- 
"Oh joy! Rapture! I''ve got a brain"
-Scarecrow

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users