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 data mode. Opts: (null)
[ 6.086195] dracut: Checking ext4: /dev/mapper/vg_elmer-lv_root
[ 6.086460] dracut: issuing e2fsck -a /dev/mapper/vg_elmer-lv_root
[ 13.545587] dracut: /dev/mapper/vg_elmer-lv_root contains a file system with errors, check forced.
[ 13.545824] dracut: /dev/mapper/vg_elmer-lv_root: 105694/260096 files (0.3% non-contiguous), 853731/1040384 blocks
[ 13.546450] dracut: Remounting /dev/mapper/vg_elmer-lv_root with -o ro
[ 13.659929] EXT4-fs warning (device dm-1): ext4_clear_journal_err:4401: Filesystem error recorded from previous mount: IO failure
[ 13.659999] EXT4-fs warning (device dm-1): ext4_clear_journal_err:4402: Marking fs in need of filesystem check.
[ 13.670784] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
[ 13.737745] dracut: Mounted root filesystem /dev/mapper/vg_elmer-lv_root
The first time I saw this, the boot dropped me to a "[repair]" shell prompt, and I could run fsck on the partition to fix the problems. But now it always says the file system was last mounted with errors. (And yes, the system shuts down cleanly.) There doesn't seem to be any problems: everything runs fine, and I get no errors in syslog.
So, is there really a problem with this partition? If not, how do I get it to stop running fsck every boot?
I know that I can boot up from the install image and run in rescue mode. But, this was a network install, and I don't have a server running with the install image. I also don't know if I would need that to fix this. I was hoping I wouldn't have to.
FWIW:
Code:
[root@Elmer ken]# uname -r
3.5.2-1.fc17.x86_64
Any help greatly appreciated.
TIA
ken