Posts made by Fog_Newb

@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

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.

Hello,

I decided to try setting up FOG on the new Ubuntu. After failing with the latest stable release I read it didn’t work because non LTS versions didn’t do PHP or something and to use version 1.6.

So I did another fresh install of 19.10 and installed version 1.6. This time I made it past “Stopping web service…Failed!”

I made it to almost the end where I need to update the database schema

but when I go to 192.x.x.x/fog/management

This is displayed

"{“error”:"An SQL error occurred: SQLSTATE[3D000]: Invalid catalog name: 1046 No database selectedSQL: SELECT hostID,hostID,hostName,hostName,hostDesc,hostIP,hostImage,hostImage,hostBuilding,hostCreateDate,hostLastDeploy,hostCreateBy,hostADUser,hostProductKey,hostPrinterLevel,hostKernelArgs,hostKernel,hostDevice,hostInit,hostPending,hostPingCode,hostExitBios,hostExitEfi,hostEnforce,imageName,hmMAC\n FROM hosts\n LEFT OUTER JOIN images\n ON hosts.hostImage = images.imageID\n LEFT JOIN hostMAC\n ON hosts.hostID = hostMAC.hmHostID\n AND hostMAC.hmPrimary = ‘1’\n WHERE hostPending = ‘1’\n ORDER BY hostName ASC\n “}”

No idea. I can always go back to 18.04 but wanted to try out this new one.

Oh yes, that is most likely what it is. It is when you click the wrench at the top right in the web interface.

FOG Version Information
404 Not Found

link text

I am not sure what to check. I am new to linux. It is running on Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-74-generic x86_64)

I know it displayed at some point. Perhaps when I updated Linux the problem started?

Thanks. Issue solved

https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

Hello,

Instead of adding the additional vendor classes for UEFI boot (Windows DHCP). I instead set the default bootfile to ipxe.efi and added a policy for PXEClient:Arch:00000 to use undionly.kpxe. So far it is working fine. Is there a reason the instructions in the link do it the other way?

Thanks all. It makes sense why it was happening now.

@Quazz

Yes, it was a legacy 10 install that was converted to EFI.

SOLVED sort of. I had to make the VM disk larger. The image is roughly 70GB. After increasing the disk size from 100GB to 130GB on the VM I was able to deploy the image.

Hello,

I am trying to deploy a Windows 10, single disk re-sizable, everything image. The image was captured from a Windows 10 UEFI based laptop.

This is the first UEFI image I captured and I am trying to deploy it on a UEFI VM before I deploy it on metal. Legacy images work fine. I searched around but I am not sure what to check. Any advice would be appreciated.

UPDATE: Here is what is in d1.partitions for that image

d1.minimum.partitons

d1.fixed_size_partitions