Squid

The local syslog server is for other computers on your network to send their logs to. What you're looking to enable is mirror syslog to flash

You need to post the entire diagnostics.zip file

You'll have to start it over

First off, massive amounts of login attempts from around the world. You should take your server out of the DMZ or stop forwarding ssh ports. Use a reverse proxy / VPN if you need to access your server remotely ec 17 04:39:19 Tower in.telnetd[19758]: connect from 14.55.142.160 (14.55.142.160) Dec 17 04:39:21 Tower in.telnetd[19828]: connect from 186.179.253.232 (186.179.253.232) Dec 17 04:39:22 Tower sshd[19793]: Failed password for root from 222.186.175.163 port 24522 ssh2 Dec 17 04:39:24 Tower sshd[19793]: Received disconnect from 222.186.175.163 port 24522:11: [preauth] Dec 17 04:39:24 Tower sshd[19793]: Disconnected from authenticating user root 222.186.175.163 port 24522 [preauth] Dec 17 04:39:33 Tower sshd[20197]: Invalid user bruscino from 178.62.90.135 port 48534 Dec 17 04:39:33 Tower sshd[20197]: error: Could not get shadow information for NOUSER Dec 17 04:39:33 Tower sshd[20197]: Failed password for invalid user bruscino from 178.62.90.135 port 48534 ssh2 Dec 17 04:39:33 Tower sshd[20197]: Received disconnect from 178.62.90.135 port 48534:11: Bye Bye [preauth] Dec 17 04:39:33 Tower sshd[20197]: Disconnected from invalid user bruscino 178.62.90.135 port 48534 [preauth] Dec 17 04:39:34 Tower in.telnetd[20242]: connect from 68.190.218.211 (68.190.218.211) Dec 17 04:39:35 Tower in.telnetd[20269]: connect from 170.238.126.136 (170.238.126.136) Dec 17 04:39:39 Tower sshd[20372]: Invalid user azzuolo from 45.55.177.170 port 45122 Dec 17 04:39:39 Tower sshd[20372]: error: Could not get shadow information for NOUSER Dec 17 04:39:39 Tower sshd[20372]: Failed password for invalid user azzuolo from 45.55.177.170 port 45122 ssh2 Dec 17 04:39:39 Tower sshd[20372]: Received disconnect from 45.55.177.170 port 45122:11: Bye Bye [preauth] Dec 17 04:39:39 Tower sshd[20372]: Disconnected from invalid user azzuolo 45.55.177.170 port 45122 [preauth] Dec 17 04:39:40 Tower in.telnetd[20440]: connect from 14.55.142.160 (14.55.142.160) Dec 17 04:39:42 Tower in.telnetd[20510]: connect from 186.179.253.232 (186.179.253.232) Dec 17 04:39:47 Tower sshd[20611]: Failed password for root from 112.85.42.189 port 16628 ssh2 ### [PREVIOUS LINE REPEATED 2 TIMES] ### Dec 17 04:39:48 Tower sshd[20611]: Received disconnect from 112.85.42.189 port 16628:11: [preauth] Dec 17 04:39:48 Tower sshd[20611]: Disconnected from authenticating user root 112.85.42.189 port 16628 [preauth] Dec 17 04:39:53 Tower sshd[20846]: Failed password for root from 51.15.87.74 port 44280 ssh2 Dec 17 04:39:53 Tower sshd[20846]: Received disconnect from 51.15.87.74 port 44280:11: Bye Bye [preauth] Dec 17 04:39:53 Tower sshd[20846]: Disconnected from authenticating user root 51.15.87.74 port 44280 [preauth] Dec 17 04:39:55 Tower in.telnetd[20916]: connect from 170.238.126.136 (170.238.126.136) Dec 17 04:39:55 Tower in.telnetd[20950]: connect from 68.190.218.211 (68.190.218.211) The actual problem though is that it looks like you've got file system corruption on disk 1. You need to https://wiki.unraid.net/Check_Disk_Filesystems

in your "go" file (config folder on the flash drive) you've got /usr/local/sbin/emhttp -p $port & This should simply be /usr/local/sbin/emhttp & If you need to change the port, you have to do that via Settings - Management Settings

I've never had a problem with SMB transfers. The owner always winds up being my user, not "nobody" but the permissions are always correct so no big deal and something I've never worried about (or cared about)

Post your diagnostics

99.9% of the time, lost data is because of user error, not unRaid But, the log show nothing (and is after a reboot). What exactly are you expecting to be seeing, and what did you do to try and recover when you first noticed the problem a week ago

If everything is fine upstairs, but pooched downstairs, its not the stick. It's the cabling / switch

My justification based on that convo was that since the SASLP/SAS2LP are very problematic and not recommended at all was to remove the test altogether rather than invest the time and energy in debugging a double check to see if the IRQ in question was using the mvsas driver (not to mention if it was another sata controller utilizing the interrupt) Basically, I look at everything that FCP tells people to post about, and keep a tally of the answers. If the vast majority of answers is don't worry about it, then the test winds up being more trouble than its worth for all concerned. On the other hand, for those few users where this actually does affect things, the nobody cared message is logged, and when asking for assistance on the forums it can be easily discerned via diagnostics

Suggestion by Johnnie Black, and when it does happen it very rarely impacts performance, so at the end of the day it was removed to stop the answers on the forum that basically said "don't worry about it"

Since you had it installed already, you should still be able to find it within Apps, Previous Apps. But it is recommended to switch to calibre instead

The others are nothing. Usual boot up stuff

You need to post the entire diagnostics.zip file before you reboot.

I use these https://www.ebay.ca/itm/Internal-Header-Adapter-2-Ports-A-USB2-0-Female-9Pin-Motherboard-to-Double-Layer/323877364954?epid=13012681081&hash=item4b689864da:g:VaAAAOSw7Excf5Cn

Missed that you tried that. What was the output?

Looks like you need to run the file system check on both disk 1 & 4

Generally you would install a vnc server on the VM (or if Windows, use RDP) to do this and passthrough, but you still wouldn't have access to it from the dashboard / vm tab.

No haven't tried, but I would guess that the property you're using is "isequal", which doesn't look like it supports wild cards (neither does "contains") You'd have to use "startswith" or "regex". Not a real use for this, but was simply curious

It's your cache drive that's been remounted as read-only. BTRFS I'm not comfortable with, so will let someone else ( @johnnie.black advise on this ), but to me it appears that it's fully allocated. Overall: Device size: 465.77GiB Device allocated: 465.77GiB Device unallocated: 2.05MiB Device missing: 0.00B Used: 219.50GiB Free (estimated): 122.30GiB (min: 122.30GiB) Data ratio: 2.00 Metadata ratio: 2.00 Global reserve: 61.23MiB (used: 3.36MiB) Data Metadata System Id Path RAID1 RAID1 RAID1 Unallocated -- --------- --------- --------- -------- ----------- 1 /dev/sdg1 231.85GiB 1.00GiB 32.00MiB 1.02MiB 2 /dev/sdh1 231.85GiB 1.00GiB 32.00MiB 1.02MiB -- --------- --------- --------- -------- ----------- Total 231.85GiB 1.00GiB 32.00MiB 2.05MiB Used 109.55GiB 199.52MiB 48.00KiB

*Usually*, it can be solved by simply using a USB2 port Kinda depends if this was a one off (you jarred it eg), or if it repeats

Best to just delete the docker.img and reinstall the apps. 5 minutes and everything will be the same as it's supposed to be. https://forums.unraid.net/topic/57181-docker-faq/#comment-564309

Those errors more imply that the flash drive dropped offline or was removed

Check the BIOS boot order