Attempting to pull my first image onto a newly install Fog. Machine has 1 HDD in it with multiple partitions including Windows 7 32/64, Windows 8.1 32/64, and 10 32/64. The image definition is as pictured in the zip along with the error received. I’ve tried setting it to Windows 10 and Windows 8.1 with the same result. What am I missing?

0_1465480503054_Error.zip

@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.

https://dl.orangedox.com/YBrRpPXIzPFUWJd9W5

@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

@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

I have tried clearing cache, doing a reload, a CTRL reload, new incognito window and have not regained sorting. If anyone else is reading this post can you please give it a try and report back. Maybe my setup has something goobered up.

1. Log into fog server
2. click Report Management
3. Click Imaging log
4. Set a valid Start and end date
5. Click Search
6. Click the column header to sort results.

I’m not sure what you mean by refreshing the page but I have been unsuccessful in any sorting on the reports after the upgrade. see the attached video

http://screencast.com/t/8Wsr1jqojc

Updated to RC2, I am not able to sort anything in the Imaging log. Tested with Firefox and Chrome

Clicking on the start and end time in Report management will place the information in ascending order, clicking the sort again does not place it in descending order. Every other field in this view switches it’s sort method each time it is clicked!

@Wayne-Workman Thanks for the link. My mistake, great support on this forum

This is a nonissue. Once the passwords were adjusted to match everything worked as I expected it to. Now that I understand how it works I’m less confused as to why it broke. However, when setting up this headless server for use specifically for a fog server I created a user “fog” and used my own password. When my password was not working after the fog server install, I logged in as root to change the password back to what I wanted and specified while installing Ubuntu. This is where the disconnect was. Maybe it is documented to not make your default user on the server “fog” or to not change the password after the fact, but I obviously missed that. Thanks for instructing me on the fix and helping me understand why it broke I won’t make the same mistake next time

@Wayne-Workman What I meant was, once the password was corrected where it needed to be would the partitions be moved to their proper location and complete the imaging process the way Fog expects it to. Or will I need to correct all the password locations, delete the task and resulting img files, and start over with a capture?

@Wayne-Workman Thanks Wayne. I did indeed change my “fog” users password manually with the root user. All I should have to do is modify the password in the Storage management option on the web? Once I fix this password issue, will the task complete or is it stuck forever?

The capture task appears to have completed as the computer rebooted. The Task management on the web shows the task as still active though nothing is happening. Checking the image information it shows the Client Image to be 150gb, but the uploaded size is No Data. /Images folder contains /dev and /postdownloadscripts. /dev has all my partition images inside. I recall reading about this but don’t recall what the issue is. 0_1465494627223_Logs.zip

@Tom-Elliott looks like whatever you did worked thanks for the quick turn around! Thread can be marked solved.