After making the change to fstab I suggested above did you try "sudo mount -av" or "sudo mount /home/pi/myFolder"?
Is there anything in the share? A mount point will look the same whether or not something is mounted there if the share is empty.
Have you looked at the output from"mount" after a reboot? If the mount has succeeded it will be listed there.
Have you looked in syslog or the output of "dmesg" for errors?
Have you set your Pi/raspbian to "Wait for Network at Boot"? See the "Boot Options" section of "sudo raspi-config". It's possible that the mount is being attempted before the network is up.
Are you running your script from root's crontab? Or you user's?
Are you capturing output and errors from your python script? Jobs started via cron have all their output discarded so you have to explictly send it somewhere. Try adding "> /tmp/my_mount.log 2>&1" to the end of your crontab entry (before any trailing & if you have one). You can then examine /tmp/my_mount.log for errors. Your crontab entry will looke something like this:
Code: Select all
@reboot /path/to/my_script.py > /tmp/my_mount.log 2>&1
Given that your script works from the terminal, my money is on the network not being ready when it's run from crontab.
Attempts to contact me outside of these forums will be ignored unless signed in triplicate, sent in, sent back, queried, lost, found, subjected to public enquiry, lost again, and finally buried in soft peat for three months and recycled as firelighters