You can not NFS share an NFS share.
I’m afraid I thought so.
But I do not have the possibility to install a Storage Node there.
Is there a possible secound way?
Could someone please explain to me why does NFS daisy chain mount does not work?
10.1.1.1:/myimages /nfsmount nfs defaults 0 0
cp -r /images/. /nfsmount- Copy all files (hidden also)
/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) /nfsmount *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=2) /nfsmount/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=3)
fsidat the end of the line must be incremented
shotmount -e 127.0.01- check NFS mount
/nfsmount/dev * /nfsmount * /images/dev * /images *
Storage Node Name = NFSmount Storage Node Description = my secound storage IP Address = 10.10.10.10 Web root = /fog Max Clients = 10 Is Master Node = [x] Replication Bandwidth (Kbps) Storage Group = NFSgroup Image Path = /nfsmount/ FTP Path = /nfsmount/ Snapin Path = /opt/fog/snapins/ SSL Path = /opt/fog/snapins/ssl/ Bitrate Rexmit Hello Interval Interface = eth0 Is Enabled = [x] Is Graph Enabled = [x] Management Username = fogproject Management Password = ****** (copy it from default Storage)
Image Name = nfsExternTest Image Description Storage Group = nfsgroup Operating System = Windows 10 Image Path = /nfsmount/nfsExternTest (it refresh automatic after you created it, just create and check it again) ...
… but when i change to the default Storage… everything is fine.
Why does NFS daisy chain mount does not work or have i an error in my configuration.
Thanks for your time.
PS: For more information: adding-additional-image-storage-space-to-fog-server
I solved the problem. In the end, the last thing i forgot was to change the ip of the fog server to the fqdn in the ipxe file.
Could you please explain in more detail, which ipxe file do you mean?
/opt/fog/.fogsettings first line?
We also needed to set the WEB HOST setting in the FOG Configuration to the FQDN.
My problem is that after my CA was changed and ipxe was rebuild; iPXE still trying to connect to the bare IP not to the FQDN.
I’ve could adjust LDAP login, and allow only admins, but I’ve some students who would also like to work with it.
So I’m allowing admins (admin role) and students (mobile role) to access.
But not all students should have full access.
As I listened, there is a new idea with the new version 1.6 on this subject.
Hopefully this will solve my problem.
I’m using LDAP with Access Control. LDAP -> User Filter = 991
I can see all LDAP users in the list and can assign them to the right role.
When new users logging in for the first time, they have admin status. (undefined role)
Is there a way to initially assign them to a “guest” role? And promote them by hand afterwards?
Thank you very much, thats all i need to know.
hat is your dhcp server?
Thank for your fast answer. @george1421
Yeah that’s a bummer. Also found this article.
But as you said, i will boot PXE in legacy and use uefi.
0000 8e 74 ff fb b3 07 b8 ca 3a a4 3a f6 08 00 45 00 .t…:.:…E.
0010 00 48 70 a3 00 00 40 11 86 d7 8d 2d b4 57 8d 2d .Hp…@…-.W.-
0020 b4 78 04 3b 00 45 00 34 3e 69 00 01 75 6e 64 69 .x.;.E.4>i…undi
0030 6f 6e 6c 79 2e 6b 70 78 65 ff 00 6f 63 74 65 74 only.kpxe…octet
0040 00 74 73 69 7a 65 00 30 00 62 6c 6b 73 69 7a 65 .tsize.0.blksize
0050 00 31 34 36 38 00 .1468.
thats the last two character in binary:
i found a strange behaviour that is nowhere (at least i found nothing) noticed.
I’ve got a Dell Optiplex 7010 which has two boot option for PXE; UEFI or Legacy.
When booting with legacy, the bootfile “undionly.kpxe” will be send over from dhcp which is then searched on tftp server. Perfect.
UEFI bootfile “ipxe.efi”
The problem is: dhcp server send the right file, but the tftp-server got a wrong request:
somehow “�” get into the bootfilename.
I have now checked the dhcp setting for the third time. But everyting looks fine.
Infoblox is used as dhcp.
I then checked with Wireshark what the DHCP really sends.
Could it be that Dell got a firmware bug for uefi booting?
I testet now 3 different Dell modells, everytime the same result.
I hope I made a mistake somewhere, otherwise…
Bonus question: I am not able to start VirtualBox in UEFI PXE mode
I installed the expansion pack and also checked “efi”.
But PXE does not boot. Does anyone know what the problem is here?
-> Not possible Link
-> second “proof” Link
Thanks for your time.
@EZY4 I think we both have different problems.
I would suggest that you open a new thread on this.
As a tip: Install VirtualBox + ExtensionPack and set up the network boot only.
VirtualBox has iPXE, which gives you more information.
Furthermore you can use wireshark to check what exactly your machine receives from the dhcp-server.
@george1421 Good to know. Thanks for the information and help!