Dapper and Installation/Grub use different identity for SATA HDDs
Bug #44605 reported by
Phil
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.
Changed in ubiquity: | |
assignee: | nobody → seisen |
assignee: | seisen → nobody |
Changed in ubiquity: | |
status: | Invalid → Incomplete |
Changed in ubiquity: | |
status: | Incomplete → Invalid |
To post a comment you must log in.
Edgy and Feisty use UUIDs to refer to partitions... has this been backported to Dapper (yet)?