Unable to start after upgrade to 0.66.1

I upgraded my hass.io installation on a pi2 from version 0.65.6 to 0.66.1.
After the upgrade the system did not come online again.

I logged in via the debug console and found the following error:

root@hassio:/mnt/boot# journalctl -f -u resin-supervisor.service -- Logs begin at Sun 2017-09-17 21:25:34 UTC. -- Apr 04 16:04:23 hassio systemd[1]: Dependency failed for Resin supervisor. Apr 04 16:04:23 hassio systemd[1]: resin-supervisor.service: Job resin-supervisor.service/start failed with result 'dependency'.

I looked a bit further with journalctl -xe and found the following error:
Apr 04 15:41:42 hassio kernel[645]: [[0;1;39m[ 12.069538] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.[[0m

I fixed this by running fsck. Unfortunatly, after a reboot, it still did not get online.

I now found the following error:
Apr 04 16:08:10 hassio systemd[1]: Starting Docker Socket for the API. Apr 04 16:08:10 hassio systemd[1]: Listening on Docker Socket for the API. Apr 04 16:08:10 hassio systemd[1]: Starting Docker Application Container Engine... Apr 04 16:08:10 hassio dockerd[1016]: time="2018-04-04T16:08:10.829569557Z" level=info msg="libcontainerd: new containerd process, pid: 1025" Apr 04 16:08:12 hassio dockerd[1016]: Error starting daemon: error while opening volume store metadata database: invalid database Apr 04 16:08:12 hassio systemd[1]: [[0;1;39mdocker.service: Main process exited, code=exited, status=1/FAILURE[[0m Apr 04 16:08:12 hassio systemd[1]: [[0;1;31mFailed to start Docker Application Container Engine.[[0m Apr 04 16:08:12 hassio systemd[1]: [[0;1;39mdocker.service: Unit entered failed state.[[0m Apr 04 16:08:12 hassio systemd[1]: [[0;1;39mdocker.service: Failed with result 'exit-code'.[[0m Apr 04 16:08:12 hassio systemd[1]: docker.service: Service hold-off time over, scheduling restart. Apr 04 16:08:12 hassio systemd[1]: Stopped Docker Application Container Engine. Apr 04 16:08:12 hassio systemd[1]: Closed Docker Socket for the API. Apr 04 16:08:12 hassio systemd[1]: Stopping Docker Socket for the API.

I seem to have enough space on my SD card:
root@hassio:/mnt/boot# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 481M 0 481M 0% /dev /dev/mmcblk0p3 295M 217M 62M 78% / /dev/disk/by-label/resin-state 19M 200K 17M 2% /mnt/state tmpfs 487M 0 487M 0% /dev/shm tmpfs 487M 5.6M 481M 2% /run tmpfs 487M 0 487M 0% /sys/fs/cgroup tmpfs 487M 0 487M 0% /tmp tmpfs 487M 40K 487M 1% /var/volatile /dev/mmcblk0p1 40M 26M 15M 63% /mnt/boot /dev/mmcblk0p6 28G 8.2G 18G 32% /mnt/data

Need help! Any ideas?

I can’t help, but I seem to have the same problem after the upgrade. I’m able to access the device but I’m stuck at an ‘unable to connect’ message via the web interface.

I just upgraded my pi3 also running hassio without any issues. The problem is that pi2 was the master…

I did make some snapshots, any ideas on how to get those using the debug console?

Didn’t manage to fix it but was able to get all the configs via the debug interface.

I guess my SD card card was corrupting the data.
After the reinstall still had some issues, so I reinstalled the hole thing on a new SD card this morning.

How do I do an FSCK from the debug prompt?
And failing that, how do I recover my config?