Squid

Update it after

Because right now we don't know if the GUI can be loaded at all...

In case of a duplicate, the lowest numbered disk with the dupe takes precedence. However, dupes should more or less be impossible to happen if you reference your appdata share by /mnt/user

/mnt/user/appdata points to ALL disks including cachepools that contain the folder appdata.

Not at the moment. It is on a todo list

Does the system boot fine if you select one of the GUI modes from the boot menu?

Unlikely that the original drive isn't corrupted, since the parity information is reflecting a corruption on the disk. You really should run memtest for at least a couple of passes to rule out it being the cause. Any (keeping the original drive untouched) fix the filesystem on the rebuilt drive (remove the -n)

That's probably the absolute easiest thing you can accomplish on Unraid. So long as you never created any custom networks. Delete the image. Apps Previous Apps, check off what you want and hit install. Before you get back from making a coffee the system is back the exact same way with no input, though etc on your part.

Did you actually see that message in the banner??? Update all plugins. Make a backup of the flash drive. Then upgrade

About the only thing which would be to remove any excess folders from /config/plugins that are from plugins which no longer installed. Realistically though, most plugins would automatically remove their directories (or should). However, there are also "system" folders (eg: dockerMan) which cannot be removed To get rid of excess templates for docker containers, go to Apps, Previous Apps and delete (check off and then delete) the ones which you are no longer / have no need for anymore

Remove the mover tuning plugin and it should work then repost your diagnostics into it's support thread

Disable any and all browser extensions and try again

What I'd try. In Settings, Network Settings disable bonding and bridging. No need for it since you've only got the single NIC After that, try creating a new docker.img (Settings - Docker - Disable the Service). Give it a different name than docker.img so that we can revert back if necessary. Then try reinstalling your apps from Apps, Previous Apps

Nov 24 04:45:25 Unraid kernel: BTRFS info (device sdc1: state E): forced readonly Wait for @JorgeB to look at this and advise. He's the resident Uber Expert par none around here

1 - We always need diagnostics (preferably grabbed while this is happening) 2 - If anyone in a position to fix the problem could ever replicate it, then it would be fixed.

Does at least the navigation bar / header show up? Reboot into safe mode

What's not reliable about it? It works. Only "issue" (and it's not an issue if you really think about what's going on under the hood) is if you attempt to pin containers to multiple isolated cores. Since you're not running any VMs, doubtful you've got any isolated cores

Looks like CT500MX500SSD1_2303E69FAF02-2023-07-14 cache2 (sdj) dropped offline / dropped dead. Check the cabling

As previously mentioned, today's release of CA brings it minimum requirements for the OS to now be 6.12.0. This is mainly because of the necessity to test, add in compatibility code etc for a number of other fixes contained within this release for OS versions 6.9 - 6.11. TBH its not worth my time and effort (realistically this takes days full time to do) to support deprecated versions of the OS. (And its already enough of a PITA to test back to 6.12.x when I run 6.13 on my systems) Big fix here is regarding AC creating orphans when performing multiple upgrades. You should check Docker (Advanced View) and delete any orphans which are present)

Support can resend you your license key if you show them a copy and paste (no screenshots) of what appears within Tools - Registration

Reboot

Only support can look into GUID issues

monitor is a built-in script and runs every minute. You should create a new thread and include your diagnostics

Known issue with the current release of Apps and performing multiple upgrades at a time. Fixed for next release (soon), but you container is updated... An orphan however will get created which you can delete via Docker, Advanced View

Can you also attach the complete diagnostics.zip file (not the commands that were run) here.