Pendrive is set as hd0, causing installation problems

Bug #152645 reported by Svein Tore Seljebotn on 2007-10-14
14
Affects Status Importance Assigned to Milestone
grub (Ubuntu)
Low
Unassigned

Bug Description

After installing Ubuntu 7.10RC from scratch I get the GRUB menu as I have with previous releases. Selecting to boot ubuntu gives a message about not being able to find anything to boot. Selecting Windows Vista (dual-boot system) I get a message about not being able to find NTLDR. Thus I have to use recovery and repair the MBR. Sorry for the scarce information, but it's hard to get much info as the system never boots. If this is something new and will be looked into, I will be able to provide more details if someone tells me how.

Note that 7.04 worked perfectly on my system.

Svein Tore Seljebotn (sveint) wrote :

After some more research I found out that GRUB got installed onto wrong HD. The reason for this is that I have to USB pen drives plugged into my computer and they were put BEFORE my SATA HD. So USB disk 1 became (hd0), USB disk 2 became (hd1) and my SATA HD became (hd2). So I reinstalled GRUB into (hd2), but that doesn't really work either as GRUB doesn't detect my USB drives at boot time so my SATA HD becomes (hd0) again and thus the entries doesn't work. Manueal editing will do it of course, but USB disks really shouldn't be set as (hd0) upon installation?

trollord (trollenlord) wrote :

That is how bios sets the order. This sort of problems have been quite common in the past. It is partially a grub problem, but with more intelligent detection the installer could force grub to work correctly in all situations.

Boniek (boniek12p) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Phillip Susi (psusi) wrote :

Closing due to lack of response ( and I'm pretty sure this was fixed long ago ).

no longer affects: ubiquity (Ubuntu)
Changed in grub (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers