Re: [gentoo-laptop] emerge broken after update gcc

[Devon Miller]

On 1/4/07, maillists <lists@×××××.net> wrote:
> On Thu, 2007-01-04 at 15:53 +0100, Jürgen Pierau wrote:
> > maillists schrieb:
> > > On Thu, 2007-01-04 at 12:32 +0100, Jürgen Pierau wrote:
> > >
> > >> maillists schrieb:
> > >>
> > >>> Hi,
> > >>>
> > >>> I just updated gcc and am running 4.1.1. but now my emerge does not work
> > >>> at all.
> > >>>
> > >>> Here is an example of trying to update portage for example:
> > >>>
> > >>> thor rbragg # emerge -a portage
> > >>> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
> > >>> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
> > >>>
> > >>>
> > >> It looks like your filesystem is mounted with the 'ro' option. Seeing
> > >> the output of 'mount' would help.
> > >>
> > >>
> > > Thanks, here is the "mount" command: As you can see I also have NFS
> > > mount some local file shares from another host. My system is
> > > on /dev/hda4. What is the "commit=0" thing?
> > >
> > > thor rbragg # mount
> > > /dev/hda4 on / type ext3 (rw,commit=0)
> > >
> > Hi Rick,
> >
> > the mount line for your / looks ok to me (don't know about the commit,
> > but afaik it shouldn't cause trouble). I'm somewhat at a loss.
> > "Read-only file system" suggests that the file system driver (ext3 in
> > this case) refuses to write to /dev/hda4. This should be reflected by a
> > 'ro' (for read-only) in the mount line. Instead, there is 'rw' which is
> > quite what it should be. It just doesn't fit the error message.
> >
> > I guess you have made sure that /var/log exists. Type 'dmesg' and check
> > the output for messages concerning hda4 or ext3/ext2. Maybe the fs
> > driver has decided to (take a) break for some reason (like fs errors,
> > read errors or some such fancy occurrence).
> >
> > C'Ya,
> > Jürgen
> >
>
> Thanks,
>
> I decided to reboot (even though I unmerged pam-login) I was forced to
> run fsck manually during boot and had alot of "orphaned inodes and tons
> of other errors on the disk.  Now it fails to start /etc/init.d/clock
> and dies. Can't even boot!
>
> This whole thing started in the middle of updating glibc, and that never
> finished. I was trying to update "emerge -auvDN system" and about 1/2
> hour into that, I got the first Read Only error...
>
> I'm hosed with the whole thing. Does anyone know when gentoo 2007.1 will
> be released?
>
> thanks again for all the help!
> rick

If you haven't started reiinstalling yet, try this (I know I've done
this on other distros, but to be honest, I haven't tried it with
Gentoo):
    assuming you're using grub
    select your boot image and press 'e'  for edit
    select the kernel line and, again,  press 'e'  for edit
    move to the end of the line and append: init=/bin/bash
    press return
    press 'b' for boot

If all goes well, it should drop you directly into a bash command prompt.
The root is probably mounted ro, so make it writable with mount -oremount,rw /
>From there you should be able to use rc-update to remove clock from
the boot run-level.
Remount root as ro before exiting the shell (mount -o remount,ro /)

dcm

-- 
gentoo-laptop@g.o mailing list