Squid

You might want to run the check filesystem against disk 4 May 16 09:49:37 Tower kernel: XFS (md4p1): Per-AG reservation for AG 12 failed. Filesystem may run out of space. Or look at the SMART information from within your controller's BIOS if possible. The SMART isn't showing up because of how the controller is configured, but that message sounds like the drive is out of its spare sectors to reallocate defects Also, disk 5, 4, 3 and disk 1 (and more) are continually resetting themselves. Poor connection at the SAS connector or power system? Reseat everything

Nothing to be done. Just replace the old drives with the new ones one at a time and start the array and the OS will rebuild the appropriate contents and expand the file system to take advantage of the extra space (once you get to the data drives)

And include a copy / paste (no screenshots) of what appears within tools - registration

The link in the pinned post only has compatibility down to 6.9.0 Obvious question is why not upgrade the OS?

Because of a typo of mine. Should be good in about 10 minutes

I would try deleting the contents of /config/ssl and /config/ssh on the flash drive, reboot and try again

Wrong support thread. But, what it's saying there is that an app you named jellyseer-1 was using .../appdata/jellyseer What is the appdata (/config) path for what the container is you currently have installed?

Nothing to think about. It's there. IE: Can't fix what ain't broke.

FWIW, readability as a whole along with general aesthetics was better previously than now currently. While it is usable, I definitely prefer how it was.

Effectively unlimited compared to the size of drives you can buy. While there may be some limitations somewhere over what the theory is on file system maximums (eg: XFS supports a maximum 8 exobyte drive size), not currently available hard drive even remotely comes close to this size.

Your server is unable to reach either GitHub.com or Limetech's mirror of the application feed. Fix Common Problems, and diagnostics also shows this behaviour. Assuming that there is normally no issues with reaching them due to your geographic location, a complete reboot of your network system (modem, router, all switches) would be the first thing I'd try. Also, if you're using jumbo frames (probably not) then disable them

Wrong thread lol

Dashboard considers I/O wait in it's displays. Next time it happens, reply back with your diagnostics before you reboot

You need to contact support. Include a copy & paste (no screenshots) of what shows up within Tools - Registration

Version that you're running is from the new dev.

/mnt/user is a unified view of all the shares. Every share exists within there, along with /mnt/diskX (or /mnt/cache)

Because appdata also exists on disk3. Set the secondary storage to be array with mover action of array --> cache, stop the docker service in Settings -> docker and run mover.

And on a reboot the patch shows as not being installed in the plugins tab (don't worry about the install errors one)

Long standing issue (fixed I believe in 6.13). It also has the net result of whenever you go to the VMs tab it's a given that all/most of your drives will spin up

Fixed next release. Thanks

You can admit it. Annoying me is also one of your goals 💋

You're probably also seeing a banner that's warning about CA and PHP errors being set to display on the screen. Unlike the rest of the GUI, CA's server side executables only send JSON responses. So any PHP error (when set to display), results in the browser receiving the JSON and the error which results in a JSON syntax error, which then results in more or less a fatal error as the above. But, thanks for finding In this case, someone listed the same Branch Tag in a template multiple times. No clue who did that mistake on a template, but CA will now drop the duplicate tag altogether in that circumstance.

Since the language you're using is Chinese, have you installed the Chinese Proxy Manager? Your server is unable to reach either GitHub or the Limetech hosted alternate feed quite possibly due to the Great Firewall

When you install When you install it does an error show up in the popup window? You can always post your diagnostics too.

Check every docker container you have and see if there's a direct reference on one or more of them to /mnt/cache. Likely need to hit the "down caret" to see all the path mappings for some of them.