Topics created by sjensen

@tom-elliott

Are there any plans to make a windows/mac/linux app that would allow FOG images to be mounted and read allowing the user to copy files from an image?

Thanks

@sjensen FOG 1.5.0 is years old and I can’t remember if multicast worked perfectly fine in that version or if there was an itch with that in 1.5.0.

@sjensen Just as a precaution - make sure you have a backup copy of all your important data from this system. I won’t be made liable for any steps you take!

So let’s take a look at the whole process of resizing which involves several “layers” - see below.

In the output of pvscan we see that the physical volume on /dev/sda3 is 400 GB in size and has 100 GB free/not in use. So gparted has extended the partition but not the physical volume (in LVM terms). To do that run:

pvresize /dev/sda3

The next step is to tell the logical volume (LV) to use that new space:

lvextend -l+100%FREE /dev/FOGServer-vg/root

As a final step you need to extend the filesystem.

resize2fs /dev/FOGserver-vg/root

Finally check the partition size in the output of df -h.

@george1421 said in Issues with inventory and uploading image:

That isn’t the response from the file command I expected.

Some older Linux systems do not provide the great output using file that we see with up to date systems.

As the OP reported the issue is solved, we don’t need to worry.

@sjensen Yes, seems like those devices can PXE boot: https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/net.md

You’d need to install your FOG server using a command line switch to enable installation of ARM kernels: ./installfog.sh -A

If PXE booting is not working you might still be able to boot those using the USB boot method.

Your dhcp server needs to send the boot file name ipxe.efi for uefi based systems and undionly.kpxe for bios based systems.

If this is just a one off system you can manage dhcp option 67 by hand. If you want it to automatically adjust based on the target computer there are instructions here as long as your dhcp server is windows 2012 or newer or linux based: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

@Sebastian-Roth said in Unallocated space:

df -h

Looks like i’m good to go. Thanks very much for all your help. I will save the commands for future reference.

@sjensen said in Selected boot device failed:

So basically i need to try the different bios setups combined with the different binaries in order to capture an Image of this Dell XPS13?

As I said, it’s probably a lot easier than debugging why undionly.kpxe doesn’t work at all and undionly.kkpxe has transfer issues…

So it’s all about the combination of Laptop, firmware and USB dongle. Here is a forum thread where someone was able to PXE boot in BIOS legacy (undionly.kpxe) with a USB dongle also based on the RTL8153 network chip. But as I said, it’s always a bit different as soon as you change one component in the equation.

And here Dell is saying that “The XPS 13 with BIOS A05 or higher, supports PXE boot with LAN7500 chipset based USB NICs.”

Just want to show you that there are many different ways and people were able to PXE boot the XPS13 but you can only know for sure when you test with the components you have at hand.

Edit: Hope this is not causing too much confusion. Just wanted to show you that there are different solutions out there and trying to do plain UEFI might be the easiest one or at least worth a try. Here is a thread where the same issue as yours is described and was solved by switching to UEFI.

@sjensen said in Issues with disk in an unsafe state:

I got the update installed and i am uploading an image from the Samsung laptop now.

Great to see that you’re up and running. I’ll mark this solved then. Please open new threads (yes several if you like) in case you hit another problem. It’s best to not mix up a dozen or so questions in one thread.

@wayne-workman said in Problems creating an image:

Bitlocker?

Could be just as well.

@sjensen You might want to try setting this image to Single Disk - All partitions (non-resizable), just to see if that works out of the box.

@sjensen said in Moving FOG virtual server to a new server.:

@Wayne-Workman is there a specific process you used? Did you export the VM?

No, I migrated. This is a Hyper-V feature.

@Wayne-Workman Wayne thank you for the reply. I used the that Junkhacker posted. It worked very.
https://blog.vbonhomme.fr/extend-a-lvm-partition-after-increasing-its-virtual-disk-on-virtualbox/

This isn’t done yet but it will likely help you:
https://wiki.fogproject.org/wiki/index.php?title=Surface_Pro

@sjensen

Then as Wayne said, make a new thread for it, sounds like your install is… special. Sudo being denied permission is silly.

@sjensen i tried sudo at the start of the string. I am getting could not open lock file /var/lib/dpkg/lock - open (13: permission denied)