Bug description
During install alongside existing Windows 11 on the same drive, the guided partitioning step launches cfdisk. I selected the existing Windows C: partition and used [ Resize ] to shrink it from 237.5G to 202.5G, then wrote.
cfdisk only rewrites the GPT entry — the NTFS filesystem inside still reported its original size. On next boot into Windows:
STOP CODE: UNMOUNTABLE_BOOT_VOLUME
Windows validates that the boot sector's declared volume size matches the partition and refuses to mount otherwise.
Evidence
From /var/log/omarchy-install.log: cfdisk session showing /dev/sdb3 resized 498059264 → 424673280 sectors ("Partition 3 resized"), followed by table write. No ntfsresize was ever run.
Expected behavior
Either
- warn/block when resizing a partition containing an in-use NTFS filesystem, pointing users to shrink from Windows Disk Management first, or
- run
ntfsresize after the cfdisk resize when the target filesystem is NTFS (ntfsprogs available), or
- document this prominently in the dual-boot install docs.
Notes
Recoverable after the fact (patch NTFS boot sector size field to match the partition + ntfsfix + chkdsk), but data extents beyond the new boundary are already lost — this trap can cause silent data loss for dual-booters.
Omarchy version: 4.0.0. Full install logs available on request.
Bug description
During install alongside existing Windows 11 on the same drive, the guided partitioning step launches
cfdisk. I selected the existing Windows C: partition and used[ Resize ]to shrink it from 237.5G to 202.5G, then wrote.cfdiskonly rewrites the GPT entry — the NTFS filesystem inside still reported its original size. On next boot into Windows:Windows validates that the boot sector's declared volume size matches the partition and refuses to mount otherwise.
Evidence
From
/var/log/omarchy-install.log: cfdisk session showing/dev/sdb3resized 498059264 → 424673280 sectors ("Partition 3 resized"), followed by table write. Nontfsresizewas ever run.Expected behavior
Either
ntfsresizeafter the cfdisk resize when the target filesystem is NTFS (ntfsprogs available), orNotes
Recoverable after the fact (patch NTFS boot sector size field to match the partition + ntfsfix + chkdsk), but data extents beyond the new boundary are already lost — this trap can cause silent data loss for dual-booters.
Omarchy version: 4.0.0. Full install logs available on request.