Problem nach Update auf 2.31.25

Einrichtung, Nutzung und Hilfe zu YAHM

Moderator: Co-Administratoren

Antworten
daniel79
Beiträge: 16
Registriert: 28.08.2014, 10:03

Problem nach Update auf 2.31.25

Beitrag von daniel79 » 25.03.2018, 01:59

Hallo,

Da meine yahm ccu aufgrund des zeitumstellungsproblems gerade nicht mehr absprechbar war, habe ich auf 2.31.25 geupdatet. Leider startet der container jetzt garnicht mehr:

Code: Alles auswählen

 pi@ccu2host:/ $ sudo yahm-ctl -v start

!!! You are using develop branch, this branch is unstable. Using at your own risk !!!!

Starting yahm LXC container in debug mode
lxc-start: No such file or directory - Mount of '/var/lib/lxc/yahm/sd-mmcblk0' onto '/usr/lib/arm-linux-gnueabihf/lxc/rootfs/media/sd-mmcblk0/' failed
lxc-start: 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: failed to setup the mount entries for 'yahm'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'yahm'
lxc-start: The container failed to start.
lxc-start: Additional information can be obtained by setting the --logfile and --logpriority options.
Was läuft hier falsch... kann mir jemand weiterhelfen?

Gruss
Daniel

daniel79
Beiträge: 16
Registriert: 28.08.2014, 10:03

Re: Problem nach Update auf 2.31.25

Beitrag von daniel79 » 26.03.2018, 09:25

Ok ich bin selber ein bisschen weiter gekommen.

Nachdem ich wie hier
viewtopic.php?f=67&t=36405&start=10#p353369
angegeben den Mountordner im rootfs des lxc Containers angelegt habe startet es bis hier:

Code: Alles auswählen

pi@ccu2host:~ $ sudo yahm-ctl -v start

!!! You are using develop branch, this branch is unstable. Using at your own risk !!!!

Starting yahm LXC container in debug mode
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
cat: can't open '/sys/module/plat_eq3ccu2/parameters/board_serial': No such file or directory
LED Code: System start: /etc/init.d/S00eQ3SystemStart: line 152: can't create /sys/class/leds/power/brightness: nonexistent directory
/etc/init.d/S00eQ3SystemStart: line 152: can't create /sys/class/leds/power/trigger: nonexistent directory
/etc/init.d/S00eQ3SystemStart: line 152: can't create /sys/class/leds/internet/trigger: nonexistent directory
/etc/init.d/S00eQ3SystemStart: line 152: can't create /sys/class/leds/info/trigger: nonexistent directory
/etc/init.d/S00eQ3SystemStart: line 152: can't create /sys/class/leds/info/brightness: nonexistent directory
/etc/init.d/S00eQ3SystemStart: line 152: can't create /sys/class/leds/info/delay_off: nonexistent directory
/etc/init.d/S00eQ3SystemStart: line 152: can't create /sys/class/leds/info/delay_on: nonexistent directory
modprobe: chdir(4.9.35-v7+): No such file or directory
modprobe: chdir(4.9.35-v7+): No such file or directory
modprobe: chdir(4.9.35-v7+): No such file or directory
modprobe: chdir(4.9.35-v7+): No such file or directory
modprobe: chdir(4.9.35-v7+): No such file or directory
modprobe: chdir(4.9.35-v7+): No such file or directory
modprobe: chdir(4.9.35-v7+): No such file or directory
modprobe: chdir(4.9.35-v7+): No such file or directory
modprobe: chdir(4.9.35-v7+): No such file or directory
modprobe: chdir(4.9.35-v7+): No such file or directory
OK
Init Firewall: Starting crond: OK
Starting logging: OK
Populating /dev using udev: cannot open /dev/null
done
Starting watchdog...
error: /dev/mmcblk0: No such file or directory
error: /dev/mmcblk0p1: No such file or directory
error: /dev/mmcblk0p2: No such file or directory
Starting network over usb: ifconfig: SIOCSIFADDR: No such device
error: /dev/loop0: No such file or directory
error: /dev/loop1: No such file or directory
error: /dev/loop4: No such file or directory
OK
error: /dev/loop3: No such file or directory
error: /dev/loop5: No such file or directory
error: /dev/loop2: No such file or directory
error: /dev/loop6: No such file or directory
error: /dev/loop7: No such file or directory
error: /dev/ram1: No such file or directory
error: /dev/ram0: No such file or directory
error: /dev/ram10: No such file or directory
Starting network...
error: /dev/ram12: No such file or directory
error: /dev/ram11: No such file or directory
error: /dev/ram14: No such file or directory
error: /dev/ram13: No such file or directory
error: /dev/ram5: No such file or directory
error: /dev/ram2: No such file or directory
error: /dev/ram15: No such file or directory
error: /dev/ram6: No such file or directory
error: /dev/ram3: No such file or directory
error: /dev/ram4: No such file or directory
error: /dev/ram8: No such file or directory
error: /dev/ram7: No such file or directory
error: /dev/ram9: No such file or directory
ip: RTNETLINK answers: File exists
sysctl: error: 'net.ipv4.tcp_timestamps' is an unknown key
eth0 carrier detected
Starting Network Interface Plugging Daemon: eth0.
Preparing start of hs485dOK
Starting setclock: 43183 26310.099    1304.0    516.4    1180.4  38177.5   -520611
hwclock: Cannot access the Hardware Clock via any known method.
hwclock: Use the --debug option to see the details of our search for an access method.
OK
Can't daemonize: No such device
Starting eq3configd: cat: can't open '/sys/module/plat_eq3ccu2/parameters/radio_mac': No such file or directory
cat: can't open '/sys/module/plat_eq3ccu2/parameters/board_serial': No such file or directory
OK
Starting lighttpd: OK
Starting sshd: PRNG is not seeded
OK
ls: /etc/config/*.keychange: No such file or directory
OK
Starting hs485d: OK
Starting multimacd:
Could not open SPI device: No such file or directory
Could not open SPI device: No such file or directory
sed: /sys/module/plat_eq3ccu2/parameters/radio_mac: No such file or directory
2018/03/26 09:18:31.045 <Error> CCU2CommControllerMod::performIdentify(): Unable to determine coprocessor state.
Could not open SPI device: No such file or directory
firmware update disabled
Waiting for multimacd to get ready.sh: 244: unknown operand
.sh: 244: unknown operand
.sh: 244: unknown operand
.sh: 244: unknown operand
.sh: 244: unknown operand
Timeout while waiting for multimacd to get ready.
Starting rfd:
Waiting for rfd to get ready.rfd is ready now.
Starting HMServer: cp: can't stat '/etc/config_templates/hmip_networkkey.conf': No such file or directory
Waiting for HMServer to get ready
ich glaube dass da das Update bzw die Anpassung der Firmware mal komplett fehlgeschlagen ist...
Kann ich das Update irgendwie wiederholen?

Gruß
Daniel

leonsio
Beiträge: 1107
Registriert: 07.01.2012, 14:06
Danksagung erhalten: 6 Mal

Re: Problem nach Update auf 2.31.25

Beitrag von leonsio » 27.03.2018, 23:18

du müsstest eigentlich nur /var/lib/lxc/yahm/sd-mmcblk0 anlegen
restliche Meldungen sind "normal"

es kann passieren dass der Homematic Treiber nicht neu installiert wird
einfach yahm-module -m pivccu-driver -f enable nochmal ausführen, dann sollte alles laufen

Antworten

Zurück zu „YAHM“