Bug#361180: [mykrowatt@comcast.net: Re: Bug#361180: Debian installer doesn't install kernel]
----- Forwarded message from Jack Carroll <mykrowatt@comcast.net> -----
Date: Fri, 7 Apr 2006 17:08:45 -0400
From: Jack Carroll <mykrowatt@comcast.net>
To: Frans Pop <aragorn@tiscali.nl>
Cc: stappers@debian.org, control@bugs.debian.org
Subject: Re: Bug#361180: Debian installer doesn't install kernel
Two of you replied to my bug report. I'll send my replies to both
of you.
I should mention that the April 6 daily build of the floppy images
does not include a boot.img. It only has root.img, cd-drivers.img, and
net-drivers.img. I took that to mean that boot.img is unchanged from the
Etch RC2 floppies, and used that.
I previously ran a test with a set of RC2 floppies, and that failed
to install either choice of initrd tools. So I tried the daily build.
On Fri, Apr 07, 2006 at 01:21:50PM +0200, Frans Pop wrote:
> On Friday 07 April 2006 06:23, Jack Carroll wrote:
>
> > Booted the previously installed system in /dev/hda1 (Debian Sarge,
> > kernel 2.6.8-686). Mounted /dev/hda2 and examined /boot on that
> > partition. No kernel, initrd, or System.map files present, only a grub
> > directory. The progress bars said it was installing the kernel, but
> > it's not there.
>
> Impossible. If the installer cannot install the kernel, it will fail in a
> big way. They _have_ been installed, just not where you are looking.
>
> Try running the installation again and, after the base-installation phase
> has finished, switch to VT2 (using alt-F2) and ls /target/boot. You
> should see the kernel there.
> Do the same after bootloader installation.
/target is mounted on /dev/hda2 as expected. /target/var is mounted on
/dev/hda6.
During kernel download, ls /target/boot shows
System.map-2.6.15-1-686
config-2.6.15-1-686
initrd.img-2.6.15-1-686.new
vmlinuz-2.6.15-1-686
At the end of kernel download, all those files have been
automatically deleted. /target/var/cache/apt/archives lists the
linux-image-2.6-686 package under a couple of names.
I tried rebooting at that point so I could mount the target
partitions on the good Sarge installation on /dev/hda1 and search the target
partitions to see if the kernel had been moved somewhere, but GRUB had been
hosed. I could probably boot with a generic GRUB floppy.
Clearly something is wrong. Is it worthwhile to run more tests, or
is it invalid because the current daily builds don't include a boot.img of
their own?
----- End forwarded message -----
Reply to: