@BlueTech said:

Also what with the changes to Fedora in regards to the package deploy and mariadb replacing mysql…

The installer takes care of that. 🙂

Fedora 21 used MySQL, while newer Fedora uses MariaDB, and MariaDB is what’s installed by the installer if it doesn’t detect anything present already.

One other thing that when you do that the documentation could with an overhaul. Seems to be all over the place.

What does that mean? Do you want to see a migration video?

@jonathanh Excellent. Glad to help!

Marking this issue resolved (or not, no option to…)

@FlowLive Hey that’s great to hear that someone can repeat my madness… 😓

@Wayne-Workman Le me see if I can clean it up a bit. I need to see if I can integrate what @Sebastian-Roth noted in this thread about using a logical to represent the fog server IP. I think I can make it work.

@Wayne-Workman Thanks Wayne… understood.

I do use the Location plugin for this very reason. I guess because it had worked in a previous trunk, I just assumed that the way I had it set up originally was how it worked. In any case, I can easily change this and put all the storage nodes in to the one storage group, making Sydney the Master node.

You can set this one as resolved.

@Tom-Elliott Thanks Tom. Just pulled and installed and it’s working for me too.

I went ahead and solved this. First, the issue wasn’t something FOG was, or wasn’t, doing. Second, the issue (as I understood it) was the host memory.

SUCCESS! I have successfully created and deployed the images for these machines in efi mode. Thank you for all the help!

@george1421 In fact, this one part of the installer has had a lot of issues in the past.

instead of trying once and just giving up if it doesn’t work the first time - I think it should try again… at least 3 tries, just for problems like below where someone is trying to download the file over a crappy connection half the world away… @Tom-Elliott

@raymondub at the moment the best documentation is in the forums. @Jbob has only posted like 300 times lol. You could probably sit down one day and read all his posts and know everything you need to know. 🙂

@Tom-Elliott
Apparently this problem is solved as well, right after I upgraded FOG to the most current version it seems to work so If I spot any problems I’ll do 😉
Thank you Tom for your help.

What are all the abbreviations?

@megs said:

i have correctly start a full register of UC

What is a UC?

If the browser is showing 100% used space, my best guess is you really ARE at 100% used space.

When fog installs, it creates the /images folder for you. If you added a 10 gigabyte partition (very small be begin with) and mounted it to the /images directory, your display should show properly.

How big is the root partition (/)? You can check with:

sudo df

Ok I managed to solve this based on a previous post where Tom had deleted files in /opt/fog/{service,etc}

I tried doing the above but still didn’t seem to resolve the problem. So I moved the existing fog folder in /opt to fog.backup. Then created the /opt/fog folder and copied the .fogsettings to it.

Performed a reinstall to pick up the existing settings and it now seems to be all ok without any errors.

I created a post a few days ago about booting a MDT iso image via the ipxe boot menu. This may help you on your quest as long as you are using a svn trunk. The only thing I think I would change from this post is to move the place I stored the iso image out of the fog directory directly. In the instructions I said to place the files in /var/www/html/fog/iso , moving forward I would put them in /var/www/html/iso This location is still addressable by apache but won’t collide with anything in the fog distro.

https://forums.fogproject.org/topic/6161/debian-8-fog-trunk-pxelinux-on-ms-server-and-ms-dhcp-help/15

Sorry I typically run all commands sans sudo simply because when I’m writing I’m usually under making the assumption that you are running it elevated already. I should’ve specified I suppose but at least you got it working.

Thanks for reporting back! Great that we could solve this. I really hope we never see anyone actually needing this cdc_ether module!!

@Warrender6 From what I can see in the two screenshots those files are probably on the same system (date and time). So I guess this is still FOG 1.2.0. I am still not sure if you can make this work with 1.2.0 but what is very clear is that init.xz is too small. Somehow got damaged?? You can download a copy straight from here: http://sourceforge.net/p/freeghost/code/HEAD/tree/tags/1.2.0/packages/web/service/ipxe/init.xz?format=raw

If you want to go FOG trunk we need more information on what went wrong. Exact error messages!

@ITSolutions Hi all,
Thanks a lot for help and for this best software around the world to deploy.
Regards

Autosolved:
“1” “fog” “xxxxx” “0000-00-00 00:00:00” “” “0”

@Tom-Elliott +1

I have no idea what is going on in this thread.

@megs In the future, please stop using acronyms in this manner. They are really confusing when not everyone is familiar and they are not defined early on in the OP.

This has been added to the WiKi to the best of my abilities. This was a difficult one because many of these things I myself do not have direct experience with, so I had to retain the formatting and color coding as closely as I could to preserve the originally presented material.

I’ve made this article exclusively about virtual HDDs as this is 95% of what these posts are about. I’ve simply removed the remarks about physical disks.

Here is the link: https://wiki.fogproject.org/wiki/index.php/Add_%26_Extend_a_2nd_Virtual_HDD