Bug#459895: GRUB autoconfigured to an unbootable state
Package: installation-reports
Boot method: CD
Image version:
http://cdimage.debian.org/debian-cd/4.0_r1/i386/iso-cd/debian-40r1-i386-netinst.iso
Date: 30 December 22:00
Machine: home-built desktop based on Via Epia M
Processor: Via C3 900MHz
Memory : 512 MB DDR
Disk setup: 2 IDE drives, 3 SATA drives
hda: unused (I plan to remove it soon)
hdb:
hdb1 --> /boot
hdb2 --> extended
hdb4 --> swap
hdb5 --> /
sda, sdb, sdc: LVM; not assigned mountpoints during initial install
GRUB menu.lst (relevant part only):
title Debian GNU/Linux, kernel 2.6.18-5-486
root (hd1,0)
kernel /vmlinuz-2.6.18-5-486 root=/dev/hdb5 ro
initrd /initrd.img-2.6.18-5-486
savedefault
I installed GRUB on the MBR of hdb (note: SECOND IDE disk, not first). After
completing the installation and rebooting, GRUB reported "file not found"
for vmlinuz. The reason for this is that since GRUB was installed on the
second disk, hdb was assigned to (hd0) instead of (hd1). Changing the "root
(hd1,0)" line to "root (hd0,0)" made the system bootable again.
The GRUB configurator in the installer should have been sophisticated enough
to realize the drive would be re-mapped and written the menu.lst correctly.
Reply to: