[SOLVED] An error occurred during the file system check. System unable to start
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
An error occurred during the file system check. System unable to start
Hi friends,
I am having a problem while starting the Linux (RHEL 5.3).The system is unable to start. Following message is shown on the screen. Please take a look
Starting udev: [OK]
Loading default keymap(us): [OK]
Setting hostname rc [OK]
Setting up Logical Volume Management:7logical volume(s) in volume group VolGroup00 now active [OK]
Checking filesystems
/dev/VolGroup00/LogVol00: clean, 26960/7864320 files, 867567/7864320 blocks
/dev/VolGroup00/LogVol02: wxt3 recovery flag is clear, but journal has data.
/dev/VolGroup00/LogVol02: run journal anyway
/dev/VolGroup00/LogVol02: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY(i.e. , without a or p options)
/dev/VolGroup00/LogVol04: clean, 86 / .. files, 280 /192 blocks
/dev/VolGroup00/LogVol05: clean, 11/78 files, / . blocks
/dev/VolGroup00/LogVol01: clean, 11/78 files, / . Blocks
/boot: clean, ../ files, / . Blocks
[FAILED]
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
Bash: /usr/bin/id: No such file or directory
Bash: [: =: unary operator expected
[root@rc ~]#
It's /tmp - generally I'd say "who cares ?". Do you (routinely) expect files on /tmp to survive across re-boot - how often do you clean it up ?.
I'd just remount /tmp to tmpfs and reformat that lv. Could be checked, but why bother if you are going to force corrective actions on it. You lose confidence in the files anyway.
Personally I'd leave /tmp on the tmpfs, but that may depend on volume.
Hi friends,
I am having a problem while starting the Linux (RHEL 5.3).The system is unable to start. Following message is shown on the screen. Please take a look
Starting udev: [OK]
Loading default keymap(us): [OK]
Setting hostname rc [OK]
Setting up Logical Volume Management:7logical volume(s) in volume group VolGroup00 now active [OK]
Checking filesystems
/dev/VolGroup00/LogVol00: clean, 26960/7864320 files, 867567/7864320 blocks
/dev/VolGroup00/LogVol02: wxt3 recovery flag is clear, but journal has data.
/dev/VolGroup00/LogVol02: run journal anyway
/dev/VolGroup00/LogVol02: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY(i.e. , without a or p options)
/dev/VolGroup00/LogVol04: clean, 86 / .. files, 280 /192 blocks
/dev/VolGroup00/LogVol05: clean, 11/78 files, / . blocks
/dev/VolGroup00/LogVol01: clean, 11/78 files, / . Blocks
/boot: clean, ../ files, / . Blocks
[FAILED]
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
Bash: /usr/bin/id: No such file or directory
Bash: [: =: unary operator expected
[root@rc ~]#
Type your root password.
Then type "fsck"
then Enter.
System will ask you to fix all the badblocks.
type "y" for yes. Then Enter.
System Display: "System Successfully Modified or something like that then it will ask you to reboot your computer"
Then Your computer will be fixed.
Uhh...why is it risky, exactly??? It's only risky to fsck a MOUNTED volume...if the system is in maintenance mode, following chrism01's advice will get it going. Also, the system is TELLING the OP how to fix the system, and you're omitting a few things.
First, just typing in "fsck" (as you say), will check ALL the file systems in the fstab file, which may (or may not) cause other problems. Second, without the "-a" flag to automatically fix error(s) found, the OP may be sitting there for half an hour or so, just pressing "Y". And after exiting the repair shell, the system will reboot automatically (as it says clearly in the OP's message), without asking anything. Again, if you're going to try to answer a question, please answer it accurately. Telling someone it'll say "something like that", doesn't give someone much guidance, and if the OP follows what you said, it could cause further problems.
OP, one thing that is of concern is how the /tmp file system got a corrupted journal? Was the system shut down uncleanly, and do you see any hardware fault lights on, or see anything in your system logs to indicate a disk failure?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.