mounting /images failed: Connection timed out
-
@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?
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
-
@george1421 Yessir.
-
@george1421 Ok gentleman do I need to upgrade 1.3.0 to fix my issue? Or do I need to do some additional debuging?
-
@sjensen All of the commands I’m asking you to run should be run on the Client machine, NOT the fog server.
-
@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.
-
@Tom-Elliott version 4.8.11 x86_64 from the client
-
@Tom-Elliott Thank you both very much for your help the last couple days. I really appreciate it.
-
@sjensen so on the fog client (target computer)
-
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. -
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" /imagesThen I’ll add my bits
ls -la /imagesThis 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 consolels -la /imagesthe values should be the same.But, this is where your image capture is failing.
-
-
@george1421
kernel version on client version 4.8.11 x86_64 from the clientmkdir /images
mount -o nolock,proto=tcp,rsize=32768,wsize=32768,intr,noatime “192.168.28.10:/images/dev” /imagesresult from above commands
mount: cant find images: in /etc/fstab -
@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 /imagesIf that one doesn’t work I have another command, but ideally the simple mount command should work.
-
@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.
-
@sjensen What is the IP of the client?
ip addr -
@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 showshould give you a listing of network interfaces, you want to look for the line witheth0in it. -
@Tom-Elliott Strangely enough there is not an ip address
-
@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 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.
-
(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). -
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.
-
-
@Tom-Elliott Will the instructions in 1. work for Ubuntu 14.04??
-
@sjensen Yes, just remember you will need to be root first.
-
If you run into issues start a new thread and let us know so we can help out.
