Re: [gentoo-user] baselayout broke my system
On Sat, 2005-11-19 at 21:08 -0800, Grant wrote: Hello everyone, I updated to something like baselayout pre9-r2 a few days ago and I immediately started getting this on boot up right after Checking root filesystem: I checked /etc/fstab and it looked fine. I tried upgrading to baselayout-1.12.0_pre10-r1 with the same results. I was able to fix it by downgrading back to baselayout-1.12.0_pre9-r1. Should I just keep trying to upgrade when a new version is released and then roll back if it still breaks? That what I'd do! Also: post your results on bugzilla (under an existing bug if there is one, or make a new one) so the devs know what the issue are. This is occasionally the fun you get with ~x86 :) -- Iain Buchanan [EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] baselayout broke my system
Hello everyone, I updated to something like baselayout pre9-r2 a few days ago and I immediately started getting this on boot up right after Checking root filesystem: did you also upgrade glibc to 2.3.6? Apparently there's some behaviour with glibc and recent versions of portage that really screw things up. More info here http://bugs.gentoo.org/show_bug.cgi?id=112082 It may not be your issue, but HTH! If you ran etc-update did you check /etc/fstab I checked /etc/fstab and it looked fine. I tried upgrading to baselayout-1.12.0_pre10-r1 with the same results. I was able to fix it by downgrading back to baselayout-1.12.0_pre9-r1. Should I just keep trying to upgrade when a new version is released and then roll back if it still breaks? - Grant -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] baselayout broke my system
Am Montag, 14. November 2005 11:16 schrieb ext Grant: Hello everyone, I updated to something like baselayout pre9-r2 a few days ago and I immediately started getting this on boot up right after Checking root filesystem: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or anything else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock; e2fsck -b 8193 device Is your root fs really ext2? Did you try disabling fs check for / in /etc/fstab? Bye... Dirk -- Dirk Heinrichs | Tel: +49 (0)162 234 3408 Configuration Manager | Fax: +49 (0)211 47068 111 Capgemini Deutschland | Mail: [EMAIL PROTECTED] Hambornerstraße 55 | Web: http://www.capgemini.com D-40472 Düsseldorf | ICQ#: 110037733 GPG Public Key C2E467BB | Keyserver: www.keyserver.net pgpA9jlwAqw6v.pgp Description: PGP signature
Re: [gentoo-user] baselayout broke my system
Iain Buchanan wrote: On Mon, 2005-11-14 at 02:16 -0800, Grant wrote: Hello everyone, I updated to something like baselayout pre9-r2 a few days ago and I immediately started getting this on boot up right after Checking root filesystem: did you also upgrade glibc to 2.3.6? Apparently there's some behaviour with glibc and recent versions of portage that really screw things up. More info here http://bugs.gentoo.org/show_bug.cgi?id=112082 It may not be your issue, but HTH! If you ran etc-update did you check /etc/fstab -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] baselayout broke my system
On Mon, 2005-11-14 at 02:16 -0800, Grant wrote: Hello everyone, I updated to something like baselayout pre9-r2 a few days ago and I immediately started getting this on boot up right after Checking root filesystem: did you also upgrade glibc to 2.3.6? Apparently there's some behaviour with glibc and recent versions of portage that really screw things up. More info here http://bugs.gentoo.org/show_bug.cgi?id=112082 It may not be your issue, but HTH! -- Iain Buchanan [EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list