I did my semi-weekly upgrade (successfully) Tues morn (5/10) and then rebooted Tues evening, unsuccessfully. During boot I get several messages about touch failing because it is a read-only file system. Finally hangs with

Starting system logger: line 930: rc.sysinit /var/log/dmesg:Read-only file system

I'm currently running off a knoppix disc, have run fsck on the drive a couple of times, can mount the drive in knoppix and read/write to it no problem. Have tried to boot some older kernels, all with same results.

This is the kernel version I'm trying to boot

2.6.10-1.770_FC3

Any help would be greatly appreciated.

maybe it will be helpfull if you post your yum /whatever log file with those updates... or try FC4t3

Had a similar problem when doing a "yum update" yesterday. Looks like something gets confused when remounting the filesystem RW (I only have a small installation with a single "/" filesystem)

In my case I managed to get the system to boot again by modifying /etc/rc.sysinit this way:
[hallvard@paviljong ~]$ diff /etc/rc.sysinit /etc/rc.sysinit.org
479c479
< action $"Remounting root filesystem in read-write mode: " mount -n -o remount,rw /dev/hda5 /
---
> action $"Remounting root filesystem in read-write mode: " mount -n -o remount,rw /

/dev/hda5 is my root filesystem.

(But I get some errormessage about LABEL=/ being a duplicate and so on when shutting down, so I guess I have not compleatly solved the problem)

--
Hallvard

strange maybe you should look for saved files by updates the *.rpmsave or similar beeing from last days - because such files are made when the author decides that the old config is not proper for the new release but nobody tells you that in the first place if such files were created which is awful