@Tom-Elliott Any update on this?
Thanks,
Hongyun

But whenever I add CLAB/ in front of the image name, it will automatically remove /, for example, if my image name is ubuntu16, if I enter CLAB/ubuntu16 in the image name, it will automatically changed to CLABubuntu16.

The old version I mean 1.2.0.
The server OS is Red Hat Enterprise 6.8, kernel 2.6.32

CLAB is just a sub folder of /images, I used to create multiple mount points so when I upload images, it will be saved in the sub folders instead of the /images folder.

If you have better solution instead of using multiple storage nodes, it should be fine for me too. Otherwise, I guess I will have to live with it.

In the old version, I can create new storage nodes by creating a subfolder in /images folder, so I can separate my FOG images for different computer labs. But ever since I upgraded FOG to the latest 1.3.4 version, it no longer works with the subfolder setting, I can only upload the images to the root /images folder.

Here is my /etc/exports file:
/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)
/images/CLAB *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/CLAB/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

And I have .mntcheck file under /images/CLAB/dev folder, but at the end of the upload process, it will say it couldn’t find the uploaded file, and I noticed that the uploaded file is actually saved under /images/dev instead of /images/CLAB/dev

I hope this problem can be resolved since I have 60+ image files, it will be more organized if I can put them in different subfolders. And this used to work with the old version…

I can boot from PXE without a problem, and I can upload an image ok, but I couldn’t upload the hardware inventory. Don’t see any error message, it just won’t do it. The task will remain as an active task. How can I troubleshoot this problem?

Thanks,
Hongyun

That was easy, Thanks!!!

I added a systemrescue CD to the iPXE boot menu through FOG Configuration -> Advanced Configuration Options.

And it works fine. But now I want to make this advanced menu password protected. In the old version, I can add MENU PASSWORD in PXE boot menu. But I’m not very familiar with iPXE menu, can anyone tell me how to add password to an iPXE menu item?

Thanks,
Hongyun

You need to add the subfolder and the subfolder/dev to the /etc/exports file, and then run exportfs -av

Ha! Thank you Ianabc, I switched to use Single Disk (Resizable), and it keeps the swap partition’s UUID, which means it’s working!!!
Have a good weekend!

Will sigle disk resizable work with Linux & dual boot systems?

Yes, I upload the image with 1.2.0, but the image type is Multiple Partition Image - Single Disk (Not Resizable).

[root@foggy henn205mageia4]# cat d1.partitions

partition table of /dev/sda

unit: sectors

/dev/sda1 : start= 2048, size=960572497, Id=83, bootable
/dev/sda2 : start=960577506, size= 16190559, Id= 5
/dev/sda3 : start= 0, size= 0, Id= 0
/dev/sda4 : start= 0, size= 0, Id= 0
/dev/sda5 : start=960577536, size= 16190529, Id=82

[root@foggy henn205mageia4]# ls -la
total 1659936
drwxrwxrwx. 2 root root 4096 Jul 25 10:29 .
drwxrwxrwx. 39 fog fog 4096 Jul 25 11:56 …
-rwxrwxrwx. 1 root root 0 Jul 25 10:16 d1.has_grub
-rwxrwxrwx. 1 root root 1048576 Jul 25 10:16 d1.mbr
-rwxrwxrwx. 1 root root 1698702304 Jul 25 10:29 d1p1.img
-rwxrwxrwx. 1 root root 1131 Jul 25 10:29 d1p2.img
-rwxrwxrwx. 1 root root 310 Jul 25 10:16 d1.partitions

That’s everything I got on the server image folder.

[quote=“ianabc, post: 34153, member: 24548”]UUIDs work for ext3 and ext4 filesystems because the UUID is part of the filesystem itself, it is written into the superblock. Since Fog 1.2.0 fog also seems to allow UUIDs in /etc/fstab for swap partitions. For other filesystems, I’m not sure, I haven’t noticed any problems with xfs, but I haven’t looked too close. Incidentally, there are some other reasons to use ext4 - fog 1.2.0 can resize ext4 filesystems automatically![/quote]
But I think the problem now is that after downloading the FOG image, the swap partition’s UUID got changed, even when I download the image to the same computer where I uploaded the image from. Our instructor prefer the Mageia 4.1, I’m still trying to make this work with FOG, a month left before the term starts, feeling the pressure now:(

I think it has something to do with the OS. I tried reupload a working image and then download it again, it still works. But this Mageia 4.1 OS doesn’t work properly. I will try to reinstall it with ext3 partition to see if it works.

Yes, I reuploaded the image after the upgrade yesterday, and redeployed the computer today.

Hi Tom,
I tried the new version, result is the same any other suggestions?

Thanks,
Hongyun

I found each time after I upgrade FOG, the /etc/exports file got overwritten, I have to re-enter all my storage nodes again to make it work. Is it possible you can keep that file in your next version? Just some thoughts

I just upgrade the FOG server, you have a 1.2.0 now? That was fast, I will try the new version. Thanks!

The newest version 1.1.2