Sorry this has already been discussed, but I got the message :
Volume is scheduled for check.
Please boot into Windows TWICE, or use the 'force' mount option.
when I try to mount my ntfs drive. The problem is I do NOT have Windows... although it never caused any data loss I couldn't cry about, I would like to avoid using the force option every time I mount this drive ...
thks for any help
tome4k, hum, what's happens if you do a ntfsfix and then a force mount ?
I don't know why but the procedure that has been published on the first post doesn't work for me.
This is my fstab file...
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
UUID=120385b3-5550-4206-b89a-e92d42f78e2a / ext3 defaults,errors=remount-ro 0 1
#UUID=30DC3ABFDC3A7F62 /media/hda5 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
/dev/hda5 /media/hda5 ntfs-3g defaults 0 0
UUID=2cb32946-237f-4aa4-a4fa-37f1871944ce none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
And after a re-boot the system doesn't mount the NTFS partition, however if I use this command from shell it works..
sudo ntfs-3g /dev/hda5 /media/hda5 -o force
where I'm wrong?
Why do you use the force option ?
What's happens if you don't use it :
Code:sudo umount /dev/hda5 sudo mount /dev/hda5
If I don't use the force option the system says that 'have to reboot windows twice' (can't remember exactly...)
I'm looking how to update the fstab so I don't have to edit/lunch anything...
The better should simply to reboot in windows twice, IMO.
Use a force option in fstab is not really recommanded.
I already did an ntfsfix, and if I use the force option it is mounted just fine, but I can't mount it without -o force.
What I should do is reboot windows twice, but problem is : I don't have Windows...
is there no chkdsk for linux ?
Last edited by tome4k; November 23rd, 2006 at 10:57 AM.