I have imaged a wide range of dell Poweredge models with Various raid setups. Mostly Perc cards with RAID 5 configs.

To assit in your original post: the issue [B]“Unable to move /images/dev/mac address to /images/name-of-image[/B]” is very common, and you may be able to resolve it here: [URL=‘http://fogproject.org/wiki/index.php/Images_Directory_Permissions’]Link to wiki discussing Image Directory Permissions[/URL]

and Jaymes is correct, you may be required to run a different kernel to accomplish this. However, do not be frightened by the entire build your own kernel thread… You may be able to get by using the “Kitchen Sink” kernel which is readily available for download.
Else, many other users including myself have compiled kernels that you can try.

I would start by providing more information to the community so we can try to make your experience a little bit less time consuming. (machine make and model and other hardware details)

I had the same issue with Lenovo systems… What I did was go into the BIOS and disable UEFI. I selected “Legacy Mode” and it booted up just fine.

Is your fog server on the same network as your workstations to be imaged? I got confused when you responded with the bandwidth of your Internet service. He was asking for your network. The internal network and the devices that run it. Like a router, switch or hub(has nothing to do with the internet service).

Ask your system admin if you have a 10MB network, a 100MB network, a 1GB network or a 10GB network.
That should give us the info to help answer your question.

First off, yes, did you create a user on your device named fog with the password of password of password? (unless you changed your default password in fog or set it on linux)

I was able to replicate this and have successfully got it passed the permission denied error.
This is NOT what I was talking about before. This requires you actually setup a new storage node in FOG web settings.

Step 1: Select “Storage Management” from the top menu in the Fog web interface.
Step 2: Add New storage node.
– See my screenshot
– Be sure to use “/mnt/pools/A/A0/images/” if this is accurate to your device. (On my Iomega share I have /images setup-- change the name to reflect your share.)

[ATTACH=full]269[/ATTACH]
NOTICE: I set this to my default storage node / is Master node. (because my server is just a virtual appliance, the storage is external…)

Now, make sure your fog installation can see it… go back to the home page and check your storage size.
(It will be blank until you change to the Storage node you just created.) (for my new storage node, it says “Unable to connect”… but when I select “default member” from the list, I see all my disk space from my Iomega device.)
[ATTACH=full]270[/ATTACH]
Finally, as you can see, In Image Management, I have it set to store images in the Default Storage group.
[ATTACH=full]271[/ATTACH]
This method should work for you, it worked for me twice… I set it up and it worked, then I re-installed fog and re-did it just to make sure.

[url="/_imported_xf_attachments/0/269_storagenode.PNG?:"]storagenode.PNG[/url][url="/_imported_xf_attachments/0/270_diskspace.PNG?:"]diskspace.PNG[/url][url="/_imported_xf_attachments/0/271_imagemanage.PNG?:"]imagemanage.PNG[/url]

looks like your /images is mounted as user = root with group = root.
run this command.
sudo chown fog /images (that will Change Owner to fog for /images.)

As for your TFTP: I was more interested to see the contents of one of your files.

do: cd /tftpboot/pxelinux.cfg/

inside this directory is where your workstation looks for the PXE file to boot.

when you set a task to run in fog, a file is output to this directory (/tftpboot/pxelinux.cfg)
the name of the file IS THE MAC ADDRESS of the host to be imaged. (ex. 01-00-24-e8-fa-e9)

I want to see what is inside of that file… that is where all of the connection information is at.

Please paste the contents of this file.

Finally, do not hesitate to ask for assistance if you need help with anything mentioned above.

make sure your newly mounted /images has user= fog group = root permissions

just run the ls -al command in the root / to check this.
Also, go into the /tftpboot directory and paste the contents of one of the command files here so I can see exactly what’s going on.
in order to see a command file, you must have an active task. the command file will have the name of the MAC address of the machine that the task is created for.

also, 10.200.44.2 = that is your fog-server correct? or is that the storage’s IP address?

I will check my setup for any additional details that could help resolve this for you…

is there a .mntcheck file in the /images and /images/dev locations?
if not, create a file named .mntcheck in each of those locations.

alright, here is the quick and dirty: (I can make a step by step if need be)
my fstab looks like this:
172.16.0.34:/mnt/pools/A/A0/images/imagesnfsuser,bg,noexec00

Explanation:
172.16.0.34= IP of Iomega storage node
/mnt/pools/A/A0/images = the actual location on the device (although it looks like its is just /images its not)
/images = location on fog server that the iomega storcenter is mounted to. so, when I ls in /images I see everything on my storage device (iomega)

nfs= the filesystem
user= allow users to mount the filesystem
bg= retry mounting in background
noexec= do not allow execution of binaries in this directory (optional, but if its only storage, its a good idea)
0= read size zero is default
0= write size, zero is default

My exports looks like this:
/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)

More detail on why its done this way:
See, its not exactly an external storage node. This is just allowing the system to access the remote storage device. FOG doesnt care where it sends the images, just as long as there is a place to put them.

My Fog-Machine is running Ubuntu 10.10 on a Dell Poweredge 1650 4GB RAM. (also have VM image in case this physical server dies.)
The storage node is an Iomega 14TB StorCenter px6-300d.

It works quite well for our environment, where we only need images 1-2 times a year because nothing really changes as far as configuration. (We image everything from workstations to AGFA printers the size of a VW bus.)

In short: Yes, you can do this for creating the image, but no its not exactly as you have imagined.
and No, you can not use this method to deploy images to a host.
Details: There is an option from the PXE menu that will allow you to do a quick image. But, that is relying on you to have previously created an image and a host.

If you are intimidated by the web UI, don’t be. It may take a short while to familiarize yourself with the options, but once you understand how to A: create an image and B: Create a host; it is really the best way.

Personally, I do not auto register my hosts… I manually enter the hostname and image type in the WebUI, then set the task to do all of the rest. Then, once I reboot the host, the imaging begins automatically.

Everyone here is here to help, so do not hesitate to ask for assistance.
(and check out some video tutorials)