I'm running Ubuntu 10.04 with Motion 3.2.12

When I start motion from the command line using
sudo motion
All is good
[0] Processing thread 0 - config file /usr/local/etc/motion.conf
[0] Motion 3.2.12 Started
[0] Motion going to daemon mode

When I auto start motion at startup and do
tail -f /var/log/syslog
I can see the error message
motion: [1] ffopen_open error creating (new) file [/media/d9a465a2-df61-429d-9494-f76a12aa69f4/motion/01-20120701162955]:

If I change the drive motion is writing to, to /tmp it works

I've tried setting drive owner/group permissions
ls /media/d9a465a2-df61-429d-9494-f76a12aa69f4/motion -al
total 361557960
drwxrwxrwx 3 root root 499712 2012-07-01 16:32 .
drwxrwxrwx 13 motion motion 4096 2012-06-29 07:36 ..

I think the mount command is correct

/dev/sdc1 on /media/d9a465a2-df61-429d-9494-f76a12aa69f4 type ext4 (rw,noexec,nosuid,nodev)

What am I missing, does the daemon have different permissions when its autostarted vs using sudo motion?