Network boot does work from the local drive on the server.

It fails to work from the iSCSI drive though. We’ve copied, and confirmed the permissions, confirmed the drive settings Master and active etc.

It continually times out at TFTP. swapping the master drive back to the internal hard drive, imaging works. (within the fog storage node administration)

Thanks a lot for your support TOM.

I will test and let you know.

Thanks
Siva

it sounds to me like this might need the same fix that is used for hyper-v virtual machines, disabling certain console features loaded in the ipxe boot menu

Somewhat like that, but organized in such a way that FOG can automatically inject the correct drivers into the firstboot process. If I were to use the Driverpacks, I’d need to build a database linking device IDs to folder structure, and that complicates the script significantly.

I did it for memtest 5.01 and it works.

:MENU
menu
item --gap – ---------------- iPXE boot menu ----------------
item MEMTESTEFI MemTestEFI
:MEMTEST
kernel [url]http://{ip}/fog/service/ipxe/memtest/EFI/BOOT/BOOTX64.EFI[/url]
boot

Now, I have to do it for WINPE

[url]http://fogproject.org/forum/threads/ipxe-boot-menu-password-protected.11499/#post-35630[/url]

Its all about keywords 😉

Now…need to learn to UPLOAD an image in the same manner.

[CODE]
:MENU
menu
item --gap Please Select one of the images below
item fog.local Boot from hard disk
item img1 COOLNAME
item return Return to main menu
choose --default fog.local target && goto ${target}

:fog.local
sanboot --no-describe --drive 0x80 || goto MENU

:img1
kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=MY.IP web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=MYIMAGE.NAME ftp=${fog-ip} imgType=n osid=7 storage=${fog-ip}:/images capone=1 imgFormat=2
imgfetch init.xz
boot || goto MENU

:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || goto MENU
autoboot[/CODE]

if you wont give information, it’s harder to help you.

different solutions for different environments, but unless you know the why… things don’t always make sense.

Also, you might look through the Wikipedia/Wikimedia tutorial on editing articles and using Transclusion to reduce data duplication. I think that’s still what they call it. We really need a wikipedia team of super documenting super heroes!

The NIC bonding isn’t difficult to achieve, I just followed the guide at [url]https://help.ubuntu.com/community/UbuntuBonding[/url]. There’s also a handy guide on a similar vein at [url]http://www.beyondvm.com/2014/03/quick-tip-bonding-lacp-and-vlans-in-linux/[/url] which adds some of the Cisco CLI commands

My etc/network/interfaces ended up as:

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet manual
bond-master bond0

auto eth2
iface eth2 inet manual
bond-master bond0

auto bond0
iface bond0 inet static
address 192.168.1.60
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 8.8.8.8 8.8.4.4
bond-mode 4
bond-miion 100
bond-lacp-rate 1
bond-slaves eth1 eth2

… which provides for a single ‘bond0’ virtual network interface that you set up beforehand and refer to as the main interface when installing Fog. If you want even more network bandwidth you could add another two port card and add these interfaces as eth3 and eth4 into the mix too but the limit would be the disk throughput I guess - and the network infrastructure. As everything is isolated and local the latter isn’t an issue for me.

Of course you do need a lan switch that supports LACP (a.k.a 802.3ad). On my sandpit system at home I have another N36L Microserver with a two port pcie-e (Intel) network card running into ports 1 &2 on a DLink DGS-3324SR switch. The latter was pretty easy to set up for LACP from its web interface. For the Cisco '3750 I may need to do some reading 😉

I’m very interested to see what performance the ssd’s will achieve on my new box. I figured that the vast majoriy of the time as I’ll be reading from them when imaging back to the G1 tablets I shouldn’t see problems related to trim settings. Time will tell !

HTH
Robin

in the developer’s pre-release version of fog, the ability to customize the ipxe boot menu has been extremely extended. using this menu modifying system, it may be possible to set fog as your default pxe boot system, and to default directly to your ZENworks pxe boot server if there is no pending fog task.
however, keep in mind that these features are still experimental and you may be the first person to work with this type of setup

so I just run Sysprep after I install all the programs needed?

I will use this XP image on multiple different OLD hardware

Thanks

Thank you for that information. I now know how to retrograde. I am still having issues with the Lenovo Yoga tablets that don’t have ethernet ports. I will follow up on this thread: [url]http://fogproject.org/forum/threads/ipxe-boot-issue-with-realtek-rtl8153.10507/#post-36781[/url]

The client is for things after imaging(Renaming, deploying snapins, etc).

As far as your problems now it looks like your client is not connecting to your DHCP server as that is where the IP comes from.

[SIZE=6][B]newbie here[/B][/SIZE]

[SIZE=6][B]How do i change the fog server ip in 1.2.0?[/B][/SIZE]

[url]http://fogproject.org/forum/threads/requests-for-wiki-access-ask-here.3811/[/url]

Sorry I can’t be of more help, I set up a server at each of my locations, but that works out to my benefit because each building uses the same base, but this lets me tweak the settings to better fit that novell context.

also, from the article, you can test with this
[CODE]env X=“() { :;} ; echo busted” /bin/sh -c “echo completed”
env X=“() { :;} ; echo busted” which bash -c “echo completed”[/CODE]
or
[CODE]wget -U “() { test;};/usr/bin/touch /tmp/VULNERABLE” myserver/cgi-bin/test[/CODE]

[quote=“Rohn Gordon, post: 37516, member: 26505”]It hung at 99.82%. I will upload the file again.

Rohn[/quote]

[url=“/_imported_xf_attachments/1/1408_errorlog.txt?:”]errorlog.txt[/url]