Ubuntu
ubiquity package

Dapper and Installation/Grub use different identity for SATA HDDs

Bug #44605 reported by Phil
6
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

When installing Dapper Flight 7 from the install CD, it referred to my 2nd SATA HDD as sdb1, as it should have. However, when rebooting after installation, it would not boot up because grub said the filesystem was not present.

Manually editing the grub entry during boot (and /boot/grub/menu.lst to make the change permanent) to use sdc1 instead of sdb1 allowed it to boot with no problems. It seems that once installed, Dapper uses a different scheme than the installer itself to refer to SATA HDDs. The menu.lst file for grub must be edited for every subsequent linux kernel that is added as well.

I'm using an A-Bit IC7-G motherboard.

Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

Edgy and Feisty use UUIDs to refer to partitions... has this been backported to Dapper (yet)?

Revision history for this message
Phil (pmagnone) wrote : Re: [Bug 44605] Re: Dapper and Installation/Grub use different identity for SATA HDDs

Wish I could help you, but I'm using Edgy now, so I'm not sure.

On 12/12/06, Jon Anderson <email address hidden> wrote:
>
> Edgy and Feisty use UUIDs to refer to partitions... has this been
> backported to Dapper (yet)?
>
> ** Changed in: Ubuntu
> Sourcepackagename: None => ubiquity
>
> --
> Dapper and Installation/Grub use different identity for SATA HDDs
> https://launchpad.net/bugs/44605
>

Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

Dapper still uses /dev/sda1, etc., so this bug is relevant.

I can't, however, confirm it.

Revision history for this message
seisen1 (seisen-deactivatedaccount-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in ubiquity:
status: New → Invalid
seisen1 (seisen-deactivatedaccount-deactivatedaccount)
Changed in ubiquity:
assignee: nobody → seisen
assignee: seisen → nobody
seisen1 (seisen-deactivatedaccount-deactivatedaccount)
Changed in ubiquity:
status: Invalid → Incomplete
Revision history for this message
Phil (pmagnone) wrote :

I haven't had any problems with the most recent releases. Unfortunately, I
chucked that particular motherboard and CPU, so I can't test that
configuration anymore. But I think Ubuntu's use of UUIDs has pretty much
made it a non-issue.

On Thu, Jul 31, 2008 at 3:19 PM, Michael Price <email address hidden> wrote:

> ** Changed in: ubiquity (Ubuntu)
> Status: Invalid => Incomplete
>
> --
> Dapper and Installation/Grub use different identity for SATA HDDs
> https://bugs.launchpad.net/bugs/44605
> You received this bug notification because you are a direct subscriber
> of the bug.
>

seisen1 (seisen-deactivatedaccount-deactivatedaccount)
Changed in ubiquity:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.