On Thu March 30 2006 12:23, Szakacsits Szabolcs wrote: > Hi Rick, > > It means that you interrupted the Windows filesystem checking process > (after scheduling the filesystem check by chkdsk, it needs __TWO__ reboots > into Windows but you did only once) so the NTFS driver refused to mount it > read-write (it's inconsistent) for your safety. > > When this safety check was implemented we didn't know yet the exact > meaning of the flag (value 0x4000, which we've never seen before) that's > why no better explanation in the log and refusal of read-write mount. As > it turned out we were right to be highly careful. > > So just boot Windows again and then mount will work what you probably > already did. Hi Szaka, Actually, I've booted Windows several times since then and I still get the error when booting Linux. So, I'm still at a loss as to why this is happening. Rick -- Rick's Law: What cannot be imagined will be accomplished by a fool.
Attachment:
pgpqKI7nBBuLm.pgp
Description: PGP signature