Downloaded the latest Subversion. Seems to be the one I was one. 1.0.1
No difference in results.
Downloaded the latest Subversion. Seems to be the one I was one. 1.0.1
No difference in results.
Oh Sorry.
Operating System: Linux - (50)
Image Type: Multiple Partition Image - Single Disk (Not Resizable) - (2)
For which image? The Ubuntu I am using is
Ubuntu 14.04 LTS Desktop.
Zorin is version 8
TinyCore 3.0.21-tinycore
I only install Ubuntu on this to make an image from it. Ultimately I want to make it so I can Boot TinyCore Linux from FOG with GUI Support to act as a Zero Client for VMware. I have a working version of TinyCore with VMware-View Loaded. It pops up and covers the screen beautifully. No one can do anything with the OS just use View-Client. Well I am reading and it seems for the GUI to be included in the core I am loading I need to remaster it. So I was playing with a current version of TinyCore (it includes more keyboard and network drivers then I have in my current core) and had it install to the local hard drive. This dumped the Partitions Ubuntu made. TinyCore didn’t install like it should have so I said hey perfect time to test and see in the deploying process really will work.
And here I am. This has been a lot harder to get this working then it should be. We have an old tech here who wants to load my current version of TinyCore on a bunch of really cheap USB drives and get USB Extension cables and hang them on the inside of the machines. This means we would have cables going into our boxes to run the OS and I can’t stand that idea. There has to be a better way to deploy this on a larger scale. That is when I came across FOG.
Currently this old Tech is using CloneZilla by slaving HDD on his machine to image new machines and I want to get away from that as well.
It doesn’t seem to matter what I set the image to. Partclone for Partimage same results. JunkHacker says all the images uploaded are Partclone so I shouldn’t have to change anything since these are fresh images on 1.0.1
So I created a new image of my second test box after I installed Ubuntu Desktop 14.04 LTS 32bit version on it. Again image created successfully. Played around with some TinyCore on it and removed the partitions. Went to reimage and Fog reported yet again that the image it had just taken was not a “partclone” however the screen flashed black and then back up and it proceeded to deploy the image for 2 other partitions? When I went to boot from the local drive I get Grub Rescue Mode which is more then I got before I attempted to reimage.
Just recaptured the image. Everything said it completed correctly. I made sure my computer is in the right group and with the right image selected. I scheduled the task and rebooted. The client machine never loads the cloning screen (Blue Background Red Status Bar)
Fog 1.0.1 fresh install a week ago on Ubuntu Server 14.04
Uploaded the image a few days later. Is there a way to tell it to be one or the other during the imaging process? Which one is better?
I am going to recapture the image and then try again.
I checked the GUI Flag and updated the image to a PartImage from PartClone and vice versa. The Client Boots but restarts before the Cloning Screen.
I am attempting to deploy my first image! I took an image of a computer running Zorin Linux 8. I then deployed that very image back to the same machine successfully. I then put a different box on the bench and tried to deploy the same image to it.
Registered the Host - success
Placed Host in Group - success
Assigned Image to Host - success
Schedule Task to Deploy - success
Booted Client into iPXE - success
Deploy Image - fail - “Not a partclone image”
Any thoughts?
Well I spoke to soon-ish. I can get TinyCore to boot but the GUI for it never loads it just boots into a terminal. on the same note the other items I have set to boot which all have the same settings just flash the menu screen back up. They don’t want to actually boot. bummer.
It Worked! Your Awesome.
[CODE]set boot-url http://${fog-ip}/${fog-webroot}
:start-http
menu City of Lewiston - Imaging and Diagnostics
item VMware VMware - Live
item DellDiag Dell Diagnostics
item hostinfo Host Informaton (Your Machine Info)
choose target && goto ${target}
:VMware
initrd ${boot-url}/ISO/VMware/TinyCORE.iso
chain memdisk iso raw ||
echo failed to boot
prompt
goto MENU
:DellDiag
initrd ${boot-url}/ISO/DellDiagnostics/DellDiag-7.iso
chain memdisk iso raw ||
echo failed to boot
prompt
goto MENU
:hostinfo
echo This computer : ||
echo MAC address…${net0/mac} ||
echo IP address…${ip} ||
echo Netmask…${netmask} ||
echo Serial…${serial} ||
echo Asset number…${asset} ||
echo Manufacturer…${manufacturer} ||
echo Product…${product} ||
echo BIOS platform…${platform} ||
echo
echo press any key to return to Menu
prompt
MENU[/CODE]
This worked nicely! I had to change the last MENU prompt from your code. For some reason it would through up a bunch of “stuff” (for lack of my current knowledge or caring as to what it was talking about) and would restart. Once I changed it the screen would refresh after the prompt to the menu. Before after the prompt it would do the restart thing.
I also changed the main folder for the ISO images to one I noticed you used from your other posts. Made more sense and was easier. I wonder what memdisk file it is pulling up with the chain command compared to the original one where I specified the path.
Side note I was playing around with the iso and raw options as you can see where the DellDiag option had it and the VMware one didn’t I was hoping to find the magic combination but was unsuccessful.
Thank you to both of you. Good education. Although using the code copied from Tom with the IP-ADDRESS filled in I have a new problem. the advanced menu doesn’t appear any more. the screen flashes and returns to the standard menu. Is there a walk through or instructional guide available for the current release on how to set an ISO as a boot-able option? I am guessing not or you would have sent me that way already.
I am not sure if I have my advanced menu written poorly or if I have a problem with my memdisk file. I tried another memdisk file provided in another post
[url]http://fogproject.org/forum/threads/pxe-boot-goldmemory.12/[/url]
This had no change. Below is my Advanced menu script and below that I will include my error message.
#/ Begin Boot Menu. the Pound and slash are not part of the menu script
set fog-server IP-ADDRESS
set boot-url [url]http://IP-ADDRESS/fog/[/url]
:start-http
menu City of Lewiston - Imaging and Diagnostics
item VMware VMware - Live
item DellDiag Dell Diagnostics
item hostinfo Host Informaton (Your Machine Info)
#item foginfo FOG system info
choose fog-opt && goto ${fog-opt}
:VMware
initrd [url]http://IP-ADDRESS/fog/service/ipxe/VMware/TinyCORE.iso[/url] raw
kernel [url]http://IP-ADDRESS/fog/service/ipxe/memdisk[/url]
boot
:DellDiag
initrd [url]http://IP-ADDRESS/fog/service/ipxe/DellDiagnostics/DellDiag-7.iso[/url]
kernel [url]http://IP-ADDRESS/fog/service/ipxe/memdisk[/url] iso raw ||
boot
:hostinfo
echo This computer : ||
echo MAC address…${net0/mac} ||
echo IP address…${ip} ||
echo Netmask…${netmask} ||
echo Serial…${serial} ||
echo Asset number…${asset} ||
echo Manufacturer…${manufacturer} ||
echo Product…${product} ||
echo BIOS platform…${platform} ||
echo ||
echo press any key to return to Menu ||
prompt
goto MENU
/#end menu
MEMDISK: Image has fraction end sector
MEMDISK: Image seems to have fractional end cylinder
Disk is hd0, 37038 k, C/H/S = 36/64/32 (guess/guess), EDD on, rw
Using safe INT 15h access to high memory
Total size needed = 2381 bytes, allocating 3K
Old dos memory at 0x8e400 (map says 0e8400), loading at 0x8d800
1588: 0xffff 15E801: 0x3c00 0x7b17
INT 13 08: Success, count = 2, BPT = 0000:0000
old: int13 = 8e40000a int15 = 8e40037f int1e = f000efc7
new: int13 = 8d40000a int15 = 8d80037f int1e = f000efc7
Loading boot sector… booting… <------ This is where the machine will hang forever.
I can’t seem to make it past this part.
any help would be appreciated and an education would be even more appreciated!
Note to the Developers:
Awesome Product and Service you provide. Just plain incredible.
I missed the Banner in my haste. The Password was being delivered from the Storage Node. I didn’t think to look there. Makes sense on a large scale operation. Thank you for the help Junkhacker. By the way your avatar looks so angry. Makes me read all your responses like your angry and grumbling or scolding people… brilliant.
I have installed Fog 1.0.1 on Ubuntu 14.04 Server. Everything is working fine however once client machines finished it’s Imaging Process (making an image) I started getting an error about the FOGFTP Login Error. it was trying to logon to the correct machine (IP Address) with the correct User Name (fog) but the wrong password (RANDOMPASS) I changed the Password in the /var/www/fog/commons/config.php and the WedGUI > Fog Settings. Restarted the process and again it came back with this error at the end of the process. I restarted the TFTP service and still no change. I have to change the local user “fog” password on the server for it to work. I would like to have my (More Complicated) password rather then the six character one created.
Any Thoughts?