IoBroker fix Fehlermeldung [Gelöst]
-
Systemdata Bitte Ausfüllen Hardwaresystem: NUC mit proxmox Arbeitsspeicher: 4GB Festplattenart: SSD Betriebssystem: Ubuntu server Node-Version: 16.13.2 Nodejs-Version: 10.x.x NPM-Version: 8.1.2 Installationsart: Skript Ich habe in letzter zeit oft Probleme mit meiner IoBroker installation.
Nach einem "iobroker fix" kam folgende Meldung:Created /etc/sudoers.d/iobroker Fixing directory permissions... chown: cannot read directory '/opt/iobroker/node_modules/iobroker.web/node_modules': Bad message chown: cannot access '/opt/iobroker/node_modules/iobroker.web/www/lib/css/themes/jquery-ui/custom-dark/images': Structure needs cleaning chown: cannot read directory '/opt/iobroker/node_modules/iobroker.web/node_modules': Bad message chown: cannot access '/opt/iobroker/node_modules/iobroker.web/www/lib/css/themes/jquery-ui/custom-dark/images': Structure needs cleaning This system does not support setting default permissions. Do not use npm to manually install adapters unless you know what you are doing!Ich wüsste nich das ich etwas an den Rechten geändert habe.
-
sudo ln -s /usr/bin/node /usr/bin/nodejs which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs -
Bitte Konsolenausgaben in CodeTags setzen.
This system does not support setting default permissions.könnte auf ein defektes Dateisystem hindeuten.
dmesg -T | grep -i ext4 -
iobroker@iobroker:/opt/iobroker$ which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.13.2 v16.13.2 8.1.2 iobroker /opt/iobroker OK:1 http://de.archive.ubuntu.com/ubuntu focal InRelease OK:2 https://deb.nodesource.com/node_16.x focal InRelease OK:3 http://de.archive.ubuntu.com/ubuntu focal-updates InRelease OK:4 http://de.archive.ubuntu.com/ubuntu focal-backports InRelease OK:5 http://de.archive.ubuntu.com/ubuntu focal-security InRelease Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Aktualisierung für 13 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen. nodejs: Installiert: 16.13.2-deb-1nodesource1 Installationskandidat: 16.13.2-deb-1nodesource1 Versionstabelle: *** 16.13.2-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x focal/main amd64 Packages 100 /var/lib/dpkg/status 10.19.0~dfsg-3ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages@thomas-braun said in IoBroker fix Fehlermeldung:
dmesg -T | grep -i ext4
iobroker@iobroker:/opt/iobroker$ dmesg -T | grep -i ext4 [Sa Feb 5 10:43:00 2022] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [Sa Feb 5 10:43:01 2022] EXT4-fs (sda2): re-mounted. Opts: (null) [Sa Feb 5 10:43:52 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:43:52 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:43:52 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:43:52 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:43:52 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:44:23 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:44:23 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:44:23 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:44:23 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:44:23 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:44:23 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:44:23 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:44:23 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:44:23 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 10:44:23 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 15:59:57 2022] EXT4-fs error: 35 callbacks suppressed [Sa Feb 5 15:59:57 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm npm: Directory block failed checksum [Sa Feb 5 16:00:01 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm npm: Directory block failed checksum [Sa Feb 5 16:00:05 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm npm: checksumming directory block 0 [Sa Feb 5 16:00:05 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm npm: checksumming directory block 0 [Sa Feb 5 16:00:05 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm npm: checksumming directory block 0 [Sa Feb 5 16:00:05 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm npm: checksumming directory block 0 [Sa Feb 5 16:01:00 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm npm: Directory block failed checksum [Sa Feb 5 16:01:04 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm npm: checksumming directory block 0 [Sa Feb 5 16:01:04 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm npm: checksumming directory block 0 [Sa Feb 5 16:01:04 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm npm: checksumming directory block 0 [Sa Feb 5 16:01:04 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm npm: checksumming directory block 0 [Sa Feb 5 16:02:09 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm chown: Directory block failed checksum [Sa Feb 5 16:02:09 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm chown: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 16:02:11 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm chown: Directory block failed checksum [Sa Feb 5 16:02:11 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm chown: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 16:02:16 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm setfacl: Directory block failed checksum [Sa Feb 5 16:02:16 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm setfacl: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 16:03:51 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm chown: Directory block failed checksum [Sa Feb 5 16:03:51 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm chown: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 16:03:52 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm chown: Directory block failed checksum [Sa Feb 5 16:03:52 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm chown: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 16:03:54 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm setfacl: Directory block failed checksum [Sa Feb 5 16:03:54 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm setfacl: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 16:04:31 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm chown: Directory block failed checksum [Sa Feb 5 16:04:31 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm chown: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 16:04:32 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm chown: Directory block failed checksum [Sa Feb 5 16:04:32 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm chown: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 16:04:34 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm setfacl: Directory block failed checksum [Sa Feb 5 16:04:34 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm setfacl: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 16:06:46 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm chown: Directory block failed checksum [Sa Feb 5 16:06:46 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm chown: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 16:06:47 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm chown: Directory block failed checksum [Sa Feb 5 16:06:47 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm chown: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 16:06:49 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm setfacl: Directory block failed checksum [Sa Feb 5 16:06:49 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm setfacl: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 16:19:45 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 16:19:45 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 16:19:45 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 16:19:45 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 16:19:45 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 16:19:46 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 16:19:46 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 16:19:46 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 16:19:46 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 16:19:46 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 23:06:43 2022] EXT4-fs error: 35 callbacks suppressed [Sa Feb 5 23:06:43 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm chown: Directory block failed checksum [Sa Feb 5 23:06:43 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm chown: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 23:06:44 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm chown: Directory block failed checksum [Sa Feb 5 23:06:44 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm chown: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 23:06:46 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm setfacl: Directory block failed checksum [Sa Feb 5 23:06:46 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm setfacl: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 23:18:43 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 23:18:43 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 23:18:43 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 23:18:43 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 23:18:43 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 23:18:43 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 23:18:43 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 23:18:43 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 23:18:43 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 23:18:43 2022] EXT4-fs error (device sda2): __ext4_find_entry:1549: inode #395017: comm node: checksumming directory block 0 [Sa Feb 5 23:19:55 2022] EXT4-fs error: 35 callbacks suppressed [Sa Feb 5 23:19:55 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm chown: Directory block failed checksum [Sa Feb 5 23:19:55 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm chown: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 23:19:56 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm chown: Directory block failed checksum [Sa Feb 5 23:19:56 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm chown: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0) [Sa Feb 5 23:19:58 2022] EXT4-fs error (device sda2): htree_dirblock_to_tree:1004: inode #395017: comm setfacl: Directory block failed checksum [Sa Feb 5 23:19:58 2022] EXT4-fs error (device sda2): ext4_ext_check_inode:496: inode #397422: comm setfacl: pblk 0 bad header/extent: invalid magic - magic f70a, entries 1, max 4(0), depth 0(0)So ein Mist, tatsächlich das Dateisystem zerschossen.
-
@fefi sagte in IoBroker fix Fehlermeldung:
So ein Mist, tatsächlich das Dateisystem zerschossen.
Ja, das ist Schrott.
-
@thomas-braun said in IoBroker fix Fehlermeldung:
@fefi sagte in IoBroker fix Fehlermeldung:
So ein Mist, tatsächlich das Dateisystem zerschossen.
Ja, das ist Schrott.
Konnte das Problem mithilfe von e2fsck lösen, indem ich den Superblock neu geschrieben habe.
Ich danke für die schnelle Hilfe. -
Dann würde ich aber überlegen wie es dazu kommt. 'Stromausfall'?
Trauen würde ich dem Datenträger jedenfalls nicht mehr. -
@thomas-braun
ich tippe mal auf Stromausfall.
Smartctl sagt mirSMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 49 Celsius Available Spare: 100% Available Spare Threshold: 5% Percentage Used: 0% Data Units Read: 4,900,862 [2.50 TB] Data Units Written: 3,103,308 [1.58 TB] Host Read Commands: 109,925,262 Host Write Commands: 141,055,215 Controller Busy Time: 2,285 Power Cycles: 59 Power On Hours: 1,665 Unsafe Shutdowns: 50 Media and Data Integrity Errors: 0 Error Information Log Entries: 7 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Temperature Sensor 1: 49 Celsius Temperature Sensor 2: 54 Celsius Thermal Temp. 1 Transition Count: 47 Thermal Temp. 1 Total Time: 13275722Ich erkenne da erstmal nix schlimes
Unsafe Shutdowns: 50
ist schon happig, das muss ich mal was tun.
