NAS Codex › QNAP › QNAP "File system is not clean." in the System Event Log: what it means and QNAP's fix
QNAP "File system is not clean." in the System Event Log: what it means and QNAP's fix
The QNAP System Event Log shows File system is not clean. followed by a volume name. QNAP's FAQ says this means a volume that contains data may not be properly mounted, and that the fix is a file system check on that volume. This page gives QNAP's causes, its steps for QTS, what to expect while the check runs, and QNAP's next steps if the NAS keeps restarting afterwards.
Written against: QTS 4.3.4 and later, excluding QuTS hero (QNAP FAQs last modified 2022-06-24, 2025-06-17 and 2025-08-12). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
QNAP's fix is a file system check on the volume named in the message: restart the NAS, then go to Storage & Snapshots > Storage > Storage/Snapshots, select the volume, click Manage > Actions > Check File System. The volume is unmounted and its shares and iSCSI LUNs may be unavailable while the check runs. Afterwards, restart the NAS and see whether the warning is still there. If the NAS keeps restarting or freezing, follow QNAP's unexpected-reboot checks.
The message
File system is not clean. [Volume Name]QNAP says this warning appears in the System Event Log when a volume that contains data may not be properly mounted. The FAQ applies to all models running QTS, and excludes QuTS hero.
Why it happens
QNAP lists three usual circumstances:
- the NAS has had an abnormal or forced shutdown;
- some services were not stopped correctly before a shutdown;
- the NAS keeps restarting unexpectedly.
QNAP's fix: check the file system (QTS 4.3.4 and later)
QNAP's warnings before you start: the volume is unmounted and inaccessible during the check; NAS shares and iSCSI LUNs may be unavailable; and the check can take a long time depending on the size of the volume. QNAP's general file-system-check FAQ adds that all services stop during the check, and recommends off-peak hours or a planned maintenance window.
- Restart the NAS.
- Log in to QTS as an administrator.
- Go to Storage & Snapshots > Storage > Storage/Snapshots.
- Select the volume and click Manage. The volume management window opens.
- Click Actions, then Check File System.
- After the check, restart the NAS.
- Check whether QTS still shows the file system warning.
QNAP also describes a one-time scheduled check, which runs only if the file system is detected as unclean: go to Storage & Snapshots > Global Settings > Storage, enable Scheduled File System Check, set a date and time, and click Apply.
How long the check takes
QNAP published two test results, which it says are for reference only:
| Model | Pool / RAID | Volume size | Used | Files | Check time | Volume type |
|---|---|---|---|---|---|---|
| TVS-h1288X | RAID 5, 4 HDDs | 4.96 TB | 4.40 TB | about 2.4 million | about 16 minutes | System volume |
| TS-2888X | RAID 0, 4 HDDs | 12.90 TB | 10.99 TB | about 3.93 million | about 13 minutes | Non-system volume |
QNAP's explanation for why the larger volume finished faster: a system volume adds service stop and start overhead, RAID 0 has higher I/O while RAID 5 is slower because of parity, and a higher-performance CPU shortens the check.
If the NAS keeps restarting or freezing
QNAP says that if the NAS still restarts or freezes unexpectedly after a file system check, it may have other issues. Its unexpected-reboot FAQ gives this order, moving to the next step only if the problem continues:
- Memory. If you changed the memory modules, put back the originals shipped with the NAS. QNAP says to use only QNAP modules, identical in specification on multi-slot models, and that unsupported modules may degrade performance, cause errors or stop the operating system starting.
- Third-party apps. In App Center, disable all third-party apps. If the problem stops, enable them one by one to find the cause.
- QNAP apps. Do the same with QNAP apps.
- SSD cache. Turn off SSD cache in Storage & Snapshots > Storage > Cache Acceleration. If that stops the problem, remove and recreate the cache.
- Disk compatibility. Note each disk model in Storage & Snapshots and compare it with the QNAP compatibility list; replace incompatible disks.
- Disk tests. Run Scan for Bad Blocks and a S.M.A.R.T. Complete Test on the disks. Replace any disk that reports a problem. If all disks pass, contact QNAP support through the Service Portal.
When to stop and get help
Stop and contact QNAP support if the check fails or will not start, if the volume does not remount afterwards, or if the disk tests report problems on more disks than your RAID can lose. Do not remove or recreate the volume or storage pool to clear the warning. If the data is not backed up elsewhere, copy off what you can reach before running anything that unmounts the volume. See also volume Unmounted after a failed conversion.
Questions
What does File system is not clean mean on a QNAP NAS?
QNAP says the System Event Log warning means a volume that contains data may not be properly mounted. It usually follows an abnormal or forced shutdown, services not stopped correctly before a shutdown, or the NAS restarting unexpectedly.
Can I use the NAS while the file system check runs?
No. QNAP says the volume is unmounted and inaccessible during the check, and that NAS shares and iSCSI LUNs may be unavailable. Its filesystem-check FAQ says all services stop, so schedule the check off-peak.
How long does a QNAP file system check take?
It depends on the volume. QNAP's reference tests took about 16 minutes for a 4.96 TB RAID 5 system volume and about 13 minutes for a 12.90 TB RAID 0 non-system volume, and QNAP says volume type, RAID level and CPU all affect the time.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.