Unable to upload image from VMware Win7 box
-
Can you tell what happens before the error and the reboot? I’m tracking down chmod calls in FOG, but there are several different times it’s called when doing a windows 7 image upload for single partition resizable.
-
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.
-
Are your other Windows 7 images also of type Single Partition - Resizable? It appears that FOG executes the same chmod command for all Windows 7 Single Partition Resizable images, regardless of the number of partitions (1 or 2). Maybe there is something keeping this image from uploading correctly and the chmod failure is just a false clue.
Try changing the type to Multiple Parition - Single Disk. It will still compress the image, you just have to restore to an HD of the same size or larger, and since VMWare default disk size is like 60GB, you shouldn’t have an issue with that.
-
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?
-
I don’t know if it’s the true cause of your issue since your other Windows 7, Single Partition - Resizable seem to work right? But in the init.gz, in the /bin/fog script, there is a line that seems to double up on the path, so you get /images//images/[mac-address].
More than likely this isn’t what’s killing your upload, since the code would execute for all Windows 7, Single Partition - Resizable images.
You might try chkdsk with the full repair/fix options to see if there is something wrong with the filesystem. Other than that, just use the multiple-partition, single disk image type for Windows 7. It’s a simpler code path and less prone to issues.
-
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?
-
Search wiki for help modifying init.gz file.
-
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.
-
Uploading to my old images works, which leads me to wonder where the information for each image is kept (other than the image itself)?
-
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.