JorgeB

Not according to the syslog: May 17 12:26:25 Horus emhttpd: online: Lexar_JD_FireFly_AADEO33DRWIDXKE6-0:0 (sdj) 512 15663104 => no partitions If you do what I mentioned above, it will almost certainly resolve the problem

Could be, or the HBA is dead.

If the problem is just with Ollama you can look for that container's support thread:

I did ask to not type anything else, but you chose the right option. Now type write and enter to write changes and post zpool import output once more

It's safe to delete the Docker folder in both places; we can then try to see what the issue is with appdata

That drive is missing the partition type sfdisk /dev/sdkthen type 2048 and hit enter and post the result (don't type anything else for now)

Pool has two bad drives at the moment; since it is raidz1, it can only recover from one, so you will likely need to recreate it. See if this works: zpool import -o readonly=on -F cache Also post output from fdisk -l /dev/sdk

You are using a Docker folder; mover can sometimes have issues with those. You can delete the folder (Settings - Docker), then move the rest and recreate it after in the new pool. I recommend recreating it as a Docker image, since Docker folders, in my experience, can have multiple issues, but you can recreate it as a folder if you prefer https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file Then: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

Spare, mirror and raidz prefixes are now reserved with 7.3.0 because they are reserved by ZFS, you can rename the pool before upgrading and then upgrade, or reimport the pool in 7.3 with a new name.

No LSI HBA is being detected by Linux, try another PCIe slot or see if it's detected in a different PC.

See igf this helps: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Please post the diagnostics.

Please use the existing plugin support thread. [Plugin] Nvidia-Driver - Plugin Support - Unraid

You need to stop the array to reassign the device. You could do a hot swap using the CLI, but then you need to reimport the pool to make it match the WebGUI assignments.

Try recreating the docker image, and then see if you can access the Docker page before restoring the apps, and try again after restoring them. https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file Then: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

Which brand/model HBA do you have?

I don't see an attempt to import the pool, did you leave the filesystem set to auto as mentioned? Also post the output from zpool import

Not in the same server, you can do it with two and then use the LAN to copy the data.

Please attach one of them to this thread.

The mover is slow if there are many small files because it checks every file is in use before moving it.

If the server cannot shut down cleanly, you will need to force it.

Most likely, try recreating the flash drive, backup, recreate with the tool, restore only the config folder from the backup

Flash drive doesn't have the correct layout, 7.3 is more strict about that. Back up the current one, recreate it using the USB tool, then restore only the config folder from the backup.

Parity disk is inaccessible; power down, check/replace its cables, and post new diags.

Which controller are you using for that SSD? Please note that only some are supported for internal booting in the release notes.