Squid

Delete it. I'm not doing an exception for a backup of a backup

Try deleting /config/plugins/corefreq.plg from the flash drive and reboot If that doesn't solve it, then try safe mode

Perfectly safe to ignore. During cpu initialization the mce was issued. Happens on certain hardware combinations and nothing to fret about

Never noticed that you couldn't change it To change the time yourself, edit the /config/plugins/dynamix/status-check.cron file on the flash drive and change the cron entry at the beginning, followed either by a reboot or update_cron

Try it in safe mode. Also try manually spinning up all the drives in the array before going to the VM tab

Bad port? It's still connecting at 100Mbs Not impossible for the router to only have 100Mbs support, but unlikely.

Kinda strange. The logs says that there's an mce, but there's no detail anywhere. My first guess however would be that it's related to the TDP settings in the BIOS. On Intel 10th gen cpus, the motherboard manufacturers all decided to massively overclock the CPU's by outright ignoring the TDP design limits on the processors and instead relying upon the chip's own thermal throttling to stop everything from melting down. Set the TDP limit explicitly in the BIOS to be 65 Watts and not "auto" or "4096W"

Update fcp

Update FCP

Post your diagnostics

Sorry, missed this You'll need to post the contents of that file here

Unfortunately, no. User scripts leverages the built-in dynamix log viewer, so it's limited by it's display constraints.

Sure. Done Always takes a while though for authors to notice and add the applicable category, but as soon as they do it'll begin to appear in CA

Do you still have access to the local console or can SSH into the server? If so, diagnostics If not, then a reboot is the only thing you can do. An parity check from the unclean shutdown will result.

Yup

Yeah, nothing on the flash drive is directly executable, so the sh (or /bin/bash) is required

I would actually investigate changing the cable. It's been forever since I've seen any router only support 100Mb/s on it's link, so it appears to be a bad cable since that's the link speed it's connecting at. And if it's a bad cable, you're going to have tons of issues

Also, regarding the slowdowns, you might want to check the what the BIOS has for thermal TDP's. Vast (ie: nearly every) motherboard manufacturer on the chipsets for the 10th and 11th gen CPUs figured it would be a good idea to do an "inherent" overclock on the CPUs by setting the TDPs to effectively be 4096 Watts and hope that the CPU would throttle itself down to prevent a nuclear accident in the case. It should be illegal (but isn't). Set your TDPs in the motherboard to be 65Watts, NOT auto (or 4096W)

@ChatNoir This is what I look at to determine the above Mar 9 13:28:34 iron kernel: smpboot: CPU0: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz (family: 0x6, model: 0xa5, stepping: 0x5) Mar 9 13:28:34 iron kernel: mce: [Hardware Error]: Machine check events logged Mar 9 13:28:34 iron kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee0000000040110a Mar 9 13:28:34 iron kernel: mce: [Hardware Error]: TSC 0 ADDR fef1e680 MISC 43880004086 Mar 9 13:28:34 iron kernel: mce: [Hardware Error]: PROCESSOR 0:a0655 TIME 1646861272 SOCKET 0 APIC 0 microcode ec Mar 9 13:28:34 iron kernel: Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver. Mar 9 13:28:34 iron kernel: ... version: 4 Mar 9 13:28:34 iron kernel: ... bit width: 48 Mar 9 13:28:34 iron kernel: ... generic registers: 4 Mar 9 13:28:34 iron kernel: ... value mask: 0000ffffffffffff Mar 9 13:28:34 iron kernel: ... max period: 00007fffffffffff Mar 9 13:28:34 iron kernel: ... fixed-purpose events: 3 Mar 9 13:28:34 iron kernel: ... event mask: 000000070000000f Mar 9 13:28:34 iron kernel: rcu: Hierarchical SRCU implementation. Mar 9 13:28:34 iron kernel: smp: Bringing up secondary CPUs ... Mar 9 13:28:34 iron kernel: x86: Booting SMP configuration: Mar 9 13:28:34 iron kernel: .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15 First line is the start of bringing the cores online and it ends at the last line. If there's an mce in the middle of it, its nothing to worry about.

The mce happened at CPU initialization and happens with certain hardware combinations. Probably related to microcode updates

Lots of stuff regarding that. I'd start with looking at the SpaceInvader One videos on you tube regarding VMs, and in particular dumping a vbios.

The default settings for those 2 folders are use cache: prefer and cache pool: cache. If you don't have a cache pool named "cache" then you'll see what you're indeed seeing. Yes, lots of apps assume a pool named "cache" in the templates, but the apps tab automatically adjusts things to reflect your system when installing. IE: the template references /mnt/cache/blah and you don't have a cache pool, but do have a pool name "ssd", the references will be automatically adjusted to /mnt/ssd/blah

OK, I *think* I see why and have put a fix in for next rev. Don't understand why it only affected Home - New - Show More, and not everything else, but I'll investigate further. Thanks Fixed On this weekend's release. If you run into this again, just delete the .cfg file from /config/plugins/community.applications on the flash drive

On mobile so can't really look at the diagnostics, but try setting static dns addresses in settings network settings of 208.67.222.222 and 208.67.220.220