/var/lib/lxc/yahm/sd-mmcblk0 missing after update to 2.31.23 firmware

[JDrewes]

I recently updated my yahm to 1.9 and subsequently my ccu2 firmware to 2.31.23. Afterwards, the yahm lxc container would not start. Errors found in yahm.log :

lxc-start 20170115050047.395 ERROR lxc_utils - utils.c:safe_mount:1751 - No such file or directory - Failed to mount /var/lib/lxc/yahm/sd-mmcblk0 onto /usr/lib/arm-linux-gnueabihf/lxc/rootfs/media/sd-mmcblk0/ lxc-start 20170115050047.396 ERROR lxc_conf - conf.c:mount_entry:1708 - No such file or directory - failed to mount '/var/lib/lxc/yahm/sd-mmcblk0' on '/usr/lib/arm-linux-gnueabihf/lxc/rootfs/media/sd-mmcblk0/' lxc-start 20170115050047.396 ERROR lxc_conf - conf.c:lxc_setup:3869 - failed to setup the mount entries for 'yahm' lxc-start 20170115050047.396 ERROR lxc_start - start.c:do_start:811 - Failed to setup container "yahm". lxc-start 20170115050047.397 ERROR lxc_sync - sync.c:sync_wait:57 - An error occurred in another process (expected sequence number 3) lxc-start 20170115050047.108 ERROR lxc_start - start.c:lxc_start:1346 - Failed to spawn container "yahm". lxc-start 20170115050052.213 ERROR lxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start. lxc-start 20170115050052.213 ERROR lxc_start_ui - tools/lxc_start.c:main:368 - To get more details, run the container in foreground mode. lxc-start 20170115050052.213 ERROR lxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options.

re-creating /var/lib/lxc/yahm/sd-mmcblk0 as a symlink to /var/lib/yahm/SDcard/yahm/sd-mmcblk0 allowed the container to start again.

However, now the CCU web front only shows the wait message:

The Homematic CCU is not yet ready Please wait. You will automatically be redirected to the home page.

yahm-ctl info gives an error regarding pivccu-driver:

sudo yahm-ctl info YAHM Version: 1.9 CCU2 Version: 2.31.23

Can not read pivccu-driver module information LXC container information Name: yahm State: RUNNING PID: 1568 IP: 192.168.1.XXX IP: 2003:5f:6e18:7500:4849:43ff:XXXX:XXXX CPU use: 12.62 seconds BlkIO use: 35.71 MiB Link: vethHI1IJ1 TX bytes: 400.64 KiB RX bytes: 42.11 KiB Total bytes: 442.76 KiB

yahm-console.log contains a single line: crond[83]: crond: crond (busybox 1.20.2) started, log level 8

How may I proceed from here, to get my yahm/ccu up and running again?

PS: great job on the project, I like it a lot!

[JDrewes]

I should add that I am running on a raspberry pi 3 B, using raspbian stretch.

[JDrewes]

and it used to work fine with my homematic devices before the upgrade to yahm 1.9 and ccu2 2.31.23

[JDrewes]

I have been able to clear the error related to pivccu-driver with disable, reboot enable. But my ccu web front is still stuck at the same screen...

YAHM Version: 1.9 CCU2 Version: 2.31.23

Module information Module Serial: OEQ0609815 Module Firmware: 1.4.1

LXC container information Name: yahm State: RUNNING PID: 734 IP: 192.168.1.XXX IP: 2003:5f:6e18:7500:4849:43ff:XXXX:XXXX CPU use: 14.77 seconds BlkIO use: 36.32 MiB Link: vethKHTY9D TX bytes: 1.07 MiB RX bytes: 125.83 KiB Total bytes: 1.19 MiB

[JDrewes]

After about 10+ minutes, the ccu web front started normally. Is this long delay expected behavior after ccu fw updates? Anyway, I made a noise for just a delay it seems, this can be closed I guess...