From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1P1g5V-0004Ri-DL for garchives@archives.gentoo.org; Fri, 01 Oct 2010 13:55:49 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 40A47E0880; Fri, 1 Oct 2010 13:55:18 +0000 (UTC) Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by pigeon.gentoo.org (Postfix) with ESMTP id 763FBE0880 for ; Fri, 1 Oct 2010 13:55:18 +0000 (UTC) Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta14.westchester.pa.mail.comcast.net with comcast id DQs11f0061wpRvQ5ERvKZl; Fri, 01 Oct 2010 13:55:19 +0000 Received: from [192.168.1.100] ([24.3.224.125]) by omta18.westchester.pa.mail.comcast.net with comcast id DRvJ1f00m2ix0EG3eRvJr7; Fri, 01 Oct 2010 13:55:19 +0000 Message-ID: <4CA5E81D.5050304@gentoo.org> Date: Fri, 01 Oct 2010 09:54:37 -0400 From: Joseph Jezak User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100914 Lightning/1.0b3pre Thunderbird/3.1.3 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-ppc-user@lists.gentoo.org Reply-to: gentoo-ppc-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-ppc-user@lists.gentoo.org Subject: Re: [gentoo-ppc-user] yaboot has kicked my butt - 5 times?! References: <4C9AAE79.8080200@gentoo.org> <4C9B5FBE.9040604@gentoo.org> <4C9BB240.1080603@gentoo.org> <4C9C3143.2050002@gentoo.org> <4C9E1165.50307@gentoo.org> <4C9F8486.4050307@gentoo.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: eaf1ced4-39de-4789-95ea-a5e5bc92125b X-Archives-Hash: 578f0a94d312ed87874d57068fe6337d Sorry, I've had a busy week and didn't have time to respond! > OK - to me this doesn't look good: > > # mount -t procfs none /proc > mount:none has wrong device number or fs type procfs not supported Sorry, that was my mistake, I was running from memory. :) You have the right invocation below. > on the off chance you menat proc instead of procfs I tried it that way > and got a slightly more reasonable message: > > # mount -t proc none /proc > can't create lock file /etc/mtab~1038: Read-only file system (use -n > flag to override) > >> Now, try fsck.ext3 again. Does it work? >> > Worked fine. fsck.ext3 said it was clean > Cool, so now we know that fsck is fine. >> Next, let's remount the root file system read/write so we can modify files: >> # mount -o remount,rw / >> > Seemed to work. Got this message: > > EXT3-fs: (hda4):using internal journal > >> We'll copy the current mount information from proc to /etc/mtab and see >> if that helps: >> # cp /proc/self/mounts /etc/mtab >> # mount -o remount,ro / >> >> Now, try fsck.ext3 again. Does it work? >> >> If so, try rebooting the system again. Does it boot now? >> > Didn't boot but got a little farther. Doesn't complain about mtab > anymore but still complains: > > * Checking root filesystem... > fsck.ext3: No such file or directory while trying to open /dev/hda4 > /dev/hda4: > The superblock could not be read...... > > Okay, so we fixed the first thing. That's good. :) Can you attach your whole kernel config? I'm wondering if maybe udev isn't running properly due to a misconfiguration. -Joe