Squid

It's those lines that FCP looked at to trigger the warning. They're all from the same computer which is probably one one your local network. Since the time frame is all within 45 seconds, I'd guess that it was you yourself who triggered it, but I'm not at your house and can't particularly say for sure.

@SpencerJ itemized it step by step in the blog (although sometimes you do have to read between the lines). For an easier install, you can use the RDP-boinc app instead which means you don't need to worry about configuring the manager on a client computer Same thing will happen with BOINC unless you turn down it's CPU preferences (which you can also do in F@H). This odds on means that your BIOS is bitching and complaining that you've exceeded a temperature warning you've set within it.

Mar 12 11:38:02 Jewel login[10832]: invalid password for 'root' on '/dev/pts/3' from 'DESKTOP-E5F9MLD.localdomain' Mar 12 11:38:06 Jewel login[10832]: invalid password for 'UNKNOWN' on '/dev/pts/3' from 'DESKTOP-E5F9MLD.localdomain' ### [PREVIOUS LINE REPEATED 3 TIMES] ### Mar 12 11:38:15 Jewel login[10832]: REPEATED login failures on '/dev/pts/3' from 'DESKTOP-E5F9MLD.localdomain' Mar 12 11:38:18 Jewel in.telnetd[12038]: connect from 192.168.5.5 (192.168.5.5) Mar 12 11:38:18 Jewel login[12039]: invalid password for 'UNKNOWN' on '/dev/pts/3' from 'DESKTOP-E5F9MLD.localdomain' ### [PREVIOUS LINE REPEATED 2 TIMES] ### Mar 12 11:38:27 Jewel login[12039]: invalid password for 'root' on '/dev/pts/3' from 'DESKTOP-E5F9MLD.localdomain' ### [PREVIOUS LINE REPEATED 1 TIMES] ### Mar 12 11:38:30 Jewel login[12039]: REPEATED login failures on '/dev/pts/3' from 'DESKTOP-E5F9MLD.localdomain' Mar 12 11:38:33 Jewel in.telnetd[13520]: connect from 192.168.5.5 (192.168.5.5) Mar 12 11:38:33 Jewel login[13521]: invalid password for 'root' on '/dev/pts/3' from 'DESKTOP-E5F9MLD.localdomain' Mar 12 11:38:36 Jewel login[13521]: invalid password for 'UNKNOWN' on '/dev/pts/3' from 'DESKTOP-E5F9MLD.localdomain' ### [PREVIOUS LINE REPEATED 2 TIMES] ### Mar 12 11:38:45 Jewel login[13521]: invalid password for 'root' on '/dev/pts/3' from 'DESKTOP-E5F9MLD.localdomain' Mar 12 11:38:45 Jewel login[13521]: REPEATED login failures on '/dev/pts/3' from 'DESKTOP-E5F9MLD.localdomain'

What warnings? Post your diagnostics (Tools - Diagnostics)

yes

Yes you would need the unraid nvidia build

The vm will pause because it cant allocate any more physical space to the vdisk

Can you access the shares via ip address? Or is the that you can see them but not access them?

The windows client also does the same thing

In the smb config change /UNRAID/disks/ramdisk to be /mnt/disks/ramdisk Add this line to your go file (/config/go on the flash drive) mkdir -p /mnt/disks/ramdisk Reboot and ramdisk is now a share on the network

With an amd gpu, yes a vm is your best option to do gpu folding

If you really want to have it within /mnt, create it somewhere within /mnt/disks (ie: /mnt/disks/ramdisk). The particular subfolder is pretty much guaranteed that unRaid will never try and touch it.

yes

No. Because the fuse driver resolves everything within it to be one physical drives.

Edit the template and pin it to certain CPUs. Or play with the slider bar to set how it runs. Or set it's priority via this to let other cpu hungry apps have priority (Plex / Jellyfin). Or any combination of the above.

I'm moving the support link for both boinc and rdp-boinc (aptalca) from the author specified ones to instead be this thread.

Did you make a fresh install? If so, the files that it looks for are gone, unless you have a backup or the original stick (they are the contents of /config/plugins/dockerMan/templates-user on the flash drive

Apps Tab. Previous Apps link along the left side of it's page

Not following what you're talking about. This thread is about creating a smb share to something completely outside of unRaid's (and Unassigned Devices) control. Anything share created with this method will most definitely not appear on the dashboard or in the shares tab.

You don't need to click run in background. All you have to do is set the cron and hit apply down at the bottom. As to why it's doing what it's doing no one can answer without seeing the exact script.

Tools - Diagnostics. Post entire ZIP file

You need to post your diagnostics

This shouldn't have anything to do with unRaid at all. IE: I can attempt to paste to any share I want no problems. I can even try and paste into a share I only have read-only access to (it'll fail, but Paste is still there)

Oops I missed that one... thanks...

Situation hasn't changed, and I don't foresee it changing anytime soon.