_MARKUS_ Posted December 31, 2023 Share Posted December 31, 2023 (edited) Hallo zusammen Ich hatte unraid jetzt ein paar tage problemlos am laufen. Aber seit gestern Abend startet der Iobroker Docker Container nicht mehr. Der Container läuft nur ein paar Minuten und beendet sich dan wieder. Ich habe Logs angehängt. "Fix Common Problems" gibt dieses Problem aus: Macvlan and Bridging found. Parity-Check (+SMART) zeigt keine Probleme in den unraid logs macht mir diese Meldung sorgen (komplette logs sind angehängt) Dec 31 12:20:58 UNRAID kernel: nvme 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Dec 31 12:20:58 UNRAID kernel: nvme 0000:01:00.0: device [15b7:5006] error status/mask=00000001/0000e000 Dec 31 12:20:58 UNRAID kernel: nvme 0000:01:00.0: [ 0] RxErr Was kann ich machen? DANKE FÜR EURE HILFE🫂 LOGS Spoiler iobroker logs find: ‘/opt/iobroker/node_modules/underscore’: Structure needs cleaning chown: cannot read directory '/opt/iobroker/node_modules/underscore': Structure needs cleaning find: ‘/opt/iobroker/node_modules/underscore’: Structure needs cleaning chown: cannot read directory '/opt/iobroker/node_modules/underscore': Structure needs cleaning ----- Version Information ----- ----- image: v9.0.1 ----- ----- build: 2023-12-24T23:44:38+00:00 ----- ----- node: v18.19.0 ----- ----- npm: 10.2.3 ----- ----- ----- ----- Environment Variables ----- ----- SETGID: 100 ----- ----- SETUID: 99 ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 1 of 5: Preparing container ----- -------------------------------------------------------------------------------- Updating Linux packages on first run... Done. Registering maintenance script as command... Done. -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker installation ----- -------------------------------------------------------------------------------- Existing installation of ioBroker detected in "/opt/iobroker". -------------------------------------------------------------------------------- ----- Step 3 of 5: Checking ioBroker installation ----- -------------------------------------------------------------------------------- (Re)setting permissions (This might take a while! Please be patient!)... -------------------------------------------------------------------------------- ------------------------- 2023-12-31 12:16:01 ------------------------- -------------------------------------------------------------------------------- ----- ----- ----- ██╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██╗ ███████╗ ██████╗ ----- ----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ ----- ----- ██║ ██║ ██║ ██████╔╝ ██████╔╝ ██║ ██║ █████╔╝ █████╗ ██████╔╝ ----- ----- ██║ ██║ ██║ ██╔══██╗ ██╔══██╗ ██║ ██║ ██╔═██╗ ██╔══╝ ██╔══██╗ ----- ----- ██║ ╚██████╔╝ ██████╔╝ ██║ ██║ ╚██████╔╝ ██║ ██╗ ███████╗ ██║ ██║ ----- ----- ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ----- ----- ----- ----- Welcome to your ioBroker Docker container! ----- ----- Startupscript is now running! ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- System Information ----- ----- arch: x86_64 ----- ----- hostname: bdd13ccb5446 ----- ----- ----- ----- Version Information ----- ----- image: v9.0.1 ----- ----- build: 2023-12-24T23:44:38+00:00 ----- ----- node: v18.19.0 ----- ----- npm: 10.2.3 ----- ----- ----- ----- Environment Variables ----- ----- SETGID: 100 ----- ----- SETUID: 99 ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 1 of 5: Preparing container ----- -------------------------------------------------------------------------------- Updating Linux packages on first run... Done. Registering maintenance script as command... Done. -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker installation ----- -------------------------------------------------------------------------------- Existing installation of ioBroker detected in "/opt/iobroker". -------------------------------------------------------------------------------- ----- Step 3 of 5: Checking ioBroker installation ----- -------------------------------------------------------------------------------- (Re)setting permissions (This might take a while! Please be patient!)... ** Press ANY KEY to close this window ** unraid logs Dec 31 12:16:01 UNRAID kernel: docker0: port 1(veth6df695b) entered blocking state Dec 31 12:16:01 UNRAID kernel: docker0: port 1(veth6df695b) entered forwarding state Dec 31 12:16:01 UNRAID rc.docker: watchtower: started succesfully! Dec 31 12:16:01 UNRAID kernel: eth0: renamed from vethdc018e3 Dec 31 12:16:02 UNRAID rc.docker: AdGuard-Home: started succesfully! Dec 31 12:16:02 UNRAID kernel: docker0: port 2(veth2742611) entered blocking state Dec 31 12:16:02 UNRAID kernel: docker0: port 2(veth2742611) entered disabled state Dec 31 12:16:02 UNRAID kernel: device veth2742611 entered promiscuous mode Dec 31 12:16:02 UNRAID kernel: docker0: port 2(veth2742611) entered blocking state Dec 31 12:16:02 UNRAID kernel: docker0: port 2(veth2742611) entered forwarding state Dec 31 12:16:02 UNRAID kernel: eth0: renamed from veth0c73610 Dec 31 12:16:02 UNRAID kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2742611: link becomes ready Dec 31 12:16:02 UNRAID rc.docker: Docker-WebUI: started succesfully! Dec 31 12:16:02 UNRAID kernel: docker0: port 3(veth929b1c0) entered blocking state Dec 31 12:16:02 UNRAID kernel: docker0: port 3(veth929b1c0) entered disabled state Dec 31 12:16:02 UNRAID kernel: device veth929b1c0 entered promiscuous mode Dec 31 12:16:02 UNRAID kernel: docker0: port 3(veth929b1c0) entered blocking state Dec 31 12:16:02 UNRAID kernel: docker0: port 3(veth929b1c0) entered forwarding state Dec 31 12:16:02 UNRAID kernel: eth0: renamed from vethd19c532 Dec 31 12:16:02 UNRAID kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth929b1c0: link becomes ready Dec 31 12:16:02 UNRAID rc.docker: doublecommander: started succesfully! Dec 31 12:16:02 UNRAID kernel: docker0: port 4(veth35f53f6) entered blocking state Dec 31 12:16:02 UNRAID kernel: docker0: port 4(veth35f53f6) entered disabled state Dec 31 12:16:02 UNRAID kernel: device veth35f53f6 entered promiscuous mode Dec 31 12:16:02 UNRAID kernel: docker0: port 4(veth35f53f6) entered blocking state Dec 31 12:16:02 UNRAID kernel: docker0: port 4(veth35f53f6) entered forwarding state Dec 31 12:16:02 UNRAID kernel: eth0: renamed from veth5e683e2 Dec 31 12:16:02 UNRAID kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth35f53f6: link becomes ready Dec 31 12:16:02 UNRAID rc.docker: paperless-ngx: started succesfully! Dec 31 12:16:03 UNRAID kernel: docker0: port 5(veth3870359) entered blocking state Dec 31 12:16:03 UNRAID kernel: docker0: port 5(veth3870359) entered disabled state Dec 31 12:16:03 UNRAID kernel: device veth3870359 entered promiscuous mode Dec 31 12:16:03 UNRAID kernel: docker0: port 5(veth3870359) entered blocking state Dec 31 12:16:03 UNRAID kernel: docker0: port 5(veth3870359) entered forwarding state Dec 31 12:16:03 UNRAID kernel: docker0: port 5(veth3870359) entered disabled state Dec 31 12:16:03 UNRAID kernel: eth0: renamed from veth7568544 Dec 31 12:16:03 UNRAID kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3870359: link becomes ready Dec 31 12:16:03 UNRAID kernel: docker0: port 5(veth3870359) entered blocking state Dec 31 12:16:03 UNRAID kernel: docker0: port 5(veth3870359) entered forwarding state Dec 31 12:16:03 UNRAID rc.docker: RomM: started succesfully! Dec 31 12:16:04 UNRAID kernel: docker0: port 5(veth3870359) entered disabled state Dec 31 12:16:04 UNRAID kernel: veth7568544: renamed from eth0 Dec 31 12:16:04 UNRAID kernel: docker0: port 5(veth3870359) entered disabled state Dec 31 12:16:04 UNRAID kernel: device veth3870359 left promiscuous mode Dec 31 12:16:04 UNRAID kernel: docker0: port 5(veth3870359) entered disabled state Dec 31 12:16:14 UNRAID kernel: XFS (md1p1): Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0x104ff3bb dinode Dec 31 12:16:14 UNRAID kernel: XFS (md1p1): Unmount and run xfs_repair Dec 31 12:16:14 UNRAID kernel: XFS (md1p1): First 128 bytes of corrupted metadata buffer: Dec 31 12:16:14 UNRAID kernel: 00000000: 49 4e 81 a4 03 02 00 00 00 00 00 63 00 00 00 64 IN.........c...d Dec 31 12:16:14 UNRAID kernel: 00000010: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ Dec 31 12:16:14 UNRAID kernel: 00000020: 35 71 c5 c7 24 75 52 5e 35 71 c5 c7 24 75 52 5e 5q..$uR^5q..$uR^ Dec 31 12:16:14 UNRAID kernel: 00000030: 35 71 e5 56 7d 1e cc d4 00 00 00 00 00 00 4c 46 5q.V}.........LF Dec 31 12:16:14 UNRAID kernel: 00000040: 00 00 00 00 00 00 00 05 00 00 00 00 00 00 00 01 ................ Dec 31 12:16:14 UNRAID kernel: 00000050: 00 00 18 01 00 00 00 00 00 00 00 00 c3 8a c4 ea ................ Dec 31 12:16:14 UNRAID kernel: 00000060: ff ff ff ff 05 27 25 aa 00 00 00 00 00 00 00 09 .....'%......... Dec 31 12:16:14 UNRAID kernel: 00000070: 00 00 00 10 00 03 28 e3 00 00 00 00 00 00 00 08 ......(......... Dec 31 12:16:21 UNRAID kernel: XFS (md1p1): Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0x104ff3bb dinode Dec 31 12:16:21 UNRAID kernel: XFS (md1p1): Unmount and run xfs_repair Dec 31 12:16:21 UNRAID kernel: XFS (md1p1): First 128 bytes of corrupted metadata buffer: Dec 31 12:16:21 UNRAID kernel: 00000000: 49 4e 81 a4 03 02 00 00 00 00 00 63 00 00 00 64 IN.........c...d Dec 31 12:16:21 UNRAID kernel: 00000010: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ Dec 31 12:16:21 UNRAID kernel: 00000020: 35 71 c5 c7 24 75 52 5e 35 71 c5 c7 24 75 52 5e 5q..$uR^5q..$uR^ Dec 31 12:16:21 UNRAID kernel: 00000030: 35 71 e5 56 7d 1e cc d4 00 00 00 00 00 00 4c 46 5q.V}.........LF Dec 31 12:16:21 UNRAID kernel: 00000040: 00 00 00 00 00 00 00 05 00 00 00 00 00 00 00 01 ................ Dec 31 12:16:21 UNRAID kernel: 00000050: 00 00 18 01 00 00 00 00 00 00 00 00 c3 8a c4 ea ................ Dec 31 12:16:21 UNRAID kernel: 00000060: ff ff ff ff 05 27 25 aa 00 00 00 00 00 00 00 09 .....'%......... Dec 31 12:16:21 UNRAID kernel: 00000070: 00 00 00 10 00 03 28 e3 00 00 00 00 00 00 00 08 ......(......... Dec 31 12:16:26 UNRAID kernel: vethce3fe52: renamed from eth0 Dec 31 12:16:28 UNRAID kernel: docker0: port 4(veth35f53f6) entered disabled state Dec 31 12:16:28 UNRAID kernel: veth5e683e2: renamed from eth0 Dec 31 12:16:28 UNRAID kernel: docker0: port 4(veth35f53f6) entered disabled state Dec 31 12:16:28 UNRAID kernel: device veth35f53f6 left promiscuous mode Dec 31 12:16:28 UNRAID kernel: docker0: port 4(veth35f53f6) entered disabled state Dec 31 12:16:33 UNRAID unassigned.devices: Mounting 'Auto Mount' Remote Shares... Dec 31 12:16:33 UNRAID sudo: root : PWD=/ ; USER=root ; COMMAND=/bin/bash -c '/usr/local/emhttp/plugins/unbalance/unbalance -port 6237' Dec 31 12:16:33 UNRAID sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Dec 31 12:16:33 UNRAID unassigned.devices: Using Gateway '192.168.0.1' to Ping Remote Shares. Dec 31 12:16:33 UNRAID unassigned.devices: Waiting 5 secs before mounting Remote Shares... Dec 31 12:17:32 UNRAID kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0 Dec 31 12:17:32 UNRAID kernel: nvme 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Dec 31 12:17:32 UNRAID kernel: nvme 0000:01:00.0: device [15b7:5006] error status/mask=00000001/0000e000 Dec 31 12:17:32 UNRAID kernel: nvme 0000:01:00.0: [ 0] RxErr Dec 31 12:19:27 UNRAID kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0 Dec 31 12:19:27 UNRAID kernel: nvme 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Dec 31 12:19:27 UNRAID kernel: nvme 0000:01:00.0: device [15b7:5006] error status/mask=00000001/0000e000 Dec 31 12:19:27 UNRAID kernel: nvme 0000:01:00.0: [ 0] RxErr Dec 31 12:20:58 UNRAID kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0 Dec 31 12:20:58 UNRAID kernel: nvme 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Dec 31 12:20:58 UNRAID kernel: nvme 0000:01:00.0: device [15b7:5006] error status/mask=00000001/0000e000 Dec 31 12:20:58 UNRAID kernel: nvme 0000:01:00.0: [ 0] RxErr Edited December 31, 2023 by _MARKUS_ Quote Link to comment
_MARKUS_ Posted December 31, 2023 Author Share Posted December 31, 2023 Ich habe jetzt xfs_repair ausgeführt. Da hat es auch was repariert (denke ich) und danach noch iob fix --> Der Container läuft wieder --> habe ich ein Hardware Problem ? Paity und SMART Status ist eigentlich i.o. Quote Link to comment
_MARKUS_ Posted January 1 Author Share Posted January 1 Kann eine XFS Dateisystem beschäftigt sein obwohl Parität i.o.? Soll die Parität eigentlich nicht vor Beschädigungen schützen? Quote Link to comment
Vr2Io Posted January 1 Share Posted January 1 Not likely XFS / parity relate. Pls shoot those PCIe / NVMe error, try re-insert the NVMe or move to different slot. Quote Link to comment
jj1987 Posted January 1 Share Posted January 1 Die NVME ist aber ja nicht im Array?! Also kann die Parity da auch nichts absichern Quote Link to comment
_MARKUS_ Posted January 1 Author Share Posted January 1 @Vr2Io I will try to solve the PCIe / NVMe error. @jj1987 doch in meinem aktuellen Test Setup ist die NVME im Array Quote Link to comment
_MARKUS_ Posted January 2 Author Share Posted January 2 @Vr2Io @all I've been working on resolving the PCIe/NVMe issue, but I've encountered several challenges. Firstly, my motherboard have no second m.2 slot for testing. I came across suggestions to update the BIOS, but unfortunately, the Lenovo M70q doesn't support direct BIOS update direct in BIOS. Consequently, updating it directly on Unraid wasn't possible. Additionally, I considered disabling 'pcie_aspm' in the BIOS as recommended, but this option isn't available either. My next step will be to test the system with different hardware in the coming days. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.