Topics created by Gerrit Anderson

@Gerrit-Anderson Thanks for this – fixed this issue for me! I used to get stuck on Init, but can get further now into the actual boot menu like you. I too have lost my custom background but really that’s a non-issue.

However, when I try to deploy an image, it asks me for a password (which is the FOG webUI username & password of course). I don’t recall this happening with my old TFTP boot files – I guess they must have had the password embedded in there somehow? Anyone know how I can fix this?

@gerrit-anderson said in Centos 7 UUID not updated during imaging - will not boot:

From what I can tell, FOG is handling the UUID’s correctly…

Would say so too from what we discovered so far. It’s interesting you can capture/deploy from/to VM<->VM and machine<->machine but not “across”.

For further debugging I suggest to dig into the dracut emergency shell/mode more. First run ls -al /dev/disk/by-uuid/ on the dracut command prompt and post a picture of that here. As well you might also follow the instrcutions printed, run journalctl and look through the log for hints on why it fails booting. Also take a look at the file /run/initramfs/rdsosreport.txt mentioned. Feel free to share the file here and I’ll take a look as well.

Edit:
Searching the web I found this: https://unix.stackexchange.com/questions/183859/initramfs-uuid-problems-after-cloning

Sounds like the initramfs might be generated differently on your VM and bare metal install. Both are missing a driver for the other one. If that turns out to be true you need to find out which one is missing and manually regenerate initramfs with dracut e.g. on your VM before capturing the image to be deployed to hardware.