Iobroker Absturz - Ursache?

brokeling

nodejs müsste upgedated sein...
an den ports bin ich gerade dran.
Gibt es ein Auflistung welche ports in Benutzung sind?
Ich würde shelly ändern.
Kann ich sie beliebig ändern?

Skript v.2023-10-10

*** BASE SYSTEM ***
   Static hostname: raspi
         Icon name: computer
  Operating System: Raspbian GNU/Linux 11 (bullseye)
            Kernel: Linux 5.10.103-v7l+
      Architecture: arm

Model           : Raspberry Pi 4 Model B Rev 1.1
Docker          : false
Virtualization  : none
Kernel          : armv7l
Userland        : armhf

Systemuptime and Load:
 20:42:26 up  1:35,  1 user,  load average: 0.58, 1.87, 2.04
CPU threads: 4


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

Previously detected issues:
No throttling issues detected.

*** Time and Time Zones ***
               Local time: Fri 2023-10-20 20:42:26 CEST
           Universal time: Fri 2023-10-20 18:42:26 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** User and Groups ***
pi
/home/pi
pi adm dialout cdrom sudo audio video plugdev games users input netdev lpadmin gpio i2c spi iobroker

*** X-Server-Setup ***
X-Server:       false
Desktop:
Terminal:       tty
Boot Target:    multi-user.target

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            3.8G        1.4G        817M        0.0K        1.5G        2.2G
Swap:            99M          0B         99M
Total:          3.9G        1.4G        917M

         3786 M total memory
         1421 M used memory
          514 M active memory
         2301 M inactive memory
          817 M free memory
          435 M buffer memory
         1112 M swap cache
           99 M total swap
            0 M used swap
           99 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

*** FAILED SERVICES ***

  UNIT                  LOAD   ACTIVE SUB    DESCRIPTION
* bthelper@hci0.service loaded failed failed Raspberry Pi bluetooth helper

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
/dev/root      ext4      117G   19G   92G  17% /
devtmpfs       devtmpfs  1.7G     0  1.7G   0% /dev
tmpfs          tmpfs     1.9G     0  1.9G   0% /dev/shm
tmpfs          tmpfs     758M  868K  757M   1% /run
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
/dev/sdb1      ext4      113G   79G   29G  74% /backup
/dev/sda1      vfat      253M   49M  204M  20% /boot
tmpfs          tmpfs     379M   16K  379M   1% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Fri Oct 20 19:07:26 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  smsc95xx.macaddr=DC:A6:32:40:0F:7D vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000  console=tty1 root=PARTUUID=6c586e13-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[Fri Oct 20 19:07:28 2023] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[Fri Oct 20 19:07:28 2023] VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
[Fri Oct 20 19:07:29 2023] EXT4-fs (sda2): re-mounted. Opts: (null)
[Fri Oct 20 19:07:31 2023] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501486: block 9962198: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501486: block 9962198: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501484: block 9962198: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501484: block 9962198: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501485: block 9962198: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501485: block 9962198: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501468: block 9962197: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501468: block 9962197: comm find: unable to read itable block
[Fri Oct 20 20:20:43 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501466: block 9962197: comm find: unable to read itable block
[Fri Oct 20 20:20:43 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501466: block 9962197: comm find: unable to read itable block
[Fri Oct 20 20:20:47 2023] EXT4-fs error: 33 callbacks suppressed
[Fri Oct 20 20:20:47 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501456: block 9962196: comm find: unable to read itable block
[Fri Oct 20 20:31:14 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212836: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:15 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #1578762: block 6291856: comm find: unable to read itable block
[Fri Oct 20 20:31:15 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7213028: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:15 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7213014: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:15 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7213020: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:15 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7213018: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:16 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212436: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578927: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578927: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578945: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578945: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578925: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578925: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578921: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578921: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578923: comm find: iget: checksum invalid
[Fri Oct 20 20:31:18 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212254: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:18 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212241: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:20 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212155: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:20 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212151: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:20 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7361724: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:22 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212356: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:22 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212340: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:22 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212936: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:22 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7361429: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:22 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7361425: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:24 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212632: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:25 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212634: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:25 2023] EXT4-fs warning: 1 callbacks suppressed
[Fri Oct 20 20:31:25 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212643: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:25 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212649: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:25 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212645: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:25 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816144: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:26 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816543: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:26 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816384: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:26 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816546: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:37 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816868: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:37 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816874: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:39 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6295018: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:39 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6294294: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:40 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6293930: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:40 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6295038: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:40 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6295036: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:40 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6294560: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:40 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6294556: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:41 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6295040: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:42 2023] EXT4-fs warning: 5 callbacks suppressed
[Fri Oct 20 20:31:42 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6424206: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:46 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1184835: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:46 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056874: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:46 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056811: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056879: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056602: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7362338: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056607: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056903: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6951908: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6821023: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6821020: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:48 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6820752: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:48 2023] EXT4-fs error: 21 callbacks suppressed
[Fri Oct 20 20:31:48 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501414: block 9962194: comm find: unable to read itable block
[Fri Oct 20 20:31:48 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501414: block 9962194: comm find: unable to read itable block
[Fri Oct 20 20:31:48 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501418: block 9962194: comm find: unable to read itable block
[Fri Oct 20 20:31:48 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501418: block 9962194: comm find: unable to read itable block
[Fri Oct 20 20:31:49 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501402: block 9962193: comm find: unable to read itable block
[Fri Oct 20 20:31:49 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501402: block 9962193: comm find: unable to read itable block
[Fri Oct 20 20:31:49 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501406: block 9962193: comm find: unable to read itable block
[Fri Oct 20 20:31:49 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501406: block 9962193: comm find: unable to read itable block
[Fri Oct 20 20:31:49 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501422: block 9962194: comm find: unable to read itable block
[Fri Oct 20 20:31:49 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501422: block 9962194: comm find: unable to read itable block
[Fri Oct 20 20:31:50 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #4481932: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:50 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #4482754: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:57 2023] EXT4-fs error: 4 callbacks suppressed
[Fri Oct 20 20:31:57 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481282: block 17827376: comm find: unable to read itable block
[Fri Oct 20 20:31:57 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481282: block 17827376: comm find: unable to read itable block
[Fri Oct 20 20:31:58 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481164: block 17827368: comm find: unable to read itable block
[Fri Oct 20 20:31:58 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481164: block 17827368: comm find: unable to read itable block
[Fri Oct 20 20:31:58 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481439: block 17827385: comm find: unable to read itable block
[Fri Oct 20 20:31:58 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481439: block 17827385: comm find: unable to read itable block
[Fri Oct 20 20:31:58 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481297: block 17827377: comm find: unable to read itable block
[Fri Oct 20 20:31:58 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481297: block 17827377: comm find: unable to read itable block
[Fri Oct 20 20:31:59 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481429: block 17827385: comm find: unable to read itable block
[Fri Oct 20 20:31:59 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481429: block 17827385: comm find: unable to read itable block
[Fri Oct 20 20:32:01 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #2893701: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:32:01 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #2893470: lblock 0: comm find: error -5 reading directory block

Show mounted filesystems \(real ones only\):
TARGET    SOURCE    FSTYPE OPTIONS
/         /dev/sda2 ext4   rw,noatime,stripe=8191
|-/backup /dev/sdb1 ext4   rw,noatime
`-/boot   /dev/sda1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remount-ro

Files in neuralgic directories:

/var:
6.4G    /var/
3.4G    /var/cache/apt
3.4G    /var/cache
3.3G    /var/cache/apt/archives
2.6G    /var/lib

Archived and active journals take up 232.0M in the file system.

/opt/iobroker/backups:
3.9G    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
1.1G    /opt/iobroker/iobroker-data/
552M    /opt/iobroker/iobroker-data/backup-objects
383M    /opt/iobroker/iobroker-data/files
78M     /opt/iobroker/iobroker-data/files/icons-open-icon-library-png
52M     /opt/iobroker/iobroker-data/files/javascript.admin

The five largest files in iobroker-data are:
41M     /opt/iobroker/iobroker-data/states.json.old
41M     /opt/iobroker/iobroker-data/states.json.bak
35M     /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map
24M     /opt/iobroker/iobroker-data/objects.jsonl
21M     /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.js.map

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-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100GB8-if03
/dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100GB8-if00

*** NodeJS-Installation ***

/usr/bin/nodejs         v18.18.2
/usr/bin/node           v18.18.2
/usr/bin/npm            9.8.1
/usr/bin/npx            9.8.1
/usr/bin/corepack       0.19.0


nodejs:
  Installed: 18.18.2-1nodesource1
  Candidate: 18.18.2-1nodesource1
  Version table:
 *** 18.18.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
        100 /var/lib/dpkg/status
     18.18.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.17.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.16.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.14.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.14.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.9.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     18.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
     12.22.12~dfsg-1~deb11u4 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages

Temp directories causing npm8 problem: 0
No problems detected

Errors in npm tree:

*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: redis

Core adapters versions
js-controller:  5.0.12
admin:          6.10.1
javascript:     7.1.4

Adapters from github:   3

Adapter State
+ system.adapter.admin.1                  : admin                 : raspi                                    -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
  system.adapter.alias-manager.0          : alias-manager         : raspi                                    -  enabled
+ system.adapter.backitup.0               : backitup              : raspi                                    -  enabled
+ system.adapter.chromecast.0             : chromecast            : raspi                                    -  enabled
+ system.adapter.cloud.0                  : cloud                 : raspi                                    -  enabled
  system.adapter.deconz.0                 : deconz                : raspi                                    - disabled, port: 80
  system.adapter.devices.0                : devices               : raspi                                    -  enabled
  system.adapter.feiertage.0              : feiertage             : raspi                                    -  enabled
  system.adapter.flot.0                   : flot                  : raspi                                    -  enabled
  system.adapter.fritzdect.0              : fritzdect             : raspi                                    - disabled
  system.adapter.hue-extended.0           : hue-extended          : raspi                                    - disabled
  system.adapter.hue.0                    : hue                   : raspi                                    - disabled, port: 443
  system.adapter.ical.0                   : ical                  : raspi                                    -  enabled
  system.adapter.icons-icons8.0           : icons-icons8          : raspi                                    -  enabled
  system.adapter.icons-mfd-svg.0          : icons-mfd-svg         : raspi                                    -  enabled
  system.adapter.icons-open-icon-library-png.0: icons-open-icon-library-png: raspi                                    -  enabled
  system.adapter.iqontrol.0               : iqontrol              : raspi                                    - disabled
+ system.adapter.javascript.0             : javascript            : raspi                                    -  enabled
  system.adapter.luftdaten.0              : luftdaten             : raspi                                    -  enabled
  system.adapter.luftdaten.1              : luftdaten             : raspi                                    -  enabled
  system.adapter.mqtt.0                   : mqtt                  : raspi                                    - disabled, port: 1884, bind: 0.0.0.0
  system.adapter.net-tools.0              : net-tools             : raspi                                    -  enabled
  system.adapter.netatmo-crawler.0        : netatmo-crawler       : raspi                                    -  enabled
+ system.adapter.nuki.0                   : nuki                  : raspi                                    -  enabled
+ system.adapter.onvif.0                  : onvif                 : raspi                                    -  enabled, port: 80, 7575, 8000, 8080, 8081, 8899
+ system.adapter.ping.0                   : ping                  : raspi                                    -  enabled
+ system.adapter.pushover.0               : pushover              : raspi                                    -  enabled
+ system.adapter.reolink.0                : reolink               : raspi                                    -  enabled
+ system.adapter.reolink.1                : reolink               : raspi                                    -  enabled
+ system.adapter.reolink.2                : reolink               : raspi                                    -  enabled
+ system.adapter.reolink.3                : reolink               : raspi                                    -  enabled
  system.adapter.reolink.4                : reolink               : raspi                                    - disabled
  system.adapter.samsung_tizen.0          : samsung_tizen         : raspi                                    - disabled, port: 8002
+ system.adapter.sayit.0                  : sayit                 : raspi                                    -  enabled
+ system.adapter.sayit.1                  : sayit                 : raspi                                    -  enabled
+ system.adapter.sayit.2                  : sayit                 : raspi                                    -  enabled
+ system.adapter.sayit.3                  : sayit                 : raspi                                    -  enabled
+ system.adapter.sayit.4                  : sayit                 : raspi                                    -  enabled
+ system.adapter.sayit.5                  : sayit                 : raspi                                    -  enabled
+ system.adapter.shelly.0                 : shelly                : raspi                                    -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.simple-api.0             : simple-api            : raspi                                    -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
  system.adapter.smartcontrol.0           : smartcontrol          : raspi                                    - disabled
+ system.adapter.sonoff.0                 : sonoff                : raspi                                    -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.sourceanalytix.2         : sourceanalytix        : raspi                                    -  enabled
+ system.adapter.spotify-premium.0        : spotify-premium       : raspi                                    -  enabled
+ system.adapter.sql.0                    : sql                   : raspi                                    -  enabled, port: 0
  system.adapter.statistics.0             : statistics            : raspi                                    - disabled
+ system.adapter.telegram.0               : telegram              : raspi                                    -  enabled, port: 8443, bind: 0.0.0.0
  system.adapter.text2command.0           : text2command          : raspi                                    - disabled
  system.adapter.vis-colorpicker.0        : vis-colorpicker       : raspi                                    -  enabled
  system.adapter.vis-fancyswitch.0        : vis-fancyswitch       : raspi                                    -  enabled
  system.adapter.vis-google-fonts.0       : vis-google-fonts      : raspi                                    -  enabled
  system.adapter.vis-history.0            : vis-history           : raspi                                    -  enabled
  system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : raspi                                    -  enabled
  system.adapter.vis-icontwo.0            : vis-icontwo           : raspi                                    -  enabled
  system.adapter.vis-jqui-mfd.0           : vis-jqui-mfd          : raspi                                    -  enabled
  system.adapter.vis-justgage.0           : vis-justgage          : raspi                                    -  enabled
  system.adapter.vis-material-advanced.0  : vis-material-advanced : raspi                                    -  enabled
  system.adapter.vis-metro.0              : vis-metro             : raspi                                    -  enabled
  system.adapter.vis-rgraph.0             : vis-rgraph            : raspi                                    -  enabled
  system.adapter.vis-timeandweather.0     : vis-timeandweather    : raspi                                    -  enabled
  system.adapter.vis.0                    : vis                   : raspi                                    -  enabled
+ system.adapter.web.0                    : web                   : raspi                                    -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
  system.adapter.whatsapp-cmb.0           : whatsapp-cmb          : raspi                                    - disabled
+ system.adapter.zigbee.0                 : zigbee                : raspi                                    -  enabled, port: /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100GB8-if00

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.1                  : admin                 : raspi                                    -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.onvif.0                  : onvif                 : raspi                                    -  enabled, port: 80, 7575, 8000, 8080, 8081, 8899
+ system.adapter.shelly.0                 : shelly                : raspi                                    -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.simple-api.0             : simple-api            : raspi                                    -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.sonoff.0                 : sonoff                : raspi                                    -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.sql.0                    : sql                   : raspi                                    -  enabled, port: 0
+ system.adapter.telegram.0               : telegram              : raspi                                    -  enabled, port: 8443, bind: 0.0.0.0
+ system.adapter.web.0                    : web                   : raspi                                    -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
+ system.adapter.zigbee.0                 : zigbee                : raspi                                    -  enabled, port: /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100GB8-if00

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    "alias-manager": 1.2.6    , installed 1.2.6
Adapter    "asterisk"     : 1.0.6    , installed 1.0.6
Adapter    "backitup"     : 2.8.1    , installed 2.8.1
Adapter    "chromecast"   : 3.0.3    , installed 3.0.3
Adapter    "cloud"        : 4.4.1    , installed 4.4.1
Adapter    "countdown"    : 2.2.0    , installed 2.2.0
Adapter    "deconz"       : 1.3.21   , installed 1.3.21
Adapter    "devices"      : 1.1.5    , installed 1.1.5
Adapter    "digitalstrom" : 2.3.0    , installed 2.3.0
Adapter    "discovery"    : 3.1.0    , installed 3.2.0
Adapter    "fb-checkpresence": 1.2.2 , installed 1.2.2
Adapter    "feiertage"    : 1.1.4    , installed 1.1.4
Adapter    "flot"         : 1.12.0   , installed 1.12.0
Adapter    "fritzdect"    : 2.3.1    , installed 2.3.1
Adapter    "fullybrowser" : 2.1.2    , installed 2.1.2
Adapter    "hue"          : 3.10.0   , installed 3.10.0
Adapter    "hue-extended" : 2.0.0    , installed 2.0.0
Adapter    "ical"         : 1.13.3   , installed 1.13.3
Adapter    "icons-icons8" : 0.0.1    , installed 0.0.1
Adapter    "icons-mfd-svg": 1.1.0    , installed 1.1.0
Adapter    "icons-open-icon-library-png": 0.1.2, installed 0.1.2
Adapter    "info"         : 2.0.0    , installed 2.0.0
Adapter    "iqontrol"     : 2.3.0    , installed 2.3.0
Adapter    "javascript"   : 7.1.4    , installed 7.1.4
Controller "js-controller": 5.0.12   , installed 5.0.12
Adapter    "luftdaten"    : 3.0.0    , installed 3.0.0
Adapter    "moma"         : 1.2.9    , installed 1.2.9
Adapter    "mqtt"         : 4.1.1    , installed 4.1.1
Adapter    "mydlink"      : 1.3.4    , installed 1.3.4
Adapter    "net-tools"    : 0.2.0    , installed 0.2.0
Adapter    "netatmo-crawler": 0.8.1  , installed 0.8.1
Adapter    "nuki"         : 1.6.0    , installed 1.6.0
Adapter    "nuki-extended": 2.6.5    , installed 2.6.5
Adapter    "octoprint"    : 4.0.0    , installed 5.0.1
Adapter    "onvif"        : 1.0.5    , installed 1.0.5
Adapter    "owntracks"    : 1.0.5    , installed 1.0.5
Adapter    "paw"          : 0.3.2    , installed 0.3.2
Adapter    "ph803w"       : 1.1.1    , installed 1.1.1
Adapter    "ping"         : 1.6.2    , installed 1.6.2
Adapter    "pushover"     : 3.0.3    , installed 3.0.4
Adapter    "samsung"      : 0.5.11   , installed 0.5.11
Adapter    "sayit"        : 3.0.5    , installed 3.0.0  [Updatable]
Adapter    "shelly"       : 6.4.1    , installed 6.4.1
Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
Adapter    "smartcontrol" : 2.0.1    , installed 2.0.1
Adapter    "socketio"     : 6.5.5    , installed 6.5.5
Adapter    "sonoff"       : 2.5.3    , installed 2.5.7
Adapter    "spotify-premium": 1.2.2  , installed 1.2.2
Adapter    "sql"          : 2.2.0    , installed 2.2.0
Adapter    "statistics"   : 2.3.0    , installed 2.3.0
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-fancyswitch": 1.1.0  , installed 1.1.0
Adapter    "vis-google-fonts": 1.0.4 , installed 1.0.4
Adapter    "vis-history"  : 1.0.0    , installed 1.0.0
Adapter    "vis-hqwidgets": 1.4.0    , installed 1.4.0
Adapter    "vis-icontwo"  : 0.96.0   , installed 0.96.0
Adapter    "vis-jqui-mfd" : 1.0.12   , installed 1.0.12
Adapter    "vis-justgage" : 1.0.2    , installed 1.0.2
Adapter    "vis-material-advanced": 1.7.4, installed 1.7.4
Adapter    "vis-metro"    : 1.2.0    , installed 1.2.0
Adapter    "vis-rgraph"   : 0.0.2    , installed 0.0.2
Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
Adapter    "web"          : 6.1.2    , installed 6.1.2
Adapter    "whatsapp-cmb" : 0.2.3    , installed 0.2.3
Adapter    "wiobrowser"   : 2.0.2    , installed 2.0.2
Adapter    "ws"           : 2.5.5    , installed 2.5.5
Adapter    "zigbee"       : 1.8.23   , installed 1.8.23

Objects and States
Please stand by - This may take a while
Objects:        15185
States:         11056

*** OS-Repositories and Updates ***
Hit:1 http://phoscon.de/apt/deconz bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:4 https://deb.nodesource.com/node_18.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:80              0.0.0.0:*               LISTEN      1000       12897      350/deCONZ
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          12058      510/sshd: /usr/sbin
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      0          14693      459/cupsd
tcp        0      0 0.0.0.0:1883            0.0.0.0:*               LISTEN      1001       458023     2123/io.sonoff.0
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      1000       14750      350/deCONZ
tcp        0      0 192.168.178.53:9092     0.0.0.0:*               LISTEN      1001       460503     2779/io.nuki.0
tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       457155     1757/iobroker.js-co
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      110        12935      586/mariadbd
tcp        0      0 127.0.0.1:6379          0.0.0.0:*               LISTEN      118        13918      473/redis-server 12
tcp6       0      0 :::8081                 :::*                    LISTEN      1001       456110     1849/io.admin.1
tcp6       0      0 :::8082                 :::*                    LISTEN      1001       460147     2534/io.web.0
tcp6       0      0 :::22                   :::*                    LISTEN      0          12060      510/sshd: /usr/sbin
tcp6       0      0 :::8087                 :::*                    LISTEN      1001       464627     3567/io.simple-api.
tcp6       0      0 ::1:631                 :::*                    LISTEN      0          14692      459/cupsd
tcp6       0      0 ::1:6379                :::*                    LISTEN      118        13919      473/redis-server 12
udp        0      0 0.0.0.0:59397           0.0.0.0:*                           108        11914      343/avahi-daemon: r
udp        0      0 0.0.0.0:5683            0.0.0.0:*                           1001       459997     2432/io.shelly.0
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          12999      903/dhcpcd
udp        0      0 0.0.0.0:631             0.0.0.0:*                           0          12141      610/cups-browsed
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           1001       459488     2196/io.chromecast.
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        11912      343/avahi-daemon: r
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           1000       14963      350/deCONZ
udp6       0      0 :::546                  :::*                                0          13018      903/dhcpcd
udp6       0      0 :::5353                 :::*                                108        11913      343/avahi-daemon: r
udp6       0      0 :::45894                :::*                                108        11915      343/avahi-daemon: r

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

2023-10-20 20:41:05.366  - warn: sonoff.0 (2123) Client "TAS-2NICE-1" not connected
2023-10-20 20:43:34.170  - info: host.raspi iobroker add shelly auto --host raspi --debug
2023-10-20 20:43:38.123  - info: host.raspi iobroker host.raspi create instance shelly
2023-10-20 20:43:38.215  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.alive created
2023-10-20 20:43:38.289  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.connected created
2023-10-20 20:43:38.317  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.compactMode created
2023-10-20 20:43:38.394  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.cpu created
2023-10-20 20:43:38.435  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.cputime created
2023-10-20 20:43:38.453  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.memHeapUsed created
2023-10-20 20:43:38.480  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.memHeapTotal created
2023-10-20 20:43:38.496  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.memRss created
2023-10-20 20:43:38.508  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.uptime created
2023-10-20 20:43:38.519  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.inputCount created
2023-10-20 20:43:38.548  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.outputCount created
2023-10-20 20:43:38.562  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.eventLoopLag created
2023-10-20 20:43:38.573  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.sigKill created
2023-10-20 20:43:38.583  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1.logLevel created
2023-10-20 20:43:38.600  - info: host.raspi iobroker host.raspi object shelly.1 created
2023-10-20 20:43:38.644  - info: host.raspi iobroker host.raspi object shelly.1.info created
2023-10-20 20:43:38.690  - info: host.raspi iobroker host.raspi object shelly.1.info.connection created
2023-10-20 20:43:38.706  - info: host.raspi iobroker host.raspi object shelly.1.info.update created
2023-10-20 20:43:38.722  - info: host.raspi iobroker host.raspi object shelly.1.info.downloadScripts created
2023-10-20 20:43:38.728  - info: host.raspi iobroker host.raspi Set default value of shelly.1.info.connection: false
2023-10-20 20:43:38.758  - info: host.raspi iobroker host.raspi object system.adapter.shelly.1 created
2023-10-20 20:43:39.787  - info: host.raspi iobroker exit 0

Thomas Braun

@brokeling

nodejs ist jetzt richtig.
Aber dem Datenträger sdb1 auf /backup geht es schlecht. Ich vermute da auch den Grund für dein Problem.

brokeling

Ich nehme an, es ist dieser part:

*** 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:80              0.0.0.0:*               LISTEN      1000       12897      350/deCONZ
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          12058      510/sshd: /usr/sbin
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      0          14693      459/cupsd
tcp        0      0 0.0.0.0:1883            0.0.0.0:*               LISTEN      1001       458023     2123/io.sonoff.0
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      1000       14750      350/deCONZ
tcp        0      0 192.168.178.53:9092     0.0.0.0:*               LISTEN      1001       460503     2779/io.nuki.0
tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       457155     1757/iobroker.js-co
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      110        12935      586/mariadbd
tcp        0      0 127.0.0.1:6379          0.0.0.0:*               LISTEN      118        13918      473/redis-server 12
tcp6       0      0 :::8081                 :::*                    LISTEN      1001       456110     1849/io.admin.1
tcp6       0      0 :::8082                 :::*                    LISTEN      1001       460147     2534/io.web.0
tcp6       0      0 :::22                   :::*                    LISTEN      0          12060      510/sshd: /usr/sbin
tcp6       0      0 :::8087                 :::*                    LISTEN      1001       464627     3567/io.simple-api.
tcp6       0      0 ::1:631                 :::*                    LISTEN      0          14692      459/cupsd
tcp6       0      0 ::1:6379                :::*                    LISTEN      118        13919      473/redis-server 12
udp        0      0 0.0.0.0:59397           0.0.0.0:*                           108        11914      343/avahi-daemon: r
udp        0      0 0.0.0.0:5683            0.0.0.0:*                           1001       459997     2432/io.shelly.0
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          12999      903/dhcpcd
udp        0      0 0.0.0.0:631             0.0.0.0:*                           0          12141      610/cups-browsed
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           1001       459488     2196/io.chromecast.
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        11912      343/avahi-daemon: r
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           1000       14963      350/deCONZ
udp6       0      0 :::546                  :::*                                0          13018      903/dhcpcd
udp6       0      0 :::5353                 :::*                                108        11913      343/avahi-daemon: r
udp6       0      0 :::45894                :::*                                108        11915      343/avahi-daemon: r

@haselchen
woher hast du gesehen, dass shelly und sonoff den gleichen port haben?
(es stimmt wohl, beide auf 1883)

brokeling

@thomas-braun

@thomas-braun said in Iobroker Absturz - Ursache?:

@brokeling

Aber dem Datenträger sdb1 auf /backup geht es schlecht. Ich vermute da auch den Grund für dein Problem.

Was ist da?

Thomas Braun

@brokeling

Das ist da:

Messages concerning ext4 filesystem in dmesg:
[Fri Oct 20 19:07:26 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  smsc95xx.macaddr=DC:A6:32:40:0F:7D vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000  console=tty1 root=PARTUUID=6c586e13-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[Fri Oct 20 19:07:28 2023] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[Fri Oct 20 19:07:28 2023] VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
[Fri Oct 20 19:07:29 2023] EXT4-fs (sda2): re-mounted. Opts: (null)
[Fri Oct 20 19:07:31 2023] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501486: block 9962198: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501486: block 9962198: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501484: block 9962198: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501484: block 9962198: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501485: block 9962198: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501485: block 9962198: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501468: block 9962197: comm find: unable to read itable block
[Fri Oct 20 20:20:42 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501468: block 9962197: comm find: unable to read itable block
[Fri Oct 20 20:20:43 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501466: block 9962197: comm find: unable to read itable block
[Fri Oct 20 20:20:43 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501466: block 9962197: comm find: unable to read itable block
[Fri Oct 20 20:20:47 2023] EXT4-fs error: 33 callbacks suppressed
[Fri Oct 20 20:20:47 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501456: block 9962196: comm find: unable to read itable block
[Fri Oct 20 20:31:14 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212836: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:15 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #1578762: block 6291856: comm find: unable to read itable block
[Fri Oct 20 20:31:15 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7213028: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:15 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7213014: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:15 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7213020: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:15 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7213018: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:16 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212436: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578927: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578927: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578945: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578945: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578925: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578925: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578921: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578921: comm find: iget: checksum invalid
[Fri Oct 20 20:31:17 2023] EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578923: comm find: iget: checksum invalid
[Fri Oct 20 20:31:18 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212254: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:18 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212241: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:20 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212155: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:20 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212151: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:20 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7361724: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:22 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212356: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:22 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212340: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:22 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212936: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:22 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7361429: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:22 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7361425: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:24 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212632: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:25 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212634: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:25 2023] EXT4-fs warning: 1 callbacks suppressed
[Fri Oct 20 20:31:25 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212643: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:25 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212649: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:25 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212645: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:25 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816144: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:26 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816543: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:26 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816384: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:26 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816546: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:37 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816868: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:37 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816874: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:39 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6295018: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:39 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6294294: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:40 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6293930: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:40 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6295038: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:40 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6295036: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:40 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6294560: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:40 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6294556: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:41 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6295040: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:42 2023] EXT4-fs warning: 5 callbacks suppressed
[Fri Oct 20 20:31:42 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6424206: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:46 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1184835: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:46 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056874: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:46 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056811: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056879: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056602: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7362338: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056607: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056903: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6951908: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6821023: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:47 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6821020: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:48 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6820752: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:48 2023] EXT4-fs error: 21 callbacks suppressed
[Fri Oct 20 20:31:48 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501414: block 9962194: comm find: unable to read itable block
[Fri Oct 20 20:31:48 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501414: block 9962194: comm find: unable to read itable block
[Fri Oct 20 20:31:48 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501418: block 9962194: comm find: unable to read itable block
[Fri Oct 20 20:31:48 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501418: block 9962194: comm find: unable to read itable block
[Fri Oct 20 20:31:49 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501402: block 9962193: comm find: unable to read itable block
[Fri Oct 20 20:31:49 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501402: block 9962193: comm find: unable to read itable block
[Fri Oct 20 20:31:49 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501406: block 9962193: comm find: unable to read itable block
[Fri Oct 20 20:31:49 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501406: block 9962193: comm find: unable to read itable block
[Fri Oct 20 20:31:49 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501422: block 9962194: comm find: unable to read itable block
[Fri Oct 20 20:31:49 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501422: block 9962194: comm find: unable to read itable block
[Fri Oct 20 20:31:50 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #4481932: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:50 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #4482754: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:31:57 2023] EXT4-fs error: 4 callbacks suppressed
[Fri Oct 20 20:31:57 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481282: block 17827376: comm find: unable to read itable block
[Fri Oct 20 20:31:57 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481282: block 17827376: comm find: unable to read itable block
[Fri Oct 20 20:31:58 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481164: block 17827368: comm find: unable to read itable block
[Fri Oct 20 20:31:58 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481164: block 17827368: comm find: unable to read itable block
[Fri Oct 20 20:31:58 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481439: block 17827385: comm find: unable to read itable block
[Fri Oct 20 20:31:58 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481439: block 17827385: comm find: unable to read itable block
[Fri Oct 20 20:31:58 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481297: block 17827377: comm find: unable to read itable block
[Fri Oct 20 20:31:58 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481297: block 17827377: comm find: unable to read itable block
[Fri Oct 20 20:31:59 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481429: block 17827385: comm find: unable to read itable block
[Fri Oct 20 20:31:59 2023] EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481429: block 17827385: comm find: unable to read itable block
[Fri Oct 20 20:32:01 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #2893701: lblock 0: comm find: error -5 reading directory block
[Fri Oct 20 20:32:01 2023] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #2893470: lblock 0: comm find: error -5 reading directory block

brokeling

@thomas-braun
evtl. Festplatten-Schaden?

Thomas Braun

@brokeling

Ich weiß ja nicht was das da für ein Datenträger ist. Jedenfalls sind das viel zu viele Fehler da auf dem Hobel.

brokeling

@thomas-braun said in Iobroker Absturz - Ursache?:

@brokeling

Ich weiß ja nicht was das da für ein Datenträger ist. Jedenfalls sind das viel zu viele Fehler da auf dem Hobel.

Es sind zwei USB Sticks dran. Aber es betrifft wohl den backup usb stick.
Denkst du das kann sich im laufenden Betrieb auswirken?

pi@raspi:~ $ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 119,2G  0 disk
├─sda1   8:1    0   256M  0 part /boot
└─sda2   8:2    0   119G  0 part /
sdb      8:16   1 114,6G  0 disk
└─sdb1   8:17   1 114,6G  0 part /backup

Thomas Braun

@brokeling sagte in Iobroker Absturz - Ursache?:

Denkst du das kann sich im laufenden Betrieb auswirken?

Na logisch.
Sonst hättest du ja nicht die ganze Latte an Fehlermeldungen.

brokeling

@thomas-braun said in Iobroker Absturz - Ursache?:

@brokeling sagte in Iobroker Absturz - Ursache?:

Denkst du das kann sich im laufenden Betrieb auswirken?

Na logisch.
Sonst hättest du ja nicht die ganze Latte an Fehlermeldungen.

ok, danke!
Den werde ich dann austauschen.

den shelly port konnte ich ändern 1883 -> 1885

jetzt aber zu den beiden anderen doppel-port-Belegungen:

 0      0 0.0.0.0:5353            0.0.0.0:*                           1001       283538     12415/io.chromecast
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        11912      343/avahi-daemon: r

jetzt ist die Frage wie ich da rankommen kann, die zu ändern...

Thomas Braun

@brokeling sagte in Iobroker Absturz - Ursache?:

jetzt ist die Frage wie ich da rankommen kann, die zu ändern...

Von avahi würde ich die Finger lassen. Ob und wie man den chromcast abschalten kann weiß ich nicht.

brokeling

@thomas-braun
ok, ich lass das jetzt mal so. Und tausche schnellstmöglich den USB Stick.
Oder kann man da was "reparieren"?
Danke für die Hilfe!!!

Thomas Braun

@brokeling sagte in Iobroker Absturz - Ursache?:

Oder kann man da was "reparieren"?

Nö.

? Offline

@brokeling sagte in Iobroker Absturz - Ursache?:

Oder kann man da was "reparieren"?

Moin,

reparieren, kann ich nicht sagen, aber bei einem korrupten Filesystem, kann man immer ein Check machen

# fsck

In Deinem Fall, so

# sudo umount /backup
# sudo fsck.ext4 /dev/sdb1

Dann schauen was kommt, falls Du Dir nicht sicher bist, dann hier posten. Den Vorgang wiederholen wenn Fehler auftauchen.

VG
Bernd

brokeling

@dp20eic said in Iobroker Absturz - Ursache?:

@brokeling sagte in Iobroker Absturz - Ursache?:

leider ist mir iobroker heute abgestürzt, wahrscheinlich um so 18:50!?!

Moin,

schau mal nicht nur ins ioBroker Log, es kann auch ein Problem außerhalb gewesen sein.
Du könntest ins journal schauen,
# sudo journalctl --since="2023-10-20 18:45:00"     

VG
Bernd

Vielen Dank übrigens für die codes!
Ich stelle den das Resultat des letzteren hier rein, vielleicht kann der ein oder andere noch was draus lesen:

pi@raspi:~ $ sudo journalctl --since="2023-10-20 18:45:00" -g 'error'
-- Journal begins at Thu 2023-08-17 15:42:50 CEST, ends at Sat 2023-10-21 21:43:52 CEST. --
-- Boot f657936a502c4d5899b0bd648d6120d7 --
Okt 20 19:32:46 raspi pipewire[18775]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could n>
Okt 20 20:20:42 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697440 op 0x0:(READ) flags 0>
Okt 20 20:20:42 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697448 op 0x0:(READ) flags 0>
Okt 20 20:20:42 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697440 op 0x0:(READ) flags 0>
Okt 20 20:20:42 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697448 op 0x0:(READ) flags 0>
Okt 20 20:20:42 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501486: block 996>
Okt 20 20:20:42 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697440 op 0x0:(READ) flags 0>
Okt 20 20:20:42 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697448 op 0x0:(READ) flags 0>
Okt 20 20:20:42 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501486: block 996>
Okt 20 20:20:42 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697440 op 0x0:(READ) flags 0>
Okt 20 20:20:42 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697448 op 0x0:(READ) flags 0>
Okt 20 20:20:42 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501484: block 996>
Okt 20 20:20:42 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697440 op 0x0:(READ) flags 0>
Okt 20 20:20:42 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697448 op 0x0:(READ) flags 0>
Okt 20 20:20:42 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501484: block 996>
Okt 20 20:20:42 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501485: block 996>
Okt 20 20:20:43 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501485: block 996>
Okt 20 20:20:43 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501468: block 996>
Okt 20 20:20:43 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501468: block 996>
Okt 20 20:20:43 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501466: block 996>
Okt 20 20:20:43 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501466: block 996>
Okt 20 20:20:47 raspi kernel: print_req_error: 72 callbacks suppressed
Okt 20 20:20:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697440 op 0x0:(READ) flags 0>
Okt 20 20:20:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697448 op 0x0:(READ) flags 0>
Okt 20 20:20:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697440 op 0x0:(READ) flags 0>
Okt 20 20:20:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697448 op 0x0:(READ) flags 0>
Okt 20 20:20:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697440 op 0x0:(READ) flags 0>
Okt 20 20:20:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697448 op 0x0:(READ) flags 0>
Okt 20 20:20:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697440 op 0x0:(READ) flags 0>
Okt 20 20:20:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697448 op 0x0:(READ) flags 0>
Okt 20 20:20:47 raspi kernel: EXT4-fs error: 33 callbacks suppressed
Okt 20 20:20:47 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501456: block 996>
Okt 20 20:31:02 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 74160 op 0x0:(READ) flags 0x80>
Okt 20 20:31:14 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230767768 op 0x0:(READ) flags >
Okt 20 20:31:14 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212836: lblock 0: com>
Okt 20 20:31:15 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 50334880 op 0x0:(READ) flags 0>
Okt 20 20:31:15 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #1578762: block 629>
Okt 20 20:31:15 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230768536 op 0x0:(READ) flags >
Okt 20 20:31:15 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7213028: lblock 0: com>
Okt 20 20:31:16 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230768480 op 0x0:(READ) flags >
Okt 20 20:31:16 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7213014: lblock 0: com>
Okt 20 20:31:16 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230768504 op 0x0:(READ) flags >
Okt 20 20:31:16 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7213020: lblock 0: com>
Okt 20 20:31:16 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230768496 op 0x0:(READ) flags >
Okt 20 20:31:16 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7213018: lblock 0: com>
Okt 20 20:31:16 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 197141808 op 0x0:(READ) flags >
Okt 20 20:31:17 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230766184 op 0x0:(READ) flags >
Okt 20 20:31:17 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212436: lblock 0: com>
Okt 20 20:31:17 raspi kernel: EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578927: comm find: iget: checksum >
Okt 20 20:31:17 raspi kernel: EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578927: comm find: iget: checksum >
Okt 20 20:31:17 raspi kernel: EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578945: comm find: iget: checksum >
Okt 20 20:31:17 raspi kernel: EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578945: comm find: iget: checksum >
Okt 20 20:31:17 raspi kernel: EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578925: comm find: iget: checksum >
Okt 20 20:31:17 raspi kernel: EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578925: comm find: iget: checksum >
Okt 20 20:31:17 raspi kernel: EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578921: comm find: iget: checksum >
Okt 20 20:31:17 raspi kernel: EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578921: comm find: iget: checksum >
Okt 20 20:31:17 raspi kernel: EXT4-fs error (device sdb1): ext4_lookup:1706: inode #1578923: comm find: iget: checksum >
Okt 20 20:31:18 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230765472 op 0x0:(READ) flags >
Okt 20 20:31:18 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212254: lblock 0: com>
Okt 20 20:31:18 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230765424 op 0x0:(READ) flags >
Okt 20 20:31:18 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212241: lblock 0: com>
Okt 20 20:31:20 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230765088 op 0x0:(READ) flags >
Okt 20 20:31:20 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212155: lblock 0: com>
Okt 20 20:31:20 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230765072 op 0x0:(READ) flags >
Okt 20 20:31:20 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212151: lblock 0: com>
Okt 20 20:31:21 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 234968984 op 0x0:(READ) flags >
Okt 20 20:31:21 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7361724: lblock 0: com>
Okt 20 20:31:22 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 58724392 op 0x0:(READ) flags 0>
Okt 20 20:31:22 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230765864 op 0x0:(READ) flags >
Okt 20 20:31:22 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212356: lblock 0: com>
Okt 20 20:31:22 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230765800 op 0x0:(READ) flags >
Okt 20 20:31:22 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212340: lblock 0: com>
Okt 20 20:31:22 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230768168 op 0x0:(READ) flags >
Okt 20 20:31:22 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212936: lblock 0: com>
Okt 20 20:31:22 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 234967824 op 0x0:(READ) flags >
Okt 20 20:31:22 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7361429: lblock 0: com>
Okt 20 20:31:22 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 234967808 op 0x0:(READ) flags >
Okt 20 20:31:22 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7361425: lblock 0: com>
Okt 20 20:31:25 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230766952 op 0x0:(READ) flags >
Okt 20 20:31:25 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212632: lblock 0: com>
Okt 20 20:31:25 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212634: lblock 0: com>
Okt 20 20:31:25 raspi kernel: print_req_error: 2 callbacks suppressed
Okt 20 20:31:25 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230767000 op 0x0:(READ) flags >
Okt 20 20:31:25 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212643: lblock 0: com>
Okt 20 20:31:25 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230767024 op 0x0:(READ) flags >
Okt 20 20:31:25 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212649: lblock 0: com>
Okt 20 20:31:25 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 230767008 op 0x0:(READ) flags >
Okt 20 20:31:25 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7212645: lblock 0: com>
Okt 20 20:31:25 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 218171528 op 0x0:(READ) flags >
Okt 20 20:31:25 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816144: lblock 0: com>
Okt 20 20:31:26 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 218173424 op 0x0:(READ) flags >
Okt 20 20:31:26 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816543: lblock 0: com>
Okt 20 20:31:26 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 218172680 op 0x0:(READ) flags >
Okt 20 20:31:26 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816384: lblock 0: com>
Okt 20 20:31:26 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 218173440 op 0x0:(READ) flags >
Okt 20 20:31:26 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816546: lblock 0: com>
Okt 20 20:31:37 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 218174960 op 0x0:(READ) flags >
Okt 20 20:31:37 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816868: lblock 0: com>
Okt 20 20:31:37 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 218174984 op 0x0:(READ) flags >
Okt 20 20:31:37 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6816874: lblock 0: com>
Okt 20 20:31:39 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 201407536 op 0x0:(READ) flags >
Okt 20 20:31:39 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6295018: lblock 0: com>
Okt 20 20:31:39 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 201404528 op 0x0:(READ) flags >
Okt 20 20:31:39 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6294294: lblock 0: com>
Okt 20 20:31:40 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 201403016 op 0x0:(READ) flags >
Okt 20 20:31:40 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6293930: lblock 0: com>
Okt 20 20:31:40 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 201407616 op 0x0:(READ) flags >
Okt 20 20:31:40 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6295038: lblock 0: com>
Okt 20 20:31:40 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 201407608 op 0x0:(READ) flags >
Okt 20 20:31:40 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6295036: lblock 0: com>
Okt 20 20:31:40 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 201405632 op 0x0:(READ) flags >
Okt 20 20:31:40 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6294560: lblock 0: com>
Okt 20 20:31:40 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 201405616 op 0x0:(READ) flags >
Okt 20 20:31:40 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6294556: lblock 0: com>
Okt 20 20:31:41 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 201407624 op 0x0:(READ) flags >
Okt 20 20:31:41 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6295040: lblock 0: com>
Okt 20 20:31:42 raspi kernel: print_req_error: 5 callbacks suppressed
Okt 20 20:31:42 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 205593712 op 0x0:(READ) flags >
Okt 20 20:31:42 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6424206: lblock 0: com>
Okt 20 20:31:46 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 37835504 op 0x0:(READ) flags 0>
Okt 20 20:31:46 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1184835: lblock 0: com>
Okt 20 20:31:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 33648672 op 0x0:(READ) flags 0>
Okt 20 20:31:47 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056874: lblock 0: com>
Okt 20 20:31:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 33648656 op 0x0:(READ) flags 0>
Okt 20 20:31:47 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056811: lblock 0: com>
Okt 20 20:31:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 33648680 op 0x0:(READ) flags 0>
Okt 20 20:31:47 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056879: lblock 0: com>
Okt 20 20:31:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 33648352 op 0x0:(READ) flags 0>
Okt 20 20:31:47 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056602: lblock 0: com>
Okt 20 20:31:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 234970008 op 0x0:(READ) flags >
Okt 20 20:31:47 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #7362338: lblock 0: com>
Okt 20 20:31:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 33648360 op 0x0:(READ) flags 0>
Okt 20 20:31:47 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056607: lblock 0: com>
Okt 20 20:31:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 33648736 op 0x0:(READ) flags 0>
Okt 20 20:31:47 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #1056903: lblock 0: com>
Okt 20 20:31:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 222384016 op 0x0:(READ) flags >
Okt 20 20:31:47 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6951908: lblock 0: com>
Okt 20 20:31:47 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 218190272 op 0x0:(READ) flags >
Okt 20 20:31:47 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6821023: lblock 0: com>
Okt 20 20:31:48 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 218190256 op 0x0:(READ) flags >
Okt 20 20:31:48 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6821020: lblock 0: com>
Okt 20 20:31:48 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 218189888 op 0x0:(READ) flags >
Okt 20 20:31:48 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #6820752: lblock 0: com>
Okt 20 20:31:48 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697440 op 0x0:(READ) flags 0>
Okt 20 20:31:48 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697448 op 0x0:(READ) flags 0>
Okt 20 20:31:48 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697440 op 0x0:(READ) flags 0>
Okt 20 20:31:48 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697448 op 0x0:(READ) flags 0>
Okt 20 20:31:48 raspi kernel: EXT4-fs error: 21 callbacks suppressed
Okt 20 20:31:48 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501414: block 996>
Okt 20 20:31:48 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 79697440 op 0x0:(READ) flags 0>
Okt 20 20:31:49 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501414: block 996>
Okt 20 20:31:49 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501418: block 996>
Okt 20 20:31:49 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501418: block 996>
Okt 20 20:31:49 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501402: block 996>
Okt 20 20:31:49 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501402: block 996>
Okt 20 20:31:49 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501406: block 996>
Okt 20 20:31:49 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501406: block 996>
Okt 20 20:31:49 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501422: block 996>
Okt 20 20:31:49 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #2501422: block 996>
Okt 20 20:31:50 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #4481932: lblock 0: com>
Okt 20 20:31:50 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #4482754: lblock 0: com>
Okt 20 20:31:57 raspi kernel: print_req_error: 26 callbacks suppressed
Okt 20 20:31:57 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 142618920 op 0x0:(READ) flags >
Okt 20 20:31:57 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 142618928 op 0x0:(READ) flags >
Okt 20 20:31:57 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 142618920 op 0x0:(READ) flags >
Okt 20 20:31:57 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 142618928 op 0x0:(READ) flags >
Okt 20 20:31:57 raspi kernel: EXT4-fs error: 4 callbacks suppressed
Okt 20 20:31:57 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481282: block 178>
Okt 20 20:31:58 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 142618920 op 0x0:(READ) flags >
Okt 20 20:31:58 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 142618928 op 0x0:(READ) flags >
Okt 20 20:31:58 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481282: block 178>
Okt 20 20:31:58 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 142618920 op 0x0:(READ) flags >
Okt 20 20:31:58 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 142618928 op 0x0:(READ) flags >
Okt 20 20:31:58 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481164: block 178>
Okt 20 20:31:58 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 142618920 op 0x0:(READ) flags >
Okt 20 20:31:58 raspi kernel: blk_update_request: critical medium error, dev sdb, sector 142618928 op 0x0:(READ) flags >
Okt 20 20:31:58 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481164: block 178>
Okt 20 20:31:58 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481439: block 178>
Okt 20 20:31:58 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481439: block 178>
Okt 20 20:31:59 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481297: block 178>
Okt 20 20:31:59 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481297: block 178>
Okt 20 20:31:59 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481429: block 178>
Okt 20 20:31:59 raspi kernel: EXT4-fs error (device sdb1): __ext4_get_inode_loc_noinmem:4457: inode #4481429: block 178>
Okt 20 20:32:01 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #2893701: lblock 0: com>
Okt 20 20:32:02 raspi kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1003: inode #2893470: lblock 0: com>
Okt 20 20:35:30 raspi bash[1130]: [ioredis] Unhandled error event: Error: write EPIPE
Okt 20 21:10:59 raspi sshd[26773]: error: kex_exchange_identification: Connection closed by remote host
Okt 20 21:58:27 raspi sshd[27425]: error: kex_exchange_identification: Connection closed by remote host
Okt 20 21:58:35 raspi pipewire-media-session[18783]: error id:0 seq:293 res:-32 (Broken pipe): connection error
Okt 20 21:58:36 raspi bash[1757]: This error originated either by throwing inside of an async function without a catch >
Okt 20 21:58:36 raspi bash[1757]: Error: DB closed
-- Boot 9034ae27f1174260808e596c062cf691 --
-- Boot f657936a502c4d5899b0bd648d6120d7 --
-- Boot 9034ae27f1174260808e596c062cf691 --
-- Boot f657936a502c4d5899b0bd648d6120d7 --
-- Boot 9034ae27f1174260808e596c062cf691 --
-- Boot f657936a502c4d5899b0bd648d6120d7 --
-- Boot 9034ae27f1174260808e596c062cf691 --
-- Boot f657936a502c4d5899b0bd648d6120d7 --
-- Boot 9034ae27f1174260808e596c062cf691 --
-- Boot f657936a502c4d5899b0bd648d6120d7 --
-- Boot 9034ae27f1174260808e596c062cf691 --
-- Boot f657936a502c4d5899b0bd648d6120d7 --
-- Boot 9034ae27f1174260808e596c062cf691 --
-- Boot f657936a502c4d5899b0bd648d6120d7 --
-- Boot 9034ae27f1174260808e596c062cf691 --
-- Boot f657936a502c4d5899b0bd648d6120d7 --
-- Boot 9034ae27f1174260808e596c062cf691 --
-- Boot f657936a502c4d5899b0bd648d6120d7 --
-- Boot 9034ae27f1174260808e596c062cf691 --
-- Boot f657936a502c4d5899b0bd648d6120d7 --
-- Boot 9034ae27f1174260808e596c062cf691 --
Okt 20 21:58:46 raspi raspi-config[473]: Error opening '/dev/input/event*': No such file or directory
Okt 20 22:23:56 raspi pipewire[16483]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could n>
Okt 20 22:24:02 raspi sshd[16619]: error: kex_exchange_identification: Connection closed by remote host
Okt 20 22:33:28 raspi sshd[22886]: error: kex_exchange_identification: Connection closed by remote host
Okt 20 22:33:31 raspi pipewire[22918]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could n>
Okt 20 22:33:32 raspi sshd[22979]: error: kex_exchange_identification: Connection closed by remote host
Okt 21 09:29:13 raspi pipewire[11613]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could n>
Okt 21 09:35:25 raspi pipewire-media-session[11623]: error id:0 seq:293 res:-32 (Broken pipe): connection error
Okt 21 09:35:46 raspi pipewire[16025]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could n>
Okt 21 09:36:03 raspi sudo[16220]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl --since=20>
Okt 21 09:37:51 raspi pipewire-media-session[16033]: error id:0 seq:293 res:-32 (Broken pipe): connection error
Okt 21 21:43:37 raspi pipewire[19010]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could n>
Okt 21 21:43:52 raspi sudo[19205]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl --since=20>
lines 199-227/227 (END)

Thomas Braun

@brokeling

Ich würde behaupten, das Ding ist fratze.
Neuinstallation (auf frischem Datenträger), Backup von vor dem Crash einspielen.
Und diesmal gleich ohne Desktop installieren.

brokeling

@thomas-braun
Aber die Haupt-SSD ist doch in Ordnung und läuft, oder wo ist das Problem?
Das Problem hat doch nur der backup-USB Stick!?!
Und die backups sind ja leider auf dem corrupten USB Stick - ob die auslesbar sind?

brokeling

pi@raspi:~ $ sudo umount /backup
umount: /backup: not mounted.
pi@raspi:~ $ sudo fsck.ext4 /dev/sdb1
e2fsck 1.46.2 (28-Feb-2021)
/dev/sdb1 is in use.
e2fsck: Cannot continue, aborting.

Thomas Braun

@brokeling sagte in Iobroker Absturz - Ursache?:

Und die backups sind ja leider auf dem corrupten USB Stick - ob die auslesbar sind?

Kannste ja probieren. Ich würde das Dateisystem aber tunlichst 'nur-lesend'-ro einhängen. Du schrabbelst das Ding sonst nur noch weiter kaputt.

brokeling

@thomas-braun said in Iobroker Absturz - Ursache?:

@brokeling sagte in Iobroker Absturz - Ursache?:

Und die backups sind ja leider auf dem corrupten USB Stick - ob die auslesbar sind?

Kannste ja probieren. Ich würde das Dateisystem aber tunlichst 'nur-lesend'-ro einhängen. Du schrabbelst das Ding sonst nur noch weiter kaputt.

wie mache ich das?

Community Forum

NEWS

Iobroker Absturz - Ursache?

Support us

261

32.8k

82.9k

1.3m