[Bug 501475] Re: device.map not correctly updated after "update-grub"
Phillip Susi
psusi at ubuntu.com
Fri Jul 20 18:51:38 UTC 2012
I'm going to call this one fixed since we did get rid of device.map.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/501475
Title:
device.map not correctly updated after "update-grub"
Status in “grub2” package in Ubuntu:
Fix Released
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/501475/+subscriptions
More information about the foundations-bugs
mailing list