The workaround I was given, and that seems to work for me was the command sudo mount -t ntfs -o rw,remove_hiberfile The final determination was that It appears windows changed something in their shutdown procedure such that it now leaves a hibernation file on the disk (even with a normal shutdown or restart) that fakes linux into believing windows is hibernated and not a clean shutdown or restart, preventing a normal read/write mount of the ntfs volume.
I followed the advice from maintainers about power settings, running chkdsk, etc., all to no avail. I then filed a bug on ntfs-3g about the failure to mount properly. I went through several iterations of shutdown & restart windows, clean shutdown, clean restart, each time with the same error on attempting to mount the ntfs volume. The message I began getting said something to the effect that windows was hibernated and the volume could not be mounted read/write and was mounted as read only. (It mounted fine in versions 20H1 and 20H2). I have a script that I use to mount the ntfs volume and copy the report files over to fedora so I can review them without needing to boot back into windows.Ībout 2 weeks ago my windows was updated to the 21H1 version and that seems to have broken mounting the ntfs volume in linux. I then boot back into fedora and am happy until the next time I need to upload the data.
#WINDOWS 10 VIRTUALBOX SHUTDOWN ERRORS PDF#
What I do is upload the data and create a report based on the data which I save as a pdf file. This is because there is some software that only runs under windows related to my medical devices.
#WINDOWS 10 VIRTUALBOX SHUTDOWN ERRORS WINDOWS 10#
I dual boot my laptop with windows 10 and fedora 33.
0 kommentar(er)
