Backitup Restore fehler
-
@glasfaser
also jscontroler ist jetzt aktualisiert 5.0.12ich kann jetzt weiter weitermachen oder ? weboberfläche geht aber nicht mehr
======== Start marking the full check here =========
Skript v.2023-06-20 *** BASE SYSTEM *** Static hostname: ubuntu Icon name: computer Machine ID: 965a81734c8d402ab05ca26017c6e6a9 Boot ID: 0c59d3c9640b486fadab37c9e124b76a Operating System: Ubuntu 23.04 Kernel: Linux 6.2.0-1013-raspi Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 23:16:45 up 8 min, 2 users, load average: 3.57, 1.61, 0.67 CPU threads: 4 Raspberry only: throttled=0x0 Other values than 0x0 hint to temperature/voltage problems temp=68.6'C volt=0.9260V *** Time and Time Zones *** Local time: Wed 2023-09-27 23:16:46 CEST Universal time: Wed 2023-09-27 21:16:46 UTC RTC time: n/a Time zone: Europe/Paris (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** esmax /home/esmax esmax adm dialout cdrom sudo audio video plugdev games users input render netdev gpio spi i2c iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 8.2G 1.4G 6.4G 3.2M 602M 6.8G Swap: 0B 0B 0B Total: 8.2G 1.4G 6.4G 7809 M total memory 1352 M used memory 283 M active memory 1153 M inactive memory 6148 M free memory 59 M buffer memory 515 M swap cache 0 M total swap 0 M used swap 0 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on tmpfs tmpfs 781M 3.1M 778M 1% /run /dev/mmcblk0p2 ext4 59G 5.2G 51G 10% / tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock /dev/mmcblk0p1 vfat 253M 151M 102M 60% /boot/firmware tmpfs tmpfs 781M 4.0K 781M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Sep 27 23:08:16 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbswap=1 smsc95xx.macaddr=E4:5F:01:1B:22:9D vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash [Wed Sep 27 23:08:29 2023] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs [Wed Sep 27 23:08:29 2023] EXT4-fs (mmcblk0p2): mounted filesystem 25a83575-fd50-4dcc-85e0-e3a81c621aa2 with ordered data mode. Quota mode: none. [Wed Sep 27 23:08:31 2023] EXT4-fs (mmcblk0p2): re-mounted 25a83575-fd50-4dcc-85e0-e3a81c621aa2. Quota mode: none. Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,relatime,discard,errors=remount-ro,commit=30 |-/snap/core22/611 /dev/loop0 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/core22/867 /dev/loop1 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/lxd/24646 /dev/loop2 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/lxd/25755 /dev/loop3 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/snapd/18600 /dev/loop4 squashfs ro,nodev,relatime,errors=continue,threads=single `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 943M /var/ 677M /var/lib 505M /var/lib/snapd 504M /var/lib/snapd/snaps 222M /var/cache Archived and active journals take up 43.0M in the file system. /opt/iobroker/backups: 4.5M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 119M /opt/iobroker/iobroker-data/ 83M /opt/iobroker/iobroker-data/files 27M /opt/iobroker/iobroker-data/files/javascript.admin 15M /opt/iobroker/iobroker-data/files/javascript.admin/static/js 15M /opt/iobroker/iobroker-data/files/javascript.admin/static The five largest files in iobroker-data are: 9.8M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/2.f6fd0e72.chunk.js.map 8.1M /opt/iobroker/iobroker-data/objects.jsonl 8.0M /opt/iobroker/iobroker-data/objects.json.migrated 8.0M /opt/iobroker/iobroker-data/objects.json.bak.migrated 4.4M /opt/iobroker/iobroker-data/files/javascript.admin/vs/language/typescript/tsWorker.js *** NodeJS-Installation *** /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x lunar/main arm64 Packages 100 /var/lib/dpkg/status 18.13.0+dfsg1-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/universe arm64 Packages Temp directories causing npm8 problem: 0 No problems detected npm ERR! code ELSPROBLEMS npm ERR! extraneous: @abandonware/bluetooth-hci-socket@0.5.3-10 /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket npm ERR! extraneous: usb@1.9.2 /opt/iobroker/node_modules/usb npm ERR! extraneous: debug@4.3.4 /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/debug npm ERR! extraneous: ms@2.1.2 /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/node_modules/ms npm ERR! invalid: @types/node@12.20.55 /opt/iobroker/node_modules/iobroker.javascript/node_modules/@types/node npm ERR! extraneous: node-addon-api@4.3.0 /opt/iobroker/node_modules/usb/node_modules/node-addon-api npm ERR! A complete log of this run can be found in: /home/esmax/.npm/_logs/2023-09-27T21_17_01_730Z-debug-0.log Errors in npm tree: 0 *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl No configuration change needed. Multihost discovery server: disabled Discovery authentication: enabled Persistent activation: disabled Objects: jsonl on 127.0.0.1 States: jsonl on 127.0.0.1 Core adapters versions js-controller: 5.0.12 admin: 5.2.1 javascript: 5.2.13 Adapters from github: 0 Adapter State system.adapter.admin.0 : admin : ubuntu - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alexa2.0 : alexa2 : ubuntu - disabled + system.adapter.backitup.0 : backitup : ubuntu - enabled system.adapter.cloud.0 : cloud : ubuntu - disabled system.adapter.discovery.0 : discovery : ubuntu - disabled system.adapter.flot.0 : flot : ubuntu - disabled + system.adapter.heatingcontrol.0 : heatingcontrol : ubuntu - enabled system.adapter.history.0 : history : ubuntu - enabled system.adapter.ical.0 : ical : ubuntu - enabled system.adapter.info.0 : info : ubuntu - disabled system.adapter.iot.0 : iot : ubuntu - disabled + system.adapter.javascript.0 : javascript : ubuntu - enabled system.adapter.linkeddevices.0 : linkeddevices : ubuntu - disabled system.adapter.mobile.0 : mobile : ubuntu - disabled system.adapter.radar2.0 : radar2 : ubuntu - disabled system.adapter.rpi2.0 : rpi2 : ubuntu - disabled + system.adapter.shuttercontrol.0 : shuttercontrol : ubuntu - enabled system.adapter.socketio.0 : socketio : ubuntu - disabled, port: 8084, bind: 0.0.0.0, run as: admin system.adapter.telegram.0 : telegram : ubuntu - disabled, port: 8443, bind: 0.0.0.0 system.adapter.text2command.0 : text2command : ubuntu - disabled system.adapter.tr-064.0 : tr-064 : ubuntu - disabled system.adapter.vis-colorpicker.0 : vis-colorpicker : ubuntu - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : ubuntu - disabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : ubuntu - disabled system.adapter.vis-metro.0 : vis-metro : ubuntu - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : ubuntu - disabled system.adapter.vis.0 : vis : ubuntu - disabled system.adapter.web.0 : web : ubuntu - enabled, port: 443, bind: 0.0.0.0, run as: admin + system.adapter.zwave2.0 : zwave2 : ubuntu - enabled + instance is alive Enabled adapters with bindings system.adapter.admin.0 : admin : ubuntu - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.web.0 : web : ubuntu - enabled, port: 443, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.10.1 , installed 5.2.1 [Updatable] Adapter "alexa2" : 3.25.2 , installed 3.9.3 [Updatable] Adapter "backitup" : 2.8.1 , installed 2.2.2 [Updatable] Adapter "cloud" : 4.4.1 , installed 4.1.0 [Updatable] Adapter "discovery" : 3.1.0 , installed 3.1.0 Adapter "flot" : 1.12.0 , installed 1.10.6 [Updatable] Adapter "heatingcontrol": 2.11.1 , installed 2.7.2 [Updatable] Adapter "history" : 2.2.6 , installed 1.9.14 [Updatable] Adapter "ical" : 1.13.3 , installed 1.11.4 [Updatable] Adapter "info" : 1.9.26 , installed 1.9.8 [Updatable] Adapter "iot" : 1.14.5 , installed 1.8.22 [Updatable] Adapter "javascript" : 7.1.4 , installed 5.2.13 [Updatable] Controller "js-controller": 5.0.12 , installed 5.0.12 Adapter "linkeddevices": 1.5.5 , installed 1.4.3 [Updatable] Adapter "mobile" : 1.0.1 , installed 1.0.1 Adapter "radar2" : 2.0.7 , installed 2.0.3 [Updatable] Adapter "rpi2" : 1.3.2 , installed 1.3.1 [Updatable] Adapter "shuttercontrol": 1.6.2 , installed 1.2.1 [Updatable] Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.5.5 , installed 3.1.4 [Updatable] Adapter "telegram" : 1.16.0 , installed 1.10.0 [Updatable] Adapter "text2command" : 3.0.2 , installed 2.1.1 [Updatable] Adapter "tr-064" : 4.2.18 , installed 4.2.14 [Updatable] Adapter "vis" : 1.4.16 , installed 1.4.5 [Updatable] Adapter "vis-colorpicker": 2.0.3 , installed 1.2.0 [Updatable] Adapter "vis-hqwidgets": 1.4.0 , installed 1.1.7 [Updatable] Adapter "vis-jqui-mfd" : 1.0.12 , installed 1.0.12 Adapter "vis-metro" : 1.2.0 , installed 1.1.2 [Updatable] Adapter "vis-timeandweather": 1.2.2, installed 1.1.7 [Updatable] Adapter "web" : 6.1.2 , installed 3.4.9 [Updatable] Adapter "zwave2" : 3.0.5 , installed 3.0.5 Objects and States Please stand by - This may take a while Objects: 4592 States: 3264 *** OS-Repositories and Updates *** Hit:1 http://ports.ubuntu.com/ubuntu-ports lunar InRelease Hit:2 http://ports.ubuntu.com/ubuntu-ports lunar-updates InRelease Hit:3 http://ports.ubuntu.com/ubuntu-ports lunar-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports lunar-security InRelease Hit:5 https://deb.nodesource.com/node_18.x lunar InRelease Reading package lists... Pending Updates: 0 *** 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 0.0.0.0:111 0.0.0.0:* LISTEN 0 17467 1/init tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 996 22635 555/systemd-resolve tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 26995 2351/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 27002 2351/iobroker.js-co tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 996 22633 555/systemd-resolve tcp6 0 0 :::111 :::* LISTEN 0 13962 1/init tcp6 0 0 :::22 :::* LISTEN 0 23620 1/init udp 0 0 127.0.0.54:53 0.0.0.0:* 996 22634 555/systemd-resolve udp 0 0 127.0.0.53:53 0.0.0.0:* 996 22632 555/systemd-resolve udp 0 0 192.168.178.54:68 0.0.0.0:* 998 22809 812/systemd-network udp 0 0 0.0.0.0:111 0.0.0.0:* 0 17468 1/init udp6 0 0 :::111 :::* 0 16876 1/init udp6 0 0 fe80::e65f:1ff:fe1b:546 :::* 998 22817 812/systemd-network *** Log File - Last 25 Lines *** 2023-09-27 23:17:33.462 - info: zwave2.0 (2938) Node 2: ready to use 2023-09-27 23:17:33.697 - info: zwave2.0 (2938) Node 2 is alive 2023-09-27 23:17:36.082 - info: zwave2.0 (2938) Node 3: ready to use 2023-09-27 23:17:36.179 - info: vis.0 (3029) Uploaded. 0 2023-09-27 23:17:36.436 - info: zwave2.0 (2938) Node 4: ready to use 2023-09-27 23:17:36.695 - info: vis.0 (3029) Terminated (NO_ERROR): Without reason 2023-09-27 23:17:37.940 - info: zwave2.0 (2938) Node 5: ready to use 2023-09-27 23:17:38.180 - info: zwave2.0 (2938) Node 5 is alive 2023-09-27 23:17:40.108 - info: zwave2.0 (2938) Node 7: ready to use 2023-09-27 23:17:40.256 - info: zwave2.0 (2938) Node 8: ready to use 2023-09-27 23:17:40.402 - info: zwave2.0 (2938) Node 9: ready to use 2023-09-27 23:17:41.185 - info: zwave2.0 (2938) Node 22: ready to use 2023-09-27 23:17:41.886 - info: zwave2.0 (2938) Node 25: ready to use 2023-09-27 23:17:59.738 - info: zwave2.0 (2938) Node 31: ready to use 2023-09-27 23:17:59.860 - info: zwave2.0 (2938) Node 31 is alive 2023-09-27 23:17:59.876 - info: zwave2.0 (2938) Node 32: ready to use 2023-09-27 23:17:59.988 - info: zwave2.0 (2938) Node 32 is alive 2023-09-27 23:18:00.067 - info: zwave2.0 (2938) Node 33: ready to use 2023-09-27 23:18:00.121 - info: zwave2.0 (2938) Node 34: ready to use 2023-09-27 23:18:00.169 - info: zwave2.0 (2938) Node 33 is alive 2023-09-27 23:18:00.183 - info: zwave2.0 (2938) Node 34 is alive 2023-09-27 23:18:00.390 - info: zwave2.0 (2938) Node 35: ready to use 2023-09-27 23:18:00.448 - info: zwave2.0 (2938) Node 35 is alive 2023-09-27 23:18:00.478 - info: zwave2.0 (2938) Node 38: ready to use 2023-09-27 23:18:00.526 - info: zwave2.0 (2938) Node 38 is alive -
iob update iob upgrade all -y iob start admin -
@thomas-braun said in Backitup Restore fehler:
@esmax666 sagte in Backitup Restore fehler:
Meine Gedanken zu dem System, kannst du umsetzen wenn der ioBroker wieder rennt.
Operating System: Ubuntu 23.04
ich wollte ertmals probieren wie es früher war um weniger Problem zu bekommen
Ungünstige Wahl für einen längeren Betrieb. Diese Interimsversionen von ubuntu leben nur 9 Monate. Besser ein Debian/Raspberry OS auf die Kiste werfen.
The systems needs to be REBOOTED!
ich auch gemacht
Keine Deko, das sollte man tun.
Time zone: Europe/Paris (CEST, +0200)
Du sitzt in Frankreich?
JA
[Wed Sep 27 17:28:35 2023] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
Du hast das System nicht sauber heruntergefahren. IMMER tun.
Seltsam ich habe nur gerade heute ubuntu / iobroker installiert ohne das Gerät auszuschalten
*** NodeJS-Installation ***
Nicht falsch, aber nicht aktuell. Stell auf das neue nodesource-Repo um.
wie soll ich das machen ?
npm ERR! invalid: @types/node@12.20.55 /opt/iobroker/node_modules/iobroker.javascript/node_modules/@types/node
Installier iobroker.javascript nochmal drüber.
-
update ist done,
ich glaube da läuft alles wieder richtig, dann mache schnell noch ein backup
Also das wäre noch eventuel zu machen ? Node.js: v18.17.1(18.18.0)
NPM: 9.6.7(9.8.1)
aber wie ?
======== Start marking the full check here =========Skript v.2023-06-20 *** BASE SYSTEM *** Static hostname: ubuntu Icon name: computer Machine ID: 965a81734c8d402ab05ca26017c6e6a9 Boot ID: 0c59d3c9640b486fadab37c9e124b76a Operating System: Ubuntu 23.04 Kernel: Linux 6.2.0-1013-raspi Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 23:43:46 up 35 min, 2 users, load average: 0.05, 0.65, 1.10 CPU threads: 4 Raspberry only: throttled=0x0 Other values than 0x0 hint to temperature/voltage problems temp=53.0'C volt=0.8600V *** Time and Time Zones *** Local time: Wed 2023-09-27 23:43:46 CEST Universal time: Wed 2023-09-27 21:43:46 UTC RTC time: n/a Time zone: Europe/Paris (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** esmax /home/esmax esmax adm dialout cdrom sudo audio video plugdev games users input render netdev gpio spi i2c iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 8.2G 1.3G 5.5G 3.3M 1.8G 6.9G Swap: 0B 0B 0B Total: 8.2G 1.3G 5.5G 7809 M total memory 1195 M used memory 476 M active memory 1755 M inactive memory 5249 M free memory 97 M buffer memory 1576 M swap cache 0 M total swap 0 M used swap 0 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on tmpfs tmpfs 781M 3.1M 778M 1% /run /dev/mmcblk0p2 ext4 59G 5.5G 51G 10% / tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock /dev/mmcblk0p1 vfat 253M 151M 102M 60% /boot/firmware tmpfs tmpfs 781M 4.0K 781M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Sep 27 23:08:16 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbswap=1 smsc95xx.macaddr=E4:5F:01:1B:22:9D vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash [Wed Sep 27 23:08:29 2023] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs [Wed Sep 27 23:08:29 2023] EXT4-fs (mmcblk0p2): mounted filesystem 25a83575-fd50-4dcc-85e0-e3a81c621aa2 with ordered data mode. Quota mode: none. [Wed Sep 27 23:08:31 2023] EXT4-fs (mmcblk0p2): re-mounted 25a83575-fd50-4dcc-85e0-e3a81c621aa2. Quota mode: none. Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,relatime,discard,errors=remount-ro,commit=30 |-/snap/core22/611 /dev/loop0 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/core22/867 /dev/loop1 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/lxd/24646 /dev/loop2 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/lxd/25755 /dev/loop3 squashfs ro,nodev,relatime,errors=continue,threads=single |-/snap/snapd/18600 /dev/loop4 squashfs ro,nodev,relatime,errors=continue,threads=single `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 944M /var/ 677M /var/lib 505M /var/lib/snapd 504M /var/lib/snapd/snaps 222M /var/cache Archived and active journals take up 43.0M in the file system. /opt/iobroker/backups: 7.6M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 229M /opt/iobroker/iobroker-data/ 192M /opt/iobroker/iobroker-data/files 52M /opt/iobroker/iobroker-data/files/javascript.admin 34M /opt/iobroker/iobroker-data/files/javascript.admin/static 33M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.js.map 19M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.2975a411.js.map 18M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js.map 8.3M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.js 8.2M /opt/iobroker/iobroker-data/objects.jsonl *** NodeJS-Installation *** /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x lunar/main arm64 Packages 100 /var/lib/dpkg/status 18.13.0+dfsg1-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/universe arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: 0 *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl No configuration change needed. Multihost discovery server: disabled Discovery authentication: enabled Persistent activation: disabled Objects: jsonl on 127.0.0.1 States: jsonl on 127.0.0.1 Core adapters versions js-controller: 5.0.12 admin: 6.10.1 javascript: 7.1.4 Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : ubuntu - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alexa2.0 : alexa2 : ubuntu - disabled + system.adapter.backitup.0 : backitup : ubuntu - enabled system.adapter.cloud.0 : cloud : ubuntu - disabled system.adapter.discovery.0 : discovery : ubuntu - disabled system.adapter.flot.0 : flot : ubuntu - disabled + system.adapter.heatingcontrol.0 : heatingcontrol : ubuntu - enabled + system.adapter.history.0 : history : ubuntu - enabled system.adapter.ical.0 : ical : ubuntu - enabled system.adapter.info.0 : info : ubuntu - disabled system.adapter.iot.0 : iot : ubuntu - disabled + system.adapter.javascript.0 : javascript : ubuntu - enabled system.adapter.linkeddevices.0 : linkeddevices : ubuntu - disabled system.adapter.mobile.0 : mobile : ubuntu - disabled system.adapter.radar2.0 : radar2 : ubuntu - disabled system.adapter.rpi2.0 : rpi2 : ubuntu - disabled + system.adapter.shuttercontrol.0 : shuttercontrol : ubuntu - enabled system.adapter.socketio.0 : socketio : ubuntu - disabled, port: 8084, bind: 0.0.0.0, run as: admin system.adapter.telegram.0 : telegram : ubuntu - disabled, port: 8443, bind: 0.0.0.0 system.adapter.text2command.0 : text2command : ubuntu - disabled system.adapter.tr-064.0 : tr-064 : ubuntu - disabled system.adapter.vis-colorpicker.0 : vis-colorpicker : ubuntu - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : ubuntu - disabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : ubuntu - disabled system.adapter.vis-metro.0 : vis-metro : ubuntu - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : ubuntu - disabled system.adapter.vis.0 : vis : ubuntu - disabled + system.adapter.web.0 : web : ubuntu - enabled, port: 443, bind: 0.0.0.0, run as: admin + system.adapter.zwave2.0 : zwave2 : ubuntu - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : ubuntu - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : ubuntu - enabled, port: 443, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.10.1 , installed 6.10.1 Adapter "alexa2" : 3.25.2 , installed 3.25.2 Adapter "backitup" : 2.8.1 , installed 2.8.1 Adapter "cloud" : 4.4.1 , installed 4.4.1 Adapter "discovery" : 3.1.0 , installed 3.1.0 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "heatingcontrol": 2.11.1 , installed 2.11.1 Adapter "history" : 2.2.6 , installed 2.2.6 Adapter "ical" : 1.13.3 , installed 1.13.3 Adapter "info" : 1.9.26 , installed 1.9.26 Adapter "iot" : 1.14.5 , installed 1.14.5 Adapter "javascript" : 7.1.4 , installed 7.1.4 Controller "js-controller": 5.0.12 , installed 5.0.12 Adapter "linkeddevices": 1.5.5 , installed 1.5.5 Adapter "mobile" : 1.0.1 , installed 1.0.1 Adapter "radar2" : 2.0.7 , installed 2.0.7 Adapter "rpi2" : 1.3.2 , installed 1.3.2 Adapter "shuttercontrol": 1.6.2 , installed 1.6.2 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.5.5 , installed 6.5.5 Adapter "telegram" : 1.16.0 , installed 1.16.0 Adapter "text2command" : 3.0.2 , installed 3.0.2 Adapter "tr-064" : 4.2.18 , installed 4.2.18 Adapter "vis" : 1.4.16 , installed 1.4.16 Adapter "vis-colorpicker": 2.0.3 , installed 2.0.3 Adapter "vis-hqwidgets": 1.4.0 , installed 1.4.0 Adapter "vis-jqui-mfd" : 1.0.12 , installed 1.0.12 Adapter "vis-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 6.1.2 , installed 6.1.2 Adapter "ws" : 2.5.5 , installed 2.5.5 Adapter "zwave2" : 3.0.5 , installed 3.0.5 Objects and States Please stand by - This may take a while Objects: 4615 States: 3306 *** OS-Repositories and Updates *** Hit:1 http://ports.ubuntu.com/ubuntu-ports lunar InRelease Hit:2 http://ports.ubuntu.com/ubuntu-ports lunar-updates InRelease Hit:3 http://ports.ubuntu.com/ubuntu-ports lunar-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports lunar-security InRelease Hit:5 https://deb.nodesource.com/node_18.x lunar InRelease Reading package lists... Pending Updates: 0 *** 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 0.0.0.0:111 0.0.0.0:* LISTEN 0 17467 1/init tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 996 22635 555/systemd-resolve tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 47592 9892/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 50371 9892/iobroker.js-co tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 996 22633 555/systemd-resolve tcp6 0 0 :::111 :::* LISTEN 0 13962 1/init tcp6 0 0 :::22 :::* LISTEN 0 23620 1/init tcp6 0 0 :::443 :::* LISTEN 1001 47776 10028/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 47619 9910/io.admin.0 udp 0 0 127.0.0.54:53 0.0.0.0:* 996 22634 555/systemd-resolve udp 0 0 127.0.0.53:53 0.0.0.0:* 996 22632 555/systemd-resolve udp 0 0 192.168.178.54:68 0.0.0.0:* 998 22809 812/systemd-network udp 0 0 0.0.0.0:111 0.0.0.0:* 0 17468 1/init udp6 0 0 :::111 :::* 0 16876 1/init udp6 0 0 fe80::e65f:1ff:fe1b:546 :::* 998 22817 812/systemd-network *** Log File - Last 25 Lines *** 2023-09-27 23:38:35.483 - info: zwave2.0 (10049) Node 4: ready to use 2023-09-27 23:38:35.521 - info: zwave2.0 (10049) Node 4 is alive 2023-09-27 23:38:37.047 - info: zwave2.0 (10049) Node 5: ready to use 2023-09-27 23:38:37.108 - info: zwave2.0 (10049) Node 5 is alive 2023-09-27 23:38:38.332 - info: zwave2.0 (10049) Node 22: ready to use 2023-09-27 23:38:38.362 - info: zwave2.0 (10049) Node 22 is alive 2023-09-27 23:38:56.528 - info: admin.0 (9910) ==> Connected system.user.admin from ::ffff:192.168.178.39 2023-09-27 23:38:58.724 - info: zwave2.0 (10049) Node 31: ready to use 2023-09-27 23:38:58.754 - info: zwave2.0 (10049) Node 31 is alive 2023-09-27 23:38:58.817 - info: zwave2.0 (10049) Node 32: ready to use 2023-09-27 23:38:58.865 - info: zwave2.0 (10049) Node 33: ready to use 2023-09-27 23:38:58.936 - info: zwave2.0 (10049) Node 34: ready to use 2023-09-27 23:38:58.970 - info: zwave2.0 (10049) Node 32 is alive 2023-09-27 23:38:58.990 - info: zwave2.0 (10049) Node 33 is alive 2023-09-27 23:38:59.014 - info: zwave2.0 (10049) Node 34 is alive 2023-09-27 23:38:59.204 - info: zwave2.0 (10049) Node 35: ready to use 2023-09-27 23:38:59.263 - info: zwave2.0 (10049) Node 35 is alive 2023-09-27 23:38:59.292 - info: zwave2.0 (10049) Node 38: ready to use 2023-09-27 23:38:59.322 - info: zwave2.0 (10049) Node 38 is alive 2023-09-27 23:40:00.027 - debug: shuttercontrol.0 (10013) calculate astrodata ... 2023-09-27 23:40:00.028 - debug: shuttercontrol.0 (10013) Sun Azimut: 331.9° 2023-09-27 23:40:00.029 - debug: shuttercontrol.0 (10013) Sun Elevation: -38.6° 2023-09-27 23:42:25.827 - debug: zwave2.0 (10049) Node 3: metadata updated: airTemperature 2023-09-27 23:42:25.830 - debug: zwave2.0 (10049) Node 3: value updated: airTemperature => 19.37 2023-09-27 23:43:32.756 - debug: zwave2.0 (10049) Node 32: value updated: value_electric_kwh_consumed => 0.5============ Mark until here for C&P =============
iob diag has finished.
Press any key for a summary
-
@esmax666 sagte in Backitup Restore fehler:
[Wed Sep 27 23:08:29 2023] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
Schon wieder. Ich vermute dann, das deine SD-Karte krümelig ist.
Wenn du ansonsten das System sauber handelst. -
@esmax666 sagte in Backitup Restore fehler:
aber wie ?
Schau in meiner Signatur nach dem node-fix-Skript.
-
@thomas-braun said in Backitup Restore fehler:
krümelig
Sag das nicht lol , ich habe gerade die karte gekauft (SANDISK Elite Extreme)
-
Die Meldung mit den orphans ist jedenfalls nicht normal. Kommt wenn dem System abrupt der Strom genommen wird und/oder bei defektem Datenträger.
-
@thomas-braun sagte in Backitup Restore fehler:
wenn dem System abrupt der Strom genommen wird
@Esmax666 Trenne niemals deinen PI einfach vom Strom. Ein OS muss immer sauber heruntergefahren werden.
-
@esmax666 sagte in Backitup Restore fehler:
Sag das nicht lol , ich habe gerade die karte gekauft (SANDISK Elite Extreme)
Moin,
Mal einfach beschrieben
ein Speichermedium verträgt nur eine gewisse Anzahl an defekten Sektoren/Inodes, da es eine bestimmte Anzahl an Sektoren/Inodes vor dem Benutzen versteckt und somit die Defekten ersetzen kann. Neigt sich dieser Vorrat dem Ende, dann kann man das Speichermedium entsorgen.
Je größer ein Speichermedium, desto mehr Sektoren/Inodes stehen zur Reparatur zur Verfügung.Fehler und ihre Folgen
Aber was viel schlimmer ist, wenn Informationen, die gerade durch, sagen wir mal, der Kernel hat seine Information aus Inode 101, 102,103 geladen und Du killst den Rechner durch Stromlos machen, sodass plötzlich Inode 102 nicht mehr gültig ist, dann kommt es beim nächsten Booten zu einem Kernel Panik und der Rechner startet nicht mehr.
Im besten Fall kann, bei geeignetem Dateisystem, etwas repariert werden, im schlechtesten Fall, totaler Datenverlust.VG
Bernd -
@simatec said in Backitup Restore fehler:
@Esmax666 Trenne niemals deinen PI einfach vom Strom. Ein OS muss immer sauber heruntergefahren werden.
das habe ich auch nicht gemacht ( bin 99% sicher , aber das spät)
