Hello everyone,
I recently encountered an issue with my CCU2 where it froze for the first time. After rebooting, I noticed that some of my HmIP actors were displaying incorrect or missing channel parameters. Specifically, the HmIP-PCBS2 actors were showing strange parameter values. I’ve included a screenshot of the affected parameters below.
I also noticed some errors in the system log related to UBI device attachment failures. Here’s a snippet of the relevant log entries:
[ 3.430000] UBI: max/mean erase counter: 43/16
[ 3.440000] UBI: image sequence number: 177226844
[ 3.450000] UBI: background thread “ubi_bgt0d” started, PID 32
[ 3.460000] UBI: attaching mtd6 to ubi1
[ 3.470000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 3.480000] UBI: logical eraseblock size: 126976 bytes
[ 3.490000] UBI: smallest flash I/O unit: 2048
[ 3.500000] UBI: VID header offset: 2048 (aligned 2048)
[ 3.510000] UBI: data offset: 4096
[ 3.520000] UBI: max/mean erase counter: 150/81
[ 3.530000] UBI: image sequence number: 2047575981
[ 3.540000] UBI: background thread “ubi_bgt1d” started, PID 33
[ 3.550000] UBI: max/mean erase counter: 43/16
[ 3.560000] UBI: image sequence number: 177226844
[ 3.570000] UBI: background thread “ubi_bgt0d” started, PID 32
[ 3.580000] UBI: max/mean erase counter: 150/81
[ 3.590000] UBI: image sequence number: 2047575981
[ 3.600000] UBI: background thread “ubi_bgt1d” started, PID 33
I’ve tried clearing the browser cache as a temporary fix, but the issue persists after rebooting. I’m wondering if this is related to the UBI device attachment errors in the log. Has anyone else experienced similar issues with HmIP actors or UBI devices?
Any advice or suggestions on how to resolve this would be greatly appreciated!
Best regards,
[Your Name]