h0dgep0dge

It seems like the Unraid OS is relying solely on the label of the boot flashdrive to identify it, and this causes some strange behaviour, such as complaining that the UUID of the boot drive does not match the licence key loaded in memory. I believe the system is mistakenly detecting any old flashdrive with the label 'UNRAID' as the boot drive, maybe related to some race condition or just the order that the devices are enumerated. So far I've noticed the array cannot be started with the additional flashdrive plugged in, and the additional flashdrive will cause the actual boot disk to be listed on the Update VM page to be attached to the VM, which could have very serious implications for data integrity. One assumes the VM system typically hides the boot device from this list, but is doing so on the basis of the label, so when it has a false positive it will hide an empty flashdrive and allow you to attach your actual boot disk. Removing the extra flashdrive immedietly solves both of these issues To reproduce - Format a flashdrive with a FAT filesystem and the label 'UNRAID' - Plug the flashdrive into an Unraid machine malphas-diagnostics-20230322-0113.zip