@george1421 I changed EFI to rEFInd. I changed legacy to the GRUB_FIRST_HDD. So far every machine I have found is working! Thanks for the help. My Bootfile Name on the DHCP server is set to: undionly.kkpxe. I have seen others who use undionly.kpxe. Should I just leave it since it is working?
Posts made by Andrew Seals
-
RE: Chainloading failed
-
RE: Chainloading failed
@george1421 Changed it to GRUB_FIRST_HDD. It is now working on the Hyper V virtual. Let me see what it does on the other physical machine that was giving me issues.
-
RE: Chainloading failed
@george1421 I went into Fog System Settings -> Fog Boot Settings and changed it to SAN Boot. Now the machine is sitting at: “Booting from SAN device 0x80”
-
RE: Chainloading failed
#!ipxe set fog-ip 10.25.8.68 set fog-webroot fog set boot-url http://${fog-ip}/${fog-webroot} cpuid --ext 29 && set arch x86_64 || set arch i386 goto get_console :console_set colour --rgb 0x00567a 1 || colour --rgb 0x00567a 2 || colour --rgb 0x00567a 4 || cpair --foreground 7 --background 2 2 || goto MENU :alt_console cpair --background 0 1 || cpair --background 1 2 || goto MENU :get_console console --picture http://10.25.8.68/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console :MENU menu colour --rgb 0xff0000 0 || cpair --foreground 1 1 || cpair --foreground 0 3 || cpair --foreground 4 4 || item --gap Host is NOT registered! item --gap -- ------------------------------------- item fog.local Boot from hard disk item fog.memtest Run Memtest86+ item fog.reginput Perform Full Host Registration and Inventory item fog.reg Quick Registration and Inventory item fog.deployimage Deploy Image item fog.multijoin Join Multicast Session item fog.sysinfo Client System Information (Compatibility) choose --default fog.local --timeout 5000 target && goto ${target} :fog.local exit || goto MENU :fog.memtest kernel memdisk initrd=memtest.bin iso raw initrd memtest.bin boot || goto MENU :fog.reginput kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://10.25.8.68/fog/ consoleblank=0 rootfstype=ext4 storage=10.25.8.68:/images/ storageip=10.25.8.68 loglevel=4 mode=manreg imgfetch init_32.xz boot || goto MENU :fog.reg kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://10.25.8.68/fog/ consoleblank=0 rootfstype=ext4 storage=10.25.8.68:/images/ storageip=10.25.8.68 loglevel=4 mode=autoreg imgfetch init_32.xz boot || goto MENU :fog.deployimage login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme param sysuuid ${uuid} :fog.multijoin login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param sessionJoin 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme param sysuuid ${uuid} :fog.sysinfo kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://10.25.8.68/fog/ consoleblank=0 rootfstype=ext4 storage=10.25.8.68:/images/ storageip=10.25.8.68 loglevel=4 mode=sysinfo imgfetch init_32.xz boot || goto MENU :bootme chain -ar http://10.25.8.68/fog/service/ipxe/boot.php##params || goto MENU autoboot
-
RE: Chainloading failed
The pxe booting computer that I am using now is a Hyper V virtual machine. It is running in bios mode. I have tried it with physical machines that are also running in bios. (same result).
Pictures are attached.![1_1547825224141_2019-01-18 10.20.23 (Phone).jpg](Uploading 100%) ![0_1547825224140_2019-01-18 10.19.41 (Phone).jpg](Uploading 100%)
-
Chainloading failed
I am in the process of creating a new Fog Server for my School District. My current one is on version 1.4. using Ubuntu. I wanted to have a virtual one and try out CentOS 7 so I started from scratch. It is using Fog version 1.5.4. I created a virtual Windows 10 machine to test with. When it boots to the new Fog Server, it will load the Fog menu and if I wait it out, it tries to boot but gets the Chainloading failed message. It then gets stuck in a boot loop. If I switch DHCP back to the old Fog Server things work. I have tried all of the BOOT EXIT types and nothing seems to help. Trying a few kernals didn’t help.
-
RE: HP Elite 8300
I’m going to update this thread because the only thing worse than finding no solution to your problem on Google is finding a problem listed without a solution.
These machines can in with 8gb of RAM. Some came in with 4 2gb sticks of memory and some came with 1 4gb and 2 2gb sticks. The machines without the 4gb stick work perfectly. They will image just fine. If I image them and then add the 4gb stick back in, they blue screen. So Tom was correct, it was a RAM issue. The 4gb stick of RAM is causing the issue. Thanks for all the help!
-
RE: HP Elite 8300
@george1421 We have uefi turned off. We are using traditional 500gb hard drives. How do I run the compatibility test?
-
RE: HP Elite 8300
I forgot to specify. We have tried 3 machines with similar results.
-
HP Elite 8300
We have been using Fog for quite awhile in our school district. Version 1.2 is running on an Ubuntu server. I can image Dell 755 machines all day long. We just recently received some HP Elite 8300 machines. They will boot to Fog and will start the imaging process. Somewhere around 3% we get an error screen. (Link to error screen images: https://drive.google.com/file/d/0B6nBHKipfiXTd1NrcnJzWHk5TEE/view?usp=sharing)
I have tried updating the kernel, and that didn’t help. The image is set to single disk resizable.
I would appreciate any help that you could provide. -
Kernel update stuck at: Download Completed! Moving file to TFTP server...
I can download the kernel update, but it gets stuck at: Download Completed! Moving file to TFTP server…
Fog version 1.2.0 on Ubuntu 14.04.
Any help would be appreciated. I searched the forum and didn’t find anything that worked. I did try turning the firewall off.
-
/Images Permission issues after Ubuntu 14.0.4 upgrade
I have Fog version 1.2.0 installed on an Ubuntu server. It was on version 12 and kept asking me if I wanted to update to version 14.0.4. In my head it sounded like a great idea. In reality, it has caused me some issues I have fog working again and can grab clients and upload an image. The issue is that the task never completes because I get a message that fog doesn’t have access to the /images folder. I am fairly green when it comes to Ubuntu. I have tried to give the fog account permission to the /images folder, but I am not successful. Can somebody point me in the right direction. I can manually copy the image from the /images/dev/MAC xxxx folder to the the /images folder. I’d hate to have to do this every time I create an image.
-
RE: Image upload/deploy screen colors wrong
I found the solution.
Version .32 uses what they call a partimage. Version 1.2.0 uses a partclone. If you image with a partimage, you get the goofy colored screen. If you image with a partimage, you get the correct colors and a progress bar. To convert a partimage to a partclone all you need to do is send the image to a PC and then upload it back to fog. Once I did that, things look correct again.
-
RE: Join domain not working in 1.2.0
Is that new from version .32 to version 1.2? I saw that in the log but wasn’t sure if I should mess with it. I will set it now and test.
That would make sense why a newly registered machine would reimage and rename and an old one wouldn’t. The new machine does have all of the services checked in the Fog Console.
-
RE: Join domain not working in 1.2.0
My log is attached. It wouldn’t let me copy/paste it here
[url=“/_imported_xf_attachments/1/1385_fog1.txt?:”]fog1.txt[/url]
-
RE: Join domain not working in 1.2.0
It is only showing events from today. I will image another PC and pull the log right after it finishes.
-
Join domain not working in 1.2.0
Just upgraded from version .32 to 1.2.0. If I take a machine and go through the host registration and image, things go fine. The machine images, renames itself, and joins the domain. We are using an Ubuntu 11 server and all of our clients are Windows 7 Dell Optiplex 755s.
If I take a machine that is currently on the domain and reimage it, it will not rename or join the domain. It’s name stays the generic CNEPC.
I went into the AD defaults and took out the domain\user from FOG_AD_DEFAULT_USER field. I put all machines in a group and changed the AD settings in that group to reflect the new changes. Still no luck.
I’m having all kinds of issues with 1.2 that I didn’t have with .32. Any help would be appreciated!
[SIZE=4][B][COLOR=#4c68a0][B]Active Directory Defaults[/B][/COLOR][/B][/SIZE]
[FONT=Ubuntu][COLOR=#555555]FOG_AD_DEFAULT_DOMAINNAME: mydomain.org[/COLOR][/FONT]
[RIGHT] [/RIGHT]
FOG_AD_DEFAULT_OU: OU=New Computers, OU=CNE Computers, OU=mydomain,DC=org
[RIGHT] [/RIGHT]
FOG_AD_DEFAULT_USER: fog
[RIGHT] [/RIGHT]
FOG_AD_DEFAULT_PASSWORD: (encrypted password)
[COLOR=#555555][FONT=Ubuntu]Show[/FONT][/COLOR]
[RIGHT] [/RIGHT] -
RE: Image upload/deploy screen colors wrong
Is there a solution to this? It makes me want to go back to version .32!
-
RE: Client text backgroud-foreground colors in fog 1.2.0
I am seeing the exact same screen on every client I image. Is there a way to fix this? It is hard to read! So far, all of my clients have been Dell Optiplex machines. Most are the Optiplex 755.