Le 25/01/2013 11:55, Alexander Graf a écrit :
Am 25.01.2013 um 11:51 schrieb Guillaume Gardet
: Hi,
JeOS-raspberry needs a FAT32 partition to boot but kiwi fails to mount it.
See error log:
[ 2776s] Jan-25 09:50:21 <1> : Creating DOS [Fat32] filesystem [ 2776s] Jan-25 09:50:21 <1> : EXEC [mkdosfs -F 32 -n 'BOOT' /dev/mapper/loop0p1 2>&1] [ 2777s] Jan-25 09:50:21 <1> : Copying boot image to disk [ 2777s] Jan-25 09:50:21 <1> : EXEC [blkid /dev/mapper/loop0p1 2>&1] [ 2777s] Jan-25 09:50:22 <1> : EXEC [pvs --noheadings -o vg_name /dev/mapper/loop0p1 2>/dev/null] [ 2777s] Jan-25 09:50:22 <1> : EXEC [blkid -o value -s TYPE /dev/mapper/loop0p1] [ 2778s] Jan-25 09:50:22 <1> : EXEC [dd if=/dev/mapper/loop0p1 bs=128k count=1 2>/dev/null | grep -qi CLIC] [ 2778s] Jan-25 09:50:23 <1> : EXEC [mount /dev/mapper/loop0p1 /tmp/kiwiloop.EchGLg 2>&1] [ 2778s] Jan-25 09:50:23 <3> : Failed to mount /dev/mapper/loop0p1 to: /tmp/kiwiloop.EchGLg: mount: unknown filesystem type 'vfat' [ 2778s] Jan-25 09:50:23 <1> : EXEC [sync] [ 2779s] Jan-25 09:50:23 <3> : Couldn't mount image boot device: /dev/mapper/loop0p1
Full log is here: https://build.opensuse.org/package/live_build_log?arch=armv5el&package=JeOS-raspberrypi&project=openSUSE%3AFactory%3AARM%3AContrib%3ARaspberryPi&repository=images
Any idea why mount does not know vfat? Is it an OBS error or a kiwi one? It means that the obs guest kernel couldn't find the vfat module. It would have to get included into the helper initrd on the obs worker nodes.
Ok. How to fix it then? Guillaume
Alex
Regards,
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org