I’ve got her machine set up as Windows native, installed on SSD. Her old Windows drive, with her old files, is hooked up to it. She can see it fine from Windows. But while she was using Linux, she’d been writing to an LVM drive, which was originally a backup, but now has some changes on it from the old drive.
I’m running Fedora as a virtual machine, and it seems to be running fine (so far). I’ve attached the old Windows drive to the physical machine, and it shows up in Nautilus and other file managers. But when I try to access it, I get a message that it’s an NTFS drive with problems, and I can only mount it read-only. It suggests I repair.
So, is this caused by the fact that its already mounted and in use by Windows? Seems a little strange, since the virtual machine probably wouldn’t know that. Windows doesn’t have a problem with it. Bigger question: Can/should I try to repair it as an unmounted drive from the virtual machine using e2fsck? That is, does e2fsck repair NTFS drives? And what is the risk if I don’t attempt to back it up first?