this post was submitted on 23 Apr 2025
22 points (92.3% liked)
Linux Gaming
18152 readers
226 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME
away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
When you run
$ mount
, you probably see something like this:If so, that entire filesystem is mounted read-only (hence the "ro" flag).
chown
(and what you probably wanted,chmod
) isn't going to affect that. It alters ownership and permissions on files and directories within a filesystem.I have no idea what Disks is, but I assume that it's some kind of graphical utility.
I'd probably try doing this, which will only affect the current mount; it won't persistent to the next boot:
That'll try and remount the thing read-write.
If that resolves the issue, then the issue is going to indeed be that it's mounted read-only.
I suspect that there's probably an option in this Disks thing to mount it read-write. I have never seen the thing, so I can't give any advice there.
If you want to stick it in /etc/fstab and mount it at boot, if you let me see the line you get back from
mount
above, maybe censoring the username, I can probably tell you what to put there.EDIT: It looks like the preferred NTFS driver is the FUSE ntfs-3g, not the kernel ntfs or ntfs3. According to the linked page, Debian apparently doesn't build their kernels by default with the ntfs kernel driver anyway, so I assume that Linux Mint Debian Edition probably also does the same. So it'll probably read something like "fuse.ntfs-3g", not "ntfs".