LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Fedora Core 7 - RO mount but /etc/fstab shows default (https://www.linuxquestions.org/questions/linux-newbie-8/fedora-core-7-ro-mount-but-etc-fstab-shows-default-576442/)

icstepec 08-11-2007 10:23 PM

Fedora Core 7 - RO mount but /etc/fstab shows default
 
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:

Quote:


Uncompressing Linux... Ok, booting the kernel.
Red Hat nash version 6.0,9 starting
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
2 logical volume(s) in volume group "VolGroup00" now active
Welcome to Fedora
Press 'I' to enter interactive startup.
Setting clock (utc): Sat Aug 11 20:48:10 CDT 2007 [OK]
Starting udev: MAKEDEV: mkdir: File exists
MAKEDEV: mkdir: File exists.
[OK]
Setting hostname localhost6.localdomain6: [OK]
Setting up Logical Volume Management: [OK]
Checking filesystem [FAILED]

*** An error occured during the file system check.
***Dropping you to a shell; the system will reboot
*** when you leave the shell.
*** Warning -- SELinux is active
*** Disabling security enforcement for system receovery.
*** Run 'setenforce 1' to reenable.
Give root password for maintenance
(or type Control-D to continue): _


My fstab shows

Quote:


/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
dev/VolGroup00/LogVol01 swap swap defaults 00

fsck shows

Quote:

fsck 1.39 (29-may-2006)
e2fsck 1.39 (29-may-2006)
/dev/VolGroup00/lOgVol00: clean, 230861/170360832 files, 29448247/170360832 blocks
e2fsck 1.39 (29-mAY-2006)
/boot: clean, 48/26104 files, 37313/104388 blocks
at reboot several screens of messages scroll by, every single one of them FAILED.. for example

Quote:

"rm: cannot remove 'var/lock/sybsys/syslog': Read-only file system." [FAILED]

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!

icstepec 08-11-2007 10:28 PM

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.

icstepec 08-11-2007 10:51 PM

more info
 
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

icstepec 08-11-2007 11:37 PM

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


All times are GMT -5. The time now is 11:58 AM.