I’m confused. There is no issue in the db, but the data is stored in the db as base64 encoded, though I plan to move this to aes encrypted just to ensure somebody can’t just steal your data.

@Sebastian-Roth for help the three exit types were sanboot, grub, and exit. Sanboot is ipxe’s way of getting first hard drive which appears at bios memory address of 0x80. It’s not always a workable method, so the grub exit type was brought in which can find or use an HDD. In 1.2.0 it always assumes the first disk is hd0. Exit does what it sounds like, it exits back to the bios for handling what to boot next.

@gooroox Did you get this issue solved?

Marking this solved here as the issue seams clear.

@bennewell Still it would be great to hear if you found what is causing it and can write a short summery for other users to know.

@ZINGARO1972 Please let us know more about your environment and we might be able to help.

Thanks Tom. I appreciate your help and this forum has always been awesome.

To me this means that even the MBR was not dumped to the disk. Otherwise you should at least see some kind of partitioning on the client that tried to download an image.

Anyhow. Marking this solved as we probably won’t bother about going into the details any further. Thanks a lot for letting us know.

@StahnAileron I’ve added a ton of functionality (I think) to the installer.

If even works with typical switches and output to assist in knowing more.

For example:

./installfog.sh -? will print potential usage options.

As we are not able to see what else is in your network it is very hard to guess what’s going on. But I can offer to look at a packet dump and hopefully we can find out what’s causing the issue.

Please turn off all your clients for that. Install tcpdump on your FOG server and start it up as root tcpdump -i eth0 -w bootup.pcap (change eth0 if you use a different network interface on this server). Leave tcpdump sitting there and start up one of your clients. After it “failed” you can stop tcpdmp with Ctrl+c and upload the PCAP file to the forum.

Please also take a picture or even better video of the booting client so we can see what you see as well.

This way we might be able to help. Everything else is just blind guessing.

Wow site giving me a fit this morning, couldnt reply for the last 20 mins.

The version is the Trunk in the first post.

Hre is the output:

root@CINDSV10011:/home/ladmin# ls -lR /images /images: total 12 drwxrwxrwx 2 root root 4096 Nov 5 15:22 dev drwxrwxrwx 2 root root 4096 Nov 4 08:37 postdownloadscripts drwxrwxrwx 2 root root 4096 Nov 5 15:22 Win7VL /images/dev: total 0 /images/postdownloadscripts: total 4 -rwxrwxrwx 1 root root 233 Nov 4 08:37 fog.postdownload /images/Win7VL: total 15459848 -rwxrwxrwx 1 root root 2 Nov 5 14:47 d1.fixed_size_partitions -rwxrwxrwx 1 root root 1048576 Nov 5 14:47 d1.mbr -rwxrwxrwx 1 root root 184 Nov 5 09:50 d1.minimum.partitions -rwxrwxrwx 1 root root 30 Nov 5 14:47 d1.original.fstypes -rwxrwxrwx 1 root root 0 Nov 5 14:47 d1.original.swapuuids -rwxrwxrwx 1 root root 8886666 Nov 5 14:50 d1p1.img -rwxrwxrwx 1 root root 15820924479 Nov 5 15:22 d1p2.img -rwxrwxrwx 1 root root 190 Nov 5 14:47 d1.partitions```

Ah Okay. I thought I was missing something. I take care of multiple locations so walking a user through getting to the network boot screen is easier than traveling to work on it there or pick it up if I suspect something. Thanks for the fast reply Tom!

Thx for this. The plugin is exactly what i need.

The site deployment server is only a storage node with own pxe\tftp and mysql-client. It uses the MySQL DB of the Master Server.

Well, that is exactly what resizeable images are made for. Either that or for deploying to larger disks (expand partitions automatically).

I just read your earlier post where we pointed you to use resizeable images. So I guess you want this with your new machine as well?!

Could you please open the file d1.original.partitions in both images on the FOG server and post the contents here. Most likely the partition scheme is causing an issue here.

Did you see any errors while uploading that Win10 client? Did you see the blue partclone window? Probably best to start another debug upload task (Host -> Basic Tasks -> Debug Upload) and take pictures while you go.

Thanks for letting us know! I’ll mark this thread solved for now. Feel free to ask more questions here (if related) or better start a new one.

@Sebastian-Roth

sry haven`t found this thread before.

Thx for this.

My workaround works only randomly, i think rc.local is the best way.

We had a minor issue with some embedded iPXE script recently. I wonder if this might have caused the hang. Although on most machines it just went straight back to the BIOS without loading default.ipxe… Or it was a corrupted download. Either way thanks for letting us know.

@Wayne-Workman
After reset encyption data works fine.
Thanks for help
Regards

ok so ive changed all the passwords on the server to 1 password and now it is all working
thank you all very much and have a great day 🙂

@george1421 said:

I see the majority of the deployments here are ubuntu.

That’s changing. I strongly push red-hat based distros here because they have been less problematic. I also tend to think that my clearly written instructions for Fedora have swayed the newcomers as well. I’m now working on the CentOS 7 article which is almost a carbon copy of the fedora 21 server article. And then I’ll start on a Fedora 22 server article next lol.

But seriously, just give me a shove in the right direction for partition resizing and I can probably make it really clear and nice looking.

@Sebastian-Roth said:

I am sure you need to spend a lot more days! Take it one step at a time. I don’t know anyone who learned linux and FOG in just a couple of days.

Took me 3 weeks just to get the web interface functional with 1.2.0 on Fedora 21 Workstation… Prior Linux experience, basically zilch. Another 2 weeks to figure out the FTP secomp_sandbox setting needed set… a few more weeks to understand the client and BEGIN to grasp how easy fog can make my job.

This whole FOG ordeal started in February this year (2015) for me. Still learning. And I still occasionally royally screw up too, thank you snapshots and hyper-V!