problem booting F13 kernel

Craig White craigwhite at azapple.com
Wed Jun 2 01:38:27 UTC 2010


On Tue, 2010-06-01 at 23:20 +0100, dexter wrote:
> On 1 June 2010 16:59, Craig White <craigwhite at azapple.com> wrote:
> > On Tue, 2010-06-01 at 11:46 +0530, Jayakrishnan M wrote:
> >> Craig,
> >>
> >> On Tue, Jun 1, 2010 at 5:37 AM, Craig White <craigwhite at azapple.com> wrote:
> >> <snip>
> >> > But when I booted I got an error - something like...
> >> >
> >> > kernel panic - VFS Error - can't mount filesystem hd(0,0) which should
> >> > be /boot
> >> >
> >> <snip>
> >> Please check the entries in /boot/grub/grub.conf and /etc/fstab. Since
> >> you did a yum update, the entries should be fine; but it is better to
> >> check those, just to be on the safer side.
> >> Can you please post them to the list so that others can give ideas?
> > ----
> > OK - relevant portions
> >
> > #boot=/dev/sda
> > default=0
> > timeout=5
> > splashimage=(hd0,0)/grub/splash.xpm.gz
> > hiddenmenu
> >
> > title           Fedora (2.6.33.5-112.fc13.i686)
> > root            (hd0,0)
> > kernel          /vmlinuz-2.6.33.5-112.fc13.i686 ro
> > root=UUID=7734afd9-2d2e-43fc-baa2-b8ea07cc98f7 rhgb quiet \
> >  SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
> > savedefault
> > boot
> > initrd /initramfs-2.6.33.5-112.fc13.i686.img
> >
> > title           Fedora (2.6.32.11-99.fc12.i686)
> > root            (hd0,0)
> > kernel          /vmlinuz-2.6.32.11-99.fc12.i686 ro
> > root=UUID=7734afd9-2d2e-43fc-baa2-b8ea07cc98f7 rhgb quiet \
> >  SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us \
> >  nomodeset rdblacklist=nouveau
> > initrd          /initramfs-2.6.32.11-99.fc12.i686.img
> > savedefault
> > boot
> >
> > The F13 kernel doesn't boot - gets the error (this is the exact message)
> >
> > Kernel panic-not syncing: VFS: Unable to mount root fs on
> > unknown-block(0,0)
> >
> > and /dev/sda1 (hd 0,0) is /boot and it is ext3 - nothing special and of
> > course it boots from the F12 kernel
> >
> > The F12 kernel boots - that is the only one I can use
> >
> > Craig
> 
> A shot in the dark :-)
> 
> Well that looks nearly sane from here, but I would move the initrd
> line in the F13 section to match how it is with F12 i.e before the
> boot and savedefault lines. If still no joy I would try re-generating
> initrd with dracut in /root and compare the two with lsinitrd..
----
indeed that is all it took

Of course my other issue was only remotely related - the onboard nVidia
just is so poorly supported by KMS and jumpy and unusable so I stuck in
a video card and it's working much better

Thanks

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



More information about the users mailing list