SMB Instability Issues

[LOF_HWalker]

We have been having an issue with one of our Unraid NAS's where SMB seems to get into a loop of crashing and restarting, and all of the shares are inaccessible. This same basically identical block appears over and over in the syslog when we are having these issues:

 

Nov 21 10:08:28 LOF1-NAS kernel: SQUASHFS error: xz decompression failed, data probably corrupt
Nov 21 10:08:28 LOF1-NAS kernel: SQUASHFS error: Failed to read block 0x92b88c0: -5
Nov 21 10:08:28 LOF1-NAS smbd[32695]: [2023/11/21 10:08:28.598924,  0] ../../lib/util/fault.c:173(smb_panic_log)
Nov 21 10:08:28 LOF1-NAS smbd[32695]:   ===============================================================
Nov 21 10:08:28 LOF1-NAS smbd[32695]: [2023/11/21 10:08:28.598973,  0] ../../lib/util/fault.c:174(smb_panic_log)
Nov 21 10:08:28 LOF1-NAS smbd[32695]:   INTERNAL ERROR: Signal 7: Bus error in pid 32695 (4.17.10)
Nov 21 10:08:28 LOF1-NAS smbd[32695]: [2023/11/21 10:08:28.598987,  0] ../../lib/util/fault.c:178(smb_panic_log)
Nov 21 10:08:28 LOF1-NAS smbd[32695]:   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
Nov 21 10:08:28 LOF1-NAS smbd[32695]: [2023/11/21 10:08:28.599012,  0] ../../lib/util/fault.c:183(smb_panic_log)
Nov 21 10:08:28 LOF1-NAS smbd[32695]:   ===============================================================
Nov 21 10:08:28 LOF1-NAS smbd[32695]: [2023/11/21 10:08:28.599024,  0] ../../lib/util/fault.c:184(smb_panic_log)
Nov 21 10:08:28 LOF1-NAS smbd[32695]:   PANIC (pid 32695): Signal 7: Bus error in 4.17.10
Nov 21 10:08:28 LOF1-NAS kernel: SQUASHFS error: xz decompression failed, data probably corrupt
Nov 21 10:08:28 LOF1-NAS kernel: SQUASHFS error: Failed to read block 0x92b88c0: -5
Nov 21 10:08:28 LOF1-NAS smbd[32695]: [2023/11/21 10:08:28.599591,  0] ../../lib/util/fault.c:292(log_stack_trace)
Nov 21 10:08:28 LOF1-NAS smbd[32695]:   BACKTRACE: 30 stack frames:
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x153cd843d64e]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x153cd843d8a9]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #2 /usr/lib64/libgenrand-samba4.so(+0x2937) [0x153cd843d937]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #3 /lib64/libc.so.6(+0x3ae20) [0x153cd821ee20]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #4 /usr/lib64/libsmbd-base-samba4.so(+0x77f50) [0x153cd8849f50]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #5 /usr/lib64/libsmbd-base-samba4.so(smbd_become_root+0x12) [0x153cd884adb2]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #6 /usr/lib64/libsmbconf.so.0(remote_arch_cache_update+0xd5) [0x153cd8715d05]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #7 /usr/lib64/libsmbd-base-samba4.so(smbd_smb2_request_process_negprot+0xe28) [0x153cd888a7d8]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #8 /usr/lib64/libsmbd-base-samba4.so(smbd_smb2_request_dispatch+0xe48) [0x153cd8886a98]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #9 /usr/lib64/libsmbd-base-samba4.so(smbd_smb2_process_negprot+0x21d) [0x153cd8888f9d]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #10 /usr/lib64/libsmbd-base-samba4.so(process_smb+0x1f3) [0x153cd8873b13]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #11 /usr/lib64/libsmbd-base-samba4.so(smbd_smb1_server_connection_read_handler+0xe0) [0x153cd88eec50]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #12 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x153cd83ff8c1]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #13 /usr/lib64/libtevent.so.0(+0xee07) [0x153cd8405e07]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #14 /usr/lib64/libtevent.so.0(+0xcef7) [0x153cd8403ef7]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #15 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x153cd83feba1]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #16 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x153cd83fee7b]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #17 /usr/lib64/libtevent.so.0(+0xce97) [0x153cd8403e97]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #18 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x153cd8875a37]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #19 /usr/sbin/smbd(+0xb090) [0x55bc3e2f0090]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #20 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x153cd83ff8c1]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #21 /usr/lib64/libtevent.so.0(+0xee07) [0x153cd8405e07]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #22 /usr/lib64/libtevent.so.0(+0xcef7) [0x153cd8403ef7]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #23 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x153cd83feba1]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #24 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x153cd83fee7b]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #25 /usr/lib64/libtevent.so.0(+0xce97) [0x153cd8403e97]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #26 /usr/sbin/smbd(main+0x1489) [0x55bc3e2ed259]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #27 /lib64/libc.so.6(+0x236b7) [0x153cd82076b7]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #28 /lib64/libc.so.6(__libc_start_main+0x85) [0x153cd8207775]
Nov 21 10:08:28 LOF1-NAS smbd[32695]:    #29 /usr/sbin/s

 

I've attached our diagnostics zip as well.

 

It seems like SMB is hitting some corrupt data and getting tripped up, but it isn't clear to me what data it is trying to access when this happens.

lof1-nas-diagnostics-20231121-1202.zip

[advait182]

I think I'm having a similar problem. I've been able to access the server through Finder completely fine up until a few days ago. Now, the server just appears and disappears in the Network tab in Finder. When I try to find the server using an MS laptop, the same thing happens. When i try to connect to the server, some of the error messages I'm getting are:

 

1. There are no shares available or you are not allowed to access them on the server. 

2. This file server will not allow any more users. 

3. This server may not exists. Please check the IP address. 

 

Sometimes I get to the login credentials window, sometimes not. Even when I log in correctly, I'll get one of the random three error messages. 

I've attached my diagnostics zip as well. 

 

islademuerta-diagnostics-20231127-1850.zip

[dlandon]

On 11/21/2023 at 12:18 PM, LOF_HWalker said:

 

It seems like SMB is hitting some corrupt data and getting tripped up, but it isn't clear to me what data it is trying to access when this happens.

Your boot flash is having problems:

Nov 21 09:56:43 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov 21 09:56:43 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Nov 21 09:56:43 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Nov 21 09:56:43 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 b1 6b 52 00 00 28 00
Nov 21 09:56:43 LOF1-NAS kernel: critical medium error, dev sda, sector 11627346 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 2
Nov 21 10:01:02 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov 21 10:01:02 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Nov 21 10:01:02 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Nov 21 10:01:02 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 b1 6b 22 00 00 b0 00
Nov 21 10:01:02 LOF1-NAS kernel: critical medium error, dev sda, sector 11627298 op 0x0:(READ) flags 0x80700 phys_seg 22 prio class 2
Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 b1 6b 5a 00 00 08 00
Nov 21 10:01:03 LOF1-NAS kernel: critical medium error, dev sda, sector 11627354 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Nov 21 10:01:03 LOF1-NAS kernel: I/O error, dev loop1, sector 300480 op 0x0:(READ) flags 0x800 phys_seg 15 prio class 2
Nov 21 10:01:03 LOF1-NAS kernel: SQUASHFS error: Failed to read block 0x92b88c0: -5
Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 b1 6b 62 00 00 08 00
Nov 21 10:01:03 LOF1-NAS kernel: critical medium error, dev sda, sector 11627362 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Nov 21 10:01:03 LOF1-NAS kernel: I/O error, dev loop1, sector 300480 op 0x0:(READ) flags 0x800 phys_seg 16 prio class 2
Nov 21 10:01:03 LOF1-NAS kernel: SQUASHFS error: Failed to read block 0x92b88c0: -5

 

Shut down and take your flash to a PC and do a file check.  You might have to reformat the flash and start over, or use a new one.  Be sure to save and restore the /flash/config/ folder.

 

Samba is crashing.

[dlandon]

1 hour ago, advait182 said:

Sometimes I get to the login credentials window, sometimes not. Even when I log in correctly, I'll get one of the random three error messages. 

I've attached my diagnostics zip as well. 

You are using Realtek NICs.  They are problematic because the drivers for Linux are not very well maintained.  You might want to consider an Intel NIC card.

 

It  loooks like you have most shares set to Public.  Try setting up an Unriad user then assign the shares permissions like you want.  Keep in mind that 'root' cannot be used to access SMB shares.

[LOF_HWalker]

11 hours ago, dlandon said:

Shut down and take your flash to a PC and do a file check.  You might have to reformat the flash and start over, or use a new one.  Be sure to save and restore the /flash/config/ folder.

I forgot to update this thread, but a couple of days after I posted this (on Thanksgiving, naturally) the problem progressed and the system wouldn't come back up after a reboot (it was throwing a bzimage checksum error). I ended up setting up a new install on a new flash drive and copying the config over and things have been fine since. Thank you!