How to pxe boot cent os 7
-
@george1421 said in How to pxe boot cent os 7:
/var/www/fog/service/ipxe *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
that one liner is pretty nice
-
@Wayne-Workman @george1421
I am getting no such file or directory exist , how do i fix this?“bash: 192.168.1.109: No such file or directory”
-
@dureal99d I’m not sure how much you know, but it doesn’t hurt you or future readers to just re-iterate what I know.
The /etc/exports file is for Network File System exports. This is how Linux natively shares files across a network.
http file distribution is done via Apache or nginx or some other http service, and is NOT nfs. these paths you have in your original post, they are web paths. Such as:
http://${fog-ip}/fog/service/ipxe/Centos/images/pxeboot/initrd.img
This is a web path. This would be accessible if you plugged the fully expanded URL into a web browser. This is not via NFS, but via HTTP using apache to serve it.Please post a picture of the error you’re getting, it’ll help us figure out what’s going on.
-
-
@Wayne-Workman I see, well clearly i have a lot to learn about nfs. and i am at another station trying to “linux” of course trying to mount the share.
-
@dureal99d I’d suggest you move all that stuff to somewhere else besides a web directory. This is a rather very nasty setup IMO - and as it is this is absolutely going to fill some partition somewhere eventually as FOG makes a complete copy of the web directory each time you re-run the installer (to update or to troubleshoot). You need to put this stuff elsewhere.
-
Where are you seeing no such? Is it in ipxe or just in cli? It appears, to me, your cli is wrong as you have <> in the cli around the IP. This is incorrect, or so I thought. It should be ip:/path/to/mount
-
@Wayne-Workman said in How to pxe boot cent os 7:
directory. This is a rather very nasty setup IMO - and
Ok I’m in the middle of moving it all to the suggested location as we speak.
-
@Tom-Elliott said in How to pxe boot cent os 7:
Is it in ipxe or just in cli
my cli is clearly wrong then as I just copied and pasted what @george1421 put a command I should use to mount and now that I look at it I probably read it wrong
-
@dureal99d it was right. In Linux when describing and line it’s quite common to use <> as a means to say: replace with… Just remove the <> and change the string for your setup
-
@Tom-Elliott ok so i did as suggested and now i get this
mount: wrong fs type, bad option, bad superblock on 192.168.1.109:/opt/bootimgs/fedora,
missing codepage or helper program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount.<type> helper program)In some cases useful info is found in syslog - try dmesg | tail or so.
-
@dureal99d our Troubleshoot NFS article linked below explains troubleshooting NFS as it relates to FOG, might help you with understanding.
But let’s take a basic example?
The images directory. It’s exported as such:
/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
Say that server’s IP address is 10.0.0.4. From a remote Linux box, I’d mount this NFS shared directory to a local directory called
/mnt
as such:mount 10.0.0.4:/images /mnt
Now, if I were to try to describe to you how to do this but try to also say “replace this field”, I might say:
mount <your IP here>:/images /mnt
all this means is completely remove the left & right carrots and put an IP there instead.But, to the root of the issue, it looks like your boot menu is using
http
which has absolutely nothing to do with NFS at all. Completely nothing to do with it.If you were to put your ISOs somewhere else, and create a soft symbolic link to them somewhere in the web directory, and then set permissions properly and path your menu properly, you can get these things working again. We would need to know where you’re putting stuff to help out.
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_NFS
-
@dureal99d lose the -t nfs?
-
@Wayne-Workman as suggested by @george1421 I am moving all my files to a folder called /opt/bootimgs on my Linux box
-
@Tom-Elliott removed the suggested lines from the command same result
-
@dureal99d said in How to pxe boot cent os 7:
@Wayne-Workman as suggested by @george1421 I am moving all my files to a folder called /opt/bootimgs on my Linux box
Because your boot menu is using http, you would still need to create a soft symbolic link from this new directory to somewhere in the web directory.
-
@Wayne-Workman said in How to pxe boot cent os 7:
you would still need to create a soft symbolic link from this new directory to somewhere in the web directory.
Ok how do i create this soft link?
-
@dureal99d The syntax is:
ln -s <source> <destination>
You should remove the left/right carrots when running the command.
If all the ISOs are in /opt/bootimgs the command would be:
ln -s /opt/bootimgs /var/www/html
Of course, apache needs access to this new directory also. It’s fine to set ownership of
/opt/bootimgs
to apache:root or 777 or something.And your resultant web path to these files would then be:
http://<IP>/bootimgs/whatever
-
@Wayne-Workman ok ima get on it and post the results shortly
-
@dureal99d after setting the new nfs paths, did you run
exportfs -a