[SOLVED] New to unRAID - Shared Drives Now Failing + CPU Spikes

[JRubenol]

Diagnostic Logs: https://drive.google.com/file/d/1kcvoEr0x5H25FeUHCnnAzShTElxbnAiF/view?usp=sharing

 

I'm currently on a trial run of unRAID looking to purchase. Things were going extremely well until yesterday when things starting going sideways. In particular samba shares that were working fine on multiple clients are now timing out consistently. Looking at CPU usage on unRAID web GUI I'm seeing huge spikes when I'm trying to access these shares. I can see highest level (i.e., "Media") but when I click into one of the sub-folders I'm getting a time out. Only thing that has changed is that I've moved about 3 TB of data off my Synology server over to my unRAID server.

 

Thoughts appreciated. Although the Server is running old hardware, I think it should have no problem hosting a few samba shares . . .

Edited July 5, 2023 by JRubenol

[JorgeB]

Samba crashed, try rebooting.

[JRubenol]

No luck. New log here: https://drive.google.com/file/d/1OpCeLMDBOgFuDco9wLyQ_XC2WQc49SzR/view?usp=sharing

 

New information after messing around a bit:

(1) Samba doesn't appear to be crashing as I always have access to highest level;

(2) I have full rights on highest level with my user which is what I want

(3) When I enter "TV_Shows" directory, things appear to work fine, divided into sub directories for DVR'd shows, I can go into these individual shows fine

(4) MOVIES directory times out (about 1.8 TB inside)

 

Then I did a bit more testing:

(5) I created a new directory MOVIES2 and moved everything from MOVIES into MOVIES2

Result: Can get into MOVIES directory fine (empty directory no time out) but MOVIES2 times out

(6) I moved a single movie from MOVIES2 back into MOVIES

Result: I can access MOVIES fine with the single item inside, MOVIES2 continues to time out

 

CPU still is showing huge spikes with SHFS being a resource hog (over 100%).

 

 

 

 

tower-diagnostics-20230704-0727.zip

[JorgeB]

Jul  3 19:53:38 Tower smbd[20168]:   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

 

Samba is still crashing, first thing update to v6.12.2, also post future diags here in the forum please.

[dlandon]

One of your didks has some issues:

Jul  3 19:35:55 Tower emhttpd: mounting /mnt/disk2
Jul  3 19:35:55 Tower emhttpd: shcmd (130): mkdir -p /mnt/disk2
Jul  3 19:35:55 Tower emhttpd: shcmd (131): mount -t xfs -o noatime,nouuid /dev/md2p1 /mnt/disk2
Jul  3 19:35:55 Tower kernel: XFS (md2p1): Mounting V5 Filesystem
Jul  3 19:35:55 Tower kernel: ata5.00: exception Emask 0x10 SAct 0x7000 SErr 0x400000 action 0x6 frozen
Jul  3 19:35:55 Tower kernel: ata5.00: irq_stat 0x08000000, interface fatal error
Jul  3 19:35:55 Tower kernel: ata5: SError: { Handshk }
Jul  3 19:35:55 Tower kernel: ata5.00: failed command: WRITE FPDMA QUEUED
Jul  3 19:35:55 Tower kernel: ata5.00: cmd 61/10:60:00:a5:e1/00:00:e8:00:00/40 tag 12 ncq dma 8192 out
Jul  3 19:35:55 Tower kernel:         res 40/00:00:10:a5:e1/00:00:e8:00:00/40 Emask 0x10 (ATA bus error)
Jul  3 19:35:55 Tower kernel: ata5.00: status: { DRDY }
Jul  3 19:35:55 Tower kernel: ata5.00: failed command: WRITE FPDMA QUEUED
Jul  3 19:35:55 Tower kernel: ata5.00: cmd 61/08:68:48:a5:e1/00:00:e8:00:00/40 tag 13 ncq dma 4096 out
Jul  3 19:35:55 Tower kernel:         res 40/00:00:10:a5:e1/00:00:e8:00:00/40 Emask 0x10 (ATA bus error)

it seems to be CRC errors on disk2.  Check cables.

 

Samba is crashing:

Jul  3 19:53:38 Tower smbd[20168]: [2023/07/03 19:53:38.638592,  0] ../../lib/util/fault.c:173(smb_panic_log)
Jul  3 19:53:38 Tower smbd[20168]:   ===============================================================
Jul  3 19:53:38 Tower smbd[20168]: [2023/07/03 19:53:38.640121,  0] ../../lib/util/fault.c:174(smb_panic_log)
Jul  3 19:53:38 Tower smbd[20168]:   INTERNAL ERROR: Signal 7: Bus error in pid 20168 (4.17.7)
Jul  3 19:53:38 Tower smbd[20168]: [2023/07/03 19:53:38.642863,  0] ../../lib/util/fault.c:178(smb_panic_log)
Jul  3 19:53:38 Tower smbd[20168]:   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
Jul  3 19:53:38 Tower smbd[20168]: [2023/07/03 19:53:38.648126,  0] ../../lib/util/fault.c:183(smb_panic_log)
Jul  3 19:53:38 Tower smbd[20168]:   ===============================================================
Jul  3 19:53:38 Tower smbd[20168]: [2023/07/03 19:53:38.648831,  0] ../../lib/util/fault.c:184(smb_panic_log)
Jul  3 19:53:38 Tower smbd[20168]:   PANIC (pid 20168): Signal 7: Bus error in 4.17.7
Jul  3 19:53:38 Tower smbd[20168]: [2023/07/03 19:53:38.658840,  0] ../../lib/util/fault.c:292(log_stack_trace)

Not sure where that is coming from.  I don't recall seeing that issue before.

[JRubenol]

Closing as resolved. It ended up being a specific file tripping up Samba - still trying to figure out which one but I've narrowed it down with a file starting with the letter S so getting there. Another thread about to be started about significant performance issues but I think it's distinct from this one. Thanks all.