Hello All,
For the past few weeks I have been getting this message in dmesg:
NTFS volume version 3.1.
NTFS-fs error (device hdb1): load_system_files(): Volume is dirty. Mounting read-only. Run chkdsk and mount in Windows.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NTFS volume version 3.1.
NTFS-fs error (device hda9): load_system_files(): Volume is dirty. Mounting read-only. Run chkdsk and mount in Windows.
NTFS volume version 3.1.
NTFS-fs error (device hda5): load_system_files(): Volume is dirty. Mounting read-only. Run chkdsk and mount in Windows.
Sure enough, when I start Windows it says there's a problem and runs chkdsk, which invariably involves a reboot after it checks the first windows drive and then it checks the other 2 without rebooting.
/etc/fstab contains 'noauto', but this dmesg says the drives are being mounted read-only and, maybe, depite this, because I have ntfs write in my kernel something may be corrupting these drives.
Another concern is that I have my /boot partition 'noauto' but lately when I compile a kernel and go to mount /boot I get the message:
mount: /dev/hda2 already mounted or /boot busy mount: according to mtab, /dev/hda2 is already mounted on /boot
I use udev and wonder whether it could be the culprit. I guess removing the ntfs write option from my kernel may stop the corruption, but wonder if anyone can shed light on why things seems to be mounted at boot, despite /etc/fstab saying not to. TIA.
-- Dennis Robertson
-- gentoo-user@gentoo.org mailing list
