chown -R fog:fog /images
the permissions are reset after a reboot. How can i make them permanent?
I have a new 1.5.4 install that i will be using with win10 clients. Should i be using Partimage or partclone?
Thanks for your input
@Sebastian-Roth Hi Sebastian.
Just wanted to say thank very much on trying to sort this issue with our old 1.2.0 images on 1.5.4
After talking to my tech team here, we’ve decided to “take the hit”. We have a live golden instance of a windows 7 VM running on Hyper-v that we can recapture with the new instance of fog. We just need to add hardware specific drivers etc.
So not to take anymore of your time and the fact we will be moving to windows 10 anyway very soon. I say thank you very much for all your effort however we are no longer pursuing a fix to this issue.
thank you once again.
@Sebastian-Roth Again thanks for your help. But it hasn’t worked, same error
contents of d1.partitions;
@Sebastian-Roth Sorry missed your last post.
See screenshots below… also see my previous post about the screen that flashes up very fast.
A little update here.
I noticed a screen flash up really quickly, but managed to get a pic of it.
Is referencing “d1.partitions” in “/images/StonePC1210h110ma/”
But that file doesn’t exist.
I’ve added a screenshots and the contents of “StonePC1210h110ma” in the /images location.
Thanks again if you’re able to help.
@Quazz no joy thanks for your input
Thanks for having a look
Now first of i must apologize, it’s been a very long time since i’ve needed to troubleshoot FOG.
I’ve used FOG 1.2.0 with Ubuntu 14.04 for many years without an issue. I’m convinced it’s something i’m overlooking as quite a lot has changed since 1.2.0!
Long story short, our 15 year old fog hardware was on it’s last leg, so i decided now would be the best time to update the latest ubuntu LTS version along with fog. I have done this before with 12.04 and fog 0.98 i think it was.
I have copied the images to the new server into the /images folder.
Recreated the image definitions in fog UI along with the correct case sensitive file names.
This worked on older versions, so i guess i’ve missed something or i can no longer use that method.
I’ve noted that on the new install, “image size” is 0.00iB which i guess isn’t right. I’ve also noticed it takes a very long time to delete the MBR when attenpliting to reimage.
They say pictures speak a 1000 words, so i’ve added some into this post.
Thanks in advance for taking to time to view this.
If i restart the fog server, i have to run
[CODE]sudo service mysql restart[/CODE]
everytime to get fog back online…Can you tell me how to automate this issue please? or educate me on why i have to do this after every restart?
thanks once again
Restarting MYSQL fixed mt issue.
Once again thank you very much for taking to time to look at this and help me (again).
It’s great knowing that if i get stuck, i can also ask for help here from yourself and the community. Being a linux newbie, that means alot.
Hi Tom thanks for your help on this… i’m not back on site now till Monday, So i’ll get right back on it then. Thax again.
Hi, Visiting 10.15.20.13 gives me a “It works” “Apache2 Ubuntu Default Page” and doesn’t redirect me.
Visiting 10.15.20.13/fog however, takes me to the “database Schema Installer/Updater” (Which i wasn’t expecting!)
Clicking “Install/Upgrade Now” gives me “Database Schema Installer / Updater
Update/Install Failed!”… Guess here lies the problem?.. it’s worth mentioning fog was “reinstalled” before i removed the dhcp…but everything was fine before that…
Thanks for looking at this for me… should a run the fog installer again?
No not that i’m aware of, where’s best to check?
today i discovered my FOGserver was clashing with our onsite DHCP server.
I could fix the issue by turning the FOGserver off.
so i decided to stop the DHCP service on the fog machine using;
sudo /etc/init.d/dhcp3-server stop
sudo sysv-rc-conf dhcp3-server off
this didn’t fix the issue, as it couldn’t “stop” the service.
I then decided to remove the DHCP service using;
“sudo apt-get remove isc-dhcp-server”
this worked! yay…
…but now my clients can boot to ipxe, but i get the following error… can anybody help?
thanks in advance.
Hi thanks for your help Purpleturtle99! after switch fog to do DHCP i can now boot from LAN thank you!
Hi thanks for your reply… Yes its a Legacy NIC on Hyper-v and set to first boot… however my on site DHCP server is serving the dynamic IPs.
I do get an IP address from my DHCP…it just displays the error in POST #1
Thanks again for looking at this.
I guys, can anybody help me on this matter… the odd thing is… i have had it working…(post #10).
I just don’t understand why i can’t get it working now…i dont want to have to make a physical machine just to do my primary image.
Did a fresh reinstall of 14.01.1 today…aswell as fog 1.2.0… commentied the line out of BootMenu.class.php.
[B][I][SIZE=12px]//print “console --picture $this->booturl/ipxe/bg.png --left 100 --right 80\n”[/SIZE][/I][/B]
[SIZE=12px]s[/SIZE][SIZE=12px]till the same as post #1 nothing to do with having teamed network cards?[/SIZE]
[SIZE=12px]When i installed fog… i changed from “eth0” to “bond0”[/SIZE]
[SIZE=12px]all clients boot to ipxe fine… hyper-v boots to ipxe but fails to load the bg. as in post one.[/SIZE]
[SIZE=12px]i’m stumped.[/SIZE][SIZE=12px] [/SIZE]
Thank you for looking into this.
And yes sir. [B][I][SIZE=12px]//print “console --picture $this->booturl/ipxe/bg.png --left 100 --right 80\n” [/SIZE][/I][/B][I][SIZE=12px]in place[/SIZE][/I]
and yes the default file was put back in place.