JorgeB

That means there's no filesystem on that sector. This partition is too small for Unraid to format it. If there's no data, you can just reformat it, but I would need to erase it first, Tools - New Config - Keep All - Apply Then back on main, all disks should have a blue icon. Click on disk1 and "ERASE", then start the array and reformat it (a new parity sync will start)

Please post the diagnostics after the upgrade.

You can copy the config to the flash drive, boot from it again, remove the boot pool and re-run the wizard. In the wizard, you select if you want a dedicated boot pool or not; the default is dedicated. https://forums.unraid.net/topic/198440-73xx-version-moving-boot-drive-nvmessd-to-another-drive-nvmessd/#findComment-1619744

That suggests you didn't remove the old pool before creating the new one. Please post the diagnostics to see their names; you can delete the old cfg.

It's fine to leave it always on

Open a terminal window and type unraid-api stop unraid-api restart Then try again to register from the dropdown

Not sure, but it does look to me like an external issue.

Please post a screenshot of the error you see when trying to sign in.

Please post the diagnostics.

FCP plugin doing the fileystem tests?

This is within the expected speed. If you are writing to the array with the default writing mode, try turbo write https://forums.unraid.net/topic/50397-turbo-write/

Open a terminal window and type unraid-api plugins install unraid-api-plugin-connect Then refresh the GUI, this usually resolves that issue.

Same firmware?

The problem now appears to be the network; the Mac is losing its network connection mid-transfer, which may be what was causing the files to corrupt in the first place.

Syslog-previous in the diags covers the event May 25 23:22:07 koaly-tower kernel: ata27: SATA link down (SStatus 0 SControl 3E0) May 25 23:22:07 koaly-tower kernel: ata27.00: disable device Disk dropped offline; this is almost always a power/connection problem.

Try starting the rebuild again for disk1, to see if there's still a write error.

You can

Please post the diagnostics.

Post new diags please.

You can split a pool for boot, but if there's data there, you need to back it up first

I would leave it disabled for a few days

Try booting with a different flash drive using a 7.3.1 stock install, no key needed, to see if it's a config problem.

You should always be able to close the onboarding by clicking the x top right. If you're not, it typically means a flash drive problem; see if you can get syslog using the CLI or over SSH.

Try recreating the docker image: 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

May 28 20:11:29 teak emhttpd: error: malloc_share_locations, 8649: Operation not supported (95): getxattr: /mnt/user/syslogs There's something creating this folder before the array is started, this is not allowed, /mnt/user cannot be used for any custom stuff, or the user shares won't work.