Your problem seems to be about the permissions you have set. FAT / FAT32 formatted drives don't support file permissions. The permissions for everything are determined by how the drive is mounted. When you set the permission open it worked when you
server# sudo mount /dev/sdb2 /home/storage -o umask=000
As for it not auto mounting on reboot
UUID=8C52-C1CD /home/storage auto user,umask=000,utf8, -->noauto<-- 0 0
The "noauto" makes this NOT automatically mount when the system starts and parses the /etc/fstab file. Remove that option and it will mount on startup. You can set the permissions on the mount point once it's mounted with chmod or specify them in /etc/fstab.
If you need the media user to access it, you can set the permissions to 764, and add them to the security group. Root always has access to everything.
see http://www.linux.org/threads/file-permissions-chmod.4094/ for some examples of propper file permissions
On a side note, bodhi.zazen made a good point
Is there some reason you need to use FAT ? If not, I would back up the data and use a linux native file system. You can then set ownership and permissions.
First run df to see what device your external drive is, for example, for me the appropriate line looks like this:
/dev/sdc1 4883769340 2392246688 2491522652 49% /media/drew/LACIE-5GB
/media/drew/LACIE-5GB is where the disk got mounted and the appropriate device is /dev/sdc1 - this can change depending on how many external drives you have and in what order they were connected.
blkid /dev/sdc1
/dev/sdc1: LABEL="LACIE-5GB" UUID="703C31971BEBAA7E" TYPE="ntfs" PTTYPE="dos" PARTLABEL="LACIE-5GB" PARTUUID="6afdadd9-39ce-4875-b747-82cae734ae02"
The UUID is 703C31971BEBAA7E
So one can put a line like this into fstav:
UUID=703C31971BEBAA7E /media/drew/LACIE-5GB ntfs defaults,noauto,noatime,uid=1000,gid=1000,umask=0000,fmask=0111 0 0
Note that noauto is important - if the drive is not connected on startup and that option is not present, the boot halts and needs to be manually restarted. uid=1000,gid=1000,umask=0000,fmask=0111 are just options for NTFS not to make every file executable (which prompts Nautilus to ask if a file is to be displayed or run when I try to read a txt file, for example). noatime is the option originally requested.
Best Answer
I think there isn't.
But you can try a workaround: using
udevrules to override theudisksoptions by creating your own/etc/udev/rules.d/*.rulesfile; for details see this great Archlinux site.