I normally use automatic IP address. But I tried a static IP now and the problem persists.
The below facts (I think) strengthen the hypothesis that the error is caused by the mount being attempted before the WiFi connection is ready:
As you report, mounts seem to work when using network cable. Only boot-ups with WiFi are affected.
For me, some of the times (10-20%) the mount actually does work with WiFi. This is consistent with the duration of WiFi connection establishment varying a little.
If this is the case introducing a short delay (a second or two) before the mount is attempted could solve the problem. Unfortunately I don’t know if this change easily can be made using SSH to test this.
faint feeling: connection rejected before the network is up.
Reason why I think so: it happened here occasionally, when I store the current values in the edit window it connects
@bakechad: Thanks for your effort, I think you’re on to something, However, I made the change to /boot/cmdline.txt but the NAS still won’t mount automatically on startup…
I have this problem as well. Raspberry pi 2 B on wifi. Adding the rootdelay=30 or rootdelay=60 did not fix the issue. Always connects to the NAS right away one I re-enter the NAS login in the My Music screen of the UI.
I have been running the RC2 hotfix version since it came out and it has never connected automatically on reboot for me.
I have the same problem connecting to nas! It works fine after mounting “manually” until next start, regardless of whether hard reset or software reboot.