Squid

Don't know much about NFS. SMB should mount however

shareExport="-" Checking your Media share, it's not exported. You need to export it on the SMB settings for it to be available on the network

Is the array started? Post your diagnostics

Look on the calendar?

Have you tried not running unmanic? OTOH it would be a memory pig. Alternatively, limit the memory available to the various containers via ExtraParameters --memory=4G

6.10. 6.12.8+ was a revamp of the settings for TimeMachine. Prior to 6.12.8 you could get TM to fail on Unraid no problem, and it would intermittently fail for apparently no reason at all. 6.12.8+ I was completely unable to manage to get TM to ever fail, no matter what I did

First thing I'd do is run memtest from the boot menu for at least a couple of passes. You've got a ton of general protection faults which a lot of times is caused by bad memory. You should also be running the memory at its actual speed of 2133 (SPD) instead of the overclocked XMP speed of 3200. All overclocks introduce instability.

Where's that file from? It's not corrupted, but FCP considers any .cfg file in /config to be a valid ini file, which it technically isn't because of the quotes and brackets in the comments

Because I never expected for the OS to reach 6.12.10 so it was marked as the maximum version allowed of 6.12.9 Fixed. Should reappear in Apps shortly

Fixed

I have nothing to do with this plugin anymore. You want @hugenbdd

Agree with what I've been doing for the last 5 years or not. I'm good with everyone's opinion and can understand both sides of the argument. But, know that like everything else in CA, these things get tested to death to ensure that they are completely harmless, and functionality isn't impeded, and watch like a hawk every posting to ensure that nothing has gone awry. CA is a passion project. Last year's tribute to the bat if you chose to continue with the homage didn't affect anything (unless you were unable to do a handstand). This year, even if you didn't "revert" to the author dictated images upon installations the author's images would appear in the docker tab, and in all cases it's a simple one click to restore that's clearly communicated. My personal opinion regarding this stuff is that it shows that I actually do care about CA, it's security, and this community. I'm not the type of person (probably few are) who could survive long in a coding factory fashioned after a sweatshop. (Pretty sure that no one else in a space invader one interview inadvertently dropped a dick joke that made it through the sensors) But, everyone did miss the biggest joke of all. While every app had a randomly selected photo (changed every 2 hours), right on the home page (Spotlight section), the "unbalanced" app had a specific picture pinned to it for the duration of the day. While Tom et al did give a go ahead for this, any and all blame / anger / misgivings should get thrown my way. I am glad however that my original idea / planning for this year I did ultimately decide against. It was going to leverage a coding change which is being put into place for a different legitimate reason, but after looking at how the end result turned out I figured it would completely mess everyone up. Either way, as far as I'm concerned, debate about yesterday's event should now be over. What's done is done and let's all get back to business.

Can you enable the syslog server (mirror to flash) and after the next crash, reply back with the syslog that'll be stored in /logs on the flash drive

FWIW, I've been gradually simplifying things on the servers in the house to handle that scenario. To make them easier to run / maintain with little if any management from the better half. But, I also worry that upon my passing no one would be able to change the input on the TV either.

Delete that file (Larry) on the flash drive

rm /boot/config/plugins/community.applications/larry lol

Also, does fix common problems say anything?

Banner says exactly what to do. Just go to settings

You'd have to post your diagnostics and a screenshot of your parity schedule settings

This would probably be your best way to handle this and work through it's webGUI settings, paths / ports rather than whatever dependencies (and managing those dependencies / any conflicts etc in the OS)

exactly the same. Generally, you only need the local GUI if your day-to-day computer is actually a VM running on the server or if you run into any network problem. Over the last 12 years, I've never once had a server set to use the local GUI.

The licence is tied to the flash drive, and the computer it is used on is irrelevant. Copying over from one flash to another the /config folder (except for the .key file for that flash drive) moves the entire configuration from one to the other.

Nothing specific, but FYI when replacing fans, most people do it because of the noise level. One thing to bear in mind however is that especially when you're dealing with drive bays, higher CFM (which your Noctua may or may not have over the stock fans) may actually be worse for cooling. CFM has no bearing on trying to pull the air through the very small cracks in drive bays. For that you need fans which have high static pressure. The two ratings do not always conform to each other. IE: High CFM != high static pressure. But for specifics, have you cleaned out the little gaps in the bays? If they're clogged up with dust, then a high CFM but low static pressure won't have a hope of pulling the air through whereas a high static pressure but low CFM will do a better job on clocked gaps.

Try editing the path and select Slave as the access mode. EG: Read/Write: SLAVE