Unable to mount an SMB share from cron
Yes, some things are different in the cron environment from your gtarsa environment. You can check the cron user environment for yourself using this "recipe". 

Since you can run your script manually, it seems likely you've set up your Samba passwords and permissions appropriately. 

You've chosen not to share your crontab entry, but I've mounted and umounted my Samba shares from a cron script with lines in my crontab like this: 

25 * * * * /sbin/mount -t smbfs //user:password@SambaServer/sharename /Users/seamus/SmbSrv01 

35 * * * * /sbin/umount /Users/seamus/SmbSrv01


This assumes a mountpoint declared (mkdir) at /Users/seamus/SmbSrv01

Since the cron user's path is not the same as gtarsa, you should check that you're using full path specifications to everything that's not in the cron user's PATH... or just everything if you're not sure.

Also NOTE: Putting userid and password in a script or a crontab as I've done here is something you should not do. Less insecure is putting the userid and password in ~/.bash_profile; e.g.:

export MOUNTUSERID="some_user" # where "some_user" is you, or a userid with Samba privileges 
export MOUNTUSERPWD="some_passwd" # "some_passwd" is "some_user" Samba password


Add these lines to the bottom of ~/.bash_profile, and use these environment vars with the mount command in your script. Before you run the script, reload ~/.bash_profile to pick up the environment variables you've just declared:

source ~/.bash_profile


&lt;redundant&gt;You've chosen not to share your crontab entry&lt;/redundant&gt;, but if you've not already done so you could help yourself by directing stderr from your script to a file for post-mortem analysis. In your crontab: 

* * * * * /full/path/to/script &gt;&gt; copy.log 2&gt;&amp;1  


will capture anything output to stderr in the file copy.log

Finally, if you're running your script under the @reboot spec, you should probably put a sleep command before you try to mount.

If none of this helps, please edit your Q to add your crontab entries, and as much of your script as possible and relevant.