Posts made by quinniedid

@george1421 I have my fog server configured with an FQDN instead of IP addresses as we have had to change our IP a few times. So ${fog-ip} is not an actual IP. Also, all computers/VM’s in our network our UEFI configured. I just find it interesting that Clonezilla will work but not this particular version of Gparted.

I changed the files to the following versions and the associated results:

0.33.0-2-i686 - Won't even boot
0.33.0-2-AMD64 - Will boot but crashes later due to the FQDN not resolving for some reason, if IP specified on fetch booted no problem
0.33.0-1-AMD64 - Will boot but crashes later due to the FQDN not resolving for some reason
0.32.0-1-AMD64 - Will boot and works with the FQDN no problem!!! :)

This is the iPXE parameters I am using:

kernel tftp://${fog-ip}/gparted/vmlinuz
initrd tftp://${fog-ip}/gparted/initrd.img
imgargs vmlinuz initrd=initrd.img boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=tftp://${fog-ip}/gparted/filesystem.squashfs
boot || goto MENU

@george1421 I am using the 0.33.0 AMD64. I think I am going to download the previous version and test. I wonder if PXE booting is an issue in this version.

@Sebastian-Roth I did find that it works with an IP address in the fetch portion of the commands.

hosts: files dns

@Sebastian-Roth The boot log is reporting a bad address to the FQDN of our server. Which is strange as within the same command-line I can nslookup the FQDN and get back the associated IP. I can ping the IP address but I cannot ping with the FQDN. Giving me the same error as bad address.

@george1421 What I find interesting is that I can now get Clonezilla to work on the UEFI VM but NOT on a physical box…
You would think that Gparted an Clonezilla would be somewhat the same.

kernel tftp://${fog-ip}/clonezilla/vmlinuz
initrd tftp://${fog-ip}/clonezilla/initrd.img
imgargs vmlinuz initrd=initrd.img boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=tftp://${fog-ip}/clonezilla/filesystem.squashfs
boot

@george1421 I got a lot closer! But I am now getting a failed to boot…

@Tom-Elliott Also tried these:

kernel tftp://${fog-ip}/gparted/vmlinuz vmlinuz initrd=initrd.img boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=tftp://${fog-ip}/gparted/filesystem.squashfs
initrd tftp://${fog-ip}/gparted/initrd.img
boot

This seemed to get further

kernel tftp://${fog-ip}/gparted/vmlinuz initrd=initrd.img boot=live union=overlay username=user config components quiet noswap toram=filesystem.squashfs ip= net.ifnames=0 nosplash
initrd tftp://${fog-ip}/gparted/initrd.img
initrd tftp://${fog-ip}/gparted/filesystem.squashfs
boot

@george1421 This is what I have configured:

kernel tftp://${fog-ip}/gparted/vmlinuz
initrd tftp://${fog-ip}/gparted/initrd.img
initrd tftp://${fog-ip}/gparted/filesystem.squashfs
imgargs initrd=initrd.img boot=live union=overlay username=user config components quiet noswap toram=filesystem.squashfs ip= net.ifnames=0 nosplash

@george1421 This is what I am getting now:

@george1421

kernel tftp://${fog-ip}/gparted/vmlinuz 
initrd tftp://${fog-ip}/gparted/initrd.img
imgargs  initrd=initrd.img boot=live config components union=overlay username=user noswap noeject vga=788 fetch=tftp://${fog-ip}/gparted/filesystem.squashfs
boot

I see the files download but this is the screen that I get:

@Sebastian-Roth I did not get it working. I have tried some different things but it fails to load.

@Sebastian-Roth I have had this same issue in our environment but it has been intermittent. Sometimes the resize works and other times it doesn’t. We are running 1.5.6.

@Sebastian-Roth It has not been resolved.

@Jonathan-Cool I find it very interesting that a SYSTEM account will work on Windows 7 but not Windows 10. One thing I would like to see is doing the same thing with PSExec running as the SYSTEM account and once you have that command window open change the directory to where you usually have the drivers dumped to. Run the xcopy from the NAS. I would be curious to see the behavior difference between Windows 7 and Windows 10.

Also, can you capture a screenshot of the security permissions of the folder specially on Windows 10 that the drivers are dropped into? Something like this:

@Jonathan-Cool Is your NAS also connected or configured to your samba domain?

@Sebastian-Roth Great point! It has been added.

I have been trying to get Gparted to work from FOG for the past week. I feel like there is something that I am simply missing.

I can get Gparted to boot but when it boots it is giving me this error:

Am I missing a config file or something? It seems that it is not finding any drives? I know that Gparted works because if I plug the USB with the exact same live image it works no problem on the device.

Here is what I have defined for my PXE menu settings:

kernel http://${fog-ip}/fog/gparted/vmlinuz initrd http://${fog-ip}/fog/gparted/initrd.img boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=http://${fog-ip}/fog/gparted/filesystem.squashfs
boot

Any advice would be greatly appreciated.

We are having an issue with settings in a group that when a host is added to that group the group settings are not being applied to the host. In fact when you go and edit the group again after adding a new host the settings are now gone. Resulting in the behavior that the plugin is not working like it used to.

Any ideas on why this is happening or how to resolve it?

Okay. That makes a lot more sense. It is working just fine. I appreciate the clarification.

Is there any documentation on rule creation? I only want the user to have access to specific hosts and groups?

@Fernando-Gietz

When I add the optimus user I see this in the table:

The issue is that optimus still acts like a full admin even though no rules are associated.

I have removed the plugin and reinstalled it and I am continuing to have the same behavior… Any ideas?

@Fernando-Gietz

Is it because of the spaces in the role name? How can I verify the database to ensure it is not corrupted?