Raspberry Pi 3 Install broken

ros-a · December 12, 2018, 1:44am

Hi,

Just tried to install Raspberry Pi 3 image from here: https://developer.ubuntu.com/core/get-started/raspberry-pi-2-3

I can login to the RPi3. After a few minutes, I get a notice that the system will reboot.

After rebooting:
$snap refresh
error: cannot communicate with server: Post http://localhost/v2/snaps: EOF
$ systemctl status snapd.service
● snapd.service - Snappy daemon
Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2018-12-12 01:34:18 UTC; 2min 1s ago
Main PID: 1250 (snapd)
CGroup: /system.slice/snapd.service
└─1250 /usr/lib/snapd/snapd
$ systemctl start snapd.service
Failed to start snapd.service: The name org.freedesktop.PolicyKit1 was not provided by any .service files
See system logs and ‘systemctl status snapd.service’ for details.
$ snap version
snap 2.36.2
snapd 2.36.2
series 16
kernel 4.4.0-1100-raspi2

I am using a 32G SD card on a Raspberry Pi 3. Using the image ubuntu-core-16-pi3.img.xz for Raspberry Pi 3’s from the download above.

Is there a different image I should be using?

Thanks,

Matt

mvo · December 12, 2018, 10:45am

Thanks for your bugreport and sorry that you have trouble. Could you please run the “systemctl” commands again with “sudo” ? This should give us some more information. Also please add the “sudo journalctl -u snapd” output. Thank you!

ros-a · December 12, 2018, 1:00pm

Here is more information running sudo:

$ sudo systemctl start snapd.service
“doesn’t return any information”

$ sudo systemctl status snapd.service

● snapd.service - Snappy daemon
   Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-12-12 03:07:35 UTC; 1min 29s ago
 Main PID: 992 (snapd)
   CGroup: /system.slice/snapd.service
           └─992 /usr/lib/snapd/snapd

Dec 12 03:07:34 localhost.localdomain systemd[1]: Starting Snappy daemon...
Dec 12 03:07:35 localhost.localdomain snapd[992]: AppArmor status: apparmor is enabled and all features are available
Dec 12 03:07:35 localhost.localdomain snapd[992]: daemon.go:381: started snapd/2.36.2 (series 16) ubuntu-core/16 (arm
Dec 12 03:07:35 localhost.localdomain snapd[992]: stateengine.go:102: state ensure error: Get https://api.snapcraft.i
Dec 12 03:07:35 localhost.localdomain systemd[1]: Started Snappy daemon.
Dec 12 03:10:27 localhost.localdomain systemd[1]: Started Snappy daemon.

$ snap version
snap 2.36.2
snapd unavailable
series -

$ sudo journalctl -u snapd
– Logs begin at Wed 2018-12-12 03:07:28 UTC, end at Wed 2018-12-12 03:13:23 UTC. –
Dec 12 03:07:34 localhost.localdomain systemd[1]: Starting Snappy daemon…
Dec 12 03:07:35 localhost.localdomain snapd[992]: AppArmor status: apparmor is enabled and all features are available
Dec 12 03:07:35 localhost.localdomain snapd[992]: daemon.go:381: started snapd/2.36.2 (series 16) ubuntu-core/16 (arm
Dec 12 03:07:35 localhost.localdomain snapd[992]: stateengine.go:102: state ensure error: Get https://api.snapcraft.i
Dec 12 03:07:35 localhost.localdomain systemd[1]: Started Snappy daemon.
Dec 12 03:10:27 localhost.localdomain systemd[1]: Started Snappy daemon.
Dec 12 03:11:03 localhost.localdomain systemd[1]: Started Snappy daemon.
Dec 12 03:12:36 localhost.localdomain snapd[992]: state.go:247: PANIC cannot checkpoint even after 5m0s of retries ev
Dec 12 03:12:36 localhost.localdomain snapd[992]: panic: cannot checkpoint even after 5m0s of retries every 3s: write
Dec 12 03:12:36 localhost.localdomain snapd[992]: goroutine 28 [running]:
Dec 12 03:12:36 localhost.localdomain snapd[992]: panic(0x100afa8, 0x118a0078)
Dec 12 03:12:36 localhost.localdomain snapd[992]: /usr/lib/go-1.6/src/runtime/panic.go:481 +0x370
Dec 12 03:12:36 localhost.localdomain snapd[992]: github.com/snapcore/snapd/logger.Panicf(0x12338f8, 0x37, 0x1172dc90
Dec 12 03:12:36 localhost.localdomain snapd[992]: /build/snapd-wsz69D/snapd-2.36.2/_build/src/github.com/snap
Dec 12 03:12:36 localhost.localdomain snapd[992]: github.com/snapcore/snapd/overlord/state.(*State).Unlock(0x118b1720
Dec 12 03:12:36 localhost.localdomain snapd[992]: /build/snapd-wsz69D/snapd-2.36.2/_build/src/github.com/snap
Dec 12 03:12:36 localhost.localdomain snapd[992]: github.com/snapcore/snapd/overlord/state.(*TaskRunner).Ensure(0x118
Dec 12 03:12:36 localhost.localdomain snapd[992]: /build/snapd-wsz69D/snapd-2.36.2/_build/src/github.com/snap
Dec 12 03:12:36 localhost.localdomain snapd[992]: github.com/snapcore/snapd/overlord.(*StateEngine).Ensure(0x1190c460
Dec 12 03:12:36 localhost.localdomain snapd[992]: /build/snapd-wsz69D/snapd-2.36.2/_build/src/github.com/snap
Dec 12 03:12:36 localhost.localdomain snapd[992]: github.com/snapcore/snapd/overlord.(*Overlord).Loop.func1(0x0, 0x0)
lines 1-22

Thanks for your help,

Matt

zyga-snapd · December 13, 2018, 5:16pm

Hello

Can you please provide the logs of the systemd unit snapd.service? You can obtain them with journalctl -u snapd.service.

EDIT: I’m blind, ignore me.

kyrofa · December 13, 2018, 5:21pm

Although perhaps journalctl --no-pager -u snapd would be helpful.

ogra · December 14, 2018, 6:50pm

how exactly did you write the SD card … if you use dd from a terminal you must make sure that all partitions of the SD have been completey unmounted before you write to it … if you do not do this, the partition table will be messed up and the writable partition will not resize and quickly run out of space. I wonder if this is what happened to you (resulting in snapd not being able to write files and the like) , you can check the free disk space with:

df -h /writable

ros-a · December 20, 2018, 3:13pm

Apologies for the late reply.

Yes, it was not able to resize. My mistake. I reloaded after stopping the individual partitions in Disks. Installed perfectly.

Thank you for your time and work on Snaps,

Matt