| 1 |
On Thu, 2007-01-04 at 15:53 +0100, Jürgen Pierau wrote: |
| 2 |
> maillists schrieb: |
| 3 |
> > On Thu, 2007-01-04 at 12:32 +0100, Jürgen Pierau wrote: |
| 4 |
> > |
| 5 |
> >> maillists schrieb: |
| 6 |
> >> |
| 7 |
> >>> Hi, |
| 8 |
> >>> |
| 9 |
> >>> I just updated gcc and am running 4.1.1. but now my emerge does not work |
| 10 |
> >>> at all. |
| 11 |
> >>> |
| 12 |
> >>> Here is an example of trying to update portage for example: |
| 13 |
> >>> |
| 14 |
> >>> thor rbragg # emerge -a portage |
| 15 |
> >>> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log' |
| 16 |
> >>> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log' |
| 17 |
> >>> |
| 18 |
> >>> |
| 19 |
> >> It looks like your filesystem is mounted with the 'ro' option. Seeing |
| 20 |
> >> the output of 'mount' would help. |
| 21 |
> >> |
| 22 |
> >> |
| 23 |
> > Thanks, here is the "mount" command: As you can see I also have NFS |
| 24 |
> > mount some local file shares from another host. My system is |
| 25 |
> > on /dev/hda4. What is the "commit=0" thing? |
| 26 |
> > |
| 27 |
> > thor rbragg # mount |
| 28 |
> > /dev/hda4 on / type ext3 (rw,commit=0) |
| 29 |
> > |
| 30 |
> Hi Rick, |
| 31 |
> |
| 32 |
> the mount line for your / looks ok to me (don't know about the commit, |
| 33 |
> but afaik it shouldn't cause trouble). I'm somewhat at a loss. |
| 34 |
> "Read-only file system" suggests that the file system driver (ext3 in |
| 35 |
> this case) refuses to write to /dev/hda4. This should be reflected by a |
| 36 |
> 'ro' (for read-only) in the mount line. Instead, there is 'rw' which is |
| 37 |
> quite what it should be. It just doesn't fit the error message. |
| 38 |
> |
| 39 |
> I guess you have made sure that /var/log exists. Type 'dmesg' and check |
| 40 |
> the output for messages concerning hda4 or ext3/ext2. Maybe the fs |
| 41 |
> driver has decided to (take a) break for some reason (like fs errors, |
| 42 |
> read errors or some such fancy occurrence). |
| 43 |
> |
| 44 |
> C'Ya, |
| 45 |
> Jürgen |
| 46 |
> |
| 47 |
|
| 48 |
Thanks, |
| 49 |
|
| 50 |
I decided to reboot (even though I unmerged pam-login) I was forced to |
| 51 |
run fsck manually during boot and had alot of "orphaned inodes and tons |
| 52 |
of other errors on the disk. Now it fails to start /etc/init.d/clock |
| 53 |
and dies. Can't even boot! |
| 54 |
|
| 55 |
This whole thing started in the middle of updating glibc, and that never |
| 56 |
finished. I was trying to update "emerge -auvDN system" and about 1/2 |
| 57 |
hour into that, I got the first Read Only error... |
| 58 |
|
| 59 |
I'm hosed with the whole thing. Does anyone know when gentoo 2007.1 will |
| 60 |
be released? |
| 61 |
|
| 62 |
thanks again for all the help! |
| 63 |
rick |
| 64 |
|
| 65 |
> |
| 66 |
|
| 67 |
|
| 68 |
-- |
| 69 |
gentoo-laptop@g.o mailing list |
Archives