@finvader Yes, set your boot order in all the machine’s firmware to Network First, HDD second. By default, if there are no jobs in FOG for said machine, it’s sent to the HDD to boot.

This “sending to hdd to boot” is controlled by the exit type in the FOG Web interface. The default can be set in FOG Settings. The setting can be altered per-host or mass-applied via Groups. The default is SANBOOT and works on most things, for most of the ones SANBOOT doesn’t work on, GRUB usually works. And then there are other options for the really difficult boxes.

I set the boot order in the firmware for 500 systems at my old job. I didn’t do it all at once, I modified the machines one by one as I needed to image them. Over the course of a year and a half, I got them all.

Of course I was also planning on modifying all new machines to boot to the network first as we received them - but then I got a new job.

I’m sorry your post isn’t clear. This is what I think I read.

“We had fog setup in a test environment running on vmware workstation 8”

“We setup a new FOG server with the same settings of the test environment.”

The “we have another server for pxe boot” and “paste into my new fog dhcp server” are confusing.

I have some questions back to you.

I your test fog server (running on vmware workstation) on the same subnet (network) as your new FOG server? On your network where your new fog server is installed, does that network already have a dhcp server installed?

We really need to know about your network to be able to help you.
On the network where new fog server is installed is FOG acting as the dhcp and dns servers?

in the interim, you could always setup rsync until toms worked his magic :-)…

Good news this morning I rebooted the server gave it another try and it all worked.

Tom, Wayne and George, THANK YOU!!!

It’s all good now. And I learned a lot. And archiving this on my end with my notes. Until next time.

I apologize for bugging so much… 😞

@fry_p Your current efforts has not gone to waste. When the other method is proven, you will just move your patched fog.mag.reg to the fog server postinits directory and add in the postinit scripts to copy it over each time. What you have created to day will work just fine moving forward, you just won’t have to unpack and repack the inits after each change.

@darkrelic said in installing now everthing is updated Failed!:

@george1421 that solution works thank you

(Lucky guesser) == George 😉

@george1421

Thanks ill create a checkpoint before i do the upgrade any way but ill give it a go today.

thanks

@Junkhacker Thanks!! I do a lot of monkey-see-monkey-do stuff. So I assume I did what others did to make this work. I applied the chmod -R 777 stuff as well. I checked the NFS services and it’s running.

I can’t say I am troubleshooting because I am applying “fixes” I found through this tread. i know, I know, that’s scary.

I will follow your advice and create a new thread. I suspect some will point me to this thread for resolution but let’s see what happens.

Thank you Tom! Good to know! It is okay for me 🙂

@Wayne-Workman I suspect this problem happens during “reinstall”.

as a root user I can get in but I need to enter root before the command

also from 1.3.0 to 1.3.5

Hi Andreas thanks

Is there a Tutorial somewhere. At least i want to clone into VirtualBox, so i only need a vdi-file from the img-file.

@Tom-Elliott
No, no need an intermediate switch. If I turn-off spanning tree, yes I need to put a intermediate switch, but if it’s on, it’s working.

@riko with this error, it appears to be a software error on the target computer’s hard drive. Clonezilla and FOG uses the same disk cloning engine called partclone. I found this answer on the clonezilla site: http://drbl.org/faq/fine-print.php?path=./2_System/108_bitmap_free_count_err.faq#108_bitmap_free_count_err.faq

It says:
"You should make sure the file system integrity is OK before you save it as an image, i.e. the file system is unmounted cleanly. If you want to check and repair the file system, you can run “fsck” on GNU/Linux or ‘chkdsk /f’, ‘chkdsk /p /r’ on MS Windows. For GNU/Linux file system, e.g. ext4, reiserfs, you can also check option “-fsck-src-part-y” when you save an image. "

FOG will only replicate with storage nodes in its group. Each group must have a master FOG node, and then X number of storage nodes.

If your storage node is in a different storage group than your master FOG node no replication will happen.

Use the replication controls on the images to control what gets sent to the storage nodes from the master node.

You will probably want to use the location plugin to direct the appropriate clients to the storage node vs the master node.

Problems resolved. Capturing and deploying images works successfully. I believe I had a bad image and mismatched settings (UEFI/BIOS). Thank you for your input Wayne/George, it will definitely help me moving forward.

@george1421 After further troubleshooting, we determined that the issue was due to a bad sector on the hd. Moved to a different HD and the system worked like a champ. Thanks George for assisting in finding that little blurb about faulty sectors during the timeout

@george1421 The switch we were using also had a network connection connected to it. So when I pulled the connection, instead of using the IP address we used localhost.

@Tom-Elliott I’m afraid this hasn’t worked. Still getting the cannot remove old partition error.