JorgeB

1TB is the only cache device now correct? If yes you can do this: If Docker/VM services are using the cache pool disable them, unassign the cache device, start array to make Unraid "forget" current cache config, stop array, reassign the cache device (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), re-enable Docker/VMs if needed, start array.

That should be unrelated, more info and workarounds here, as for the shfs issue you could try this posted just above:

Everything looks fine to me with the HBA, it's being initialized correctly, not on the latest firmware but shouldn0t be an issue, I assume you're using the same cables as before? Still worth checking all connections.

Not really, bit by the description it looks like a hardware issue.

Please post the diagnostics: Tools -> Diagnostics

Put the flash drive in your desktop/laptop and see if there are any files there or if it's mostly empty, I hope it's not the case here but there have been an abnormal number of hacked users with wiped flash drives and servers in the last few days, it this keeps happening we need to find out what they have in common.

Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

No, drives are only disable when there's a write error, that happened before this reboot, so not covered in the diags, but when a disk gets disable it can sometimes cause some filesystem corruption in the emulated disk, the filesystem in the actual disk should be better, and since the disk looks healthy it should be recoverable. You can run xfs_repair now on the emulated disk, and check the results, whatever is there is what will be in a rebuilt disk, if results are not good and the old disk is mounting correctly with UD and data looks better, you can either rebuild using a new disk and then compare the data with the old disk, or do a new config with it and re-sync parity. If you have more doubts ask, I don't spend much time in the forum during weekends but somebody else should be able to help you, and I'll still check back later if needed.

It wasn't always like that, but it has been since about 3 or 4 years ago.

Auto parity check after an unclean shutdown is always non correct.

That was a non correcting check, run a correcting check, it should find but this time correct all the same errors, then you can run a non correcting one to confirm all is well.

Yes, that was what I was asking, if you can't get to the wegGUI after a reboot, if you can't grab new diags over SSH.

You don't have GUI access after rebooting?

OK, now wait for the next scheduled check and see how that one goes, and make sure no unclean shutdowns in between, as a few errors after one are normal.

Couple of more questions: When you say the USB failed do you mean it failed physically as it was unreadable or it was readable but it was missing files or empty? Did you have any way of accessing the server remotely and/or were forwarding any ports to the server? Or using DMZ?

Assuming this is fixed reboot and post new diags with the array started.

Always good to read the release notes. Usually yes.

It would go away by reformatting cache, but if it's recurring it suggests an underlying problem, unlikely to be the SSD, are there any regular server crashes? I did see a macvlan call trace on the log.

Neither, format is never an option to recover data and parity can't help with filesystem corruption. Run xfs_repair without -n to see if all the data comes back and there aren't a lot of lost+found files in the emulated disk, if it's not a good result you can mount the actual disk outside the array and check that.

If you mean data disks mounted but they are empty it wasn't just a flash drive problem, but you can start the array and grab diags, it won't cause any more damage.

You can report any issues in the existing plugin support thread.

Check if the missing drive is detected in the BIOS, if not it will never be detected by Unraid.

Syslog is spammed with the previous errors, please reboot and post new ones.

One other thing that could have caused the issue is if you connected the UPS at that point, if for some reason reset the USB controller and if the flash drive was using the same one it could have been the reason for the drop.