Posts made by Fog_Newb

@Sebastian-Roth

Also I just updated to 1.58 it went smoothly. I was worried when it forced a password on mysql, I screen capped it and so far everything is working.

This kind of thing is so much more fun compared to Windows stuff.

@Sebastian-Roth

Oh. Got it. That makes sense.

@Sebastian-Roth

This is very cool. The image finished deploying and it can boots up Windows but it would not load the desktop it goes to repair. But this could be because there is a huge difference in hardware?

Perhaps a feature could be added to convert back and forth from 4k to 512 in the web interface. The one thing I was curious about is why a 250GB drive would be needed since the image is around 60GB

@Sebastian-Roth said in Unable to restore 4k cluster size NVME:
Cool! I changed d1.partitions to what you posted and it was able to deploy the image onto a VM with a 512 sector drive.

d1.partitions.txt @Sebastian-Roth said in Unable to restore 4k cluster size NVME:

I have since delete the BIGPIG image. Here is the one from TEST. This image was captured from the 4k block NVME

d1.partitions.txt

@Reuban1219

Yes you can run the DHCP server on the same FOG// Debian machine. I am new to Linux and don’t know much about setting up a DHCP server on that. I used Windows for the DHCP server.

Imaging with FOG doesn’t require the internet. The PC’s have to be on the same network and you need a DHCP server of some type that allows you to add option 66 and 67 for boot file name and boot file server.

@Sebastian-Roth

Thanks. Do you know where I can add the -C option to skip the disk size check?

@Sebastian-Roth

I have been searching for information on how to create a 4k sector virtual drive in VMWARE workstation and ESXi 6.7 but I can’t find it. Any ideas?

@Sebastian-Roth

Hello,

They are on separate SSDs. Windows 10 on it’s own SSD with its own EFI etc etc. And mac OS on its own SSD with it’s own EFI etc etc.

Oh damn, how could I have missed Host Primary Disk in the settings. So I would just put something like “/dev/sdx”?

@Sebastian-Roth

It looks like what went wrong is… When i tried to deploy an image that was captured from an NVME with a 4k block / sector size on a pc with a 512 block /sector size it gets confused about the size of the image. Like in the screen shot, it shows the image is 300+GB but it was really 30 something GB.

Also, trying to deploy an image captured from a 512 sector sized drive to the 4k sector NVME … it will deploy onto the drive but windows won’t boot on it.

So I just figured you can’t image between drives with different sector sizes.

I had converted the drive to 4k back in the day so Sierra could run native on it.

I now want to go back to 512 but unfortunately I didn’t think it through prior to reloading the OS from scratch last night.

uh… never mind please delete

So fog has been working great until I tried to deploy a win 10 image captured from my NVME. The NVME was converted to 4k cluster size from back in the day when Sierra supported no other on NVME.

This is what happens when I try to deploy the captured image onto a UEFI based VM.

Then this

I am thinking about converting the drive back to 512 k cluster…

You have to use FOG version 1.6.

https://forums.fogproject.org/topic/14153/fog-version-1-6-on-ubuntu-19-10-so-close/2?_=1581723908061

I was able to get it working on 19.10 to where I could log into the web admin but bit was unusable. Navigating the web interface was not possible.

Hello @Sebastian-Roth ,

The Fog dashboard indicates “Your version of FOG is up to date.
You’re running the latest stable version: 1.5.7” I am using Ubuntu 18.04 LTS server with all updates.

This may sound dumb but I am not sure how to tell FOG which drive to capture. If I create a new “Windows 10 image, Single Disk Re-sizable, Everything” in FOG, then set my laptop host to capture it it will capture the Windows 10 drive.

If I create a new “Apple Mac OS image, Single Disk Re-sizable, Everything” in FOG, then set my laptop host to capture it it will give this error

If I create a new “Other image, Single Disk Re sizable, Everything” in FOG, then set my laptop host to capture it it will give this error

/dev/sda is the Windows 10 drive. I don’t know how to have it capture the other one

Thank you

Woops EDIT.

My DHCP server IP is different from my router too.

During the install when you are prompted with -

Would you like to setup a router address for the DHCP Server? [Y/n]
Choose: Y and enter the IP Address of your router.

and

Would you like to use the FOG Server for DHCP Service? [y/N]
Choose: N

You can edit the fog settings after the install. They are located in /fog/.fogsettings

In a way, Fog doesn’t really need to know where you DHCP server is but the DHCP server needs to know where FOG is located. Scope options 66 and 67

The .fogsettings doesn’t contain any info about your DHCP server

Hello,

I have been trying to capture the Hackintosh drive on my laptop but it fails every time. I have tried setting the image to Apple Mac Os and Other.

The method I use for Hackintosh is Clover Boot loader which resides in a fat32 EFI partition along with the 3rd party kernel extensions etc etc and the other partition is HFS Plus with the OS on it.

Is there some additional information I could provide that could make this happen? It is probably just a small tweak.

Thanks

@Wayne-Workman said in Doing this backwards. Is there any drawback?:

You’re welcome to update the article if you’d like

I would be happy to.

@Tom-Elliott

Nice, it is working now.

There was a slight blip where it got stuck at

Downloading kernel, init and fog-client binaries…

So I ‘quit’ the install removed user fogproject and ran the install again.

I was able to update the database schema, continue the install and login.

New interface looks slick!

@Sebastian-Roth
Sorry about the 16. It was late

I used these steps to install Fog

sudo -i
git clone https://github.com/FOGProject/fogproject
cd fogproject
git checkout working-1.6
cd bin
./installfog.sh

I will try git pull

@Tom-Elliott

So… the newest Fog has been updated since I originally posted

working-1.6
Updated 10 hours ago by mastacontrola
Cool

Gonna spin up 19.10 in a VM and see what happens.