ian_smart
5th March 2007, 04:10 PM
Hi, I'm pretty new to linux and hope my question is in the right place - apologies if I should be using a different forum.
Anyway, I've had FC6 installed on my pc for a month or so now without any problems until today. Some updates got loaded which required a reboot and during the reboot I now get an error during the "Checking filesystems" phase.
I get the message... (apologies for slight typos - I'm copying this from another screen!)
*** an error occurrred 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 recovery
*** run 'setenforce 1' to reenable
I log on with my root password and get the prompt:
(Repair filesystem) 1 #
Having looked around the forums here and elsewhere I've tried running fsck which comes back very quickly with a message saying that
/boot: clean
/dev/VolGroup00/LogVol00: clean
there's other stuff about version numbers and file and block counts too. which is long so I haven't included it here.
If I then reboot it's groundhog day again!
Can anyone suggest what I should try next?
TIA, Ian
Anyway, I've had FC6 installed on my pc for a month or so now without any problems until today. Some updates got loaded which required a reboot and during the reboot I now get an error during the "Checking filesystems" phase.
I get the message... (apologies for slight typos - I'm copying this from another screen!)
*** an error occurrred 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 recovery
*** run 'setenforce 1' to reenable
I log on with my root password and get the prompt:
(Repair filesystem) 1 #
Having looked around the forums here and elsewhere I've tried running fsck which comes back very quickly with a message saying that
/boot: clean
/dev/VolGroup00/LogVol00: clean
there's other stuff about version numbers and file and block counts too. which is long so I haven't included it here.
If I then reboot it's groundhog day again!
Can anyone suggest what I should try next?
TIA, Ian