I have never been able to get it to work at reboot. Are you saying to use the sudo mount before the mount pointIf it did work this way, try adding x-systemd.automout to your fstab entry
No. I'm saying (and I can't put it more clearly than this). With your current fstab entry:
- (re)boot the Pi
- Login and, if necessary, open a terminal.
- Check status of mount:
Code:
mountpoint /mnt/SynPi/homes - Run
Code:
sudo mount /mnt/SynPi/homes - Check status of mount:
Code:
mountpoint /mnt/SynPi/homes - Post results including any error message here.
and add the “ x-systemd.automount” as well and were does “x-systemd.automount” go, is it right after the mount? Like below?sudo mount /mnt/SynPi/homes x-system.automount /mnt/SynPi/homes cifs uid=1000,credentials=/home/farrissfpi/passwords/credentials.txt,iocharset=utf8,vers=3.0,noperm,nofail 0 0
No. You never need to put sudo into fstab. fstab has a fixed format and entries that do not follow it will be broken, unmountable, and may prevent system boot. You'd add ,x-systemd.automount after nofail and before 0 0.
You really need to read and digest my guide. Everything you need to sort this is in there. You may also want to read the output from man fstab and man mount.
FWIW, the fstab equivalent to your manual mount command is
Code:
//192.168.1.94/homes /mnt/SynPi/homes cifs defaults,username=f*****f,password=******** 0 0Statistics: Posted by thagrol — Mon Mar 11, 2024 3:16 pm