[Dapper] Wrong disc enumeration when installing (or updating from Breezy)

Bug #49211 reported by Fnx
2
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hello,

I am reporting a bug encounter for both new installation from the Dapper 6.06 liveCD and (dist-) upgrading from a fully functionnal Breezy install.
After upgrade, the computer is unable to start again. It boots but the system crash during mount of the local partitions.

My system (Athlon XP [686] on a Asus Abit NF-7S motherboard) has three hard drives connected through an inboard IDE controller and a PCI Silicon Graphic 680 IDE controller.
Before installation and for other linux distro the disc enumeration is as follow
Grub Dapper Disk
hd0 /dev/hda WD (onboard IDE0)
hd1 /dev/hde Maxtor (PCI Sil680 IDE0)
hd2 /dev/hdg IBM (PCI Sil680 IDE1)
             /dev/hdc DVD Drive (onboard IDE1)

For Dapper 6.06, my system is recognize as follow
Grub Dapper Disk
hd0 /dev/hde WD (onboard IDE0)
hd1 /dev/hda Maxtor (PCI Sil680 IDE0)
hd2 /dev/hdc IBM (PCI Sil680 IDE1)
             /dev/hdg DVD Drive (onboard IDE1)

Firstly, I strongly suspected a grub error, but by checking the partitions numbers for each disk, I managed to check that before the start of the linux kernel, grub detects the disk in the correct order (as listed above).
The file /boot/grub/device.map looks also correct (Breezy after Dapper update)
(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/hde
(hd2) /dev/hdg

For me this problem is critical, since it prevent Dapper to start.
It might be also a security issue, since during linux start, other partitions not linked with ubuntu are mistakaly mounted and data could be erased or altered.

NB: I think this bug is related with Bug #6367 and Bug #40993.

Fnx (td-safemail-tmp)
description: updated
Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 49211] [[Dapper] Wrong disc enumeration when installing (or updating from Breezy)

 unsubscribe ubuntu-security

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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