Ubuntu
firestarter package

kernel panic after edgy upgrade

Bug #68652 reported by Ali
This bug report is a duplicate of:  Bug #67028: Could not install "firestarter". Edit Remove
10
Affects Status Importance Assigned to Milestone
firestarter (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I did not find a suitable bug, so I will post this as new.

I upgraded yesterday to edgy from dapper using
"sudo update-manager -c -d"

because of the slow speed (<50kb/s) I killed the upgrade process, changed the repository location to de.archive.ubuntu.com and rerun the update.

It was not possible to do it with "sudo update-manager -c -d" so I used "gksu update-manager -c".

After downloading all packages and installing them there were two problems, which said, that the install process went wrong. But the installation keeps on running.

When the upgrade had finished, I rebootet the systems and got the following error message:

[17179570.772000] kernel panic - not syncing: VFS - unable to mount root fs on unknown-block(0,0).

See original description
Tags: edgy-upgrade
Revision history for this message
Ali (allad1) wrote :

the main log

description: updated
Revision history for this message
Caroline Ford (secretlondon) wrote :

The errors at the end of the log are:

2006-10-26 23:51:19,671 ERROR got an error from dpkg for pkg: 'firestarter': 'subprocess post-installation script returned error exit status 2
'
2006-10-26 23:57:22,373 DEBUG got a conffile-prompt from dpkg for file: '/etc/gdm/gdm.conf-custom'
2006-10-26 23:58:07,814 ERROR SystemError from cache.commit(): installArchives() failed

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Can you please also attach the file /var/log/dist-upgrade/term.log to the bugreport? The problem during the upgrade is caused by the firestarter package, I will reassign to it. But the term.log file should give us a idea why the kernel failed when rebooting.

Thanks,
 michael

Changed in update-manager:
status: Unconfirmed → Needs Info
Revision history for this message
Ali (allad1) wrote :

Sorry micheal.

I had to delete my linux partition and so deleted the log files, too. I did not find any hints in the file, so I did not make a copy of it. There were no entries for 27.10.2006 or later.

Sorry

Ali

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs which you find.

Revision history for this message
Acitta (acitta1) wrote :

I got the same kernel panic. It seemed to be the result of the Kernel not being upgraded to the latest. I was able to upgrade the kernel by booting from an old Ubuntu CD and chrooting to the proper partition. I also had the firestarter problem.

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

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

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

Other bug subscribers

Bug attachments

Remote bug watches

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