bwitting

For anyone stumbling on this in the future, there is a firmware fix for my specific device (Terramaster D8): https://forum.terra-master.com/en/viewtopic.php?t=6748 This fixed the problem and I can now use each m.2 drive.

Hello folks, I have a Terramaster D8 USB 3 enclosure that can house 4 3.5" drives (via SATA) and 4 m.2 nvme drives. When full of drives and connected to Unraid, all 4 3.5" disks show up as individual disks and work fine (can be added as pool devices, etc). However, when there are 3 m.2 drives (and I assume 4, I just don't have 1 more to test) hooked up, only one seems to work at a time. I can only mount 1 at a time or use 1 at a time as a pool device. The others show up in Unassigned Devices but I can't do anything with them: Is this an issue with the device I'm using, or an Unraid limitation, or something incorrect with my configuration? Thanks for the thoughts! orthanc-diagnostics-20250121-1719.zip

After some back and forth giving Raven support some info, they finally came back with: So even though their marketing materials say SMB is supported (not SMB on Windows/Mac only...), their support isn't interested in helping at this time. I'll stick with the FTP solution for now - that is doing what I need. @cjohnson46 - good thinking asking ChatGPT 😄

Wanted to add for others having this problem - I'm using the SFTPGo Docker image to set up a FTP server, and set up FTP as a destination on the Raven scanner. That is working great. I opened a case with Raven support too. It looks like the app on the scanner is using the smbj library to connect, and their app is writing a file called "raven-test-file.txt" to the share and then quickly deleting it to make sure the destination is available and writable (and if you make a file called raven-test-file.txt yourself, it will delete it). I'm wondering if the file is getting deleted before the lock on the file is released, and that's what is causing the Samba crash. I'll post if I discover anything else useful.

I just got a Raven scanner and am having the same issues as well on 6.11.5. According to the logs, it looks like there is a problem with a file lock and the Samba service is crashing: Mar 6 14:51:29 Orthanc smbd[2882]: [2023/03/06 14:51:29.843490, 0] ../../source3/smbd/close.c:312(close_remove_share_mode) Mar 6 14:51:29 Orthanc smbd[2882]: close_remove_share_mode: Could not get share mode lock for file Paperless/Consumption/raven-test-file.txt Mar 6 14:51:29 Orthanc smbd[2882]: [2023/03/06 14:51:29.843575, 0] ../../source3/smbd/fd_handle.c:39(fd_handle_destructor) Mar 6 14:51:29 Orthanc smbd[2882]: PANIC: assert failed at ../../source3/smbd/fd_handle.c(39): (fh->fd == -1) || (fh->fd == AT_FDCWD) Mar 6 14:51:29 Orthanc smbd[2882]: [2023/03/06 14:51:29.843586, 0] ../../lib/util/fault.c:173(smb_panic_log) Mar 6 14:51:29 Orthanc smbd[2882]: =============================================================== Mar 6 14:51:29 Orthanc smbd[2882]: [2023/03/06 14:51:29.843596, 0] ../../lib/util/fault.c:174(smb_panic_log) Mar 6 14:51:29 Orthanc smbd[2882]: INTERNAL ERROR: assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in pid 2882 (4.17.3) Mar 6 14:51:29 Orthanc smbd[2882]: [2023/03/06 14:51:29.843602, 0] ../../lib/util/fault.c:178(smb_panic_log) Mar 6 14:51:29 Orthanc smbd[2882]: 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 Mar 6 14:51:29 Orthanc smbd[2882]: [2023/03/06 14:51:29.843608, 0] ../../lib/util/fault.c:183(smb_panic_log) Mar 6 14:51:29 Orthanc smbd[2882]: =============================================================== Mar 6 14:51:29 Orthanc smbd[2882]: [2023/03/06 14:51:29.843612, 0] ../../lib/util/fault.c:184(smb_panic_log) Mar 6 14:51:29 Orthanc smbd[2882]: PANIC (pid 2882): assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in 4.17.3 Mar 6 14:51:29 Orthanc smbd[2882]: [2023/03/06 14:51:29.843816, 0] ../../lib/util/fault.c:292(log_stack_trace) Mar 6 14:51:29 Orthanc smbd[2882]: BACKTRACE: 32 stack frames: Mar 6 14:51:29 Orthanc smbd[2882]: #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x149a4d08764e] Mar 6 14:51:29 Orthanc smbd[2882]: #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x149a4d0878a9] Mar 6 14:51:29 Orthanc smbd[2882]: #2 /usr/lib64/libsmbd-base-samba4.so(+0x4d10b) [0x149a4d46810b] Mar 6 14:51:29 Orthanc smbd[2882]: #3 /usr/lib64/libtalloc.so.2(+0x44df) [0x149a4d0374df] Mar 6 14:51:29 Orthanc smbd[2882]: #4 /usr/lib64/libsmbd-base-samba4.so(file_free+0xd6) [0x149a4d4752e6] Mar 6 14:51:29 Orthanc smbd[2882]: #5 /usr/lib64/libsmbd-base-samba4.so(close_file_free+0x29) [0x149a4d4a5d49] Mar 6 14:51:29 Orthanc smbd[2882]: #6 /usr/lib64/libsmbd-base-samba4.so(+0x5d046) [0x149a4d478046] Mar 6 14:51:29 Orthanc smbd[2882]: #7 /usr/lib64/libsmbd-base-samba4.so(+0x5d192) [0x149a4d478192] Mar 6 14:51:29 Orthanc smbd[2882]: #8 /usr/lib64/libsmbd-base-samba4.so(files_forall+0x19) [0x149a4d474119] Mar 6 14:51:29 Orthanc smbd[2882]: #9 /usr/lib64/libsmbd-base-samba4.so(file_close_conn+0x44) [0x149a4d474184] Mar 6 14:51:29 Orthanc smbd[2882]: #10 /usr/lib64/libsmbd-base-samba4.so(close_cnum+0x67) [0x149a4d4c0fd7] Mar 6 14:51:29 Orthanc smbd[2882]: #11 /usr/lib64/libsmbd-base-samba4.so(smbXsrv_tcon_disconnect+0x4e) [0x149a4d4f41de] Mar 6 14:51:29 Orthanc smbd[2882]: #12 /usr/lib64/libsmbd-base-samba4.so(+0xbbe92) [0x149a4d4d6e92] Mar 6 14:51:29 Orthanc smbd[2882]: #13 /usr/lib64/libtevent.so.0(tevent_common_invoke_immediate_handler+0x17a) [0x149a4d04acfa] Mar 6 14:51:29 Orthanc smbd[2882]: #14 /usr/lib64/libtevent.so.0(tevent_common_loop_immediate+0x16) [0x149a4d04ad16] Mar 6 14:51:29 Orthanc smbd[2882]: #15 /usr/lib64/libtevent.so.0(+0xea7b) [0x149a4d050a7b] Mar 6 14:51:29 Orthanc smbd[2882]: #16 /usr/lib64/libtevent.so.0(+0xcd77) [0x149a4d04ed77] Mar 6 14:51:29 Orthanc smbd[2882]: #17 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x149a4d049b61] Mar 6 14:51:29 Orthanc smbd[2882]: #18 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x149a4d049e3b] Mar 6 14:51:29 Orthanc smbd[2882]: #19 /usr/lib64/libtevent.so.0(+0xcd17) [0x149a4d04ed17] Mar 6 14:51:29 Orthanc smbd[2882]: #20 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x149a4d4bece7] Mar 6 14:51:29 Orthanc smbd[2882]: #21 /usr/sbin/smbd(+0xb090) [0x555b64eda090] Mar 6 14:51:29 Orthanc smbd[2882]: #22 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x149a4d04a791] Mar 6 14:51:29 Orthanc smbd[2882]: #23 /usr/lib64/libtevent.so.0(+0xec87) [0x149a4d050c87] Mar 6 14:51:29 Orthanc smbd[2882]: #24 /usr/lib64/libtevent.so.0(+0xcd77) [0x149a4d04ed77] Mar 6 14:51:29 Orthanc smbd[2882]: #25 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x149a4d049b61] Mar 6 14:51:29 Orthanc smbd[2882]: #26 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x149a4d049e3b] Mar 6 14:51:29 Orthanc smbd[2882]: #27 /usr/lib64/libtevent.so.0(+0xcd17) [0x149a4d04ed17] Mar 6 14:51:29 Orthanc smbd[2882]: #28 /usr/sbin/smbd(main+0x1489) [0x555b64ed7259] Mar 6 14:51:29 Orthanc smbd[2882]: #29 /lib64/libc.so.6(+0x23177) [0x149a4ce55177] Mar 6 14:51:29 Orthanc smbd[2882]: #30 /lib64/libc.so.6(__libc_start_main+0x85) [0x149a4ce55235] Mar 6 14:51:29 Orthanc smbd[2882]: #31 /usr/sbin/smbd(_start+0x21) [0x555b64ed7b31] Mar 6 14:51:29 Orthanc smbd[2882]: [2023/03/06 14:51:29.843913, 0] ../../source3/lib/dumpcore.c:315(dump_core) Mar 6 14:51:29 Orthanc smbd[2882]: dumping core in /var/log/samba/cores/smbd I'm going to look around and see if I can find any more info about this or how to fix (or hopefully it's fixed in a newer version of Samba). I will try using FTP for now as a workaround, but hopefully this can be resolved.