Kev600

If this relates to the array failing to stop fully before shut-down, then you could try changing the Settings>Disk Settings>'Default spin down delay' - To - 'Never'. I see you have shutdownTimeout set to '90', which should be ok. OR - Is your shutdown unexpected/unwanted?

Itimpi gave you a direct link to the help file..

This should have all the answers..

Nice - Have you gone through much config/usage in those 10 days?

Ahh you're quite right there - Sorry.. "Remote Shares" are those hosted under 'Unassigned Devices' - Not in the Array. Krusader is a good alternative to MC..

It might be better to use unBALANCE to move the files.

Thanks Rysz. So - I'm gutted to realise/admit that the Share in question had public read/write access for both NFS and SMB; which I guess explains how the files became exposed. I think I set that because Windows was failing to connect to the Share! I'm still at a total loss as to what triggered the exploit though! I've never had any issues like this with any data on any devices... Moreover, what's a recommended way, please, to use UNRAID as a safe, robust storage/fileserver at LAN level, let alone WAN.....(Planning to use NextCloud for that). Surely just using ONE read/write share with the subsequent file management; isn't the only/best solution? Thanks Kev

I came back from vacation and powered up my 6.12.4 Unraid server and, whilst working to build my ebooks/pdf collections, I noticed I had a specific share partly affected by the 0xxx ransomware on 06/11/23. I don't think it's affected anything too crucial - but with a sick feeling in my stomach, I'm still reviewing the remaining 600~ infected files -Obviously, I'm not paying $800 worth of Bitcoin. I went through this - outdated?! page - https://unraid.net/blog/unraid-server-security-best-practices and didn't have anything as a great big 'come get me' misconfiguration... and I think that the exploit has possibly occurred when accessing an old BuffaloNAS drive which only supports SMBv1, via Unassigned Devices; with a clean/uninfected Windows10 laptop in the middle... But I'm still not sure how this actually happened, when my router isn't exposing any sensitive ports... OK I did have #80 pushed to #380, when trying, unsuccessfully; to get Nginx Proxy Manager to work with Containers.. and I have an old Win7 VM which I'll investigate a little further.. I've never had any issues with that BuffaloNAS server in over 10 years as an externally, port forwarded FTP Server, with occasional WebAccess via BuffaloNAS.com, and direct SMBv1 access to/from my Windows 7/10 PC's. So I'm not convinced it's the source of the exploit. I set up ClamAV and I've scanned everything on my Unraid Array - and yes there are a bunch of really old Windows exe files that are infected with some really old trojans, I knew about - Which shouldn't have any effect in a linux environment, and have subsequently been deleted... But the bottom line here is WE, the Unraid Community, NEED HELP TO PREVENT THIS. I currently feel very uncertain about having a combined app/storage/backup server when it's already been compromised. Very interested to hear comments on this, please. Thanks Kev

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?

I put my boot USB into a different port, updated my system BIOS - and the errors still occurred. I then put it back in the mobo USB slot - and the errors have stopped; which makes no sense at all.

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)

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

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

@JorgeB "With only the boot USB Flash drive in" No other USB ports are in use. I've just rebooted and without the array started - the errors are occurring. Fresh logs attached. Any ideas would be appreciated. kbnas-diagnostics-20231027-1023.zip kbnas-syslog-20231027-0923.zip

I have this exact problem, I don't know when it started, since I took more attention of the logs after upgrading a lot of hardware. With only the boot USB Flash drive in - the logs cycle through devices 1 > 128.. I have gone through the share split config as above, and, as far as I can discern, I have removed any Level 1 share splitting.. Restarted the Array, and the errors come flooding back again.. Oct 26 22:49:27 KBNAS kernel: usb 2-1.3: USB disconnect, device number 54 Oct 26 22:49:28 KBNAS kernel: usb 2-1.3: new high-speed USB device number 55 using ehci-pci Oct 26 22:49:28 KBNAS kernel: hub 2-1.3:1.0: USB hub found Oct 26 22:49:28 KBNAS kernel: hub 2-1.3:1.0: 2 ports detected Oct 26 22:50:18 KBNAS kernel: usb 2-1.3: USB disconnect, device number 55 Oct 26 22:50:19 KBNAS kernel: usb 2-1.3: new high-speed USB device number 56 using ehci-pci Oct 26 22:50:19 KBNAS kernel: hub 2-1.3:1.0: USB hub found Oct 26 22:50:19 KBNAS kernel: hub 2-1.3:1.0: 2 ports detected Oct 26 22:51:18 KBNAS kernel: usb 2-1.3: USB disconnect, device number 56 Oct 26 22:51:18 KBNAS kernel: usb 2-1.3: new high-speed USB device number 57 using ehci-pci Oct 26 22:51:19 KBNAS kernel: hub 2-1.3:1.0: USB hub found Oct 26 22:51:19 KBNAS kernel: hub 2-1.3:1.0: 2 ports detected Oct 26 22:52:44 KBNAS kernel: usb 2-1.3: USB disconnect, device number 57 Oct 26 22:52:45 KBNAS kernel: usb 2-1.3: new high-speed USB device number 58 using ehci-pci Oct 26 22:52:45 KBNAS kernel: hub 2-1.3:1.0: USB hub found Oct 26 22:52:45 KBNAS kernel: hub 2-1.3:1.0: 2 ports detected Oct 26 22:53:39 KBNAS kernel: usb 2-1.3: USB disconnect, device number 58 Oct 26 22:53:40 KBNAS kernel: usb 2-1.3: new high-speed USB device number 59 using ehci-pci Oct 26 22:53:40 KBNAS kernel: hub 2-1.3:1.0: USB hub found Oct 26 22:53:40 KBNAS kernel: hub 2-1.3:1.0: 2 ports detected Oct 26 22:54:35 KBNAS kernel: usb 2-1.3: USB disconnect, device number 59 Oct 26 22:54:35 KBNAS kernel: usb 2-1.3: new high-speed USB device number 60 using ehci-pci Oct 26 22:54:35 KBNAS kernel: hub 2-1.3:1.0: USB hub found Oct 26 22:54:35 KBNAS kernel: hub 2-1.3:1.0: 2 ports detected Oct 26 22:56:01 KBNAS kernel: usb 2-1.3: USB disconnect, device number 60 Oct 26 22:56:02 KBNAS kernel: usb 2-1.3: new high-speed USB device number 61 using ehci-pci Oct 26 22:56:02 KBNAS kernel: hub 2-1.3:1.0: USB hub found Oct 26 22:56:02 KBNAS kernel: hub 2-1.3:1.0: 2 ports detected Oct 26 22:56:56 KBNAS kernel: usb 2-1.3: USB disconnect, device number 61 Oct 26 22:56:57 KBNAS kernel: usb 2-1.3: new high-speed USB device number 62 using ehci-pci Oct 26 22:56:57 KBNAS kernel: hub 2-1.3:1.0: USB hub found Oct 26 22:56:57 KBNAS kernel: hub 2-1.3:1.0: 2 ports detected Oct 26 22:57:52 KBNAS kernel: usb 2-1.3: USB disconnect, device number 62 Oct 26 22:57:52 KBNAS kernel: usb 2-1.3: new high-speed USB device number 63 using ehci-pci Oct 26 22:57:53 KBNAS kernel: hub 2-1.3:1.0: USB hub found Oct 26 22:57:53 KBNAS kernel: hub 2-1.3:1.0: 2 ports detected Oct 26 22:59:19 KBNAS kernel: usb 2-1.3: USB disconnect, device number 63 Oct 26 22:59:19 KBNAS kernel: usb 2-1.3: new high-speed USB device number 64 using ehci-pci Oct 26 22:59:19 KBNAS kernel: hub 2-1.3:1.0: USB hub found Oct 26 22:59:19 KBNAS kernel: hub 2-1.3:1.0: 2 ports detected Any other ideas, please? @JorgeB kbnas-diagnostics-20231026-2313.zip

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

So I'd be a very happy man if I got £5 for every eyeroll, muttered RTFM, Search the forum, noob, just do it properly, etc. kind of comment. I'm even surprised nobody tried to 'coach me' to use paid support with the Unraid Guru's! I'd also be happy with any 'here's what worked for me' type of responses... I've made a lot of progress by using Cloudflared instead of using any flavour of reverse-proxying. Something isn't/wasn't right with my config and I just couldn't get to the bottom of it.

Thanks Zeze21!

What's showing in your syslog? If you can't access it via console, set up a syslog server..

I'm gutted for you mate. I hope you turn a corner with your set up.

Hello! After dumping various old disks into my array/unassigned storage, I have a whole load of media files, all over the place.. Could someone please suggest the best means of searching for these with an option of moving the results, to reorganise my 'media' shares? I know there are apps that would find them, but I don't want them scattered everywhere. Just looking for the most efficient ways in which some of you may have handled this? Thanks Kev

Me too. 👍

Hey Guys, (My unraid Docker engine works - but the 'Docker Containers' section was disabled and I couldn't submit this there!) I'm looking for some help, please... on getting my Docker Containers to respond by domain name.. Just can't seem to get it working.. I'm on Unraid 6.12.4. I have a domain and configured it in Cloudflare - I have followed stuff by SpaceInvader One and Ibracorp - Initially with Nginx Proxy Manager, and now subsequently, with Traefik... But still having access and certificate issues. With NPM, after the Error code 526, and reducing the security level in Cloudflare, I was just getting the Unraid Log-in page, instead of my apps.. With Traefik I now have the Cloudflare Error code 526 page again, even though it's supposed to have automatically set up Let'sEncrypt certs? I have a docker network and have forwarded the ports on my router... Most of the guides are old and refer to DuckDNS with outdated Unraid and outdated Cloudflare info - and then I see other refs saying don't use that use NPM/Traefik/Swag... I've gone round and round in circles. Any assistance/suggestions for main troubleshooting points would be HUGELY appreciated, because this is tiresome and totally deflating my ideas after building and upgrading my Unraid server to Plus... 🤦‍♂️

My Unraid GUI has started being unresponsive this evening.. (6.12.4) I've been working with nginx & cloudflare config and it ground to a halt - It seemed to be fixed after a restart but the system log was flooded with entries like: Oct 8 01:09:01 KBNAS nginx: 2023/10/08 01:09:01 [alert] 11885#11885: worker process 18538 exited on signal 6 - before I started the container! I'm happy to try to look for any commonalities that might give us a reproducible-on-demand scenario 👍