Boot problems on Lenovo M720s with M.2 drive & UEFI
-
I’m having trouble getting a working image and have run out of options. We have a ton of Lenovo M720s’ to deploy.
The master seems to capture, but when I deploy, the PC won’t boot unless it boots PXE, goes to the menu, then uses the exit file.
The M.2 drive doesn’t even show up when you try to select a boot device manually.
My image is set for:
Windows 10
Single Disk - Resizable
Everything.
My bootfile is ipxe.efi, simply set as Option 67 on a Win DHCP Server.
the exit file is rEFInd_EFI
Like I said, it boots, it captures fine, and it deploys fine, but it won’t boot on it’s own. It only boots if you PXE boot into the menu, then select boot from the Hard disk.
The Bios in both the Master and the deployed PC is the latest, and the settings are Factory Defaults, except Secure Boot is turned off. The boot order has the M.2 first. It’s also set for EUFI Only. It won’t boot Legacy.
On normal bootup, it goes straight to PXE, and if you F12 it and try to select a boot device, the M.2 isn’t even listed.
what am I missing here? -
It turns out that this was a problem with the Trusted Platform Module. Apparently it didn’t like the new O/S being installed on hardware it had already “signed”. Not being too schooled in how TPM works, I’m making an assumption here, but clearing the TPM after deployment fixed my bootup problem. This can be done in the BIOS, or by letting the system boot from the Hard Drive at the Fog Menu, then running tpm.msc and clearing it there.
-
Did you sysprep the image before capture?
How did you build your reference image? Did you build it on the same model computer, capture and then deploy to a different computer of the same model, or did you create a generic reference image on a VM and then deployed it to the target hardware.
For uefi computers, if the boot device has a fat32 partition with the boot file in the proper location the uefi firmware will let you set it as a bootable device. If the boot file isn’t found that drive won’t be selectable to boot.
So this tells me that refind can find the proper uefi boot loader, but the firmware can’t??
Does the lenovo have something similar to the Dell F12 boot manager? If so can you select the m.2 drive from that menu and have it boot?
-
This post is deleted! -
No, I didn’t use SysPrep, but have never had to in the past.
These are the same model workstations. We built a Master workstation, captured it, and we’re attempting to deploy to an exact same model workstation.
Yes the Lenovo’s have a startup boot selection menu you can access with F12. The M.2 drive isn’t even listed.
I’ve looked at the disk partitions on both Master and Deployed and they look exactly the same. there is a 100mb partition called EFI System Partition:
Thanks for the fast reply!
-
@mattlong01 said in Boot problems on Lenovo M720s with M.2 drive & UEFI:
The M.2 drive isn’t even listed
So this tells me that the firmware can’t find the uefi boot loader typically in /EFI/Boot directory on the uefi boot partition.
I didn’t ask you this last time, what version of FOG are you using? If its not 1.5.7 then what kernel version are you using (as seen under the fog configuration menu)?
-
Yes, fog version is 1.5.7
-
@mattlong01 Please read through this topic and try the suggestion on manually creating the Windows EFI bootloader entry to see if that might help: https://forums.fogproject.org/topic/14142/fog-doesn-t-copy-nvram-from-cloned-machine-to-the-new-machine
-
It turns out that this was a problem with the Trusted Platform Module. Apparently it didn’t like the new O/S being installed on hardware it had already “signed”. Not being too schooled in how TPM works, I’m making an assumption here, but clearing the TPM after deployment fixed my bootup problem. This can be done in the BIOS, or by letting the system boot from the Hard Drive at the Fog Menu, then running tpm.msc and clearing it there.
