[Bug 426398] Re: installer guesses wrong drive numbers

[Launchpad Bug Tracker]

[Expired for grub-installer (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: grub-installer (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub-installer in Ubuntu.
https://bugs.launchpad.net/bugs/426398

Title:
  installer guesses wrong drive numbers

Status in grub-installer package in Ubuntu:
  Expired

Bug description:
  Binary package hint: grub-installer

  ubiquity 1.12.12

  When trying to do a clean install of Ubuntu 9.04 AMD64, the installer
  picks the wrong drive numbers for menu.lst.

  My layout is as follows:

  /dev/sda1 - ntfs personal files
  /dev/sda2 - existing Ubuntu /home
  /dev/sda3 - junk ext3 partition

  /dev/sdb1 - Windows Vista
  /dev/sdb2 - existing Ubuntu 9.04 (x86)
  /dev/sdb5 - existing swap

  During the install, I chose to format /dev/sdb2 to replace it with the
  target install (9.04 AMD64). Upon successful installation and
  rebooting, I could boot Ubuntu just fine but trying to boot Vista gave
  an "NTLDR is missing" error.

  Turns out, as shown in the attached menu.lst generated by grub-
  installer, I have the following entry:

  title		Windows Vista (loader)
  rootnoverify	(hd1,0)
  savedefault
  makeactive
  map		(hd0) (hd1)
  map		(hd1) (hd0)
  chainloader	+1

  This makes sense if sdb1 -> hd1,0 but this is apparently not the case
  because changing the entry to:

  title		Windows Vista (loader)
  rootnoverify	(hd0,0)
  savedefault
  makeactive
  chainloader	+1

  makes Windows book properly. So, I guess the original problem is in
  the generated device.map:

  (hd0)	/dev/sda
  (hd1)	/dev/sdb

  should be vice-versa.

  The Ubuntu entries were apparently unaffected since they use UUIDs.

  Please let me know if I can provide any more information. I apologize
  if this is a duplicate, I saw other similar reports, but don't have
  the technical knowledge to determine if this is the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/426398/+subscriptions