Posts made by Matt.Collins

Yeah, I checked that too and that wasn’t my issue. I’m now starting to think I just picked a bad laptop to work on out of the bunch as after further testing with more, I’m able to upload and deploy without a problem. Just my luck I guess.

Greetings fellow foggers,

We’ve recently ordered over 300 of the Dell Latitude 3330 for the district I work for. I’m attempting to upload a new image via FOG, however whenever I try to do this, FOG comes up with “No Partitions Found” and errors out. I’ve tried multiple kernels all with the same problem.

Now, these dells come standard with the HDD mode in Raid which I’ve set it to AHCI which STILL hasn’t resolved my issue. When I look in Disk Management, I have 1 hard disk with 2 partitions, one of which is the 100mb Win 7 partition that is installed.

Does anyone have any knowledge of imaging with this model of laptop or if anyone has any information that could point me in the direction of resolving, I would appreciate it.

Thanks.

I would check your kernal. I ran into this problem and assumed that it was the 100 mb partition that was mucking everything up, turns out it was actually the kernal. Once I found a new kernal that worked, I was able to upload all my Win 7 images using the Single Partition-Resizable. Hope this helps.

You can have multiple kernels installed on your system, however you need to add the kernel location to the host. For example fog/kernel/kernel name would be what I would input under the host settings.

If you don’t find a kernel that works with your machines, you’ll have to compile your own, which is out of my league. Perhaps someone with a bit more knowledge on building kernels can step in here.

Is this your original fog server? We had an issue in another district when migrating certain images off to another fog server and when manually recreating the image definitions, it would error out with the same message. We ended up having to migrate the entire /images directory versus just the select images that were used at that site.

Once you applied the kernel to the host group, have you selected an individual host to verify the settings are indeed missing? This could be just a funny display issue with PHP, I know I had an issue in the past with setting kernels and even though it would visibly disappear, it was still bringing down the correct kernel that I specified.

There are multiple kernels available for download. I would suggest taking a look at the list of working devices ([url]http://www.fogproject.org/wiki/index.php/WorkingDevices[/url]) many of which have notes on the models of which kernels work. If they aren’t working and are not listed, you’ll have to do some testing. In my district when working with kernel testing, I was sure to rename the kernel to identify which model I was testing it on as bzImage is the standard name and will overwrite your existing kernel unless you specify otherwise.

If I recall, you can manually add a host by MAC and also set the kernel and arguments from the host settings page.

Hope this helps.

Greetings fellow foggers,

I’m wondering if anyone can offer me any advice on the configuration of WOL with Cisco switches. Versus getting into extreme detail, is there any particular port or noticeable configuration that must be made on the switches to allow this to work?

The problem were having is WOL WAS working if they were on the same subnet as the FOG server, however the FOG server resides on our server VLAN and all the client PC’s on whichever VLAN based on the switch. We’ve added the IP Helper Addresses on each switch to point back to the FOG server. I can image without a problem, I just cannot for the life of me get WOL to work. Here’s a few things I’ve checked and verified:

1.) Under Fog Settings, I have made sure that the WOL_HOST and WOL_Path are correct.
2.) I went as far as editing the WOL.php and referencing the correct broadcast addresses for my Class A network. (I used a subnet calculator to be certain).
3.) I checked the config.php information to verify that all was correct and indeed all the information there is correct.
4.) I have tried manually running a WOL command via http://[COLOR=#3366ff]FOG_WOL_HOST[/COLOR]/[COLOR=#3366ff]FOG_WOL_PATH[/COLOR]?wakeonlan=[COLOR=#3366ff]MAC [COLOR=#000000]and that is not working either.[/COLOR][/COLOR]
[COLOR=#3366ff][COLOR=#000000]5.) I checked to make sure that WOL.php is being called correctly and I’ve confirmed that it IS being called correctly. [/COLOR][/COLOR]

[COLOR=#3366ff][COLOR=#000000]I’m completely stumped…[/COLOR][/COLOR]

Any help would be appreciated.

I ran into a similar issue, but only on one model of laptop, Dell E6510. I tested the same Windows 7 image on another model (HP) and it worked and uploaded as NTFS versus Raw. If anyone gets any information on how to fix this issue, it would be greatly appreciated. Again - Windows 7 64 bit - NTFS File System according to Windows and Partition Magic - Fog only sends up as Raw regardless of image type (Single Partition/NTFS Resizable, Multiple Partition/Single Disk).

Thanks.

I decided to try a few different kernels until I found one that worked. I’ve now set up my FOG with a different kernel for each machine type that I have after testing out which works best.

That’s odd Astrouga, maybe it’s dependent on the machines? I’ve never once had a problem with it, but as you said, I could be one of the rare ones from the sounds of it. Thanks for the info

Depending on your install of Windows 7 will determine what image type you can select. Most of the major manufacturers have that little recovery partition that is preloaded into the OEM versions of Windows 7 that comes with the machines, therefore you either have to CAREFULLY remove the recovery partitions (there are many guides on the internet detailing this, but use with caution) or upload as Multiple Partition - Single Disk. However, if you are using a stand-alone install of Windows 7, the Single Disk - NTFS Resizable works just fine.

Again, I want to echo if you’re considering deleting the recovery partition to be very careful in doing so, depending on the OEM install, that partition may also contain the Bootmgr and other necessary startup files, so proceed with caution.

I’m actually having the same exact problem myself. My thread and previous discussion can be found here:

[url]http://fogproject.org/forum/threads/deploying-too-fast.972/#post-4769[/url]

Hmm, I’ll have to take a look. We orinally had our FOG server installed on a standalone 4 GB 2.3 GHZ box with a single 10/100 card installed and it was working fine. I recently got my hands on a pretty hefty server to use instead with quad nics, of which I still am only using 1 nic as I don’t see it making a huge difference by bridging these and using all 4. I’m not too familiar with configuring the switches, but what would be the ideal situation for FOG to work?

So is there a setting or change that can be made to auto-accept pending MACs? I see this being a huge pain in the rear as I’m running primarily 1200 laptops and versus having to select each host one by one and approve the pending MAC, it’d be much simpler to just have it auto-register and approve with host registration.

Update
It would appear that this issue is hit or miss on the same as well as different models of machines. Just now, I was attempting to deploy an image and it’s freezing at 1% still and claiming to be pushing at 7 GiB. I decided to plug the machine into a 10/100 switch and the same image and the machine that I was having problems with is now deploying fine. Is there anyways to throttle the speeds coming from the server?

I’m not familiar with manually pulling down an image. Is there a guide to this that I can test this out?

Steady 650 MiB/Min

I can upload an image without a problem.

Update
I’ve also tried reverting back to .29 version of FOG with no luck. It really boggles my mind on how UDPCAST works but NSF doesn’t.