Fog 0.33b Snappin deployment
r1155 should have fixed the hostname_early issue, but I don’t know if just turning it off has helped you out at all.
I updated to R1155 and still get the popup box…
Tom I was double checking that hostname_early was disabled( It is disabled) and noticed this…
I haven’t, quite, figured that out yet. I get those as well. It seems to be something from the Capone plugin causing the issue.
Actually, it appears to be the way the method is called.in the ServiceConfigurationPage.class.php file. I’m checking if this is correct.
It, by itself, is nothing to be worried about. You can remove those entries from the database, as they are a nuisance. I’ve updated the trunk and this should be fixed.
Is the hostname_early the only thing that could cause my popup box going from R1141+
It’s the only thing, windows related, that I could think of as causing your particular issue.
I’m trying to look at the issue.
I didn’t change to the new scripts until: r1142
In r1140 to r1141, I changed the files:
change/trunk/packages/web/management/reports/User Login Hist.php (diff)
None of those files deals with Windows services except the usertracking.report.php file, which only deals with logging who’s logged in when.
I’m trying something out if you’re patient with me.
Please update to r1157 and try again.
The only major change for the fog scripts was in 1141 fog creates the partitions 1 and 2 in windows 7 based image deploy. In 1142, in the fog.download script, I removed this but starting to think it is still needed. r1157 contains this and hopefully helps you out. I think the reason you’re seeing that error is the 100MB partition doesn’t actually have any data on it which may contain the information your system is looking for.
I tried R1157 and still get the message Tom.
I am heading home for the night. I can pickup where we left off tomorrow.
With any luck, this issue is now fixed.
It seems, with all the coding I’ve done, I made a little typo, I had a 2 where a 3 should have been. Basically what this means is, it was converting your hard-disk to gpt. The imaging would work fine because, for all technical purposes, the partitions were created and created properly, but then sgdisk would run when it shouldn’t have.
Hopefully this fixes our issue with this. r1160 should contain this fix.
Tom, I updated to R1160 and I am still getting the error…
If you revert the system to r1141 (before the fog scripts were regenerated) and deploy an image, then update to r1161, and re-upload the image, then try to redeploy, does it work?
I ask this because I am only using a sysprepped image at work and all works perfectly fine.
I did as you asked. and I still get the error message.
My image is sysprepped as well, with driver packs from driverpacks.net.
Can you try sysprep without driver pack installation?
It would seem possible, to me at least, that that whole Hostname early thing is causing the issue. To my knowledge, hostname_early sends if the hostname=blahblahblah in the 01-XX-XX-XX-XX-XX-XX file is filled out. It’s supposed to check if hostname_early is enabled on the server and, if so, set this up, but I have a sneaky suspicion that this variable is being sent in either case.
While this doesn’t affect me, it would seem to make sense that driver packs are making changes to the sysprepped system, after another change has already happened. This would, theoretically, explain why you’re seeing this issue. This is what my mind is telling me. I really haven’t changed anything too drastically. I can, if you’re willing, create an init.gz file with the original fog script and see if all works for you.
download the new init.gz with the original fog script: (slightly modified to use double quotes where there was single quotes.)
mv init.gz init.gz_r1161
wget -O init.gz --no-check-certificate https://mastacontrola.com/fogboot/images/init.gz_origfog[/code]
Tom, I dont know if this helps any… but i noticed that when the image is going to work i see this screen before it boots into setup.
I dont know what made it work, probably your init.gz because i re-sysprepped without the driverpacks.
I will try with the image that has the driverpacks and see if it works.
Maybe I fix/broke the chkdisk feature. Now we’re getting somewhere.
Good news! the image with the driverpacks worked!