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

Am Freitag, 25. Januar 2013, 12:01:18 schrieb Alexander Graf:

On 25.01.2013, at 11:57, Guillaume Gardet wrote:

...

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?

Ask Adrian to put the vfat module into all /etc/sysconfig/kernel files and rebuild the initrd on all worker nodes :)

Hm, I added them for future deployment for KVM workers now. A workaround for is to require XEN workers, they have it already. Do this by adding a _constraints file beside the kiwi file containing: <constraints> <sandbox>xen</sandbox> </constraints> -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 25/01/2013 13:08, Adrian Schröter a écrit :

Am Freitag, 25. Januar 2013, 12:01:18 schrieb Alexander Graf:

...

On 25.01.2013, at 11:57, Guillaume Gardet wrote:

...

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? Ask Adrian to put the vfat module into all /etc/sysconfig/kernel files and rebuild the initrd on all worker nodes :) Hm, I added them for future deployment for KVM workers now.

A workaround for is to require XEN workers, they have it already. Do this by adding a _constraints file beside the kiwi file containing:

<constraints> <sandbox>xen</sandbox> </constraints>

Hmm, does not seems to work. Error log: [ 4441s] Jan-25 13:45:32 <1> : Creating DOS [Fat32] filesystem [ 4441s] Jan-25 13:45:32 <1> : EXEC [mkdosfs -F 32 -n 'BOOT' /dev/mapper/loop0p1 2>&1] [ 4441s] Jan-25 13:45:32 <1> : Copying boot image to disk [ 4441s] Jan-25 13:45:32 <1> : EXEC [blkid /dev/mapper/loop0p1 2>&1] [ 4442s] Jan-25 13:45:33 <1> : EXEC [pvs --noheadings -o vg_name /dev/mapper/loop0p1 2>/dev/null] [ 4442s] Jan-25 13:45:33 <1> : EXEC [blkid -o value -s TYPE /dev/mapper/loop0p1] [ 4442s] Jan-25 13:45:34 <1> : EXEC [dd if=/dev/mapper/loop0p1 bs=128k count=1 2>/dev/null | grep -qi CLIC] [ 4443s] Jan-25 13:45:34 <1> : EXEC [mount /dev/mapper/loop0p1 /tmp/kiwiloop.N5WqyT 2>&1] [ 4443s] [ 4388.845378] FAT-fs (dm-0): codepage cp437 not found [ 4443s] Jan-25 13:45:34 <3> : Failed to mount /dev/mapper/loop0p1 to: /tmp/kiwiloop.N5WqyT: mount: wrong fs type, bad option, bad superblock on /dev/mapper/loop0p1, [ 4443s] missing codepage or helper program, or other error [ 4443s] In some cases useful info is found in syslog - try [ 4443s] dmesg | tail or so [ 4443s] Jan-25 13:45:34 <1> : EXEC [sync] [ 4444s] Jan-25 13:45:35 <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

Le 25/01/2013 15:12, Adrian Schröter a écrit :

Am Freitag, 25. Januar 2013, 14:56:00 schrieb Guillaume Gardet:

...

Le 25/01/2013 13:08, Adrian Schröter a écrit :

...

Am Freitag, 25. Januar 2013, 12:01:18 schrieb Alexander Graf:

...

On 25.01.2013, at 11:57, Guillaume Gardet wrote:

...

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? Ask Adrian to put the vfat module into all /etc/sysconfig/kernel files and rebuild the initrd on all worker nodes :) Hm, I added them for future deployment for KVM workers now.

A workaround for is to require XEN workers, they have it already. Do this by adding a _constraints file beside the kiwi file containing:

<constraints> <sandbox>xen</sandbox> </constraints>

Hmm, does not seems to work. Hm, it seems it needs also nls_cp437 kernel module :/

So, xen hosts are not okay either. You can remove the _constraints file again.

Either I will add also this module to all hosts or you can avoid to use fat fs. I will wait for the end of the other thread :)

FAT is mandatory. ;) So question is: should we use it for u-boot or for kernel images? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org