Linux

48372 readers

1150 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 5 years ago

MODERATORS

[email protected]

Issue with mounting 2nd drive on boot (self.linux)

submitted 6 months ago by WeebLife to c/[email protected]

23 comments fedilink hide all child comments

Bonjour tout le monde,

I have finally fully installed linux mint and have been working on getting everything up and running. So far, I haven't had many issues, but I am having trouble with my 2nd drive. I just want my 2nd drive to mount on boot, and for programs to be able to write to it.

I have looked up guides on pulling up the disks in mint and going into the mount options and selecting mount on boot. This works, but for some reason, programs lose permission to write to it. When I switch the drive back to 'user session defaults' programs can write to it, but it doesn't mount on boot. I haven't found anyone mentioning this problem so I thought I would post here. Also, my home folder isn't encrypted and when I go to permissions on the drive, it says 'permissions could not be determined'

Thanks

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 6 months ago (1 children)

You do need to be careful, but you can check for errors after editing /etc/fstab by running the command sudo mount -a. With the drive attached but not mounted. (Also good practice to use the UUID of the drive in the fstab entry)

That command runs through etc/fstab and attempts to mount everything it is instructed to mount if it is not already mounted. And if there is an error it will let you know.

If you run sudo mount -a and you get no output in the terminal, then there are no errors, your drive should now be mounted, and you should be fine for reboots and it should mount on startup as expected.

[–] WeebLife 2 points 6 months ago (2 children)

I followed the video tutorial that was in another comment and it worked but my programs still can't write to it due to lacking permissions

[–] [email protected] 4 points 6 months ago (2 children)

At the terminal, go to the directory that contains the mount point for the disk (so if the mount point is /mnt/disk go to /mnt.

Run ls -l. This should list everything in /mnt with the owners and permissions. If your mount point (in this example disk) is owned by user and group root, then you just need to change ownership of the mount point and the disk attached.

With the disk attached, run sudo chown -R user:user disk

Replace each instance ofuser with your system username (if you’re not sure what you’re username is run whoami and it will tell you), and replace disk with your mount point directory.

Here’s what this does:

sudo: escalates your privileges to run the chown command
chown: the utility that allows you to change ownership of files and directories
-R: tells chown to change ownership recursively
user:user specifies the user and group that will own the files/directories you are modifying.
disk: specifies the file(s)/directories you want to change ownership for.

[–] WeebLife 3 points 6 months ago (1 children)

Thank you! This worked!

[–] [email protected] 2 points 6 months ago

Awesome! Glad I could help.

[–] [email protected] 2 points 5 months ago

I love this comment because it explains the keywords in the command. Hats off to you.

[–] [email protected] 1 points 6 months ago (1 children)

NTFS?

[–] WeebLife 1 points 6 months ago (1 children)

No, ext4

[–] [email protected] 1 points 6 months ago (1 children)

In that case you can use chown

[–] WeebLife 1 points 6 months ago

I followed another commenter's guide using that command and it worked, thanks