[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#410643: linux-image-2.6-amd64: linux fails to read partition table on boot device after upgrade from 2.6.17 to 2.6.18

severity 410643 important
reassign 410643 linux-2.6

On Mon, Feb 12, 2007 at 11:22:05AM +0100, Kuno Woudt wrote:
> Package: linux-image-2.6-amd64
> Version: 2.6.18+5
> Severity: critical
> Justification: breaks the whole system

> I have installed debian using an amd64 etch installer which installs 
> a 2.6.17 kernel (2.6.17-2-amd64).  The setup uses a 256mb boot partition,
> and everything else on a software raid (fdisk output for both disks 
> pasted below).  This all works without problem.

> After upgrading the kernel to the debian packaged 2.6.18-7, the system
> cannot read the partition table on /dev/sda.  A failure to mount /boot
> results in some error messages during boot, booting continues after
> pressing CTRL-D, the root file system (software raid, /dev/md0) is
> mounted fine, the /boot filesystem is not. Note, only the partition
> table of /dev/sda cannot be read, the output of 'fdisk /dev/sdb' is
> the same as when booted with 2.6.17.

This implies that the RAID is also being brought up in degraded mode due to
the missing component on /dev/sda.

Have you verified that under 2.6.18, the disk doesn't get renamed to
something other than /dev/sda, for some unclear reason?  I.e., do you have
any other /dev/sd* device nodes?

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Reply to: