Creating an image from scratch was the solution to my problem. So further trouble shooting/hacking is not necessary

Thanks for the help!

I was on vacation for two weeks so couldn’t respond earlier.

But I’ve run the cleanmgr and dism command without any luck. So there is nothing left to do then a clean install. I’ll let you know if that works.

@Sebastian-Roth
I’ve run chkdsk, sfc /scannow and several DISM commands but all without succes.

@Quazz The total size in use is around the 18-19GB so that is correct. I also doubt that it’s a bad sector fault because I have tried making an image with several different PC’s.

Right now I’m using an old image to recover and I need to update Windows. If I try to create a new image from the updated Windows I get this error.
But when I recover the old image and directly try to make a new image it goes successful. I find that very strange.
I tried to recover an old image, update windows run chdkdsk several times, SFC and DISM but still I get this error.

I’m going on vacation for two weeks so I can’t respond for this period but if you leave any suggestions I"ll be happy to follow up on my return.
One of the first things I’m going to do is trying to create an image from a fresh Windows install.

Hello all,

I have a similar/same issue as mentioned in this topic: https://forums.fogproject.org/topic/13546/problem-capturing-image-no-space-left-on-device

I have FOG 1.5.7 running on Ubuntu 18.04. The bzImage version I’m using is 4.19.48. When I try to make a new image I’ll get the next error after resizing is done:

Contents of /dev/mac directory:

File: d1.fixed_size_partitions

:1:1

File: d1.original.fstypes

/dev/sda2 ntfs

File: d1.original.swapuuids

File is empty

File: d1.partitions

label: dos
label-id: 0xd74c9d19
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=      204800, type=7, bootable
/dev/sda2 : start=      206848, size=   123916800, type=7
/dev/sda3 : start=   124123648, size=      921600, type=27

Putting images back is no problem, but I can’t create anymore. Running a capture debug gives the next error:

Followed by

Image information in FOG:
Image Type: Single Disk - Resizable
Partition: Everything
Image Manager: Partclone Gzip

I have the same issue on diffrent PC’s. Since this topic is closed because the problem was “solved” for the reporter, what info do you guys need from mee?

My error screen looks the same as the reporter.

I’m on FOG 1.5.5 because I can’t yet upgrade to 1.5.7 due to problems with confilcts between ubuntu, mariadb and fog.

Does somebody have any suggestions for me?

@george1421
Thanks for your reply.

The system is not sysprept and bitlocker is not enabled. But the PC is not even attempting to boot Windows because the BIOS doesn’t see the Windows Boot Manager.
In the BIOS CMS is enabled and set to UEFI and legacy. Network and storage are set to legacy.
I’ve installed installed Windows on the source PC with EUFI and legacy. Both have the same problem.

The hardware is x64 (Intel Celeron N3160). A normal PC, so not an actual IoT device. Storage is on a m2 SSD.
And mine mistake, it’s not Windows 10 IoT, but Windows 10 IoT LTBS. So it is actually Windows 10 Enterprise.

Hello,

I’m having difficulties with deploying a Windows 10 IoT image. I’ve made an image on one PC and tried to deploy it on a different one.

All the partitions and flags are the same, but I don’t get a bootable system on the deployed PC. In the BIOS there is no Windows Boot Manager as a boot option. The only way to fix this is booting Windows PE and execute the following commands:

• bootrec /FixMbr
• bootrec /FixBoot
• bootrec /ScanOs
• bootrec /RebuildBcd

Deploying the same image on the source PC also don’t work (If I delete all the partitions first).

What I’v tried:

• Different image types: Single Disk - Resizable and Multiple Partition Image - Single Disk (Not Resizable)
• Different Operation System: Windows 10 and Windows Other
• Switched between BIOS and UEFI (reinstalled image)
• Tried options Image manager Partclone Gzip and Partimage

I’m using:

• FOG 1.5.4
• Ubuntu 16.04

Yes, I also recreated the DMI assosication.

Also tried different DMI fields etc. But the menu item fog.capone doesn’t show up in the iPXE menu.

Thanks for the quick replies btw

Yes, I first removed Capone, then activated and installed it. In the plugin management it is visible so no problems here.

But the last time I wasn’t very clear I see. When I reinstall Capone it does not show up in the iPXE Menu Configuration menu.
So I can make associations etc. but when I boot up a PC the option Capone is not visible.