Hi Oli, Bug fired with suggestions and my workaround. <a href="https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-core/+bug/1563737">https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-core/+bug/1563737</a> Cheers, Jian <div class="gmail_quote">On Mar 29, 2016 17:16, "Oliver Grawert" <<a href="mailto:ogra@ubuntu.com">ogra@ubuntu.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi, Am Dienstag, den 29.03.2016, 16:17 +0200 schrieb Jian LUO: > Hi Sergio, > > Have you got time to look at the problem? > > Further more, the ubuntu-core-generic-initrd can't detect U-Boot on > x86 thus doesn't generate the correct fstab entry accordingly. I can > workaround the two issues with manually partitioning the SD image and > patch scripts/ubuntu-core-rootfs in my kernel snap. It would be great > however if Ubuntu core supports it officially. > there are sadly more issues than the one with the initrd [1], but it would be nice if you could file a bug against the initramfs-tools-ubuntu-core package where this binary comes from (this is also not limited to the generic initrd but will affect all initrds) there are also further issues with the "snappy list" command that has certain expectations about where a bootloader should mount stuff in /boot, i fear just hacking the initrd script wont help here. it would be good to get these issues fixed for the 16.04 snappy release :) ciao oli [1] <a href="https://bugs.launchpad.net/snappy/+bug/1563358" rel="noreferrer" target="_blank">https://bugs.launchpad.net/snappy/+bug/1563358</a> -- snappy-devel mailing list <a href="mailto:snappy-devel@lists.ubuntu.com">snappy-devel@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snappy-devel" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snappy-devel</a> </blockquote></div>