[SOLVED] system:unexpected inconsistency; RUN fsck Manually

nitsss · 07-25-2016, 05:27 AM

Hi,

i m using artica proxy & now stuck during startup. Actually my lan card was not working so i restart the proxy 3-4 times after replugh the lan card & it works. But now it gives me an error.

system:UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
(i.e., without -a or -p options)
fsck died with exit status 4
failed (code 4)
[...] An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. the fsck should be performed in maintenance mode with the root filesystem mount in read-only mode... failed!
[...] The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press Control-D to terminate maintenance shell & restart the system.
Give root password for maintenance
(or type Control-D to continue):

also when i give root password, it gives me shell.

root@(none):~#
i also tried with mount -o remount,rw /

please help me....

amilo · 07-25-2016, 06:20 AM

I presume you powerd yoer system off without give it an desent shutdown or init 0 command.
Check on witch device your root normal is mounted.
Reboot your system with a resqeue cd.
Perform a fsck on your root device.

Reboot.

pan64 · 07-25-2016, 06:20 AM

so what did you try?

malekmustaq · 07-25-2016, 07:37 AM

Quote:

m using artica proxy & now stuck during startup. Actually my lan card was not working so i restart the proxy 3-4 times after replugh the lan card & it works. But now it gives me an error.
system:UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
(i.e., without -a or -p options)
fsck died with exit status 4
failed (code 4)

Error Code 4 means the filesystem is left uncorrected. (This happens when fsck is hesitant to alter anything for some predetermined reason. For example if the the partition to be corrected is mounted or the root partition which cannot be unmounted.)

I met this error many times. My solution is usually to boot the machine using a live CD (this will allow me to work while the root partition in the hard drive is not mounted and fsck may no longer be hesitant to correct it.) From the LiveCD when booted you may now bring up a terminal and examine if the hard drive partition is there.

Code:

fdisk -l

if you see the partition then you may now make it a target:

Code:

fsck -a /dev/sda1 <if that is in your case, or /dev/sda{X} whatever number you have actually>

If the "-a" option remains hesitant, then you better use the "-y" option, to automate a "yes" answer in the interactive. For example "fsck -y /dev/sda{n}" at least fsck proceeds without you needing to press "yes" each correction.

BE CAREFUL IF YOU HAVE CRITICAL AND IMPORTANT DATA. AND IF YOU ARE RUNNING RAID YOU MUST NEED SEARCH ALTERNATIVE SOLUTION FIRST.

Hope that helps. Good luck.

m.m.