Hi,
I am working on same config (deploying esxi 5.1 using autodeploy stateless caching) and had issues. If these are HP proliant blade server then these are arguments are fine "esx,local,hpsa"...the only issue is that if you are reusing old server which already had esx install and.even if you delete the raid (which doesn't delete the metadata completely - even erase utility from HP does not work) and recreate it ...the esxi installer reads disk properties and finds metadata on disk and considers it as snapshot volume..you can run command to verify that disk will be there but would need resignaturing. this is a bug (worked with vmware on this). Workable workaround is to reset all settings including erasing disk in bios....go back and reset date/time (reset sets it to default and if time is wrong auto deploy will not add host to vcenter), change boot order (pxe first, disk 2nd), go to controller and delete and then recreate array. After all these steps..autodeploy works like charm and configures boot banks and local datastore (reconfirm caching by booting to disk). let me know if you need any further help.