personal_x86.img will not update core

Ted Gould ted at
Mon Oct 19 13:52:05 UTC 2015

On Sat, 2015-10-17 at 10:54 -0400, Dale Beaudoin wrote:
> Please belay my last message. There was some type of font error.
> I am not able to use the snappy update command to update the snappy
> core versions. I and another tester keep getting this error:
> Oct 10 21:20:34 localhost snappy[2627]: main.go:57: DEBUG: [snappy
> update] failed: Failed to run command
> '/bin/cp /writable/cache/assets/vmlinuz-4.2.0-15-generic.efi.signed /boot/grub/b': /bin/cp: error writing ‘/boot/grub/b/vmlinuz-4.2.0-15-generic.efi.signed’: No space left on device#012/bin/cp: failed to extend ‘/boot/grub/b/vmlinuz-4.2.0-15-generic.efi.signed’: No space left on device#012 (exit status 1)
> Does anyone know  why this is happening. I am testing snappy_personal
> images which are restored on both USB and HDDs .

I'm not sure that anyone is looking at the personal image right now.
It's not currently based on the same core, so it probably needs
additional tweaking.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the snappy-devel mailing list