PDA

View Full Version : Filesystem errors on bootup



doctorwhite
30th May 2012, 03:36 AM
On every reboot I get:

05/29/12 04:58:56 PM dracut Warning e2fsck returned with 4
05/29/12 04:58:56 PM dracut Warning _Fedora-14-x86_6 contains a file system with errors, check forced.
05/29/12 04:58:56 PM dracut Warning _Fedora-14-x86_6: Duplicate or bad block in use!
05/29/12 04:58:56 PM dracut Warning _Fedora-14-x86_6: Multiply-claimed block(s) in inode 5031: 306904 306905 306906 306907 306908 306909 306910 306911 306912 306913 306914 306915 306916 306917 306918 306919 306920 306921 306922 306923 306924 306925 306926 306927 306928 306929 306930 306931 306932 306933 306934 306935 306936 306937 306938
05/29/12 04:58:56 PM dracut Warning _Fedora-14-x86_6: Multiply-claimed block(s) in inode 7383: 306904 306905 306906 306907 306908 306909 306910 306911 306912 306913 306914 306915 306916 306917 306918 306919 306920 306921 306922 306923 306924 306925 306926 306927 306928 306929 306930 306931 306932 306933 306934 306935 306936 306937 306938
05/29/12 04:58:56 PM dracut Warning _Fedora-14-x86_6: (There are 2 inodes containing multiply-claimed blocks.)
05/29/12 04:58:56 PM dracut Warning
05/29/12 04:58:56 PM dracut Warning _Fedora-14-x86_6: File /usr/share/locale/nl/LC_MESSAGES/libc.mo (inode #5031, mod time Mon May 14 19:22:07 2012)
05/29/12 04:58:56 PM dracut Warning has 35 multiply-claimed block(s), shared with 1 file(s):
05/29/12 04:58:56 PM dracut Warning _Fedora-14-x86_6: /usr/share/locale/uk/LC_MESSAGES/setroubleshoot-plugins.mo (inode #7383, mod time Mon May 7 14:32:49 2012)
05/29/12 04:58:56 PM dracut Warning _Fedora-14-x86_6:
05/29/12 04:58:56 PM dracut Warning *** An error occurred during the file system check.
05/29/12 04:58:56 PM dracut Warning *** Dropping you to a shell; the system will try
05/29/12 04:58:56 PM dracut Warning *** to mount the filesystem(s), when you leave the shell.


So at:

(Repair filesystem):/#

I do fsck -y /dev/sda2 and it tells me its mounted. Do I umount /dev/sda2 first?

OS is F16.

---------- Post added at 06:36 PM ---------- Previous post was at 02:42 PM ----------

/dev/sda2 is incorrect. I didn't run blkid as root. I should be using /dev/mapper/VolGroup-lv_root

/dev/sda1: UUID="98ac4e72-4b4c-4bdd-bd77-6d41bedef6e6" TYPE="ext4"
/dev/sda2: UUID="OJM8gN-ypbR-1srz-hKTa-T9al-2n1N-1Dc5Hg" TYPE="LVM2_member"
/dev/mapper/VolGroup-lv_root: LABEL="_Fedora-14-x86_6" UUID="ba028935-9a09-4211-8037-5eb767341397" TYPE="ext4"
/dev/mapper/VolGroup-lv_swap: UUID="0316d41e-abb4-4845-85f4-151cd4c1fb4d" TYPE="swap"
/dev/mapper/VolGroup-lv_home: UUID="061af90c-025a-40fb-a436-055111d22ac8" TYPE="ext4"

Gareth Jones
30th May 2012, 10:11 AM
If root fails an automatic check, really it should already be mounted read-only, but other posts have made me wonder whether Fedora handles that properly. To be sure, run "mount -o remount,ro /" before running the fsck. (You cannot ever unmount the root file-system in Linux, and trying to do so should normally force a read-only remount, but read-only is good enough for fsck so long as you reboot after. It's all about keep fsck's and the kernel's idea of the file-system layout in sync and preventing both from modifying the FS at the same time, which would cause corruption.)