@Quazz Yes, very true that is.
@zago123 You may even try undionly.kkpxe
(note the double ‘k’). This definitely helps in some cases - I just keep forgetting about this as it is less and less the case.
@Quazz Yes, very true that is.
@zago123 You may even try undionly.kkpxe
(note the double ‘k’). This definitely helps in some cases - I just keep forgetting about this as it is less and less the case.
@Arkhad Welcome to the forums. It’s always good to mention the FOG version you are currently running in every new thread you open. Though I think your issue could happen in all the versions it’s still good to make sure you don’t use an old one…
The message “No DHCP response on interface…” is a bit misleading and I ought to change that at some point. Look a bit further up where it says “Either DHCP failed or we were unable to access 10.0.0.2/fog//index.php for connection testing”. I’d say you are missing the http://
schema there. Let me guess, you installed FOG 1.4.4 and then put in the latest kernel/initrd by hand? At some point after 1.4.4 we changed that part in the scripts and PHP interface. This is why I guess you use 1.4.4 web interface but newer kernel/init.
Can you outline the exact steps you went to install FOG?
@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.
@loosus456 Without directly knowing your setup I might be a little off the track with my guesses but here it goes, see what it’s worth for:
You need some kind of EFI boot manager (entry) to boot Windows. This is what Boot Camp usually does for you and it can be done using rEFInd for example as well. This boot entry is partly stored in NVRAM (not on disk) an therefore will persist even if you delete the macOS partition. But that doesn’t mean that you don’t need that. I think there is a chance you can do what you want because FOG comes with rEFInd on board that can start Windows straight from PXE booting. PXE to the FOG menu and default exit style rEFInd should do the trick. That gets me to your second question.
You can use USB keys to boot up into the FOG menu - this is not essentially PXE booted but it’s still partly network booting after the initial boot from USB. But you can also fully PXE most Macs! Take a look at our wiki article on this. One simple method I like is blessing the Mac so it does load iPXE straight from the FOG TFTP server without you having to setup DHCP properly. But in your case I don’t think that’s a good option because once macOS is gone it’ll be very hard to change the blessing later on. So you can either go the “Using stones…” method or set the Macs to netboot before deleting macOS - the later has a similar issue to the “Using stones” method because you can’t easily change the bootup setting if macOS is not installed anymore.
I don’t know of any tool that can set boot configuration in NVRAM on Macs other than macOS itself. Possibly tools exist but I don’t know of any. Maybe it can be done using a macOS boot USB key? Give it a go and let us know!
Special note: There is one particular ethernet card in some Macs that do have an issue with iPXE on macOS Sierra and newer - see here! I am working on this but I can’t say when I’ll get that fixed. But it’s only that one particular NIC as far as we know - Broadcom 57765. Take a look at the device manager (About my Mac) to see if you have that NIC in your Macs.
@bloodwar The video is pretty good, though it’s not with the mmap
debug enabled.
@majikins said in Network boot of host comes up with mount permission denied:
ubuntuserver–vg-Images
That LVM is mounted to /mnt/share which probably FOG is not aware of. Take a look at the storage node configuration in the web UI. I recommend to stick to the default path /images
. It’s easier to move things around and leave the FOG default path for it as is.
So depending on what you have in /mnt/share
already (see with ls -al /mnt/share
) - assuming it is mostly empty - I’d go like this:
sudo -i
mv /images/* /mnt/share
mv /images/.mntcheck /mnt/share
umount /mnt/share
Now edit /etc/fstab
and change /mnt/share
to simply /images
. Then remount that mount /images
and you should be all setup.
@bloodwar Yeah, but there are the debug messages from the last picture you took somewhere in between. I’d like to see exactly that screen as picture. Things like real_mode_target ...
and real_mode_mem ...
should be on there.
@bloodwar Please plug the USB key back into a running (Windows) machine and edit the file boot\grub2\grub.cfg
and add ,mmap
to line number 6, so it looks like this:
set myimage=/boot/bzImage
set mydbgimage=/boot/11_bzImage
set myinit=/boot/init.xz
set myloglevel=7
set pager=1
set debug=linux,mmap
set timeout=-1
insmod all_video
...
Boot from that USB key again - now you need to skip through the pages as there are many messages on screen… Best if you can take a steady video of all this.
@tmerrick The logs you posted don’t show anything WOL related. Any PC doing a PXE boot will request files via TFTP, so that’s not an argument for WOL causing the PCs to startup.
If it’d be the FOG server sending WOL packets you would see those in tcpdump on the FOG server!! Maybe connect a Windows PC in the client subnet and look at the packets using Wireshark from there. If the network switch forgot about the client MAC address it needs to send out the WOL as broadcast I think.
@majikins Please run the following commands and post pictures or listings here: mount
and ls -al /images /images/dev
and cat /etc/fstab
(note the spaces in the commands!)
@zago123 Well, please tell us more about the computer model you have issues with. Exact model name, ethernet card (screenshot of the details from Windows device manager for example).
The picture you posted looks like you are booting those machines in legacy BIOS mode (using undionly.kpxe
). Have you tried switching to UEFI (using ipxe.efi
binary) yet?
@bloodwar Ok, I forgot to add one parameter and therefore it fails. But booting essentially works. Could you please take a video of the start sequence between the point where you hit ENTER after selecting one of the two kernels and where the kernel messages scroll past. I’d like to see the GRUB debug messages! You could even just take a picture of it if you know exactly which debug messages I mean. On the screen it should say something like loader/i386/linux.c ....
@majikins said in Network boot of host comes up with mount permission denied:
This problem is exactly like - https://forums.fogproject.org/topic/4979/problem-mounted-file-system-permission-denied-solved
I kind of doubt that yours is exactly like that. The post is two and a half years old and FOG 1.2.0 was the official release back then. I hope you don’t still use version 1.2.0 as we don’t support that anymore. Current stable version is 1.4.4 as of today. Please let us know which version you run.
@bloodwar If we can’t make it work this way yet I’d suggest trying a different combination like GRUB + Linux kernel. For that please download usb.img
(same download link - 64 MB), get an empty USB key and dump that image to USB like this:
dd bs=1M if=/tmp/usb.img of=/dev/sdX
Make sure you have the correct device filename - could be /dev/sdb
or /dev/sdc
… After connecting the USB key to your machine wait 5 seconds for it to settle and the run dmesg | tail
to see which device name it has.
If you only have a Windows machine at hand you can also use Win32DiskImager to write that image to your USB key.
Then boot your Lenovo N24 of that USB key and see what happens. It has GRUB debug enabled and should loop at that stop where we seem to have a problem on “exit_boot_services”. Though I am not sure this will help. It’s just a test to see if you can boot the kernel straight from a GRUB USB key.
@mwarner In that PCAP I only see three TFTP packets. No DHCP packets at all. Probably your network structured in a way that we don’t see the DHCP broadcasts and answers at all. Can you connect a dumb network hub in front of your Surface client and use another PC to capture the network traffic there. You can even use the GUI version called Wireshark if you like.
@kafluke In the WebUI go to this host’s settings an click the button “Reset Encryption Data”…
@tmerrick Do you actually see Wake On LAN packets in your network?? Maybe it’s something completely different. What if you shut down the FOG server? PCs still turn back on?
@unknownhost99 Well, the output looks ok on first sight. What exactly is the issue? What do you see on the client? Timeout/error!?!
@bloodwar 11_bzImage
will try 10 times. Don’t think this helps but it’s easy to test.