Squid

https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6120-rc2-available-r2310/?tab=comments#comment-22566

There's absolutely nothing wrong with that expresion.  Have you tried rebooting?

Nothing obvious.  Try a different browser?  Clear cookies?

There is a plugin installation you did that for one reason or another did not exit correctly.  Reboot or delete /tmp/plugins/plugin-pending

It appears that the Marvel controller crashed.
 
Marvel based controllers haven't been recommended for use in servers for probably about 5 years now as their hardware / software tends to be very buggy.

Your flash drive is either corrupted, dropped offline, or you deleted the contents of /config/plugins/dockerMan/templates-user
 
But, if you're also bypassing the system now by managing via Portainer to have installed it, then it would be normal to see that error

Dynamix File Manager installed?

Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 28 00 00 00 01 80 12 b6 88 40 00 43d+11:57:14.120 READ FPDMA QUEUED ea 00 00 00 00 00 00 00 00 00 00 00 00 43d+11:57:13.644 FLUSH CACHE EXT 61 01 20 00 20 00 02 04 77 dc c0 40 00 43d+11:57:04.705 WRITE FPDMA QUEUED 61 04 00 00 18 00 02 04 77 d8 c0 40 00 43d+11:57:04.705 WRITE FPDMA QUEUED 61 04 00 00 10 00 02 04 77 d4 c0 40 00 43d+11:57:04.705 WRITE FPDMA QUEUED Error 2 [1] occurred at disk power-on lifetime: 17515 hours (729 days + 19 hours)  
Reseat the cabling.
 
Also, trimming every hour is going to decrease the lifetime of the SSD.  Once a week is more than sufficient.

Nope.  Switch the UPS's and then set it back up if the communication method / protocol has changed.

Switch to advanced view on the docker tab.  There's a startup delay option that pauses before the next app in the list is started up.

Because it'd be command line only and needs to be executed via a shell (and have the interactive shell passed to it)
 
See https://hub.docker.com/r/wrfly/ctop

Can you try from a command prompt
 
use_ssl no  
and then navigate in the browser to 192.168.1.192
 
 
 

#1 - Forget about using repositories and install Community Applications (unless the absolute only thing you ever want to run is LT's plex)
#2 - Ideally you should post what happens when you try and install the app as per this post: https://lime-technology.com/forum/index.php?topic=40937.msg481150#msg481150
 
Sight unseen of #2, I'd say you probably need to go to plugins, check for updates, and install the webUI update that'll be available.  (http://lime-technology.com/forum/index.php?topic=40937.msg463355#msg463355)

You should contact support with the email address associated with your old forum account and they should be able to assist you.

Are you using any docker apps with dedicated IP addresses (or set to network type br0 with a dynamic address)
 
If so, you will attain higher stability by switching the network type from macvlan in Settings - Docker (with the service disabled) to be ipvlan.
 
Also (either caused by the crashes or bad memory) 
Feb 24 22:11:51 Helios kernel: BTRFS error (device nvme1n1p1): block=87024451584 write time tree block corruption detected Feb 24 22:11:51 Helios kernel: BTRFS: error (device nvme1n1p1) in btrfs_commit_transaction:2418: errno=-5 IO failure (Error while writing out transaction) Feb 24 22:11:51 Helios kernel: BTRFS info (device nvme1n1p1: state E): forced readonly I'll let @JorgeB advise on the btrfs recovery, but personally I'm not a fan of using BTRFS on single device pools.  You will always obtain better stability on the pools / filesystems by using XFS unless you require the features of btrfs (of which they are minimal on a single device)

You have what appears to be a docker container that is continually restarting.
 
The docker image is in the system share which is currently on the cache drive and disk 3.  Impossible to tell from diagnostics where the docker.img file is on which of those two drives, but if its on disk 3 then what you're seeing would be expected.
 
Go to Shares, next to system hit calculate.  If you see 100G (which may be overkill) on disk 3 then that's your issue.  Stop the entire docker service in settings - docker and run mover from the main tab

Check the connections to the cache drive.  It dropped completely offline

Enable Host Access To Docker Networks in Settings - Docker (Advanced View) with the service stopped

https://forums.unraid.net/topic/134016-fix-to-a-small-issue-with-updating-oci-docker-images/page/2/#comment-1220827
 

You really should post within the plugin's support thread

The penguin is for NFS shares.  SMB shares you want to click the windows icon.  Any problems with mounting though and you post in the UD support thread.

Start with running a memtest for at least a couple of complete passes

https://forums.unraid.net/topic/134016-fix-to-a-small-issue-with-updating-oci-docker-images/page/2/#comment-1220827
 

/boot/config/plugins/dockerMan/userprefs.cfg