1 2 Previous Next 15 Replies Latest reply on May 25, 2010 2:18 PM by cgodden

    HII image deployment to Lenovo M58

    Rookie

      I am trying to delpoy our HII image to new Lenovo desktops M58.  I am able to pxe boot to the network and the STATA drivers and Network drivers have successfully be added to WinPE.  The deployment template goes though the steps of deploying the image and running sysprep, when the machine reboots, Windows does not start the machine is in a loop, rebooting, then show the "Windows did not start properly" menu and option (safe mode ect) does not work and the machine reboots.

       

      Any help suggestion would be greatly appreciated, I am assuming there is an issue with the OS image, but this same image works fine on M57 and T400's.

       

      Liz

       

      PS:  the image is Windows XP sp3

        • 1. Re: HII image deployment to Lenovo M58
          Employee

          Perhaps the source machine is IDE and the target machine is SATA? Or if the source machine is SATA, it is likely to have an older version of the SATA driver that doesn't support the newer SATA controller found in the target machine...

           

          Either way, unless you have done something to inject a SATA driver at deployment time, a reboot loop will result as the target machine reboots into mini-setup. The sequence of events will be deploy image / reboot from hard drive / WinXP splash screen / blue screen (code 7B) / reboot / windows did not start properly / WinXP splash screen etc. Safe mode crashes as well. The blue screen only appears for a fraction of a second and you may - just possibly - be watching the spectacle without noticing it.

           

          You don't mention that you did something to inject a new SATA driver, so if you allow me to speculate that you didn't, I suppose we know what might be going wrong.

           

          What you can do to salvage the situation is use the capturemsd / injectmsd tools that come with the HII whitepaper. Read up on them in the document.

           

          Let me know how you get on...

          • 2. Re: HII image deployment to Lenovo M58
            Rookie

            Thanks Jan, that souds right, as we are fairly new at implementing LANDesk I am sure we have not inject the SATA driver at deployment, I will read up on it and let you know how we go, I am on leave for a couple of weeks so will try it when I get back.

             

            Thanks for your input.

            • 3. Re: HII image deployment to Lenovo M58
              Rookie

              I have the exact same problem, my master image was created on a M55 and I'm trying image and m58 with I get the same problem described by csdefe,

              both machines are SATA. I'm gonna try Jan Buelens suggestion on how to fix it.

              I'll post the results.

              • 4. Re: HII image deployment to Lenovo M58
                Rookie

                I just noticed something after I image the M58 computer I get error : "source folder not found C:\Drivers\6137A2U" then the computer reboots and goes into the loop.

                • 5. Re: HII image deployment to Lenovo M58
                  Rookie

                  OK, I've managed to fix the error "source folder not found C:\Drivers\6137A2U" , but I still have the same problem, I have 4 computer models I'm trying to image but the only one that works is the one I created the image on. could someone with me a hand please?

                  Thanks.

                  • 6. Re: HII image deployment to Lenovo M58
                    Employee

                    It's not clear from what you say above, but I suppose your problem is still the reboot loop? That reboot loop, if my description of it matches what you are seeing, is happening because your image doesn't have a SATA driver - or if it does, it's an older version that doesn't support the target machine.

                     

                    Remember that the hard drive is a special case in HII. Your target can have the "wrong" NIC, display adapter etc and you won't run into trouble because mini-setup can install the right driver for you. But mini-setup can't install your mass storage driver (MSD) because without the right MSD, the machine isn't bootable - the machine crashes before it gets into mini-setup and you get the reboot loop.

                     

                    All of this is described in the HII document, as well as the solutions. You don't mention that you took steps to inject an appropriate SATA driver so I suppose you didn't. One solution is capturemsd/injectmsd. In essence, you run capturemsd on a fully installed target machine, you copy the files produced by capturemsd to the msd subfolder of your machine specific driver folder and you run injectmsd at deployment time.

                    • 7. Re: HII image deployment to Lenovo M58
                      Rookie

                      Jan,

                      I'm still having the loop problem with the m58 machine, I followed the instructions to fix this issues with Capturemsd/injectmsd but the problem persists.

                      When I capturremsd I get 3 files:

                      iaStor1.reg

                      iaStor2.reg

                      IaStor.sys

                      When I opened  iaStor1.reg it looked like this:

                      Windows Registry Editor Version 5.00

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2681&cc_0106]

                      "Service"="iaStor"

                      "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

                      I edited this file to reflect my driver and now it looks like this:

                       

                      Windows Registry Editor Version 5.00

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2681&cc_0106]

                      "Service"="iaStor"

                      "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_27C1&cc_0106]

                      "Service"="iaStor"

                      "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_27C5&cc_0106]

                      "Service"="iaStor"

                      "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2821&cc_0106]

                      "Service"="iaStor"

                      "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2829&cc_0106]

                      "Service"="iaStor"

                      "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2922&cc_0106]

                      "Service"="iaStor"

                      "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2929&cc_0106]

                      "Service"="iaStor"

                      "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_3A02&cc_0106]

                      "Service"="iaStor"

                      "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_3A22&cc_0106]

                      "Service"="iaStor"

                      "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

                       

                      The iaStor2.reg file looks like this:

                      Windows Registry Editor Version 5.00

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor]

                      "Type"=dword:00000001

                      "Start"=dword:00000000

                      "ErrorControl"=dword:00000001

                      "Tag"=dword:00000019

                      "ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\

                        52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,61,00,53,00,74,00,6f,00,72,\

                        00,2e,00,73,00,79,00,73,00,00,00

                      "DisplayName"="Intel AHCI Controller"

                      "Group"="SCSI Miniport"

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor\Parameters]

                      "queuePriorityEnable"=dword:00000000

                      "BusType"=dword:00000003

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor\Parameters\Port0]

                      "AN"=dword:00000000

                      "LPM"=dword:00000000

                      "LPMSTATE"=dword:00000000

                      "LPMDSTATE"=dword:00000001

                      "GTF"=dword:00000000

                      "DIPM"=dword:00000000

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor\Parameters\Port1]

                      "AN"=dword:00000000

                      "LPM"=dword:00000000

                      "LPMSTATE"=dword:00000000

                      "LPMDSTATE"=dword:00000001

                      "GTF"=dword:00000000

                      "DIPM"=dword:00000000

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor\Parameters\Port2]

                      "AN"=dword:00000000

                      "LPM"=dword:00000000

                      "LPMSTATE"=dword:00000000

                      "LPMDSTATE"=dword:00000001

                      "GTF"=dword:00000000

                      "DIPM"=dword:00000000

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor\Parameters\Port3]

                      "AN"=dword:00000000

                      "LPM"=dword:00000000

                      "LPMSTATE"=dword:00000000

                      "LPMDSTATE"=dword:00000001

                      "GTF"=dword:00000000

                      "DIPM"=dword:00000000

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor\Parameters\Port4]

                      "AN"=dword:00000000

                      "LPM"=dword:00000000

                      "LPMSTATE"=dword:00000000

                      "LPMDSTATE"=dword:00000001

                      "GTF"=dword:00000000

                      "DIPM"=dword:00000000

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor\Parameters\Port5]

                      "AN"=dword:00000000

                      "LPM"=dword:00000000

                      "LPMSTATE"=dword:00000000

                      "LPMDSTATE"=dword:00000001

                      "GTF"=dword:00000000

                      "DIPM"=dword:00000000

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor\Security]

                      "Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\

                        00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\

                        00,00,02,00,60,00,04,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,\

                        05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\

                        20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,\

                        00,18,00,fd,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,\

                        00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

                       

                      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor\Enum]

                      "0"="PCI\\VEN_8086&DEV_3A02&SUBSYS_304817AA&REV_02\\3&61aaa01&0&FA"

                      "Count"=dword:00000001

                      "NextInstance"=dword:00000001

                       

                      Anyway my M58 it still not getting the msd driver and it loops, I've attached the iaStor.sys file just in case.

                      Thanks in advanced for your help Jan.

                      • 8. Re: HII image deployment to Lenovo M58
                        Employee

                        For the record, the changes you've made to the reg files generated by capturemsd add all hardware IDs supported by the driver. By default, capturemsd/injectmsd will only work if source and target machines have identical hard drive controllers (sane hw id). By doing what Abel Foelster did, the captured driver should support all hardware ids meant to be supported by the driver.

                         

                        But that's academic if it doesn't get you out of the reboot loop...

                         

                        Let's reexamine one assumption: what does that reboot loop look like exactly? An "inaccessible boot device" loop looks as follows: boot, WinXP splash screen, blue screen code 7B, reboot, windows did not start properly, WinXP splash screen etc. The blue screen only appears for a fraction of a second and I can imagine - just - that you might miss it if you're not specifically looking out for it. But the WinXP splash screen would be hard to miss.

                         

                        If the machine crashes before it gets as far as the WinXP splash screen, the problem is probably nothing to do with the mass storage driver. One useful test would be to change the target's BIOS settings to IDE. If the machine still crashes even though the hard drive is IDE, the problem can't be anything to do with the SATA driver.

                         

                        Could it be a HAL problem? The usual symptom in the case of a HAL problem is machine hangs (black scree) before it ever gets to the WinXP splash screen. I don't know that a HAL problem can cause a reboot loop. But it's worth exploring the possibility. Did you downgrade the HAL, as suggested in the HII document? Have you tried the new HalConfig? I don't know that you can get an M58 into the kind of HAL trouble that the new HalConfig is meant to avoid, but again, maybe it's worth trying...

                        • 9. Re: HII image deployment to Lenovo M58
                          Specialist

                          I have run into similar issues with the X61s and X60s laptops. In that instance we were able to set the SATA Controller mode to Compatibility instead of AHCI. I am not sure if it applies to the desktops but might help.

                          • 10. Re: HII image deployment to Lenovo M58
                            Rookie

                            Unfortunately the Desktops do not have this option in the BIOS, we have use this option for our Notebooks,  We are currently working on injecting the drivers into the image following Jan advise.

                            • 11. Re: HII image deployment to Lenovo M58
                              Rookie

                              Thanks Jan, we have been successful.  We have downloaded the lastest SATA drivers from Intel and, following the info in the HII whiltepaper added the following into the sysprep.inf file in the build mass storage device section.  This has solved the issue with imaging out Lenovo notebooks as well, there is no need to change the BIOS for the T400 to compatibilty.

                               

                              [Sysprep]
                              BuildMassStorageSection=Yes
                              [SysprepMassStorage]
                              PCI\VEN_8086&DEV_2681&CC_0106=c:\drivers\sata\iaahci.inf
                              PCI\VEN_8086&DEV_27C1&CC_0106=c:\drivers\sata\iaahci.inf
                              PCI\VEN_8086&DEV_27C5&CC_0106=c:\drivers\sata\iaahci.inf
                              PCI\VEN_8086&DEV_2821&CC_0106=c:\drivers\sata\iaahci.inf
                              PCI\VEN_8086&DEV_2829&CC_0106=c:\drivers\sata\iaahci.inf
                              PCI\VEN_8086&DEV_2922&CC_0106=c:\drivers\sata\iaahci.inf
                              PCI\VEN_8086&DEV_2929&CC_0106=c:\drivers\sata\iaahci.inf
                              PCI\VEN_8086&DEV_3A02&CC_0106=c:\drivers\sata\iaahci.inf
                              PCI\VEN_8086&DEV_3A22&CC_0106=c:\drivers\sata\iaahci.inf
                              PCI\VEN_8086&DEV_2682&CC_0104=c:\drivers\sata\iastor.inf
                              PCI\VEN_8086&DEV_27C3&CC_0104=c:\drivers\sata\iastor.inf
                              PCI\VEN_8086&DEV_27C6&CC_0104=c:\drivers\sata\iastor.inf
                              PCI\VEN_8086&DEV_2822&CC_0104=c:\drivers\sata\iastor.inf
                              PCI\VEN_8086&DEV_282A&CC_0104=c:\drivers\sata\iastor.inf
                              Thanks for your assistance it was greatly appreciated.
                              • 12. Re: HII image deployment to Lenovo M58
                                Rookie

                                Thank you so much csdefe this has fixed my problem!!

                                • 13. Re: HII image deployment to Lenovo M58
                                  tdavenport Specialist

                                  Abel or Jan,

                                   

                                  Concerning the "Source Folder not found" error. What did you do to fix it? I've checked and rechecked the path and it is correct. If I look at the copydrivers log, it looks like the program can get to the directory. If I copy the path in the error log and paste it into explorer, it connects just fine. The path is correct. Here's a copy of the log file....

                                   

                                  CopyDrivers V1.6, command line parameter(s): 1
                                     /c
                                  H:\HIITools\copydrivers.ini,section [Config]:
                                     DriversSource = \\XXXXX-ldpackage\OSImages\Drivers
                                     DriversTarget = C:\Drivers\PnP
                                  source: \\XXXXX-ldpackage\OSImages\Drivers, target: C:\Drivers\PnP
                                  WMI info: Manufacturer=Hewlett-Packard, Model=HP Compaq 6000 Pro SFF PC, Version=
                                  H:\HIITools\copydrivers.ini,section [Models]:
                                     HP Compaq dc5100* = DC5100
                                     HP Compaq nc6320* = NC6320
                                     HP D530* = D530
                                     HP Compaq dc5800* = DC5800
                                     HP Compaq dc5700* = DC5700
                                     HP Compaq 6000* = 6000
                                     HP Compaq 6730b* = 6730b
                                     HP Compaq 6710b* = 6710b
                                     8215D6U = M52
                                     EVO* = EVO
                                     HP Compaq dc7600* = DC7600
                                     nc6340* = NC6320
                                     8171* = S51
                                     8183V* = S50
                                     OptiPlex GX280 = GX280
                                     HP Compaq nx63* = NC6320
                                     HP Compaq tc4400* = TC4400
                                  Match on line 6: HP Compaq 6000*
                                  21:48:11 Start copy from \\XXXXXldpackage\OSImages\Drivers\6000 to C:\Drivers\PnP
                                  Source folder not found: \\XXXXXldpackage\OSImages\Drivers\6000

                                   

                                  This directory exists and is accesible.

                                   

                                  There are sub directories. Would this be an issue? I don't need to dump all of the inf's into the root do I? That would be a mess.

                                   

                                  Any ideas?

                                   

                                   

                                  Thank you!

                                  • 14. Re: HII image deployment to Lenovo M58
                                    tdavenport Specialist

                                    Well, I answered my own question.

                                     

                                    Copy drivers was attempting to access copydrivers and the drivers themselves via a UNC path. Since I don't have a null session share for OSD (no multicasting thank you), access was denied. I changed the copydrivers.ini file to use the H: drive - the mapped drive letter in WinPE. Now my copydrivers.ini file reads:

                                     

                                    [Config]
                                    DriversSource=H:\Drivers\
                                    DriversTarget=C:\Drivers\PnP
                                    [Models]
                                    HP Compaq dc5100*=DC5100
                                    HP Compaq nc6320*=NC6320
                                    HP D530*=D530
                                    HP Compaq dc5800*=DC5800
                                    HP Compaq dc5700*=DC5700
                                    HP Compaq 6000*=6000
                                    HP Compaq 6730b*=6730b
                                    HP Compaq 6710b*=6710b
                                    8215D6U=M52
                                    EVO*=EVO
                                    HP Compaq dc7600*=DC7600
                                    nc6340*=NC6320
                                    8171*=S51
                                    8183V*=S50
                                    OptiPlex GX280=GX280
                                    HP Compaq nx63*=NC6320
                                    HP Compaq tc4400*=TC4400

                                     

                                    Works like champ.

                                     

                                    I guess if I had a null session share created, then I wouldn't have had the issue.

                                    1 2 Previous Next