Disk write error due to read-only filesystem
Disk write error due to read-only filesystem
Disclaimer: I am very new to Linux (1 week).
I have installed the Valve version of Steam on LMDE6. I have used Disks to automatically mount the NTFS drive I used with Windows (doesn't hold bootloader, it is just for Steam library storage) at boot ( /media/[username]/Gaming ) and I made it the default library folder in Steam.
Running games works perfectly (actually, performance is surprisingly good), but I cannot install them due to a "disk write error".
I looked for solutions and found this page, from which I understand that I need to change permissions to the mounting point, but when I do, using chown -R, I get a "Read-only filesystem" error for all files and folders.
I can see no options to fix this in Disks and I tried to edit fstab once, but it messed things up so badly I had to use the USB drive with the portable installer to fix things.
You're viewing a single thread.
This might be due to windows hibernation behavior. When you shut down windows 10 and 11, it actually hibernates the drive instead of a full shutdown. You can disable it by turning off "fast startup" option(s). I haven't had to do it in a while so I can't recall exactly where the option lives. Hibernated drives get marked to prevent writing to them as it may corrupt the windows install.
Oh, yeah,
$ man mount.ntfsmentions that:Windows hibernation and fast restarting On computers which can be dual-booted into Windows or Linux, Windows has to be fully shut down before booting into Linux, otherwise the NTFS file systems on internal disks may be left in an inconsistent state and changes made by Linux may be ignored by Windows. So, Windows may not be left in hibernation when starting Linux, in order to avoid inconsistencies. Moreover, the fast restart feature available on recent Windows systems has to be disabled. This can be achieved by issuing as an Administrator the Windows command which disables both hi‐ bernation and fast restarting : powercfg /h off If either Windows is hibernated or its fast restart is en‐ abled, partitions on internal disks are forced to be mounted in read-only mode.And then:
remove_hiberfile When the NTFS volume is hibernated, a read-write mount is denied and a read-only mount is forced. One needs either to resume Windows and shutdown it prop‐ erly, or use this option which will remove the Win‐ dows hibernation file. Please note, this means that the saved Windows session will be completely lost. Use this option under your own responsibility.Good catch. If you're right about this being the cause, then my suggestion above about mounting read-write will probably just result in another read-only mount (though I bet that mount.ntfs will print something about a read-only mount being forced in the console).
Good odds that OP just needs to fully shut down Windows, rather than suspending it.
What’s with that disaster of colorized text?
Lemmy's Web UI does something wonky and nonstandard with Markdown backtick-surrounded monospaced text. I assume that it's some attempt to pretty-print code or something that nobody wants. Doing the four-space indent gets monospaced text and avoids it, but then you can't do it inline with proportional text.
I just ignore the colorization. Hopefully someday they'll just get rid of it.
I am going to specify in the body of the post that this is a drive I used as library drive only for Steam, it is not the one holding the Windows boot.
Would that change things?
To me that means I would feel comfortable using the remove_hiberfile and recover options listed here https://linux.die.net/man/8/mount.ntfs-3g
Put these in your fstab and it'll get fixed every mount
I haven't run into this myself, but from the mount.ntfs man page snippet I listed below, it doesn't sound like it; it references "partitions", so I don't think that it's just the system partition in Windows that's affected.