Added nodes, updated everything to 3429. Can no longer image.
-
Don’t forget that around SVN 3410 and up the storage node installer resets the storage password when run. It should display the new password at the end of the install.
-
i have those new passwords already set in the the storage node part. I have disabled all of them now. I am trying to get something to just boot up and image off the main server like it did. But nothing is happening just that bzimage error failed to load
-
Ok so I tried to use a VM to image and it worked just fine. The VM boots into PXE and will quick image. So why won’t my Lenovo’s? I changed the kernel to what I was told to and it worked I use kkpxe. They were working just fine now all of a sudden they do not? But my VM’s do?
-
@saltlife3122 said:
Ok so I tried to use a VM to image and it worked just fine. The VM boots into PXE and will quick image. So why won’t my Lenovo’s? I changed the kernel to what I was told to and it worked I use kkpxe. They were working just fine now all of a sudden they do not? But my VM’s do?
Can you try kernel 3.19.3 x86_x64 ?
-
when I download that what all do i need to do? I go to the GUI then download it. Then what?
-
@saltlife3122 said:
when I download that what all do i need to do? I go to the GUI then download it. Then what?
FOG Configuration -> Kernel Update -> Download.
That’s it.
-
save it over the previous bzimage
-
when I go to the fog configuration even though i went to the 19.3 kernel it still says 4.0.2.
Still won’t work still get a bzimage error. The VM still quick images just fine. -
If it still says 4.0.2, then something is definately wrong…
Can you doublecheck that FTP is functional? FTP is used to get the kernels.
-
Can you post a pic of the exact error?
-
FTP is working, its enabled and running and I can get to the fog ftp site
-
This is the error from physical machines. VM’s do not get any errors
-
@saltlife3122 said:
This is the error from physical machines. VM’s do not get any errors
Are you, by chance, using dnsmasq?
-
not that I know of
-
Ok…
The issue is that path… three slashes, see them?
We know the problem now, just need to figure out why.
-
Chatted and found out the problem.
This was a two part problem.
Problem number one.
Location Plugin was installed, but no entries were made. I don’t know yet if there’s a bug specifically in this, but there was a location association at one point in time. This lost its association but made it so the default location was not set. This is why the http:///fog/service/ipxe/bzImage was display.
Problem number two.
The FOG Configuration->FOG Settings->TFTP Server->FOG_TFTP_PXE_KERNEL setting was literally set to
/bzImageinstead ofbzImageAny of the files being stated should not have a beginning precursor as such.
Hopefully we’ve helped out and helped figure out other means to troubleshoot.
