Squid

What do you mean you can see the pages but can't interact with them....

Best guess is that you've disturbed the cabling and now its hit and miss on whether it makes a proper connection and keeps it. If anything happens again, post your diagnostics before you reboot.

/media is mapped to /mnt, so all of your disks should show up there. Along with "user" which is all the the shares combined from all disks Are you saying that nothing else is showing up in /media except for disk14? You could always try editing that path mapping and changing the access mode to be Read/Write:SLAVE and see if that makes a difference (in theory it shouldn't matter though)

Changed Status to Closed

Not a bug. The templates for the containers that you added are no longer on the flash drive or corrupted. They are stored in /config/plugins/dockerMan/templates-user For docker being full, Container Size on the Docker tab should offer some insights as to what is going on

Are you talking about the WebUI entry on the template? It was probably already set up with something akin to http://[IP]:[PORT80]/ Where when the WebUI resolves the URL it goes to the IP address of the server (if in host or bridge mode) or the IP of the container itself if not in host / bridge and the port 80 is mapped to in the container (bridge mode) or port 80 for all other networking modes.

You should reply back with your diagnostics

Yeah. Hover over the Icon or the Info button will auto open the sidebar after ~3sec Similar to how the forum works, but can be disabled.

What ever command you need to use you would enter it into a new script with the User Scripts plugin with its frequency set to be "At Initial Array Start" Alternatively, you can edit the file "go" (/config on the flash drive) and add in the command there.

Have you tried specifying the vBIOS file for the GPU? There's a video here

Pretty much....

Are you specifying "LOCALHOST" or the IP address of the server? LOCALHOST within a container does not mean the server's IP. It refers to the IP of the container itself. You would need to specify the IP address of the server and the port you've specified for the database FWIW, I just installed Nextcloud and MariaDB (both from LSIO) with no apparent ill effects and no logged message like what you're seeing....

This topic: The applicable modifications to an OS file will be listed in there. But much easier to simply upgrade the OS to 6.11 and then install the plugin instead.

And it should now be gone....

Thank you. This will get fixed up tonight. Template error on that app....

Don't think it's CA. You need to have him look at page source and see what function is in that line (2510) Check Plugin (built into the OS) seems like it's not the cause since it succeeds for plugins and returns the response.

What other plugins did you try to install? "Pending" comes from the underlying plugin system and means that another plugin has not finished installing (or there's a bug in the system). To clear it out, as you won't be able to handle any plugin related operation you need to either reboot or rm /tmp/plugins/pluginPending/*

Flash drive read only??? Also any weird punctuation etc in the script names?

Not your complete problem, but you've got two SSDs (disk 1 & 2) and a spinner (parity) Reads are going to be fast, but writes will be slow. The docker image and appdata are effectively read and written to constantly, so the write penalty will be huge. You're going to be better off setting up the SSDs as a cache pool (trim isn't supported in the array). This will significantly increase your speed / response (orders of magnitude) You've got tons of "invalid opcodes" being logged. Could be simple program errors, but also could be bad memory. Run memtest for at least a couple of passes.

There is a new plugin to also tweak the AD settings to try and come up with the solution(s)

Anything in the System Event Log in the BIOS? Enable the syslog server (mirror to flash) and upload the resulting file (logs folder of flash drive) after the next crash

ca.cleanup.appdata.plg - 2022.10.21 (Up to date) Running clean up appdata (if you have) effectively deletes the appdata for anything not installed, so if you did this for calibre (as an example), it would indeed be a new install.

You have a bunch of shares like that appdata shareUseCache="only" # Share exists on cache, disk1 d------d shareUseCache="only" # Share exists on cache, disk1 t-------e shareUseCache="only" # Share exists on cache, disk1 And the same steps need to be done for all of them. Set them to "Prefer" and run mover. Should be noted that mover cannot move any opened files so that's why Docker and VMs need to be disabled in Settings for it to move those related files. If you're still having issues, then post the output of ls -ail /mnt/disk1/appdata

Stop overclocking your memory via the XMP profile. Run it instead at the speed you actually bought. 2133 not 3600 (ie: run at SPD speed not XMP), and also run memtest for minimum of a pass or 2

First thing to do is to ensure that your TDW is set correctly within the BIOS. And NOT Auto. In your case it should be set to 125W. "Auto" will usually run your CPU in an inherent overclock situation where it will completely ignore the TDP limits of your processor.