Package Search
 
Members: 353 | Topics: 767 | Posts: 3211
We welcome our newest member: ClintBarton
Info
» You aren't logged in, login or registerOnline: No members and 69 guests | Time: 15:00
Kernel too old, glibc
paldo Support Forum    paldo    General Support
Reply Reply   Subscribe Topic Subscribe Topic
11 posts found.Page: 1 2
 Kernel too old, glibc
Junior Mitglied
 
 
 
Posts: 7
Registered: 2008-01-08
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 )
Profile   Private Message
Created: 2008-01-08 23:34
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Kernel too old, glibc
Administrator
 
 
 
Posts: 426
Registered: 2004-09-09
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?
Profile   Private Message   Web
Created: 2008-01-08 23:43
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Kernel too old, glibc
Junior Mitglied
 
 
 
Posts: 7
Registered: 2008-01-08
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?
Profile   Private Message
Created: 2008-01-09 11:26 | Modified: 2008-01-09 12:00 by hackers
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Kernel too old, glibc
Administrator
 
 
 
Posts: 426
Registered: 2004-09-09
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.
Profile   Private Message   Web
Created: 2008-01-09 11:39
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Kernel too old, glibc
Junior Mitglied
 
 
 
Posts: 7
Registered: 2008-01-08
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
Profile   Private Message
Created: 2008-01-09 16:00
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Kernel too old, glibc
Administrator
 
 
 
Posts: 426
Registered: 2004-09-09
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
Profile   Private Message   Web
Created: 2008-01-09 16:06
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Kernel too old, glibc
Junior Mitglied
 
 
 
Posts: 7
Registered: 2008-01-08
it generates the script and executes but then fails on:

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

Profile   Private Message
Created: 2008-01-09 16:24
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Kernel too old, glibc
Administrator
 
 
 
Posts: 426
Registered: 2004-09-09
Try with

Code[In neuem Fenster öffnen]
upkg-bootstrap --verbose paldo-base
Profile   Private Message   Web
Created: 2008-01-09 16:31
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Kernel too old, glibc
Junior Mitglied
 
 
 
Posts: 7
Registered: 2008-01-08
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
Profile   Private Message
Created: 2008-01-09 16:34
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Kernel too old, glibc
Junior Mitglied
 
 
 
Posts: 7
Registered: 2008-01-08
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
Profile   Private Message
Created: 2008-01-09 18:39
Highlight selected Text   Edit   Delete   Quote Reply
This topic contains further posts. Next
Page: 1 2
Subscribe Topic Subscribe Topic
powered by bitron board 1.23a