How to pxe boot cent os 7

[dureal99d]

@Wayne-Workman as suggested by @george1421 I am moving all my files to a folder called /opt/bootimgs on my Linux box

[dureal99d]

@Tom-Elliott removed the suggested lines from the command same result

[Wayne Workman]

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

[dureal99d]

@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?

[Wayne Workman]

@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

[dureal99d]

@Wayne-Workman ok ima get on it and post the results shortly

[Tom Elliott]

@dureal99d after setting the new nfs paths, did you run exportfs -a

[Tom Elliott]

Also may be useful to see the exact command you’re typing now.

[dureal99d]

@Tom-Elliott sudo mount 192.168.1.109:/opt/bootimgs/fedora /mnt

[dureal99d]

@Tom-Elliott no, i didnt know i had to, but will try it

[dureal99d]

@Tom-Elliott said in How to pxe boot cent os 7:

exportfs -a

exportfs: /etc/exports [3]: Neither ‘subtree_check’ or ‘no_subtree_check’ specified for export “*:/var/www/fog/service/ipxe”.
Assuming default behaviour (‘no_subtree_check’).
NOTE: this default has changed since nfs-utils version 1.0.x

exportfs: /etc/exports [4]: Neither ‘subtree_check’ or ‘no_subtree_check’ specified for export “*:/opt/bootimgs/fedora”.
Assuming default behaviour (‘no_subtree_check’).
NOTE: this default has changed since nfs-utils version 1.0.x

[Tom Elliott]

@dureal99d those messages are fine
Any luck mounting now?

[dureal99d]

@Tom-Elliott said in How to pxe boot cent os 7:

@dureal99d those messages are fine
Any luck mounting now?

No luck

[Tom Elliott]

@dureal99d can you post your exports file again?

[dureal99d]

@Tom-Elliott said in How to pxe boot cent os 7:

@dureal99d can you post your exports file again?

/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
/var/www/fog/service/ipxe *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/opt/bootimgs *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)

[Tom Elliott]

@dureal99d That’s the issue you can’t mount a full path. Only mount up to the bootimgs folder.

Instead of:
mount 192.168.1.109:/opt/bootimgs/fedora /mnt use :
mount 192.168.1.109:/opt/bootimgs /mnt

[dureal99d]

This post is deleted!

[dureal99d]

@Tom-Elliott said in How to pxe boot cent os 7:

mount 192.168.1.109:/opt/bootimgs /mnt

mount: wrong fs type, bad option, bad superblock on 192.168.1.109:/opt/bootimgs,
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.

[Tom Elliott]

@dureal99d and output of dmesg | tail -20?

[dureal99d]

@Tom-Elliott said in How to pxe boot cent os 7:

dmesg | tail -20

[ 8605.032191] nfsd: last server has exited, flushing export cache
[ 8605.178847] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 8605.179097] NFSD: starting 90-second grace period (net ffffffff81ef3ec0)
[177245.456195] nfsd: last server has exited, flushing export cache
[177245.571541] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[177245.571572] NFSD: starting 90-second grace period (net ffffffff81ef3ec0)
[504820.256179] nfsd: last server has exited, flushing export cache
[504820.379183] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[504820.379211] NFSD: starting 90-second grace period (net ffffffff81ef3ec0)
[505766.396169] nfsd: last server has exited, flushing export cache
[505766.443252] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[505766.443281] NFSD: starting 90-second grace period (net ffffffff81ef3ec0)
[512189.424200] nfsd: last server has exited, flushing export cache
[512189.469462] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[512189.469507] NFSD: starting 90-second grace period (net ffffffff81ef3ec0)
[512652.019883] FS-Cache: Loaded
[512652.045276] FS-Cache: Netfs ‘nfs’ registered for caching
[512652.087294] NFS: Registering the id_resolver key type
[512652.087309] Key type id_resolver registered
[512652.087310] Key type id_legacy registered