Scenario: Running 'emerge -u world' One of the ebuild items is the latest 'ext2progs'. emerge quits with a "can't find ls:" message. Attempted reboot results in kernel panic message above. "/" is ext3 based. "/" is mountable and appears to be intact when booting off of the 1.4-rc1 iso and toms boot linux. Current recovery method: Move root hard disc to secondary position. Insert new primary hard disk. Build new copy of gentoo on new hard disk (I used reiserfs). Mount old disk and retrieve data. So far, this has happened to three different people including myuself.
Note: I was running 'emerge -u world' from an xterm window while in kde.
I don't remember what the error message was when ebuilding, and I can't be absolutely certain it has to do with e2fsprogs, but this happened to me to while emerge -u world on my Gentoo 1.4rc1 system, while I was in X windows (in an aterm, in OpenBox 2.1.3). The system seemed to lose track of where my root partition was. Upon examining /etc/fstab (with rescue disk) I found fstab had entries like "/dev/ROOT" instead of /dev/hda3, but I don't actually think this is a problem (but some in #gentoo said it was). No avail changing fstab. Kernel is definitely booting with correct "root=" option (/dev/hda3 in my case).
*sigh* Note: http://forums.gentoo.org/viewtopic.php?t=21077
you could have always booted with a livecd and attempted a repair of system that way ... chroot-ing, rebuilding of kernel, etc...
I've confirmed the following: ldd /sbin/init libc.so.6 => /usr/lib/libc.so.6 (0x2aac6000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaab000) And there is no libc.so.6 on my system. I'm going to try booting a liveCD and such, but am quite a newbie. This bug is likely a portage bug, something about unmerging glibc when you're not supposed to.
what version of glibc do you guys have installed ?
chroot to the old root partition and then run `qpkg glibc` ... if you dont have `qpkg` then `emerge gentoolkit`
Please note: everywhere I said 'ext2progs' I meant to say 'e2fsprogs'. I've already fdisked my old drive and re-partitioned it as a single partition. I've also formatted it for reiserfs. It is now dedictated as my /pub directory. I 'emerge -pu world' and usually 'emerge -u world' at least weekly. Often twice a week. So I'm fairly certain that the version of glibc I was running was the second to last one. (or there abouts anyway depending on how fast changes have been made.) If you roll back to November 11th to the 14th, the then state of portage would be representative of my system prior to the emerge which gave me problems. Sorry I can't provide more information. This is my critical system and I couldn't take any risks with the data nor could I let it stay down long. :(
FYI: My immediate problem is somewhat fixed, currently bootstrapping a new system. Summary of this bug should be changed. Upon rebooting system, init can't find libc.so.6 causing a kernel panic. It seems impossible to chroot to the old system from rescue, because all the shells expect this library.
modified to include new additional info in the summary line. See RGM's last post.
So whats going on with this? Reopen it if it is still an issue.
