Kernel 2.6.20-14 does not boot anymore

Bug #104232 reported by Jonathan Kempa
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.20

Starting with Kernel 2.6.20-14, my system does not boot anymore. With Kernel 2.6.20-13 everythign works fine.

Revision history for this message
Jonathan Kempa (jonikempa) wrote :
Revision history for this message
Jonathan Kempa (jonikempa) wrote :
Revision history for this message
Jonathan Kempa (jonikempa) wrote :
Revision history for this message
Alex Sidorenko (asid) wrote :

I have two similar PCs, one with IDE-only, another one with both IDE and SATA disks and using LVM (primary boot-block on /dev/hda). Only the host with noth IDE and SATA has problems - after boot there are no /dev/hd* devices created. The same host boots fine with 2.6.20-13

Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-team
status: Unconfirmed → Confirmed
Revision history for this message
Alex Sidorenko (asid) wrote :

There's a related thread on Ubuntu Forums:
http://ubuntuforums.org/showthread.php?t=402758

According to it, the kernel upgrade [2.6.20-14] makes hd devices change from /dev/hda* /dev/hdb* to /dev/mapper/sda*

A workaround suggested in that thread is not to use real devices but just UUIDs in /etc/fstab. But I wonder whether this will work when both SD and HD devices are present

Revision history for this message
magilus (magilus) wrote :

Afaik, the computer uses UUIDs.

It is a fresh Feisty Herd 5 install.

Revision history for this message
Alex Sidorenko (asid) wrote :

I used dist-upgrade from edgy->feisty. After I edited /etc/fstab manually and replaced /dev/hda* with UUID, the system boots and mounts disks - but there are still no /dev/hda* devices so this breaks hdparm and other things.

On my host I have the following HDDs: /dev/hda, /dev/sda and /dev/sdb.

Comparing 'fdisk -l' output on the same host booted single-user mode with 2.6.20-13 and 2.6.20-14 shows that with 2.6.20-14 /dev/hda -> /dev/sdc:

{root 13:33:25} diff fdisk-l-13.out fdisk-l-14.out
2,14d1
< Disk /dev/hda: 163.9 GB, 163928604672 bytes
< 255 heads, 63 sectors/track, 19929 cylinders
< Units = cylinders of 16065 * 512 = 8225280 bytes
<
< Device Boot Start End Blocks Id System
< /dev/hda1 * 1 1958 15727603+ 7 HPFS/NTFS
< /dev/hda2 1959 2695 5919952+ 83 Linux
< /dev/hda3 2696 3296 4827532+ c W95 FAT32 (LBA)
< /dev/hda4 3297 19929 133604572+ f W95 Ext'd (LBA)
< /dev/hda5 3297 8395 40957686 7 HPFS/NTFS
< /dev/hda6 8396 8518 987966 82 Linux swap / Solaris
< /dev/hda7 8519 19929 91658826 83 Linux
<
31a19,31
>
> Disk /dev/sdc: 163.9 GB, 163928604672 bytes
> 255 heads, 63 sectors/track, 19929 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sdc1 * 1 1958 15727603+ 7 HPFS/NTFS
> /dev/sdc2 1959 2695 5919952+ 83 Linux
> /dev/sdc3 2696 3296 4827532+ c W95 FAT32 (LBA)
> /dev/sdc4 3297 19929 133604572+ f W95 Ext'd (LBA)
> /dev/sdc5 3297 8395 40957686 7 HPFS/NTFS
> /dev/sdc6 8396 8518 987966 82 Linux swap / Solaris
> /dev/sdc7 8519 19929 91658826 83 Linux

Revision history for this message
Alex Sidorenko (asid) wrote :

There was another 2.6.20-14 update, but the problem is still there: all my disks and DVD devices are detected as SCSI - /dev/sd* and /dev/sc*

Revision history for this message
logicoder (logicoder) wrote :

Does not boot here too.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Brad Figg (brad-figg) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
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.