> Source: [sk115713](https://support.checkpoint.com/results/sk/sk115713)

# sk115713 - File system check is forced after a reboot 

| Property | Value |
|----------|-------|
| Solution ID | sk115713 |
| Date Created | 2017-01-30 |
| Last Modified | 2020-12-04 |
| Technical Level | General |
| Products | Security Gateway, Security Management Server |
| Versions | R82.10, R82, R81.20, R82.10, R82, R81.20, R82.20 |
| OS | Linux, Gaia |

## Symptoms

- * After reboot system start a force file system check (fsck).
* No console output after a reboot, but system recovers after 30-40 minutes.
* System uptime before reboot was more than 6 month.

## Cause

Default behaviour of EXT3 file system

## Solution

Force file system check on reboot is an expected behavior.   

The EXT3 file system has a pre-configures shedule file system check. It can be configured as a time frame or number of remounts (reboots)

To check the scheduler, use:

*# tune2fs -l /dev/mapper/vg_splat-lv_current* - For a root partition

*# tune2fs -l /dev/mapper/vg_splat-lv_log* - For a log partition

<br />

Example of the output:

*# tune2fs -l /dev/mapper/vg_splat-lv_current*

*tune2fs 1.39 (29-May-2006)*

*Filesystem volume name: \<none\>*

*Last mounted on: \<not available\>*

*Filesystem UUID: e5831f5a-a71d-43a1-bb92-24a1c1ece325*

*Filesystem magic number: 0xEF53*

*Filesystem revision #: 1 (dynamic)*

*Filesystem features: has_journal resize_inode dir_index filetype needs_recovery sparse_super large_file*

*Default mount options: (none)*

*Filesystem state: clean*

*Errors behavior: Continue*

*Filesystem OS type: Linux*

*Inode count: 4194304*

*Block count: 8388608*

*Reserved block count: 419430*

*Free blocks: 6919576*

*Free inodes: 4140920*

*First block: 0*

*Block size: 4096*

*Fragment size: 4096*

*Reserved GDT blocks: 1022*

*Blocks per group: 32768*

*Fragments per group: 32768*

*Inodes per group: 16384*

*Inode blocks per group: 512*

*Filesystem created: Wed Jan 4 15:51:14 2017*

*Last mount time: Thu Jan 5 16:36:13 2017*

*Last write time: Thu Jan 5 16:36:13 2017*

*Mount count: 6*

*Maximum mount count: 28*

*Last checked: Wed Jan 4 15:51:14 2017*

*Check interval: 15552000 (6 months)*

*Next check after: Mon Jul 3 16:51:14 2017*

*Reserved blocks uid: 0 (user admin)*

*Reserved blocks gid: 0 (group root)*

*First inode: 11*

*Inode size: 128*

*Journal inode: 8*

*First orphan inode: 1705660*

*Default directory hash: tea*

*Directory Hash Seed: 3fdb7675-f2e8-4485-8a32-4a337c63a15b*

*Journal backup: inode blocks*

In this example mount count for force file system check is 28 and file system check schedule to 6 months

To change the periodic of the force file system check, use:   
Remount count:   
*# tune2fs --c \<Number of remounts (-1 to disable)\> \<Partition\>*

<br />

Periodic:   
*# tune2fs -i \<interval-between-checks\[d\|m\|w\] (0 to disable)\> \<Partition\>*

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content