Comment 3 for bug 71099

This sounds much like the 'bug' I found (I tried to find the bug report
number, but maybe it's closed and therefore I can not see it?). In the
end, with just a SATA HD in my system I installed GRUB, but
counterintuitively GRUB installed to 'hda'. I don't know anything about
GRUB, but 'hda' was how my previous ATA HD was listed. So now I have
GRUB installed to a HD in a system with no other HDs...

This 'hda' naming only seems to be an issue because the person
installing Ubuntu is allowed to change the GRUB target device name (hda)
to anything s/he wants even if the name is invalid, e.g. 'sda', and then
things get messy. Maybe the UI control for GRUB target device name could
be changed from a textbox to a dropdown menu? A dropdown menu would have
been nice when I had SATA and ATA HDs in my system, needed to pick which
HD should have GRUB installed, and had no idea what valid GRUB device
names were.

Thanks for your hard work folks.

Andy Schaumberg

richwillal wrote:
> *** This bug is a duplicate of bug 73825 ***
>
> I've seen the e-mail trail, and hope this isn't just an annoying duplicate,
> but I tried different variations after I found the manpage on grub. All of
> then resulted in the same error message. I can try again in a few days to
> replicate the conditions if it will help, but it was on an external drive
> that has been re-formatted since so I don't have the logs.
>
> Thanks,
> Rich
>
>
> On 12/1/06, Colin Watson <email address hidden> wrote:
>
>> Could you please attach /var/log/syslog and /var/log/partman to this
>> bug, by commenting on the bug's web page? Thanks in advance.
>>
>> Did you literally tell GRUB to install to "(sda)"? That's not a valid
>> GRUB device name.
>>
>> ** Changed in: ubiquity (Ubuntu)
>> Status: Unconfirmed => Needs Info
>>
>> --
>> GRUB failed to install to (sda)
>> https://launchpad.net/bugs/71099
>>
>>
>
>