Posts made by sami.blackkite

@mashina

Hey mashina, thanks for the info.
However, all my images are single disk and this image is also set to single disk resizable.

I’ve done some research and found that any unallocated space on the disk seems to flag FOG which then results it in a full disk image, rather than just the occupied space.

Hello Fog team.

I’ve added a policy for snponly.efi with the correct mac address for my machine.
However, my machine does not boot into FOG despite being the only machine in that policy and this specific policy being the only one that’s active.

If I swap back to my netboot policy, the device picks it up instantly.

I’ve tried both snponly.efi + ipxe.efi
and both fail to boot into FOG via PXE.

Secure boot is off on my machine.

Has anyone got any ideas?

Hi everyone.
I’m trying to capture an intel nuc with Ubuntu on it.
But every time I clone an image, it produces an image that’s 230GB.

All I want to do is have an image of the OS build, not the whole disk.
I’ve checked via DEBUG and the error I seem to have upon partclone attempting to shrink the disk is the one in the title.

“Not shrinking (/dev/nvme0n1p1) as it is detected as fixed size”

Has anyone got any advice or solutions to this?

Currently on FOG Version 1.5.10.5

Thank you!

@JJ-Fullmer said in Windows Images - Too large.:

@sami-blackkite Looks like you’re on the dev branch, which is good. Updating is always a good first step in troubleshooting stuff like this in case it’s already fixed.
I’m not seeing anything in the commits (https://github.com/FOGProject/fogproject/commits/dev-branch) that actually looks related since the version you’re on, but sometimes a refresh still helps.

I took a look at the default settings of a new image and it’s close to what I use, only difference is I set compression to 11.

Are you familiar with a debug capture/deploy task? If not, simply check the ‘debug task’ checkbox when queuing up the capture task. It allows you to step through the capture process and you can catch any messages that might be telling us why it’s behaving odd. Just use the command fog once it’s booted up and ready to start the image and you’ll hit enter for each step. You can also set it up to watch it and step through over ssh if you want by, before running the fog command, getting the ip address with ifconfig and then setting a password with passwd then you can ssh into the debug session from your workstation with ssh root@ip.add.re.ss then the password you set. The password will only exist for that session on that machine. SSH just makes screenshotting and or copying any error messages to share here a bit easier.

Oh thank you so much, JJ.
I’ll give those steps a go and report back.

@JJ-Fullmer said in Windows Images - Too large.:

@sami-blackkite That’s the right option.
What version of FOG are you on?

I’m on 1.5.10.5

It says here that the latest one is 1.5.10 and that I’m not on the latest.

https://prnt.sc/SNZxKw_L0WVF

@Tom-Elliott
Hi Tom.
Thanks for the speedy reply.
All 3 windows images that I’ve made are set to

Single Disk - Resizable (1)

Is that the wrong option?

Thanks.

Hey everyone.
FOG has been great the past couple times I’ve used it and in a current new windows build I’m having a couple issues with cloning and image.

My windows build is about 80-90GB and I’ve been using FOG’s default settings to clone the image.
Before, the image would be a 1 to 1 copy, 90gb on my FOG server, however, this time, no matter how many images I take, FOG always picks up the full drive.

My windows disk is 256GB and my build is 80gb [of used space on the disk]
I only want to take the size of the Windows image.

How can I fix this?
I’ll add some screenshots if required. Thank you.