Apologies. Turns out my rootfs did not have enough remaining space.
After deleting previous images, both snap and deb worked.
Cheers,
kyleN
On 02/17/2017 04:05 AM, Lukasz Zemczak wrote:
Hello Kyle!
I was unable to reproduce the issue with the .deb 0.15 xenial
ubuntu-image using the standard pc-amd64-model.assertion for building
the image (+ the additional size constraint). Is your model using any
different partition scheme? As per Steve's request, we'd need to get
all the possible details since we did change the way we partition the
image. Could you also check and see if the issue is reproducible in
the deb-based ubuntu-image that's in xenial-proposed?
Cheers,
On 17 February 2017 at 01:05, Steve Langasek
<steve.langa...@canonical.com> wrote:
On Thu, Feb 16, 2017 at 06:20:12PM -0500, Barry Warsaw wrote:
On Feb 16, 2017, at 06:01 PM, knitzsche wrote:
$ sudo kpartx -a test-learnit.img
[sudo] password for knitzsche:
$ findfs LABEL=writable
/dev/mapper/loop4p2
$ sudo mount /dev/mapper/loop4p2 mnt
Killed
How very weird. What is mount actually barfing on there? Anyway, I'll try to
fire up a Xenial VM tomorrow and see if I can reproduce it.
Since this relates to trying to mount a filesystem, it's possible the
problem won't be reproducible unless you're building a filesystem with the
exact same contents (file sizes, etc). Kyle, would it be possible for you
to post your image somewhere for examination?
Also, please paste the output of 'dmesg' - this is likely a kernel-level
crash.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
--
Devices mailing list
Devices@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.snapcraft.io/mailman/listinfo/devices
--
Devices mailing list
Devices@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.snapcraft.io/mailman/listinfo/devices
