@Wayne-Workman The 1tb drive is internal and also used to run the OS.
fog@FogServer:~$ sudo file -sL /dev/sda1
/dev/sda1: Linux rev 1.0 ext4 filesystem data, UUID=546a8cba-febc-48e5-87da-a4c6ea712a5e (needs journal recovery) (extents) (large files) (huge files)
permission on /images
fog@FogServer:~$ ls -ld /images
drwxrwxrwx 5 root root 4096 Dec 14 11:11 /images
Anything I missed?
@TOM ELLIOTT ask and you shall receive 
@Arrowhead-IT
fog@FogServer:~$ cat /etc/exports
/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
My HD info looks accurate in the gui, see the screen shot below. I looked into the user/password of the storage management section and it looks to be correct. I have also tried rebooting the machine and restarting apache with no success unfortunately. This is not a show stopping issue by any means but the tinkerer in me is annoyed 
@ch3i Thanks for the quick reply. here is the output
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 909G 48G 815G 6% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 3.9G 4.0K 3.9G 1% /dev
tmpfs 800M 676K 799M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 4.0G 0 4.0G 0% /run/shm
none 100M 0 100M 0% /run/user
@ch3i The TB drive also houses the Ubuntu Server OS. I’m not really sure how to answer your question unless my response does
Is there a way to force a refresh of this information? Would log files help in troubleshooting?
EDIT: I tried disabling the graph in Storage Management > Edit and it screws up the home page badly
@Wayne-Workman I’m almost positive that when I used the deploy option, BEFORE he fixed the order issue, it would restore SDA1, SDA10, SDA2… and the machines would boot up correctly and function fine. The only time that I saw the issue was when the Multicast was used, again restoring them out of order. That was the puzzling part, why would they both restore out of order but it was only an issue with the Multicast restore process and not the deploy. Either way it looks like it’s running swell now
@Tom-Elliott The 2 machines restored using multicast without issue using GIT Trunk 5698. I did notice the partitions restored in order, putting the 10th partition last. Is this how a normal deploy functions currently? I could have sworn the deploy option would send the partitions sda1, sda10, sda2…
Either way I really appreciate the fast turn around with the issue I was experiencing. Expect more questions and bug reports as we continue to use this great imaging solution. We are a qa team working for a software company using it to image our test machines.
@Tom-Elliott I can certainly update. I am new to this and plan on using GIT. Is there anything special I need to do to update? Last commit looks to be from yesterday which tell me your code is not there quite yet.
Edit: nevermind, I was looking at the wrong location Updating in a few
@Tom-Elliott You can find my log files at the link below. I just ran another multicast this morning and ended up with the same results.
@Wayne-Workman Sure.
The multicast does not begin till both machines are ready to receive. The machines progress at the same rate, switching to restoring a new partition until finished. Each machine renames the computer at the end of the restore process and reboots. (appears to fail for Windows 10 32/64 upon further inspection)
The computers show the normal pre OS boot screens and then the multiboot Windows selection screen is shown. Selecting Windows 10 for instance, which is second on the list but default choice, actually loads up Windows 7 which appears first on the list. Windows 7 attempts to load the desktop but hangs. Task manager shows a bunch of instances of winmail.exe. I was concerned it was a virus somehow stuck in there
Restoring both machines at the same time with the deploy option completes successfully and is bootable.
@Wayne-Workman I’m using the web ui to set up a multicast to my group of computers (2). Everything appears to work correctly until the machine reboots and an OS is selected. Another interesting thing I noticed is when the images are sent back to the machine they are send in alphabetical instead of numeric. In my case I have partitions up to sda10. The restore order goes sda1, sda10, sda2,sda3… Not sure if that matters, just thought I’d mention it.
Good afternoon. As the title states I am using Trunk 5676 on a clean install Ubuntu 14.04 server. The master image consists of multiple partitions on 2 primary and and extended partition. MBR on Part 1 Primary, Win 7 32 on Part 2 Primary, Extended Partition has 7 64, 8.1 32, 8.1 64, 10 32, 10 64, 7 Enterprise 64.
I am able to pull an image and deploy it back to multiple computers successfully. However, when deploying via multicast I end up with a bad restoration on both computers. For starters my OS selection screen appears to be fine, but selecting Win 10 boots up Win 7 32. Once in the OS it hangs with explorer never launching.
Can anyone give any insight? Is it due to our weird partitions? Is anyone successful in deploying via multicast lately? I appreciate the replies!
I’m running Fog Server on 14.04 LTS Ubuntu server with Trunk 5676. Logging into the web ui shows my Disk Information as 2gb free and 2gb used. My /images folder is located on a 1tb drive with about 900gb available. I was able to create an image from my test machine and the chart never updates. Is this a configuration issue or a potential bug in the ui? Anything else I can provide to help please let me know.
@Sebastian-Roth This was a new install from Trunk. I am still very new to the Fog project and started with a fresh install of 14.04 server and latest Trunk (5676) at the time. The default setting in PXE boot menu was “sanboot”. I switched it to EXIT per LJedi post and it seems to fix the issue.
I am seeing the same issue. I am using Trunk 5676.
Boot.php output available here http://pastebin.com/0ADFrF1v