Posts made by StevenT

@Wayne-Workman @Tom-Elliott Interesting development. After wiping the drive everything appears to be working. In fact, I am even able to restore the original image that wasn’t working before. I believe the issue was not with the source master PC and the partitions on it, but I think FOG was having trouble trying to remove the partitions from the destination PC. I suspect the OEM partition #1.

@Wayne-Workman We are going to start over with a new machine. We are going to keep the original PC as reference for configuring the second. Before we start I’m going to low level format the beast and then try to image it as soon as the OS is installed to make sure it works. Not sure why it would have a problem from the factory, but hopefully that will fix it.

@Wayne-Workman So this is a brand new OS straight from the factory. No reinstall. No changes made in the BIOS
and never touched by FOG until the backup. Why would it have pieces of GTP ‘left’ on the disk?

@Wayne-Workman So running fixparts will NOT wipe the drive data? When would a drive be “previously GPT”? When it used to be Windows 8 and reinstalled as 7, ect?

@Tom-Elliott In addition I would be pretty surprised if the partitions were the issue. We did not reinstall the OS. We only configured it as needed from the factory. Its a brand new pc.

@Tom-Elliott Alright we’re stuck here. This is a master PC we have configured as needed. It is the only working copy we know of since we cannot restore the data to another workstation. I’m concerned about running the partfix because I dont know if it will wipe the drive or not and I’m not sure if that is what is causing the problem or not.
Is there anything else before we go this route? Is there a chance that partimage would work better than partclone in this instance?

@Tom-Elliott Not familiar with the utility (if you hadn’t guessed already). This should not lose any data, correct? Its not recreating the partitions, right?

@Tom-Elliott So I just start the fixparts utility, ‘w’ to save (without changing anything else) and then try to image again?

@Tom-Elliott Wasn’t sure what you wanted me to do once I started the fixparts app, but I check in Windows and it does not list the disk as GPT.

@Tom-Elliott is it just ‘fixparts sda’ ?

@Tom-Elliott This is a pretty standard setup for us. There is OEM and recovery partition and then two windows drive letters. Is there a way around the issue?

@Wayne-Workman Were you able to review the images? Did anything stand out?
Thanks.

@Wayne-Workman Not sure if that worked. If not I have the images here as well:

http://imgur.com/3hAvede
http://imgur.com/sM4V4Fg

@Wayne-Workman Here is the debug information you requested and diskpart info from the Windows as well. 

@Wayne-Workman Sorry about the delay. I’m getting ready to do the debug process now. This is the first I time running the debug. I’m concerned about the way the description is worded on the web page and I do not want to overwrite my master hard drive by mistake. For the master PC I want to select the 'Upload Debug", correct?

@Wayne-Workman I think I’ve narrowed it down to either the source hard drive. Its either bad (which i doubt), there is a problem with the partitions on the source hard drive or FOG is unable to support the source hard drive or partition setup.

-I have tried to capture deploy using the native XE2 hardware platform and failed.
-I have tried to use a current patch version of FOG to capture / deploy using the XE2 hardware and failed.
-I have tried to move the hard drive to an older hardware platform that worked previously and failed.
-To make sure FOG still worked at all I tried to backup and restore and completely different 7020 and it worked fine.

There is sometime about this drive or partition setup causing the problem.

@Wayne-Workman We’ll try that next to make sure. It *appears the master disk is working ok. It boots, runs the OS, ect fine. We have also tried to deploy the image taken from the master to 3 different XE2 PCs with no luck. I wouldn’t think its a hard drive issue, but we will make sure.

Also I have been able to image and deploy other PCs on this FOG server. I’ll admit the image was taken from and restored to the exact same PC (backup/restore), but that at least proves the server is ABLE to take and deploy an image.

@Wayne-Workman Good idea. We are in the process now. The deploy just failed so we are trying to use alternative hardware for the entire process now - upload image from master HD in an alternative PC and deploy the image to slave HD in an alternative PC. The alternative PC we are using we know worked in the past.

@Tom-Elliott To reiterate what @george1421 said our final attempt was with a brand new OS / FOG installation upgraded to trunk via SVN. I registered only the master / slave hosts, uploaded the image and then tried to deploy it. Even with the brand new upgraded install we were getting an error trying to deploy. That is where we left off.

@Tom-Elliott I installed 1.2.0 and then ran the procedure to upgrade to trunk using the following instructions. I’m not sure if that updates the inits as well.

https://wiki.fogproject.org/wiki/index.php?title=SVN