So after I uploaded one of my existing images successfully, I made a new image and uploaded the contents of the VM to it.
Now it works. One thing I noticed is FOG can see two partitions rather than just one which is all it was seeing before. I’m not sure FOG can only see one partition on the disk I was using previously. I didn’t do anything different to prep it this time.
Uploading to my old images works, which leads me to wonder where the information for each image is kept (other than the image itself)?
I checked the fog script. Everything looks good to me.
I’m going to try imaging the VM using one of the images I already have, and then writing the image back to FOG and see what happens.
Maybe I’m just being a n00b, but there are no subdirectories in my ./bin/. Is that where I should be looking for this script?
Thanks so much for your help, chad!
Ok, so it does work when the image is set to Multiple Partition - Single Disk. I tried changing it back to Single Partition - Resizable and the error comes back.
Is there a config file that needs to be edited somewhere?
Sysprep is working fine. I made another image and this time around it worked. Not sure what changed.
Now I’m trying to make a new base image and FOG will not allow me to upload it, but that’s another thread…
Before the error everything looks normal. The resize test runs successfully, the partition is resized, the disks are allowed to settle, and then the blue screen comes up with the “Please wait” message. That sticks around for 3-4 seconds and right underneath the error appears and it all quickly scrolls off the screen.
Then, FOG continues as though there was no error. The MBR is restored, disks are settled again, partition size restored, and then the system begins the reboot process.
Here you are:
[code]
DEFAULT send
LABEL send
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= type=up img=Win764BitStandardV2 imgid=11 mac=00:0c:29:8e:f7:2a storage=10.10.15.13:/images/dev/ web=10.10.15.13/fog/ ignorepg=1 osid=5 pct=5 imgType=n shutdown= loglevel=4 consoleblank=0 fdrive= chkdsk=0
[/code]
I checked, and it is set to “Win764BitStandardV2”, just like the other working images (the other images have different names of course).
The name of the image is entirely different from what the error states. The file name it’s looking for appears to be the MAC address of the VM, where the image file name I have it set to in the FOG GUI is “Win764BitStandardV2”.
Using some screen capture software I managed to see the error. It says “chmod: cannot access ‘/images//images/000c298cf72a’: No such file or directory”
Any idea on where that comes from?
I’ve built a brand new Win7 x64 box in VMware to use as my new base image. I have the HDD type set to IDE in VMware Workstation, and have Win7 prepped and ready to go.
The problem is when I go to upload the image, I get to the blue “Please wait” screen, and then it scrolls up with what looks like an error below (scrolls way too fast to read), and then FOG continues to reboot the VM as though the image was completed.
Has anyone else run into this problem before? Maybe there’s a VMware setting I’m missing?
Some new computers were received require AHCI drivers for Windows to boot. Because the image we were previously using did not have any AHCI drivers installed, Windows 7 would BSOD immediately after the “Starting Windows” splash screen was finished, and send the machine into a boot loop.
I tried booting the machine with the HDD controller in IDE mode, which allowed me to get into Windows and I tried all the registry tweaks I know of to get AHCI working after Windows has been installed. Despite this having worked on other systems in the past, it refuses to work at all with these, so I got to work on a new image where these drivers are installed.
So on one of the problem machines I installed a fresh copy of Windows, got all drivers and applications installed, ran Sysprep/FOGprep and uploaded this image to the FOG server. Deployed the image to one of the other machines, and it has the same issue (BSOD on boot).
So that said, is there any way to preload drivers on a system image? This image will only be used on machines with this HDD controller.
