Public bug reported:
Binary package hint: grub2
Adding a new, third SATA disk and installing Mythbuntu (but NOT GRUB) to
complement Windows 7 on sda (with GRUB in the MBR) and Ubuntu 9.10 on sdb,
followed by "update-grub" produced a device.map containing:
(hd0) /dev/sda
(hd1) /dev/sdb
(hd2) /dev/sdg
Naturally booting from the third drive failed. I have no idea where the
'g' came from, but editing device.map manually to the correct 'sdc' for
hd2 restored the boot function. Obviously this action resolved my
original problem, but others may encounter this bug hence this report. A
secondary question is whether manual editing of device.map is a
preferred method, or is there an alternative?
ProblemType: Bug
Architecture: amd64
Date: Tue Dec 29 20:51:30 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: grub-pc 1.97~beta4-1ubuntu4.1
ProcEnviron:
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: grub2
Uname: Linux 2.6.31-16-generic x86_64
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug
--
device.map not correctly updated after "update-grub"
https://bugs.launchpad.net/bugs/501475
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
