Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Einsteigerfragen
  4. [erledigt] Nach Node.js Updateversuch plötzlich I/O Errors

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    2.0k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    926

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.2k

[erledigt] Nach Node.js Updateversuch plötzlich I/O Errors

Geplant Angeheftet Gesperrt Verschoben Einsteigerfragen
6 Beiträge 2 Kommentatoren 452 Aufrufe 2 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • A Offline
    A Offline
    AlexWest
    schrieb am zuletzt editiert von AlexWest
    #1

    Hallo,

    Ich betreibe seit einiger Zeit eine VM mit IOBroker unter Proxmox. Nun wollte ich vorhin Node.js updaten und dabei ging scheinbar irgendwas gewaltig schief.
    Nun lässt sich der iobroker nicht mehr starten und in der Konsole kriege ich ständig solche Fehler:

    [  533.665586] sd 2:0:0:0: [sda] tag#40 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  533.668333] sd 2:0:0:0: [sda] tag#40 Sense Key : Aborted Command [current] 
    [  533.670327] sd 2:0:0:0: [sda] tag#40 Add. Sense: I/O process terminated
    [  533.672233] sd 2:0:0:0: [sda] tag#40 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  533.674330] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    [  535.753394] sd 2:0:0:0: [sda] tag#42 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  535.756140] sd 2:0:0:0: [sda] tag#42 Sense Key : Aborted Command [current] 
    [  535.758191] sd 2:0:0:0: [sda] tag#42 Add. Sense: I/O process terminated
    [  535.760107] sd 2:0:0:0: [sda] tag#42 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    

    Diese Fehlermeldungen kriege ich auch wenn ich jetzt versuche ein Backup zu erstellen (vor dem Updateversuch habe ich leider keine Backups gemacht; Für diese Fahrlässigkeit/Faulheit könnte ich mich gerade in den Hintern beißen...).

    Könnt ihr mir bitte auf den richtigen Weg helfen um diese Fehler zu beseitigen und doch noch ein Backup zu erstellen? Das wäre super!

    Im Anhang noch der "Diag" Auszug:

    Skript v.2023-10-10
    
    *** BASE SYSTEM ***
       Static hostname: iobrokerVM
             Icon name: computer-vm
               Chassis: vm
        Virtualization: kvm
      Operating System: Debian GNU/Linux 11 (bullseye)
                Kernel: Linux 5.10.0-28-amd64
          Architecture: x86-64
    
    model name      : Common KVM processor
    Docker          : false
    Virtualization  : kvm
    Kernel          : x86_64
    Userland        : amd64
    
    Systemuptime and Load:
     16:46:44 up 7 min,  1 user,  load average: 0.16, 0.15, 0.09
    CPU threads: 4
    
    
    *** Time and Time Zones ***
                   Local time: Mon 2024-04-01 16:46:44 CEST
               Universal time: Mon 2024-04-01 14:46:44 UTC
                     RTC time: Mon 2024-04-01 14:46:45
                    Time zone: Europe/Berlin (CEST, +0200)
    System clock synchronized: yes
                  NTP service: active
              RTC in local TZ: no
    
    *** User and Groups ***
    iobroker
    /home/iobroker
    iobroker tty dialout cdrom floppy audio dip video plugdev netdev bluetooth
    
    *** X-Server-Setup ***
    X-Server:       false
    Desktop: 
    Terminal:       tty
    Boot Target:    graphical.target
    
    *** MEMORY ***
                   total        used        free      shared  buff/cache   available
    Mem:            3.9G         68M        3.5G        0.0K        384M        3.6G
    Swap:           974M          0B        974M
    Total:          4.9G         68M        4.4G
    
             3919 M total memory
               69 M used memory
              258 M active memory
              104 M inactive memory
             3465 M free memory
               49 M buffer memory
              335 M swap cache
              974 M total swap
                0 M used swap
              974 M free swap
    
    *** FAILED SERVICES ***
    
      UNIT            LOAD   ACTIVE SUB    DESCRIPTION
    * miflora.service loaded failed failed Xiaomi Mi Flora Plant Sensor MQTT Client/Daemon
    
    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.
    1 loaded units listed.
    
    *** FILESYSTEM ***
    Filesystem     Type      Size  Used Avail Use% Mounted on
    udev           devtmpfs  1.9G     0  1.9G   0% /dev
    tmpfs          tmpfs     392M  524K  392M   1% /run
    /dev/sda1      ext4       19G  6.1G   12G  35% /
    tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
    tmpfs          tmpfs     5.0M     0  5.0M   0% /run/lock
    tmpfs          tmpfs     392M     0  392M   0% /run/user/0
    
    Messages concerning ext4 filesystem in dmesg:
    [Mon Apr  1 16:38:47 2024] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
    [Mon Apr  1 16:38:48 2024] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
    
    Show mounted filesystems \(real ones only\):
    TARGET SOURCE    FSTYPE OPTIONS
    /      /dev/sda1 ext4   rw,relatime,errors=remount-ro
    
    Files in neuralgic directories:
    
    /var:
    953M    /var/
    483M    /var/cache
    476M    /var/cache/apt
    408M    /var/cache/apt/archives
    322M    /var/log
    
    Hint: You are currently not seeing messages from other users and the system.
          Users in groups 'adm', 'systemd-journal' can see all messages.
          Pass -q to turn off this notice.
    Archived and active journals take up 144.0M in the file system.
    
    /opt/iobroker/backups:
    32M     /opt/iobroker/backups/
    
    /opt/iobroker/iobroker-data:
    1.8G    /opt/iobroker/iobroker-data/
    156M    /opt/iobroker/iobroker-data/files
    57M     /opt/iobroker/iobroker-data/files/javascript.admin
    48M     /opt/iobroker/iobroker-data/files/telegram.admin
    38M     /opt/iobroker/iobroker-data/files/javascript.admin/static
    
    The five largest files in iobroker-data are:
    1.6G    /opt/iobroker/iobroker-data/objects.jsonl
    19M     /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.js.map
    15M     /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js.map
    8.2M    /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.js
    7.2M    /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js
    
    USB-Devices by-id:
    USB-Sticks -  Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id':
    
    /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0
    
    *** NodeJS-Installation ***
    
    /usr/bin/nodejs         v20.12.0
    /usr/bin/node           v20.12.0
    /usr/bin/npm            10.5.0
    /usr/bin/npx            10.5.0
    /usr/bin/corepack       0.25.2
    
    
    nodejs:
      Installed: 20.12.0-1nodesource1
      Candidate: 20.12.0-1nodesource1
      Version table:
     *** 20.12.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
            100 /var/lib/dpkg/status
         20.11.1-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.11.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.10.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.9.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.8.1-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.8.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.7.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.6.1-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.6.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.5.1-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.5.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.4.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.3.1-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.3.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.2.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.1.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         20.0.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
         12.22.12~dfsg-1~deb11u4 500
            500 http://deb.debian.org/debian bullseye/main amd64 Packages
            500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
    
    Temp directories causing npm8 problem: 0
    No problems detected
    
    Errors in npm tree:
    
    *** ioBroker-Installation ***
    
    ioBroker Status
    [  496.674272] sd 2:0:0:0: [sda] tag#37 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  496.677223] sd 2:0:0:0: [sda] tag#37 Sense Key : Aborted Command [current] 
    [  496.679241] sd 2:0:0:0: [sda] tag#37 Add. Sense: I/O process terminated
    [  496.681165] sd 2:0:0:0: [sda] tag#37 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  496.683405] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    [  498.786020] sd 2:0:0:0: [sda] tag#38 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  498.788965] sd 2:0:0:0: [sda] tag#38 Sense Key : Aborted Command [current] 
    [  498.791246] sd 2:0:0:0: [sda] tag#38 Add. Sense: I/O process terminated
    [  498.793298] sd 2:0:0:0: [sda] tag#38 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  498.795705] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    node:events:496
          throw er; // Unhandled 'error' event
          ^
    
    Error: EIO: i/o error, read
    Emitted 'error' event on Interface instance at:
        at ReadStream.onerror (node:internal/readline/interface:239:10)
        at ReadStream.emit (node:events:518:28)
        at emitErrorNT (node:internal/streams/destroy:169:8)
        at errorOrDestroy (node:internal/streams/destroy:238:7)
        at node:internal/fs/streams:272:9
        at FSReqCallback.wrapper [as oncomplete] (node:fs:687:5) {
      errno: -5,
      code: 'EIO',
      syscall: 'read'
    }
    
    Node.js v20.12.0
    
    Core adapters versions
    js-controller:  4.0.23
    admin:          6.13.16
    javascript:     7.8.0
    
    Adapters from github:   0
    
    Adapter State
    [  517.829925] sd 2:0:0:0: [sda] tag#81 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  517.832530] sd 2:0:0:0: [sda] tag#81 Sense Key : Aborted Command [current] 
    [  517.834516] sd 2:0:0:0: [sda] tag#81 Add. Sense: I/O process terminated
    [  517.836470] sd 2:0:0:0: [sda] tag#81 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  517.838551] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    [  519.934728] sd 2:0:0:0: [sda] tag#39 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  519.937443] sd 2:0:0:0: [sda] tag#39 Sense Key : Aborted Command [current] 
    [  519.939535] sd 2:0:0:0: [sda] tag#39 Add. Sense: I/O process terminated
    [  519.941450] sd 2:0:0:0: [sda] tag#39 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  519.943542] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    node:events:496
          throw er; // Unhandled 'error' event
          ^
    
    Error: EIO: i/o error, read
    Emitted 'error' event on Interface instance at:
        at ReadStream.onerror (node:internal/readline/interface:239:10)
        at ReadStream.emit (node:events:518:28)
        at emitErrorNT (node:internal/streams/destroy:169:8)
        at errorOrDestroy (node:internal/streams/destroy:238:7)
        at node:internal/fs/streams:272:9
        at FSReqCallback.wrapper [as oncomplete] (node:fs:687:5) {
      errno: -5,
      code: 'EIO',
      syscall: 'read'
    }
    
    Node.js v20.12.0
    
    Enabled adapters with bindings
    [  533.665586] sd 2:0:0:0: [sda] tag#40 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  533.668333] sd 2:0:0:0: [sda] tag#40 Sense Key : Aborted Command [current] 
    [  533.670327] sd 2:0:0:0: [sda] tag#40 Add. Sense: I/O process terminated
    [  533.672233] sd 2:0:0:0: [sda] tag#40 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  533.674330] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    [  535.753394] sd 2:0:0:0: [sda] tag#42 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  535.756140] sd 2:0:0:0: [sda] tag#42 Sense Key : Aborted Command [current] 
    [  535.758191] sd 2:0:0:0: [sda] tag#42 Add. Sense: I/O process terminated
    [  535.760107] sd 2:0:0:0: [sda] tag#42 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  535.762209] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    node:events:496
          throw er; // Unhandled 'error' event
          ^
    
    Error: EIO: i/o error, read
    Emitted 'error' event on Interface instance at:
        at ReadStream.onerror (node:internal/readline/interface:239:10)
        at ReadStream.emit (node:events:518:28)
        at emitErrorNT (node:internal/streams/destroy:169:8)
        at errorOrDestroy (node:internal/streams/destroy:238:7)
        at node:internal/fs/streams:272:9
        at FSReqCallback.wrapper [as oncomplete] (node:fs:687:5) {
      errno: -5,
      code: 'EIO',
      syscall: 'read'
    }
    
    Node.js v20.12.0
    
    ioBroker-Repositories
    [  549.473313] sd 2:0:0:0: [sda] tag#47 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  549.475982] sd 2:0:0:0: [sda] tag#47 Sense Key : Aborted Command [current] 
    [  549.478009] sd 2:0:0:0: [sda] tag#47 Add. Sense: I/O process terminated
    [  549.479920] sd 2:0:0:0: [sda] tag#47 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  549.482026] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    [  551.568982] sd 2:0:0:0: [sda] tag#48 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  551.571705] sd 2:0:0:0: [sda] tag#48 Sense Key : Aborted Command [current] 
    [  551.573750] sd 2:0:0:0: [sda] tag#48 Add. Sense: I/O process terminated
    [  551.575689] sd 2:0:0:0: [sda] tag#48 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  551.577798] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    node:events:496
          throw er; // Unhandled 'error' event
          ^
    
    Error: EIO: i/o error, read
    Emitted 'error' event on Interface instance at:
        at ReadStream.onerror (node:internal/readline/interface:239:10)
        at ReadStream.emit (node:events:518:28)
        at emitErrorNT (node:internal/streams/destroy:169:8)
        at errorOrDestroy (node:internal/streams/destroy:238:7)
        at node:internal/fs/streams:272:9
        at FSReqCallback.wrapper [as oncomplete] (node:fs:687:5) {
      errno: -5,
      code: 'EIO',
      syscall: 'read'
    }
    
    Node.js v20.12.0
    
    Installed ioBroker-Instances
    [  565.290235] sd 2:0:0:0: [sda] tag#61 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  565.292874] sd 2:0:0:0: [sda] tag#61 Sense Key : Aborted Command [current] 
    [  565.294859] sd 2:0:0:0: [sda] tag#61 Add. Sense: I/O process terminated
    [  565.296764] sd 2:0:0:0: [sda] tag#61 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  565.298882] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    [  567.388434] sd 2:0:0:0: [sda] tag#50 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  567.391259] sd 2:0:0:0: [sda] tag#50 Sense Key : Aborted Command [current] 
    [  567.393380] sd 2:0:0:0: [sda] tag#50 Add. Sense: I/O process terminated
    [  567.395330] sd 2:0:0:0: [sda] tag#50 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  567.397445] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    node:events:496
          throw er; // Unhandled 'error' event
          ^
    
    Error: EIO: i/o error, read
    Emitted 'error' event on Interface instance at:
        at ReadStream.onerror (node:internal/readline/interface:239:10)
        at ReadStream.emit (node:events:518:28)
        at emitErrorNT (node:internal/streams/destroy:169:8)
        at errorOrDestroy (node:internal/streams/destroy:238:7)
        at node:internal/fs/streams:272:9
        at FSReqCallback.wrapper [as oncomplete] (node:fs:687:5) {
      errno: -5,
      code: 'EIO',
      syscall: 'read'
    }
    
    Node.js v20.12.0
    
    Objects and States
    Please stand by - This may take a while
    [  581.141984] sd 2:0:0:0: [sda] tag#55 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  581.144691] sd 2:0:0:0: [sda] tag#55 Sense Key : Aborted Command [current] 
    [  581.147015] sd 2:0:0:0: [sda] tag#55 Add. Sense: I/O process terminated
    [  581.149208] sd 2:0:0:0: [sda] tag#55 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  581.151579] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    [  583.215653] sd 2:0:0:0: [sda] tag#56 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  583.218329] sd 2:0:0:0: [sda] tag#56 Sense Key : Aborted Command [current] 
    [  583.220358] sd 2:0:0:0: [sda] tag#56 Add. Sense: I/O process terminated
    [  583.222327] sd 2:0:0:0: [sda] tag#56 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  583.224438] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    Objects:        0
    [  596.969737] sd 2:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  596.972442] sd 2:0:0:0: [sda] tag#6 Sense Key : Aborted Command [current] 
    [  596.974573] sd 2:0:0:0: [sda] tag#6 Add. Sense: I/O process terminated
    [  596.976731] sd 2:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  596.979126] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    [  599.072349] sd 2:0:0:0: [sda] tag#106 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
    [  599.075447] sd 2:0:0:0: [sda] tag#106 Sense Key : Aborted Command [current] 
    [  599.077630] sd 2:0:0:0: [sda] tag#106 Add. Sense: I/O process terminated
    [  599.079863] sd 2:0:0:0: [sda] tag#106 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
    [  599.082251] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    States:         0
    
    *** OS-Repositories and Updates ***
    Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
    Hit:2 http://deb.debian.org/debian bullseye InRelease
    Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
    Hit:4 https://deb.nodesource.com/node_20.x nodistro 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          11914      1/init              
    tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          13138      464/sshd: /usr/sbin 
    tcp6       0      0 :::111                  :::*                    LISTEN      0          11918      1/init              
    tcp6       0      0 :::22                   :::*                    LISTEN      0          13140      464/sshd: /usr/sbin 
    udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          13013      384/dhclient        
    udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          11915      1/init              
    udp6       0      0 :::111                  :::*                                0          11921      1/init              
    
    *** Log File - Last 25 Lines ***
    
    2024-04-01 16:39:32.527  - info: host.iobrokerVM ip addresses: 192.168.178.40 2a02:810d:340:5ad8:cf5:fdff:fe1c:2975 fe80::cf5:fdff:fe1c:2975
    2024-04-01 16:39:37.859  - error: host.iobrokerVM uncaught exception: EIO: i/o error, read
    2024-04-01 16:39:37.860  - error: host.iobrokerVM Error: EIO: i/o error, read
    2024-04-01 16:39:37.866  - info: host.iobrokerVM terminated. Could not reset alive status for instances
    2024-04-01 16:39:42.343  - info: host.iobrokerVM iobroker.js-controller version 4.0.23 js-controller starting
    2024-04-01 16:39:42.345  - info: host.iobrokerVM Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
    2024-04-01 16:39:42.345  - info: host.iobrokerVM hostname: iobrokerVM, node: v20.12.0
    2024-04-01 16:39:42.345  - info: host.iobrokerVM ip addresses: 192.168.178.40 2a02:810d:340:5ad8:cf5:fdff:fe1c:2975 fe80::cf5:fdff:fe1c:2975
    2024-04-01 16:39:47.712  - error: host.iobrokerVM uncaught exception: EIO: i/o error, read
    2024-04-01 16:39:47.713  - error: host.iobrokerVM Error: EIO: i/o error, read
    2024-04-01 16:39:47.716  - info: host.iobrokerVM terminated. Could not reset alive status for instances
    2024-04-01 16:39:52.338  - info: host.iobrokerVM iobroker.js-controller version 4.0.23 js-controller starting
    2024-04-01 16:39:52.340  - info: host.iobrokerVM Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
    2024-04-01 16:39:52.340  - info: host.iobrokerVM hostname: iobrokerVM, node: v20.12.0
    2024-04-01 16:39:52.340  - info: host.iobrokerVM ip addresses: 192.168.178.40 2a02:810d:340:5ad8:cf5:fdff:fe1c:2975 fe80::cf5:fdff:fe1c:2975
    2024-04-01 16:39:57.724  - error: host.iobrokerVM uncaught exception: EIO: i/o error, read
    2024-04-01 16:39:57.725  - error: host.iobrokerVM Error: EIO: i/o error, read
    2024-04-01 16:39:57.728  - info: host.iobrokerVM terminated. Could not reset alive status for instances
    2024-04-01 16:40:02.335  - info: host.iobrokerVM iobroker.js-controller version 4.0.23 js-controller starting
    2024-04-01 16:40:02.338  - info: host.iobrokerVM Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
    2024-04-01 16:40:02.338  - info: host.iobrokerVM hostname: iobrokerVM, node: v20.12.0
    2024-04-01 16:40:02.338  - info: host.iobrokerVM ip addresses: 192.168.178.40 2a02:810d:340:5ad8:cf5:fdff:fe1c:2975 fe80::cf5:fdff:fe1c:2975
    2024-04-01 16:40:07.768  - error: host.iobrokerVM uncaught exception: EIO: i/o error, read
    2024-04-01 16:40:07.769  - error: host.iobrokerVM Error: EIO: i/o error, read
    2024-04-01 16:40:07.772  - info: host.iobrokerVM terminated. Could not reset alive status for instances
    
    

    Ich bedanke mich im Voraus für eure Hilfe und wünsche euch noch einen schönen Feiertag!
    Mfg,
    Alex

    Thomas BraunT 1 Antwort Letzte Antwort
    0
    • A AlexWest

      Hallo,

      Ich betreibe seit einiger Zeit eine VM mit IOBroker unter Proxmox. Nun wollte ich vorhin Node.js updaten und dabei ging scheinbar irgendwas gewaltig schief.
      Nun lässt sich der iobroker nicht mehr starten und in der Konsole kriege ich ständig solche Fehler:

      [  533.665586] sd 2:0:0:0: [sda] tag#40 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  533.668333] sd 2:0:0:0: [sda] tag#40 Sense Key : Aborted Command [current] 
      [  533.670327] sd 2:0:0:0: [sda] tag#40 Add. Sense: I/O process terminated
      [  533.672233] sd 2:0:0:0: [sda] tag#40 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  533.674330] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      [  535.753394] sd 2:0:0:0: [sda] tag#42 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  535.756140] sd 2:0:0:0: [sda] tag#42 Sense Key : Aborted Command [current] 
      [  535.758191] sd 2:0:0:0: [sda] tag#42 Add. Sense: I/O process terminated
      [  535.760107] sd 2:0:0:0: [sda] tag#42 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      

      Diese Fehlermeldungen kriege ich auch wenn ich jetzt versuche ein Backup zu erstellen (vor dem Updateversuch habe ich leider keine Backups gemacht; Für diese Fahrlässigkeit/Faulheit könnte ich mich gerade in den Hintern beißen...).

      Könnt ihr mir bitte auf den richtigen Weg helfen um diese Fehler zu beseitigen und doch noch ein Backup zu erstellen? Das wäre super!

      Im Anhang noch der "Diag" Auszug:

      Skript v.2023-10-10
      
      *** BASE SYSTEM ***
         Static hostname: iobrokerVM
               Icon name: computer-vm
                 Chassis: vm
          Virtualization: kvm
        Operating System: Debian GNU/Linux 11 (bullseye)
                  Kernel: Linux 5.10.0-28-amd64
            Architecture: x86-64
      
      model name      : Common KVM processor
      Docker          : false
      Virtualization  : kvm
      Kernel          : x86_64
      Userland        : amd64
      
      Systemuptime and Load:
       16:46:44 up 7 min,  1 user,  load average: 0.16, 0.15, 0.09
      CPU threads: 4
      
      
      *** Time and Time Zones ***
                     Local time: Mon 2024-04-01 16:46:44 CEST
                 Universal time: Mon 2024-04-01 14:46:44 UTC
                       RTC time: Mon 2024-04-01 14:46:45
                      Time zone: Europe/Berlin (CEST, +0200)
      System clock synchronized: yes
                    NTP service: active
                RTC in local TZ: no
      
      *** User and Groups ***
      iobroker
      /home/iobroker
      iobroker tty dialout cdrom floppy audio dip video plugdev netdev bluetooth
      
      *** X-Server-Setup ***
      X-Server:       false
      Desktop: 
      Terminal:       tty
      Boot Target:    graphical.target
      
      *** MEMORY ***
                     total        used        free      shared  buff/cache   available
      Mem:            3.9G         68M        3.5G        0.0K        384M        3.6G
      Swap:           974M          0B        974M
      Total:          4.9G         68M        4.4G
      
               3919 M total memory
                 69 M used memory
                258 M active memory
                104 M inactive memory
               3465 M free memory
                 49 M buffer memory
                335 M swap cache
                974 M total swap
                  0 M used swap
                974 M free swap
      
      *** FAILED SERVICES ***
      
        UNIT            LOAD   ACTIVE SUB    DESCRIPTION
      * miflora.service loaded failed failed Xiaomi Mi Flora Plant Sensor MQTT Client/Daemon
      
      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.
      1 loaded units listed.
      
      *** FILESYSTEM ***
      Filesystem     Type      Size  Used Avail Use% Mounted on
      udev           devtmpfs  1.9G     0  1.9G   0% /dev
      tmpfs          tmpfs     392M  524K  392M   1% /run
      /dev/sda1      ext4       19G  6.1G   12G  35% /
      tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
      tmpfs          tmpfs     5.0M     0  5.0M   0% /run/lock
      tmpfs          tmpfs     392M     0  392M   0% /run/user/0
      
      Messages concerning ext4 filesystem in dmesg:
      [Mon Apr  1 16:38:47 2024] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
      [Mon Apr  1 16:38:48 2024] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
      
      Show mounted filesystems \(real ones only\):
      TARGET SOURCE    FSTYPE OPTIONS
      /      /dev/sda1 ext4   rw,relatime,errors=remount-ro
      
      Files in neuralgic directories:
      
      /var:
      953M    /var/
      483M    /var/cache
      476M    /var/cache/apt
      408M    /var/cache/apt/archives
      322M    /var/log
      
      Hint: You are currently not seeing messages from other users and the system.
            Users in groups 'adm', 'systemd-journal' can see all messages.
            Pass -q to turn off this notice.
      Archived and active journals take up 144.0M in the file system.
      
      /opt/iobroker/backups:
      32M     /opt/iobroker/backups/
      
      /opt/iobroker/iobroker-data:
      1.8G    /opt/iobroker/iobroker-data/
      156M    /opt/iobroker/iobroker-data/files
      57M     /opt/iobroker/iobroker-data/files/javascript.admin
      48M     /opt/iobroker/iobroker-data/files/telegram.admin
      38M     /opt/iobroker/iobroker-data/files/javascript.admin/static
      
      The five largest files in iobroker-data are:
      1.6G    /opt/iobroker/iobroker-data/objects.jsonl
      19M     /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.js.map
      15M     /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js.map
      8.2M    /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.js
      7.2M    /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js
      
      USB-Devices by-id:
      USB-Sticks -  Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id':
      
      /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0
      
      *** NodeJS-Installation ***
      
      /usr/bin/nodejs         v20.12.0
      /usr/bin/node           v20.12.0
      /usr/bin/npm            10.5.0
      /usr/bin/npx            10.5.0
      /usr/bin/corepack       0.25.2
      
      
      nodejs:
        Installed: 20.12.0-1nodesource1
        Candidate: 20.12.0-1nodesource1
        Version table:
       *** 20.12.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
              100 /var/lib/dpkg/status
           20.11.1-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.11.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.10.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.9.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.8.1-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.8.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.7.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.6.1-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.6.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.5.1-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.5.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.4.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.3.1-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.3.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.2.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.1.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.0.0-1nodesource1 600
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           12.22.12~dfsg-1~deb11u4 500
              500 http://deb.debian.org/debian bullseye/main amd64 Packages
              500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
      
      Temp directories causing npm8 problem: 0
      No problems detected
      
      Errors in npm tree:
      
      *** ioBroker-Installation ***
      
      ioBroker Status
      [  496.674272] sd 2:0:0:0: [sda] tag#37 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  496.677223] sd 2:0:0:0: [sda] tag#37 Sense Key : Aborted Command [current] 
      [  496.679241] sd 2:0:0:0: [sda] tag#37 Add. Sense: I/O process terminated
      [  496.681165] sd 2:0:0:0: [sda] tag#37 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  496.683405] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      [  498.786020] sd 2:0:0:0: [sda] tag#38 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  498.788965] sd 2:0:0:0: [sda] tag#38 Sense Key : Aborted Command [current] 
      [  498.791246] sd 2:0:0:0: [sda] tag#38 Add. Sense: I/O process terminated
      [  498.793298] sd 2:0:0:0: [sda] tag#38 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  498.795705] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      node:events:496
            throw er; // Unhandled 'error' event
            ^
      
      Error: EIO: i/o error, read
      Emitted 'error' event on Interface instance at:
          at ReadStream.onerror (node:internal/readline/interface:239:10)
          at ReadStream.emit (node:events:518:28)
          at emitErrorNT (node:internal/streams/destroy:169:8)
          at errorOrDestroy (node:internal/streams/destroy:238:7)
          at node:internal/fs/streams:272:9
          at FSReqCallback.wrapper [as oncomplete] (node:fs:687:5) {
        errno: -5,
        code: 'EIO',
        syscall: 'read'
      }
      
      Node.js v20.12.0
      
      Core adapters versions
      js-controller:  4.0.23
      admin:          6.13.16
      javascript:     7.8.0
      
      Adapters from github:   0
      
      Adapter State
      [  517.829925] sd 2:0:0:0: [sda] tag#81 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  517.832530] sd 2:0:0:0: [sda] tag#81 Sense Key : Aborted Command [current] 
      [  517.834516] sd 2:0:0:0: [sda] tag#81 Add. Sense: I/O process terminated
      [  517.836470] sd 2:0:0:0: [sda] tag#81 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  517.838551] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      [  519.934728] sd 2:0:0:0: [sda] tag#39 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  519.937443] sd 2:0:0:0: [sda] tag#39 Sense Key : Aborted Command [current] 
      [  519.939535] sd 2:0:0:0: [sda] tag#39 Add. Sense: I/O process terminated
      [  519.941450] sd 2:0:0:0: [sda] tag#39 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  519.943542] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      node:events:496
            throw er; // Unhandled 'error' event
            ^
      
      Error: EIO: i/o error, read
      Emitted 'error' event on Interface instance at:
          at ReadStream.onerror (node:internal/readline/interface:239:10)
          at ReadStream.emit (node:events:518:28)
          at emitErrorNT (node:internal/streams/destroy:169:8)
          at errorOrDestroy (node:internal/streams/destroy:238:7)
          at node:internal/fs/streams:272:9
          at FSReqCallback.wrapper [as oncomplete] (node:fs:687:5) {
        errno: -5,
        code: 'EIO',
        syscall: 'read'
      }
      
      Node.js v20.12.0
      
      Enabled adapters with bindings
      [  533.665586] sd 2:0:0:0: [sda] tag#40 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  533.668333] sd 2:0:0:0: [sda] tag#40 Sense Key : Aborted Command [current] 
      [  533.670327] sd 2:0:0:0: [sda] tag#40 Add. Sense: I/O process terminated
      [  533.672233] sd 2:0:0:0: [sda] tag#40 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  533.674330] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      [  535.753394] sd 2:0:0:0: [sda] tag#42 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  535.756140] sd 2:0:0:0: [sda] tag#42 Sense Key : Aborted Command [current] 
      [  535.758191] sd 2:0:0:0: [sda] tag#42 Add. Sense: I/O process terminated
      [  535.760107] sd 2:0:0:0: [sda] tag#42 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  535.762209] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      node:events:496
            throw er; // Unhandled 'error' event
            ^
      
      Error: EIO: i/o error, read
      Emitted 'error' event on Interface instance at:
          at ReadStream.onerror (node:internal/readline/interface:239:10)
          at ReadStream.emit (node:events:518:28)
          at emitErrorNT (node:internal/streams/destroy:169:8)
          at errorOrDestroy (node:internal/streams/destroy:238:7)
          at node:internal/fs/streams:272:9
          at FSReqCallback.wrapper [as oncomplete] (node:fs:687:5) {
        errno: -5,
        code: 'EIO',
        syscall: 'read'
      }
      
      Node.js v20.12.0
      
      ioBroker-Repositories
      [  549.473313] sd 2:0:0:0: [sda] tag#47 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  549.475982] sd 2:0:0:0: [sda] tag#47 Sense Key : Aborted Command [current] 
      [  549.478009] sd 2:0:0:0: [sda] tag#47 Add. Sense: I/O process terminated
      [  549.479920] sd 2:0:0:0: [sda] tag#47 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  549.482026] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      [  551.568982] sd 2:0:0:0: [sda] tag#48 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  551.571705] sd 2:0:0:0: [sda] tag#48 Sense Key : Aborted Command [current] 
      [  551.573750] sd 2:0:0:0: [sda] tag#48 Add. Sense: I/O process terminated
      [  551.575689] sd 2:0:0:0: [sda] tag#48 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  551.577798] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      node:events:496
            throw er; // Unhandled 'error' event
            ^
      
      Error: EIO: i/o error, read
      Emitted 'error' event on Interface instance at:
          at ReadStream.onerror (node:internal/readline/interface:239:10)
          at ReadStream.emit (node:events:518:28)
          at emitErrorNT (node:internal/streams/destroy:169:8)
          at errorOrDestroy (node:internal/streams/destroy:238:7)
          at node:internal/fs/streams:272:9
          at FSReqCallback.wrapper [as oncomplete] (node:fs:687:5) {
        errno: -5,
        code: 'EIO',
        syscall: 'read'
      }
      
      Node.js v20.12.0
      
      Installed ioBroker-Instances
      [  565.290235] sd 2:0:0:0: [sda] tag#61 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  565.292874] sd 2:0:0:0: [sda] tag#61 Sense Key : Aborted Command [current] 
      [  565.294859] sd 2:0:0:0: [sda] tag#61 Add. Sense: I/O process terminated
      [  565.296764] sd 2:0:0:0: [sda] tag#61 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  565.298882] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      [  567.388434] sd 2:0:0:0: [sda] tag#50 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  567.391259] sd 2:0:0:0: [sda] tag#50 Sense Key : Aborted Command [current] 
      [  567.393380] sd 2:0:0:0: [sda] tag#50 Add. Sense: I/O process terminated
      [  567.395330] sd 2:0:0:0: [sda] tag#50 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  567.397445] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      node:events:496
            throw er; // Unhandled 'error' event
            ^
      
      Error: EIO: i/o error, read
      Emitted 'error' event on Interface instance at:
          at ReadStream.onerror (node:internal/readline/interface:239:10)
          at ReadStream.emit (node:events:518:28)
          at emitErrorNT (node:internal/streams/destroy:169:8)
          at errorOrDestroy (node:internal/streams/destroy:238:7)
          at node:internal/fs/streams:272:9
          at FSReqCallback.wrapper [as oncomplete] (node:fs:687:5) {
        errno: -5,
        code: 'EIO',
        syscall: 'read'
      }
      
      Node.js v20.12.0
      
      Objects and States
      Please stand by - This may take a while
      [  581.141984] sd 2:0:0:0: [sda] tag#55 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  581.144691] sd 2:0:0:0: [sda] tag#55 Sense Key : Aborted Command [current] 
      [  581.147015] sd 2:0:0:0: [sda] tag#55 Add. Sense: I/O process terminated
      [  581.149208] sd 2:0:0:0: [sda] tag#55 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  581.151579] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      [  583.215653] sd 2:0:0:0: [sda] tag#56 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  583.218329] sd 2:0:0:0: [sda] tag#56 Sense Key : Aborted Command [current] 
      [  583.220358] sd 2:0:0:0: [sda] tag#56 Add. Sense: I/O process terminated
      [  583.222327] sd 2:0:0:0: [sda] tag#56 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  583.224438] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      Objects:        0
      [  596.969737] sd 2:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  596.972442] sd 2:0:0:0: [sda] tag#6 Sense Key : Aborted Command [current] 
      [  596.974573] sd 2:0:0:0: [sda] tag#6 Add. Sense: I/O process terminated
      [  596.976731] sd 2:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  596.979126] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      [  599.072349] sd 2:0:0:0: [sda] tag#106 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
      [  599.075447] sd 2:0:0:0: [sda] tag#106 Sense Key : Aborted Command [current] 
      [  599.077630] sd 2:0:0:0: [sda] tag#106 Add. Sense: I/O process terminated
      [  599.079863] sd 2:0:0:0: [sda] tag#106 CDB: Read(10) 28 00 00 62 7a c0 00 00 08 00
      [  599.082251] blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
      States:         0
      
      *** OS-Repositories and Updates ***
      Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
      Hit:2 http://deb.debian.org/debian bullseye InRelease
      Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
      Hit:4 https://deb.nodesource.com/node_20.x nodistro 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          11914      1/init              
      tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          13138      464/sshd: /usr/sbin 
      tcp6       0      0 :::111                  :::*                    LISTEN      0          11918      1/init              
      tcp6       0      0 :::22                   :::*                    LISTEN      0          13140      464/sshd: /usr/sbin 
      udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          13013      384/dhclient        
      udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          11915      1/init              
      udp6       0      0 :::111                  :::*                                0          11921      1/init              
      
      *** Log File - Last 25 Lines ***
      
      2024-04-01 16:39:32.527  - info: host.iobrokerVM ip addresses: 192.168.178.40 2a02:810d:340:5ad8:cf5:fdff:fe1c:2975 fe80::cf5:fdff:fe1c:2975
      2024-04-01 16:39:37.859  - error: host.iobrokerVM uncaught exception: EIO: i/o error, read
      2024-04-01 16:39:37.860  - error: host.iobrokerVM Error: EIO: i/o error, read
      2024-04-01 16:39:37.866  - info: host.iobrokerVM terminated. Could not reset alive status for instances
      2024-04-01 16:39:42.343  - info: host.iobrokerVM iobroker.js-controller version 4.0.23 js-controller starting
      2024-04-01 16:39:42.345  - info: host.iobrokerVM Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
      2024-04-01 16:39:42.345  - info: host.iobrokerVM hostname: iobrokerVM, node: v20.12.0
      2024-04-01 16:39:42.345  - info: host.iobrokerVM ip addresses: 192.168.178.40 2a02:810d:340:5ad8:cf5:fdff:fe1c:2975 fe80::cf5:fdff:fe1c:2975
      2024-04-01 16:39:47.712  - error: host.iobrokerVM uncaught exception: EIO: i/o error, read
      2024-04-01 16:39:47.713  - error: host.iobrokerVM Error: EIO: i/o error, read
      2024-04-01 16:39:47.716  - info: host.iobrokerVM terminated. Could not reset alive status for instances
      2024-04-01 16:39:52.338  - info: host.iobrokerVM iobroker.js-controller version 4.0.23 js-controller starting
      2024-04-01 16:39:52.340  - info: host.iobrokerVM Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
      2024-04-01 16:39:52.340  - info: host.iobrokerVM hostname: iobrokerVM, node: v20.12.0
      2024-04-01 16:39:52.340  - info: host.iobrokerVM ip addresses: 192.168.178.40 2a02:810d:340:5ad8:cf5:fdff:fe1c:2975 fe80::cf5:fdff:fe1c:2975
      2024-04-01 16:39:57.724  - error: host.iobrokerVM uncaught exception: EIO: i/o error, read
      2024-04-01 16:39:57.725  - error: host.iobrokerVM Error: EIO: i/o error, read
      2024-04-01 16:39:57.728  - info: host.iobrokerVM terminated. Could not reset alive status for instances
      2024-04-01 16:40:02.335  - info: host.iobrokerVM iobroker.js-controller version 4.0.23 js-controller starting
      2024-04-01 16:40:02.338  - info: host.iobrokerVM Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
      2024-04-01 16:40:02.338  - info: host.iobrokerVM hostname: iobrokerVM, node: v20.12.0
      2024-04-01 16:40:02.338  - info: host.iobrokerVM ip addresses: 192.168.178.40 2a02:810d:340:5ad8:cf5:fdff:fe1c:2975 fe80::cf5:fdff:fe1c:2975
      2024-04-01 16:40:07.768  - error: host.iobrokerVM uncaught exception: EIO: i/o error, read
      2024-04-01 16:40:07.769  - error: host.iobrokerVM Error: EIO: i/o error, read
      2024-04-01 16:40:07.772  - info: host.iobrokerVM terminated. Could not reset alive status for instances
      
      

      Ich bedanke mich im Voraus für eure Hilfe und wünsche euch noch einen schönen Feiertag!
      Mfg,
      Alex

      Thomas BraunT Online
      Thomas BraunT Online
      Thomas Braun
      Most Active
      schrieb am zuletzt editiert von
      #2

      @alexwest sagte in Nach Node.js Updateversuch plötzlich I/O Errors:

      blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

      Das deutet für mich auf Trouble mit dem Datenträger hin. Da ist ein Sektor kaputt.
      Im übrigen ist dein nodejs@20 nicht die derzeitig empfohlene Version...

      iob nodejs-update 18
      

      liefert?

      Linux-Werkzeugkasten:
      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
      NodeJS Fixer Skript:
      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

      A 1 Antwort Letzte Antwort
      1
      • Thomas BraunT Thomas Braun

        @alexwest sagte in Nach Node.js Updateversuch plötzlich I/O Errors:

        blk_update_request: I/O error, dev sda, sector 6453952 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

        Das deutet für mich auf Trouble mit dem Datenträger hin. Da ist ein Sektor kaputt.
        Im übrigen ist dein nodejs@20 nicht die derzeitig empfohlene Version...

        iob nodejs-update 18
        

        liefert?

        A Offline
        A Offline
        AlexWest
        schrieb am zuletzt editiert von
        #3

        @thomas-braun Danke für den Hinweis! Das Nodeupdate hat erfolgreich funktioniert.

        ioBroker nodejs updater 2023-10-13
        You requested to intall latest version from nodejs v18 tree.
        
        Your current setup is:
        /usr/bin/nodejs         v20.12.0
        /usr/bin/node           v20.12.0
        /usr/bin/npm            10.5.0
        /usr/bin/npx            10.5.0
        /usr/bin/corepack       0.25.2
        
        We found these nodejs versions available for installation:
        
        nodejs:
          Installed: 20.12.0-1nodesource1
          Candidate: 20.12.0-1nodesource1
          Version table:
         *** 20.12.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
                100 /var/lib/dpkg/status
             20.11.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.11.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.10.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.9.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.8.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.8.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.7.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.6.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.6.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.5.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.5.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.4.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.3.1-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.3.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.2.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.1.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             20.0.0-1nodesource1 600
                500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
             12.22.12~dfsg-1~deb11u4 500
                500 http://deb.debian.org/debian bullseye/main amd64 Packages
                500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
        
        
        
        Nothing to do - Your installation is using the correct paths.
        
        You are running nodejs v20.12.0. Do you want to install latest version from nodejs v.18 tree? 
        
        Press <y> to continue or any other key to quit
        Trying to update your installation now. Please be patient.
        
        Virtualization: kvm
        Waiting for ioBroker to shut down - Give me a minute...
        ############################################################
        
        *** These repos are active on your system:
        Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
        Hit:2 http://deb.debian.org/debian bullseye InRelease
        Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
        Fetched 44.1 kB in 0s (108 kB/s)    
        Reading package lists... Done
        
        *** Installing ca-certificates, curl and gnupg, just in case they are missing.
        
        *** Creating new /etc/apt/sources.list.d/nodesource.list and pinning source
        
        deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main
        Package: nodejs
        Pin: origin deb.nodesource.com
        Pin-Priority: 1001
        
        *** These repos are active after the adjustments:
        Hit:1 http://deb.debian.org/debian bullseye InRelease
        Hit:2 http://security.debian.org/debian-security bullseye-security InRelease   
        Hit:3 http://deb.debian.org/debian bullseye-updates InRelease                  
        Get:4 https://deb.nodesource.com/node_18.x nodistro InRelease [12.1 kB]        
        Get:5 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages [7731 B]
        Fetched 19.9 kB in 0s (42.8 kB/s)   
        Reading package lists... Done
        
        Installing the recommended nodejs version now!
        
        Exact recommended version unknown, installing a fallback!
        dpkg: warning: downgrading nodejs from 20.12.0-1nodesource1 to 18.0.0-1nodesource1
        (Reading database ... 58252 files and directories currently installed.)
        Preparing to unpack .../nodejs_18.0.0-1nodesource1_amd64.deb ...
        Detected old npm client, removing...
        Unpacking nodejs (18.0.0-1nodesource1) over (20.12.0-1nodesource1) ...
        Setting up nodejs (18.0.0-1nodesource1) ...
        Processing triggers for man-db (2.9.4-2) ...
        
        Updating fallback to latest nodejs v18 release
        (Reading database ... 58539 files and directories currently installed.)
        Preparing to unpack .../nodejs_18.20.0-1nodesource1_amd64.deb ...
        Detected old npm client, removing...
        Unpacking nodejs (18.20.0-1nodesource1) over (18.0.0-1nodesource1) ...
        Setting up nodejs (18.20.0-1nodesource1) ...
        Processing triggers for man-db (2.9.4-2) ...
        v18.20.0 has been installed! You are using the latest version now!
        Installing the recommended nodejs version!
        
        *** You need to manually restart your container/virtual machine now! *** 
        
        We tried our best to update or fix your nodejs. Please run 'iob diag' again to verify.
        

        Dennoch kriege ich nach einem Reboot weiterhin die I/O Errors :(.
        Gibt es eine Möglichkeit ein manuelles Backup vom Iobroker anzustoßen (ohne die Backup Funktion)?
        Vielen Dank im Voraus!

        A 1 Antwort Letzte Antwort
        0
        • A AlexWest

          @thomas-braun Danke für den Hinweis! Das Nodeupdate hat erfolgreich funktioniert.

          ioBroker nodejs updater 2023-10-13
          You requested to intall latest version from nodejs v18 tree.
          
          Your current setup is:
          /usr/bin/nodejs         v20.12.0
          /usr/bin/node           v20.12.0
          /usr/bin/npm            10.5.0
          /usr/bin/npx            10.5.0
          /usr/bin/corepack       0.25.2
          
          We found these nodejs versions available for installation:
          
          nodejs:
            Installed: 20.12.0-1nodesource1
            Candidate: 20.12.0-1nodesource1
            Version table:
           *** 20.12.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
                  100 /var/lib/dpkg/status
               20.11.1-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.11.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.10.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.9.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.8.1-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.8.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.7.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.6.1-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.6.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.5.1-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.5.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.4.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.3.1-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.3.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.2.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.1.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               20.0.0-1nodesource1 600
                  500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
               12.22.12~dfsg-1~deb11u4 500
                  500 http://deb.debian.org/debian bullseye/main amd64 Packages
                  500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
          
          
          
          Nothing to do - Your installation is using the correct paths.
          
          You are running nodejs v20.12.0. Do you want to install latest version from nodejs v.18 tree? 
          
          Press <y> to continue or any other key to quit
          Trying to update your installation now. Please be patient.
          
          Virtualization: kvm
          Waiting for ioBroker to shut down - Give me a minute...
          ############################################################
          
          *** These repos are active on your system:
          Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
          Hit:2 http://deb.debian.org/debian bullseye InRelease
          Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
          Fetched 44.1 kB in 0s (108 kB/s)    
          Reading package lists... Done
          
          *** Installing ca-certificates, curl and gnupg, just in case they are missing.
          
          *** Creating new /etc/apt/sources.list.d/nodesource.list and pinning source
          
          deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main
          Package: nodejs
          Pin: origin deb.nodesource.com
          Pin-Priority: 1001
          
          *** These repos are active after the adjustments:
          Hit:1 http://deb.debian.org/debian bullseye InRelease
          Hit:2 http://security.debian.org/debian-security bullseye-security InRelease   
          Hit:3 http://deb.debian.org/debian bullseye-updates InRelease                  
          Get:4 https://deb.nodesource.com/node_18.x nodistro InRelease [12.1 kB]        
          Get:5 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages [7731 B]
          Fetched 19.9 kB in 0s (42.8 kB/s)   
          Reading package lists... Done
          
          Installing the recommended nodejs version now!
          
          Exact recommended version unknown, installing a fallback!
          dpkg: warning: downgrading nodejs from 20.12.0-1nodesource1 to 18.0.0-1nodesource1
          (Reading database ... 58252 files and directories currently installed.)
          Preparing to unpack .../nodejs_18.0.0-1nodesource1_amd64.deb ...
          Detected old npm client, removing...
          Unpacking nodejs (18.0.0-1nodesource1) over (20.12.0-1nodesource1) ...
          Setting up nodejs (18.0.0-1nodesource1) ...
          Processing triggers for man-db (2.9.4-2) ...
          
          Updating fallback to latest nodejs v18 release
          (Reading database ... 58539 files and directories currently installed.)
          Preparing to unpack .../nodejs_18.20.0-1nodesource1_amd64.deb ...
          Detected old npm client, removing...
          Unpacking nodejs (18.20.0-1nodesource1) over (18.0.0-1nodesource1) ...
          Setting up nodejs (18.20.0-1nodesource1) ...
          Processing triggers for man-db (2.9.4-2) ...
          v18.20.0 has been installed! You are using the latest version now!
          Installing the recommended nodejs version!
          
          *** You need to manually restart your container/virtual machine now! *** 
          
          We tried our best to update or fix your nodejs. Please run 'iob diag' again to verify.
          

          Dennoch kriege ich nach einem Reboot weiterhin die I/O Errors :(.
          Gibt es eine Möglichkeit ein manuelles Backup vom Iobroker anzustoßen (ohne die Backup Funktion)?
          Vielen Dank im Voraus!

          A Offline
          A Offline
          AlexWest
          schrieb am zuletzt editiert von AlexWest
          #4

          @alexwest Das Thema kann als erledigt markiert werden.
          Kurz zu meiner Lösung:
          Ich habe mich per Filezilla auf die VM geschalten und den kompletten iobroker Ordner gesichert. Im Anschluss hab ich den iobroker samt seines Ordners gelöscht. Nach einer Neuinstallation hab ich diese mit dem gesicherten Ordner überbügelt. Das hat überraschenderweise funktioniert und jetzt läuft wieder alles. Ich werde mich nun direkt um die Einrichtung eines automatischen Backups kümmern....
          Viel Dank dir und noch einen schönen Tag!
          Mfg,
          Alex

          Thomas BraunT 1 Antwort Letzte Antwort
          0
          • A AlexWest

            @alexwest Das Thema kann als erledigt markiert werden.
            Kurz zu meiner Lösung:
            Ich habe mich per Filezilla auf die VM geschalten und den kompletten iobroker Ordner gesichert. Im Anschluss hab ich den iobroker samt seines Ordners gelöscht. Nach einer Neuinstallation hab ich diese mit dem gesicherten Ordner überbügelt. Das hat überraschenderweise funktioniert und jetzt läuft wieder alles. Ich werde mich nun direkt um die Einrichtung eines automatischen Backups kümmern....
            Viel Dank dir und noch einen schönen Tag!
            Mfg,
            Alex

            Thomas BraunT Online
            Thomas BraunT Online
            Thomas Braun
            Most Active
            schrieb am zuletzt editiert von
            #5

            @alexwest sagte in [erledigt] Nach Node.js Updateversuch plötzlich I/O Errors:

            Das hat überraschenderweise funktioniert

            Ich bin da skeptisch. In der Regel gehen da Links usw. kaputt.
            Hast du wenigstens nach der Harakiri-Aktion ein

            iob fix
            

            folgen lassen?

            Linux-Werkzeugkasten:
            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
            NodeJS Fixer Skript:
            https://forum.iobroker.net/topic/68035/iob-node-fix-skript
            iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

            A 1 Antwort Letzte Antwort
            1
            • Thomas BraunT Thomas Braun

              @alexwest sagte in [erledigt] Nach Node.js Updateversuch plötzlich I/O Errors:

              Das hat überraschenderweise funktioniert

              Ich bin da skeptisch. In der Regel gehen da Links usw. kaputt.
              Hast du wenigstens nach der Harakiri-Aktion ein

              iob fix
              

              folgen lassen?

              A Offline
              A Offline
              AlexWest
              schrieb am zuletzt editiert von
              #6

              @thomas-braun
              Vielen Dank für den Hinweis! Den Befehl habe ich gerade nach dem Stoppen des iobrokers ausgeführt:

              library: loaded
              Library version=2024-01-04
              
              ==========================================================================
              
                  Welcome to the ioBroker installation fixer!
                  Script version: 2024-01-04
              
              ==========================================================================
              
              
              ==========================================================================
                  Installing prerequisites (1/5)
              ==========================================================================
              
              Hit:1 http://deb.debian.org/debian bullseye InRelease
              Hit:2 http://security.debian.org/debian-security bullseye-security InRelease   
              Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]        
              Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease                  
              Fetched 44.1 kB in 1s (86.0 kB/s)                            
              Reading package lists... Done
              
              ==========================================================================
                  Checking ioBroker user and directory permissions (2/5)
              ==========================================================================
              
              Created /etc/sudoers.d/iobroker
              Fixing directory permissions...
              
              ==========================================================================
                  Check and cleanup npm temporary directories (3/5)
              ==========================================================================
              
              Done.
              
              ==========================================================================
                  Database maintenance (4/5)
              ==========================================================================
              
              Checking for uncompressed JSONL databases... This might take a while!
              
              Compressing /opt/iobroker/iobroker-data/states.jsonl
              Compressing /opt/iobroker/iobroker-data/objects.jsonl
              Compressed 2 JSONL files. Done
              
              ==========================================================================
                  Checking autostart (5/5)
              ==========================================================================
              
              Enabling autostart...
              Autostart enabled!
              
              ==========================================================================
              
                  Your installation was fixed successfully
                  Run iobroker start to start ioBroker again!
              
              ==========================================================================
              
              1 Antwort Letzte Antwort
              0
              Antworten
              • In einem neuen Thema antworten
              Anmelden zum Antworten
              • Älteste zuerst
              • Neuste zuerst
              • Meiste Stimmen


              Support us

              ioBroker
              Community Adapters
              Donate

              880

              Online

              32.6k

              Benutzer

              82.2k

              Themen

              1.3m

              Beiträge
              Community
              Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
              ioBroker Community 2014-2025
              logo
              • Anmelden

              • Du hast noch kein Konto? Registrieren

              • Anmelden oder registrieren, um zu suchen
              • Erster Beitrag
                Letzter Beitrag
              0
              • Home
              • Aktuell
              • Tags
              • Ungelesen 0
              • Kategorien
              • Unreplied
              • Beliebt
              • GitHub
              • Docu
              • Hilfe