fsck on boot

joeljkp · #1 21st July 2005, 06:45 PM

FC3 used to prompt the user to scan the hard drive on boot if the computer was shut down improperly. Why doesn't FC4 do that? How can I get it to do a full scan if I have to reset the computer without shutting it down properly?

tejas · #2 21st July 2005, 07:52 PM

post your /etc/grub.conf

ghaefb · #3 21st July 2005, 08:19 PM

Use this command: shutdown -rF NOW

joeljkp · #4 21st July 2005, 11:04 PM

Quote:

Originally Posted by tejas

post your /etc/grub.conf

Code:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd0,2)
#          kernel /boot/vmlinuz-version ro root=/dev/hdc3
#          initrd /boot/initrd-version.img
#boot=/dev/hdc
default=0
timeout=5
splashimage=(hd0,2)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.12-1.1398_FC4)
        root (hd0,2)
        kernel /boot/vmlinuz-2.6.12-1.1398_FC4 ro root=LABEL=/1 rhgb quiet
        initrd /boot/initrd-2.6.12-1.1398_FC4.img
title Fedora Core (2.6.12-1.1390_FC4)
        root (hd0,2)
        kernel /boot/vmlinuz-2.6.12-1.1390_FC4 ro root=LABEL=/1 rhgb quiet
        initrd /boot/initrd-2.6.12-1.1390_FC4.img
title Gentoo
        root (hd0,4)
        chainloader +1
title Windows XP
        rootnoverify (hd0,0)
        chainloader +1

Quote:

Originally Posted by ghaefb

Use this command: shutdown -rF NOW

Yes, that will force a fsck on the next reboot, but I'm talking about a situation in which I haven't done a 'shutdown' - when the power goes out, or my computer freezes, or something like that. In that situation, FC3 would prompt during the init sequence asking if I wanted to do a full scan or not. Why did FC4 get rid of that, and how can I get it back?

tejas · #5 22nd July 2005, 02:53 AM

wooooooooops, I meant your /etc/fstab

Sorry

joeljkp · #6 22nd July 2005, 03:44 AM

Quote:

Originally Posted by tejas

wooooooooops, I meant your /etc/fstab

Code:

# This file is edited by fstab-sync - see 'man fstab-sync' for details
LABEL=/1                /                       ext3    defaults        1 1
/dev/devpts             /dev/pts                devpts  gid=5,mode=620  0 0
/dev/shm                /dev/shm                tmpfs   defaults        0 0
/dev/proc               /proc                   proc    defaults        0 0
/dev/sys                /sys                    sysfs   defaults        0 0
/dev/hdc2               swap                    swap    defaults        0 0
/dev/hdc1                               /mnt
ntfs    uid=500,gid=500,user,noauto     0 0
//storage/Music                 /mnt                                    smbfs
uid=500,gid=500,user,noauto             0 0
/dev/hda                /media/cdrom            auto    pamconsole,exec,noauto,managed 0 0

tejas · #7 22nd July 2005, 05:13 AM

I'm confused the 1 1 in the 3rd line of your fstab implies that your fs should be checked at startup.

I dont know why it doesn't check for errors.

Anyway, it will check for errors every 50 mounts or so, so you don't have to worry too much

joeljkp · #8 22nd July 2005, 03:40 PM

Quote:

Originally Posted by tejas

I'm confused the 1 1 in the 3rd line of your fstab implies that your fs should be checked at startup.

I dont know why it doesn't check for errors.

Anyway, it will check for errors every 50 mounts or so, so you don't have to worry too much

Well it does do its quick scan. In FC3 though, if you didn't shut down properly, on the next reboot a message would appear before the rhgb stuff started that said something like "This computer was not properly shut down. Do you want to perform a full scan (y/N)?"

I'm just wondering why they got rid of that option, or how to get it back.

dishawjp · #9 22nd July 2005, 05:38 PM

The simplest way is to force a file system check it to just put the empty file forcefsck on your root directory and it will run a complete fsck on your next boot.

# touch /forcefsck

Since the initscripts were modified to permit this option, other methods have been let go. The

# shutdown -rF -now

will do the same thing. Either way, a reboot will be required.

HTH,

Jim Dishaw

joeljkp · #10 22nd July 2005, 07:07 PM

Thanks for the explanation, dishawjp. I still think the other way was easier, but I can accept this as well.

dishawjp · #11 22nd July 2005, 08:03 PM

The nicest thing about the forcefsck method is that if everything seems to be running well and there's most likely no file system damage, you can continue to work until you're good and ready to do a reboot. There is also the :

# touch /.autorelabel

which is like doing the old single user mode "fixfiles relabel" deal if you are having SELinux errors.

Regardless of how you do it, just be glad that you're not running M$Windows :-)

Jim