b_tob Posted May 21, 2022 Share Posted May 21, 2022 Hallo zusammen es war wieder mal soweit, mein Unraid Server ist gecrasht. Gestern musste ich nachdem ich den Server sauber heruntergefahren und wieder gestartet habe einen Parity Check machen, der lief gemäss Telegram Bot von 12:33 - 23:55 Uhr. Vorhin wollte ich nun auf die WebGUI bzw. auf eine Win10 VM zugreifen, jedoch herrschte nur tote Hose. In den Logs, welche auf den USB Stick geschrieben wurden, taucht seit heute Morgen bis zum Neustart vorhin alle 3 Minuten folgende Meldung auf: May 21 07:35:57 ZEUS kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks: May 21 07:35:57 ZEUS kernel: rcu: 1-...0: (0 ticks this GP) idle=8da/1/0x4000000000000000 softirq=4172968/4172968 fqs=14257 May 21 07:35:57 ZEUS kernel: (detected by 11, t=60002 jiffies, g=7699541, q=7220) May 21 07:35:57 ZEUS kernel: Sending NMI from CPU 11 to CPUs 1: May 21 07:35:57 ZEUS kernel: NMI backtrace for cpu 1 May 21 07:35:57 ZEUS kernel: CPU: 1 PID: 20211 Comm: sh Tainted: G O 5.10.28-Unraid #1 May 21 07:35:57 ZEUS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B460M Pro4, BIOS P1.50 08/31/2020 May 21 07:35:57 ZEUS kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x79/0x18a May 21 07:35:57 ZEUS kernel: Code: c1 e0 08 89 c2 8b 07 30 e4 09 d0 a9 00 01 ff ff 74 0c 0f ba e0 08 72 1a c6 47 01 00 eb 14 85 c0 74 0a 8b 07 84 c0 74 04 f3 90 <eb> f6 66 c7 07 01 00 c3 48 c7 c0 00 30 02 00 65 48 03 05 f0 8e f8 May 21 07:35:57 ZEUS kernel: RSP: 0018:ffffc90000160e58 EFLAGS: 00000002 May 21 07:35:57 ZEUS kernel: RAX: 0000000000040101 RBX: ffffc90000160e80 RCX: 0000000000000000 May 21 07:35:57 ZEUS kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888100881540 May 21 07:35:57 ZEUS kernel: RBP: ffff8881024f3000 R08: ffffffff82013888 R09: ffffffff82013580 May 21 07:35:57 ZEUS kernel: R10: 0000b585e8f2d58a R11: 0000000000000000 R12: 0000000000000000 May 21 07:35:57 ZEUS kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 000003508e77bc22 May 21 07:35:57 ZEUS kernel: FS: 0000153eb1464740(0000) GS:ffff88844f640000(0000) knlGS:0000000000000000 May 21 07:35:57 ZEUS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 21 07:35:57 ZEUS kernel: CR2: 0000153eb14f0f10 CR3: 0000000046ebc005 CR4: 00000000003726e0 May 21 07:35:57 ZEUS kernel: Call Trace: May 21 07:35:57 ZEUS kernel: <IRQ> May 21 07:35:57 ZEUS kernel: queued_spin_lock_slowpath+0x7/0xa May 21 07:35:57 ZEUS kernel: nr_blockdev_pages+0x13/0x64 May 21 07:35:57 ZEUS kernel: si_meminfo+0x3a/0x57 May 21 07:35:57 ZEUS kernel: Sys_MemInfo+0x20/0x9b [corefreqk] May 21 07:35:57 ZEUS kernel: ? irq_work_run_list+0x2f/0x36 May 21 07:35:57 ZEUS kernel: ? asm_sysvec_irq_work+0x12/0x20 May 21 07:35:57 ZEUS kernel: ? timekeeping_get_ns+0x19/0x2f May 21 07:35:57 ZEUS kernel: ? Sys_DumpTask+0xe9/0xf1 [corefreqk] May 21 07:35:57 ZEUS kernel: Cycle_Skylake+0x53a/0x730 [corefreqk] May 21 07:35:57 ZEUS kernel: __hrtimer_run_queues+0xb7/0x10b May 21 07:35:57 ZEUS kernel: ? Cycle_Skylake_X+0x711/0x711 [corefreqk] May 21 07:35:57 ZEUS kernel: hrtimer_interrupt+0x8d/0x15b May 21 07:35:57 ZEUS kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 May 21 07:35:57 ZEUS kernel: asm_call_irq_on_stack+0xf/0x20 May 21 07:35:57 ZEUS kernel: </IRQ> May 21 07:35:57 ZEUS kernel: sysvec_apic_timer_interrupt+0x71/0x95 May 21 07:35:57 ZEUS kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 May 21 07:35:57 ZEUS kernel: RIP: 0010:nr_blockdev_pages+0x41/0x64 May 21 07:35:57 ZEUS kernel: Code: b5 f9 00 45 31 c0 48 8b 87 48 05 00 00 48 8d 97 48 05 00 00 48 2d 10 01 00 00 48 8d 88 10 01 00 00 48 39 d1 74 17 48 8b 48 30 <48> 8b 80 10 01 00 00 4c 03 41 58 48 2d 10 01 00 00 eb dd 48 81 c7 May 21 07:35:57 ZEUS kernel: RSP: 0018:ffffc9000155fe78 EFLAGS: 00000202 May 21 07:35:57 ZEUS kernel: RAX: ffff8881051f06b8 RBX: ffffc9000155fec0 RCX: ffff8881051f0828 May 21 07:35:57 ZEUS kernel: RDX: ffff888100881548 RSI: 000000000000d4c0 RDI: ffff888100881000 May 21 07:35:57 ZEUS kernel: RBP: ffffc9000155feb0 R08: 0000000000000000 R09: 0000000000000000 May 21 07:35:57 ZEUS kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffffc9000155fec0 May 21 07:35:57 ZEUS kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 May 21 07:35:57 ZEUS kernel: ? nr_blockdev_pages+0x13/0x64 May 21 07:35:57 ZEUS kernel: si_meminfo+0x3a/0x57 May 21 07:35:57 ZEUS kernel: do_sysinfo+0x95/0x12e May 21 07:35:57 ZEUS kernel: __do_sys_sysinfo+0x20/0x59 May 21 07:35:57 ZEUS kernel: do_syscall_64+0x5d/0x6a May 21 07:35:57 ZEUS kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 May 21 07:35:57 ZEUS kernel: RIP: 0033:0x153eb157e307 May 21 07:35:57 ZEUS kernel: Code: f0 ff ff 73 01 c3 48 8b 0d 86 7b 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 b8 63 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 59 7b 0c 00 f7 d8 64 89 01 48 May 21 07:35:57 ZEUS kernel: RSP: 002b:00007ffd63038fd8 EFLAGS: 00000202 ORIG_RAX: 0000000000000063 May 21 07:35:57 ZEUS kernel: RAX: ffffffffffffffda RBX: 000000000048bdf0 RCX: 0000153eb157e307 May 21 07:35:57 ZEUS kernel: RDX: 0000153eb16098d8 RSI: 000000000000004c RDI: 00007ffd63038fe0 May 21 07:35:57 ZEUS kernel: RBP: 0000000000000055 R08: 0000000000000000 R09: fffffffffffffc00 May 21 07:35:57 ZEUS kernel: R10: 0000000000418012 R11: 0000000000000202 R12: 00000000000004f0 May 21 07:35:57 ZEUS kernel: R13: 00000000004d8504 R14: 0000000000000000 R15: 0000000000000030 Weiss jemand was das bedeutet? Den Syslog und die Diagnostics hänge ich für weiter Informationen ebenfalls noch an. Vielen Dank. Beste Grüsse syslog zeus-diagnostics-20220521-2203.zip Quote Link to comment
mgutt Posted May 22, 2022 Share Posted May 22, 2022 Starte mal eine Reparatur auf allen Disks (auf die Disk klicken und xfs_repair ausführen) und einen scrub im Pool (falls BTRFS). Wurden irgendwo Fehler korrigiert? Quote Link to comment
b_tob Posted May 22, 2022 Author Share Posted May 22, 2022 Muss das Array dazu im Wartungsmodus gestartet werden? Wenn ich auf die Disk klicke sehe ich nur "Dateisystem Überprüfungsstatus", das kann ich aber nur auswählen wenn das Array im Wartungsmodus ist, xfs_repair sehe ich leider nirgendwo. Quote Link to comment
mgutt Posted May 22, 2022 Share Posted May 22, 2022 Ja genau der Punkt ist das. Da erscheint dann im Wartungsmodus die Repair Option. Erst mit einem Buchstaben, aber den kannst du gleich rauslöschen, damit der eine reale Reparatur ausführt. Quote Link to comment
b_tob Posted May 22, 2022 Author Share Posted May 22, 2022 Festplatte 1 gab folgende Rückmeldung: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 5 - agno = 4 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done Festplatte 2: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 4 - agno = 2 - agno = 5 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done Wurde da jetzt etwas repariert? 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.