The file system is not clean. It is suggested that you run “check disk”.

I – Warning “, “System”, “127.0.0.1″, “localhost”, “[Linear Disk Volume: Drive 1 2 3 4] The file system is not clean. It is suggested that you run “check disk”.”

II – How To Solve “Examination Failed(Cannot unmount disk) Error” With Unmounting Volume With Qumount

.

I – Warning “, “System”, “127.0.0.1″, “localhost”, “[Linear Disk Volume: Drive 1 2 3 4] The file system is not clean. It is suggested that you run “check disk”.”

This Error might caused by corrupt configuration due to the disk failure. So please, firt, check if you dont have any broken HDD or not. If you got any broken HDD, which is marked as “Normal” or “Abnormal”, please change that HDD before this process;

After beeing sure your all HDD’s are fine, Please try the steps below to do troubleshooting.

1  -Go to Storage Manager -> Storage Space -> and doublle click on you Volume;

qnap chkdisk check file system (1)

2 – Go To Actions -> check filesystem

qnap chkdisk check file system (2)

3 – Please dont forget that this will cause you not able to access your datas in that volme for a few hours!

qnap chkdisk check file system (3)

.

II – How To Solve “Examination Failed(Cannot unmount disk) Error” With Unmounting Volume With Qumount

If you got this error Message;

Examination failed(Cannot unmount disk) (1)

But Qnap returns with this error;

Level:  Error

[RAID5 Disk Volume: Drive 1 2 3] Examination failed(Cannot unmount disk).

Examination failed(Cannot unmount disk) (2)

.

To Solve İssue, Install Qumount QPKG, Unmount NAS, and start file system check!

What is Qumount?

Qumount is a package to log and workaround the issue where filesystem can not unmount.

For example:

  1. Some process keeps filesystem in use and cause filesystem check failed

  2. Some process keeps filesystem in use and cause “filesystem not clean” after reboot

How to get the qpkg:

http://download.qnap.com/Storage/tsd/utility/Qumount_0.2.zip

How to use:

1. Install in the App Center

2. Reboot NAS or do filesystem check

3. If there was any volume fail to unmount, there will be a log file umountxxxxxxx.log in the Public folder. You can use this log to find the process which locks volume

4. If there was any volume fail to unmount, the package will try to kill the process and unmount again. Therefore customer should not see error message in system logs after installing this qpkg.

Example log file:

umount_cachedev3_2015-12-16_13.21.54.log

.

II – 2.th Way To Unmount Volume Manually via SSH

You can unmount volume manually, and start check process;

For Old Firmware (3.8.0 – 4.0.5)

/etc/init.d/services.sh stop
/etc/init.d/opentftp.sh stop
/etc/init.d/Qthttpd.sh stop
umount /dev/md0
e2fsck -f -v -C 0 /dev/md0
mount /dev/md0
reboot

http://dev.mensfeld.pl/2013/08/qnap-nas-file-system-not-clean-examination-failed-cannot-unmount-disk/

.
For New Firmware (4.1.0 and later) (64 Bit)
/etc/init.d/services.sh stop
/etc/init.d/opentftp.sh stop
/etc/init.d/Qthttpd.sh stop
umount /dev/mapper/cachedev1
e2fsck_64 -f -v -C 0 /dev/mapper/cachedev1
mount -t ext4 /dev/mapper/cachedev1 /share/CACHEDEV1_DATA
reboot
https://forum.qnap.com/viewtopic.php?t=123461

.
For NewFirmware (4.1.0 and later) (32 Bit)
/etc/init.d/services.sh stop
/etc/init.d/opentftp.sh stop
/etc/init.d/Qthttpd.sh stop
/etc/init.d/rsnap.sh stop
umount /dev/mapper/cachedev1
e2fsck -f -v -C 0 /dev/mapper/cachedev1

VN:F [1.9.22_1171]
Rating: 5.3/10 (6 votes cast)
VN:F [1.9.22_1171]
Rating: -2 (from 2 votes)
The file system is not clean. It is suggested that you run “check disk”.The file system is not clean. It is suggested that you run “check disk”., 5.3 out of 10 based on 6 ratings

3 Responses to The file system is not clean. It is suggested that you run “check disk”.

  1. Neno says:

    Not sure why antivirus thinks there’s a virus on this page and is blocking access to it. Infection URL:Mal

  2. Customer says:

    All services stopped successfully. But the problem still there at each time of reboot.

  3. Rvdd says:

    I must say this is very annoying. We have the NAS only for a week and this happens.

    This post helped, but after rebooting the system still cant do a filesystem check. So the original problem remains.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>