cancel
Showing results for 
Search instead for 
Did you mean: 
klara
Level 10

Unexpected Inconsistency; run fsck manually

Jump to solution

Hi everyone,

I got this error in a Web Gateway 4000 with version 7.2 after a electric power failure...  " /dev/mapper/vg00-opt: Unexpected Inconsistency; run fsck manually"

error-web-gateway.JPG

When we insert the root password the Web gateway shows repair filesystem promt, we can't  get a feedback file or even try for a shutdown -rF now.  Nothing works

error-web-gateway.JPG

We can't see the file /opt/mwg..  the error was Not such file  or directory.

error-feedback-mwg.JPG

To resolve the issue we execute this command fsck  /dev/mapper/vg00-opt  and power cycle the web gateway,  after that the Web gateway start again without problems.

I post this issue because I want to have more information about the commands we can execute to resolve this kind of problem,  like a CLI documentation or something like that..

Thanks a lot for your support

0 Kudos
1 Solution

Accepted Solutions

Re: Unexpected Inconsistency; run fsck manually

Jump to solution

MWG appliance is based on a redhat compatible linux distribution. The file system check you saw there is part of the basic operating system. It detected an inconsistency in the file system - caused by the power failure - and asked for manual repair because the file system check might encounter errors it is not able to resolve automatically. Running fsck was the right solution there.

Next time consider using "fsck -y /dev/...", -y will try to auto-repair any corruptions that it finds. A human expert might do a better job, but auto-repair is faster and in most cases you need an "expert" expert to make better decisions than the tool. If the tool encounters any situation it cannot resolve safely it will still ask for guidance.

MWG tools are located on a separate partition, /opt. At the time of file system check these partition are not mounted into the file system tree. Running feedback script wouldn't have helped anyway, it doesn't collect any meaningful information about filesystem state.

0 Kudos
2 Replies

Re: Unexpected Inconsistency; run fsck manually

Jump to solution

MWG appliance is based on a redhat compatible linux distribution. The file system check you saw there is part of the basic operating system. It detected an inconsistency in the file system - caused by the power failure - and asked for manual repair because the file system check might encounter errors it is not able to resolve automatically. Running fsck was the right solution there.

Next time consider using "fsck -y /dev/...", -y will try to auto-repair any corruptions that it finds. A human expert might do a better job, but auto-repair is faster and in most cases you need an "expert" expert to make better decisions than the tool. If the tool encounters any situation it cannot resolve safely it will still ask for guidance.

MWG tools are located on a separate partition, /opt. At the time of file system check these partition are not mounted into the file system tree. Running feedback script wouldn't have helped anyway, it doesn't collect any meaningful information about filesystem state.

0 Kudos
klara
Level 10

Re: Unexpected Inconsistency; run fsck manually

Jump to solution

Hi Ed,

Thanks a lot for your response.

0 Kudos