Posts made by astrouga

Myke:

I’ve been using the .33 beta to install 4k drives for several weeks. The latest trunk will let you do the image upload/download, so give it a try if you just need to get the task done. Otherwise you’ll need to wait a while until the developers finish up with all the code. They are pretty busy, but a lot of progress has been made in the last 30 days.

If you decide to give the beta a try, I’d recommend that you set up a spare pc so you don’t destroy your current fog server. You have a couple of options is you decide to try it. Easiest would be to do a clean install of Fog .33. Of course, if you want to try to migrate your db over, you could always install .32 on the spare machine, backup the db and set it up, then upgrade to .33. That would also give the developers another data point for bug testing. You can read about .33 and post your results here:
[url]http://fogproject.org/forum/threads/bugs-in-fog-0-33.631/[/url]

If you need help, just let us know.

I got a 3.4 kernel built and it works with my 0.33 beta FOG server. The imaging issues I had with this nic are now resolved. I’ll post a follow-up with the process next week.

What options do you have selected for the image definition? I can’t remember where fog 0.32 stores the OS type(should be windows 7) and image type definitions (multiple partition, single partition, raw image, …). What do you have selected for those? Also, is there anything different about this particular image? Do you have the 100MB Windows partition on it?

My results are the same as falkos. I assume the reports section will get addressed after the key features, but just in case, I’ll go ahead and report that none of them work for me. Also, I haven’t tried playing with snapins or printer management yet. Let us know what to test with each update.

Couldn’t you just store them in another folder and create soft links to them from the tftpboot folder? I haven’t tried it, but I suspect it would work. Just need to make sure the perms are the same.

chad-bisd, I’ll give it whirl. I’ll see if I can use your instructions from the old forums.

Update: first run through… Kernel panic… I didn’t see any obvious issues. Suggestions? Things to watch out for?

Is TFTP working? What happens when you PXE boot the clients? Do you get to the FOG menu?

Give us a little more info about your XP image – how is the disk structured and what options did you use to define your image?

Sounds like you need to modify your existing DHCP server so it can point to your FOG server:

[url]http://www.fogproject.org/wiki/index.php/Modifying_existing_DHCP_server_to_work_with_FOG[/url]

[quote=“Davis SHula, post: 3523, member: 1144”]I am getting this error.
-----Volume not found--------
Can’t read the following [I]volume[/I] file
/(path)/(imagename).001[/quote]
You’ve gotta give us more information here. What is your setup, what are you trying to do, when are you getting the error?

–astrouga

Draylorre, did you get this figured out?

I have imaged Optiplex 755’s running Windows 7 many times with and without the 100MB system partition. I have never had any issues when I use the “Multiple Partition - Single Disk” option.

–astrouga

I have these nics in some new Dell Optiplex 990 systems. Imaging these systems stinks. It starts out speedy, but over time the speed just continues to slow to a crawl. What should take 20 minutes takes hours.

All other systems I image on the same networking equipment and server are pretty quick. I am considering building a custom kernel to see if I can resolve the issue. I’ll probably just wait until .33 is finalized though because these systems also have 4K disks and that is not supported in other versions of fog.

Please do post your progress on this issue as you go. Thanks.

–astrouga

More details:
This is a common issue that keeps coming up in the forums. You install 12.04, install fog and reboot and then TFTP times out.

Look in your /var/log/syslog file and you’ll see something like:
[Code]
May 22 14:16:22 yourServer in.tftpd[968]: cannot resolve local IPv4 bind address: 0.0
.0.0, Name or service not known
May 22 14:16:22 yourServer cron[1003]: (CRON) STARTUP (fork ok)
May 22 14:16:22 yourServer kernel: [ 19.271357] init: tftpd-hpa main process (968)
terminated with status 66
May 22 14:16:22 yourServer kernel: [ 19.271374] init: tftpd-hpa main process ended,
respawning
[/code]
Your nic doesn’t have an IP address when tftpd-hpa starts, so it isn’t going to work. Just do this from a terminal window:
[Code]
sudo stop tftpd-hpa
sudo start tftpd-hpa
[/code]
This is a “confirmed” bug in 12.04.

–astrouga

This is a common issue that keeps coming up in the forums. You install 12.04, install fog and reboot and then TFTP times out.

Look in your /var/log/syslog file and you’ll see something like:
[code]May 22 14:16:22 yourServer in.tftpd[968]: cannot resolve local IPv4 bind address: 0.0
.0.0, Name or service not known
May 22 14:16:22 yourServer cron[1003]: (CRON) STARTUP (fork ok)
May 22 14:16:22 yourServer kernel: [ 19.271357] init: tftpd-hpa main process (968)
terminated with status 66
May 22 14:16:22 yourServer kernel: [ 19.271374] init: tftpd-hpa main process ended,
respawning
[/code]

Your nic doesn’t have an IP address when tftpd-hpa starts, so it isn’t going to work. Just do this from a terminal window:
[code]
sudo stop tftpd-hpa
sudo start tftpd-hpa
[/code]

This is a “confirmed” bug in 12.04.

–astrouga

I just stopped and started tfpd-hpa:
[code]
sudo stop tftpd-hpa
sudo start tftpd-hpa
[/code]

That is a great idea. It would be helpful in managing images.

I reinstalled my systems with Win7 and kept the 100MB system partition. Using the “Single Partition” option, the image uploads succeed and the clients reboot properly. I cannot image any systems that do not have the 100MB system partition though.

–astrouga

[quote=“Dean211, post: 3621, member: 411”]@astrouga
Have u tried setting the OS type to Vista.[/quote]

Yeah, I changed the OS setting in the image definition to Vista, just to test. Blue screen flashes, like the others, except it tries to write to the images directory and fails. It spit out an ftp error. I didn’t look at it closely because though. I’ll see what it says in a bit.

UPDATE: OK, if I change the OS to Vista, things proceed as I mentioned above. Right after the “* Resizing NTFS…Done” message, I get the following messages looping:
[code]

• unable to move /Images/dev/macaddress to /images/imagename
  FTP Host: (server IpAddress here), Error: ftp_rename(): RNFR command failed.
  [/code]
  This just goes on until I manually power-cycle the client.

I think if this trick ever works, it really isn’t meant to.

–astrouga

[quote=“Blackout, post: 3603, member: 1”]Could you please verify that this wasnt a file system issue by running chkdsk a few times and trying the single partition upload. I havent changed any of the Windows 7 code, so there shouldnt be any issues if 2 partition works.[/quote]

Trunk 875. I can’t get “Single Partition” imaging to upload. I tried two different Win7 64-bit systems with no 100MB partition. I ran chkdsk 3 to 5 times on each before attempting to upload. In both cases, the blue progress screen flashes for a fraction of a second. No file is actually written to the server. The clients reboot and come up fine.

After the failed “Single Partition” efforts, I tried imaging both systems using the “Multiple Partition - Single Disk” Option and both tasks worked perfectly. Image stored on server, client rebooted and came up OK.

Suggestions?

Thanks for making the task upload status change. It works and is useful.

–astrouga

Jigar:
I would use the multiple partition option. Leave the OS set to Windows 7. It never fails.

I think kirksec is right regarding the single partition settings. I have only ever been able to get it to work in that situation. In the past it was always problematic for me so I stopped using it.

–astrouga