Tagged: geexbox PXE
April 27, 2017 at 02:04 #11649
I am sorry to disturb your rest time
My client side has caught the server sent dhcp
Finally, still can not mount root fs
I set the relevant value po you see where is the problem Thank you
:Data folderApril 27, 2017 at 02:12 #11652April 27, 2017 at 06:13 #11653
Everything seems quite good
as I can see :
192.168.2.21 is nfs-server
192.168.2.21 is dhcp server too
on this machine, (if ubunutu like ?), what returns
cat /var/log/syslog | grep rpc
you should see something like :
Apr 26 20:51:33 servA rpc.mountd: authenticated mount request from 192.168.1.24:753 for /data/geexbox-nfs2 (/data/geexbox-nfs2)April 27, 2017 at 06:20 #11654
hum, one thing : your gateway is quite not standard : 255.255.255.255 ? (first photo)April 27, 2017 at 08:14 #11655
1.nfs-server dhcp-server samba-server is 192.168.2.21
2.i use centos 7 i can’t find /var/log/syslog XD
3.I revised the dhcp set up after the gateway has been normal
But finally the same can not mout the problem
Although it is made to obtain IP but unable to mount mount
I guess will not be a network card did not drive success?
i use this iso —> geexbox-devel-20170426-r75682bb-i386.iso
April 27, 2017 at 11:59 #11657
- This reply was modified 2 years, 6 months ago by antony0509.
1) You should have some logs about that in /var/log/*
here maybe : https://docstore.mik.ua/orelly/networking_2ndEd/nfs/ch14_06.htm
2) hum, I have no more ideas
is it the same gateway configured in your server ?
I’m pretty sure that now it’s a problem of gateway, (so the geexbox can not connect the server)
or a problem with your nfs server (sometimes i have to restart mine even without errors on logs)April 27, 2017 at 15:22 #11658
Not sure if it can help you, but there is something interesting here :
Cheers !April 30, 2017 at 08:22 #11659
Just a quick note :
on virtualbox :
1) I created an isolated debian server for dhcp, nfs, and tftpd-hpa. Installing geexbox on it to allow booting via the network
2) using a 2nd virtual machine, with no disk, no cdrom, I was able to boot using this server.
So to summarize, you have a problem with your network or firewall or …
I will update the documentation to boot from network
B.RApril 30, 2017 at 16:28 #11669
Because the recent home out of things
So until now to see your Replies
And then go to work on Tuesday to test to see
Time to talk to your return the results thank youMay 3, 2017 at 02:38 #11689
I am sorry to ask you that is a linux operating systemMay 3, 2017 at 06:11 #11690
Sorry, I do not understand.May 3, 2017 at 07:50 #11691
You are using that kind of linux?May 3, 2017 at 08:17 #11692
I also use Debian 8 is the same error message
I really do not know where the problem isMay 3, 2017 at 12:02 #11694
I use debian8 on a virtual machine and geexbox on a virtual machine to isolate them from my real lan.
So debian8 is the dhcp, tftp and nfs server. Once configured, geexbox boot using nfsroot.
o to summarize, no problem from our side.
Now, for you,
step 1) your dhcp server is (seems) ok : you have an ip and you can go to the next step
step 2) your tftpd server too (you have already a menu)
step 3) your nfs server : maybe the problem is here, it’s not necessary a problem with your server
-> from another computer on your lan , try to mount a nfs share, if you have a problem, maybe check your firewallMay 4, 2017 at 01:32 #11698
If the client side today I use CD-ROM boot
And then use nfs to mount server can be successful
So I will say really do not know the problem is out there
- You must be logged in to reply to this topic.