BIOS UUID has been modified, please rescan the host

[AlexLeadingEdge]

Case #07721609

Hi guys,

We had a server coming up with an error about bad blocks so we replaced the SSD in it and cloned the old drive, and while doing so we updated the BIOS at the same time. We now get an error message saying this:

4/06/2025 8:59:53 a.m. :: Task failed. Error: Failed to process REDACTED: BIOS UUID has been modified, please rescan the host

As the machine is a stand-alone server with only one drive, there is no 'host' so I have to assume it means itself. Running a scan on the server doesn't seem to fix the error (I tried several times), but I now see two servers with the same name, one that says the last good backup was X days ago and the other that says a backup has never run. I deleted the server from the Inventory but on doing so both servers disappeared, I then deleted the backup job, but on recreating the backup job I'm now seeing two servers with the same name again, one that fails with "BIOS UUID has been modified" and the other that runs successfully, but it says the backup job failed because the "BIOS UUID has been modified" copy failed. I can't seem to delete the server that is failing, if I delete it then the other one deletes as well.

I'm a little stuck now.

[Mildur]

Hi Alex,

I see that you are actively working with our support engineer on the case, and I'm glad to hear the issue has already been solved together with our customer support team in a remote session.

Next time you get "stuck" in a support case, please consider using the "Talk to a Manager" option first, as we can't troubleshoot technical issues in customers environment over a forum post.

Best,
Fabian

[Justin Sciacca]

What was the fix for this? i'm encountering the same issue.. Any ideas?

[AlexLeadingEdge]

Back story: A BIOS update changed the UUID, so that the stand-alone machine was no longer recognised as the same machine. (as a side note the Windows install de-authenticated itself too!)

Problem: The Inventory re-scan doesn't seem to fix the UUID change.

Solution: As there was only the offending computer in the backup Job we added a random computer to the backup Job as a placeholder and deleted the offending computer from the backup Job, then removed the offending computer in the Inventory (right-click "Remove from Configuration"), we then re-added the offending computer into to the Inventory (Right-click Protection Group > Properties > Computers > Add...), then added the offending computer back into the Job (right-click on the offending machine and Add to backup job). Then in the backup Job delete the random machine placeholder, go to Storage and Map backup, then select the backups for that offending computer. The only real downside is that it then made a Full Backup as an Incremental Backup, which blew out the free space as there were effectively two Full Backups in the same job as the Incremental Backup was almost as large as the Full Backup.