Hi,

Please help me!!

I've upkg-upgraded my system. Now it doesn't boot anymore. It stops with "Kernel too old". I've heard it has to do it glibc but I'm not sure.

Also, when I choose an older kernel in grub, it can boot but cannot mount my root partition in write mode. It says I should run e2fsck which I did.

What should I do?

(Before that, paldo was running on that machine for more than 2 years )

The current glibc package in paldo requires linux 2.6.17 or later, while we currently have 2.6.23 in the repository. Do you get that error message when starting with 2.6.23 or can't you start 2.6.23 for some reason?

The newest version (this version results in the Kernel too old panic) in grub is:
paldo stable (linux 2.6.16.23-paldo1)

I have older kernels in grub which I can run without kernel panics, but then I cannot run upkg... (it gives some glibc error)

What shall I do?

Hm, I suspect that the upgrade broke due to the very old kernel. Skipping 5 paldo releases when upgrading the system was one release too late, apparently.

You should be able to recover your system by booting from a recent Rescue or Live CD, mounting your system at /upkg and run upkg-upgrade after entering chroot with upkg-chroot.

I did with the live cd:

Zitat

mount /dev/sda1 /upkg upkg-chroot /upkg

and it gives:

Code	[In neuem Fenster öffnen]
Entering chroot... chroot: cannot run command '/bin/bash': no such file or directory returned from chroot

The system seems to be severly broken. Try the following outside chroot after mounting with the Live CD:

Code	[In neuem Fenster öffnen]
upkg-bootstrap paldo-base

it generates the script and executes but then fails on:

*** ERROR: upkg-watch-x86-glibc-2.6-gcc-4.2-1-0.248-1

Try with

Code	[In neuem Fenster öffnen]
upkg-bootstrap --verbose paldo-base

ok, I've just run upkg-check and it gives a lot of wrong md5 hashes and read errors, all related to packages with glibc-2.6.

I'm running e2fsck now, and then I'll try to do that verbose thing you suggested

ok, so, when it executes the script (after I chose Y to install the recommended packages) it fails:

the last lines:

Installing upkg-watch-0.248-1 (stable)...
... (some stuff)
[CHECK] mount --bind /dev /upkg/dev
[CHECK] mount --bind /dev/pts /upkg/dev/pts
[CHECK] mount --bind /proc /upkg/proc
[CHECK] mount --bind /sys /upkg/sys
[CHECK] mount --bind /var/cache/upkg /upkg/var/cache/upkg
chroot: cannot run command '/usr/bin/env': No such file or directory
*** ERROR: upkg-watch-x86-glibc-2.6-gcc-4.2-1-0.248-1