Morning

I originally posted at
fedora forums


In any case,

I was editing my security settings on files this morning, the system eventually froze up (see above post for descriptive details) and at reboot I received a read only error for the file system and it won't boot.

fsck shows no errors, and fstab shows default settings; I can't change the fstab from default b/c the entire file system if read only... all the securities are set standard, ie; files are showing up with rwxr-xr-x for example, and the global files are rwxrwxrwx.


When booting the screen below follows:


My fstab shows

fsck shows

at reboot several screens of messages scroll by, every single one of them FAILED.. for example


When searching in google for this error everyone asks to remount, but attempting to remount gives me an error that the file system is already mounted... please help!

Oh yeah,

fsck -A shows an error that I need a terminal for interactive repairs (since I'm working under the repair filesystem app) - while using the rescue Cd will mount the files unto mnt/sysimage, I can't run any applications - and the fstab is m missing? There's an mtab, but it's empty.

so, trying to umount -f /dev/VolGroup00/LogVol00 or /dev/sdb1 or /sysfs or /proc (from fstab) all give an error saying that those files are not mounted...

and trying to mount them shows that according to mtab, they are.


/etc/mtab shows

/dev/VolGroup00/LogVol00 / ext3 rw,defaults 0 0
/dev/sdb1 /boot ext3 rw,defaults 0 0
sysfs /sys sysfs rw,defaults 0 0
proc /proc proc rw,defaults 0 0


Also, I quit the repair mode by using shutdown now and it brought me up to a shell, su - and I was able to login to the terminal and view everything...

Again, I'm not really sure of the exact problem anymore; here's a repeat of the symptoms

- at boot it gives a message about MAKEDEV: makedir exists, which was not there before
- fsck shows no problems
- can't remount, unmount, or mount
- I can view all the files, login to root, but can't use command line applications
- the entire system is read only even though mtab believes its not

AAaaand I'm out of leads.

I'm going to bed. Maybe it'll be magically fixed tomorrow. All I can think off is that the crash somehow affected a system file, which means reinstall, which sucks more than I care to worry.

Man, in 8 years of using Windows crap like this never happened because of a simple crash. Restart fixed everything back in those days :P

/I keed
//sigh
///slashies