trurl

Welcome! We are friendly and helpful. Don't hesitate to ask.

Attach Diagnostics ZIP to your NEXT post in this thread.

Your cache drive is corrupt so has been made read-only. Probably a hardware problem because Some segfaults in syslog Nov 3 13:40:10 Tower kernel: .NET ThreadPool[1571238]: segfault at 6 ip 000014d41752d0a0 sp 000014d2c8c815a8 error 6 likely on CPU 2 (core 1, socket 0) Nov 4 02:10:51 Tower kernel: .NET Tiered Com[2852605]: segfault at 4 ip 000014fd35e38307 sp 000014fbbb102130 error 4 in libcoreclr.so[237307,14fd35da9000+4b6000] likely on CPU 6 (core 3, socket 0) Nov 4 11:30:59 Tower kernel: AnyIO worker th[2145550]: segfault at 1 ip 000014b82b543045 sp 000014b82298def0 error 4 in libpython3.14.so.1.0[143045,14b82b43b000+27a000] likely on CPU 0 (core 0, socket 0) I still suspect RAM.

The "caching" pool can be allowed to overflow to the array. The shares on the other pool can be exclusive to that pool for better performance.

Why not just install from CA? That guide has you create a share immich-gen that it says should be kept on cache, but then it says to set it to be moved to the array.

Create the support thread, or just edit this thread, and we'll move it to Plugin Support.

The diagnostics you posted earlier says appdata is a "cache-prefer" share. This means it is allowed to overflow to the array. To make it cache-only remove the secondary storage. This will also make it an Exclusive share, and fuse won't be used, /mnt/user/appdata would just be a symlink to /mnt/cache/appdata.

Unassigned Devices is one of the most commonly used Unraid plugins. When you have your new Unraid server working, use the Unassigned Devices plugin to access the data on the old drives.

How did your data partition get named "boot"? Probably a reserved word. Seems to have caused other problems. The boot partition is mounted at /boot, but that data partition is mounted at /mnt/boot1.

What did you really mean? That version doesn't exist. Attach Diagnostics ZIP to your NEXT post in this thread.

You should not copy emulated disk2 data to other array disks. That would go against Backup means to another system, or at least to an Unassigned Device.

Changing the boot device | Unraid DocsThe boot device is critical to your Unraid server as it stores the operating system, configuration files, and license. (For typical USB installs this is a USB flash drive; with internal boot it is ano

Should be there.

https://docs.unraid.net/unraid-os/system-administration/maintain-and-update/changing-the-flash-device

That seems to say default boot is no GUI

What do you get from command line with this? cat /boot/syslinux.cfg-

Attach Diagnostics ZIP to your NEXT post in this thread.

Are you booting from flash drive?

At the screen where it is saying you need to reboot, does it not also give an option to cancel the upgrade?

Unraid doesn't run from the flash drive. The flash drive contains archives of the OS, these are loaded fresh into RAM on boot, and the OS runs completely in RAM. Any changes you make in the webUI are written to flash so they can be reapplied at boot. First make a backup of each as explained. Instead of replacing them, you might just follow those instructions using the same flash drives. If that works, you won't have to do a license transfer. Changing the boot device | Unraid DocsThe boot device is critical to your Unraid server as it stores the operating system, configuration files, and license. (For typical USB installs this is a USB flash drive; with internal boot it is ano

I have 2x2 NVMe pools, all working fine for me after upgrade to 7.3.3

This is exactly the scenario parity swap procedure is for. https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#parity-swap Probably a good idea to let us take a look though. Attach Diagnostics ZIP to your NEXT post in this thread.

You already said 2x1TB. Should be plenty.

The simplest thing would be to make the Unassigned nvme a pool so Unraid could manage it. Should only require updating path mappings to get Emby using it just as before. Or just leave it as is since the other shares are already on cache. But are you sure none of them have files on the array? Do you know how to check? How large is your cache pool?

And if you need further support for your problem, or any problem reported by FCP, start a new thread in General Support. This thread is just for support of the Fix Common Problems plugin itself, not for problems FCP finds. As explained in the first post of this thread: