FOG 1.0.1 - client doesn't get the FOG boot menu.
-
[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
-
[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 had more success with this file, unfortunately it only boots to line: "Configuring (net0 <mac add>) . . . "
Hardware: Dell OptiPlex 9020
Any other possible tips?
-
yes, try the latest file in the svn trunk. tom worked with the ipxe developers and helped them resolve a bug in their code. as far as i’ve heard, the latest version “just works” for everyone so far.
-
[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’m having the same issues as these guys, brand new install of 1.0.1 on Ubuntu 14.04 server edition. Tried the file above - got an “operation not permitted” message and the machine boots to windows.
This is on a HP Z230 right now.
-
[quote=“Junkhacker, post: 28712, member: 21583”]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][/quote]This one gets stuck on initializing devices after grabbing a dhcp address.
-
[quote=“Dave Hill, post: 29207, member: 24496”]This one gets stuck on initializing devices after grabbing a dhcp address.[/quote]
Try the latest and greatest within svn trunk?
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/[/url]Any of the ipxe or undionly labeled files. They have the “true” fix from ipxe in them.
-
Can i try both? Or does it have to be a undionly.kpxe?
Also, after restarting my server every time to try these new files, when trying to hit the web GUI i get an unable to connect to database error - although i’ve put the password in the commons/config.php folder…it was workign previously
