<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Partition 3 (NTFS) skipped during deployment]]></title><description><![CDATA[<p dir="auto"><strong>Kernel version:</strong> 6.12.35<br />
<strong>FOG version:</strong> 1.5.10.1798<br />
<strong>Imaging settings</strong>: Operating System (Windows 10), Image Type (Single Disk - Resizable), Partition (Everything), Image Enabled (check), Replicate? (check), Compression (6), Image Manager (Partclone Ztsd)</p>
<p dir="auto">Hey guys,<br />
I’m running into a brick wall with a Windows 11 image. I’m using a GPT/NVMe setup and had a lot of trouble getting the capture to finish, so I ran it in Debug Mode.</p>
<p dir="auto">The capture seemed to work, I watched Partclone hit 100% on nvme0n1p3 (the main Windows partition (237GB)), and I have a 5.6GB d1p3.img.000 file on my server. However, at the very end of the capture, the client froze on the blue Partclone screen - it “freezes” every time I try to capture an image. I couldn’t Ctrl+C or reboot, so I had to hard-reset the master PC and manually move the files from /images/dev/ to the image folder.</p>
<p dir="auto"><strong>The Problem:</strong><br />
When I try to deploy, FOG restores p1 and p2, but then it just skips p3 entirely. It says “Cloned successfully” and starts resetting UUIDs without ever showing the blue Partclone screen for the main partition.</p>
<p dir="auto"><strong>Observation:</strong><br />
I noticed a mismatch in my partition files. My d1.partitions shows the full size, but the minimum and shrunken files show the 16GB size from the resize test.</p>
<pre><code>d1.partitions: /dev/nvme0n1p3 : start=444416, size=498042880
d1.minimum.partitions: /dev/nvme0n1p3 : start=444416, size=33833186
</code></pre>
<p dir="auto">Is the deploy skipping p3 because the capture didn’t “finish” properly and the metadata is inconsistent? How can I fix this problem or find out where it’s coming from?</p>
<p dir="auto">It’s driving me insane that I can’t deploy images even after days of working on it.</p>
<p dir="auto">Thanks in advance!</p>
]]></description><link>http://forums.fogproject.org/topic/18150/partition-3-ntfs-skipped-during-deployment</link><generator>RSS for Node</generator><lastBuildDate>Thu, 09 Apr 2026 23:02:53 GMT</lastBuildDate><atom:link href="http://forums.fogproject.org/topic/18150.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 09 Apr 2026 14:30:14 GMT</pubDate><ttl>60</ttl></channel></rss>