Squid

Post your diagnostics

Or if they're containing data, then the Unassigned Devices Plugin.

To get the fan sensors working (with system temp plugin) on the Vision G (and possibly other boards), sensors-detect Answer Yes to everything. With luck you'll see in the middle of all this, Trying family `ITE'... Yes Found unknown chip with ID 0x8688 Add to your go file (/config/go on the flash drive). This forces the 8688 to be recognized as an 8628 modprobe it87 force_id=0x8628 Reboot. You should have fan speeds showing once you detect the sensors in System Temp. If you don't, then try adding the following to the append line in syslinux.cfg acpi_enforce_resources=lax

Post your diagnostics

Probably just because nothing has been set yet for any scheduled jobs etc. Initially, safe to ignore. There is no such thing. You can either use the USB Creator Tool (as you did) or download the zip file, extract the files, rename the flash drive to UNRAID, run make_bootable (as administrator)

Probably best to post in the Unassigned Disks thread

1 * * * * means to run at the first minute of every hour, every day etc. You want * * * * *

Anything listed in the system's event log in the bios?

Still present. Delete /config/vfio-pci.cfg from the flash drive. Reboot and retry

Looks like you've bound some items for passthrough to a VM. Uncheck them all and try again (Tools - System Devices)

From the local console (or via SSH) diagnostics File will be saved onto the flash drive (logs folder)

It's something misconfigured within say Radarr / Sabnzbd that's creating the folder at /mnt/user

Interesting read: https://www.gamersnexus.net/guides/3590-dont-run-z490-motherboards-with-default-settings-for-your-build In my particular case, I just picked up an i9-10900 (non k), and couldn't figure out why the Intel stock Cooler wouldn't do anything at all to cool down the chip under load. Sure, stock coolers aren't all that great, but they are designed to handle the CPUs in a non OC situation. But, when I'm running a simple passmark benchmark on a VM and watching the CPU temp go over 100C I know that there's something very wrong somewhere. A little investigation, and I see that all of the cores are hitting 5GHz+, which I know is way way out of spec for the chip. Look at the BIOS, and all of the power settings are set to be "Auto", which when reading the manual (Gigabyte Z490 Vision G) means that it utilizes the specs of the processor. Couldn't be more wrong. Some further investigation reveals that by Auto Gigabyte means Maximum, which means it was setting the max TDP as 4096 watts. Manually set it back down to where it's actually supposed to be (65Watts), and everything starts working perfectly. Chip nice and cool even at full load. Nice of the MB manufacturer's to actually force you to enable XMP, but they default the BIOS to knowingly run the chips way out of spec. Something to be aware of for any one who doesn't OC, (or who does OC but still wants the chip to survive it)

Did you try this https://forums.unraid.net/topic/91163-solved-webui-is-messed-up/?tab=comments#comment-853465

Dec 14 14:48:32 v1ew-s0urce kernel: [Hardware Error]: Corrected error, no action required. Dec 14 14:48:32 v1ew-s0urce kernel: [Hardware Error]: CPU:0 (17:71:0) MC27_STATUS[-|CE|MiscV|-|-|-|SyndV|-|-|-]: 0x982000000002080b Dec 14 14:48:32 v1ew-s0urce kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001 Dec 14 14:48:32 v1ew-s0urce kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error. Dec 14 14:48:32 v1ew-s0urce kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout) IIRC, Ryzen has problems with Overclocking memory in some circumstances. Run the memory at the SPD speed to see if that makes a difference.

That's how docker itself handles things. There's no problems with a zero byte pull (as you've noticed). Unraid itself however did automatically delete your existing icon under the assumption that as part of the update procedure. It'll get re-downloaded when your internet is back up and running and you hit either the dashboard / docker pages

Are you sure it's even plugged in? Can you see it within the BIOS? Not quite sure what you mean by this. They haven't failed. The necessary information is stored on the flash drive. But, all of the meta data for the apps (eg: your library information in Plex) was stored within the appdata share which is (presumably) on the now missing disk 1.

Then try reinstalling CA, but in it's settings make sure that Send Emergency Notifications is turned off.

Then post the diagnostics

There's probably more information in the Servers Event Log about this.

edac_mce_amd is included in Unraid for the last couple of years The message is simply a reminder to everyone else in the world that the author(s) of mcelog have no idea how to properly word an informational sentence or they are not native English speakers and utilized a TI-99/4A to translate the actual message into English. IE: It's simply telling you that the mcelog default driver (Intel) doesn't support the chip. Its automatically using the AMD module instead

????

extremely unlikely

So long as you have the docker.img set on the array, you will pretty much always have the 2 drives spun up. Every container is like a miniature OS, and every write will keep those 2 drives spun up. By and large the vast majority of people place the docker.img file onto a cache drive which is outside of the parity protected array so that 2 drives do not always need to be spun up. Reason why stopping the containers doesn't fix the spindown is that the service itself is still running. But, yes 6.9 does solve the excessive write issue (really only affected certain SSDs)