PXE Menu Parameters for Diskless NFS?
-
Hi Team and People,
I am following parts of what are now several tutorials to serve a diskless Ubuntu over FOG. Looking back it would have been easier not to involve FOG. Oh well, glad to know it, want to keep it!So I am on my last step, the diskless install is ready and exported to NFS, it has its fstab and everything set up to work properly. I just need to get it to chainload.
I’ve modified pxelinux.cfg/default and the changes never, ever show up on the menu I get when booting to undionly.kkpxe. So I’ve started using the Dashboard and the changes do show up right away.
Now that I have to enter my parameters in the Dashboard, I suspect I could be formatting it wrong. So I came here to ask:
Can anyone see an obvious problem with this?
Parameters:
kernel vmlinuz-5.0.0-21-lowlatency root=/nfs initrd initrd.img-5.0.0-21-lowlatency nfsroot=192.168.1.2/nfs/private/pxe/athens,rw ip=dhcp rw
Boot Options: none
-
Its sad that you find its difficult to use FOG for diskless booting. While its not the focus or intent of The FOG Project there are ways you can use the opensource nature of FOG to netboot ubuntu: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/12
-
@smellyonionman In regards to your boot options, FOG uses iPXE as a boot loader and not syslinux. I can tell you from my tutorial that you need to use the netboot version of the ubuntu kernel and inits or it wont boot over the network.
For your nfsroot, you need to make sure that you have the nfs share configured correctly. FOG does configure everything correctly for netbooting even though its intent is system imaging.
With that said you surely do not need to use FOG to make a netboot envrionment. FOG just nicely installs all of the bits (services) you need for netbooting.
-
@george1421
Thanks for the link. I won’t deny I am new to most of the topics involved. It’s hard to find up-to-date tutorials outside of man pages, so having someone actually post a link they trust is a big help right now. -
nfs addresses have to be written like
192.168.1.2:/nfs
(notice the:
)