How to properly mount other partitions (NTFS) on my Fedora FSH?
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
I recently switched to Fedora 27 Beta (UEFI install, dual-boot with Win 10), and I changed my /etc/fstab to include the two following lines:
UUID=D0E24ECDE24EB78C /media/DownloadsBin ntfs-3g auto,user,rw,x-gvfs-show 0 0
UUID=4E565C9C565C869D /media/VMs ntfs-3g auto,user,rw,x-gvfs-show 0 0
It should have loaded the devices bearing the given UUIDs into /media/DownloadsBin and /media/VMs appropriately with rw permissions, right? Well, since these are Windows partitions, I had to mount them using NTFS-3g. I can see the files, but whenever I even try to create a new folder (e.g. using mkdir test), I get the error:
mkdir: cannot create directory ‘test’: Read-only file system
The strange part is a similar script worked before on Fedora 26, although I'm not sure if it's got something to do with Fedora 27 Beta (a bug?!) or if there's an error in my code. So, I've come to ask the experts for help!
NOTE : I really don't want to mess around with partition or the folder permissions, especially changing the owner, since Windows started complaining and stopped me from writing to the disk the last time I tried this! I'm hoping there's a better way I can share entire partitions between Win 10 and Fedora 27 Beta without pissing either operating system off?!
Upon further investigation, it turns out that the partitions might be mounted as read-only as confirmed by findmnt /media/(dir):
[somu@lappyPrime DownloadsBin]$ findmnt /media/DownloadsBin TARGET
SOURCE FSTYPE OPTIONS /media/DownloadsBin /dev/sda5 fuseblk
ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096
[somu@lappyPrime DownloadsBin]$ findmnt /media/VMs TARGET SOURCE
FSTYPE OPTIONS /media/VMs /dev/sda6 fuseblk
ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096
Can anyone tell me what's going on?!
fedora fstab readonly uuid ntfs-3g
edited Jan 20 at 17:45
Jeff Schaller
32.3k849109
asked Oct 10 '17 at 15:46
Somenath Sinha
223110
 |Â
show 1 more comment
up vote
2
down vote
favorite
I recently switched to Fedora 27 Beta (UEFI install, dual-boot with Win 10), and I changed my /etc/fstab to include the two following lines:
UUID=D0E24ECDE24EB78C /media/DownloadsBin ntfs-3g auto,user,rw,x-gvfs-show 0 0
UUID=4E565C9C565C869D /media/VMs ntfs-3g auto,user,rw,x-gvfs-show 0 0
It should have loaded the devices bearing the given UUIDs into /media/DownloadsBin and /media/VMs appropriately with rw permissions, right? Well, since these are Windows partitions, I had to mount them using NTFS-3g. I can see the files, but whenever I even try to create a new folder (e.g. using mkdir test), I get the error:
mkdir: cannot create directory ‘test’: Read-only file system
The strange part is a similar script worked before on Fedora 26, although I'm not sure if it's got something to do with Fedora 27 Beta (a bug?!) or if there's an error in my code. So, I've come to ask the experts for help!
NOTE : I really don't want to mess around with partition or the folder permissions, especially changing the owner, since Windows started complaining and stopped me from writing to the disk the last time I tried this! I'm hoping there's a better way I can share entire partitions between Win 10 and Fedora 27 Beta without pissing either operating system off?!
Upon further investigation, it turns out that the partitions might be mounted as read-only as confirmed by findmnt /media/(dir):
[somu@lappyPrime DownloadsBin]$ findmnt /media/DownloadsBin TARGET
SOURCE FSTYPE OPTIONS /media/DownloadsBin /dev/sda5 fuseblk
ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096
[somu@lappyPrime DownloadsBin]$ findmnt /media/VMs TARGET SOURCE
FSTYPE OPTIONS /media/VMs /dev/sda6 fuseblk
ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096
Can anyone tell me what's going on?!
fedora fstab readonly uuid ntfs-3g
edited Jan 20 at 17:45
Jeff Schaller
32.3k849109
asked Oct 10 '17 at 15:46
Somenath Sinha
223110
once mounted run mount -o remount rw /mountpoint
– Alex Austin
Oct 10 '17 at 22:37
Why do you usentfs-3gand notntfs?
– Michael Hampton
Jan 20 at 17:51
@MichaelHampton ntfs-3g is the available option for read-write access to ntfs.ntfsis the kernel filesystem type, which only ever had experimental write support, I don't even know if it exists anymore because it's not very useful.
– sourcejedi
Jan 20 at 21:11
What happens if you unmount the FS and mount it manually? Does it show any warning? Note, systemd did not save mount messages to the system log due to an oversight which I submitted a patch for a few days ago :).
– sourcejedi
Jan 20 at 21:13
@sourcejedi Er, ntfs is still around, still has write support and still works. AFAIK ntfs-3g is the outdated filesystem.
– Michael Hampton
Jan 20 at 21:16
 |Â
show 1 more comment
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I recently switched to Fedora 27 Beta (UEFI install, dual-boot with Win 10), and I changed my /etc/fstab to include the two following lines:
UUID=D0E24ECDE24EB78C /media/DownloadsBin ntfs-3g auto,user,rw,x-gvfs-show 0 0
UUID=4E565C9C565C869D /media/VMs ntfs-3g auto,user,rw,x-gvfs-show 0 0
It should have loaded the devices bearing the given UUIDs into /media/DownloadsBin and /media/VMs appropriately with rw permissions, right? Well, since these are Windows partitions, I had to mount them using NTFS-3g. I can see the files, but whenever I even try to create a new folder (e.g. using mkdir test), I get the error:
mkdir: cannot create directory ‘test’: Read-only file system
The strange part is a similar script worked before on Fedora 26, although I'm not sure if it's got something to do with Fedora 27 Beta (a bug?!) or if there's an error in my code. So, I've come to ask the experts for help!
NOTE : I really don't want to mess around with partition or the folder permissions, especially changing the owner, since Windows started complaining and stopped me from writing to the disk the last time I tried this! I'm hoping there's a better way I can share entire partitions between Win 10 and Fedora 27 Beta without pissing either operating system off?!
Upon further investigation, it turns out that the partitions might be mounted as read-only as confirmed by findmnt /media/(dir):
[somu@lappyPrime DownloadsBin]$ findmnt /media/DownloadsBin TARGET
SOURCE FSTYPE OPTIONS /media/DownloadsBin /dev/sda5 fuseblk
ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096
[somu@lappyPrime DownloadsBin]$ findmnt /media/VMs TARGET SOURCE
FSTYPE OPTIONS /media/VMs /dev/sda6 fuseblk
ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096
Can anyone tell me what's going on?!
fedora fstab readonly uuid ntfs-3g
edited Jan 20 at 17:45
Jeff Schaller
32.3k849109
asked Oct 10 '17 at 15:46
Somenath Sinha
223110
I recently switched to Fedora 27 Beta (UEFI install, dual-boot with Win 10), and I changed my /etc/fstab to include the two following lines:
UUID=D0E24ECDE24EB78C /media/DownloadsBin ntfs-3g auto,user,rw,x-gvfs-show 0 0
UUID=4E565C9C565C869D /media/VMs ntfs-3g auto,user,rw,x-gvfs-show 0 0
It should have loaded the devices bearing the given UUIDs into /media/DownloadsBin and /media/VMs appropriately with rw permissions, right? Well, since these are Windows partitions, I had to mount them using NTFS-3g. I can see the files, but whenever I even try to create a new folder (e.g. using mkdir test), I get the error:
mkdir: cannot create directory ‘test’: Read-only file system
The strange part is a similar script worked before on Fedora 26, although I'm not sure if it's got something to do with Fedora 27 Beta (a bug?!) or if there's an error in my code. So, I've come to ask the experts for help!
NOTE : I really don't want to mess around with partition or the folder permissions, especially changing the owner, since Windows started complaining and stopped me from writing to the disk the last time I tried this! I'm hoping there's a better way I can share entire partitions between Win 10 and Fedora 27 Beta without pissing either operating system off?!
Upon further investigation, it turns out that the partitions might be mounted as read-only as confirmed by findmnt /media/(dir):
[somu@lappyPrime DownloadsBin]$ findmnt /media/DownloadsBin TARGET
SOURCE FSTYPE OPTIONS /media/DownloadsBin /dev/sda5 fuseblk
ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096
[somu@lappyPrime DownloadsBin]$ findmnt /media/VMs TARGET SOURCE
FSTYPE OPTIONS /media/VMs /dev/sda6 fuseblk
ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096
Can anyone tell me what's going on?!
fedora fstab readonly uuid ntfs-3g
fedora fstab readonly uuid ntfs-3g
edited Jan 20 at 17:45
Jeff Schaller
32.3k849109
asked Oct 10 '17 at 15:46
Somenath Sinha
223110
edited Jan 20 at 17:45
Jeff Schaller
32.3k849109
asked Oct 10 '17 at 15:46
Somenath Sinha
223110
edited Jan 20 at 17:45
Jeff Schaller
32.3k849109
edited Jan 20 at 17:45
Jeff Schaller
32.3k849109
edited Jan 20 at 17:45
Jeff Schaller
32.3k849109
32.3k849109
asked Oct 10 '17 at 15:46
Somenath Sinha
223110
asked Oct 10 '17 at 15:46
Somenath Sinha
223110
asked Oct 10 '17 at 15:46
Somenath Sinha
223110
223110
once mounted run mount -o remount rw /mountpoint
– Alex Austin
Oct 10 '17 at 22:37
Why do you usentfs-3gand notntfs?
– Michael Hampton
Jan 20 at 17:51
@MichaelHampton ntfs-3g is the available option for read-write access to ntfs.ntfsis the kernel filesystem type, which only ever had experimental write support, I don't even know if it exists anymore because it's not very useful.
– sourcejedi
Jan 20 at 21:11
What happens if you unmount the FS and mount it manually? Does it show any warning? Note, systemd did not save mount messages to the system log due to an oversight which I submitted a patch for a few days ago :).
– sourcejedi
Jan 20 at 21:13
@sourcejedi Er, ntfs is still around, still has write support and still works. AFAIK ntfs-3g is the outdated filesystem.
– Michael Hampton
Jan 20 at 21:16
 |Â
show 1 more comment
once mounted run mount -o remount rw /mountpoint
– Alex Austin
Oct 10 '17 at 22:37
Why do you usentfs-3gand notntfs?
– Michael Hampton
Jan 20 at 17:51
@MichaelHampton ntfs-3g is the available option for read-write access to ntfs.ntfsis the kernel filesystem type, which only ever had experimental write support, I don't even know if it exists anymore because it's not very useful.
– sourcejedi
Jan 20 at 21:11
What happens if you unmount the FS and mount it manually? Does it show any warning? Note, systemd did not save mount messages to the system log due to an oversight which I submitted a patch for a few days ago :).
– sourcejedi
Jan 20 at 21:13
@sourcejedi Er, ntfs is still around, still has write support and still works. AFAIK ntfs-3g is the outdated filesystem.
– Michael Hampton
Jan 20 at 21:16
once mounted run mount -o remount rw /mountpoint
– Alex Austin
Oct 10 '17 at 22:37
once mounted run mount -o remount rw /mountpoint
– Alex Austin
Oct 10 '17 at 22:37
Why do you use
ntfs-3g and not ntfs?– Michael Hampton
Jan 20 at 17:51
Why do you use
ntfs-3g and not ntfs?– Michael Hampton
Jan 20 at 17:51
@MichaelHampton ntfs-3g is the available option for read-write access to ntfs.
ntfs is the kernel filesystem type, which only ever had experimental write support, I don't even know if it exists anymore because it's not very useful.– sourcejedi
Jan 20 at 21:11
@MichaelHampton ntfs-3g is the available option for read-write access to ntfs.
ntfs is the kernel filesystem type, which only ever had experimental write support, I don't even know if it exists anymore because it's not very useful.– sourcejedi
Jan 20 at 21:11
What happens if you unmount the FS and mount it manually? Does it show any warning? Note, systemd did not save mount messages to the system log due to an oversight which I submitted a patch for a few days ago :).
– sourcejedi
Jan 20 at 21:13
What happens if you unmount the FS and mount it manually? Does it show any warning? Note, systemd did not save mount messages to the system log due to an oversight which I submitted a patch for a few days ago :).
– sourcejedi
Jan 20 at 21:13
@sourcejedi Er, ntfs is still around, still has write support and still works. AFAIK ntfs-3g is the outdated filesystem.
– Michael Hampton
Jan 20 at 21:16
@sourcejedi Er, ntfs is still around, still has write support and still works. AFAIK ntfs-3g is the outdated filesystem.
– Michael Hampton
Jan 20 at 21:16
 |Â
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f397256%2fhow-to-properly-mount-other-partitions-ntfs-on-my-fedora-fsh%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
once mounted run mount -o remount rw /mountpoint
– Alex Austin
Oct 10 '17 at 22:37
Why do you use
ntfs-3gand notntfs?– Michael Hampton
Jan 20 at 17:51
@MichaelHampton ntfs-3g is the available option for read-write access to ntfs.
ntfsis the kernel filesystem type, which only ever had experimental write support, I don't even know if it exists anymore because it's not very useful.– sourcejedi
Jan 20 at 21:11
What happens if you unmount the FS and mount it manually? Does it show any warning? Note, systemd did not save mount messages to the system log due to an oversight which I submitted a patch for a few days ago :).
– sourcejedi
Jan 20 at 21:13
@sourcejedi Er, ntfs is still around, still has write support and still works. AFAIK ntfs-3g is the outdated filesystem.
– Michael Hampton
Jan 20 at 21:16