25
Issue with mounting 2nd drive on boot
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 31 May 2024
25 points (100.0% liked)
Linux
48047 readers
688 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
No, I did see some tutorials on using that, but they said that any mistake could result in crashes and having an ubootable pc.. so I didn't want to risk it.
You can always check its consistency if you run a
mount -aafter editing fstab. But yeah, an error in the file can cause some annoyance-Backup the file and have a live USB ready just in case.
Already had to use it and timeshift back lol.
You do need to be careful, but you can check for errors after editing
/etc/fstabby running the commandsudo 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/fstaband 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 -aand 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.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
At the terminal, go to the directory that contains the mount point for the disk (so if the mount point is
/mnt/diskgo to/mnt.Run
ls -l. This should list everything in/mntwith the owners and permissions. If your mount point (in this exampledisk) is owned by user and grouproot, 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 diskReplace each instance of
userwith your system username (if you’re not sure what you’re username is runwhoamiand it will tell you), and replacediskwith your mount point directory.Here’s what this does:
sudo: escalates your privileges to run thechowncommandchown: the utility that allows you to change ownership of files and directories-R: tellschownto change ownership recursivelyuser:userspecifies 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.Thank you! This worked!
Awesome! Glad I could help.
I love this comment because it explains the keywords in the command. Hats off to you.
NTFS?
No, ext4
In that case you can use chown
I followed another commenter's guide using that command and it worked, thanks
You can always boot a live environment and edit the file from there if anything goes wrong.