Fdisk & parted are reporting two different sda1 definitions:
1-FAT32 vs. FAT16
2-start @1MB vs. start @2MB
Other than starting over, I have no suggestion how best to fix it. If starting over, I would create a new GPT table. Booting is commonly more reliable using GPT.
FWIW, a 100M sda1 is typically an ESP partition definition created by Windows on a GPT disk. Was Windows ever installed on this microSD card? The Debian installer creating a new one on an empty disk wouldn't be making one that size I don't think (something else was always installed first here, so no direct experience for the context). Most Linux installers default to a much larger size for an ESP, but will keep 100M undisturbed for multiboot usage.
1-FAT32 vs. FAT16
2-start @1MB vs. start @2MB
Other than starting over, I have no suggestion how best to fix it. If starting over, I would create a new GPT table. Booting is commonly more reliable using GPT.
FWIW, a 100M sda1 is typically an ESP partition definition created by Windows on a GPT disk. Was Windows ever installed on this microSD card? The Debian installer creating a new one on an empty disk wouldn't be making one that size I don't think (something else was always installed first here, so no direct experience for the context). Most Linux installers default to a much larger size for an ESP, but will keep 100M undisturbed for multiboot usage.
Statistics: Posted by mrmazda — 2024-01-21 04:38 — Replies 1 — Views 32