Solved Bugs in FOG 0.33
-
Any solutions? I thought the .33beta allowed EXT4 imaging?
-
I’m going to attempt to throw .33 on a DELL PowerEdge R620 running Ubuntu 12.04 LTS.
All the systems I need cloned are EXT4 and this is my last shot. I will keep everyone informed.
The machines I will be cloning are HP Z620’s running Ubuntu 12.04 LTS- Install went smooth.
- Imaged first computer/workstation. FOG detected the partitions as EXT3FS even though they are EXT4… any work around?
-Partitioned first computer/workstation as EXT3. Booted fine.
-
Found a visual bug on the login form. If you switch languages, the names and fields would get all out-of-wack. The diff file I have attached should fix the issue (tested in the latest FF, Chrome and IE 9), just add a .diff to the end if you’re using svn.
[url=“/_imported_xf_attachments/0/216_fog.css?:”]fog.css[/url]
-
This post is deleted! -
[quote=“Jesus Jordan, post: 9263, member: 2573”]Hey guys. I’m running 0.32, not 0.33 but I wanted to share some insight to help the Windows 8 support for 0.33.
I set up a virtual machine running Windows 8 Enterprise with a single partition and uploaded it to FOG. I ran the fogprep exe which I had to modify because it does not support Windows 8 (I just commented where you check to make sure the machine is running Windows 7 because the registry keys being modified are exactly the same in Windows
and I ran sysprep with my unattended xml answer file. When I tried to download the image to another machine, I received an error at boot saying “Booting… Missing Operating System”. I dug into the fog source code with my boss and discovered that the issue is that there is a method that checks the os version and applies one of several mbr files that you have. Because Windows 8 is not supported and I selected Windows 7 as the host os on the fog web interface, it wrote the wrong mbr to the machine. After we copied the correct mbr from the Windows 8 master image and wrote it to the machine, it booted correctly. There still is a problem, however. The hard drive was not resized properly to the size of the new machine it was being imaged to. The new machine is showing only ~40GB which was the size of the actual fog image. Also, I the fog client is not working properly. It is not renaming the machine or joining it to the domain.[/quote]Hopefully this (windows 8 support) is rectified in version .33 because we are having the same problem. Curiously it does occasionally work but only on certain machines. Also fog client from memory did work, it renamed and installed snapins?
-
We don’t sysprep for the pure fact that we don’t trust our users to make it through the first boot process. . it’s much easier to make an image for a certain model, setup everything just the way we want it and let FOG/Active Directory do everything Post-first boot.
-
Hey guys. I’m running 0.32, not 0.33 but I wanted to share some insight to help the Windows 8 support for 0.33.
I set up a virtual machine running Windows 8 Enterprise with a single partition and uploaded it to FOG. I ran the fogprep exe which I had to modify because it does not support Windows 8 (I just commented where you check to make sure the machine is running Windows 7 because the registry keys being modified are exactly the same in Windows
and I ran sysprep with my unattended xml answer file. When I tried to download the image to another machine, I received an error at boot saying “Booting… Missing Operating System”. I dug into the fog source code with my boss and discovered that the issue is that there is a method that checks the os version and applies one of several mbr files that you have. Because Windows 8 is not supported and I selected Windows 7 as the host os on the fog web interface, it wrote the wrong mbr to the machine. After we copied the correct mbr from the Windows 8 master image and wrote it to the machine, it booted correctly. There still is a problem, however. The hard drive was not resized properly to the size of the new machine it was being imaged to. The new machine is showing only ~40GB which was the size of the actual fog image. Also, I the fog client is not working properly. It is not renaming the machine or joining it to the domain. -
Dealman, non-sysprep’d images have worked in the past, and there are plenty of people that for whatever reason choose not to sysprep, so we want to insure that functionality still exists. We’ve already encountered some issues while testing non-sysprep’d images, but more tests with detailed step by step documentation can help us track down the bug a lot faster.
Falko, give it a try. I haven’t tested that functionality myself, and I haven’t heard of anyone else testing it, and I know the database schema changed with 0.33, so go ahead and try.
-
just to double check, when I set up my FOG 0.33 test vm, all I need to do is Import the Host Inventory cvs from my FOG 0.32 box? Following the format provided from the Web Interface cvs ‘Import example’ sheet?
-
[quote=“BryceZ, post: 9205, member: 2”]Always looking for more testers :)[/quote]
Cool count me in. I just setup a xenserver environment so i can do testing all sorts of things outside of my vmware environment. I have a question while i’m downloading the latest tarball why do we need to test non-sysprep images?
-
Always looking for more testers
-
are you still looking for testers?
-
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.
-
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!
-
[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] -
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] -
Please see this thread in regards to NTFS Resizing testing: [url]http://fogproject.org/forum/threads/ntfs-resizable-testing.1102/[/url]
-
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
-
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 -
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
