Bugs in FOG 0.33
-
FOG trunk 875 (Ubuntu 12.04 Server)
windows 7 ie9/firefox as can be seen below the IMAGE NAME and actual image name overlap
[IMG]http://db.tt/eJPwkmOD[/IMG]
also just uploaded a Windows 7 Image (normal install with 100mb) with the above settings ( OS: Windows 7 || Image Type: Single Partition (resizable)) The image uploaded successfully (right size on server) and the original machine restored mbr and restarted fine.
when deploying the uploaded image to a pc it only deploys the 100mb partition says its complete and restarts
-
[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
-
Have u tried setting the OS type to Vista.
-
[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
- unable to move /Images/dev/macaddress to /images/imagename
-
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
-
Issues I’m aware of:
[LIST]
[]“Single Partition” (NTFS Resizable) needs love - most uploads work, some deploys do not
[]Multi Partition works - please tell if im wrong
[]FOG Configuration (previosuly known as ‘Other Information’) pages do not exist - they have not been created
[]Various “save” operations in Group Management and other areas do not save
[/LIST] -
[quote=“Blackout, post: 3636, member: 1”]Issues I’m aware of:
[LIST]
[]“Single Partition” (NTFS Resizable) needs love - most uploads work, some deploys do not Agree
[]Multi Partition works - please tell if im wrong
[]FOG Configuration (previosuly known as ‘Other Information’) pages do not exist - they have not been created
[]Various “save” operations in Group Management and other areas do not save
[/LIST]
[/quote]Yes for all of them, on a side note I Imported my host list from my Production Fog machine 0.32 and that worked fine.
I was however unable to do a Full Inventory report error below, this is a highly regarded feature by my team as we use it to track assets
[CODE]Unable to load system configuration information.[/CODE]keep up the good work, thanks
-
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.
-
I installed latest trunk and am able to upload my images with no issues. When I attempt to download my images the computer gets to the blue screen with progress bar for an instant and then instead of starting to download the image the computer just reboots. My .32 fog box works fine. Is this an issue you have seen?
-
[quote=“klasikrkade, post: 3890, member: 622”]I installed latest trunk and am able to upload my images with no issues. When I attempt to download my images the computer gets to the blue screen with progress bar for an instant and then instead of starting to download the image the computer just reboots. My .32 fog box works fine. Is this an issue you have seen?[/quote]
Are using the “single partition” image option?
-
Blackout:
What needs to be tested at this point? Anything you need checked in the latest build?
Thanks again for all the hard work. FOG has really come a long way.
astrouga
-
I will access the sub-menu “PXE Boot Menu” or “FOG Settings” on top of page returns that message.
“FOG DEBUG: FOGPageManager: Class: FOGConfigurationPage, Method: settings, Error: Method not found in class, defaulting to index()”
:S -
Chuck and Jian have been hard at work fixing the NTFS Resize issues for me.
The latest init.gz can be found in SVN or here: [url]http://freeghost.svn.sourceforge.net/viewvc/freeghost/trunk/packages/tftp/fog/images/[/url]
Jian reported
[quote]Test case scenarios we use - all works.Windows 7 1 partition(os) resize
80gb HD - full size partition, 7gb ntfs volume -> 3TB HD - 2TB partition, 2TB ntfs volumeWindows 7 2 partition(100mb recovery and 80gb OS) resize
80gb HD - full size partition, 7gb ntfs volume -> 3TB HD - 2TB partition, 2TB ntfs volumeWindows 7 3 partition(100mb recovery, 50gb OS and 30gb data) no resize
80gb HD - full size partition, 7gb ntfs volume -> 3TB HD - 2TB partition, 2TB ntfs volume[/quote]If you guys could please test Windows Vista & Windows 7 resizable partitions with and without the boot partition.
Please report any errors, screenshots are very helpful, etc
-
Please see this thread in regards to NTFS Resizing testing: [url]http://fogproject.org/forum/threads/ntfs-resizable-testing.1102/[/url]
-
Last time I spoke with the devs it seems we’re still having an issue with non-sysprep images that are resizeable. If people are interested in providing more testing and feedback, here is a list of scenarios to test (taken from Blackout’s todo list):
[LIST]
[]Windows XP - NTFS, Multi
[]Windows 7 x86 - One & Two partition layout - with & without sysprep - NTFS & Multi types
[]Windows 7 x64 - One & Two partition layout - with & without sysprep - NTFS & Multi types
[]Windows 8 x86 - One & Two partition layout - with & without sysprep - NTFS & Multi types
[]Windows 8 x64 - One & Two partition layout - with & without sysprep - NTFS & Multi types
[]Windows Vista x86 - One & Two partition layout - with & without sysprep - NTFS & Multi types (not critical)
[]Windows Vista x64 - One & Two partition layout - with & without sysprep - NTFS & Multi types (not critical)
[]Multicast
[/LIST] -
[LIST=1]
[*]The bug reported by Astrouga could be solved adding error_reporting(0); to the script /var/www/fog/services/Post_Stage2.php, because the main script on the rootfs of the bootable linux waits for a “##” symbol, and it gets “unable to move /Images/dev/macaddress to /images/imagename FTP Host: (server IpAddress here), Error: ftp_rename(): RNFR command failed.##” instead, due to an error on the first ftp_rename() function. This worked for me and should be fixed on next revision.
[/LIST] -
I’ve seen mention that the database is different in 0.33, and there is no possibility of returning to 0.32 after upgrading. My question is: are 0.32 images compatible after upgrading to 0.33? It was also suggested to install 0.33 in a VM, but is that still relevant?
I’m thinking that grabbing from SVN and running the install will be all the configuration I’ll need… is that correct?
Thanks!
-
The database is different and there is no easy way of reverting back to 0.32 ( you might be able to do it manually, but I wouldn’t suggest it to anyone). The images are compatible as we are still using Partimage to collect and deploy images. Running FOG 0.33 in a VM is just a suggestion; 0.33 is still n beta and not really ready for production use (you can use it in production, but again I wouldn’t suggest it to anyone), so the idea is that people wanting to help with bug testing or get a feel for what’s coming will pull down 0.33 and test it in an isolated environment.
-
are you still looking for testers?
-
Always looking for more testers
