I’d start by rebooting the fog server. That should clear whatever is locking the directory.
I’ve done this at least 2-3 times with great success so I know it can be done.
Even if the NAS can use NFS it’s still a little hokey because of the FTP issue discussed in the [URL=‘http://www.fogproject.org/wiki/index.php/FOGUserGuide’]Wiki[/URL], “[B]KNOWN ISSUE[/B] You will get an error “Ftp connection to storage server has failed” at the end of uploading images though. You will have to manually rename and move the file from the dev directory to the directory below.”
I ended up getting around the issues by using VMware. I installed centos6 and FOG in a VM. I iSCSI attached my NAS to VMware and added another disk to the VM using the iSCSI as the source. I then mounted the new disk under /images.
It would be nice if in .33 the whole FTP thing went away since the client already has NFS access to the FOG server. It would be nicer to just have the clients pull directly from the NAS instead of routing the traffic through the FOG server. hint hint
I have been plagued for about a week with a LSASS requested operation was unsuccessful error. It happens shortly on boot after a successful XP image deployment on Dell laptops (my HP laptops never had this error). After examining everything I could think of I finally figured out what the problem is and I wanted to share the issue and recommend a change to FOG to prevent this for others.
The problem was the computer name length. The netbios name length is limited to 15 characters but in the FOG host screen you are allowed 16 characters. I was creating the host name by prepending the autogenerated host name MAC with Dell so my computer name was Dell123456789012… thus 16 characters. (My HPs were only 14 characters so they never had the issue…)
Please consider changing the Host Name length to restrict it to 15 characters.
Hope this helps someone else.