Deployment issues on some Dell 740s and 520s
-
[quote=“cadyfish, post: 35349, member: 24458”]When you said
Are they the same model and image?
Also are they the same hardware (including hdd size/manufacturer) & bios wise?
Did you do anything different with them?[/quote]Yes, the image is the same for both machines, they are both Optiplex 740s, one might be slightly different as far as CPU or something.
BIOS on the one that worked was like 2.1.9 and i updated the other from 1.1.something to 2.2.7(newest).
EDIT: Not sure on the hard drives, I think they are the same size, shouldnt matter my image is like 15gb and the drives are atleast 60gb in size, the image is set to single part/single disk in fog.
I have been reimaging them with FOG for years, had no issues until now. I will try and do more testing today.
EDITS
It seems the machine that works was built in 2009 vs the one that don’t work was in 2007.
updated bios from 2.2.7 on non working to 2.1.9 still no luck.Well I thought I would try to upload it using the PartImage imager, but according to Tom on the forums they have it forced to use PartClone, which is a bummer, I think it would be nice to be able to switch between imagers, however PartClone seems to be much better. So needless to say that this didn’t work and I am out of ideas.
Anyone have any suggestions?
-
As a temp patch by I am going to upload the image to a .32 server and move it to my production server as a partimage image. This should work. Will post back if doesnt.
EDIT
Didnt work, really thought this should have. Going to have to run 2 fog servers while i push the images back out to the problem computers.would be really nice if i could upload using PartImage on fog 1+.
-
For those wonder what error i get trying to use PartImage. Here is a screen shot.[IMG]http://ruppnet.net/fog740partimg.jpg[/IMG]
-
This sounds like an issue with the image and the partition layouts.
Your partition layout on the “new” system’s hard drives is different than what is expected.
When you created the “resize” image, how did you resize the original disk?
-
[quote=“Tom Elliott, post: 36144, member: 7271”]This sounds like an issue with the image and the partition layouts.
Your partition layout on the “new” system’s hard drives is different than what is expected.
When you created the “resize” image, how did you resize the original disk?[/quote]
Not 100% sure I follow, but here is what i did.
Deploy image to working 740 from production server. ( single part/single disk image)
switch over to my new .32 server
register the host
upload as single disk/single part
copy image to production server
switch back to production server
schedule image deploy from new file (i did chmod on the permissions for the file so it matches the rest in the /images directory)
didnt work, tried debug and thats where the image came from.Do you have any thoughts on the original post?
in my testing it seems that no matter the kernel or bios version it can always see the network and the hard drive, it appears to be directly an issue with partclone.Should pull the hard drive from a not working machine and try to image that drive in a working machine?
Thanks,
-
did you set the format to partimage on the image profile?
-
[quote=“Junkhacker, post: 36178, member: 21583”]did you set the format to partimage on the image profile?[/quote]
Yes I did, forgot to mention that in the post before. I did this on the production server I pushed from
-
Is it possible that the issue is that the computer the image came from has a larger hard drive then the destination computer? I thought the single partition option was supposed to support this, pending that your image isnt larger than the disk. This is in thought to the original problem.
-
Well, I tried to resize the partition before uploading to a small size and then try deploying it, still didnt work.
-
If the smallest size the image can be (windows 7 defaults base install sysprepped and all is 8.9GB) is larger than the disk you’re trying to put the image on, it will not work.
If you resize the partition before FOG get’s to resize it, the partition is marked that it’s already shrunk and fog Cannot do anything with it. So let’s say you make a partition size of 40GB as the shrunken state, and you try putting the image on an exactly the same size, in 1.2.0 I made the partition size to 99% of the full size of the partition, so you’d end up with around a 39GB partition which is smaller than 40GB and the image would not deploy. I have since found and corrected this issue in SVN. That said, with the release of 1.0.0 we went with partclone as your primary upload method. We are still supporting partimage for legacy compatibility reasons. If you’d be willing you can send me your gmail address in a pm and I’ll see if I can help fix the image for you.
Hopefully this helps you out too. If you’re willing, try out SVN and see if your image starts working. There’s always a chance it won’t work and you’re left in a state no different than you currently are. However, there’s also the chance that this may help you out. You’ll also get to see some of the work we’ve been putting forward for 1.3.0 or whatever it’s labeled when we release.
-
[quote=“Tom Elliott, post: 36348, member: 7271”]If the smallest size the image can be (windows 7 defaults base install sysprepped and all is 8.9GB) is larger than the disk you’re trying to put the image on, it will not work.
If you resize the partition before FOG get’s to resize it, the partition is marked that it’s already shrunk and fog Cannot do anything with it. So let’s say you make a partition size of 40GB as the shrunken state, and you try putting the image on an exactly the same size, in 1.2.0 I made the partition size to 99% of the full size of the partition, so you’d end up with around a 39GB partition which is smaller than 40GB and the image would not deploy. I have since found and corrected this issue in SVN. That said, with the release of 1.0.0 we went with partclone as your primary upload method. We are still supporting partimage for legacy compatibility reasons. If you’d be willing you can send me your gmail address in a pm and I’ll see if I can help fix the image for you.
Hopefully this helps you out too. If you’re willing, try out SVN and see if your image starts working. There’s always a chance it won’t work and you’re left in a state no different than you currently are. However, there’s also the chance that this may help you out. You’ll also get to see some of the work we’ve been putting forward for 1.3.0 or whatever it’s labeled when we release.[/quote]
PM Sent
-
For anyone that is following this thread, this issue has been resolved and should be included in the 1.3.0 release.
