I've just compiled a new kernel, but when I reboot grub will not load the new
kernel. I get error 15 (file not found). But the file is there.
Yes grub is install properly and yes the boot partition was mounted when I
copied the new kernel across and changed the grub.conf. What's really
confusing me is there's no syntax error in the grub.conf that I can see, and
the first kernel on the list boots fine. Anyone got any cluse as to why grub
can't see the second kernel?
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Dr. Matthew R. Lee
Instituto Biologia Marina 'Jurgen Winter'
Universidad Austral de Chile
Campus Isla Teja
Valdivia
matt@matthewlee.org
URL: meiochile.matthewlee.org
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
--
gentoo-user@lists.gentoo.org mailing list
07-05-2008, 11:15 PM
Mick
grub boot problem
On Sunday 06 July 2008, Matthew R. Lee wrote:
> I've just compiled a new kernel, but when I reboot grub will not load the
> new kernel. I get error 15 (file not found). But the file is there.
> Yes grub is install properly and yes the boot partition was mounted when I
> copied the new kernel across and changed the grub.conf. What's really
> confusing me is there's no syntax error in the grub.conf that I can see,
> and the first kernel on the list boots fine. Anyone got any cluse as to
> why grub can't see the second kernel?
>
> [grub.conf]
> default 0
>
> timeout 30
>
> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
>
> title=Gentoo 2.6.22-r2
>
> root (hd0,0)
> kernel /boot/kernel-2.6.22-r2-2 root=/dev/sda3
> video=vesafb:mtrr,ywrap,1280x800-24@70
>
> title=Gentoo 2.6.24-r8
>
> root (hd0,0)
> kernel /boot/kernel-2.6.24-r8 root=/dev/sda3
> video=vesafb:mtrr,ywrap,1280x800-24@70
Could you please show us:
$ mount
and
# ls -la /boot
--
Regards,
Mick
07-05-2008, 11:38 PM
"Matthew R. Lee"
grub boot problem
On Saturday 05 July 2008 19:15:05 Mick wrote:
> On Sunday 06 July 2008, Matthew R. Lee wrote:
> > I've just compiled a new kernel, but when I reboot grub will not load the
> > new kernel. I get error 15 (file not found). But the file is there.
> > Yes grub is install properly and yes the boot partition was mounted when
> > I copied the new kernel across and changed the grub.conf. What's really
> > confusing me is there's no syntax error in the grub.conf that I can see,
> > and the first kernel on the list boots fine. Anyone got any cluse as to
> > why grub can't see the second kernel?
> >
> > [grub.conf]
> > default 0
> >
> > timeout 30
> >
> > splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> >
> > title=Gentoo 2.6.22-r2
> >
> > root (hd0,0)
> > kernel /boot/kernel-2.6.22-r2-2 root=/dev/sda3
> > video=vesafb:mtrr,ywrap,1280x800-24@70
> >
> > title=Gentoo 2.6.24-r8
> >
> > root (hd0,0)
> > kernel /boot/kernel-2.6.24-r8 root=/dev/sda3
> > video=vesafb:mtrr,ywrap,1280x800-24@70
>
> Could you please show us:
>
> $ mount
>
> and
>
> # ls -la /boot
/dev/sda3 on / type ext3 (rw,noatime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec)
udev on /dev type tmpfs (rw,nosuid)
devpts on /dev/pts type devpts (rw,nosuid,noexec)
shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85)
/dev/sda1 on /boot type ext2 (rw)
I should probably give /boot a clean, but could this be the problem?
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Dr. Matthew R. Lee
Instituto Biologia Marina 'Jurgen Winter'
Universidad Austral de Chile
Campus Isla Teja
Valdivia
matt@matthewlee.org
URL: meiochile.matthewlee.org
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
--
gentoo-user@lists.gentoo.org mailing list
07-05-2008, 11:47 PM
Matt Harrison
grub boot problem
Matthew R. Lee wrote:
On Saturday 05 July 2008 19:15:05 Mick wrote:
On Sunday 06 July 2008, Matthew R. Lee wrote:
I've just compiled a new kernel, but when I reboot grub will not load the
new kernel. I get error 15 (file not found). But the file is there.
Yes grub is install properly and yes the boot partition was mounted when
I copied the new kernel across and changed the grub.conf. What's really
confusing me is there's no syntax error in the grub.conf that I can see,
and the first kernel on the list boots fine. Anyone got any cluse as to
why grub can't see the second kernel?
/dev/sda3 on / type ext3 (rw,noatime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec)
udev on /dev type tmpfs (rw,nosuid)
devpts on /dev/pts type devpts (rw,nosuid,noexec)
shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85)
/dev/sda1 on /boot type ext2 (rw)
I should probably give /boot a clean, but could this be the problem?
According to your grub.conf your default is the top entry, but the
kernel image for that doesn't exist in your boot partition.
kernel /boot/kernel-2.6.22-r2-2 root=/dev/sda3
should probably be
kernel /boot/kernel-2.6.22-r2 root=/dev/sda3
Thats if 2.6.22-r2 is the kernel your trying to boot.
HTH
Matt
--
gentoo-user@lists.gentoo.org mailing list
07-05-2008, 11:59 PM
Dale
grub boot problem
Matt Harrison wrote:
Matthew R. Lee wrote:
On Saturday 05 July 2008 19:15:05 Mick wrote:
On Sunday 06 July 2008, Matthew R. Lee wrote:
I've just compiled a new kernel, but when I reboot grub will not
load the
new kernel. I get error 15 (file not found). But the file is there.
Yes grub is install properly and yes the boot partition was mounted
when
I copied the new kernel across and changed the grub.conf. What's
really
confusing me is there's no syntax error in the grub.conf that I can
see,
and the first kernel on the list boots fine. Anyone got any cluse
as to
/dev/sda3 on / type ext3 (rw,noatime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec)
udev on /dev type tmpfs (rw,nosuid)
devpts on /dev/pts type devpts (rw,nosuid,noexec)
shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
usbfs on /proc/bus/usb type usbfs
(rw,noexec,nosuid,devmode=0664,devgid=85)
I should probably give /boot a clean, but could this be the problem?
According to your grub.conf your default is the top entry, but the
kernel image for that doesn't exist in your boot partition.
kernel /boot/kernel-2.6.22-r2-2 root=/dev/sda3
should probably be
kernel /boot/kernel-2.6.22-r2 root=/dev/sda3
Thats if 2.6.22-r2 is the kernel your trying to boot.
HTH
Matt
Hi,
Another thing you can try is tab completion in the grub menu. Just hit
the "e" key twice and let grub help you with what kernels it can see.
Hope that helps.
Dale
:-) :-)
--
gentoo-user@lists.gentoo.org mailing list
07-06-2008, 12:13 AM
"Matthew R. Lee"
grub boot problem
On Saturday 05 July 2008 19:47:10 Matt Harrison wrote:
> Matthew R. Lee wrote:
> > On Saturday 05 July 2008 19:15:05 Mick wrote:
> >> On Sunday 06 July 2008, Matthew R. Lee wrote:
> >>> I've just compiled a new kernel, but when I reboot grub will not load
> >>> the new kernel. I get error 15 (file not found). But the file is there.
> >>> Yes grub is install properly and yes the boot partition was mounted
> >>> when I copied the new kernel across and changed the grub.conf. What's
> >>> really confusing me is there's no syntax error in the grub.conf that I
> >>> can see, and the first kernel on the list boots fine. Anyone got any
> >>> cluse as to why grub can't see the second kernel?
> >>>
> >>> [grub.conf]
> >>> default 0
> >>>
> >>> timeout 30
> >>>
> >>> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> >>>
> >>> title=Gentoo 2.6.22-r2
> >>>
> >>> root (hd0,0)
> >>> kernel /boot/kernel-2.6.22-r2-2 root=/dev/sda3
> >>> video=vesafb:mtrr,ywrap,1280x800-24@70
> >>>
> >>> title=Gentoo 2.6.24-r8
> >>>
> >>> root (hd0,0)
> >>> kernel /boot/kernel-2.6.24-r8 root=/dev/sda3
> >>> video=vesafb:mtrr,ywrap,1280x800-24@70
> >>
> >> Could you please show us:
> >>
> >> $ mount
> >>
> >> and
> >>
> >> # ls -la /boot
> >
> > /dev/sda3 on / type ext3 (rw,noatime)
> > proc on /proc type proc (rw)
> > sysfs on /sys type sysfs (rw,nosuid,nodev,noexec)
> > udev on /dev type tmpfs (rw,nosuid)
> > devpts on /dev/pts type devpts (rw,nosuid,noexec)
> > shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
> > usbfs on /proc/bus/usb type usbfs
> > (rw,noexec,nosuid,devmode=0664,devgid=85) /dev/sda1 on /boot type ext2
> > (rw)
> >
> > total 17256
> > drwxr-xr-x 5 root root 1024 Jul 5 18:28 .
> > drwxr-xr-x 21 root root 4096 Dec 29 2007 ..
> > drwxr-xr-x 4 root root 1024 Aug 16 2007 boot
> > -rw-r--r-- 1 root root 37395 Dec 25 2006 config-2.6.18-r5
> > -rw-r--r-- 1 root root 35286 Dec 28 2006 config-2.6.18-r6
> > -rw-r--r-- 1 root root 29907 Jul 19 2007 config-2.6.21-r4
> > -rw-r--r-- 1 root root 39449 Aug 4 2007 config-2.6.22-r2
> > -rw-r--r-- 1 root root 44583 Jul 5 18:48 config-2.6.24-r8
> > -rw-r--r-- 1 root root 44541 Jun 23 18:25 config-2.6.25-r5
> > drwxr-xr-x 2 root root 1024 Jun 23 17:02 grub
> > -rw-r--r-- 1 root root 486761 Oct 7 2006 initrd.img-2.6.17-sata
> > -rw-r--r-- 1 root root 1637016 Dec 25 2006 kernel-2.6.18-r5
> > -rw-r--r-- 1 root root 1606118 Dec 28 2006 kernel-2.6.18-r6
> > -rw-r--r-- 1 root root 1916280 Jul 19 2007 kernel-2.6.21-r4
> > -rw-r--r-- 1 root root 1740624 Aug 4 2007 kernel-2.6.22-r2
> > -rw-r--r-- 1 root root 1847000 Jul 5 18:48 kernel-2.6.24-r8
> > -rw-r--r-- 1 root root 2952220 Jun 23 18:24 kernel-2.6.25-r5
> > drwx------ 2 root root 12288 Dec 27 2007 lost+found
> > -rw-r--r-- 1 root root 738926 Dec 25 2006 system.map-2.6.18-r5
> > -rw-r--r-- 1 root root 712206 Dec 28 2006 system.map-2.6.18-r6
> > -rw-r--r-- 1 root root 813409 Jul 19 2007 system.map-2.6.21-r4
> > -rw-r--r-- 1 root root 810321 Aug 4 2007 system.map-2.6.22-r2
> > -rw-r--r-- 1 root root 870491 Jul 5 18:48 system.map-2.6.24-r8
> > -rw-r--r-- 1 root root 1183038 Jun 23 18:25 system.map-2.6.25-r5
> >
> > I should probably give /boot a clean, but could this be the problem?
>
> According to your grub.conf your default is the top entry, but the
> kernel image for that doesn't exist in your boot partition.
>
> kernel /boot/kernel-2.6.22-r2-2 root=/dev/sda3
>
> should probably be
>
> kernel /boot/kernel-2.6.22-r2 root=/dev/sda3
>
> Thats if 2.6.22-r2 is the kernel your trying to boot.
>
> HTH
>
> Matt
This is wierd, I hadn't noticed that, but that's not causing the problem.
I'm running the 2.6.22-r2 kernel now, that's the one that boots, the 2.6.24-r8
is the one grub can't find.
Matt
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Dr. Matthew R. Lee
Instituto Biologia Marina 'Jurgen Winter'
Universidad Austral de Chile
Campus Isla Teja
Valdivia
matt@matthewlee.org
URL: meiochile.matthewlee.org
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
--
gentoo-user@lists.gentoo.org mailing list
07-06-2008, 12:27 AM
Volker Armin Hemmann
grub boot problem
one question:
why don't you use 'make install' and have a 'vmlinuz' and 'vmlinuz.old' entry
in menu.lst/grub.conf?
that solves/prevents lots of errors.
--
gentoo-user@lists.gentoo.org mailing list
07-06-2008, 12:33 AM
"Matthew R. Lee"
grub boot problem
On Saturday 05 July 2008 20:13:20 Matthew R. Lee wrote:
> On Saturday 05 July 2008 19:47:10 Matt Harrison wrote:
> > Matthew R. Lee wrote:
> > > On Saturday 05 July 2008 19:15:05 Mick wrote:
> > >> On Sunday 06 July 2008, Matthew R. Lee wrote:
> > >>> I've just compiled a new kernel, but when I reboot grub will not load
> > >>> the new kernel. I get error 15 (file not found). But the file is
> > >>> there. Yes grub is install properly and yes the boot partition was
> > >>> mounted when I copied the new kernel across and changed the
> > >>> grub.conf. What's really confusing me is there's no syntax error in
> > >>> the grub.conf that I can see, and the first kernel on the list boots
> > >>> fine. Anyone got any cluse as to why grub can't see the second
> > >>> kernel?
> > >>>
> > >>> [grub.conf]
> > >>> default 0
> > >>>
> > >>> timeout 30
> > >>>
> > >>> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> > >>>
> > >>> title=Gentoo 2.6.22-r2
> > >>>
> > >>> root (hd0,0)
> > >>> kernel /boot/kernel-2.6.22-r2-2 root=/dev/sda3
> > >>> video=vesafb:mtrr,ywrap,1280x800-24@70
> > >>>
> > >>> title=Gentoo 2.6.24-r8
> > >>>
> > >>> root (hd0,0)
> > >>> kernel /boot/kernel-2.6.24-r8 root=/dev/sda3
> > >>> video=vesafb:mtrr,ywrap,1280x800-24@70
> > >>
> > >> Could you please show us:
> > >>
> > >> $ mount
> > >>
> > >> and
> > >>
> > >> # ls -la /boot
> > >
> > > /dev/sda3 on / type ext3 (rw,noatime)
> > > proc on /proc type proc (rw)
> > > sysfs on /sys type sysfs (rw,nosuid,nodev,noexec)
> > > udev on /dev type tmpfs (rw,nosuid)
> > > devpts on /dev/pts type devpts (rw,nosuid,noexec)
> > > shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
> > > usbfs on /proc/bus/usb type usbfs
> > > (rw,noexec,nosuid,devmode=0664,devgid=85) /dev/sda1 on /boot type ext2
> > > (rw)
> > >
> > > total 17256
> > > drwxr-xr-x 5 root root 1024 Jul 5 18:28 .
> > > drwxr-xr-x 21 root root 4096 Dec 29 2007 ..
> > > drwxr-xr-x 4 root root 1024 Aug 16 2007 boot
> > > -rw-r--r-- 1 root root 37395 Dec 25 2006 config-2.6.18-r5
> > > -rw-r--r-- 1 root root 35286 Dec 28 2006 config-2.6.18-r6
> > > -rw-r--r-- 1 root root 29907 Jul 19 2007 config-2.6.21-r4
> > > -rw-r--r-- 1 root root 39449 Aug 4 2007 config-2.6.22-r2
> > > -rw-r--r-- 1 root root 44583 Jul 5 18:48 config-2.6.24-r8
> > > -rw-r--r-- 1 root root 44541 Jun 23 18:25 config-2.6.25-r5
> > > drwxr-xr-x 2 root root 1024 Jun 23 17:02 grub
> > > -rw-r--r-- 1 root root 486761 Oct 7 2006 initrd.img-2.6.17-sata
> > > -rw-r--r-- 1 root root 1637016 Dec 25 2006 kernel-2.6.18-r5
> > > -rw-r--r-- 1 root root 1606118 Dec 28 2006 kernel-2.6.18-r6
> > > -rw-r--r-- 1 root root 1916280 Jul 19 2007 kernel-2.6.21-r4
> > > -rw-r--r-- 1 root root 1740624 Aug 4 2007 kernel-2.6.22-r2
> > > -rw-r--r-- 1 root root 1847000 Jul 5 18:48 kernel-2.6.24-r8
> > > -rw-r--r-- 1 root root 2952220 Jun 23 18:24 kernel-2.6.25-r5
> > > drwx------ 2 root root 12288 Dec 27 2007 lost+found
> > > -rw-r--r-- 1 root root 738926 Dec 25 2006 system.map-2.6.18-r5
> > > -rw-r--r-- 1 root root 712206 Dec 28 2006 system.map-2.6.18-r6
> > > -rw-r--r-- 1 root root 813409 Jul 19 2007 system.map-2.6.21-r4
> > > -rw-r--r-- 1 root root 810321 Aug 4 2007 system.map-2.6.22-r2
> > > -rw-r--r-- 1 root root 870491 Jul 5 18:48 system.map-2.6.24-r8
> > > -rw-r--r-- 1 root root 1183038 Jun 23 18:25 system.map-2.6.25-r5
> > >
> > > I should probably give /boot a clean, but could this be the problem?
> >
> > According to your grub.conf your default is the top entry, but the
> > kernel image for that doesn't exist in your boot partition.
> >
> > kernel /boot/kernel-2.6.22-r2-2 root=/dev/sda3
> >
> > should probably be
> >
> > kernel /boot/kernel-2.6.22-r2 root=/dev/sda3
> >
> > Thats if 2.6.22-r2 is the kernel your trying to boot.
> >
> > HTH
> >
> > Matt
>
> This is wierd, I hadn't noticed that, but that's not causing the problem.
> I'm running the 2.6.22-r2 kernel now, that's the one that boots, the
> 2.6.24-r8 is the one grub can't find.
> Matt
Ok,
I figured out the problem, but no why it's happened. If you look at the output
of ls -la /boot there is another folder /boot and within this a symlink /boot
(./) By copying the kernel to this folder and modifiying the grub.conf in the
associated /grub folder the the new kernel boots.
Question is how did I come to have a cascade of boot folders and how do I get
things back the way they should be?
Matt
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Dr. Matthew R. Lee
Instituto Biologia Marina 'Jurgen Winter'
Universidad Austral de Chile
Campus Isla Teja
Valdivia
matt@matthewlee.org
URL: meiochile.matthewlee.org
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
--
gentoo-user@lists.gentoo.org mailing list
07-06-2008, 07:05 AM
Dirk Heinrichs
grub boot problem
Am Sonntag, 6. Juli 2008 schrieb Matthew R. Lee:
> > > >>> [grub.conf]
> > > >>> default 0
> > > >>>
> > > >>> timeout 30
> > > >>>
> > > >>> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> > > >>>
> > > >>> title=Gentoo 2.6.22-r2
> > > >>>
> > > >>> root (hd0,0)
> > > >>> kernel /boot/kernel-2.6.22-r2-2 root=/dev/sda3
> > > >>> video=vesafb:mtrr,ywrap,1280x800-24@70
> > > >>>
> > > >>> title=Gentoo 2.6.24-r8
> > > >>>
> > > >>> root (hd0,0)
> > > >>> kernel /boot/kernel-2.6.24-r8 root=/dev/sda3
> > > >>> video=vesafb:mtrr,ywrap,1280x800-24@70
>
> Ok,
> I figured out the problem, but no why it's happened. If you look at the
> output of ls -la /boot there is another folder /boot and within this a
> symlink /boot (./) By copying the kernel to this folder and modifiying the
> grub.conf in the associated /grub folder the the new kernel boots.
> Question is how did I come to have a cascade of boot folders and how do I
> get things back the way they should be?
Don't know how you got there, but to get things back to normal you should
remove /boot/boot and make it a symlink to /boot:
grub boot problem
