@greventlv said in How do I FOG my FOG server?:

I know that’s something that I can do, but I have a bunch of other stuff on the server and during production breakdowns, it would be a lot faster to hit a few buttons and get everything back to the original state without having to deal with a new install, restore and etc.

Then really you should build a fog server in a VM and just snapshot it. That’s literally ‘a single button click’ to restore from a past state.

@m-fitzgerald Good to hear this fixed the issue for you. Though from my point of view it’s only partly solved. If you capture the image again you will need to edit that file again. So question remains why it does not recognize your boot partition as such. Usually this happens if Windows is not installed as English version or partition labels have been modified by hand. As I said, take a screen shot of the disk management view in Windows and post here. I am fairly sure we can figure out why that is.

Follow on question though. How do I edit the order of Storage Nodes?

We try to keep topics separate. Please open a new thread for this! Won’t answer here.

Okay so I finally figured out the issue. Whenever this error came up the storage didn’t show up on the main page. Once I was able to get the storage node figured out and the pie chart came up on the main page I was able to create a snapin just fine.

@george1421 GEORGE THANK YOU SO MUCH!!! YOU HELPED SO MUCH

If there are not important files on the hard drive, you can repartition it. During partitioning a hard disk, you can select partition table type, partition numbers, sizes, etc. After that, you’ll be able to get a valid partition table. If you do not try repartitioning, you can try rebuilding MBR using an installation disc. You can refer steps here to rebuild MBR manually:eassos.com/how-to/how-to-fix-invalid-partition-table.php

Thanks Sebastian,

I have read it a while ago, but looks like I missed your edits…
Unfortunately I just lost access to these servers just now as I moved a company (last day), as a workaround, we just changed the bios to boot from local hard drive after we fogged them.

Thanks for your help,

Aviram

Thanks Guys, I can confirm its working now.

Aviram

@palermo Deploy that disk image file (d1p1.img) to either real hardware or a virtual machine. Understand FOG is a disk imaging tool not a live boot or VDI environment.

@sebastian-roth

thank you
dnsmasg install
I solved the problem

@sebastian-roth Unfortunately it has been lower on my priority list right now, we are undergoing a lot of changes as a business right now. I’ll update ASAP.

@zingaro Please post the PCI IDs as a reference as well.

Did you try my suggestion on using a dump mini switch?

Other than that you could try different iPXE binaries like undionly.kkpxe (note the double k), ipxe.pxe, realtek.kpxe or realtek.kkpxe

The other question is, why not going UEFI all the way?

@sebastian-roth Thank you and everyone replied for help and patience. That someone who messed up is me 🙂 This is a test server so going to be far more efficient to reload.

Thanks again everyone.

@wayne-workman Correct… Thanks for your help

@sunks if it happens again like this, come back and tell us, try to use this same thread.

OK. Will do. Thanks!

Typical newbie mistake. I’ve done my best to spread this knowledge all over the wiki:
https://wiki.fogproject.org/wiki/index.php?title=Ubuntu_16.04_Server#Settings

set a username, recommended name is YOUR first name, or “admin”. Do not use “fog”!

And
https://wiki.fogproject.org/wiki/index.php?title=Password_Central#Local_.22fog.22_user

Please do not use the local “fog” user account on the server to do back-end work. Create another account and use that.

It’s other places too. I don’t know what it’s about but I think the force compels the human soul to set the local account name as fog

@sebastian-roth I never had the option to reset encryption on this host and it wasn’t working for all hosts.

@arkhad said in Failed to get an IP via DHCP!:

I installed 1.44 again and tried to register a host and it worked this time.

Because reinstalling fog 1.4.4 replaced the kernel and inits with the correct versions for 1.4.4