JorgeB

May 16 17:37:17 Bunker kernel: FAT-fs (sde1): error, fat_get_cluster: invalid cluster chain (i_pos 0) Flash drive problem: you try running ScanDisk on it, or just recreating it, if issues persist, replace it.

Try checkinmg filesystem on that disk, using the checkmark icon on UD.

That disk needs to get replaced as well. Since you have dual parity, you can replace both at the same time, or if you don't have a spare, rebuild disk2 first, then replace disk1.

There's a problem with the pool cfg file, try this first: on main click on the first device for that pool and then "remove pool" back on main, create a new pool with the same name and number of slots assign the pool devices, leave the filesystem set to auto start the array to import the pool and post new diags.

Please create a new thread in the general support forum and post the diagnostics after updating.

Thanks for the post, 7.3 is more strict about the flash drive layout. You can also just back up the current flash drive, recreate it using the USB tool, restore only the config folder from the backup and you are all set.

There are issues with two devices, not just one; please post the diagnostics.

Please use the existing plugin suppor thread.

That will be a plugin.

This suggests a hardware issue; recommend addressing this first. Read errors on disk1 are logged as a disk problem; run an extended SMART test.

You should have backups of anything important either way, if you have good backups and they are easy to restore, RAIDZ1 is less of a risk, but even with RAIDZ2, backups are still needed.

This is the boot pool, these two disks, if those are the one you wanted to use, it's correct. It is. Post the diagnosis to confirm a TPM device is not being detected, or if it is but there'sa problem..

Try the open files plugin.

You can, or you will need to resync parity. Either way, the new disk will need to be formatted in the end.

It would mostly depend on how good the backups are. The extra I/O should not be a big deal for healthy drives.

Probably some change in the kernel. What is the time zone set to in Settings - Date and Time?

Click on reset stats, then scrub the pool and if there are any errors found, post the scrub result.

You can ignore that.

If this is a dedicated boot pool, the easiest way is to boot from the flash again and recreate the boot pool using another device: https://forums.unraid.net/topic/198440-73xx-version-moving-boot-drive-nvmessd-to-another-drive-nvmessd/#findComment-1619744

Try recreating the flash drive, first backup the current one, then recreate it using the USB tool, confirm the flash drive boots with the stock install, and if yes, restore only the /config folder from the backup overwriting any existing files. If that doesn't work or you need more help, please start a new thread in the general support forum.

Try just closing it, if you can't reboot and close it when it first shows

There are issues with multiple devices, and I see you are using a controller with SATA port multiples. Those are not recommended and can cause a lot of issues. It could also be the reason for the unresponsive issues with newer versions due to kernel updates. I recommend replacing it with one from here:Recommended controllers for Unraid - Storage Devices and Controllers - Unraid

Reimporting the pool will keep all the data. Any shares that were using that pool you can edit and reapply with the new pool name, if you have multiple shares configured the same way, you can copy the setting from one to many, in the Share settings page.

If you have space on the array, you can also use the mover to empty an array disk, format it with the new filesystem, then move on to the next one

May 15 09:49:53 nas emhttpd: Error: (/dev/sda) not known There's a problem with the flash drive partition or layout; 7.3 is more strict about that. Back up the flash drive, recreate it using the USB tool, then restore only the config folder from the backup