Says Drive is read only when I try to write to it. Any suggestions? I’ve tried to chown directory But says read only file system
What mount options are shown for the drive from the following command?
mount | grep ntfs
Also, is it possible that something went wrong when trying to mount the filesystem? dmesg or journalctl -b should give you more info, then search for ntfs, for example like this:
- open a terminal
- in the terminal, execute
dmesg | less - type
/ntfs, then press the enter key (repeatedly)
I’d expect that at some place there should be error messages.
nothing shown
pattern not found
Odd… that would mean the drive isn’t mounted, which could help explain the write error.
Would you mind posting the entire output from the mount command?
Is the NTFS volume on an internal drive, external drive (USB?), or another partition on the same drive Linux is on?
Would you mind posting the entire output from the
mountcommand?
/dev/sde2 on / type btrfs (rw,relatime,seclabel,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/fedora)
devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=7597396k,nr_inodes=1899349,mode=755,inode64)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,seclabel,nsdelegate,memory_recursiveprot)
none on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime,seclabel)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,size=3054404k,nr_inodes=819200,mode=755,inode64)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,nosuid,noexec,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=5668
)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime,seclabel)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,nosuid,nodev,relatime,seclabel,pagesize=2M)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime,seclabel)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime,seclabel)
tmpfs on /run/credentials/systemd-journald.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,seclabel,size=1024k,n
r_inodes=1024,mode=700,inode64,noswap)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,seclabel,size=7636008k,nr_inodes=1048576,inode64)
/var/lib/snapd/snaps/hello-world_29.snap on /var/lib/snapd/snap/hello-world/29 type squashfs (ro,nodev,relatime,context=system_u
:object_r:snappy_snap_t:s0,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/core_17247.snap on /var/lib/snapd/snap/core/17247 type squashfs (ro,nodev,relatime,context=system_u:object_
r:snappy_snap_t:s0,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/core_17272.snap on /var/lib/snapd/snap/core/17272 type squashfs (ro,nodev,relatime,context=system_u:object_
r:snappy_snap_t:s0,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/snapd_25577.snap on /var/lib/snapd/snap/snapd/25577 type squashfs (ro,nodev,relatime,context=system_u:objec
t_r:snappy_snap_t:s0,errors=continue,x-gdu.hide,x-gvfs-hide)
/dev/sde3 on /home type ext4 (rw,relatime,seclabel)
/dev/sda1 on /mnt/7CA4FD93A4FD505E type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096,x-gvfs-s
how)
tmpfs on /run/credentials/systemd-resolved.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,seclabel,size=1024k,n
r_inodes=1024,mode=700,inode64,noswap)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=1527200k,nr_inodes=381800,mode=700,uid=1000,gid=1000,
inode64)
tmpfs on /run/credentials/getty@tty2.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,seclabel,size=1024k,nr_inod
es=1024,mode=700,inode64,noswap)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sdg1 on /run/media/spaceboy/Ventoy type exfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,iocharset=u
tf8,errors=remount-ro,uhelper=udisks2)
/dev/sdf on /run/media/spaceboy/fc9faef1-0355-405d-ba69-77561687b359 type ext4 (rw,nosuid,nodev,relatime,seclabel,errors=remount
-ro,uhelper=udisks2)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
this one /dev/sda1 ?
/dev/sda1 on /mnt/7CA4FD93A4FD505E type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096,x-gvfs-s how)
looks like a windows system partition. WIndows was not shutdown but was hibernated (is win fast startup enabled)?
btw use either three ` or ~
```
pre
formatted
text
```
/dev/sda1 on /mnt/7CA4FD93A4FD505E type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096,x-gvfs-show)
It looks like the NTFS volume was manually mounted or perhaps via /etc/fstab because a desktop environment on Fedora usually uses a mount point such as /run/media/<username>/<volume_label>/.
Windows normally doesn’t use the first primary partition for itself, so that helps rule out a few possibilities.
So, again, what type of drive is it? – e.g. internal, external, etc. – the more details the easier and faster it is to diagnose the issue.
What are the contents of your /etc/fstab file?
Also check systemd’s journal…
journalctl | grep -i ntfs
… or manually unmount and mount to see if there are any immediate errors:
umount /mnt/7CA4FD93A4FD505E ; mount -v /dev/sda1 /mnt/7CA4FD93A4FD505E
Ah, I expected your NTFS partition to be mounted in the kernel, but it seems to be mounted with FUSE instead. What does journalctl -b --grep=fuse give you?
looks like a windows system partition. WIndows was not shutdown but was hibernated (is win fast startup enabled)?
btw use either three ` or ~
Is not a Windows system partition but possibly a shutdown issue last login.
What does
journalctl -b --grep=fusegive you?
``` Mar 02 23:42:43 fedora kernel: fuse: init (API version 7.45)
Mar 02 23:42:43 fedora systemd-modules-load[229]: Inserted module ‘fuse’
Mar 02 23:42:58 fedora systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse…
Mar 02 23:42:58 fedora systemd[1]: modprobe@fuse.service: Deactivated successfully.
Mar 02 23:42:58 fedora systemd[1]: Finished modprobe@fuse.service - Load Kernel Module fuse.
Mar 02 23:42:58 fedora systemd[1]: Mounting sys-fs-fuse-connections.mount - FUSE Control File System…
Mar 02 23:42:58 fedora systemd[1]: Mounted sys-fs-fuse-connections.mount - FUSE Control File System.
Mar 02 23:42:58 fedora systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse…
Mar 02 23:42:58 fedora systemd[1]: modprobe@fuse.service: Deactivated successfully.
Mar 02 23:42:58 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=>
Mar 02 23:42:58 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='>
Mar 02 23:42:58 fedora systemd[1]: Finished modprobe@fuse.service - Load Kernel Module fuse.
Mar 02 23:42:59 fedora mount[737]: Metadata kept in Windows cache, refused to mount.
Mar 02 23:42:59 fedora ntfs-3g[791]: Version 2022.10.3 integrated FUSE 28
Mar 02 23:59:35 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 02 23:59:40 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 02 23:59:45 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 02 23:59:50 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 02 23:59:55 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 03 00:00:00 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 03 00:00:05 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 03 00:00:10 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 03 00:00:15 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 03 00:00:20 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 03 00:00:25 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 03 00:00:30 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 03 00:00:35 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 03 00:00:40 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 03 00:00:45 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 03 00:00:50 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Mar 03 00:00:55 fedora touchegg[4897]: Error connecting to Touchégg daemon: Could not connect: Connection refused
Is not a Windows system partition but possibly a shutdown issue last login.
Yes, looks like it:
Mar 02 23:42:59 fedora mount[737]: Metadata kept in Windows cache, refused to mount.
If you boot back into Windows, shut down cleanly (and make sure fast startup is disabled) - and then come back into Fedora, does it mount correctly?
If you boot back into Windows, shut down cleanly (and make sure fast startup is disabled) - and then come back into Fedora, does it mount correctly?
Yes, it’s working now