Boot failure on Thinkpad R40e

Bug #445233 reported by Stefan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After installing the current beta of Kubuntu Karmic on a Thinkpad R40e i encountered the following boot error.
The message was (i think from grub) something like 'The device <long number> (e.g. 32123124234235-34534534-453) could not be found'.
I partitioned the hard disk during setup to be used only by Kubuntu (one root partitiion with ext4 (/dev/sda1) and one swap partition (/dev/sda5)).
After that message the boot process stopped.

tags: added: ubuntu-boot
Revision history for this message
Robbie Williamson (robbiew) wrote :

Did you take the default partition setup? If you did the manual setup, I think it will ask you where to install the bootloader and you have to make sure you check the box next to /dev/sda.

Can you boot to a live session using the CD or USB? If so, do this, mount your /dev/sda1 partition and copy and paste the contents of /boot/grub/grub.cfg from sda1.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
Stefan (stefan-hahne) wrote : Re: [Bug 445233] Re: Boot failure on Thinkpad R40e

Yes, i tried different partition schemes. One of them was the default
partitioning. The filesystem type (ext3/ext4) doesn't matter either.
After some googleing i did the following:

- First of all i checked that the UUIDs pointed to the correct
partition/device (using ls /dev/disks/by-uuid or something similar). But
the numbers were correct.

  - Using the live cd (which works, by the way; besides a bug with the
window decoration; i guess there is a problem with the ati graphics card
in the 40e) i re-installed grub.
- After that i had a boot menu with different boot entries (default
kernel, recovery kernel, memtest)
- Inside this boot menu i selected 'e' to edit the boot entry
- I removed all entries containing that device number (uuid) and changed
the root-kernel parameter to point to /dev/sda2

After that the loading startet but a little bit later during the kernel
initialisation stage sometimes i get a timeout and sometimes a kernel panic.

I'm not sure if it is important but if i look at the kernel messages
using 'dmesg' it always says that the bios has disabled the local apic.
Therefore i always add an additional parameter to the command line to
re-enable it (lapic). But the problems occur with or without that parameter.

So all in all i gave up installing this version on the Thinkpad 40e and
made a fall back to Kubuntu 8.10 which works flawlessly (9.04 did not
work either).

I'm sorry for not providing the content of the grub.cfg but currently
the system is running with 8.10 and i don't want to remove all the stuff
again.

Regards,
Stefan Hahne

Robbie Williamson schrieb:
> Did you take the default partition setup? If you did the manual setup,
> I think it will ask you where to install the bootloader and you have to
> make sure you check the box next to /dev/sda.
>
> Can you boot to a live session using the CD or USB? If so, do this,
> mount your /dev/sda1 partition and copy and paste the contents of
> /boot/grub/grub.cfg from sda1.
>
> ** Changed in: ubuntu
> Status: New => Confirmed
>
>
>
> ------------------------------------------------------------------------
>
>
> Eingehende eMail ist virenfrei.
> Von AVG ýberprýft - www.avg.de
> Version: 8.5.421 / Virendatenbank: 270.14.9/2428 - Ausgabedatum: 10/11/09 06:39:00
>

Revision history for this message
Mohamed Amine Ilidrissi (ilidrissi.amine) wrote :

Can you test installing Lucid or Maverick, and see if the issue is still present? Thanks!

affects: ubuntu → ubiquity (Ubuntu)
Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
tags: added: karmic
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.