Lenovo N22 PXE boot issues

[Wayne Workman]

@blue_steel in putty, to copy you select text and just right click. To paste something from the clipboard, just right click.

[blue_steel]

Ok, so maybe my issue is here…

mkfs.fat 3.0.28 (2015-05-16)
/dev/mapper/loop0p1: No such file or directory
Mount the filesystem via loopback
mount: special device /dev/mapper/loop0p1 does not exist
Install GRUB
grub-install: error: /usr/lib/grub/i386-efi/modinfo.sh doesn’t exist. Please specify --target or --directory.
grub-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn’t exist. Please specify --target or --directory.
Installing for i386-pc platform.
grub-install: error: failed to get canonical path of `/cow’.

I am a linux noob running off of a live usb, so putty isn’t really possible. But I think my main issue might be in the above.

[george1421]

@blue_steel Let me make this img for you. I found out during testing that I have the best luck with ubuntu but there are adjustments needed to the script. I’ll create a current img file and upload it to dropbox so you can get it. That would address your issues.

[blue_steel]

@george1421 You are truly a wizard!

[blue_steel]

@george1421 Some success!!!

[george1421]

@blue_steel Excellent.

1. Make sure you have the network cable installed
2. Now select option 6.
3. When you see press enter to continue you will have to hit enter a few times.
4. That should drop you to a command prompt. (This is the FOS engine command shell)
5. Now key in ip addr show that should report the ip address of that target computer.

Hopefully the FOS engine sees your network adapter. If you can get this far then we can talk about part 2 if you don’t want to update your FOG server.

[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.