HOWTO: force filesystem check on reboot in a Linux system

Usually, only a superficial file system check is performed automatically on boot up, and it's sufficient; but sometimes it could be handy to force a full file system check (i. e., to run the Linux fsck utility) to ensure the FS is really OK.

1. Classic init (SysVinit): just reboot the system with a special option:

   # shutdown -rF now

2. systemd init: much more interesting: at the boot time, you need to append a special kernel command line parameter (e. g., you can specify it at the GRUB command line):

   linux /boot/vmlinuz root=UUID=... ro fsck.mode=force

P. S. It should then check all the filesystems enabled for checking in /etc/fstab.

References:

1. man shutdown
2. man systemd-fsck
3. man fstab
4. man fsck

HOWTO: force filesystem check on reboot in MS Windows (NT family)

These tricks may be well-known, but still handy for busy volumes (e. g., the system one):

0. Open a command prompt (cmd) with administrator privileges (either via "Start → Run..." menu, "<WinKey> + <R>" hotkey, or other methods you like).
1. Two options.
   1. Marking volume "dirty":

      > fsutil dirty set C:
      Volume - C: is now marked dirty
      

   2. A milder option, just scheduling the volume to be checked on startup:

      > chkntfs /C C:
      
      

2. Reboot safely.
3. Watch the CHKDSK operation progress...
4. DONE!
   (You can check the CHKDSK logs later in the "Event Viewer" (eventvwr.msc or simply eventvwr for short)).

References:

• MS TechNet Library - Windows Server:
  • Chkntfs
  • Fsutil dirty
• MS Knowledge Base:
  • CHKNTFS.EXE: What You Can Use It For
• MS Windows XP Professional Product Documentation:
  • Microsoft Windows XP - Chkntfs
  • Microsoft Windows XP - Fsutil: dirty

---
Last updated: 2016-05-20