LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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


Reply
  Search this Thread
Old 06-21-2011, 06:15 AM   #1
rohitchauhan
Member
 
Registered: Nov 2010
Distribution: RedHat
Posts: 97

Rep: Reputation: Disabled
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
 
Old 06-21-2011, 06:30 AM   #2
ssrameez
Member
 
Registered: Oct 2006
Location: bangalore
Distribution: Fedora, Ubuntu, Debian, Redhat
Posts: 82

Rep: Reputation: 6
run fdisk -l and paste the results.
 
Old 06-21-2011, 06:44 PM   #3
chrism01
LQ Guru
 
Registered: Aug 2004
Location: Sydney
Distribution: Rocky 9.2
Posts: 18,348

Rep: Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749
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...
 
1 members found this post helpful.
Old 06-21-2011, 09:03 PM   #4
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,103

Rep: Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117
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.
 
1 members found this post helpful.
Old 06-21-2011, 10:10 PM   #5
tailinlinux
Member
 
Registered: Oct 2010
Location: Paudpod, Botolan, Zambales, Philippines
Distribution: Mandriva, Ubuntu, Mint, Open Suse, Meego
Posts: 390
Blog Entries: 3

Rep: Reputation: 25
Quote:
Originally Posted by rohitchauhan View Post
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.

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.
 
0 members found this post helpful.
Old 06-22-2011, 09:24 AM   #6
TB0ne
LQ Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 26,553

Rep: Reputation: 7946Reputation: 7946Reputation: 7946Reputation: 7946Reputation: 7946Reputation: 7946Reputation: 7946Reputation: 7946Reputation: 7946Reputation: 7946Reputation: 7946
Quote:
Originally Posted by tailinlinux View Post
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?
 
Old 05-17-2018, 09:52 AM   #7
jmba08
LQ Newbie
 
Registered: May 2018
Posts: 1

Rep: Reputation: Disabled
Thumbs up It works!

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

I appreciated



Quote:
Originally Posted by tailinlinux View Post
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.

Hope this one help.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
An error Occurred during the file system check. Dropping you to shell; the system wil aneikei Linux - Newbie 3 02-11-2010 07:38 PM
File system check on every start -- Ubuntu 9.04 ffilc7373 Linux - Newbie 2 12-18-2009 03:33 PM
An error occurred during the file system check bcbotha Fedora 1 10-23-2009 05:40 PM
An error occurred during the file system check oloijuok Linux - Newbie 3 05-29-2009 06:29 AM
"An error occurred during the file system check." JedSezZed Linux - Newbie 5 08-14-2008 12:23 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 05:53 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration