Wayne,
Thanks for the reply - Sorry I should have added all the info you requested in my first post:
Ubuntu 14.04 LTS
Upgraded from 1.2.0
Reason for upgrade was simply browsing this forum and noticing a few other issues that I was encountering was fixed fixed in other trunks…so I just figuring updating to the latest trunk would be the best idea. I have searched through the forums in regards to possible host issues and I could see this query being referenced :

SELECT * FROM hosts WHERE hostID NOT IN (SELECT hmhostID FROM hostMAC);

this only brings back 1 host…so it seems that the hostsID and hostMAC’s match bar 1…

Thanks again

@Tom-Elliott I managed to fix this…I noticed the only difference between the 1 host working from the old config was no spaces in the name! after updating the db name from test 1 to test_1 it now appears in the gui!! So spaces make a difference in the name!

Thanks again for rapid help and expect more from me to help this project in any way.
Regards

@Tom-Elliott
Alas they are now found! Always read the doc’s! File this under user error
Thanks Again - Fast and great support.

@george1421
This approach makes sense! This should be filed under a doc change for best practices when booting from local custom iso’s!

@george1421
So is it fair to say any Advanced Menu customization will cause issues if configured in previous versions and upgrading to 1.3.x?

@george1421
Thanks I figured as much! - the only other concern for me was the update wiping out my customs ISO’s!.
Thanks

@george1421
Hey George - from the advanced menu and this was all configured in 1.20 then upgraded to 1.3.5 - I have quite a long list of around 10 items - I use the advanced menu for WINPE booting as well as other useful ISO’s - very useful! - I did notice more options for the advanced menu in 1.3.5…
Thanks

@george1421
Thanks for the reply - The thing here is that I have 2 vm’s - The original one upgraded to 1.3.5 and the Centos one is a fresh 1.3.5 with just the database and images copied across. If I just concentrate on the upgraded one (ubuntu) the 2 issues are that after going to 1.3.5 the advanced menu no longer works with the Could not boot - result too large" “Chainloading failed…” - and the fact the upgrade seemed to wipe out subfolders in the ipxe dir…

I did manage to get passed the “result too large” error by recreating the advanced menu list with starting form the line “Menu” - It would seem to me that there are change’s in 1.3.5 that dont mesh if you have previous populated advanced menu items prior to the upgrade - What was obvious to me what that there seemed to be some enhancements to the menus items in 1.3.5 which may explain the issue - Of course this also could just be something in my environment…Im a software engineer so im fully aware this could be user issue…

Thanks!

Server

• FOG Version: 1.3.5
• OS: Ubuntu/Centos

Client

• Service Version:
• OS:

Description

Hey All - Firstly again let me start with a praise - Nothing but love for the fog project. So onto my issue - After upgrading to 1.3.5 the Advanced Menu no longer works…on the boot screen when the Advanced menu is selected it gives an error stating " Could not boot - result too large" “Chainloading failed…” - I was going to migrate over from my ubuntu installation anyway to a Centos server so I setup fog fresh on the Centos side - all good…I imported the fog database and the images it all seemed ok - however the advanced menu was still giving the same error - I did get it to work by starting the populate the advanced menu again just starting from “menu” - Am I right in thinking that there might be a few differences between the way the advanced menu works in 1.3.5 compared to earlier versions? Also one other strange issue - I placed a few custom ISO’s in an iso folder (…fog/service/ipxe/iso) - I use these to boot from in the Advanced menu but the upgrade wiped this out from my ubuntu vm???
Regards

@Tom-Elliott Yeah sorry I didn’t provide enough information - being a software engineer myself I know that the key is in the detail! Still this will be a nice quick fix if anyone else see this or if its added to any FAQ.

@Tom-Elliott I managed to fix this…I noticed the only difference between the 1 host working from the old config was no spaces in the name! after updating the db name from test 1 to test_1 it now appears in the gui!! So spaces make a difference in the name!

Thanks again for rapid help and expect more from me to help this project in any way.
Regards

Wayne,
Thanks for the reply - Sorry I should have added all the info you requested in my first post:
Ubuntu 14.04 LTS
Upgraded from 1.2.0
Reason for upgrade was simply browsing this forum and noticing a few other issues that I was encountering was fixed fixed in other trunks…so I just figuring updating to the latest trunk would be the best idea. I have searched through the forums in regards to possible host issues and I could see this query being referenced :

SELECT * FROM hosts WHERE hostID NOT IN (SELECT hmhostID FROM hostMAC);

this only brings back 1 host…so it seems that the hostsID and hostMAC’s match bar 1…

Thanks again