LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   An error occurred during the file system check. System unable to start (https://www.linuxquestions.org/questions/linux-newbie-8/an-error-occurred-during-the-file-system-check-system-unable-to-start-887514/)

rohitchauhan 06-21-2011 06:15 AM

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 ~]#


The entries of /etc/fstab file-
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
/dev/VolGroup00/LogVol02 /tmp ext3 defaults 1 2
/dev/VolGroup00/LogVol04 /var ext3 defaults 1 2
/dev/VolGroup00/LogVol05 /opt ext3 defaults 1 2
/dev/VolGroup00/LogVol01 /home ext3 defaults 1 2
/dev/VolGroup00/LogVol03 /usr ext3 defaults 1 2
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/LogVol06 swap swap defaults 0 0

ssrameez 06-21-2011 06:30 AM

run fdisk -l and paste the results.

chrism01 06-21-2011 06:44 PM

Quote:

/dev/VolGroup00/LogVol02: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY(i.e. , without –a or –p options)
It's telling you to fsck http://linux.die.net/man/8/fsck that LVM. Remember to umount http://linux.die.net/man/8/umount it first though...

syg00 06-21-2011 09:03 PM

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.

tailinlinux 06-21-2011 10:10 PM

Quote:

Originally Posted by rohitchauhan (Post 4391584)
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 ~]#


The entries of /etc/fstab file-
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
/dev/VolGroup00/LogVol02 /tmp ext3 defaults 1 2
/dev/VolGroup00/LogVol04 /var ext3 defaults 1 2
/dev/VolGroup00/LogVol05 /opt ext3 defaults 1 2
/dev/VolGroup00/LogVol01 /home ext3 defaults 1 2
/dev/VolGroup00/LogVol03 /usr ext3 defaults 1 2
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/LogVol06 swap swap defaults 0 0

This is very easy but to risky.:tisk:

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.

Hope this one help.

TB0ne 06-22-2011 09:24 AM

Quote:

Originally Posted by tailinlinux (Post 4392340)
This is very easy but to risky.

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?

jmba08 05-17-2018 09:52 AM

It works!
 
Hi, i tried with fsck and then reboot and my system works now.

I appreciated :)



Quote:

Originally Posted by tailinlinux (Post 4392340)
This is very easy but to risky.:tisk:

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.

Hope this one help.



All times are GMT -5. The time now is 02:32 PM.