Hi Marcus, I am trying to build an armv5 image for Raspberry Pi with a FAT32 boot partition but the partition flag is wrong. It is 83 (Linux) instead of 0C (FAT32 LBA). Any idea why? Moreover, in OBS JeOS image build, FAT32 partition cannot be mounted. Error log: ******************************************************************************** [ 2030s] Nov-19 10:54:35 <1> : EXEC [mkdosfs -F 32 -n 'BOOT' /dev/mapper/loop0p1 2>&1] [ 2030s] Nov-19 10:54:35 <1> : Copying boot image to disk [ 2030s] Nov-19 10:54:35 <1> : EXEC [blkid /dev/mapper/loop0p1 2>&1] [ 2030s] Nov-19 10:54:35 <1> : EXEC [pvs --noheadings -o vg_name /dev/mapper/loop0p1 2>/dev/null] [ 2031s] Nov-19 10:54:36 <1> : EXEC [blkid -o value -s TYPE /dev/mapper/loop0p1] [ 2031s] Nov-19 10:54:36 <1> : EXEC [dd if=/dev/mapper/loop0p1 bs=128k count=1 2>/dev/null | grep -qi CLIC] [ 2031s] Nov-19 10:54:36 <1> : EXEC [mount /dev/mapper/loop0p1 /tmp/kiwiloop.awflR6 2>&1] [ 2031s] [ 2002.933444] FAT-fs (dm-0): codepage cp437 not found [ 2033s] Nov-19 10:54:38 <3> : Failed to mount /dev/mapper/loop0p1 to: /tmp/kiwiloop.awflR6: mount: wrong fs type, bad option, bad superblock on /dev/mapper/loop0p1, [ 2033s] missing codepage or helper program, or other error [ 2033s] In some cases useful info is found in syslog - try [ 2033s] dmesg | tail or so [ 2033s] Nov-19 10:54:38 <1> : EXEC [sync] [ 2033s] Nov-19 10:54:38 <3> : Couldn't mount image boot device: /dev/mapper/loop0p1 ******************************************************************************** Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org