Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[sanda]

Hallo zusammen,

ich habe das Problem, dass IObroker kürzlich schon mehrmals nicht mehr startet bzw. abstürzt.
Danach muss man per Befehl "iob fix" und "iob start" durchführen und dann startet das System wieder.
Danach holt es sich irgendwo einen letzten, alten Stand hoch und die Bilder (icons-mfd-png) in den Schaltflächen verschwinden.
Alle Änderungen, wie neue Adapter oder Anpassungen in den VIS, werden einfach wieder zurückgesetzt/ gelöscht und ein bestimmter alter Stand kommt wieder.
Ich habe schon die node.js und npm aktualisiert auch das letzte Backup vom iobroker draufgespielt, trotzdem kommt immer irgendein alter letzter Stand und alle Änderungen sind weg, auch das letzte Backup hilft nicht.

Was kann es sein, wie kann man nun die Änderungen wieder speicher lassen, auch wenn das System abstürzt?
Was kann man noch überprüfen oder aktualisieren, damit das System überhaupt nicht mehr abstürzt?

Danke euch im Voraus, ich bin schon wirklich am Verzweifeln.

VG Alex

[Homoran]

@sanda das klingt als ob die SD-Karte den Geits aufgibt und nur noch RO ist.

genaues sagt iob diag

[sanda]

Die Liste mit iob diag ist schon etwas lang, kann man dort etwas sofort erkennen, wofür die Abstürze verantwortlich sind:

========== Start marking the full check here ===========

```bash
Script v.2025-08-09

*** BASE SYSTEM ***
Operating System: Raspbian GNU/Linux 11 (bullseye)
   Static hostname: raspi
         Icon name: computer
            Kernel: Linux 6.1.21-v8+
      Architecture: arm64
OS is similar to: debian

Model           : Raspberry Pi 4 Model B Rev 1.2
Docker          : false
Virtualization  : none
Kernel          : aarch64
Userland        : 32 bit

Systemuptime and Load:
 11:21:38 up 14:44,  2 users,  load average: 2.72, 5.68, 5.76
CPU threads: 4


*** LIFE CYCLE STATUS ***
Debian Release codenamed 'bullseye' reached its END OF LIFE and needs to be updated to the latest stable release 'trixie' NOW!

*** RASPBERRY THROTTLING ***
Current issues:
No throttling issues detected.

Previously detected issues:
~ Under-voltage has occurred

*** TIME AND TIMEZONES ***
               Local time: Sun 2025-12-07 11:21:38 CET
           Universal time: Sun 2025-12-07 10:21:38 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
pi
HOME=/home/pi
GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin gpio i2c spi iobroker

User that is running 'js-controller':
js-controller is not running

*** DISPLAY-SERVER SETUP ***
Display-Server:         false
Display-Manager:        * lightdm.service - Light Display Manager
Desktop:
Session:                tty

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            3.8G        536M        1.5G        1.0M        1.8G        3.4G
Swap:            99M          0B         99M
Total:          3.9G        536M        1.6G

Active iob-Instances:   0

         3794 M total memory
          536 M used memory
          745 M active memory
         1209 M inactive memory
         1496 M free memory
          258 M buffer memory
         1502 M swap cache
           99 M total swap
            0 M used swap
           99 M free swap

*** top - Table Of Processes  ***
top - 11:21:41 up 14:44,  2 users,  load average: 2.72, 5.68, 5.76
Tasks: 177 total,   1 running, 176 sleeping,   0 stopped,   0 zombie
%Cpu(s):  1.4 us,  1.4 sy,  0.0 ni, 97.1 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   3794.3 total,   1495.8 free,    537.1 used,   1761.5 buff/cache
MiB Swap:    100.0 total,    100.0 free,      0.0 used.   3397.4 avail Mem

*** FAILED SERVICES ***

  UNIT             LOAD   ACTIVE SUB    DESCRIPTION
* fstrim.service   loaded failed failed Discard unused blocks on filesystems from /etc/fstab
* iobroker.service loaded failed failed ioBroker Server

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
2 loaded units listed.


*** DMESG CRITICAL ERRORS ***
8 CRITICAL ERRORS DETECTED!
Check 'sudo dmesg --level=emerg,alert,crit -T' for details

*** FILESYSTEM ***
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/root      ext4       29G   21G  7.6G  73% /
devtmpfs       devtmpfs  1.7G     0  1.7G   0% /dev
tmpfs          tmpfs     1.9G     0  1.9G   0% /dev/shm
tmpfs          tmpfs     759M  1.3M  758M   1% /run
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
/dev/mmcblk0p1 vfat      253M   51M  202M  20% /boot
tmpfs          tmpfs     380M   20K  380M   1% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Sun Dec  7 10:55:17 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[Sun Dec  7 10:55:17 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[Sun Dec  7 10:56:04 2025] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:1098: group 233, block bitmap and bg descriptor inconsistent: 4077 vs 12269 free cl                           usters
[Sun Dec  7 10:57:27 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[Sun Dec  7 11:05:51 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[Sun Dec  7 11:21:16 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[Sun Dec  7 11:21:16 2025] EXT4-fs error (device mmcblk0p2): __ext4_new_inode:1277: comm ln: failed to insert inode 261255: doubly allocated?
[Sun Dec  7 11:21:18 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem

Show mounted filesystems:
TARGET  SOURCE         FSTYPE OPTIONS
/       /dev/mmcblk0p2 ext4   rw,noatime
`-/boot /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remount-ro

Files in neuralgic directories:

/var:
du: cannot access '/var/lib/grafana/grafana.db-journal': No such file or directory
du: cannot access '/var/lib/influxdb/data/_internal/monitor/1427/000000029-000000001.tsm': No such file or directory
du: cannot access '/var/lib/influxdb/data/_internal/monitor/1427/000000008-000000002.tsm': No such file or directory
du: cannot access '/var/lib/influxdb/data/_internal/monitor/1427/000000035-000000001.tsm': No such file or directory
du: cannot access '/var/lib/influxdb/data/_internal/monitor/1427/000000032-000000001.tsm': No such file or directory
du: cannot access '/var/lib/influxdb/data/_internal/monitor/1427/000000033-000000001.tsm': No such file or directory
du: cannot access '/var/lib/influxdb/data/_internal/monitor/1427/000000028-000000002.tsm': No such file or directory
du: cannot access '/var/lib/influxdb/data/_internal/monitor/1427/000000034-000000001.tsm': No such file or directory
du: cannot access '/var/lib/influxdb/data/_internal/monitor/1427/000000036-000000001.tsm': No such file or directory
du: cannot access '/var/lib/influxdb/data/_internal/monitor/1427/000000016-000000002.tsm': No such file or directory
du: cannot access '/var/lib/influxdb/data/_internal/monitor/1427/000000031-000000001.tsm': No such file or directory
du: cannot access '/var/lib/influxdb/wal/_internal/monitor/1427/_00124.wal': No such file or directory
du: cannot access '/var/lib/influxdb/wal/_internal/monitor/1427/_00125.wal': No such file or directory
du: cannot access '/var/lib/influxdb/wal/_internal/monitor/1427/_00122.wal': No such file or directory
du: cannot access '/var/lib/influxdb/wal/_internal/monitor/1427/_00123.wal': No such file or directory
5.2G    /var/
3.0G    /var/log/journal/f5b93586183c4958a25d963a3f774c93
3.0G    /var/log/journal
3.0G    /var/log
1.2G    /var/lib

Archived and active journals take up 2.9G in the file system.

/opt/iobroker/backups:
7.4M    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
334M    /opt/iobroker/iobroker-data/
226M    /opt/iobroker/iobroker-data/files
77M     /opt/iobroker/iobroker-data/backup-objects
47M     /opt/iobroker/iobroker-data/files/admin.admin
46M     /opt/iobroker/iobroker-data/files/admin.admin/custom/assets

The five largest files in iobroker-data are:
27M     /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map
9.2M    /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js
8.5M    /opt/iobroker/iobroker-data/objects.jsonl
8.1M    /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-C_W7K-9p.js
4.6M    /opt/iobroker/iobroker-data/files/javascript.admin/vs/language/typescript/tsWorker.js

USB-Devices by-id:
USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':

/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2410294-if00

*** ZigBee Settings ***
Zigbee Network Settings on your coordinator/in nvbackup are:

zigbee.X
Extended Pan ID:
*** MASKED ***
Pan ID:
*** MASKED ***
Channel:
*** MASKED ***
Network Key:
*** MASKED ***

To unmask the settings run 'iob diag --unmask'


*** NodeJS-Installation ***

/usr/bin/nodejs         v20.19.0
/usr/bin/node           v20.19.0
/usr/bin/npm            10.8.2
/usr/bin/npx            10.8.2
/usr/bin/corepack       0.31.0

nodejs:
  Installed: 20.19.0-1nodesource1
  Candidate: 22.15.0-1nodesource1
  Version table:
     22.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.13.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.5.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.4.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
     22.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
 *** 20.19.0-1nodesource1 100
        100 /var/lib/dpkg/status
     12.22.12~dfsg-1~deb11u7 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
     10.24.0~dfsg-1~deb10u3 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

Checking for nodejs vulnerability:


██████   █████  ███    ██  ██████  ███████ ███████
██   ██ ██   ██ ████   ██ ██       ██      ██   ██
██   ██ ███████ ██ ██  ██ ██   ███ █████   ███████
██   ██ ██   ██ ██  ██ ██ ██    ██ ██      ██   ██
██████  ██   ██ ██   ████  ██████  ███████ ██   ██


The current Node.js version (v20.19.0) is vulnerable to the following CVEs:

CVE-2025-23166(high):  The C++ method SignTraits::DeriveBits() may incorrectly call ThrowException() based on user-supplied inputs when executing in a background threa                           d, crashing the Node.js process. Such cryptographic operations are commonly applied to untrusted inputs. Thus, this mechanism potentially allows an adversary to remote                           ly crash a Node.js runtime.
Patched versions: ^20.19.2 || ^22.15.1 || ^23.11.1 || ^24.0.2
=

CVE-2025-23167(medium): A flaw in Node.js 20's HTTP parser allows improper termination of HTTP/1 headers using `\r\n\rX` instead of the required `\r\n\r\n`.
This inconsistency enables request smuggling, allowing attackers to bypass proxy-based access controls and submit unauthorized requests.

The issue was resolved by upgrading `llhttp` to version 9, which enforces correct header termination.

Impact:
* This vulnerability affects only Node.js 20.x users prior to the `llhttp` v9 upgrade.

Patched versions: ^20.19.2
=

*** ioBroker-Installation ***

ioBroker Status
iobroker is not running on this host.


Objects type: jsonl
States  type: jsonl

Hosts:

Core adapters versions
js-controller:  7.0.7
admin:          7.7.19
javascript:     8.9.2

nodejs modules from github:     2
+-- iobroker.comfoairq@0.1.0 (git+ssh://git@github.com/klein0r/ioBroker.comfoairq.git#69bcd8796c74fcffcf400f2a57e0f648e693d06b)
+-- iobroker.fusionsolar@1.0.0 (git+ssh://git@github.com/KornSW/ioBroker.fusionsolar.git#5316673cf49c8cccefdf4481cfcbdec66e8cb1f4)

Adapter State


Enabled adapters with bindings

ioBroker-Repositories
List is empty

Installed ioBroker-Adapters
Error: Object "system.repositories" not found

Objects and States
Please stand by - This may take a while
Objects:        15082
States:         2743

*** OS-Repositories and Updates ***
E: The repository 'https://archive.raspbian.org/raspbian buster Release' no longer has a Release file.
E: The repository 'http://raspbian.raspberrypi.org/raspbian buster Release' no longer has a Release file.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.grafana.com/oss/deb stable InRelease: The following signatures were invalid: EXPKEYSIG 963FA27710458545 Grafana Labs <engineering@grafana.com>
Pending Updates: 62

*** Listening Ports ***
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
tcp        0      0 127.0.0.1:8088          0.0.0.0:*               LISTEN      119        11931      573/influxd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          15471      602/sshd: /usr/sbin
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      0          137654     16930/cupsd
tcp        0      0 0.0.0.0:5900            0.0.0.0:*               LISTEN      0          15526      598/vncserver-x11-c
tcp        0      0 127.0.0.1:6379          0.0.0.0:*               LISTEN      117        15342      572/redis-server 12
tcp6       0      0 :::3000                 :::*                    LISTEN      120        16175      1406/grafana
tcp6       0      0 ::1:631                 :::*                    LISTEN      0          137653     16930/cupsd
tcp6       0      0 :::6600                 :::*                    LISTEN      0          11701      1/init
tcp6       0      0 ::1:6379                :::*                    LISTEN      117        15343      572/redis-server 12
tcp6       0      0 :::22                   :::*                    LISTEN      0          15473      602/sshd: /usr/sbin
tcp6       0      0 :::8086                 :::*                    LISTEN      119        18544      573/influxd
tcp6       0      0 :::5900                 :::*                    LISTEN      0          15525      598/vncserver-x11-c
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          14270      477/dhcpcd
udp        0      0 0.0.0.0:52359           0.0.0.0:*                           108        14160      411/avahi-daemon: r
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        14158      411/avahi-daemon: r
udp6       0      0 :::546                  :::*                                0          14302      477/dhcpcd
udp6       0      0 :::46035                :::*                                108        14161      411/avahi-daemon: r
udp6       0      0 :::5353                 :::*                                108        14159      411/avahi-daemon: r

*** Log File - Last 25 Lines ***

2025-12-07 10:55:07.980  - error: host.raspi Caught by controller[0]:     at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/maybeCallback.ts:129:17)
2025-12-07 10:55:07.981  - error: host.raspi Caught by controller[0]:     at Gruenbeck._setObjectNotExists (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:5098:26)
2025-12-07 10:55:07.981  - error: host.raspi Caught by controller[0]:     at processTicksAndRejections (node:internal/process/task_queues:95:5)
2025-12-07 10:55:07.981  - error: host.raspi Caught by controller[0]:     at /opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2336:17
2025-12-07 10:55:07.981  - warn: host.raspi instance system.adapter.gruenbeck.0 terminated due to SIGKILL
2025-12-07 10:55:07.982  - info: host.raspi instance system.adapter.gruenbeck.0 terminated with code null ()
2025-12-07 10:55:07.982  - warn: host.raspi instance system.adapter.web.1 terminated due to SIGKILL
2025-12-07 10:55:07.983  - info: host.raspi instance system.adapter.web.1 terminated with code null ()
2025-12-07 10:55:08.050  - warn: host.raspi instance system.adapter.telegram.0 terminated due to SIGKILL
2025-12-07 10:55:08.051  - info: host.raspi instance system.adapter.telegram.0 terminated with code null ()
2025-12-07 10:55:09.326  - info: comfoairq.0 (20442) starting. Version 0.1.0 (non-npm: klein0r/ioBroker.comfoairq#69bcd8796c74fcffcf400f2a57e0f648e693d06b) in /opt/iobroker/node_modules/iobroker.comfoairq, node: v20.19.0, js-controller: 7.0.7
2025-12-07 10:55:09.804  - info: comfoairq.0 (20442) State value to set for "comfoairq.0.sensor.fanNextChange" has to be type "number" but received type "object"
2025-12-07 10:55:09.875  - info: comfoairq.0 (20442) State value to set for "comfoairq.0.sensor.fanNextChange" has to be type "number" but received type "object"
2025-12-07 10:55:09.903  - info: comfoairq.0 (20442) State value to set for "comfoairq.0.version.comfonet" has to be type "string" but received type "number"
2025-12-07 10:55:10.024  - info: comfoairq.0 (20442) State value to set for "comfoairq.0.version.gateway" has to be type "string" but received type "number"
2025-12-07 10:55:17.538  - info: host.raspi force terminating
2025-12-07 10:55:17.539  - info: host.raspi Adapter comfoairq still running
2025-12-07 10:55:20.235  - info: comfoairq.0 (20442) terminating with timeout
2025-12-07 10:55:20.237  - info: comfoairq.0 (20442) Terminated (NO_ERROR): Without reason
2025-12-07 10:55:22.509  - error: comfoairq.0 (20442) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2025-12-07 10:55:22.557  - warn: comfoairq.0 (20442) get state error: Connection is closed.
2025-12-07 10:55:22.559  - warn: comfoairq.0 (20442) get state error: DB closed
2025-12-07 10:55:22.561  - info: comfoairq.0 (20442) terminating
2025-12-07 10:55:22.562  - info: comfoairq.0 (20442) terminating
2025-12-07 10:55:27.514  - error: comfoairq.0 (20442) Cannot check object existence of "comfoairq.0.sensor.fanExhaustSpeed": Connection is closed.

============ Mark until here for C&P =============

iob diag has finished.

[Homoran]

@sanda sagte in iobroker startet nicht und nach Neustart alte Daten:

*** DMESG CRITICAL ERRORS ***
8 CRITICAL ERRORS DETECTED!
Check 'sudo dmesg --level=emerg,alert,crit -T' for details

bitte durchführen, aber

Messages concerning ext4 filesystem in dmesg:
[Sun Dec 7 10:55:17 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[Sun Dec 7 10:55:17 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[Sun Dec 7 10:56:04 2025] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:1098: group 233, block bitmap and bg descriptor inconsistent: 4077 vs 12269 free cl usters
[Sun Dec 7 10:57:27 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[Sun Dec 7 11:05:51 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[Sun Dec 7 11:21:16 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[Sun Dec 7 11:21:16 2025] EXT4-fs error (device mmcblk0p2): __ext4_new_inode:1277: comm ln: failed to insert inode 261255: doubly allocated?
[Sun Dec 7 11:21:18 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem

sagt schon alles

[sanda]

Das sieht glaub ich nicht so toll aus oder:

pi@raspi:~ $ sudo dmesg --level=emerg,alert,crit -T
[So Dez  7 10:55:17 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[So Dez  7 10:55:17 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[So Dez  7 10:56:04 2025] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:1098: group 233, block bitmap and bg descriptor inconsistent: 4077 vs 12269 free clusters
[So Dez  7 10:57:27 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[So Dez  7 11:05:51 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[So Dez  7 11:21:16 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[So Dez  7 11:21:16 2025] EXT4-fs error (device mmcblk0p2): __ext4_new_inode:1277: comm ln: failed to insert inode 261255: doubly allocated?
[So Dez  7 11:21:18 2025] EXT4-fs error (device mmcblk0p2) in ext4_free_inode:362: Corrupt filesystem
[So Dez  7 11:31:16 2025] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:1098: group 116, block bitmap and bg descriptor inconsistent: 4666 vs 4794 free clusters

[Homoran]

@sanda sagte in iobroker startet nicht und nach Neustart alte Daten:

Das sieht glaub ich nicht so toll aus oder:

richtig!
wie vermutet

[sanda]

Am besten nun eine neue SD-Karte kaufen und dann alles neu aufsetzen?
Kriege ich alle Daten irgendwie wieder rüberkopiert auf die neue SD-Karte, am besten nach dem Neuaufsetzen, dann mit Backitup das letzte Backup draufspielen?

[Thomas Braun]

@sanda sagte in iobroker startet nicht und nach Neustart alte Daten:

Raspbian GNU/Linux 11 (bullseye)

Veraltet, upgrade nicht möglich. Installier da NEU
Raspbian GNU/Linux 13 (trixie)

Diesmal dann gleich in der 64Bit-Lite-Version, ohne Desktop-Gekröse.

~ Under-voltage has occurred

Spannungsversorgung vermutlich wackelig.
4GB RAM kann auch zu wenig sein.

8 CRITICAL ERRORS DETECTED!

Check 'sudo dmesg --level=emerg,alert,crit -T' for details

Kannst du mal anschauen, aber da du eh neuinstallierst (auf einem frischen Datenträger)...
Das Dateisystem ist nämlich kaputt:
Corrupt filesystem

Pending Updates: 62

Das neue System regelmäßiger aktuell halten.

[sanda]

Ich habe erst letzte Woche alles aktualisiert, dann lief es mal wieder eine Woche und nun sind die Daten wieder zurückgesetzt.
Alles sehr seltsam.

[Thomas Braun]

@sanda sagte in iobroker startet nicht und nach Neustart alte Daten:

Alles sehr seltsam.

Auf ein korruptes Dateisystem kann nicht geschrieben werden. Deswegen siehst du da halt die alten Dateien.

[Homoran]

@sanda sagte in iobroker startet nicht und nach Neustart alte Daten:

Alles sehr seltsam.

sagte in iobroker startet nicht und nach Neustart alte Daten:

klingt als ob die SD-Karte den Geist aufgibt und nur noch RO ist.

dann bleiben die Änderungen nur im RAM

[sanda]

Ok, vielen lieben Dank euch, hab eben eine neue SD-Karte bestellt und setzte es dann nächste Woche alles neu auf.
Danke und VG Alex