i’ve actually changed options to defaults and seems working for now, but I kind of unsure if that was correct.
maybe if I get some problem I will use your way…
thanks btw for the info
This commands with -R will delete data ? I want to remount a disk/folder that i had previously mounted with gnome-disks, and i am kinda worried this -R will wipe everything
No it is just giving the command the Recursive Function meaning not only the folder but everything in the folder.
2 Likes
@thefrog is right.
What you should be afraid of if it is rm -r or rm -R. chown will only change which user owns the folder/file rights or permissions.
1 Like
There is no reason to use -R in that command in the first place.
It is an empty directory.
I think you may be talking about two different things
which mounting and owning are two different things 
Thinking about it i probably didn’t need to use the owning command again, because gnome-disk handled that, but i think its best if i just do everything the guide says from the begging
(sorry for the extensive editing, its early in the morning and i had a pretty shit sleep this night 
)
I never really got errors until recently but its much worse. Its not reliable for me to use systemd mounting.
Jun 03 03:00:23 saiyaman-b550gamingxv2 systemd[1]: Dependency failed for /mnt/Gaming.
Jun 03 03:00:23 saiyaman-b550gamingxv2 systemd[1]: Dependency failed for /srv/nfs/shares/gaming.
Jun 03 03:00:23 saiyaman-b550gamingxv2 systemd[1]: srv-nfs-shares-gaming.mount: Job srv-nfs-shares-gaming.mount/start failed with result ‘dependency’.
Jun 03 03:00:23 saiyaman-b550gamingxv2 systemd[1]: mnt-Gaming.mount: Job mnt-Gaming.mount/start failed with result ‘dependency’.
Jun 03 03:00:23 saiyaman-b550gamingxv2 systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/c19d679e-b447-45cd-b7bb-41a7f4c3a23c.
Jun 03 03:00:23 saiyaman-b550gamingxv2 systemd[1]: systemd-fsck@dev-disk-by\x2duuid-
EDIT: Shortened the post. What worked for me is turning off the fsck option. Some of these disks don’t have partitions they’re just filesystems (opps).
Still issues on the secondary nvme.
Final EDIT: I’m a dummy and the reason the NVME doesn’t seem to be mounted at boot is because nothing accesses it which is a feature of the systemd mounting. I assume that is what happens as it gets mounted soon as an application accesses it.
The issues I had just went away with a new kernel. No changes at all but I notice now my fstab has arrows in it before the spaces. I have no idea what this is and I didn’t put it there. Also it was never an issue when it wouldn’t mount. It would go into emergency mode and I would just ctrl+D to continue and all my storage was mounted like nothing had ever happened.