Examination Failed(Cannot unmount disk) Hatası

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

II – How To Unmount Volume Manually via SSH

.

I – 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)

 

II – How 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

 

Here is an examle;

Qnap file system check unmount volume (1) Qnap file system check unmount volume (2) Qnap file system check unmount volume (3) Qnap file system check unmount volume (4)

VN:F [1.9.22_1171]
Rating: 10.0/10 (4 votes cast)
VN:F [1.9.22_1171]
Rating: +4 (from 4 votes)
Examination Failed(Cannot unmount disk) ErrorExamination Failed(Cannot unmount disk) Hatası, 10.0 out of 10 based on 4 ratings

One Response to Examination Failed(Cannot unmount disk) Hatası

  1. In my case, I had to pass the -l flag to umount, otherwise it wouldn’t let me unmount
    /dev/mapper/cachedev1. From the documentation:


    There are several options that can be tried in the event that umount refuses to unmount a filesystem for no immediately apparent reason. Perhaps the most useful is the -l (i.e., lazy) option, which immediately detaches the filesystem from the main filesystem and then cleans up all references to the unmounted filesystem as soon as it is no longer busy. This capability requires Linux kernel 2.4.11 or later.

Leave a Reply to Pedro Pombeiro Cancel 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>