To image is to download… Create image is to upload… Never really thought about it past that.

Fog makes perfect sense to me, however I don’t believe FOG is for beginners? Not at all discouraging anyone by any means, but to seasoned vets that do this day in and day out… FOG is a great design as is, and has little confusion from the UI in my opinion.

We all started green, and yes many moons ago I too placed a blank drive over an image… OOPS ! Once you do this to yourself it will most certainly never happen again…lol Been there, done that… Learned the definitions quickly after that. Old Norton’s Ghost days, and I am far from missing them

Many thanks to all that contribute !!

.

Funny you mentioned that, just had my first dell laptop come across without Ethernet… Talk about cheap…

Anyway, I have a few HP 3005pr USB 3.0 Port Replicators that use Ethernet over USB.

Not sure if it will work, but I will give it a go and see if it’s an option ?

.

That’s wild, I’m on a Dell PowerEdge R900 ESXi, these are my specs.

PowerEdge R900 4 X 6 Hex core (24 Cores)
128Gb memory in failover mode ( Shows 64Gb)
H700 Raid on a MD1000 3Tb X 4 Raid0 ( Cloned nightly as it is RAID 0 ) 7200RPM SATA III
ESXi 5.5 U2
Using Fog 1.2.0 Ubuntu 13.10 X64 ( 6Gb memory, 2 Virtual Sockets, 2 Cores Per Socket )
Brocade 1Gb Layer 3 switch

Fog seems fast, no issues uploading and downloading images. I can deploy between 4-5 Gb Per Minute.
Uploads are now slower, but I’m at max compression as I have a ton of images. I need the deploy speed fast after I create the master image. When I was at default my upload was about 1.5 to 2Gbps. At max I’m sitting just under 1Gbps

However my FTP is maxed at 100Mbps, everything else runs at 1000Mbps ?

I can live with it as everything else seems great. However when I figure whats up with the FTP transfer speed I’ll relay it in hopes it may help ?

Booting to Hirens takes about 20 seconds at most Hirens 15.2 Restored( 2.7Gb ) Hirens maxes my brocade switch out.

Here is how I boot to ISO in advanced boot

:hirens
initrd [url]http://10.10.10.1/ISO/hirens.iso[/url]
chain memdisk iso raw ||
goto MENU

Hope it helps !

You know I read through that… And could have sworn it was for .32

Many thanks !! It’s been a long week

I see ton’s of info about booting from Hirens in the old version of fog.

However does anything change modifying the menu and booting from Hirens ISO in the latest release ?

I’m running the latest fog server and it’s working well… So I just want to see if there is anything I should know before I fix something that isn’t broke o_O

Many thanks in advance !

I like to use the svn, but I just have issues like that…lol " Its working great, lets change it "

Just to let you know I didn’t just leave this thread

I did have that enabled and had it switched under the image itself.

However I didn’t have a chance to get that model back on the bench, as soon as I do I’ll report back ( hate when people don’t post solution if something worked )

The good side is that I have imaged about 42 machines, 8 different models and all seems to be going good ! Loving fog !

The only real issue I see is that I have to keep restarting multicast service after every boot.

I’ll update this as soon as I get that box back on the bench. Thanks !

As far as my old images, figured I would just a fast machine and switch back and forth networks. Download from Snap deploy, register fog and re-upload it. I have 2 different PXE servers. Acronis snap deploy on one network, and fog on another. Soon to be leaving snap all together

Did you actually set the image to be of Partimage style?

I guess that’s the part I’m stumped on ? Whats needed on my end to tell fog it’s partimage and not partclone ?

How do I set them to partimage style ?

Just to be clear about partimage ?

I understand that Partimage was the old way, yes I had a .32 server on Ubuntu 14 server. However I was having issues and wanted to have a clean build so I took a day and put together a new build. Gotta love VM’s

Anyway, I have Ubuntu Server 13.10 with Fog 1.2.0 running under ESXi 5.5, fog on Local storage and images on external SAS enclosure with H700.

All went well outside having to run the restart on multicast service, but I’m with others in saying I believe I like the individual imaging anyway… However I have my images I rsynced from the .32 server I retired.

I set the flag for legacy in the GUI, however it still tries to use partclone ? I have them selected as partimage, and I restarted all tasks. It doesn’t seem to care…lol

 My question is, does the new install do something to the images that basically it says they are partclone and not partimage ?  I attached the 2nd vmdk that had my images before I installed 1.2.0.  Is there any manual way I can tag the image as partimage so I can just download and re-upload as partclone and get rid of my mess ?

I have about 320Gb of images I don’t want to do over for obvious reasons (time)

Many thanks in advance for all your work, I’m loving Fog ! Was a former snap deploy user… THAT was a mess I will not return to !

Oh, also what kernel should I be using ? Do I need to upgrade it after the new install or is it on the newest ?