Lenovo N22 PXE boot issues

[blue_steel]

@george1421 Wamp Wamp. Hit a snag.

[george1421]

@blue_steel You might want to use the file info I sent you via DM to build that bootable usb drive. Something went wrong with the build you did.

[george1421]

@george1421 If I had to guess what is wrong with your build. I would check the grub.cfg file to make sure these variables are set

set myimage=/boot/bzImage
set myinits=/boot/init.xz

The error would indicate that myimage is not set or is blank. OR bzImage doesn’t exist in the /boot folder on the usb drive.

[blue_steel]

@george1421 Ok, looking good it pulled an ip off the adapter. Well it shows 2 an inet and a brd.

[george1421]

@blue_steel Well I guess you are at a point where you need a management decision.

You can either upgrade the trunk version to the latest (or above r8050) or install 2 files from the trunk build and hope that they act responsible with your current build.

[blue_steel]

@george1421 on 7945 what do you think the odds are they will function reasonably well? I am for updating to trunk…just got to get it approved by the network admin.

[blue_steel]

This post is deleted!

[blue_steel]

@george1421 Ok, so updated to trunk and I think it worked. A couple errors when trying the laptop.

Both registering the host and trying to upload an image.

http://imgur.com/a/9Vzle

http://imgur.com/a/kOTW0

It also passes the fog compatibility test, and pings the host fine under diagnostics.

[blue_steel]

@blue_steel https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Credentials_.2F_Passwords
This seemed to help!

[george1421]

@blue_steel So you found that the fog (linux user’s password) was out of sync with what the FOG database had?

[Wayne Workman]

@blue_steel said in Lenovo N22 PXE boot issues:

@blue_steel https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Credentials_.2F_Passwords
This seemed to help!

@Tom-Elliott this is concerning, since those service pages should have ensured FTP credentials are correct.

[Tom Elliott]

@Wayne-Workman I’m confused isn’t that exactly what they did?

[blue_steel]

@george1421 Indeed, the linux user password here

vi /opt/fog/.fogsettings

Was not correct.

[Wayne Workman]

@blue_steel said in Lenovo N22 PXE boot issues:

@george1421 Indeed, the linux user password here

vi /opt/fog/.fogsettings

Was not correct.

Well, that’s arguable. Anything set in the .fogsettings file is the ultimate definition of “correct” on your system. Everything is based around that file. All updates follow that file. It was correct as far as fog was concerned, it’s up to you to adjust that as you need.

[blue_steel]

Ok, so the fog server is up and running and everything is getting images again after the file fix. Except for the N22. Will try different kernels and see if that helps.

[george1421]

@blue_steel If you have the trunk version installed you have the latest kernels. So no need to work in that area.

Now that you are on a current build, can you refresh our memories what is failing with the N22?

[blue_steel]

@george1421

[george1421]

@blue_steel I know I’m asking for this again, but we have a different set of contexts to deal with (trunk version of fog). If you run a compatibility test does both the hard drive and network adapter pass?

[blue_steel]

@george1421

[george1421]

@Developers Any idea on how to debug this. It looks like its failing in the registration script (fog.man.reg) in the FOS Engine.

I’ve looked at the code between
echo " * Starting host registration"
and
[[ $exists != "#!ok" ]] && handleError "Unable to register host: $exists ($0)\n

There is nothing that jumps out at me other than calls to urls like http://${web}service... where if $web doesn’t contain a trailing slash the call would fail.

@blue_steel cal you tail the apache error log and see if its throwing an error when you try to register. If it is an invalid path the apache error log should trap it.