Ric_ Posted August 27, 2009 Posted August 27, 2009 I've taken an image of a T60 Thinkpad using FOG 0.27. All seems well. However, deploying this image is proving troublesome. The laptops image in their usual speedy manner but then just sit there after boot... no message or anything. I have used UBCD to check that the partitions are there (which they are - one for the OS and one for the IBM service partition) and the correct one is marked as active. I have re-imaged a single laptop on its own but the same problem occurs. I've tried booting into the service partition... again the same problem. I read the post at http://www.edugeek.net/forums/o-s-deployment/39873-error-loading-o-s.html thinking it may be the same problem but I cannot find a BIOS option to change the hard disk mode I really need some help... I'm running out of ideas and need to get these laptops imaged (they are all blank at the moment). This is the last job of the summer as well
morganw Posted August 27, 2009 Posted August 27, 2009 (edited) Is it a sysprep image? If it is just try installing windows, upload image, deploy image to make sure it isn't an issue with the sysprep process. Start with a totally blank drive as well so you don't have any service or restore partitions in the mix. Edited August 27, 2009 by morganw
Ric_ Posted August 27, 2009 Author Posted August 27, 2009 The image has been sysprepped and then FOG has taken an image of the entire drive (i.e. both partitions). The drives on the machines receiving the image were completely blank to begin with. I want the support partition.
morganw Posted August 27, 2009 Posted August 27, 2009 I think some people have had issues with fog and service partitions. I've had a multi-partition image which didn't work quite right, but that wasn't a bootable one like a service or restore and the problem could be fixed through the disk management application in Windows afterwards. I would try it with just one partition so then you know whether you should be directing your attention at the BIOS, SysPrep, or Fog.
sparkeh Posted August 27, 2009 Posted August 27, 2009 Ok to rule out a simple issue, you did choose the correct image type ie "Multiple Partition - Single Disk"
Ric_ Posted August 27, 2009 Author Posted August 27, 2009 Ok to rule out a simple issue, you did choose the correct image type ie "Multiple Partition - Single Disk" Yup... that's the thing... I can see the partition table is correct! I'm just making a DOS boot disk because there's an IBM tool that supposedly fixes similar issues.
sparkeh Posted August 27, 2009 Posted August 27, 2009 Just noticed that someone on the Fog forum has exactly the same issue. No solution but at least someone else has come across this, so perhaps more to do with laptop than FOG?
sparkeh Posted August 27, 2009 Posted August 27, 2009 (edited) Apparently the T-series also have issues with Ghost. Seems there is a solution here at Experts Exchange (but I am not a member so can't see it Edit: seem some posts on other forums about other cloning software having difficulties as well. Some people report success with disabling quick boot in BIOS (if this is an option) Edited August 27, 2009 by sparkeh 1
Michael Posted August 27, 2009 Posted August 27, 2009 I wonder if the service partition contains information specific to that laptop? If you boot from a Windows CD and perform a repair or repair the boot config what happens? Have you tried any alternative imaging products? You could also clone a hard drive directly (without running Sysprep initially) and see if this actually works. Then manually run Sysprep and re-name and join the machine to the domain with an answer file.
Ric_ Posted August 27, 2009 Author Posted August 27, 2009 Went for a walk and got my USB floppy drive from the server room, created a DOS 6.22 boot disk and ran fdisk /mbr The issue is resolved... FOG must mangle the MBR on those machines for some reason. An easy fix but a PITA since I have 30 to set up
round2it Posted September 13, 2009 Posted September 13, 2009 i had issues with ibm imaging. acronis works for these machines but i did have to change the sata to compatability mode in the bios. Dont know if this helps.............
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now