mounting /images failed: Connection timed out

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

[sjensen]

@Tom-Elliott Strangely enough there is not an ip address

[george1421]

@sjensen Do you see a line for eth0? There will be one for the loop back interface lo or something like that.

Part 2 of the question is what type of ethernet adapter is in this computer? Is it a usb ethernet adapter or a built in one on the motherboard?

[sjensen]

@george1421

Pretty sure it is an intel adapter

the Ethernet is built on the motherboard

[Tom Elliott]

@sjensen Based on what I’m seeing, your issue is the kernel isn’t doing what I hoped it would be doing.

You can do one of two things.

1. (and I’d recommend this over everything else), install the Latest RC (37 if you’re unsure) following the Wiki: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk#Git
   I recommend this method because you will get all of the fixes and improvements, features, etc in the current RC system. (Most of which you’ll likely never know you wanted but will be pleasantly, and automatically, available by upgrading).

2. Change the backup kernel to your primary (go back to what came with 1.2.0). The Problem is 1.2.0 didn’t auto populate the devices with IP addresses via a service. I modified the 1.3.0 kernels to try to read the IP address during the load of the kernel itself, but it seems this didn’t work for you. The error messages you were seeing (tsc: calibration) whatever didn’t mean anything and did not pose any threat or mean your systems were not compatible with fog.

[sjensen]

@Tom-Elliott Will the instructions in 1. work for Ubuntu 14.04??

[Tom Elliott]

@sjensen Yes, just remember you will need to be root first.

[Tom Elliott]

If you run into issues start a new thread and let us know so we can help out.

[sjensen]

@Tom-Elliott thanks

[sjensen]

@Tom-Elliott I forgot how be the root, can you point me in the right direction?

[sjensen]

@sjensen i tried sudo at the start of the string. I am getting could not open lock file /var/lib/dpkg/lock - open (13: permission denied)