Linux Mint Forums

I think the problem with nofail is how you interprit If the NAS is not connected . If the NAS is not available when the system boots nofail works just as you describe. It will not stop or stall booting if the NAS is not available. But at some point after boot and login the NAS does become available ...

I haven't used NFS this century but if you want it to mount automatically at boot why are you using the noauto option: 192.168.1.100:/volume1/homes /home/denbigh/NAShome nfs nouser,vers=3,rsize=8192,wsize=8192,atime, noauto ,rw,dev,exec,suid 0 0 Perhaps in NFS noauto has a different meaning but for ...

I have two USB drives (one HDD, one SSD) mounted to the VM via /etc/fstab Depending on the desktop environment you use: If the mount point is under your home directory or under /media the mount icon will appear on your desktop. If it's anywhere else it will not unless you add to your fstab statemen...

I guess this proves I have no real life but I was reading through your original posts and found this: If I launch a player and try to play a music file, it gives a message error, something like "obsolete file". I wonder if the actual error message ( in english ) concerned " stale file...

At the same time a folder was automatically mounted (fritzbox on nas), Since I don't know what that means or how that can happen from a cifs mount it appears I can't help you. If I can't personally solve a samba issue in less than 5 or 6 posts I try to reproduce the situation on my systems but in t...

So why isn't the correct way to address this share this: //192.168.0.1/NASSOX /media/nas ... And if there is some sort of conflict with permissions remember cifs is a virtual filesystem you can make it anything you want. //192.168.0.1/NASSOX /media/nas cifs nounix,dir_mode=0777,file_mode=0666,nofail...

Avm assistance keeps saying to try both //mystaticip//sharename and //fritz.box/sharename, where in this case sharename = /nas#/files/NASBOOK The advice AVM is giving you is textbook correct since it should be //server-name/share-name but what you state as the share is confusing since it appears th...

I've got a suspicion the Fritzbox is using samba in a weird way. I downloaded the user manual for your device and found this for MacOS: macOS Open the Finder. Click "Go" and then "Connect to Server" in the menu bar of the Finder. Enter smb://fritz.box in the "Server Address:...

Could you provide one more piece of information please: Install nmap: sudo apt install nmap THen run this command and post the output: nmap -Pn --script smb-protocols ip-address-of-fritz-box EDIT : You've got too many commas there: //xxx.xxx.xxx.1/sharefolder /media/sharefolder cifs x-systemd.automo...

systemd which controls everything in Linux already knows it's a network device. If you replace _netdev,auto with x-systemd.automount you transfer how and more importantly when it will mount the share to systemd. I think the issue may be that it's not mounting at boot time. x-systemd.automount will o...

There's always the systemd method. Change your mount expression to this:

LABEL=SSD /mount/SSD auto nosuid,nodev,nofail,x-gvfs-show,noauto,x-systemd.automount 0 0

This will also not mount at boot. It will only mount when the mountpoint is accessed. It does this seamlessly.

I am confused by this observation: I can connect it to the network drive with the commands given above, but after reboot the players do not load the files, while I can see under /media/sharefoldername all the contents. If you can "see" all the files you have read access to the mounted shar...

I have a suggestion but you are not going to like it: Change the mount point to be under /media ... something like /media/SSD. Then change the mount declaration from this: LABEL=SSD /mount/SSD auto nosuid,nodev,nofail,x-gvfs-show,noauto 0 0 To this: LABEL=SSD /media /SSD auto nosuid,nodev,nofail,x-g...

The partitions labeled SSD, Project, HDD, and Documents all have the same set of options in their mount declarations: auto nosuid,nodev,nofail , noauto , x-gvfs-show 0 0 None of those partitions will mount automatically at boot because of the noauto option. Do you want them to mount at boot? If you ...

Please post the output of the following commands so the folks here can see how you are set up:

You can add yet another option to the list x-gvfs-hide but that will prevent any mount icon from being generated - just as it would if you mounted this under /mnt.

You can try replacing the auto option with x-systemd.automount : //192.168.50.9/Documents /home/longtallmatt/Videos/Documents cifs credentials=/home/longtallmatt/.smbcreds, uid=longtallmatt,user ,x-systemd.automount 0 0 But your chances would be better with x-systemd.automount if you mounted this so...

The next major hurdle for Desktop Linux is to overtake Unknown:

Well, kind of, but as I already mentioned, why is that information not available in the file manager? Seems counter-intuitive to me. As far as I can tell, Nemo is labelled as a file manager. A file manager should have access to all files. To display that information, it needs to relate the location...

That I would need ANOTHER program to list disks other than the default File Manager? WT*?

Open a terminal and run: Is that what you want?