Please Help…
I cannot mount NTFS Disk with rw mode on booting…
I added this to /etc/fstab
UUID=2C24110D2410DC20 /run/media/reredrum/Data\040Disk ntfs-3g user,rw,nofail,auto 0 0
and also tried
UUID=2C24110D2410DC20 /run/media/reredrum/Data\040Disk ntfs-3g defaults 0 0
but NTFS disk was mounted as Read-Only mode…
So cannot use this disk as a storage…
What should I do?
Please help me!!
My own personal recommendation would be to format the drive to a Linux native file system such as ext4, and then chown the drive.
See:
man chown
Welcome to the Garuda community @reredrum. 
...reredrum/Data\040Disk...
I have never used backslash and I have never seen anyone use backslash while specifying a directory on Linux.
I use the KDE’s application called KDE Partition Manager to auto mount on boot, rather than manually editing /etc/fstab
Thank you… I solved it… with KDE partition Manager you said!!
& That tool adds same option I wrote to fstab… but manual editing doesn’t work, but editing with KDE tool works… -o-;; I don’t know the defference…haha~~!
Have a good day~~!
\040 is the octal representation of the space character in ASCII. It appears the user named their mount point “Data Disk” (with a space in it).
Another way this could be written is with quotes:
UUID=2C24110D2410DC20 "/run/media/reredrum/Data Disk" ntfs-3g user,rw,nofail,auto 0 0
Or using a backslash to escape the space directly:
UUID=2C24110D2410DC20 /run/media/reredrum/Data\ Disk ntfs-3g user,rw,nofail,auto 0 0
It seems they used an application to automatically generate the fstab entry, and for some reason the application represents space characters with octal ASCII.
Yeah, that’s what I do too. Wouldn’t using backslash before 0 would just result in the shell just interpreting it as 0?
EDIT:
Apparently it doesn’t just interpret it as 0.
╰─λ echo data\040data
data data
Perhaps this would be an appropriate time to mention that adding spaces when naming drives in Linux only complicates things greatly. Best to always use an underscore or a dash between separate words when naming drives. If you ever require a script that calls that drive, you will find white spaces in a name will make for far more trouble than it’s worth.
IMO you need to start learning to do things the Linux way, and not simply continue doing things the way you’ve always done things in Windows. As with white spaces in drive names, using Windows file systems in Linux is simply looking for problems down the road. Search the forum and you will usually find at least one thread a week from someone who uses an NTFS drive that has become corrupted and is unmountable. Using NTFS with Linux is like playing Russian roulette with your data, sooner or later you will suffer a data loss because Linux was not designed to run with Windows file systems. In most cases (if you are lucky), the corruption can be corrected on an NTFS drive. However, if your luck runs out and the drive corruption is uncorectable, you can kiss your data goodbye.
If you intend to continue using Linux then you need to do further researching on fstab usage. There are fstab options that can help to limit the regular NTFS drive corruptions that occur because of the differences in naming conventions between Linux and Windows. Using a utility to set your drive options in fstab usually results in less than optimal choices being set for mounting an NTFS drive.
I’m not trying to be be negative towards you and give you a hard time, I’m trying to help simplify your transition to Linux. I’m trying to help you realize that continuing to do things the “Windows way” will make your life far more difficult down the road if you want to continue using Linux. Better to accept Linux for what it is, than to try and bend it into a twisted replica of Windows.
Good luck on your transition to Linux @reredrum.
I formatted all the drives to exFAT that I share between Windows and Linux. Is that safe?
Lots of people use exFAT, but I do not personally think it is a good choice. ExFat is not a journaled file system and is prone to corruption if a power outage or crash occurs.
I have not used Windows for many years, so I stick to the rock solid reliability of ext4 for all my storage drives.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.