Posts made by Tom

@Wayne-Workman WOW, I don’t know what change, but it’s working now. I was able to register the OptiPlex 990 and the Latitude E7240.
Now I have to figure out the new interface, since it’s very different from 0.31.

THANK YOU ALL FOR YOUR HELP, I WOULD NOT BE ABLE TO DO IT WITHOUT YOU.

Tom

@Wayne-Workman So, disabled the firewall on my win 10 machine. Ran tftp -i x.x.x.x get undionly.kpxe successfully.
I’m not sure why target machine cannot boot to pxe.

Thanks,

Tom

@Wayne-Workman as much as I agree with you, that decision was made above me. Also, I have never encountered any issue with this setup.
In terms od fog, I never had any issue while running 0.31.

@Tom-Elliott Let me explain, I have 2 domain controllers in one subnet providing DHCP to workstations (70/30 rule). The 3rd is DHCP server on different subnet, which does not play any role in this scenario.
I build new VM from scratch, Ubuntu 14.04.3 and fog 6257.
From DCs I was able to ping fog successfully.
Options 66 set with ip address correctly
Option 67 set to undionly.kpxe. I tried kkpxe and pxe - I got “selected boot device failed”. When it was incorrectly set to prelinux.0 I got the kernel panic-not syncing error.
Installed tftp on my windows station, tried to do tfpt -I x.x.x.x get undioly.kpxe and received the following error:
Timeout occurred, connect request failed.
On the fog machine: Ran tftp -v x.x.x.x -c get undionly.kpxe and got:
Connected to x.x.x.x (x.x.x.x), port 69
getting from x.x.x.x:undionly.kpxe to undionly.kpxe [netascii]
Received 92617 bytes in 0.3 seconds [2762316 bit/s]
Then, ran service tftp-hpa status and received tftp-gpa:unrecognized service
Ran cat /etc/xinetd.d/tftp results looks correct.
Ran cat /etc/default/tftpd-hpa and got "cat: /etc/default/tftp-hpa: No such file or directory

I hope it will give you a better insight,

Thanks for all the help

Tom

@Tom-Elliott You are right, I checked the 3 domain controllers that hold DHCP, 2 had pxelinux.0 and the other had undionly.kpxe.
did not pay attention. (so sorry)
so, after correcting it, my client cannot boot from pxe at all. I tried undionly.kkpxe as well.
I get “selected boot device failed”.
I also updated to 6257.
Thanks,

Tom

@Tom-Elliott Tom, if you referring DHCP option 67 than the value is undionly.kpxe , I will try undionly.kkpxe and let you know.
Other than that I will need more clarification where to look.

Thanks,

Tom

@george1421 George, at this point I will do it, I need it working. The questions are:

1. will it most likely to resolved the issue? After the P2V I ran into updating the schema issue.
   so, I installed 14.04 fresh and (at the time) fog 6028 and since then I have kernel panic issue

In any case, I’ll build new VM, really have nothing to lose.

2. How easy it will be to export the images files and setting from my 0.31 machine?

Thanks a lot,

Tom

@george1421 George,

As I mentioned earlier in this thread, the mode is bios. My DHCP 67 option set to:undionly.kpxe

Maybe the issue lies in the VM settings.

The first FOG was physical machine with Ubuntu 10.1 and Fog 0.31. Then I P2V it and it was tested successfully.

When trying to upgrade, all issues started.

Maybe the recent version of Fog/Ubuntu require certain settings to be set on the VM in order to work properly.

Thank you all for the help and patience.

@Sebastian-Roth Yes, just tested Latitude E6330 - Same results.

@Sebastian-Roth Yes, the dates are copy/paste typo. My client’s are the OptiPlex 990 and Latitude E7240.
They both shows the same error.

Thanks,

Tom

@Tom-Elliott

Also, ran this again:
sudo ls -al /var/www/html/fog/service/ipxe/init* ; ls -al /var/www/html/fog/service/ipxe/bzImage*

Results:
-rw-r–r-- 1 fog www-data 17611576 Feb 8 13:08 /var/www/html/fog/service/ipxe/init_32.xz
-rw-r–r-- 1 fog www-data 18786192 Feb 4 13:08 /var/www/html/fog/service/ipxe/initxz
-rw-r–r-- 1 fog www-data 6957536 Feb 4 13:08 /var/www/html/fog/service/ipxe/bzImage
-rw-r–r-- 1 fog www-data 6856848 Feb 4 13:09 /var/www/html/fog/service/ipxe/bzImage32

@Tom-Elliott Thank you, successfully updated to 6237. The issue is not resolved.

Should I start over from scratch? will it make any difference?

Thanks,
Tom

@Tom-Elliott
Navigating to svn/trunk/bin
sudo installfog.sh

@Tom-Elliott
Trying to run installfog.sh and I get command not found.

At this point, would it make any difference is I’ll scrap the VM and start from scratch?

Thanks,

Tom

@Sebastian-Roth
Ran the following command:
sudo ls -al /var/www/html/fog/service/ipxe/init* ; ls -al /var/www/html/fog/service/ipxe/bzImage*

Results:
-rw-r–r-- 1 fog www-data 17659820 Feb 4 13:37 /var/www/html/fog/service/ipxe/init_32.xz
-rw-r–r-- 1 fog www-data 18750104 Feb 4 13:36 /var/www/html/fog/service/ipxe/init.xz
-rw-r–r-- 1 fog www-data 6883968 Feb 4 13:37 /var/www/html/fog/service/ipxe/bzImage
-rw-r–r-- 1 fog www-data 6783136 Feb 4 13:37 /var/www/html/fog/service/ipxe/bzImage32

@Tom-Elliott Not sure if it’s relevant, but I thought I throw it out there:

My Fog is VM lives on ESXI 6. The disk type is Thick provision Lazy Zeroed.

Tom

@Sebastian-Roth Completed svn up successfully - Running 6196.

Tested on the OptiPlex 990 and the Latitude E7240 - the issue is not resolved.

I get the same error.

Thanks,

Tom

@george1421 Captured the boot process here

I tried to record it in slow motion both with Galaxy S5 and iPhone 6 - That’s the best results.

Thanks,

Tom

@Sebastian-Roth

I had to run the command on different path: /var/www/html/fog/service/ipxe

resuls:
-rw-r–r-- 1 dog www-data 17660824 Feb 3 16:01 /var/www/html/fog/service/ipxe/init_32.xz

-rw-r–r-- 1 fog www-data 18752488 Feb 3 16:01 /var/www/html/fog/service/ipxe/init.xz

-rw-r–r-- 1 fog www-data 6883968 Feb 3 16:01 /var/www/html/fog/service/ipxe/bzImage

-rw-r–r-- 1 fog www-data 6783136 Feb 3 16:01 /var/www/html/fog/service/ipxe/bzImage32

@george1421 Tried to register Dell E7240, the same results - Kernel is panicing.