this post was submitted on 04 Jan 2024
21 points (92.0% liked)

Linux

48329 readers
1133 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

Here's the entry in the fstab file for mounting my hard drive. I have bolded the name of the hard drive (that's what it shows up as on the dock when it isn't mounted):

UUID=D4C0A66EC0A65710 /media/lucky/New Volume ntfs rw,auto,users,exec,nls=utf8,umask=003,gid=46,uid=1000    0   0

After making that entry in fstab, I execute the, systemctl daemon-reload, command, and then mount -a, afterwards which gives me this error.

you are viewing a single comment's thread
view the rest of the comments
[–] ozoned@lemmy.world 2 points 10 months ago* (last edited 10 months ago) (1 children)

You've made a directory path literally called

/media/lucky/New Volume

?

That REALLY doesn't seem like a good idea considering that *'s are wildcards for anything, and Linux isn't really fond of spaces.

The error basically tells you that you have an error on line 18, which I'm assuming is this line you're stating and that it's ignored that line so that it can still go on and mount other things.

Most likely you'd want something like:

# mkdir /media/lucky/NewVol

and then your fstab would be:

UUID=D4C0A66EC0A65710 /media/lucky/NewVol ntfs rw,auto,users,exec,nls=utf8,umask=003,gid=46,uid=1000 0 0

Also do you have a lib or something for linux to handle NTFS file system types? I haven't run Windows in 17 years now, so I don't have a clue if Linux can natively handle NTFS.

You can also run:

# lsblk

or

# blkid

to get the storage information and verify the storage UUID is correct.

[–] mmababes@lemmy.world 1 points 10 months ago* (last edited 10 months ago) (1 children)

That REALLY doesn’t seem like a good idea considering that *'s are wildcards for anything, and Linux isn’t really fond of spaces.

There are no asterisks in the fstab file. I put them here to emphasize the name of the hdd (I edited my original post to remove them to avoid confusing people).

Also do you have a lib or something for linux to handle NTFS file system types?

I'm using the ntfs-3g driver.

Btw this is what the entry on fstab looks like now but I'm still getting the parsing error:

UUID=D4C0A66EC0A65710 "/media/lucky/New Volume" ntfs rw,auto,users,exec,nls=utf8,umask=003,gid=46,uid=1000 0 0

[–] ozoned@lemmy.world 2 points 10 months ago (1 children)

But you have a space in there. I don't know how spaces are handled in fstab. You'll either need to quote it or at least escape the space:

UUID=D4C0A66EC0A65710 '/media/lucky/New Volume' ntfs rw,auto,users,exec,nls=utf8,umask=003,gid=46,uid=1000 0 0

OR

UUID=D4C0A66EC0A65710 /media/lucky/New\ Volume ntfs rw,auto,users,exec,nls=utf8,umask=003,gid=46,uid=1000 0 0

The space is absolutely an issue in fstab as it's thinking "Volume" is the filesystem type and ntfs goes into your options, etc.

[–] mmababes@lemmy.world 2 points 10 months ago* (last edited 10 months ago)

But you have a space in there. I don’t know how spaces are handled in fstab. You’ll either need to quote it or at least escape the space

Instead of using spaces or quotes (single or double), I used \040 (as @shortdorkyasian) said and that made all the difference:

UUID=D4C0A66EC0A65710 /media/lucky/New\040Volume/ ntfs rw,auto,users,exec,nls=utf8,umask=003,gid=46,uid=1000 0 0