|
|||||||||||
|
Bug#459895: GRUB autoconfigured to an unbootable state
From: Jack Gruendler <jack.gruendler(at)gmail.com>
Date: Mon Dec 31 2007 - 12:23:37 EST
Boot method: CD
Machine: home-built desktop based on Via Epia M
Processor: Via C3 900MHz
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)
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. -- To UNSUBSCRIBE, email to debian-boot-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Wed Jan 9 07:42:13 2008 This archive was generated by hypermail 2.1.8 : Wed Mar 19 2008 - 04:08:02 EDT |
||||||||||
|
|||||||||||