1

e2fsck returned error with 4

view story
linux-howto

http://forums.fedoraforum.org – After a recent system shut down I am getting the following warning e2fsck returned with 4 dracut Warning: /dev/mapper/vg_localhost-lv_root: Inodes that were part of a corrupted orphan linked list found When I type exit it starts booting with the [OK] ... statments but I do see one marked [FAILED] but it scrolls by to quickly to see. Is there a log file somewhere I could view to get more info? What should I do to correct this problem ? Thanks, Val (HowTos)

nicelinux's picture
Submitted by nicelinux on 01/11/2013

Stories similar to e2fsck returned error with 4

During each boot the recovery console is appeared.

Quote:

/dev/mapper/VolGroup-lv_root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) dracut Warning: e2fsck returned with 4 dracut Warning: /dev/mapper/VolGroup-lv_root contains a file system with errors, check forced. dracut Warning: /dev/mapper/VolGroup-lv_root: Inodes that were part

Boot Problem 51 weeks 6 days ago

I am experiencing errors when I boot up. I get some error messages and get a command prompt at the end. If I type exit at the command prompt it will then boot up.

The error messages are:

/dev/mapper/VolGroup-lv_root:

unexpected inconsistency: Run fsck manually (i.e.

Problem with booting (fsck) 23 weeks 4 days ago

Relative newb.

When switching on it fails and goes to this screen

Code: _Fedora-17-x86_6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY (ie without -a or -p options)

dracut warning: e2fsck returned with 4 dracut warning: _Fedora-17-x86_6 contains a file systen with errors, check forced dracut warning: _Fedora-17-x86_6: inodes that were part of a corrupted orphan linked list found. dracut war

How to rescue and start Fedora 31 weeks 3 days ago

Hi all,

(dual boot) Fedora 17 64bit Debian 6.0.6 64bit

On booting Fedora Code: ...... powernow-k9: try again with latest BIOS Cannot open font file True

_Fedora=17-x86_6: UNEXPECTED INCONSISTENCY: Run fsck manual. (i.e.

Fedora 16 does not boot 39 weeks 4 days ago

Hi,

I am using Fedora 16 32+ bit distro and I am getting this error when I try to boot Fedora.

[F18] Errors during the boot 9 weeks 5 days ago

During the boot phase I get the following mistakes:

Code: dracut-initqueue[310]: Warning: e2fck returned with 4 dracut-initqueue[310]: Warning: /dev/mapper/fedora_dhcpp5-root: contains errors dracut-initqueue[310]: Warning: /dev/mapper/fedora_dhcpp5-root: Inodes that were part of a corrupted  dracut-initqueue[310]: Warning: /dev/mapper/fedora_dhcpp5-root:***An Erroroccurred during t

I upgraded my F16 to F17 using the network install CD.

I had some problems during the yum installation phase and had to restart in rescue mode to clean up yum then rerun the upgrade process to get it to complete.

However on first boot I get the dracut warning and I drop out into a dracut# prompt.

dracut Warning: Unable to process initiqueue dracut Warning: /dev/mapper/vg_walden6-lv_root

Short reply: Have you run e2fsck on the partition?  Warning – do NOT run e2fsck on a mounted partition.The warning message suggests you have not enabled filesystem checking for this partition in your fstab.  Fixing your fstab would have e2fsck run automatically on a schedule.You may run e2fsck manually.  If you are uncomfortable using e2fsck at the command line, Gparted uses e2fsck

root fs error on boot 38 weeks 4 days ago

When I boot, I always get these messages:

Code: [    5.916703] EXT4-fs warning (device dm-1): ext4_clear_journal_err:4401: Filesystem error recorded from previous mount: IO failure [    5.916775] EXT4-fs warning (device dm-1): ext4_clear_journal_err:4402: Marking fs in need of filesystem check. [    5.917544] EXT4-fs (dm-1): mounted filesystem with ordered d