As some of you know I plan to install Win 10 and Garuda for my roommate. Today under Manjaro he asked me to install and setup a new drive to replace a failing one. Normally a no brainer, just remove the old drive, add the new one, format it, and mount it. Today however I noticed that two of his mounts were messed up. The first one being the drive that got replaced /home/whacker/Whackers/TV Series was mounted to /home/whacker/Whackers/Music and the second one Music was mounted to /home/whacker/Whackers/TV Series. Now the issue is that I got the TV Series drive mounted correctly and showing in fstab, the Music drive / mount is not listed in fstab for some reason. I believe what happened is when I went to correct the mount point for Music I didn't unmount the TV Series thus not allowing for the mount point of Music to be changed from /home/whacker/Whackers/TV to /home/whacker/Whackers/Music. What I'd like to do is add the proper line in fsbtab to get the Music mount to properly mount. Normally I'd just use Gparted to simply recreate the partition and copy everything back to it from the Master Backup, but there's 2+ gigs to copy back from a USB 3.0 drive to a USB 3.0 drive. I believe it would be far faster to fix the current mounting than to copy the files back. Help with this would be greatly appreciated. Thanks
I know it's not the Manjaro forums. I posted here cause between tomorrow and Thrusday I'll be getting his new Win 10 and Garuda installed and once set up the Manjaro disk will be reset and removed from the system. I just didn't want to hit up the Manjaro forums for what would probably be the last question asked there for now.
Now that said you mean something like this?
`UUID=6dfbe343-3531-4452-89c0-e47824758ec8 auto /home/whacker/whackers/Music/ auto nosuid,nodev,nofail,x-gvfs-show
If so will that override and replace it trying to mount to TV Series?
The true shame is why couldn't the one drive hold out for another 3 days. I wouldn't of even had to create this thread then.
The system's memory on mounts is only the contents of fstab. mtab is reset after each reboot.
It seems like a user mistake.
I would like to mention that there is a mistake in all previous posts on possible or actual fstab entries, which may not be actual, just human memory errors
The auto flag (FS type) is entered twice, of which the 1st occurrence should not exist. It's an example of how an error may create a problem
I find fstab a very interesting Linux feature that volumes could be written about all its permutations for mounting. It's almost like black magic mastering all its combinations of options.
I enjoy using fstab, but I'm sure most users new to Linux dread having to edit fstab. Always be sure to make a copy before editing the original. Not quite as necessary with btrfs and timeshift, but still a good habit to get into all the same.
But, seriously I feel that sometimes the options it selects are not the best. Also if you ever intend to do advanced stuff like mounting shares, bind mounts etc, then you really need to do some RTFM.
Just from looking at his prior fstab configuration, I'm pretty sure he already used disks to write his load line. Disks fingerprints are all over it, and as I say I'm not keen on some of it's decisions for options.
I always make a backup of any important file I have to edit or manually replace just in case. Linux like Windows isn't that hard to get into to replace the original if need be and be back where one was. Looks like I will have to use the original command I put together to get auto-mount. That correction @jonathon posted does not have the two drives auto-mount.
@SGS I actually prefer using Disk rather than fstab, but the bright side this issue taught me something new.
@tbg Calling using Disk cheating is an opinion, As for the options it selects it typically selects to have the volume auto-mount and not have to be manually mounted. At least when you manually edit the volumes mount settings in Disk.
It really really wasn't even an opinion, it was more of a joke. That's why there was a smiley at the end of my sentience, (so you'd get that I was just kidding around). This isn't EnOS or Arch, this distro is chock full of GUI tools for those that prefer them. Just in case you hadn't noticed all the new GUI system tools, we probably have far more GUI system config apps than most any other Arch based distro now.
The guys are busy developing more GUI tools to assist newbies all the time. This distro's probably more GUI friendly than most other Arch flavors I'd say. There's absolutely nothing wrong with using a GUI tool rather than the terminal or editing config files by hand.
My real opinion is however that sometimes editing a config file by hand gives you more fine grained control than a GUI app that makes rather more generic one size fits all type decisions. There's nothing wrong with using a GUI app to make those decisions. However, if you need to mount things in a more advanced manner you don't have a lot of other ways to do some of those things except via editing config files by hand. Some advanced methods of mounting really don't have any GUI tools available in Linux yet. So you don't have much alternatives except learning fstab usage or in some cases there might be an app (but it's not GUI).
@tbg I wrote that post in a hurry while in the middle of cooking dinner and half starving, so my apologies it wasn't my intention to step on anyones toes. To be honest I probably paid more attention to the post above yours. As for the GUI friendly that's exactly why I selected Garuda for my roommate. Myself I do prefer EOS cause I can build it to my liking without being as barebones as pure Arch. Unfortunately there are a couple on the EOS forums that are true Terminal diehards and true ***es to anyone using any GUI app.
Now that said I'm more than willing to get under the hood with a proper tut, and if I know in the particular instance it is either going to be faster or as you said give me better control over what I'm trying to do.
As for the mounting agree. As far as I know with whatever caused the issue on Gary's system going in to fstab or correcting via the terminal were my best options.
The thing with the terminal is I know I screw up with the keyboard a lot and I mean a lot, so I get a bit leery typing thing into the terminal without a cut and paste option from some tut I found or something someone posted trying to help me.
Now for those celebrating Turkey day please be salf while still enjoying the day.