@zingaro why? We take a backup then put ours in place. We can’t use bcdedit in Linux as those are Windows tools.

@zingaro Please post the PCI IDs as a reference as well.

Did you try my suggestion on using a dump mini switch?

Other than that you could try different iPXE binaries like undionly.kkpxe (note the double k), ipxe.pxe, realtek.kpxe or realtek.kkpxe

The other question is, why not going UEFI all the way?

@zingaro Can we mark this solved? I guess sudburr’s hint is spot on.

@zingaro Please let us know if you could follow the description in the other post and got it setup on your system as well or if you need any more help with this.

To create a menu in the advanced one, you must fill it in under iPXE General Configuration -> Advanced Menu Settings > Advanced Menu Commands

example:

:urls set msdart-url http://192.168.1.155/2-MSDART :MENU menu colour --rgb 0xff0000 0 || cpair --foreground 1 1 || cpair --foreground 0 3 || cpair --foreground 4 4 || item --gap -- ------------------------------------- item fog.local Boot from hard disk item msdart6x86 Microsoft DaRT for Windows Vista 32bit item msdart6x64 Microsoft DaRT for Windows Vista 64bit item msdart7x86 Microsoft DaRT for Windows 7 32bit item msdart7x64 Microsoft DaRT for Windows 7 64bit item msdart81x86 Microsoft DaRT for Windows 8.1 32bit item msdart81x64 Microsoft DaRT for Windows 8.1 64bit item fog.return Return to previous menu choose --default fog.local --timeout 5000000 target && goto ${target} :fog.local sanboot --no-describe --drive 0x80 || goto MENU :msdart6x86 initrd ${msdart-url}/MSDaRT60x86.iso chain memdisk iso raw :msdart6x64 initrd ${msdart-url}/MSDaRT60x64.iso chain memdisk iso raw :msdart7x86 initrd ${msdart-url}/MSDaRT70x86.iso chain memdisk iso raw :msdart7x64 initrd ${msdart-url}/MSDaRT70x64.iso chain memdisk iso raw :msdart81x86 initrd ${msdart-url}/MSDaRT8.1x86.iso chain memdisk iso raw :msdart81x64 initrd ${msdart-url}/MSDaRT8.1x64.iso chain memdisk iso raw :fog.return chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || prompt goto MENU

@zingaro said:

There are the difference with VM Machine ?

Well, VM is not hardware and vice versa and also hardware is not equal to all other hardware. We do see many issues related to slight differences in the UEFI firmware and such things. Causing a lot of trouble sometimes. There is no easy answer to your question. You’d need to get into debugging the problem on your VMware to see why it doesn’t work.

@george1421 This fixed my problem, thank you!

I don’t believe there are currently steps designed for it. When Partclone has a new release, FOG tends to include it in a future update.

Do note that FOG does not use the master branch of partclone as that’s considered unstable/experimental.

If you still want to try, you’ll have to replace it in the init files. But these get overwritten with new FOG updates

@Sebastian-Roth I still think you’re correct.

The CD SHOULD be asking you to “press any key to boot from CD”. Is there some reason this is a big concern? Sure it adds another step, but I think the reasoning is something in 1.2 iPXE code wasn’t sending the HDD, where in newer versions it’s releasing the system allowing the ISO to actually see the HDD prompting it to run a scan.

I don’t understand what problem it working as if this was a CD being booting this brings to the table.

The “image ignore” and “client ignore” flags are meant to IGNORE the mac address in use for the respective item. For example:

Image Ignore makes it so the MAC Address being loaded is NOT going to be able to be used for Imaging. But this is only regards to the system it’s registered with. (Seeing as identity is verified/validated by the MAC Address this should be expected).

So, an unregistered machine, using a NIC that is registered to another machine, will appear to be that “registered” machine. Why would Image Ignore be a useful option? I don’t know, but I know the client ignore option IS useful (for example a shared USB nic on multiple machines so you can have the client work without thinking the system is another host.)

Can you give us more details? Does this happen on every machine you capture from? Can you give a screenshot of the error?

@robe2conoby Just to be clear IT Admins should never directly touch/use the linux user called fog. This is not the web ui admin account called fog (unfortunate coincidence). The linux user FOG is 100% managed by the fog installer. If someone changes this account afterwards or uses the linux fog account for system management bad things will happen.

The next time the fog installer runs it will think that it has control of this account and will reset things back to what it needs, probably clobbering your configuration. Please don’t touch or change this account.

@zingaro No, we’ve been putting together documentation where we feel it’s needed, and we consider including any submitted documentation. Is there something in particular you want to know about? Links to the wiki are in my signature.

Rename .fogsettings to .fogsettingsold, in /opt/fog

@zingaro Here are some resources:

https://wiki.fogproject.org/wiki/index.php?title=NAS_Storage_Node
https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node/1

There are others you can find too if you just search for the key words.

Perfect !
I substitute the conf files and replaced “Fog IP Server”,now it works !

Solved !
Regards

@george1421 ,
Hi,
with Intel I5/I7 processor the system start correct,
j1900 e3826 reboot (it’s not a fog problem but ACHI driver installed ).

@zingaro That’s not NFS, in the command it says cifs. without heavy init modification, fog will not work with cifs. Also, you shouldn’t setup an NFS share this way, either. The share does not get mounted to the server at all, because if it were, imaging would not work. The Linux kernel will not allow you to re-export an already exported directory. You don’t even need to touch the CLI of the main server to do this. Just the NAS and the web interface of FOG.

On the NAS, create an NFS share with full read/write permissions for everyone. Create an FTP user called fog and grant it full rights to the share. In the share, make a file called .mntcheck and a folder called dev and inside of dev make another file called .mntcheck Then plug in the IP address and share name and the fog user along with it’s password, and ftp path into FOG’s web interface.

@Tom-Elliott all OK.
i have moved all image in another folder.
now work fine !

/var/www/fog/images is redirect to /var/www/fog/images
Case Closed!

I believe the entire ISO is stored into RAM. So, you gotta have room for that plus space for running the OS and applications.