windows ntfs drive cannot mount dirty bit fix
Posted: Tue Jul 12, 2011 12:01 am
sometimes when an apple os X system freezes while going through an NTFS drive, the dirty bit is set, or you may have frozen and or not properly shutdown in a windows (7/vista/xp) environment, keeping the 'dirty bit' dirty. As a computer properly shuts down, the dirty bit is turned of.
You may find in linux or os x that the drive is not visible and cannot mount. To fix this problem, if it is not the boot drive (c: usually) and a data drive (d,e,f,g,h,etc) boot back into window 7, or put the hard drive into another computer as an extra drive, and allow the windows 7 system to boot normally.
find the drive letter (d: for instance)
start the cmd prompt
start>cmd[enter]
then use:
then restart the computer normally, and after being restarted, shut down after that.
your drive will no longer be dirty if there are no real problems with it.
jsut a safety quirk in the ntfs system and windows so it always checks if the drive or system was interrupted by a freeze or other bug and the file system is overviewed just in case there are serious errors that would cause corruption if another OS tried to use it.
try to NOT disable the dirty bit with command line code or using os x hacks. to do so would endanger the outline of your drive's contents, and things may get corrupt, a very bad idea!
You may find in linux or os x that the drive is not visible and cannot mount. To fix this problem, if it is not the boot drive (c: usually) and a data drive (d,e,f,g,h,etc) boot back into window 7, or put the hard drive into another computer as an extra drive, and allow the windows 7 system to boot normally.
find the drive letter (d: for instance)
start the cmd prompt
start>cmd[enter]
then use:
Code: Select all
chkdsk /f /r d:your drive will no longer be dirty if there are no real problems with it.
jsut a safety quirk in the ntfs system and windows so it always checks if the drive or system was interrupted by a freeze or other bug and the file system is overviewed just in case there are serious errors that would cause corruption if another OS tried to use it.
try to NOT disable the dirty bit with command line code or using os x hacks. to do so would endanger the outline of your drive's contents, and things may get corrupt, a very bad idea!