Squid

Looks like disk1 is shot 197 Current_Pending_Sector -O--CK 200 200 000 - 214 Problem is that I'm not 100% sure what actually happens when parity is invalid (as it's building) when a read error happens on another drive. If Parity is valid, then the system recalculates what's supposed to be on disk1 via Parity and rewrites the appropriate data. If the write fails, then the disk gets disabled. But, since in your case if Parity isn't valid the above would result in corruption on disk 1. I *think* that the system wouldn't attempt to rewrite, but I'm not 100% sure. Either way, your best course of action would be to replace disk 1 and re-copy the data. @JorgeB Do you know what the OS does in this situation?

Post your diagnostics

The one on the left is the real frequency each core is running at.

What does that mean? Did you click the icon on the docker tab and then say Remove?

Did it explicity state VT-D or just Virtualization? Virtualization options in BIOS enable VT-x. VT-d is usually buried within submenus of the BIOS

Personally, I would hope not. "In place" anything is fraught with dangers and whenever it's been offered by any other OS for stuff like filesystem change / encryption I've declined as if (just if) something goes wrong (read errors, filesystem errors etc) then you're drive is going to be in somewhat of a limbo state and half converted with basically no recourse.

In cases like this, Main is where you want to be as there's more information on it.

Note though that if you move files between shares and the use cache settings / included / excluded the moved file may wind up not respecting the destination's settings (because you're bypassing the system)

MyServers / Unraid.net plugin Those errors however seem to imply that /tmp/plugins does not exist at all. Usually this would be from doing something like having Plex transcoding to RAM and having the mappings of /transcode mapped to /tmp when it should instead be mapped to /tmp/plex

Is piHole running as a container on Unraid? Generally, I do not recommend using piHole (especially if it's running on the server) to use for your DNS There's zero ads / tracking etc within the OS to begin with If you stop the array / container you lose access to the internet from the OS

What version of Unraid. I thought I got rid of that being visible in 6.9.2, but maybe my memory is incorrect and it was 6.10

There already is. Documented here https://forums.unraid.net/topic/38619-docker-template-xml-schema/page/3/?tab=comments#comment-1015826 Support for the maintainers adding this in directly when generating the template via dockerMan will be slow until 6.10 becomes stable (the tag support has been in there for quite a while now) For other maintainers like LinuxServer that generate the templates via a script it requires them to adjust the scripts accordingly to add the tag when appropriate. Every once in a while when I've got nothing else to do I do random searches within CA and add the tag via moderation, but in the case of Hedgedoc since there's no mention of SQL within it I would not have seen it via any search. Adding the tag now. Thanks.

Not unheard of for Sonarr to not import episodes that have filenames like that.

It's a semantic change, but effectively it is a different template. If it wasn't for that semantic change in the repository, the LinuxServer Plex would have also given a Reinstall option, but because it's effectively a new template it didn't. Previous Apps is where you pretty much always want to look whenever reinstalling something and keeping your settings and not searching.

The drop down will probably disappear at some point during 6.10 but definitely by 6.11

Only if you installed another template named the exact same name. You wanted to use Apps - Previous Apps

Try settings static DNS addresses in Settings - Network Settings of 208.67.222.222 and 208.67.220.220

You shouldn't be mounting anything outside of shares within /mnt/user Use /mnt/disks/... or /mnt/remotes/... instead

Yes - Settings - CPU Pinning.

Yes, with 2 caveats Virtual Machines if you're utilizing passthrough. This will require you to reconfigure the devices, ACS override settings etc to match your new system If you utilize on either the old system or the new system a RAID controller set to JBOD mode which changes the serial numbers of the drives will require you to reconfigure the drives since the S/N's may change. Can't tell if you fall into #1, and it definitely looks like you won't fall into #2

OTOH, give it more cores. Minimum requirements are dual core, but *technically* you're only giving the VM a single core (with a HT) Also wouldn't be a bad idea to enable TPM within the BIOS (It tends to be disabled by default) What is the CPU you're using?

run the check filesystem against the cache drive Dec 26 04:30:03 Tower kernel: XFS (sdc1): Metadata corruption detected at xfs_dinode_verify+0xa5/0x52e [xfs], inode 0x60000db5 dinode Dec 26 04:30:03 Tower kernel: XFS (sdc1): Unmount and run xfs_repair Dec 26 04:30:03 Tower kernel: XFS (sdc1): First 128 bytes of corrupted metadata buffer:

You've got an old version of the template that had an issue in it. Edit the file /config/plugins/dockerMan/templates-user/my-homeassistant.xml on the flash drive and the line that says <TemplateURL>someURLhere</TemplateURL> change it to <TemplateURL>false</TemplateURL> and the devices will not come back on updates.

That's just the daemon starting over again. And will happen weekly