FYI that I had this problem with a bunch Lenovo P51s. Bios did not have a setting for AHCI/SATA but in Boot priority I saw nvme beside the drive which none of my dells or even the P52s have (they show as HDD)
From one of the other posts I tried set the “Host Primary Disk” for that client in the fog web gui to “/dev/nvme0n1”. I was able to deploy images to these P51s.

@agray said in Imaging an SSD:

When we get our next batch of new PCs in, I’ll see if that fixes it and respond here. Thank you!

Do those have 500 GB drives?

You should be able to use the original refind.efi from 1.6.0 as this is one of the older versions. Whether it works I don’t know, but I do know of at least one person who uses this old version (0.9.4 I believe?) with their HP machines. They also needed to use the 10 second delay files due to NICs being power save ready.

@nextechinc I can’t answer that. If you can tweak 5.4 with the newer driver then go for it. 5.5rc may also work. I guess the question would be how many NUCs do you have and what would take the least amount of effort to do (probably 5.5). Understand that you can define a custom kernel for each host definition. SO what ever direction you go in keep the kernel name unique and only assign that kernel to the systems that need it.

It appears (guess) that FOS or iPXE is seeing two different network adapters as nic0. It is possible to boot FOS Linux from a usb stick. The issue is that the deploy image function you use is a product of iPXE and not avaialble via the FOS Linux usb boot method. With that said there is a hack of the FOS Linux usb boot hack that can simulate the “iPXE Deploy Image” menu.

I posted instructions on how to do this with graphical representation late last year but I can’t seem to find it at the moment. In this post it kind of explains how to do it with the FOS Linux grub menu. https://forums.fogproject.org/topic/12842/fos-boot-usb-quick-image-issue/12

Edit: Ah I found it, look at the last post in this thread: https://forums.fogproject.org/topic/13977/suggestion-please/66?lang=en-US&page=1

If I remember correctly the X90s was the first model to support uefi booting (not via the network) The x010s were the first models to support network booting in uefi mode.

So a couple of things first for the x010s, while they will pxe boot in uefi mode, iPXE will hang initializing the devices and sit there forever.

So this workaround will with for both the 790 and 7010s.

You can image the machines in bios mode, but switch them back to uefi mode before the first boot into OOBE. The easiest way to do this is to have fog power off the device after imaging. So you will have a tech standing in front to power it on to go into the F2 bios screen and switch the mode to uefi before oobe runs.

The second option is to boot FOS Linux from a usb stick with the hardware in uefi mode. FOS Linux (the OS that is downloaded via iPXE) boots correctly in bios and uefi mode. Since iPXE and pxe booting is not used there is no conflict.

The third option is don’t use 12 year old+ hardware (which isn’t probably an option)

Hi folks!
Thanks for taking time to look into this.
And yes, you’re right about the FOG client. It’s inside the image and the service is activated from the beginnen. While researching I came across the mentioned link after I experienced those problems.
It was just such a weird behavior I was unsure and did not try out the delayed strting of the service.
I’m going to modify my image in the next weeks. If the issue continues I’m going to open a new thread.
Thanks a lot!
Great help from a great community!

Chris
P.S. How to mark this issue as “solved”?

@tunatoksoz Hmmmm, thanks for joining the discussion here! Seems like you are making progress on this more than we have. 🙂

May I ask you if this is on Lenovo 300e as well? As you are saying yours has a build in NIC plus one on PCI I kind of doubt you have the same machine. Can you be more specific on what make and model you see the issue on?

@doubleve Do you have fast boot disabled in Windows before you started the capture task? Sure the machine is not hibernated or anything?

Did you see any error message in the blue partclone window that has been on screen hust before the screen we see in the picture?

@george1421 @Sebastian-Roth I reverted everything back and switched the Sata mode to AHCI and everything is working great again and both the NIC and storage passed the compatability test!

Big thanks to both of you!

Hopefully the big companies will start releasing open-source drivers so Linux can thrive

Thank you for the response, I appreciate it. I’ll give that a try.

I thought of a bit of an easier way to explain the field mapping between the kernel parameters ( cat /proc/cmdline ) and the grub menu. Here is a graphic that explains how to map the values between the two different booting methods.

Grub_field_mapping.png

Hi Sebastian - interestingly when I switch to the 32bit kernel everything woks fine so as far as were concerned the problem is solved

@Sebastian-Roth Sadly I am out of surface go’s to test at this time. Gotta get the ones we have in production.

I think I figured it out. I found another article where a user recommended removing the bg.png file from the menu backdrop in the PXE menu. I did this and it did manage to boot to the menu, and allow me then to enroll and image.

https://forums.fogproject.org/topic/8264/stuck-at-bg-png-issues-with-lenovo-x1-carbon-6th-gen-lenovo-onelink-dock-rtl8135-usb/6

Thank You,
Kevin Hauser

@Acuity From what I know about this and read between the lines I think this is caused by the Dell Optiplex AIO 5270’s UEFI firmware not being able to find EFI boot loaders by itself. We had other people report this kind of thing and I thought about adding a feature to FOG that would also save a copy of the EFI boot entry with the image and also deploy it to new machines (forum topic). While it seems to be a vital thing to do on first sight I stepped back from the idea because we don’t have many reports on this being an issue at all (1, 2). While on the other hand we have reports on UEFI firmware creating multiple boot entries (new one on every deploy I guess) or somehow messing with the entries by themselves (1, 2) Because of that I decided to better not mess with the EFI boot loader entries as it could cause trouble on systems we don’t know well enough (like dual boot and such).

Nevertheless you can try to use efibootmgr tool in post deploy scripts to set the boot entry for you. Search the forums for those two things and if you need assistance just let us know.

@rocksteve69 Unfortunately I’m unsure what else to try at the moment.

@george1421 had a look at our Dell 5300 device and it doesn’t have the Thunderbolt port. Although we have resolved the issue another way, I may consider looking at getting the rest of the devices optioned with Thunderbolt ports.

Thanks!

Derek

@george1421 I found that my previous image which I used on Elitebook g5s is having diffrent ethernet driver, its issue with image. I test it on diffrent computer its installed correct. Please disregard my question.

@Foglalt said in ASRock B360M Pro4 imaging issue:

As for the fog versions. I would upgrade it when i will have time for it.

At this time I’m only suggesting that you update the FOS Linux kernels in /var/www/html/fog/service/ipxe directory. There are two files there bzImage and bzImage32 (watch the case). Replace them with 4.12.3 versions from here: https://fogproject.org/kernels/

Download them, rename them to bzImage and bzImage32 respectively and then move them to the fog server in the path above. Be sure to rename the original files just in case you need them later. Once you are on at least 4.12 then the new(ish) hardware with the I219 network adapters (very common nowadays) will be supported.