Can not boot after upgrade

Bug #43517 reported by Peter Hopfgartner
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: linux-image-2.6-686

Machine (ASUS P2B-S, two IDE drives with software raid, XFS Filesystems) run ok until today (almost, except the missing symbols for Adaptec aic7xxx drivers).

Update with dselect as of today from linux-image-2.6.15-21 to linux-image-2.6.15-22-server.

Linux halts during boot with the following message:

RAMDISK: Compressed image found at block 0
RAMDISK: ran out of compressed data
invalid compressed format (err=1)
VFS: Cannot open root device "900" or unknown-block (9,0)
Kernel panic: Unable to mount root fs or unknown-block (9,0)

Regards,

Peter

Revision history for this message
Miguel Gaspar (ghaspias) wrote :

Could it be that you ran out of space in the /boot directory?
I use a separate boot partition, and it is too small, so now each time I need to update the kernel I must first move the init ram disk (which takes most of the space), otherwise I'm left with an unbootable state (apt deosn't get the error message from gunzip, and reports no installation error).
Always have a livecd at hand, or store a working kernel / etc. so that you can boot it manually in grub.

Revision history for this message
Peter Hopfgartner (phopfgartner) wrote : Re: [Bug 43517] Re: Can not boot after upgrade

No, I do not have a separate /boot partition and / is 9.4 GB and almost
empty.

Regards,

Peter

On 5/11/06, Miguel Gaspar <email address hidden> wrote:
>
> Could it be that you ran out of space in the /boot directory?
> I use a separate boot partition, and it is too small, so now each time I
> need to update the kernel I must first move the init ram disk (which takes
> most of the space), otherwise I'm left with an unbootable state (apt deosn't
> get the error message from gunzip, and reports no installation error).
> Always have a livecd at hand, or store a working kernel / etc. so that
> you can boot it manually in grub.
>
> --
> Can not boot after upgrade
> https://launchpad.net/bugs/43517
>

Revision history for this message
EJ Finneran (ej-finneran) wrote :

I'm getting the same error on my Dapper box. I'm using 1 IDE HD and 1 IDE DVD-RW Drive.

Recovery mode fails with the same message.

Revision history for this message
EJ Finneran (ej-finneran) wrote :

I should specify, the k7 kernel fails. I have a notebook with dapper on it and the 22 revision of the 686 kernel boots fine.

Revision history for this message
EJ Finneran (ej-finneran) wrote :

Ok, one more update.

I chrooted into the system off a boot CD and ran dpkg-reconfigure on the failed kernel and it seemed to fix the problem.

Not sure what that means but its probably worth something.

Revision history for this message
Peter Hopfgartner (phopfgartner) wrote :

Everything runs fine on this machine with the regular linux-image-2.6.15-22-686 kernel.

Peter

Revision history for this message
Ben Collins (ben-collins) wrote :

Sounds like a passing issue. Probably can't reproduce it, so closing bug report.

Changed in linux-meta:
status: Unconfirmed → Rejected
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.