FOG 1.0.1 - client doesn't get the FOG boot menu.
-
try replacing your undionly.kpxe file with this one [url]http://mastacontrola.com/ipxe/f3d42-QUOTA_20-GOOD/undionly.kpxe[/url] and please report back
-
Thanks for the quick reply.
With that new file, after the 'configuring (net0 -{mac}) line, the machine reboots back to the start of the pxe process. So on the upside, it’s not booting off the hdd now.
But I still didn’t get to the FOG menu. -
we are still narrowing down the exact cause of these problems on some machines. here is another file to try
[url]http://mastacontrola.com/ipxe/f473-GOOD/undionly.kpxe[/url] -
Still no menu, and it rebooted to the pxe. If it helps, the main nic I’m currently concerned with is a Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC.
My guess is that I screwed up something small and dumb on the FOG server, but I don’t know what to troubleshoot, past verifying tftp function. A tech long ago set up the 0.32 version, so I don’t know what (if any) customizations he may have done to it. I ran the update to 1.0.1 and it seemed to go smoothly.
IF the answer winds up being ‘kill it with fire, and start over’ - can I save the old images (we only have 2 saved) and have the new instal recognize them? If not, re-building those images wouldn’t be the end of the world. -
Actually, cancel that Realtek model number, as I’m not 100% sure it’s right. The motherboard is a gigabyte m1m3xap from a new Brix A8, but I’ve also tested with a realtek from about 2 years ago on an MSI 970A-G46. (I know they can put different nics in without changing motherboard model names.)
-
realtek cards are one of the ones having problems. from what i have seen so far, nothing appears to be configured incorrectly in your setup. tftp is operating and serving out the ipxe undionly.kpxe. it’s only then that it fails to pull a dhcp address and load the rest of what it needs.
-
try this file [url]http://mastacontrola.com/ipxe/f3d42-QUOTA_20-GOOD/undionly.kkpxe[/url]
note the extra k, you will need to make sure you dhcp option 67 is set for that (or rename this file to the same as the last one, but make note of this technically incorrect naming convention) -
Ooo, I think that worked. The menu flashed by too fast to get into it, but I did see something new that time. I’m off to lunch, so I’ll try holding up arrow when I return, and report back.
Thanks! -
[quote=“utcreeper, post: 28736, member: 24428”]Ooo, I think that worked. The menu flashed by too fast to get into it, but I did see something new that time. I’m off to lunch, so I’ll try holding up arrow when I return, and report back.
Thanks![/quote]Change the setting in the Fog configuration settings under the dashboard. You want to find the FOG Pxe Menu Configuration setting and up the delay.
-
Good news, lunch was great!
The menu delay had been set at 5, which just flashed by. But, holding up-arrow made it stay, and my machine is now happily imaging. Thank you very much!
I wonder if the menu delay is related to the Mobile A8 that is in the Brix computer, some kind of driver/clockspeed issue. No matter, it’s easy enough to work around, and you have defeated the evil Realtek!
-
[quote=“Junkhacker, post: 28727, member: 21583”]try this file [url]http://mastacontrola.com/ipxe/f3d42-QUOTA_20-GOOD/undionly.kkpxe[/url]
note the extra k, you will need to make sure you dhcp option 67 is set for that (or rename this file to the same as the last one, but make note of this technically incorrect naming convention)[/quote]I used this kkpxe file and was able to get the boot menu & upload my image via Lenovo M78 workstation (similiar RealTek card). However when I go to DOWNLOAD the newly created image, the computer goes into an endless loop, reboots, the task completes and disappears. Any ideas? I’m going to attach a .mov video captured from my phone. Any help would be great. This is a fairly new model just released from Lenovo. Video Link: [url]https://drive.google.com/file/d/0B6t9vun6oTf6MTBRX3pnOGttZ2s/edit?usp=sharing[/url]
-
My guess as to the boot loop issue is that the disk is in GPT partitioning mode where the image is expecting to be mbr.
-
[quote=“TOMMY C, post: 28922, member: 8253”]I used this kkpxe file and was able to get the boot menu & upload my image via Lenovo M78 workstation (similiar RealTek card). However when I go to DOWNLOAD the newly created image, the computer goes into an endless loop, reboots, the task completes and disappears. Any ideas? I’m going to attach a .mov video captured from my phone. Any help would be great. This is a fairly new model just released from Lenovo. Video Link: [url]https://drive.google.com/file/d/0B6t9vun6oTf6MTBRX3pnOGttZ2s/edit?usp=sharing[/url][/quote]
The video that you have posted is pretty much the same thing that’s happening when I try to download an image to one of my computers, only I’ve tried to deploy the image from the Web UI rather then selecting the Quick Image from the PXE menu.
Have you found a fix for this? What do I need to do? Help!!! - I have a dead machine with a new hard drive waiting to be imaged but I’m now really stuck after upgrading to 1.0.1 from 0.33 - I’ve made sure that the Image File has been setup to use the legacy imaging options but that’s made no difference.
Thanks
Matt
-
What’s the image type set to? Partimage or Partclone?
-
I’ve changed my image to be partclone rather then partimage[SIZE=2] in the Image Management interface of the UI as the image was created on an earlier build of FOG.[/SIZE]
-
[quote=“Tom Elliott, post: 28930, member: 7271”]What’s the image type set to? Partimage or Partclone?[/quote]
I’m not certain what mine is set to as I started fresh with an image upload on version 1.0.1. How do I change it? It doesn’t matter if I start the image via the UI or through the boot menu, it continues to loop and never download the image. If I start it with the UI, the job is executed and then when the computer reboots, the job disappears as if it was completed. Before I updated to the [URL=‘http://mastacontrola.com/ipxe/f3d42-QUOTA_20-GOOD/undionly.kkpxe’][I][SIZE=12px]undionly.kkpxe[/SIZE][/I][/URL] file, I wasn’t able to get to the menu at all. It just hung. Tom were you aware of a graphical error in your logo? Version 1.1.0 rather than 1.0.1?
[url=“/_imported_xf_attachments/0/878_Screen Shot 2014-06-03 at 7.42.15 AM.png?:”]Screen Shot 2014-06-03 at 7.42.15 AM.png[/url][url=“/_imported_xf_attachments/0/879_Screen Shot 2014-06-03 at 7.43.46 AM 1.png?:”]Screen Shot 2014-06-03 at 7.43.46 AM 1.png[/url]
-
[quote=“TOMMY C, post: 28995, member: 8253”]I’m not certain what mine is set to as I started fresh with an image upload on version 1.0.1. How do I change it? It doesn’t matter if I start the image via the UI or through the boot menu, it continues to loop and never download the image. If I start it with the UI, the job is executed and then when the computer reboots, the job disappears as if it was completed. Before I updated to the [URL=‘http://mastacontrola.com/ipxe/f3d42-QUOTA_20-GOOD/undionly.kkpxe’][I][SIZE=12px]undionly.kkpxe[/SIZE][/I][/URL] file, I wasn’t able to get to the menu at all. It just hung. Tom were you aware of a graphical error in your logo? Version 1.1.0 rather than 1.0.1?[/quote]
It’s partclone for the image upload…
-
that’s not an error. you’re running a pre-official release version of 1.1.0
the latest official release is 1.0.1
if you have not used prior versions of fog, all your images are partclone format, and you do not need to change anything -
[quote=“Junkhacker, post: 29011, member: 21583”]that’s not an error. you’re running a pre-official release version of 1.1.0
the latest official release is 1.0.1
if you have not used prior versions of fog, all your images are partclone format, and you do not need to change anything[/quote]Thanks for the clarification. I just discovered that if I use the same hard drive that I uploaded with (download to the same hard drive), the image download process works. If I change hard drive it fails. The original HD is 500 GB and I tried to download to an 80 GB drive (actual image is about 20 GB in size). Minor discovery. I’m going to try and cleanly wipe the 80 GB and see if it’ll take the image.
-
only the single disk re-sizable image type option allows you to put an image on a smaller size drive then the one you made it on
