Ask Your Question
1

Filesystem errors on bootup

asked 2012-05-29 20:37:10 -0500

binaryhat gravatar image

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-x866 contains a file system with errors, check forced. 05/29/12 04:58:56 PM dracut Warning Fedora-14-x866: Duplicate or bad block in use! 05/29/12 04:58:56 PM dracut Warning Fedora-14-x866: 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-x866: 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-x866: (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-x866: File /usr/share/locale/nl/LCMESSAGES/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-x866: /usr/share/locale/uk/LCMESSAGES/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-x866: 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.

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
1

answered 2012-05-30 19:44:56 -0500

binaryhat gravatar image

I fixed it. I was using the wrong blkid:

/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="LVM2member" /dev/mapper/VolGroup-lvroot: LABEL="Fedora-14-x866" UUID="ba028935-9a09-4211-8037-5eb767341397" TYPE="ext4" /dev/mapper/VolGroup-lvswap: UUID="0316d41e-abb4-4845-85f4-151cd4c1fb4d" TYPE="swap" /dev/mapper/VolGroup-lvhome: UUID="061af90c-025a-40fb-a436-055111d22ac8" TYPE="ext4"

edit flag offensive delete link more
0

answered 2012-05-30 15:09:24 -0500

misc gravatar image

Yes, if fsck do refuse to run due to that, you have to unmount it. Filesystems cannot be repaired while the system is in use, like you can hardly fix a motor while driving :)

However, I suspect that it cannot be unmounted easily, and so I would suggest to take a livecd in order to be able to fix the issue. just run it, find the proper partition ( likely the same ) and run fsck.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2012-05-29 20:37:10 -0500

Seen: 2,344 times

Last updated: May 30 '12