we deploy to 1000 computers every 12 weeks… never syspreped once… is that bad??

Hi guys,

Since I bonded my server nics, I no longer get the front page stats.

I converted all the locations in the web GUI that specify eth0 with bond0 but all I get is the ip info box and spinning cogs of death for the HDD stats and bandwidth.

Any ideas?

Are there config files that don’t update nic change that I need to update manually?

[quote=“Tom Elliott, post: 17763, member: 7271”]I don’t think so. PXE in it’s native form doesn’t do anything bios related, however, there are PXE based EFI configurations out there from some of the research I’ve looked into.[/quote]

This seems very viable…no??

[url]https://wiki.ubuntu.com/UEFI/PXE-netboot-install[/url]

[quote=“Tom Elliott, post: 17758, member: 7271”]As I’m relatively new and mainly been working on the GUI, I’ll try seeing if I can update my init.gz file to test around with EFI a little bit. The kernel’s that I’ve been building have already included support for EFI, so it may just be a matter of … finally … switching to partclone to get true UEFI support imaging. Again, I’m new so it may not work right away and may take a little bit more time, but I will try and keep trying until I get it for you all. I will, as per usual, request others to test out as well as all I’ve got is a VM that I can tell to use EFI for bootup.[/quote]

Hey Tom

That would be awesome… All new devices are being churned out with UEIF bios, and when they start becoming cheaper, then the ability to boot in non UEfi mode will diminish…

Does this also mean that you would not be able to pxe boot anymore?

the FUN just keeps on coming…

DAY 3
Decided to bond the NIC’s

again… googled the hell out of it, surprisingly, there is no result for Fedora 15 nic bonding, save the official docs from Fedora that clearly articulates how to achieve bonding…

HOWEVER, not once did they mention that you needed to chkconfig NetworkManager off, nor did they mention to service NetworkManager Stop…
They failed to mention that when bond0 comes up, for some reason eth1 still holds an ip address, and that ifdown eth1 then ifup eth1 gets it to behave… then ifdown bond0 followed by ifup bond0…

they failed to mention the horror when you can no longer ping anything… not even the router even though all settings in the ifcfg file are correct and you’ve quadruple checked ifconfig -a output…

endless googling finally reveals that “perhaps” you may need to add a route by tying route add default gw 192.168.x.x dev bond0 which doesn’t seem to persist on network restarts…

suffice it to say, blowing away the server and re-installing crossed my mind on several occasions…

the result???

I have internet access but I can only ping computers on the same subnet, all other computers on any subnet can ping me… thats fine for now because imaging is working… again…

note to self… charge more for this $h!t in future…

[quote=“Todd Holte, post: 17741, member: 141”]Did you convert the GPT Disk to MBR Disk? I used “AOMEI Partition Assistant Standard Edition 5.2” its free for private and commercial use. [url]http://www.disk-partition.com/download-home.html[/url][/quote]

Hey Todd

I actually resolved this issue today…

I originally did convert the GPT disk to MBR disk, however, it was still giving me the same errors.

The eventual setup that worked was the following:

Boot into windows 7 install disk, and shit + f10 on the first screen before you start the install process, blow away the partitions etc and create a new one so that you can have a single partition windows 7 install.

I then decided to use single disk, single partition to upload the image, thats when FOG told me that no partitions can be located. It turns out, there is a post on this forum (which I can no longer find for some reason) I found while googling the error message which led me to a free tool called fixpart (there is a windows version) that you download and run on the computer with the following steps:

fixpart.exe 0:

it then immediately told me that there were left over GPT signatures on the drive mixed in with the MBR and that it would take care of them if I pressed Y.

After that, i committed the changes with “w”, it wrote the new MBR, I rebooted and presto… the image got taken up.

after I deployed it back to another laptop, the image went down fine however fog complained that partition 2 to 5 were missing but wasnt bombing out with IO errors like before… it then said task completed and it rebooted into windows 7…

so happy days!!

[quote=“Axel, post: 12528, member: 686”]So I spent 10+ hours today trying to get this to work. I’ve followed multiple tutorials on using an external NFS share and my results are not good. After I configure the NFS share in FOG the web GUI says unable to connect on the front page where usually the space free/used is displayed. I’ve created the NFS share, remade /images mounted my NFS share in FOG on /images, created the .mntcheck and then the /dev folder with .mntcheck inside it. I’ve made sure to chmod -R fog:root /images. When uploading an image once the process gets to send method-nfs I get an error of mount: 192.168.62.125:mnt/nfsdata/dev/ failed, reason given by server : Permission denied
mount: mounting 192.168.62.125:/mnt/nfsdata/dev/ on /images failed bad file descriptor. I’ve even tried following posts on here where people had similar issues and i’ve had no luck. The fog server is a vm running in Proxmox with bridged networking. Any ideas?[/quote]

hey Axel

not sure if you resolved your issue, post is too long… didn’t read all of it…

however, I have noticed two things that may be causing your issue…

the first… you used chmod -R fog:root /images… when it should be chown -R fog:root /images (perhaps you meant to type that…)
the second, in your screen shots for the storage node section, the password field should resemble the password in plain text, not the encrypted type… try changing to your normal password, save and try that…

I always issue (right or wrong) the following commands on the /images folder…
chmod -R 777 /images
chown -R fog:root /images

but that’s just me…

also… try restarting the multicast service… sounds trivial, but when multicast bombs for me… (ie stuck on the please wait screen) I restart the service and it works…

yes… unless that computer name exists in AD already, you will not get GPO’s either… no?

hey guys…

could possibly be unrelated… but…
we were having issues with TFTP Timeout when it came to subnets other than the one fog was on… it turns out the switch needed configuration to allow spanning subnets (not sure on exact terminology but 5 minutes after the network guy worked on the core switch, it was working).

the bad descriptor problem, I resolved by making sure that .mntcheck was in both the /images and in the /images/dev folder…

good luck… let us know how you go…