mounting /images failed: Connection timed out

[george1421]

@sjensen The first thing I want you to do is this:

On the console of the target computer key in

1. ip addr show that will tell you the current IP address of the target computer (please post it here)
2. I need you to give root a password so we can connect to it remotely (so you don’t have to sit in front of the target computer) passwd and give root a password it can be something as simple as Password-1 or complex, it is up to you. This password will exist until the target computer is rebooted so its only temporary.
3. Install putty on your computer [ http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html ], its a free download and will allow you to connect to the target computer over the network. You will need this to copy and paste commands given by Tom or myself. The exe is not installed, but just run.

I see Tom went in directly to the point.

[sjensen]

@Tom-Elliott

[sjensen]

This post is deleted!

[george1421]

@sjensen OOoops you fell into the kernel hole. The kernels between 4.2 and 4.6 don’t work for FOG 1.2.0, if you upgrade to latest kernels for FOG 1.3.0 you will be in a better state.

cd /var/www/html/fog/service/ipxe
cp bzImage bzImage.old
cp bzImage32 bzImage32.old
wget -P https://fogproject.org/kernels/bzImage
wget -P https://fogproject.org/kernels/bzImage32

Now here is the part I’m not sure of, and Tom will need to answer. I was under the impression that FOG 1.2.0 was 32bit only? if that’s the case we need to rename the kernel file

[sjensen]

@Tom-Elliott this is what got
mount: cant find images: in /etc/fstab

[Tom Elliott]

@sjensen I need to see the exact mount command you used.

The command should not run multiple lines.

[Tom Elliott]

@george1421 1.2.0 (1.0.0 and up really) all used 64 bit and auto adjusted for 32 bit.

[george1421]

@Tom-Elliott said in mounting /images failed: Connection timed out:

@george1421 1.2.0 (1.0.0 and up really) all used 64 bit and auto adjusted for 32 bit.

OK so the names bzImage == x64 and bzImage32 == x86 is still proper for 1.2.0?

[Tom Elliott]

@george1421 Yessir.

[sjensen]

@george1421 Ok gentleman do I need to upgrade 1.3.0 to fix my issue? Or do I need to do some additional debuging?

[Tom Elliott]

@sjensen All of the commands I’m asking you to run should be run on the Client machine, NOT the fog server.

[sjensen]

@Tom-Elliott I used the exact lines you posted on the client in debug mode as instructed. I can send a picture of what is being displayed on the clients screen.

[sjensen]

@Tom-Elliott version 4.8.11 x86_64 from the client

[sjensen]

@Tom-Elliott Thank you both very much for your help the last couple days. I really appreciate it.

[george1421]

@sjensen so on the fog client (target computer)

1. Can you attempt to ping the FOG server? ping <fog_server_IP> where you replace the <fog_server_ip> with the real ip address of your fog server.

2. What was the results of executing Tom’s commands to connect the FOG server from the target computer over NFS.

mkdir /images
mount -o nolock,proto=tcp,rsize=32768,wsize=32768,intr,noatime "192.168.28.10:/images/dev" /images

Then I’ll add my bits

ls -la /images

This should give you a listing of all of the files in the /images share on the fog server.
If you do this from the fog server console ls -la /images the values should be the same.

But, this is where your image capture is failing.

[sjensen]

@george1421
kernel version on client version 4.8.11 x86_64 from the client

mkdir /images
mount -o nolock,proto=tcp,rsize=32768,wsize=32768,intr,noatime “192.168.28.10:/images/dev” /images

result from above commands
mount: cant find images: in /etc/fstab

[george1421]

@sjensen Strange…

Lets try this mount command (sorry I’m old school here, we don’t need all them fancy options where I’m from)

Make sure the /images directory exists on the target computer with ls -la /images (ran from the target computer).

Then mount the local /images on the target computer to /images/dev on the FOG computer
mount -t nfs 192.168.28.10:/images/dev /images

If that one doesn’t work I have another command, but ideally the simple mount command should work.

[sjensen]

@george1421 think i may have found the issue. I cannot ping the fog server from the command prompt on the client. I cannot ping anything on the same network from the client. I don’t get it.

[Tom Elliott]

@sjensen What is the IP of the client?

ip addr

[george1421]

@sjensen said in mounting /images failed: Connection timed out:

@george1421 think i may have found the issue. I cannot ping the fog server from the command prompt on the client. I cannot ping anything on the same network from the client. I don’t get it.

Well in a way this is GREAT NEWS. No pingy means no mounty.

The ip addr show should give you a listing of network interfaces, you want to look for the line with eth0 in it.