Abbell
Members
-
Joined
-
Last visited
-
So far it looks like it was Guacamole. I had a broken share path.
-
Thank you @Kilrah I will power down all the dockers and bring them up one at a time to see if I can isolate the culprit.
-
Good morning, I have been going around in circles trying to determine why I have constant disk reads pinging all my drives. This has been preventing the drives from spinning down for months. I have poured through various forum posts and tried several troubleshooting steps to no avail. I do not post often as I like to find my own solutions, but I am stumped. Can I ask for assistance, please? I would like to reduce the wear and tear, heat, and power usage on my drives. I need to figure out what setting I have wrong that could be the root cause for the drives never spinning down like they used to. tower-diagnostics-20250506-0743.zip
-
I have been getting kernel panics fairly often and it has caused me to lose 5TB of data as it caused my drives to lose stability while performing rebuilds. I have set the syslog so I can see what is happening before such failures. So I am watching the logs as diligently as I can. Rebuilds take more than a day and fails have already forced me to lose an entire drive. un 19 15:10:14 Tower kernel: CPU: 36 PID: 0 Comm: swapper/36 Tainted: P O 5.15.46-Unraid #1 Jun 19 15:10:14 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. TRX40 AORUS MASTER/TRX40 AORUS MASTER, BIOS F5q 04/12/2021 Jun 19 15:10:14 Tower kernel: RIP: 0010:refcount_warn_saturate+0xa7/0xe8 Jun 19 15:10:14 Tower kernel: Code: 05 f1 5a fb 00 01 e8 d8 66 42 00 0f 0b c3 80 3d e1 5a fb 00 00 75 53 48 c7 c7 fa a6 0f 82 c6 05 d1 5a fb 00 01 e8 b9 66 42 00 <0f> 0b c3 80 3d c1 5a fb 00 00 75 34 48 c7 c7 22 a7 0f 82 c6 05 b1 Jun 19 15:10:14 Tower kernel: RSP: 0018:ffffc90000d28eb0 EFLAGS: 00010282 Jun 19 15:10:14 Tower kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027 Jun 19 15:10:14 Tower kernel: RDX: 0000000000000003 RSI: ffffc90000d28d38 RDI: ffff889ffd91c510 Jun 19 15:10:14 Tower kernel: RBP: ffff888137cacc40 R08: ffff88a07f0da6a8 R09: ffffffff8284e288 Jun 19 15:10:14 Tower kernel: R10: 00000fffffffffff R11: 000000002d2d2d2d R12: 0000000000000000 Jun 19 15:10:14 Tower kernel: R13: 0000000000000006 R14: ffff888137cad5e0 R15: ffff888100ab9e80 Jun 19 15:10:14 Tower kernel: FS: 0000000000000000(0000) GS:ffff889ffd900000(0000) knlGS:0000000000000000 Jun 19 15:10:14 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 19 15:10:14 Tower kernel: CR2: 00000000005c3958 CR3: 000000000620a000 CR4: 0000000000350ee0 Jun 19 15:10:14 Tower kernel: Call Trace: Jun 19 15:10:14 Tower kernel: <IRQ> Jun 19 15:10:14 Tower kernel: refcount_dec_and_test+0x24/0x2a Jun 19 15:10:14 Tower kernel: __put_task_struct+0x98/0xaf Jun 19 15:10:14 Tower kernel: rcu_do_batch+0x216/0x40a Jun 19 15:10:14 Tower kernel: rcu_core+0x1c2/0x1f3 Jun 19 15:10:14 Tower kernel: ? timekeeping_get_ns+0x1c/0x32 Jun 19 15:10:14 Tower kernel: __do_softirq+0xef/0x218 Jun 19 15:10:14 Tower kernel: __irq_exit_rcu+0x4d/0x88 Jun 19 15:10:14 Tower kernel: sysvec_apic_timer_interrupt+0x66/0x7d Jun 19 15:10:14 Tower kernel: </IRQ> Jun 19 15:10:14 Tower kernel: <TASK> Jun 19 15:10:14 Tower kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Jun 19 15:10:14 Tower kernel: RIP: 0010:arch_local_irq_enable+0x7/0x8 Jun 19 15:10:14 Tower kernel: Code: a2 bc 1c 00 85 db 48 89 e8 79 03 48 63 c3 5b 5d 41 5c c3 9c 58 0f 1f 44 00 00 c3 fa 66 0f 1f 44 00 00 c3 fb 66 0f 1f 44 00 00 <c3> 0f 1f 44 00 00 55 49 89 d3 48 81 c7 b0 00 00 00 48 83 c6 70 53 Jun 19 15:10:14 Tower kernel: RSP: 0018:ffffc9000041fea0 EFLAGS: 00000246 Jun 19 15:10:14 Tower kernel: RAX: ffff889ffd92bb40 RBX: 0000000000000001 RCX: 000000000000001f Jun 19 15:10:14 Tower kernel: RDX: 0000000000000024 RSI: 0000000000000024 RDI: 0000000000000000 Jun 19 15:10:14 Tower kernel: RBP: ffff88810b2d0c00 R08: 00000000ffffffff R09: 071c71c71c71c71c Jun 19 15:10:14 Tower kernel: R10: 0000000000000020 R11: 0000000000000021 R12: ffffffff82314da0 Jun 19 15:10:14 Tower kernel: R13: 0000000000000001 R14: 0000173a0ba852f5 R15: 0000000000000000 Jun 19 15:10:14 Tower kernel: cpuidle_enter_state+0x117/0x1db Jun 19 15:10:14 Tower kernel: cpuidle_enter+0x2a/0x36 Jun 19 15:10:14 Tower kernel: do_idle+0x1b7/0x225 Jun 19 15:10:14 Tower kernel: cpu_startup_entry+0x1d/0x1f Jun 19 15:10:14 Tower kernel: secondary_startup_64_no_verify+0xb0/0xbb Jun 19 15:10:14 Tower kernel: </TASK> This has caused me no small amount of anxiety. I have to have a stable system. tower-diagnostics-20220619-1612.zip
-
Other than the custom case being evil... I have 3 16TB drives almost ready to replace 8's. I have to find out why one drive bay is not connecting though first.
