My Unraid seems unstable. The SMB stops working erratically. WebUi is working, but file share shuts down.
Attaching some logs. Please help!

 

Aug  4 00:32:51 nasone smbd[32453]:   ===============================================================
Aug  4 00:32:51 nasone smbd[32453]: [2023/08/04 00:32:51.923772,  0] ../../lib/util/fault.c:174(smb_panic_log)
Aug  4 00:32:51 nasone smbd[32453]:   INTERNAL ERROR: Signal 11: Segmentation fault in pid 32453 (4.17.7)
Aug  4 00:32:51 nasone smbd[32453]: [2023/08/04 00:32:51.923799,  0] ../../lib/util/fault.c:178(smb_panic_log)
Aug  4 00:32:51 nasone smbd[32453]:   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
Aug  4 00:32:51 nasone smbd[32453]: [2023/08/04 00:32:51.923822,  0] ../../lib/util/fault.c:183(smb_panic_log)
Aug  4 00:32:51 nasone smbd[32453]:   ===============================================================
Aug  4 00:32:51 nasone smbd[32453]: [2023/08/04 00:32:51.923846,  0] ../../lib/util/fault.c:184(smb_panic_log)
Aug  4 00:32:51 nasone smbd[32453]:   PANIC (pid 32453): Signal 11: Segmentation fault in 4.17.7
Aug  4 00:32:51 nasone smbd[32453]: [2023/08/04 00:32:51.924489,  0] ../../lib/util/fault.c:292(log_stack_trace)
Aug  4 00:32:51 nasone smbd[32453]:   BACKTRACE: 26 stack frames:
Aug  4 00:32:51 nasone smbd[32453]:    #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x14659e38c64e]
Aug  4 00:32:51 nasone smbd[32453]:    #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x14659e38c8a9]
Aug  4 00:32:51 nasone smbd[32453]:    #2 /usr/lib64/libgenrand-samba4.so(+0x2937) [0x14659e38c937]
Aug  4 00:32:51 nasone smbd[32453]:    #3 /lib64/libc.so.6(+0x3ae20) [0x14659e16de20]
Aug  4 00:32:51 nasone smbd[32453]:    #4 /lib64/libc.so.6(+0x96b12) [0x14659e1c9b12]
Aug  4 00:32:51 nasone smbd[32453]:    #5 /lib64/libc.so.6(+0x99238) [0x14659e1cc238]
Aug  4 00:32:51 nasone smbd[32453]:    #6 /lib64/libc.so.6(malloc+0x1a2) [0x14659e1cd402]
Aug  4 00:32:51 nasone smbd[32453]:    #7 /usr/lib64/libtalloc.so.2(+0x5b6e) [0x14659e33cb6e]
Aug  4 00:32:51 nasone smbd[32453]:    #8 /usr/lib64/libtalloc.so.2(talloc_pool+0x25) [0x14659e33d1e5]
Aug  4 00:32:51 nasone smbd[32453]:    #9 /usr/lib64/libsamba-util.so.0(+0x223d3) [0x14659e5283d3]
Aug  4 00:32:51 nasone smbd[32453]:    #10 /usr/lib64/libsmbd-base-samba4.so(+0xa0b7e) [0x14659e7c1b7e]
Aug  4 00:32:51 nasone smbd[32453]:    #11 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x85) [0x14659e34db95]
Aug  4 00:32:51 nasone smbd[32453]:    #12 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x14659e34de7b]
Aug  4 00:32:51 nasone smbd[32453]:    #13 /usr/lib64/libtevent.so.0(+0xce97) [0x14659e352e97]
Aug  4 00:32:51 nasone smbd[32453]:    #14 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x14659e7c4a37]
Aug  4 00:32:51 nasone smbd[32453]:    #15 /usr/sbin/smbd(+0xb090) [0x56441466a090]
Aug  4 00:32:51 nasone smbd[32453]:    #16 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x14659e34e8c1]
Aug  4 00:32:51 nasone smbd[32453]:    #17 /usr/lib64/libtevent.so.0(+0xee07) [0x14659e354e07]
Aug  4 00:32:51 nasone smbd[32453]:    #18 /usr/lib64/libtevent.so.0(+0xcef7) [0x14659e352ef7]
Aug  4 00:32:51 nasone smbd[32453]:    #19 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x14659e34dba1]
Aug  4 00:32:51 nasone smbd[32453]:    #20 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x14659e34de7b]
Aug  4 00:32:51 nasone smbd[32453]:    #21 /usr/lib64/libtevent.so.0(+0xce97) [0x14659e352e97]
Aug  4 00:32:51 nasone smbd[32453]:    #22 /usr/sbin/smbd(main+0x1489) [0x564414667259]
Aug  4 00:32:51 nasone smbd[32453]:    #23 /lib64/libc.so.6(+0x236b7) [0x14659e1566b7]
Aug  4 00:32:51 nasone smbd[32453]:    #24 /lib64/libc.so.6(__libc_start_main+0x85) [0x14659e156775]
Aug  4 00:32:51 nasone smbd[32453]:    #25 /usr/sbin/smbd(_start+0x21) [0x564414667b31]
Aug  4 00:32:51 nasone smbd[32453]: [2023/08/04 00:32:51.924714,  0] ../../source3/lib/dumpcore.c:315(dump_core)
Aug  4 00:32:51 nasone smbd[32453]:   dumping core in /var/log/samba/cores/smbd
Aug  4 00:32:51 nasone smbd[32453]: 
Aug  4 00:32:53 nasone smbd[32464]: [2023/08/04 00:32:53.486474,  0] ../../lib/util/fault.c:173(smb_panic_log)
Aug  4 00:32:53 nasone smbd[32464]:   ===============================================================
Aug  4 00:32:53 nasone smbd[32464]: [2023/08/04 00:32:53.486585,  0] ../../lib/util/fault.c:174(smb_panic_log)
Aug  4 00:32:53 nasone smbd[32464]:   INTERNAL ERROR: Signal 11: Segmentation fault in pid 32464 (4.17.7)
Aug  4 00:32:53 nasone smbd[32464]: [2023/08/04 00:32:53.486621,  0] ../../lib/util/fault.c:178(smb_panic_log)
Aug  4 00:32:53 nasone smbd[32464]:   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
Aug  4 00:32:53 nasone smbd[32464]: [2023/08/04 00:32:53.486663,  0] ../../lib/util/fault.c:183(smb_panic_log)
Aug  4 00:32:53 nasone smbd[32464]:   ===============================================================
Aug  4 00:32:53 nasone smbd[32464]: [2023/08/04 00:32:53.486694,  0] ../../lib/util/fault.c:184(smb_panic_log)
Aug  4 00:32:53 nasone smbd[32464]:   PANIC (pid 32464): Signal 11: Segmentation fault in 4.17.7
Aug  4 00:32:53 nasone smbd[32464]: [2023/08/04 00:32:53.487680,  0] ../../lib/util/fault.c:292(log_stack_trace)
Aug  4 00:32:53 nasone smbd[32464]:   BACKTRACE: 26 stack frames:
Aug  4 00:32:53 nasone smbd[32464]:    #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x14659e38c64e]
Aug  4 00:32:53 nasone smbd[32464]:    #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x14659e38c8a9]
Aug  4 00:32:53 nasone smbd[32464]:    #2 /usr/lib64/libgenrand-samba4.so(+0x2937) [0x14659e38c937]
Aug  4 00:32:53 nasone smbd[32464]:    #3 /lib64/libc.so.6(+0x3ae20) [0x14659e16de20]
Aug  4 00:32:53 nasone smbd[32464]:    #4 /lib64/libc.so.6(+0x96b12) [0x14659e1c9b12]
Aug  4 00:32:53 nasone smbd[32464]:    #5 /lib64/libc.so.6(+0x99238) [0x14659e1cc238]
Aug  4 00:32:53 nasone smbd[32464]:    #6 /lib64/libc.so.6(malloc+0x1a2) [0x14659e1cd402]
Aug  4 00:32:53 nasone smbd[32464]:    #7 /usr/lib64/libtalloc.so.2(+0x5b6e) [0x14659e33cb6e]
Aug  4 00:32:53 nasone smbd[32464]:    #8 /usr/lib64/libtalloc.so.2(talloc_pool+0x25) [0x14659e33d1e5]
Aug  4 00:32:53 nasone smbd[32464]:    #9 /usr/lib64/libsamba-util.so.0(+0x223d3) [0x14659e5283d3]
Aug  4 00:32:53 nasone smbd[32464]:    #10 /usr/lib64/libsmbd-base-samba4.so(+0xa0b7e) [0x14659e7c1b7e]
Aug  4 00:32:53 nasone smbd[32464]:    #11 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x85) [0x14659e34db95]
Aug  4 00:32:53 nasone smbd[32464]:    #12 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x14659e34de7b]
Aug  4 00:32:53 nasone smbd[32464]:    #13 /usr/lib64/libtevent.so.0(+0xce97) [0x14659e352e97]
Aug  4 00:32:53 nasone smbd[32464]:    #14 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x14659e7c4a37]
Aug  4 00:32:53 nasone smbd[32464]:    #15 /usr/sbin/smbd(+0xb090) [0x56441466a090]
Aug  4 00:32:53 nasone smbd[32464]:    #16 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x14659e34e8c1]
Aug  4 00:32:53 nasone smbd[32464]:    #17 /usr/lib64/libtevent.so.0(+0xee07) [0x14659e354e07]
Aug  4 00:32:53 nasone smbd[32464]:    #18 /usr/lib64/libtevent.so.0(+0xcef7) [0x14659e352ef7]
Aug  4 00:32:53 nasone smbd[32464]:    #19 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x14659e34dba1]
Aug  4 00:32:53 nasone smbd[32464]:    #20 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x14659e34de7b]
Aug  4 00:32:53 nasone smbd[32464]:    #21 /usr/lib64/libtevent.so.0(+0xce97) [0x14659e352e97]
Aug  4 00:32:53 nasone smbd[32464]:    #22 /usr/sbin/smbd(main+0x1489) [0x564414667259]
Aug  4 00:32:53 nasone smbd[32464]:    #23 /lib64/libc.so.6(+0x236b7) [0x14659e1566b7]
Aug  4 00:32:53 nasone smbd[32464]:    #24 /lib64/libc.so.6(__libc_start_main+0x85) [0x14659e156775]
Aug  4 00:32:53 nasone smbd[32464]:    #25 /usr/sbin/smbd(_start+0x21) [0x564414667b31]
Aug  4 00:32:53 nasone smbd[32464]: [2023/08/04 00:32:53.488051,  0] ../../source3/lib/dumpcore.c:315(dump_core)
Aug  4 00:32:53 nasone smbd[32464]:   dumping core in /var/log/samba/cores/smbd

hardware Info:

AMD 3200g with AsRock b450 motherboard.

2x16 gb Crucial Vengence ram running at default clock speeds without XMP.

3x 16TB + 1x 8TB Hdds

logs-2.gz nasone.lan-syslog-20230803-1902.zip

Edited August 3, 20232 yr by aditya333
Added hardware info

Several unrelated crashes and call traces, start by running memtest.

@JorgeB
Hey, I Already ran memtest.
No issues. Ran it twice. 4 + 4 passes

Edited August 4, 20232 yr by aditya333

Post the complete diags to see the hardware, it still looks to me like a hardware problem.

@JorgeB

Here is the diags:

Although, I restarted, and I don't see the crash now. The diags is downloaded after restart.

nasone.lan-diagnostics-20230804-2357.zip

Edited August 4, 20232 yr by aditya333

It failed again. New Diags:

 

nasone.lan-diagnostics-20230805-0109.zip

@JorgeB
I see this, does that mean something?

 

Aug  5 00:19:59 nasone kernel: smartctl_type[13048]: segfault at 1ff0c95da0 ip 000000000094ad22 sp 00007ffcf3c6f2f0 error 4 in php[600000+3b3000] likely on CPU 3 (core 3, socket 0)
Aug  5 00:19:59 nasone kernel: Code: 00 48 98 49 0f ba ee 3f 45 8b 64 85 00 41 83 fc ff 75 10 e9 80 00 00 00 45 8b 64 24 0c 41 83 fc ff 74 75 49 c1 e4 05 4d 01 ec <4d> 39 74 24 10 75 e7 4d 8b 7c 24 18 49 3b 6f 10 75 dc 49 8d 7f 18
Aug  5 00:19:59 nasone kernel: traps: smartctl_type[13049] general protection fault ip:14cea85bf159 sp:7ffd9abd40f8 error:0 in libc-2.37.so[14cea847c000+169000]
Aug  5 00:19:59 nasone kernel: traps: smartctl_type[13047] general protection fault ip:148150bb6464 sp:7fff48d10bb0 error:0 in ld-2.37.so[148150bad000+27000]
Aug  5 00:19:59 nasone kernel: traps: smartctl_type[13047] general protection fault ip:148150bb6464 sp:7fff48d10bb0 error:0 in ld-2.37.so[148150bad000+27000]
Aug  5 00:19:59 nasone kernel: traps: smartctl_type[13051] general protection fault ip:600630 sp:7ffcac9f50c8 error:0 in php[600000+3b3000]
Aug  5 00:19:59 nasone kernel: traps: smartctl_type[13052] general protection fault ip:15445eba6159 sp:7fff8607fab8 error:0 in libc-2.37.so[15445ea63000+169000]
Aug  5 00:19:59 nasone kernel: traps: smartctl[13053] general protection fault ip:153d7a7b33cf sp:7ffc3dd91d40 error:0 in libc-2.37.so[153d7a73b000+169000]
Aug  5 00:19:59 nasone kernel: traps: smartctl_type[13046] general protection fault ip:14abb606e6b5 sp:7ffca20a89c8 error:0 in libz.so.1.2.13[14abb606c000+e000]
Aug  5 00:20:00 nasone smbd[13062]: [2023/08/05 00:20:00.413482,  0] ../../lib/util/fault.c:173(smb_panic_log)
Aug  5 00:20:00 nasone smbd[13062]:   ===============================================================
Aug  5 00:20:00 nasone smbd[13062]: [2023/08/05 00:20:00.413556,  0] ../../lib/util/fault.c:174(smb_panic_log)
Aug  5 00:20:00 nasone smbd[13062]:   INTERNAL ERROR: Signal 11: Segmentation fault in pid 13062 (4.17.7)
Aug  5 00:20:00 nasone smbd[13062]: [2023/08/05 00:20:00.413580,  0] ../../lib/util/fault.c:178(smb_panic_log)
Aug  5 00:20:00 nasone smbd[13062]:   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
Aug  5 00:20:00 nasone smbd[13062]: [2023/08/05 00:20:00.413602,  0] ../../lib/util/fault.c:183(smb_panic_log)
Aug  5 00:20:00 nasone smbd[13062]:   ===============================================================
Aug  5 00:20:00 nasone smbd[13062]: [2023/08/05 00:20:00.413619,  0] ../../lib/util/fault.c:184(smb_panic_log)
Aug  5 00:20:00 nasone smbd[13062]:   PANIC (pid 13062): Signal 11: Segmentation fault in 4.17.7
Aug  5 00:20:00 nasone smbd[13062]: [2023/08/05 00:20:00.413872,  0] ../../lib/util/fault.c:292(log_stack_trace)
Aug  5 00:20:00 nasone smbd[13062]:   BACKTRACE: 30 stack frames:
Aug  5 00:20:00 nasone smbd[13062]:    #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x147314e5464e]
Aug  5 00:20:00 nasone smbd[13062]:    #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x147314e548a9]
Aug  5 00:20:00 nasone smbd[13062]:    #2 /usr/lib64/libgenrand-samba4.so(+0x2937) [0x147314e54937]
Aug  5 00:20:00 nasone smbd[13062]:    #3 /lib64/libc.so.6(+0x3ae20) [0x147314c35e20]
Aug  5 00:20:00 nasone smbd[13062]:    #4 /lib64/ld-linux-x86-64.so.2(+0x97a4) [0x1473153ce7a4]
Aug  5 00:20:00 nasone smbd[13062]:    #5 /lib64/ld-linux-x86-64.so.2(+0xa4e8) [0x1473153cf4e8]
Aug  5 00:20:00 nasone smbd[13062]:    #6 /lib64/ld-linux-x86-64.so.2(+0x10d9d) [0x1473153d5d9d]
Aug  5 00:20:00 nasone smbd[13062]:    #7 /lib64/ld-linux-x86-64.so.2(+0x132da) [0x1473153d82da]
Aug  5 00:20:00 nasone smbd[13062]:    #8 [0x147314e17419]
Aug  5 00:20:00 nasone smbd[13062]:    #9 /usr/lib64/libsmbd-base-samba4.so(smbd_smb2_request_process_tdis+0x1bd) [0x1473152a5c3d]
Aug  5 00:20:00 nasone smbd[13062]:    #10 /usr/lib64/libsmbd-base-samba4.so(smbd_smb2_request_dispatch+0xe14) [0x14731529db24]
Aug  5 00:20:00 nasone smbd[13062]:    #11 /usr/lib64/libsmbd-base-samba4.so(+0xb5ad1) [0x14731529ead1]
Aug  5 00:20:00 nasone smbd[13062]:    #12 [0x147314e168c1]
Aug  5 00:20:00 nasone smbd[13062]:    #13 [0x147314e1ce07]
Aug  5 00:20:00 nasone smbd[13062]:    #14 [0x147314e1aef7]
Aug  5 00:20:00 nasone smbd[13062]:    #15 [0x147314e15ba1]
Aug  5 00:20:00 nasone smbd[13062]:    #16 [0x147314e15e7b]
Aug  5 00:20:00 nasone smbd[13062]:    #17 [0x147314e1ae97]
Aug  5 00:20:00 nasone smbd[13062]:    #18 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x14731528ca37]
Aug  5 00:20:00 nasone smbd[13062]:    #19 /usr/sbin/smbd(+0xb090) [0x563a2cf83090]
Aug  5 00:20:00 nasone smbd[13062]:    #20 [0x147314e168c1]
Aug  5 00:20:00 nasone smbd[13062]:    #21 [0x147314e1ce07]
Aug  5 00:20:00 nasone smbd[13062]:    #22 [0x147314e1aef7]
Aug  5 00:20:00 nasone smbd[13062]:    #23 [0x147314e15ba1]
Aug  5 00:20:00 nasone smbd[13062]:    #24 [0x147314e15e7b]
Aug  5 00:20:00 nasone smbd[13062]:    #25 [0x147314e1ae97]
Aug  5 00:20:00 nasone smbd[13062]:    #26 /usr/sbin/smbd(main+0x1489) [0x563a2cf80259]
Aug  5 00:20:00 nasone smbd[13062]:    #27 /lib64/libc.so.6(+0x236b7) [0x147314c1e6b7]
Aug  5 00:20:00 nasone smbd[13062]:    #28 /lib64/libc.so.6(__libc_start_main+0x85) [0x147314c1e775]
Aug  5 00:20:00 nasone smbd[13062]:    #29 /usr/sbin/smbd(_start+0x21) [0x563a2cf80b31]
Aug  5 00:20:00 nasone smbd[13062]: [2023/08/05 00:20:00.414180,  0] ../../source3/lib/dumpcore.c:315(dump_core)
Aug  5 00:20:00 nasone smbd[13062]:   dumping core in /var/log/samba/cores/smbd
Aug  5 00:20:00 nasone smbd[13062]: 
Aug  5 00:20:00 nasone kernel: traps: notify[13063] general protection fault ip:150d8954063a sp:7ffdb8b7c638 error:0 in ld-2.37.so[150d8951e000+27000]
Aug  5 00:20:00 nasone kernel: traps: sh[13065] general protection fault ip:452dc8 sp:7ffdc307a628 error:0 in bash[426000+c5000]
Aug  5 00:20:01 nasone kernel: monitor[13071]: segfault at 1ff8c5a8f8 ip 00000000008d860e sp 00007ffcbf0a4220 error 4 in php[600000+3b3000] likely on CPU 2 (core 2, socket 0)

 

@JorgeB

Something new that I noticed:

My docker container data also got corrupted. 
For Prowlarr and Radarr

Remove one of the RAM sticks and try again, if the same try the other one.

@JorgeB

I can try that, however I was wondering what gives you the impression that its a RAM issue or a hardware issue at that?

Because multiple unrelated things are crashing, and RAM is a good suspect and the easiest to test.

@JorgeB and for anyone else who comes by, removing one RAM solved it. However, i don't understand how that should be an issue. I've used this same RAM for a windows PC before this with no issues. Multiple memtest doesn't show any errors.

So I have this exact error on my 6.12.4 system, when, either VM or Docker are enabled; with nothing actually running on them.
Disable both services and the errors stop.

Oct 26 22:49:24 KBNAS smbd[62935]: [2023/10/26 22:49:24.131417,  0] ../../lib/util/fault.c:173(smb_panic_log)
Oct 26 22:49:24 KBNAS smbd[62935]:   ===============================================================
Oct 26 22:49:24 KBNAS smbd[62935]: [2023/10/26 22:49:24.131526,  0] ../../lib/util/fault.c:174(smb_panic_log)
Oct 26 22:49:24 KBNAS smbd[62935]:   INTERNAL ERROR: Signal 11: Segmentation fault in pid 62935 (4.17.10)
Oct 26 22:49:24 KBNAS smbd[62935]: [2023/10/26 22:49:24.131589,  0] ../../lib/util/fault.c:178(smb_panic_log)
Oct 26 22:49:24 KBNAS smbd[62935]:   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 26 22:49:24 KBNAS smbd[62935]: [2023/10/26 22:49:24.131649,  0] ../../lib/util/fault.c:183(smb_panic_log)
Oct 26 22:49:24 KBNAS smbd[62935]:   ===============================================================
Oct 26 22:49:24 KBNAS smbd[62935]: [2023/10/26 22:49:24.131705,  0] ../../lib/util/fault.c:184(smb_panic_log)
Oct 26 22:49:24 KBNAS smbd[62935]:   PANIC (pid 62935): Signal 11: Segmentation fault in 4.17.10
Oct 26 22:49:24 KBNAS smbd[62935]: [2023/10/26 22:49:24.132847,  0] ../../lib/util/fault.c:292(log_stack_trace)
Oct 26 22:49:24 KBNAS smbd[62935]:   BACKTRACE: 31 stack frames:
Oct 26 22:49:24 KBNAS smbd[62935]:    #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x153cfdfdc64e]
Oct 26 22:49:24 KBNAS smbd[62935]:    #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x153cfdfdc8a9]
Oct 26 22:49:24 KBNAS smbd[62935]:    #2 /usr/lib64/libgenrand-samba4.so(+0x2937) [0x153cfdfdc937]
Oct 26 22:49:24 KBNAS smbd[62935]:    #3 /lib64/libc.so.6(+0x3ae20) [0x153cfddbde20]
Oct 26 22:49:24 KBNAS smbd[62935]:    #4 /usr/lib64/libsamba-util.so.0(strncasecmp_m_handle+0x3f) [0x153cfe1675cf]
Oct 26 22:49:24 KBNAS smbd[62935]:    #5 /usr/lib64/libsamba3-util-samba4.so(strnequal+0x29) [0x153cfe24ad29]
Oct 26 22:49:24 KBNAS smbd[62935]:    #6 /usr/lib64/libsmbd-base-samba4.so(+0x102cf4) [0x153cfe473cf4]
Oct 26 22:49:24 KBNAS smbd[62935]:    #7 /usr/lib64/libsmbd-base-samba4.so(reply_trans+0x213) [0x153cfe474323]
Oct 26 22:49:24 KBNAS smbd[62935]:    #8 /usr/lib64/libsmbd-base-samba4.so(+0x11b7f3) [0x153cfe48c7f3]
Oct 26 22:49:24 KBNAS smbd[62935]:    #9 /usr/lib64/libsmbd-base-samba4.so(construct_reply+0xb8) [0x153cfe48d4d8]
Oct 26 22:49:24 KBNAS smbd[62935]:    #10 /usr/lib64/libsmbd-base-samba4.so(process_smb1+0x141) [0x153cfe48d9f1]
Oct 26 22:49:24 KBNAS smbd[62935]:    #11 /usr/lib64/libsmbd-base-samba4.so(process_smb+0x8a) [0x153cfe4129aa]
Oct 26 22:49:24 KBNAS smbd[62935]:    #12 /usr/lib64/libsmbd-base-samba4.so(smbd_smb1_server_connection_read_handler+0xe0) [0x153cfe48dc50]
Oct 26 22:49:24 KBNAS smbd[62935]:    #13 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x153cfdf9e8c1]
Oct 26 22:49:24 KBNAS smbd[62935]:    #14 /usr/lib64/libtevent.so.0(+0xee07) [0x153cfdfa4e07]
Oct 26 22:49:24 KBNAS smbd[62935]:    #15 /usr/lib64/libtevent.so.0(+0xcef7) [0x153cfdfa2ef7]
Oct 26 22:49:24 KBNAS smbd[62935]:    #16 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x153cfdf9dba1]
Oct 26 22:49:24 KBNAS smbd[62935]:    #17 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x153cfdf9de7b]
Oct 26 22:49:24 KBNAS smbd[62935]:    #18 /usr/lib64/libtevent.so.0(+0xce97) [0x153cfdfa2e97]
Oct 26 22:49:24 KBNAS smbd[62935]:    #19 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x153cfe414a37]
Oct 26 22:49:24 KBNAS smbd[62935]:    #20 /usr/sbin/smbd(+0xb090) [0x55a1b4bf2090]
Oct 26 22:49:24 KBNAS smbd[62935]:    #21 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x153cfdf9e8c1]
Oct 26 22:49:24 KBNAS smbd[62935]:    #22 /usr/lib64/libtevent.so.0(+0xee07) [0x153cfdfa4e07]
Oct 26 22:49:24 KBNAS smbd[62935]:    #23 /usr/lib64/libtevent.so.0(+0xcef7) [0x153cfdfa2ef7]
Oct 26 22:49:24 KBNAS smbd[62935]:    #24 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x153cfdf9dba1]
Oct 26 22:49:24 KBNAS smbd[62935]:    #25 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x153cfdf9de7b]
Oct 26 22:49:24 KBNAS smbd[62935]:    #26 /usr/lib64/libtevent.so.0(+0xce97) [0x153cfdfa2e97]
Oct 26 22:49:24 KBNAS smbd[62935]:    #27 /usr/sbin/smbd(main+0x1489) [0x55a1b4bef259]
Oct 26 22:49:24 KBNAS smbd[62935]:    #28 /lib64/libc.so.6(+0x236b7) [0x153cfdda66b7]
Oct 26 22:49:24 KBNAS smbd[62935]:    #29 /lib64/libc.so.6(__libc_start_main+0x85) [0x153cfdda6775]
Oct 26 22:49:24 KBNAS smbd[62935]:    #30 /usr/sbin/smbd(_start+0x21) [0x55a1b4befb31]
Oct 26 22:49:24 KBNAS smbd[62935]: [2023/10/26 22:49:24.133858,  0] ../../source3/lib/dumpcore.c:315(dump_core)
Oct 26 22:49:24 KBNAS smbd[62935]:   dumping core in /var/log/samba/cores/smbd
Oct 26 22:49:24 KBNAS smbd[62935]: 


MEMTEST has passed 14.5 consecutive runs of my 2x 8GB and 2x 4GB DIMMS, with 0 Errors.
I guess I need to pull DIMMS anyway and test...?! 
What are the implications of this error anyway? @JorgeB

If it only happens with Docker or VM enable seems unlikely that it's a RAM issue.

Ok... Longer test period - So with the array stopped - and VM/Docker Disabled - These errors are still occurring...  Back to pulling DIMMS I guess!
@JorgeB

I actually have a lot of updates to apply to my HP Server itself - I'll start with those!

Back to just the original HP 2* 8GB RAM that my Server shipped (to me) with. I have more RAM coming and will swap it out - but the Segmentation errors still occur, pretty consistently, whether VM/Docker are in use; or not. BIOS and iLO updated, not that I think they have any impact.

 

I am also checking my Parity at the moment, with over 1000 corrections! I'm not really filled with confidence of this system at all.
(13 days since last check, minimal usage. A few docker containers added/removed - Using Cache = 2* 1TB SSD's in ZFS Raid 1 pool)

 

New RAM has arrived which I'll fit today.

The 2500+ Parity Sync errors were likely caused by Unraid shutting down before the array was stopped. (I have now changed the Settings>Shutdown time-out value to '180'). The subsequent 'non-correcting' Parity scan showed 0 Sync Errors. Thanks to this:

 

I also had an old, empty 120GB SSD fail during the first run of the non-corrective Parity check.
This:

Unraid Disk 4 error: 04-11-2023 16:26

Alert [KBNAS] - Disk 4 in error state (disk dsbl)
KINGSTON_SV300S3_50026B73310309DF_350026b73310309df (sdd)

I removed and readded it and it was then fine! Parity rebuilt with no errors.  The full non-corrective Parity scan was good.

I wanted to get the parity straight before removing this drive from my array - But - @JorgeB Do you think a bad disk could influence the Segmentation Fault?

 

 

Seems unlikely, unless there was some filesystem corruption causing issues.