@Quazz Yep, I’ve checked both of those and they seem fine to me. Not having enough memory does sound like the correct answer.
It’s not too important to have this feature - it’s just a nice thing to have so we can run repairs via the iso if and when the time comes, rather than having to find a disc and then take it to the system physically.

@george1421 I’ve tried following the guide, and I became stuck on the “copy “C:\Program Files\Windows AIK\Tools\PETools\amd64\winpe.wim” C:\winpe_amd64\ISO\Sources\Boot.wim” section.

Because it’s Windows 10 ADK, I believe winpe.wim is buried in:
“C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us”.

However, I received an error saying the system can’t find the path specified for the second part of the command. I’ve taken a look and there is no ISO folder. It’s now buried in:

“C:\winPE_amd64\media\sources\boot.wim”

I assume it’s correct to overwrite this file?

@Quazz I thought that - I wasn’t too sure what parted: was but assumed it was something to do with Parted Magic. I removed it to test, but I still ran into the same issue.
I’ll definitely give George’s guide a go and see if I can get it to work. Thanks for the help, guys. If I run into issues with that, I’ll post back here.

HI all,

I’m currently having issues booting to different ISOs. This is a follow-on from this thread:
https://forums.fogproject.org/topic/7703/parted-magic-boot-menu/11

I’ve added a new entry in my FOG iPXE Menu called Win10Pro64ISO and have written the following:

parted:
initrd ${boot-url}/win10pro/Win10Pro64.ISO
chain memdisk ||
echo failed to boot
prompt
goto MENU

This is almost exactly the same as the Parted Magic ISO I have working, although that is set to a different folder. (${boot-url}/pmagic/pmagic.iso)

When trying to boot from the Windows 10 Pro 64-bit ISO, however, I receive the following error:

The link provided simply tells me that the content length is mismatched, but doesn’t provide any information about how to fix it.
I’m currently running a Ubuntu 14.04 server, running FOG version 5949.
Any help with this would be greatly appreciated.

@Wayne-Workman Hmm, that’s interesting… although I’m certain my hard disks aren’t set to dyanmically expand/shrink.
I worked around this by using a physical hard drive.

@Quazz Unfortunately I can’t run chkdsk /f after the upload attempt - it seems to really screw up the VHD to the extent that it is no longer bootable. I’m going to try from a real hard drive and see if that makes any difference.

The last message I received with a brand new VM and VHD was:

@Tom-Elliott After trying to upload this on a new VHD, I get the following error:

@Tom-Elliott Ubuntu 14.04

@Sebastian-Roth I created a new virtual machine with a copy of the VHD that was faulty and now it’s back to ‘resizing file system’ for over an hour and a half.
I’m currently running a chkdsk /b on the original version of the VHD in the hopes that will fix it. I’ll try the upload again afterwards, otherwise it looks like I’ll have to rebuild the image.

@Quazz Yes, quite a few times. This issue only just started happening within the past few days.
I’ll try creating a new VM with a copy of the VHD it’s using to see if I can upload it then.

@Quazz Yes - with 40GB free on it.

Hi all,

I currently have a problem where I can’t upload an image from a Hyper-V VM. When trying to do so, it hangs on ‘Resizing Filesystem’ for over an hour, and then comes back saying it could not mount /dev/sda2. I’ve run chkdsk /f multiple times and restarted multiple times, but still run into this error. It was working before, so I’m wondering if the VHD has gone wrong? Would cloning everything to a new VHD make it work?

I just updated FOG to cover that base (currently running version 1.3.0-RC-8 (SVN revision: 5949), and now I’m getting ‘attempting to check-in… failed’. I’ve attached screenshots of all the errors.

Any help with this would be appreciated as this is happening with our most used image and the upload attempt has actually wiped the image from the FOG server (so this is the only copy…).

@RobTitian16 Just seems to have been a slow network day I guess as it’s running through fine now at 3GB/min

@Wayne-Workman I’ve checked all of those things… I’ll see how it goes when I upload the next image tomorrow morning.

The VM is type 1.

@Wayne-Workman Apologies - I wrote the above in haste.

FOG version is 8169.
OS - Ubuntu 14.04
Image OS I’m attempting to upload - Windows 10.
Attempted a reboot to no avail. I also tried deleting the host and re-adding it to FOG to no success. The only thing I didn’t do was delete the image and re-add it, but I shouldn’t need to, should I?
I noticed that the upload in progress repeatedly seemed to lose connection, at which point the rate would decrease. When it picked it up again, it would be much lower than when it started out. For example, it started at 3GB/min, but then decreased to 2, and then 1, and finally 600mb/min. Sometimes the rate went up slightly - say from 1 to 1.1GB/min, or 630 to 650mb/min and would then seem to resume the upload at that new speed.
I’m going to try a different system later today to see if I can upload it then.

Morning everyone,

I’m currently having an issue (linked to my previous post found here: https://forums.fogproject.org/topic/7804/schema-installer-doesn-t-ask-for-update-can-t-upload-image/9) where I’m trying to upload a Windows 10 image, but the rate of the upload is constantly decreasing. It started out at about 4GB/min but now it’s decreased to 930mb/min. I’ve also noticed my FOG server is a little slow with basic commands (like logging in, listing directories, etc.) I have 50GB free out of 200GB, so I don’t believe it’s the hard drive capacity. It has 1GB of RAM as well (running as a VM on a Windows 2012 R2 host).
Does anyone have any ideas as to what could be causing it? I really need this image to be uploaded as soon as possible.

Thanks!

@Sebastian-Roth Doh… I think I’ve resolved it by turning off fast startup. I’m currently on ‘Resizing File System’, but that always takes a little bit of time. If it doesn’t go through, I’ll post back. Your suggestions lead me to this post, which gave me the answer:

http://askubuntu.com/questions/145902/unable-to-mount-windows-ntfs-filesystem-due-to-hibernation

Many thanks for your help

Is there a place on the wiki that mentions imaging windows 10? If not, it might be helpful for others in the future just so they know.

@Sebastian-Roth Morning gents,

This is what I get:

@Sebastian-Roth

Here’s the picture as requested!

@Tom-Elliott Failed to mount /dev/sda1
I’ll see if I can get a photo of it when it comes up so you can see the full thing.

Thanks for the help! Somehow after increasing the size of my FOG server hard drive, it went through perfectly fine