Posts made by Fimlore

@tom-elliott Thanks for your reply. I will give the snponly a try.
I wouldnt know where else to ask about iPXE to be honest, as this forum seems to be the most actively using it Hence why I hoped other users already had the same experience perhaps

I can add a static IP, but this info is also not working, I can’t ping the GW or do a DNS lookup.
the network works, otherwise the initial DHCP response would not service the WDS menu (that loads ipxe.efi)

this is my DHCP:

subnet 192.168.1.0 netmask 255.255.252.0 {
dynamic-bootp-lease-length 14400;
authoritative;
max-lease-time 14400;
default-lease-time 14400;
allow unknown-clients;
next-server 192.168.1.14;
range 192.168.1.30 192.168.3.200;
filename “ipxe.efi”;

Hello,
we have a new type of laptop that is unable to configure the network on iPXE: The Lenovo ThinkPad L14

It get’s to this:

Waiting for link-up on net0: OK
Configuring (Net0 <the mac here>) … No configuration methods succeeded

other devices do not have this issue.
I’ve created a new server and upgraded all of FOG, replaced the ipxe.efi with the included file (1.20.1+), but that did not solve this issue.

@Sebastian-Roth hi, yes: they have the same settings, they are all from the same batch (production wise)

I believe the system partition is the issue. I tried imaging on legacy and uefi, issue doesn’t change.

Tried to wipe the disks first, also no change.

Will try the full copy tomorrow, thanks for your suggestion.

Hi All,

So I have a Windows 10 golden image that is being cloned (SIngle Disk, Multi Part, no resize and resize) and restored to the same type of clients.
this is all fine and dandy, the issue is that the devices can’t boot. I receive a BSOD 0xc00000e while booting.

What I accidentally noticed, was that I CAN boot to Windows when plug in a bootable USB, then boot to Network and cancel that boot.

I am able to fix the device by running bcdedit C:\Windows /h E: /f BIOS

any idea how to fix this during the FOG phase? We need to do 300~ devices, so the workaround is not viable…

(i am using FOG 1.5.4)

@Quazz
I thinks that I fixed the issue somewhere along the way and kept on having a different issue on my debug VM, then when I went to check out that issue, I recognized the fact that I already solved it somewhere… The Physical devices also deploy without issue now;

I’ll still need to confirm that the exact issue is solved, so i’ll be creating a few images and see if they restore out of the box.

Thanks again for the quick support, I’ll mark this thread as solved

edit;
(…if I knew how… )

@Quazz
I’m confused.
Ok, so I tried to perform the command myself, it complains that the disk isn’t big enough;
so, I expanded the disk of the VM, and suddenly the image ís able to deploy, in both Debug and non-debug VM’s…

will have to check on the actual devices, since they gave the same issues as the VM

@Fimlore said in Migrated /images folder:

I’ll try the debug option to see what I can find.

the files are clearly there… what does Exit RC 4 mean?

@Quazz

(image is disabled because the team had to finish an order today, so am deploying using the ‘cheat’ I described earlier)

I’ll try the debug option to see what I can find.

@Quazz said in Migrated /images folder:

@Fimlore Yes, the FOS environment mounts your image location to /images on the client.

Does the FOSenv have some sort of shell so that I can troubleshoot while the folder is mounted?

@Quazz
The ‘old’ images (which were on the older server) do work. So if I rename the folder of the image that doesn’t work, to one of the folders that do work, the image deploys.

it appears to me that newly created images do not receive the correct file path; I’ve checked the database / Images table and it doesn’t store that path with the images, as far as I can see. So I tried reconfiguring the StorageNode (defaultMember) by just removing the /FOGImages and adding it again, but to no avail.

@Quazz
I am facing another issue,
exported and imported images work without issue, new images give me the error as can be seen in the picture:

If I rename the folder to be like one of the working images, than it works like a charm. It’s just that somehow the Image GUI doesnt seem to store the correct location?

p.s. the Args passed is something that I also see on the working images… it’s a bit confusing but I guess it’s a mount or something?

Thank you, this was indeed the issue.
I did have to reinstall FOG, I don’t quite know what you meant by

“If you let FOG build exports automatically, then just rerun the installer after that change.
If not, you have to edit /etc/exports”

I had no /etc/exports, so tried reinstaller anyway, problem solved. Thank you!

It is a fresh install, on that part.
I did mess with settings on the Imaging section (changed the DefaultMember to /images/FOGimages) I did not change the FOG settings

The disk is shared with different methods of imageing (WDS, FOG etc) so it’s mainly for clarity.
this setup worked in the old machine, in fact, the disk was detached from the old machine and attached.
FOG was already installed at that point however, i’ve overwritten the /images folder with the mounted disk

Hi Fog,

I’ve migrated an old server to a new one, and attached the drive to the /images mount.

I then chown-ed all files and folders to fog:root
i chmod-ded everything to 777.

The settings of “DefaultMember” are:

image path: /images/FOGImages
FTPPath: /images/FOGImages

the rest is default.

What else do I need to do in order to fix the catpure stage?, I now receive the following error:

Failed to create image capture path (PrepareUploadLocation)
Args Passed: /images/<mac>

I believe this is wrong, it should be /images/FOGImages/dev/<mac> ?
where is this set and does it require aditional rights?

Hello!

I am using FOG 1.5.4 and I’ve noticed when captureing an image, that it doesnt checkin, because /fogservice/pre_stage1.php isn’t found;'which is logical: it’s fog/service/pre_stage1.php…

I’ve worked around this by creating a symlink in /var/www tot /fog/service, but is this an issue in my installation?

@Tom-Elliott oh, so basically I create two storage nodes that point towards the same device, I didn’t think about that… Will give it a try tomorrow, thanks!

Also, with notepad++, you can change the formatting from Windows to Linux, to prevent these kind of issues

@Fimlore

P.s. The original question was:
How can I setup Fog to listen on both (or more) NICs in the server? Multicast is (for now) only needed on ETH0, the other ETH connections will mainly be unicast. If it is supported, that’s great; if not than no big deal, as long as one nic can do it.

I tried to delete the post because I was planning to put it in general, but failed at that