Lenovo Thinkpad E14 Gen 2 Issues
-
@sebastian-roth Hi Sebastian, as I mentioned previously, if I manually switch to boot from the hard drive, it simply skips over the device entirely as if it is not even there. If I disable all boot devices aside from the hard drive, it hangs at the BIOS boot menu forever with the only option to select being the hard drive. If I select it, it just brings up the exact same boot menu again.
-
@kayotte Sounds like the deployment didn’t work at all. Can you please schedule another deploy task on this machine but check the switch for debug mode in the FOG web UI just before you click the “Create Task” button. Boot the machine up and when you get to the command shell (after hitting ENTER twice) I want you to run
lsblkto see what the disk drive is named (e.g. /dev/sda or /dev/nvme0n1). Then runsfdisk -d /dev/sdausing the device name you found using lsblk. Take a picture of the screen and port that here. -
-
@kayotte What version of FOG are you using? Also what version of the FOS Linux kernel (FOG Configuration->Kernel Update will tell you) do you have installed?
It appears from the picture FOS can see the nvme drive.
Also since this is the first uefi system you are deploying to, is your image that you are wanting to deploy uefi based? FWIW you can’t deploy an image captred from a bios computer and deploy it to a uefi computer and have it work. The disk structure is too different between the platforms.
-
@kayotte In your post you mostly talk about UEFI but the partition layout is DOS style (legacy BIOS). Something’s wrong here!?
-
@sebastian-roth @george1421 I’m honestly not sure if I did anything different at all but I made another new image from one of the laptops and the deployment now seems to have worked for the most part. I will note that I did update fog as well as the fog client. I am now running the most up to date fog version 1.5.9.111 and kernel 5.10.71.
However, I am experiencing a different issue now. After the initial deployment has completed, the computer boots to the administrator desktop and restarts, then after restarting it signs in to administrator once more and then hangs there at the desktop forever without joining the domain. Also not sure if it has anything to do with it, but when capturing it displayed a bunch of “ucsi_acpi USBC000:00: possible ucsi driver bug 2” messages. I have attached a picture of what those errors looked like. The capture/deployment does seem to have worked regardless of this though.
-
@kayotte The error is an annoyance message at the moment. Its saying that there is an issue communicating with a usb-c based device. A firmware update on the computer may fix it or a FOS linux kernel update on fog might solve it.
What version of the FOS Linux kernel are you using?
FOG Configuraiton-> Kernel update -
@george1421 It doesn’t directly tell me which one I have installed but the most recent one I clicked to download and install was 5.10.71 TomElliott 64.
-
@kayotte said in Lenovo Thinkpad E14 Gen 2 Issues:
I clicked to download and install was 5.10.71
When you have a chance see if that one throws the same error on the same model of computers. You will want the latest kernel to support the latest hardware anyway. So its not a bad idea to upgrade.
-
@kayotte said in Lenovo Thinkpad E14 Gen 2 Issues:
However, I am experiencing a different issue now. After the initial deployment has completed, the computer boots to the administrator desktop and restarts, then after restarting it signs in to administrator once more and then hangs there at the desktop forever without joining the domain.
Don’t think this is something FOG can cause.
-
@sebastian-roth Hmm in that case do you have any idea what might be causing it? I noticed that now deploying old images on old laptops is also having this same problem not joining the domain. Is it possible that the fog update I ran could’ve changed something?
-
@kayotte said in Lenovo Thinkpad E14 Gen 2 Issues:
I noticed that now deploying old images on old laptops is also having this same problem not joining the domain. Is it possible that the fog update I ran could’ve changed something?
It’s probably best you open a new topic for this as it doesn’t seem to be related to the issue you had before. Please grab the fog-client log file (
C:\fog.log) and post that (upload to a file share). I am pretty sure we’ll find why it doesn’t join in there. As well you might also add more information on details like sysprep or what else you do to prepare your image.
