Raven document scanner/SMB share can't comunicate after update to 6.11 from 6.10.3

[cjohnson46]

Hello all,

 

I'm not sure what changed between Unraid 6.10.3 to 6.11.5, but my Raven document scanner isn't able to connect to my SMB share for file backup.  It gives me a "Undefined: undefined" error.  I was hoping someone with some more knowledge could help me out.  Everything was working on 6.10.3, upgraded to 6.11.5 and it wouldn't connect, then downgraded back to 6.10.3 and it worked again.  Unfortunately I didn't save any logs so I can't help in that way.  I'm just wondering if some sort of protocol changed between these versions.  Or, maybe it changed a default setting that I didn't notice.  The read and write permissions were correct and I tried all combinations with Public, Secure and Private security. I also enabled NetBIOS and WSD in case it was a SMBv1 issue.  I'm at a loss. 

[MrGrey]

Disable SMB1 (if you haven't already). I don't know what a Raven Document Scanner is, but I suspect it's a device attached via ethernet cable, or a device attached via USB to a device attached via an ethernet cable. If it's WIFI, you might just ignore me...

 

How are you accessing UnRAID for management? I'm guessing WebUI, but that could be "local" (ip address) or through "MyServers" plugin? Windoze or Mak (or Linux) or directly plugged in monitor and keyboard?

 

UnRaid is tightening security, as it should, and 6.10 to 6.11 is quite a leap.

 

I'm sorry I don't have the answer yet...

On 1/5/2023 at 3:57 PM, cjohnson46 said:

It gives me a "Undefined: undefined" error. 

 

That is the most true error I've seen in a long, long time.

 

MrGrey.

 

[cjohnson46]

Thanks for the reply!

 

On 1/8/2023 at 10:01 PM, MrGrey said:

Disable SMB1 (if you haven't already).

 

I did try disabling SMBv1 (Enable NetBIOS: No) after enabling it.  My current setup for SMB is exactly the same as it was once I upgraded and I tried all other combinations, so I have no other ideas.

 

On 1/8/2023 at 10:01 PM, MrGrey said:

I don't know what a Raven Document Scanner is, but I suspect it's a device attached via ethernet cable, or a device attached via USB to a device attached via an ethernet cable. If it's WIFI, you might just ignore me...

 

The scanner is connected through Ethernet and has a WiFi backup.  I tried disconnecting each at a time but nothing changed.

 

On 1/8/2023 at 10:01 PM, MrGrey said:

How are you accessing UnRAID for management? I'm guessing WebUI, but that could be "local" (ip address) or through "MyServers" plugin? Windoze or Mak (or Linux) or directly plugged in monitor and keyboard?

 

I'm connecting to UnRAID through the local WebUI.  As I said, I haven't changed anything other than upgrading to the latest stable build.

 

On 1/8/2023 at 10:01 PM, MrGrey said:

UnRaid is tightening security, as it should, and 6.10 to 6.11 is quite a leap.

 

I'm starting to think that some sort of change that UnRAID made in these more recent builds might be causing the issue.  I've went through the changelog and can't find any mention of changes that would cause this.

 

On 1/8/2023 at 10:01 PM, MrGrey said:

That is the most true error I've seen in a long, long time.

 

LOL!  I know!  I wish it was more explanatory.  This seems to be my luck.  I have also tried contacting Raven for support but they must not like hard questions because they hang up immediately every time I call now.

 

Thank you again for the help! 

[Shadowwrath5]

On 1/11/2023 at 6:34 PM, cjohnson46 said:

Thanks for the reply!

 

 

I did try disabling SMBv1 (Enable NetBIOS: No) after enabling it.  My current setup for SMB is exactly the same as it was once I upgraded and I tried all other combinations, so I have no other ideas.

 

 

The scanner is connected through Ethernet and has a WiFi backup.  I tried disconnecting each at a time but nothing changed.

 

 

I'm connecting to UnRAID through the local WebUI.  As I said, I haven't changed anything other than upgrading to the latest stable build.

 

 

I'm starting to think that some sort of change that UnRAID made in these more recent builds might be causing the issue.  I've went through the changelog and can't find any mention of changes that would cause this.

 

 

LOL!  I know!  I wish it was more explanatory.  This seems to be my luck.  I have also tried contacting Raven for support but they must not like hard questions because they hang up immediately every time I call now.

 

Thank you again for the help! 

 

Curious if you found an answer or solution to this problem. We just bought a scanner for some testing and Im running into this same issue

[SimonMisc]

+1 for interest here, just tried setting it up and assumed it was a Raven Scanner issue until I saw this thread saying it used to work on 6.10.3.

[bwitting]

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. 

[bwitting]

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. 

[daemian]

Just wanted to chime in to say I am running into the same issue w/ my Raven scanner and unraid (which had been working for quite some time). Hoping you get a resolution from their support - let us know!

[cjohnson46]

Hey guys,

 

I'm glad it's not just me with this issue. Unfortunately I'm not getting update notifications on my posts, but I'll start to check it manually more often. 

I decided to give ChatGPT a try on the issue and it basically states what @bwitting said. After entering my logs, I got this reply.

 

Quote

Based on the logs you provided, it seems that Samba encountered an internal error and crashed. The log indicates a "PANIC" and an "assert failed" error message. The error message also refers to a file "raven-test-file.txt" that couldn't acquire a share mode lock, as well as a file descriptor handle assertion that failed.

 

These errors suggest that there may be a problem with Samba's configuration or with the file share that you are trying to access. To troubleshoot the issue, you can try the following steps:

 

1) Check your Samba configuration file to ensure that it is properly set up and that all necessary shares and permissions are correctly defined.

 

2) Verify that the file share you are trying to access is accessible and has the correct permissions set.

 

3) Check the Samba log files again to see if there are any additional error messages or clues that may help identify the cause of the issue.

 

4) If the problem persists, consider updating Samba to the latest version and/or reporting the issue to the Samba development team.

 

Note that some Samba issues can also be caused by network connectivity problems, hardware failures, or other system-related issues. Therefore, it may be helpful to check your system logs and run hardware diagnostics if necessary.

 

I installed nano next and changed my samba config file to include my share and "browseable = yes" to my share path as someone online suggested. It didn't help but I thought I'd add it just in case you wanted to know what works or not.

 

[Docspell_consume]
   path = /mnt/user/Docspell_consume
   browseable = yes
   writable = yes
   guest ok = yes
   read only = no
   create mask = 0666
   directory mask = 0777

 

bwitting - I also took your advice on SFTPGo. It was a one click install. I just fired it up, so I'll have to figure it out. It's definitely worth a try for a quick fix but I'm not giving up yet.

[bwitting]

After some back and forth giving Raven support some info, they finally came back with:

 

Quote

We do support SMBs on Windows and Mac Computers/servers, but not on any other operative system or environment like yours at this moment (Unraid 6.11.6).

 

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 😄

[cjohnson46]

I have completely given up on Raven support.  While their product is great, their customer & technical support is some of the worst I've dealt with.  Between their scripted (basic) responses and being hung up on multiple times when they did not want to elevate me to a more knowledgeable tech agent, I stopped trying.  They also used to push updates all of the time.

 

As much as I don't want to give them an out, we did have it working in Unraid 10, so hopefully we can get it figured out on our side.

 

SFTPGo is great!  I installed it and was up and running with the FTP within 5 minutes.  It's far superior to Unraid's FTP server.  sFTP didn't work unfortunately 😏

[BitVentures USA]

I wouldn't blame Raven, I'm trying to backup to a SMB share on the latest unraid (6.12.6) using Swift Backup on Android and I'm getting the same errors and panics. I'm surprised this is an ongoing issue but hopefully it is resolved in the next release. I'd rather not introduce *FTP for security reasons. I'd entertain using SCP or maybe FTPS but that's not an option. 

 

Has anyone else overcome this issue? The log output is below.

 

Feb  5 11:13:29 NAS-01 smbd[20419]: [2024/02/05 11:13:29.907910,  0] ../../source3/smbd/fd_handle.c:39(fd_handle_destructor)
Feb  5 11:13:29 NAS-01 smbd[20419]:   PANIC: assert failed at ../../source3/smbd/fd_handle.c(39): (fh->fd == -1) || (fh->fd == AT_FDCWD)
Feb  5 11:13:29 NAS-01 smbd[20419]: [2024/02/05 11:13:29.907949,  0] ../../lib/util/fault.c:173(smb_panic_log)
Feb  5 11:13:29 NAS-01 smbd[20419]:   ===============================================================
Feb  5 11:13:29 NAS-01 smbd[20419]: [2024/02/05 11:13:29.907995,  0] ../../lib/util/fault.c:174(smb_panic_log)
Feb  5 11:13:29 NAS-01 smbd[20419]:   INTERNAL ERROR: assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in pid 20419 (4.17.12)
Feb  5 11:13:29 NAS-01 smbd[20419]: [2024/02/05 11:13:29.908012,  0] ../../lib/util/fault.c:178(smb_panic_log)
Feb  5 11:13:29 NAS-01 smbd[20419]:   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
Feb  5 11:13:29 NAS-01 smbd[20419]: [2024/02/05 11:13:29.908028,  0] ../../lib/util/fault.c:183(smb_panic_log)
Feb  5 11:13:29 NAS-01 smbd[20419]:   ===============================================================
Feb  5 11:13:29 NAS-01 smbd[20419]: [2024/02/05 11:13:29.908043,  0] ../../lib/util/fault.c:184(smb_panic_log)
Feb  5 11:13:29 NAS-01 smbd[20419]:   PANIC (pid 20419): assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in 4.17.12
Feb  5 11:13:29 NAS-01 smbd[20419]: [2024/02/05 11:13:29.908421,  0] ../../lib/util/fault.c:292(log_stack_trace)
Feb  5 11:13:29 NAS-01 smbd[20419]:   BACKTRACE: 27 stack frames:
Feb  5 11:13:29 NAS-01 smbd[20419]:    #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x150f5ac6e64e]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x150f5ac6e8a9]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #2 /usr/lib64/libsmbd-base-samba4.so(+0x4d0fb) [0x150f5b0500fb]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #3 /usr/lib64/libtalloc.so.2(+0x44df) [0x150f5ac1d4df]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #4 /usr/lib64/libsmbd-base-samba4.so(file_free+0xd6) [0x150f5b05d266]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #5 /usr/lib64/libsmbd-base-samba4.so(+0xc0781) [0x150f5b0c3781]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #6 /usr/lib64/libsmbd-base-samba4.so(smbd_smb2_request_process_close+0x211) [0x150f5b0c3f01]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #7 /usr/lib64/libsmbd-base-samba4.so(smbd_smb2_request_dispatch+0xdfa) [0x150f5b0b7bfa]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #8 /usr/lib64/libsmbd-base-samba4.so(+0xb5bc1) [0x150f5b0b8bc1]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #9 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x150f5ac308c1]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #10 /usr/lib64/libtevent.so.0(+0xee07) [0x150f5ac36e07]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #11 /usr/lib64/libtevent.so.0(+0xcef7) [0x150f5ac34ef7]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #12 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x150f5ac2fba1]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #13 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x150f5ac2fe7b]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #14 /usr/lib64/libtevent.so.0(+0xce97) [0x150f5ac34e97]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #15 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x150f5b0a6be7]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #16 /usr/sbin/smbd(+0xb090) [0x565282edd090]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #17 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x150f5ac308c1]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #18 /usr/lib64/libtevent.so.0(+0xee07) [0x150f5ac36e07]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #19 /usr/lib64/libtevent.so.0(+0xcef7) [0x150f5ac34ef7]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #20 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x150f5ac2fba1]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #21 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x150f5ac2fe7b]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #22 /usr/lib64/libtevent.so.0(+0xce97) [0x150f5ac34e97]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #23 /usr/sbin/smbd(main+0x1489) [0x565282eda259]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #24 /lib64/libc.so.6(+0x236b7) [0x150f5aa386b7]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #25 /lib64/libc.so.6(__libc_start_main+0x85) [0x150f5aa38775]
Feb  5 11:13:29 NAS-01 smbd[20419]:    #26 /usr/sbin/smbd(_start+0x21) [0x565282edab31]
Feb  5 11:13:29 NAS-01 smbd[20419]: [2024/02/05 11:13:29.908717,  0] ../../source3/lib/dumpcore.c:315(dump_core)
Feb  5 11:13:29 NAS-01 smbd[20419]:   dumping core in /var/log/samba/cores/smbd
Feb  5 11:13:29 NAS-01 smbd[20419]: