ALameLlama

After much messing around, it seems like there might be an issue with the backplate, when I bypass it and correct it directly to the mobo or HBA, it seems to pick up all 4 drives right away. Imma contact Silverstone to see if I am doing something wrong or if there's an issue with the backplates Thanks again

I am using a Corsair AX 1000 I've tried both molex cables it comes with. I'll see if I can get a SATA to molex adapter to test with. I don't think I am anywhere near the max watts for the PSU itself It is powering an AMD Ryzen 9 5900X and Nvidia 3080. there should still be lots of headroom for the PSU. I power if it's overheating since the SilverStone RM43-320-RS does get a little toasty and the PSU is facing towards the CPU since the case didn't have holes on the other side

rocinante-diagnostics-20241103-1732.zip It seems like one of the drives is really dead? Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#564 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#564 Sense Key : 0x2 [current] Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#564 ASC=0x4 ASCQ=0x0 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#564 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 d2 80 00 00 02 e8 00 00 Nov 2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450482816 op 0x1:(WRITE) flags 0x0 phys_seg 93 prio class 2 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#566 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#566 Sense Key : 0x2 [current] Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#566 ASC=0x4 ASCQ=0x0 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#566 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 ce 80 00 00 04 00 00 00 Nov 2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450481792 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 2 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#567 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#567 Sense Key : 0x2 [current] Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#567 ASC=0x4 ASCQ=0x0 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#567 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 bf e8 00 00 01 28 00 00 Nov 2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450478056 op 0x1:(WRITE) flags 0x0 phys_seg 37 prio class 2 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#568 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#568 Sense Key : 0x2 [current] Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#568 ASC=0x4 ASCQ=0x0 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#568 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 c8 b0 00 00 01 d0 00 00 Nov 2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450480304 op 0x1:(WRITE) flags 0x0 phys_seg 58 prio class 2 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#570 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#570 Sense Key : 0x2 [current] Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#570 ASC=0x4 ASCQ=0x0 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#570 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 c1 10 00 00 01 70 00 00 Nov 2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450478352 op 0x1:(WRITE) flags 0x0 phys_seg 46 prio class 2 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#571 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#571 Sense Key : 0x2 [current] Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#571 ASC=0x4 ASCQ=0x0 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#571 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 c6 48 00 00 01 50 00 00 Nov 2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450479688 op 0x1:(WRITE) flags 0x0 phys_seg 42 prio class 2 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#572 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#572 Sense Key : 0x2 [current] Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#572 ASC=0x4 ASCQ=0x0 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#572 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 c7 98 00 00 01 18 00 00 Nov 2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450480024 op 0x1:(WRITE) flags 0x0 phys_seg 35 prio class 2 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#574 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#574 Sense Key : 0x2 [current] Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#574 ASC=0x4 ASCQ=0x0 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#574 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 ca 80 00 00 04 00 00 00 Nov 2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450480768 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 2 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#575 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#575 Sense Key : 0x2 [current] Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#575 ASC=0x4 ASCQ=0x0 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#575 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 c2 80 00 00 03 c8 00 00 Nov 2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450478720 op 0x1:(WRITE) flags 0x0 phys_seg 121 prio class 2 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#512 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#512 Sense Key : 0x2 [current] Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#512 ASC=0x4 ASCQ=0x0 Nov 2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#512 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 d5 68 00 00 04 00 00 00 Nov 2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450483560 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2 Nov 2 22:35:58 Rocinante kernel: sd 7:0:2:0: [sdd] tag#565 CDB: opcode=0x12 12 00 00 00 24 00 Nov 2 23:30:55 Rocinante emhttpd: spinning down /dev/sdd Nov 2 23:31:39 Rocinante emhttpd: read SMART /dev/sdd If that's the case I'll just need to run without it

Ok, I ended up splitting the drives up into 2 backplates and it's looking better, I am now rebuilding the data and hopefully, it'll be normal this time rocinante-diagnostics-20241103-1617.zip

Hmm, I'll see what I can do about that, I currently have 1 molex cable per backplate (like between the psu and backplate and not sharing the same cable between multiple), I believe there is 2 plugs but the docs say they are for redundant power. I really appreciate the help

I have 2 drives now showing smart errors. I've tried to reformat them and assign them, but the kernel has panicked during the rebuild. I will try to get something to bypass the rake backplate and connect it directly to the HBA to see if that's what is causing the issue. I might also see if there is SATA x4 host to sff-8643 target? I'm not sure if this is a thing. I can only find the host sff-8643 but I want to connect my mobo directly to the backplate to see if the HBA is the issue. I have this diagnostic when I tried to reformat and it didn't seem to do so successfully. I will try to keep debugging it once I get more physical stuff to do so. rocinante-diagnostics-20241102-2230.zip

Here is the diagnostic after starting the array, I should also mention I found this and ran the commands on all 4 drives to disable EPC and low current spinup but the same result, device is disabled rocinante-diagnostics-20241029-2011.zip

I recently set up a new HBA which was pre-flashed and connects to the backplate for SilverStone RM43-320-RS From what I can tell it seems the HBA is initializing correctly and it's reporting 4 drives, but one of the 4 drives is reporting it's disabled I've attached diagnostics tower-diagnostics-20241029-1826.zip Any help is greatly appreciated.

After lots of testing ended up being a dying mobo

Had it kernel panic, The syslog didn't show anything from what I can tell. the syslog-previous just stopped in the middle of what it was doing. I've included the syslog on the reboot in case there is anything useful there. I've started doing another memtest and am gonna leave it over night to see if that'll give more accurate results syslog

Surprisingly, after moving the RAM around, the memtest passes without any issues. I've removed the corrupted files and I'll see if that resolves the issue

It looks like something is wrong with the memory. I've moved the sticks around and am running another mem test to see if it's the stick or the slot.

This was the btrfs scrub, I'll shart the mem test shortly but that will take a while to finish. UUID: 2a375431-ec6e-43a0-95ec-bb06d85a107c Scrub started: Sat Oct 5 20:08:02 2024 Status: finished Duration: 0:05:58 Total to scrub: 870.00GiB Rate: 2.43GiB/s Error summary: csum=10 Corrected: 0 Uncorrectable: 10 Unverified: 0

@itimpi Finally, This is the end of the syslog-previous file that was on the USB after rebooting it after the crash. seems like samba is dying and crashing? Oct 5 03:07:22 Rocinante kernel: eth0: renamed from vethc1e5873 Oct 5 03:07:22 Rocinante kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth135303c: link becomes ready Oct 5 03:07:22 Rocinante kernel: br-fa8dec63aaac: port 7(veth135303c) entered blocking state Oct 5 03:07:22 Rocinante kernel: br-fa8dec63aaac: port 7(veth135303c) entered forwarding state Oct 5 03:08:14 Rocinante kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 5954788 off 1348083712 csum 0xcdeade6f expected csum 0x36e7aeaa mirror 1 Oct 5 03:08:14 Rocinante kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 0, flush 0, corrupt 20, gen 0 Oct 5 03:08:14 Rocinante kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 5954788 off 1348083712 csum 0xcdeade6f expected csum 0x36e7aeaa mirror 1 Oct 5 03:08:14 Rocinante kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 0, flush 0, corrupt 21, gen 0 Oct 5 03:08:15 Rocinante kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 5954429 off 564867072 csum 0xa2e600ff expected csum 0xa78c04e1 mirror 1 Oct 5 03:08:15 Rocinante kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 19, gen 0 Oct 5 03:08:15 Rocinante kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 5954429 off 564867072 csum 0xa2e600ff expected csum 0xa78c04e1 mirror 1 Oct 5 03:08:15 Rocinante kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 20, gen 0 Oct 5 05:00:01 Rocinante Plugin Auto Update: Checking for available plugin updates Oct 5 05:00:01 Rocinante Docker Auto Update: Community Applications Docker Autoupdate running Oct 5 05:00:01 Rocinante Docker Auto Update: Checking for available updates Oct 5 05:00:07 Rocinante Plugin Auto Update: fix.common.problems.plg version 2024.10.02 does not meet age requirements to update - 2 days old Oct 5 05:00:07 Rocinante Plugin Auto Update: folder.view.plg version 2024.10.02 does not meet age requirements to update - 2 days old Oct 5 05:00:07 Rocinante Plugin Auto Update: unassigned.devices.plg version 2024.10.02 does not meet age requirements to update - 2 days old Oct 5 05:00:07 Rocinante Plugin Auto Update: Checking for language updates Oct 5 05:00:07 Rocinante Plugin Auto Update: Community Applications Plugin Auto Update finished Oct 5 05:00:50 Rocinante Docker Auto Update: Found update for redis-auth. Not set to autoupdate Oct 5 05:00:50 Rocinante Docker Auto Update: Found update for redis-pterodactyl. Not set to autoupdate Oct 5 05:00:50 Rocinante Docker Auto Update: Found update for traefik. Not set to autoupdate Oct 5 05:00:50 Rocinante Docker Auto Update: Stopping FileFlows Oct 5 05:01:01 Rocinante kernel: br-fa8dec63aaac: port 23(vethb4465c7) entered disabled state Oct 5 05:01:01 Rocinante kernel: vethd7e54eb: renamed from eth0 Oct 5 05:01:01 Rocinante kernel: br-fa8dec63aaac: port 23(vethb4465c7) entered disabled state Oct 5 05:01:01 Rocinante kernel: device vethb4465c7 left promiscuous mode Oct 5 05:01:01 Rocinante kernel: br-fa8dec63aaac: port 23(vethb4465c7) entered disabled state Oct 5 05:01:02 Rocinante Docker Auto Update: Installing Updates for FileFlows Oct 5 05:02:26 Rocinante Docker Auto Update: Restarting FileFlows Oct 5 05:02:26 Rocinante kernel: br-fa8dec63aaac: port 23(vethc20ee0e) entered blocking state Oct 5 05:02:26 Rocinante kernel: br-fa8dec63aaac: port 23(vethc20ee0e) entered disabled state Oct 5 05:02:26 Rocinante kernel: device vethc20ee0e entered promiscuous mode Oct 5 05:02:28 Rocinante kernel: eth0: renamed from veth05326fa Oct 5 05:02:28 Rocinante kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc20ee0e: link becomes ready Oct 5 05:02:28 Rocinante kernel: br-fa8dec63aaac: port 23(vethc20ee0e) entered blocking state Oct 5 05:02:28 Rocinante kernel: br-fa8dec63aaac: port 23(vethc20ee0e) entered forwarding state Oct 5 05:02:29 Rocinante Docker Auto Update: Community Applications Docker Autoupdate finished Oct 5 17:42:12 Rocinante webGUI: Successful login user root from 192.168.1.165 Oct 5 18:03:31 Rocinante smbd[13056]: [2024/10/05 18:03:31.674881, 0] ../../source3/smbd/close.c:1485(close_directory) Oct 5 18:03:31 Rocinante smbd[13056]: Could not close dir! fname=torrents/Ethically-sourced-media fd=40, err=116=Stale file handle Oct 5 18:03:31 Rocinante smbd[13056]: [2024/10/05 18:03:31.674949, 0] ../../source3/smbd/fd_handle.c:39(fd_handle_destructor) Oct 5 18:03:31 Rocinante smbd[13056]: PANIC: assert failed at ../../source3/smbd/fd_handle.c(39): (fh->fd == -1) || (fh->fd == AT_FDCWD) Oct 5 18:03:31 Rocinante smbd[13056]: [2024/10/05 18:03:31.674960, 0] ../../lib/util/fault.c:173(smb_panic_log) Oct 5 18:03:31 Rocinante smbd[13056]: =============================================================== Oct 5 18:03:31 Rocinante smbd[13056]: [2024/10/05 18:03:31.674969, 0] ../../lib/util/fault.c:174(smb_panic_log) Oct 5 18:03:31 Rocinante smbd[13056]: INTERNAL ERROR: assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in pid 13056 (4.17.12) Oct 5 18:03:31 Rocinante smbd[13056]: [2024/10/05 18:03:31.674974, 0] ../../lib/util/fault.c:178(smb_panic_log) Oct 5 18:03:31 Rocinante smbd[13056]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting Oct 5 18:03:31 Rocinante smbd[13056]: [2024/10/05 18:03:31.674980, 0] ../../lib/util/fault.c:183(smb_panic_log) Oct 5 18:03:31 Rocinante smbd[13056]: =============================================================== Oct 5 18:03:31 Rocinante smbd[13056]: [2024/10/05 18:03:31.674984, 0] ../../lib/util/fault.c:184(smb_panic_log) Oct 5 18:03:31 Rocinante smbd[13056]: PANIC (pid 13056): assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in 4.17.12 Oct 5 18:03:31 Rocinante smbd[13056]: [2024/10/05 18:03:31.675188, 0] ../../lib/util/fault.c:292(log_stack_trace) Oct 5 18:03:31 Rocinante smbd[13056]: BACKTRACE: 27 stack frames: Oct 5 18:03:31 Rocinante smbd[13056]: #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x148db832064e] Oct 5 18:03:31 Rocinante smbd[13056]: #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x148db83208a9] Oct 5 18:03:31 Rocinante smbd[13056]: #2 /usr/lib64/libsmbd-base-samba4.so(+0x4d0fb) [0x148db87020fb] Oct 5 18:03:31 Rocinante smbd[13056]: #3 /usr/lib64/libtalloc.so.2(+0x44df) [0x148db82cf4df] Oct 5 18:03:31 Rocinante smbd[13056]: #4 /usr/lib64/libsmbd-base-samba4.so(file_free+0xd6) [0x148db870f266] Oct 5 18:03:31 Rocinante smbd[13056]: #5 /usr/lib64/libsmbd-base-samba4.so(+0xc0781) [0x148db8775781] Oct 5 18:03:31 Rocinante smbd[13056]: #6 /usr/lib64/libsmbd-base-samba4.so(smbd_smb2_request_process_close+0x211) [0x148db8775f01] Oct 5 18:03:31 Rocinante smbd[13056]: #7 /usr/lib64/libsmbd-base-samba4.so(smbd_smb2_request_dispatch+0xdfa) [0x148db8769bfa] Oct 5 18:03:31 Rocinante smbd[13056]: #8 /usr/lib64/libsmbd-base-samba4.so(+0xb5bc1) [0x148db876abc1] Oct 5 18:03:31 Rocinante smbd[13056]: #9 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x148db82e28c1] Oct 5 18:03:31 Rocinante smbd[13056]: #10 /usr/lib64/libtevent.so.0(+0xee07) [0x148db82e8e07] Oct 5 18:03:31 Rocinante smbd[13056]: #11 /usr/lib64/libtevent.so.0(+0xcef7) [0x148db82e6ef7] Oct 5 18:03:31 Rocinante smbd[13056]: #12 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x148db82e1ba1] Oct 5 18:03:31 Rocinante smbd[13056]: #13 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x148db82e1e7b] Oct 5 18:03:31 Rocinante smbd[13056]: #14 /usr/lib64/libtevent.so.0(+0xce97) [0x148db82e6e97] Oct 5 18:03:31 Rocinante smbd[13056]: #15 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x148db8758be7] Oct 5 18:03:31 Rocinante smbd[13056]: #16 /usr/sbin/smbd(+0xb090) [0x55efeb70b090] Oct 5 18:03:31 Rocinante smbd[13056]: #17 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x148db82e28c1] Oct 5 18:03:31 Rocinante smbd[13056]: #18 /usr/lib64/libtevent.so.0(+0xee07) [0x148db82e8e07] Oct 5 18:03:31 Rocinante smbd[13056]: #19 /usr/lib64/libtevent.so.0(+0xcef7) [0x148db82e6ef7] Oct 5 18:03:31 Rocinante smbd[13056]: #20 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x148db82e1ba1] Oct 5 18:03:31 Rocinante smbd[13056]: #21 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x148db82e1e7b] Oct 5 18:03:31 Rocinante smbd[13056]: #22 /usr/lib64/libtevent.so.0(+0xce97) [0x148db82e6e97] Oct 5 18:03:31 Rocinante smbd[13056]: #23 /usr/sbin/smbd(main+0x1489) [0x55efeb708259] Oct 5 18:03:31 Rocinante smbd[13056]: #24 /lib64/libc.so.6(+0x236b7) [0x148db80e86b7] Oct 5 18:03:31 Rocinante smbd[13056]: #25 /lib64/libc.so.6(__libc_start_main+0x85) [0x148db80e8775] Oct 5 18:03:31 Rocinante smbd[13056]: #26 /usr/sbin/smbd(_start+0x21) [0x55efeb708b31] Oct 5 18:03:31 Rocinante smbd[13056]: [2024/10/05 18:03:31.675254, 0] ../../source3/lib/dumpcore.c:315(dump_core) Oct 5 18:03:31 Rocinante smbd[13056]: dumping core in /var/log/samba/cores/smbd Oct 5 18:03:31 Rocinante smbd[13056]:

It seems to be a case of Schrödinger's crash, Ever since I've enabled mirroring the syslog to the USB, it's been stable. I'll leave it over the weekend if nothing happens. I'll disable it again and see if that's any different

I've enabled that now, I'll update you once it's done it again. Thanks

I recently updated to 6.12.13 and had some weird issues with Unraid being unresponsive after some time, I've had it die almost instantly after starting my array and also after a few days of it working without any issues. At first, I thought it was the jumbo package issue since I have an RTL8111 NIC but I have the driver installed. But I also noticed that when I physically plugged in a keyboard/monitor I didn't get any response until I restarted it. I've attached the diagnostics after it's crashed and I've restarted without starting arrays or anything else, any advice would be greatly appreciated rocinante-diagnostics-20240930-2336.zip

This ended up being gluetun messing up my interfaces on the host. reset it gluetun and that resolved my issues after a reboot

I ended up shutting down all the docker containers to see if that was messing with the interfaces but even with them all down, unraid still doesn't seem to have internet connection outbound

rocinante-diagnostics-20240911-2032.zip

Hey All, I have a power outage and on restart, I've had some weird network issues since restarting. When I restart and remove I mount the array, I have full network on unraid, I can ping google etc. When I mount the array (which starts all my docker containers) I have a connection for about 10 seconds and then it dies, I can still access the web Ui but unraid can't reach Google and all my docker containers show they are up but the web UI and stuff are unreachable and the logs show it is timing out as the try reach external things. Pinging during the array start, the 400ms change ``` root@Rocinante:~# ping google.com PING google.com (142.250.70.206) 56(84) bytes of data. 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=1 ttl=60 time=2.74 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=2 ttl=60 time=1.90 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=3 ttl=60 time=1.94 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=4 ttl=60 time=2.80 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=5 ttl=60 time=2.00 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=6 ttl=60 time=2.14 ms ... 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=65 ttl=60 time=2.10 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=66 ttl=60 time=2.12 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=67 ttl=60 time=2.74 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=68 ttl=60 time=2.72 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=69 ttl=110 time=404 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=70 ttl=110 time=405 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=71 ttl=110 time=404 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=72 ttl=110 time=405 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=73 ttl=110 time=405 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=74 ttl=110 time=405 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=75 ttl=110 time=404 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=76 ttl=110 time=407 ms ``` After ``` root@Rocinante:~# ping google.com PING google.com (142.250.70.174) 56(84) bytes of data. ^C --- google.com ping statistics --- 8 packets transmitted, 0 received, 100% packet loss, time 7149ms ``` I noticed this getting spammed in my syslog ``` Sep 11 20:26:05 Rocinante kernel: vethd9cdd38: renamed from eth0 Sep 11 20:26:05 Rocinante kernel: br-fa8dec63aaac: port 2(vethcb937c5) entered disabled state Sep 11 20:26:06 Rocinante kernel: br-fa8dec63aaac: port 2(vethcb937c5) entered disabled state Sep 11 20:26:06 Rocinante kernel: device vethcb937c5 left promiscuous mode Sep 11 20:26:06 Rocinante kernel: br-fa8dec63aaac: port 2(vethcb937c5) entered disabled state Sep 11 20:26:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered blocking state Sep 11 20:26:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered disabled state Sep 11 20:26:08 Rocinante kernel: device veth7108d6a entered promiscuous mode Sep 11 20:26:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered blocking state Sep 11 20:26:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered forwarding state Sep 11 20:26:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered disabled state Sep 11 20:26:10 Rocinante kernel: eth0: renamed from vetha9d430b Sep 11 20:26:10 Rocinante kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7108d6a: link becomes ready Sep 11 20:26:10 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered blocking state Sep 11 20:26:10 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered forwarding state Sep 11 20:29:02 Rocinante kernel: veth653fe1e: renamed from eth0 Sep 11 20:29:02 Rocinante kernel: br-fa8dec63aaac: port 1(veth247469c) entered disabled state Sep 11 20:29:02 Rocinante kernel: br-fa8dec63aaac: port 1(veth247469c) entered disabled state Sep 11 20:29:02 Rocinante kernel: device veth247469c left promiscuous mode Sep 11 20:29:02 Rocinante kernel: br-fa8dec63aaac: port 1(veth247469c) entered disabled state Sep 11 20:29:05 Rocinante kernel: br-fa8dec63aaac: port 1(vethbceda4d) entered blocking state Sep 11 20:29:05 Rocinante kernel: br-fa8dec63aaac: port 1(vethbceda4d) entered disabled state Sep 11 20:29:05 Rocinante kernel: device vethbceda4d entered promiscuous mode Sep 11 20:29:06 Rocinante kernel: eth0: renamed from veth9a12e9a Sep 11 20:29:06 Rocinante kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbceda4d: link becomes ready Sep 11 20:29:06 Rocinante kernel: br-fa8dec63aaac: port 1(vethbceda4d) entered blocking state Sep 11 20:29:06 Rocinante kernel: br-fa8dec63aaac: port 1(vethbceda4d) entered forwarding state Sep 11 20:29:07 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered disabled state Sep 11 20:29:07 Rocinante kernel: vetha9d430b: renamed from eth0 Sep 11 20:29:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered disabled state Sep 11 20:29:08 Rocinante kernel: device veth7108d6a left promiscuous mode Sep 11 20:29:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered disabled state Sep 11 20:29:10 Rocinante kernel: br-fa8dec63aaac: port 2(veth69c3a92) entered blocking state Sep 11 20:29:10 Rocinante kernel: br-fa8dec63aaac: port 2(veth69c3a92) entered disabled state Sep 11 20:29:10 Rocinante kernel: device veth69c3a92 entered promiscuous mode Sep 11 20:29:12 Rocinante kernel: eth0: renamed from vethc75d97f Sep 11 20:29:12 Rocinante kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth69c3a92: link becomes ready Sep 11 20:29:12 Rocinante kernel: br-fa8dec63aaac: port 2(veth69c3a92) entered blocking state Sep 11 20:29:12 Rocinante kernel: br-fa8dec63aaac: port 2(veth69c3a92) entered forwarding state ``` I have DHCP starting at 100 and have a static IP set on the unraid machine below DHCP. Im honestly kinda stumped at what might be causing things.

Legend, Looks like they mounted after a reformat and they seem to be working. I screwed up my backup/restore but the cache drives are mounted and I can worry about fixing up my docker/vm since there wasn't anything important there Thanks

Diagnostics after starting the array with the cache drives. rocinante-diagnostics-20240114-2302.zip

Looks like that allowed the cache drives to mount but they are read only by the looks of it. I can't start some VM's and docker contrains. Getting errors like this: Postgres docker 2024-01-08 02:17:29.393 AEDT [4270] FATAL: could not open file "base/16384/2601": Read-only file system 2024-01-08 02:17:29.403 AEDT [4271] FATAL: could not open file "base/16384/2601": Read-only file system 2024-01-08 02:17:29.412 AEDT [4272] FATAL: could not open file "base/16384/2601": Read-only file system chmod: changing permissions of '/var/lib/postgresql/data': Read-only file system chmod: changing permissions of '/var/lib/postgresql/data': Read-only file system 2024-01-14 22:39:53.519 AEDT [1] FATAL: could not remove old lock file "postmaster.pid": Read-only file system 2024-01-14 22:39:53.519 AEDT [1] HINT: The file seems accidentally left over, but it could not be removed. Please remove the file by hand and try again. Debian VM internal error: qemu unexpectedly closed the monitor: 2024-01-14T11:46:19.378780Z qemu-system-x86_64: -device {"driver":"virtio-blk-pci","bus":"pci.4","addr":"0x0","drive":"libvirt-2-format","id":"virtio-disk2","bootindex":1,"write-cache":"on","serial":"vdisk1"}: Could not open '/mnt/cache/domains-ssd/VSVR-71-Workshop/vdisk1.img': Read-only file system

Updated to 6.12.6 and it was running well for a day and then it turned off. when I rebooted and started the array both the cache m.2 drives are unmountable. Any help would be nice thanks rocinante-diagnostics-20240114-1351.zip