Iobroker Absturz - Ursache?
-
@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
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!!!@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
# fsckIn Deinem Fall, so
# sudo umount /backup # sudo fsck.ext4 /dev/sdb1Dann schauen was kommt, falls Du Dir nicht sicher bist, dann hier posten. Den Vorgang wiederholen wenn Fehler auftauchen.
VG
Bernd -
@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
ioBrokerLog, es kann auch ein Problem außerhalb gewesen sein.
Du könntest insjournalschauen,# sudo journalctl --since="2023-10-20 18:45:00"VG
BerndVielen 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) -
@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
ioBrokerLog, es kann auch ein Problem außerhalb gewesen sein.
Du könntest insjournalschauen,# sudo journalctl --since="2023-10-20 18:45:00"VG
BerndVielen 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)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. -
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.@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? -
@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? -
@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 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 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.
@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?
-
@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?
@brokeling
Ist die in der fstab drin?cat /etc/fstab -
@brokeling
Ist die in der fstab drin?cat /etc/fstab@thomas-braun said in Iobroker Absturz - Ursache?:
cat /etc/fstab
pi@raspi:~ $ cat /etc/fstab proc /proc proc defaults 0 0 PARTUUID=6c586e13-01 /boot vfat defaults,flush 0 2 PARTUUID=6c586e13-02 / ext4 defaults,noatime 0 1 # a swapfile is not a swap partition, no line here # use dphys-swapfile swap[on|off] for that PARTUUID=85032a97-01 /backup ext4 defaults,noatime,nofail 0 2 -
@thomas-braun said in Iobroker Absturz - Ursache?:
cat /etc/fstab
pi@raspi:~ $ cat /etc/fstab proc /proc proc defaults 0 0 PARTUUID=6c586e13-01 /boot vfat defaults,flush 0 2 PARTUUID=6c586e13-02 / ext4 defaults,noatime 0 1 # a swapfile is not a swap partition, no line here # use dphys-swapfile swap[on|off] for that PARTUUID=85032a97-01 /backup ext4 defaults,noatime,nofail 0 2@brokeling sagte in Iobroker Absturz - Ursache?:
PARTUUID=85032a97-01 /backup ext4 defaults,noatime,nofail 0 2
Trag da mal
PARTUUID=85032a97-01 /backup ext4 defaults,ro,noatime,nofail 0 2ein. Dann
sudo mount -o remount /backupIch weiß nur nicht, ob sich ro nicht mit defaults beißt. Müsste ich nachschauen.
-
@brokeling sagte in Iobroker Absturz - Ursache?:
PARTUUID=85032a97-01 /backup ext4 defaults,noatime,nofail 0 2
Trag da mal
PARTUUID=85032a97-01 /backup ext4 defaults,ro,noatime,nofail 0 2ein. Dann
sudo mount -o remount /backupIch weiß nur nicht, ob sich ro nicht mit defaults beißt. Müsste ich nachschauen.
@thomas-braun
Ich kann doch den USB stick auch einfach entfernen. -
@thomas-braun
Ich kann doch den USB stick auch einfach entfernen.@brokeling dann kommst duvaber icht mehr an dein(e) Backup(s) ran
-
@thomas-braun
Ich kann doch den USB stick auch einfach entfernen.@brokeling sagte in Iobroker Absturz - Ursache?:
Ich kann doch den USB stick auch einfach entfernen.
Aber NICHT wenn der gemountet ist oder da irgendwas noch drauf zugreift...
Das kann nämlich auch zu defekten Dateien führen. -
@brokeling sagte in Iobroker Absturz - Ursache?:
Ich kann doch den USB stick auch einfach entfernen.
Aber NICHT wenn der gemountet ist oder da irgendwas noch drauf zugreift...
Das kann nämlich auch zu defekten Dateien führen.@thomas-braun
ok ich trage in der fstab
stattPARTUUID=85032a97-01 /backup ext4 defaults,noatime,nofail 0 2das hier ein:
PARTUUID=85032a97-01 /backup ext4 defaults,ro,noatime,nofail 0 2 -
@brokeling sagte in Iobroker Absturz - Ursache?:
Ich kann doch den USB stick auch einfach entfernen.
Aber NICHT wenn der gemountet ist oder da irgendwas noch drauf zugreift...
Das kann nämlich auch zu defekten Dateien führen.@thomas-braun said in Iobroker Absturz - Ursache?:
@brokeling sagte in Iobroker Absturz - Ursache?:
Ich kann doch den USB stick auch einfach entfernen.
Aber NICHT wenn der gemountet ist oder da irgendwas noch drauf zugreift...
Das kann nämlich auch zu defekten Dateien führen.Ich hatte den aber schon abgenommen...
-
@thomas-braun said in Iobroker Absturz - Ursache?:
@brokeling sagte in Iobroker Absturz - Ursache?:
Ich kann doch den USB stick auch einfach entfernen.
Aber NICHT wenn der gemountet ist oder da irgendwas noch drauf zugreift...
Das kann nämlich auch zu defekten Dateien führen.Ich hatte den aber schon abgenommen...
@brokeling sagte in Iobroker Absturz - Ursache?:
Ich hatte den aber schon abgenommen...
Computergrundwissen: Macht man nicht.
-
@brokeling sagte in Iobroker Absturz - Ursache?:
Ich hatte den aber schon abgenommen...
Computergrundwissen: Macht man nicht.
@thomas-braun said in Iobroker Absturz - Ursache?:
@brokeling sagte in Iobroker Absturz - Ursache?:
Ich hatte den aber schon abgenommen...
Computergrundwissen: Macht man nicht.
im abgeschalteten modus.
-
@thomas-braun said in Iobroker Absturz - Ursache?:
@brokeling sagte in Iobroker Absturz - Ursache?:
Ich hatte den aber schon abgenommen...
Computergrundwissen: Macht man nicht.
im abgeschalteten modus.
pi@raspi:~ $ cat /etc/fstab proc /proc proc defaults 0 0 PARTUUID=6c586e13-01 /boot vfat defaults,flush 0 2 PARTUUID=6c586e13-02 / ext4 defaults,noatime 0 1 # a swapfile is not a swap partition, no line here # use dphys-swapfile swap[on|off] for that # PARTUUID=85032a97-01 /backup ext4 defaults,noatime,nofail 0 2 PARTUUID=85032a97-01 /backup ext4 defaults,ro,noatime,nofail 0 2 -
pi@raspi:~ $ cat /etc/fstab proc /proc proc defaults 0 0 PARTUUID=6c586e13-01 /boot vfat defaults,flush 0 2 PARTUUID=6c586e13-02 / ext4 defaults,noatime 0 1 # a swapfile is not a swap partition, no line here # use dphys-swapfile swap[on|off] for that # PARTUUID=85032a97-01 /backup ext4 defaults,noatime,nofail 0 2 PARTUUID=85032a97-01 /backup ext4 defaults,ro,noatime,nofail 0 2mount | sort
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden272
Online32.8k
Benutzer82.9k
Themen1.3m
Beiträge