Suggestion please

george1421

@ziolucione In the section picture, The lines we need to investigate in the log file have minimum version required iwlwifif-7 (can’t see the rest). This should be the area in the log file that describes what went wrong.

Also post what sebastian posted with a twist.

lspci -nn |grep -i net
and
lsusb

ziolucione

@Sebastian-Roth

guys sorry for the quality

ziolucione

@george1421

george1421

@ziolucione In case you don’t know how to use vi (very basic and cryptic text editor to look at messages file)

vi /var/log/messages

the key sequence is very cryptic but key in the following

/ no suitable firmware found and press enter. It should jump you down to the line where the firmware isn’t found. If it doesn’t get the line with iwlwifi in it (the name of the intel driver) hit / and press enter again it will jump to the next occurrence. Take a screen shot of where its says the proper firmware needed. Then to exit the vi editor hit ESC key then :q!

george1421

@ziolucione OK great that is what I needed iwlwifi-7265D

george1421

@ziolucione https://drive.google.com/open?id=1OnLxsKRboYoxv3LMcupyZAMDgvkTp-qa

Download this to the usb stick replacing bzImageWiFi on the flash drive.

ziolucione

@george1421 Thanks, I have the wireless adapter wlp1s0 (and I believe I have also an IP address now)

george1421

@ziolucione Ok now lets take baby steps.

Manually register the mac address of the wifi adapter with FOG ip link show will get you the mac addresses. Once the target computer is registered create a image definition to capture the tablet to (we are only interested to see if we can capture the image, we don’t care about the image). Assign that image to the target computer. Then schedule a capture task in FOG. Now reboot the tablet and pick option 1 in the grub menu. Hopefully the target computer will start capturing the image and completes fully. IF that works then we can discuss the load and go steps since we don’t have iPXE to help us use the standard method.

ziolucione

@george1421 Alright, I have to change the FOG configuration to use the wifi instead of ethernet. I’ll keep you posted.

Thanks indeed
Much appreciated.

L.

george1421

@ziolucione said in Suggestion please:

I have to change the FOG configuration to use the wifi

I don’t understand this, you shouldn’t have to do anything with the FOG Server end for wifi since the target computer is the only bits using wifi to connect to your network infrastructure. I want to make sure we are on the same page when setting this up.

ziolucione

@george1421 from the wifi network I cannot reach the wired one. So, because FOG server is on the wired one, I have to revert back the FOG server to use the wifi. They are on 2 different subnets with no network rules between them.

ziolucione

@george1421
Hi, I have reconfigured the FOG server to use wifi.

How can I register the MAC address manually?
Option 2 in the FOS menu list?

Thanks.
L.

george1421

@ziolucione Well there are 2 options,

Use the Grub menu and pick one of the registration options (2 or 3 if I remember correctly)
Go into the web ui and in host management and create a new host. Key in the proper values and the mac address you collected from the target computer during the debug session.

Either way will work.

ziolucione

@george1421

But let me check the patclone option, probably I have made a mistake. I have selected to not use compression.

Rgards.
L.

george1421

@ziolucione What version of FOG are you using?

ziolucione

@george1421 From the master branch v1.5.7 I believe.

george1421

@Sebastian-Roth this init is using the updated init files from github. Looking at the error code, its almost like bash didn’t do the variable expansion. The troubled line in 2071 from the funcs.sh script.

partclone.$fstype -n "Storage Location $storage, Image name $img" -cs $part -O $fifoname -Nf 1 -a0

Was this section of code changed since 1.5.7?

Edit: Looking at the partclone screen again, I see we are getting the command line parameters into partclone because I can see bits of them on the partclone banner. I’m starting to suspect fog server access now. This is also partclone 0.3.12.

george1421

@ziolucione Will you show me screen shots of the host definition and image definition [PPTestImage] for this target computer?

We may need to do a debug session with this image. Because either partclone is blowing up for some reason or it can’t access the fog server or write to the destination on the fog server. It should have failed before now if it can’t reach the fog server.

ziolucione

@george1421 IMG_20191203_131244 (2).jpg

george1421

@ziolucione Ok (unfortunately for me) everything appears to be setup correctly. So what we are going to do is to edit the grub.cnf file like you did when you updated your wifi ssid information. Search down that config file for a section that looks like this:

menuentry "1. FOG Image Deploy/Capture" {
 echo loading the kernel
 linux  $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 ssid=$ssid ssidpw=$ssidpw
 echo loading the virtual hard drive
 initrd $myinits
 echo booting kernel...
}

It won’t be exact because there will be the ssid and ssidpw kernel parameters ( don’t have the image file at my office) but after those parameters add in <space> isdebug=yes. That section should look similar to this:

menuentry "1. FOG Image Deploy/Capture" {
 echo loading the kernel
 linux  $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 ssid=$ssid ssidpw=$ssidpw  isdebug=yes
 echo loading the virtual hard drive
 initrd $myinits
 echo booting kernel...
}

Save and exit the editor. Move the USB back to the target computer and usb boot. Make sure the current capture task is still active on the fog server then pick option 1 again. This will start the capture task in debug mode. You will be dropped to a linux command prompt. In the option 1 debug mode (different than option 6) we can launch the capture by keying in fog <enter>. At each break point in the deployment script it will pause waiting for an enter key press. What we want to do is single step through the capture until the error is thrown then hit ctrl-C to drop back to the linux command prompt.

At this point I want to make sure the target computer can still reach the fog server key in ls -la /images You should see files in that directory and a directory with the same name as the mac address of the target computer. See if that directory exists then look into that directory to see if any files have been created. (we are testing from the fos engine side at this point). But on the fog server you should also find those files in /images/dev directory.

Suggestion please

248

11.6k

17.1k

154.6k