Hi Rick,
> I'm not sure when this started to occur. Perhaps after I installed the
> 2.6.16 kernel. In any event, I just noticed it today.
>
> During bootup, the following lines appear on the screen and in syslog:
>
> Mar 27 14:48:32 localhost kernel: NTFS driver 2.1.26 [Flags: R/W MODULE].
> Mar 27 14:48:32 localhost kernel: NTFS volume version 3.1.
> Mar 27 14:48:32 localhost kernel: NTFS-fs warning (device hda1):
> load_system_files(): Unsupported volume flags 0x4000 encountered.
> Mar 27 14:48:32 localhost kernel: NTFS-fs error (device hda1):
> load_system_files(): Volume has unsupported flags set. Mounting read-only.
> Run chkdsk and mount in Windows.
> Mar 27 14:48:32 localhost kernel: NTFS volume version 3.1.
>
> Obviously, I have a dual-boot system. when I run chkdsk on all my
> Windows drives, no error is found. Considering that the NTFS partition
> is being mounted read-only by Linux, I am not really concerned. But, I
> am curious what might be causing this error to show up.
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.
Szaka
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
