Posts made by wdmartin

Well, it imaged, but the OS fails to boot. It may not like having been put on a VirtualBox when it was originally built against an Optiplex 990.

I got the 58 GB figure from the FOG imaging screen while it was building the second partition. The resulting VDI file is 58 GB, so I think that’s probably accurate.

At this point, the FOG part of it is working – it successfully deploys the image across the network to VirtualBox. It’s not FOG’s fault that the image doesn’t work on VirtualBox’s emulated hardware. I may give up and just do a manual install – I only need one VirtualBox installation. Perhaps I’ll pull an image from it for future use once I’ve got it built.

Thanks for the assistance! I greatly appreciate it when projects have helpful communities.

Yeah. Would that make a difference?

I gave the virtual disk 200 GB, and it failed.

Not to be deterred, I gave it 400 GB – and it appears to be working!

It seems a tad peculiar that it failed with 200 GB available considering that the original partition is apparently 58 GB. Surely the remaining 142 GB should have been ample? But apparently it really needs lots of breathing room.

@Wayne-Workman The version is 1.2.0.

@Sebastian-Roth I looked, and there is no d1.partitions file as far as I can see. The image is stored in /images/Win7GeneralStaffSysprep, which contains the following:

wdmartin@FOG:/images/Win7GeneralStaffSysprep$ ls -hal
total 28G
drwxrwxrwx  2 root root 4.0K May 12  2015 .
drwxrwxrwx 32 fog  root 4.0K Feb  9 09:58 ..
-rwxrwxrwx  1 root root 8.5M May 12  2015 rec.img.000
-rwxrwxrwx  1 root root  28G May 12  2015 sys.img.000

I tried making a fresh VirtualBox with 30 GB of allocated space. Unfortunately, it displayed the exact same behavior: grabbed a tiny 100MB image, then rebooted and found no OS.

Hi! I’ve run into an odd situation that I don’t know how to address.

I’m attempting to deploy an image from our FOG server onto a VirtualBox instance. When I try, it goes like this:

1. VirtualBox successfully boots from FOG;
2. VirtualBox successfully registers as a host with FOG;
3. I use the console to set up a deploy task for the new host, and reboot VirtualBox;
4. It appears to pull an image, but it’s much, MUCH faster than expected, and the image is only 100 MB instead of 2 GB.
5. It reboots, and fails to load Windows.

The image screens go by too fast to read, but I used VirtualBox’s video capture to record this happening and stepped through frame by frame. Here are some screen captures of what seem like key moments:

Apologies for the blurry text, the video had some pretty aggressive compression. Is that broken pipe and the following “aborted” message on the second screen normal?

I’m a longtime Linux user, but a comparative FOG newbie, having inherited this system from a coworker who left for greener pastures a few weeks ago. I don’t know what’s going on, or why it’s apparently sending only 100 MB instead of the 2 GB I was expecting. any suggestions welcome.

Thanks.