Struggling with a Dell Precision T3600, Boot Image does not see Hard drive.

Hi
I recently got a lab of 25 of these stations in and shortly I will be imaging them. I am using the Boot Image (x86) the ones that come with sccm 2012  and I downloaded the sccm driver cab from dell and imported the storage and raid drivers into the
boot image, yet every time I boot winpe to try to image the machine no hard drive is found.
I followed this thread at Dell
http://en.community.dell.com/support-forums/disk-drives/f/3534/t/19460505.aspx
and seeming all these drivers are in the boot image (x86)
Intel(R) C600/X79 series chipset 6-Port SATA AHCI Controller - 1D02
Intel(R) C600 Series Chipset SAS RAID Controller
PERC H310 for Dell Precision
and still now hard drive seen when I boot winpe via sccm pxe.
Does anyone have any of these machines, or any advice for me I REALLY need to solve this, I been struggling for a day so far and getting nowhere fast.
Thanks

Are you using the correct driver for the version of WINPE you are using?
3.1
Built from Windows
7 SP1 code base. 
4.0
Built from Windows
8 code base. 
5.0
Built from Windows
8.1 code base. 
So if you had a boot image based on WINPE 4.0, you would need to use a Windows 8 driver, etc.

Similar Messages

  • Boot image does not exist and cannot read disk label errors.

    Hi - I'm having a problem with installing Solaris 9 4/04 on a Netra T1. The Netra already has Solaris 7. I need to get this set up as a jumpstart server but it can't find the boot image. I'm using a brand new bonafide installation disk - not a copy. The system won't let me install/upgrade to Solaris 9 either. I get an error stating that disk label can't be read. I've tried swapping out the CDROM but I still get the same errors. Does anyone know what or why this may be happening? (Oh - and another strange thing - like I said the CDs are the original but there doesn't appear to be a cdrom/cdrom0/s0 directory. The directory I see is cdrom/cdrom0/sol_9_404_sparc/Solaris_9/Tools)
    ERROR: Install boot image /cdrom/sol_9_404_sparc/Solaris_9/Tools/Boot does not exist
    Check that boot image exists, or use [-t] to
    specify a valid boot image elsewhere.
    and
    Excuting last command: boot cdrom [- nowin]
    Boot device: /pci@1f,0/pc1@1/ide/cdrom@2:f file and args: [- nowin]
    Can't read disk label.
    Can't open disk label package
    Evaulating: boot cdrom [- nowin]@1/ide@e/cdrom@2:f File and args: [- nowin]
    Can't open boot device
    I appreciate any help at all - is there anyone out there who can tell me what I may be doing wrong?
    Thanks

    Hi check that you are booting of the right cd. Make sure it is soalris 9 software 1/2 if that fails then it may well be that your cd is buggered. most likely it is buggered it it cant find the boot image.

  • MDT 32bit boot image does not boot type 2 virtual machine in hyper-v

    I created a type 2 virtual machine on a windows server 2012 R2 and tried to boot it with MDT 32 bit (x86) boot media and it will not boot.
    Same media works if I use type 1 virtual machine .
    Is this expected behavior ? 
    Thanks

    Hi,
    Yes as Gen 2 machines only nsupports only x64 os and the following OS:s
    Windows Server 2012
    Windows Server 2012 R2 
    64-bit versions of Windows 8
    64-bit versions of Windows 8.1
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • G4 not booting...not a hard drive issue?

    I have another post about this, but something new has been added to the mix.
    I've got a last generation power PC mac mini I use in a school environment. I'm looking to get this one working as a new comptuer is not an option.  $ and all.
    The computer froze up, and after a hard restart, refused to move past the "prohibited sign".
    Zapped pram.  nope
    Tried starting from Tiger install disk. nope
    Booted in single user mode, but warning...oof...left the note at school..."waiting for system .....? something" repeated over, and over, and over again.
    Didn't work in single user mode.
    Connect the damage mini using firewire to a working mini.  Checked HD, all good.
    Put the Tiger OS install dvd in the host machine, erased and installed the OS on the damaged mac Mini through firewire.
    The damaged machine, while connected through firewire, restarted, screen came up using the host machine, set up the system per ususal...all looked good.
    Picked the HOST startup disk to reboot.  Ejected the firewire connected mini.  Disconnected, physically the damaged mini.  Shut it down. Then fired it back up.
    The damaged Mine still would not get past Apple logo with spinning progress wheel > leading to "prohibited" sign with spinning progress wheel. 
    During the install of the OS on the damaged machine, I put my ear to the mini and could hear the HD working away.
    BUT...the OS did install, and things were good until I asked the damage machine to rely upon its own innards as opposed to that of the host machine.
    SO...is it possible then that the HD in the damaged Mini, with the brand new freshly installed OS, is OK and that there is another issue.  OR could this still mean that the HD is toast.  I'm truly hoping that it is the HD as that is a more easily remedied problem.
    The machine is scheduled to be dropped off at a local shop next week.
    Fill me with wisdom oh wise ones.
    Thanks!

    Hi
    I wonder whether the problem is related to the Sonnet CPU upgrade. According to their website it's supported by Mac OS X 10.3.5 and higher. It may be that Apple added support for the 7447 G4 variants used in the CPU upgrade in 10.3.5, and earlier versions of Panther simply won't recognise the processors.
    If this is the case, I'm not sure what to suggest other than to reinstall the original CPU card, reinstall the OS and upgrade it to 10.3.5 or later via the web and then reinstall the CPU upgrade. Alternatively you could try and get hold of some Panther discs that you knew were 10.3.5 or later.
    With Protools and the CPU upgrade, it seems you may be limited to 10.3.5, 10.3.6 or 10.3.7
    Did you try updating Panther to 10.3.7 with the hard drive in the other machine before swapping it back?
    Message was edited by: Rodney Culling

  • M30x bios does not detect hard drive, wont boot from HD

    Can someone help me in this issue.
    My Sat m30x wont boot from Hard Drive, instead tries to boot from network.
    Tried to load setup defaults and Hd wont show on the settings
    tried to reistal origin CD software by toshiba and the message no target drive displays
    Can this be a hardware problem, some damaged fisical conection, or is it a bios problem
    thanks in advance for some ligth on this problem

    My M30x has the same problem. I just have used it for 2 months.
    I sent it to the repair center as I was told to do, because it has warranty.
    I'm still waiting for a response from them. I don't know what caused it.

  • Somehow, i have 2 iPhoto libraries which I opened today.  The one with the vast majority of my images does not allow me to export photos.  What can I do to manage this situation?

    With my MacBook Pro, OS X Yosemite, iPhoto 9.6, I find I have two iPhoto libraries.  I discovered this when opening iPhoto today.  One has only a few old images; the other, all current images.  I cannot export images from the current image library.  Can anyone enlighten me as to why I would have two libraries and how to resolve the issue of exporting?

    What happens when you try to export from the library?  Where are you trying to export to? Are both libraries located in the same Place?  If not where are they located.  If on an external HD how is that HD formatted?
    How much free space do you have on your HD(s)?

  • HP Pavilion dv5-1108ax, Windows Vista 32-bit: BIOS Boot Order does not see external eSATA HDD

    I am trying to run some Linux OS (Debian, Ubuntu, Fedora) from my external USB 2.0/eSATA HDD on my laptop. I can boot from a  USB connection but not from an eSATA connection. Is there any chance of updating the BIOS to support booting from eSATA? Is there something I am missing in the BIOS setup menu?

    No the eSata port is not bootable.

  • RD440 Boot Options do not see HDs

    The RAID 5 setup went fine and I can see the drive acknowlegded in the pre-boot. But the Bios does not see the drives as I look in the Boot Device Selection, boot options or SATA portion of Bios. I ran an Xenserver install, the install seemed to go fine, no hick-ups. Was expecting to need to select where to boot from, but can't find any HD to choose. 
    Any idea what I'm missing?

    The redaction tool isn't available in the Standard edition.

  • Build & Capture TS (MDT) - Capture fails at PrepareOS (sysprep) with "Boot Image package not found"

    Hi all,
    I'm searching for a while on this one now... I'm unable to perform a "ZeroTouch" Build & Capture of my reference machine to get a master image, with Capture Media it seems to be working, but this is a manual step...
    While running a W7SP1 Build & Capture task sequence, the "Capture the reference machine" group fails at "PrepareOS". The step before "PrepareOS",  "Prepare ConfigMgr Client" runs without any issues.
    The only error I can find, shows up in the report "OSD - history of a TS":
    ... 0005 that is either already released or we have not connected to it.
    BootImage::ResolveImageSource( pszPackageId, sImagePackageSourcePath, sImageSourcePath), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\bootimage.cpp,732)
    TS::Boot::BootImage::StageBootImage(sPkgID), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,917)
    PreStageWINPE(m_bDebug), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,1363)
    pCmd->Sysprep(bActivate, bMsd), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\main.cpp,270)
    De-Initialization successful
    Exiting with error code 2
    sending with winhttp failed; 80072ee2
    SendResourceRequest() failed. 80072ee2
    Download() failed. 80072ee2.
    Boot Image package not found.
    he system cannot find the file specified. (Error: 80070002; Source: Windows)
    Failed to pre-stage WINPE image, hr=0x80070002
    Unable to sysprep the machine, hr=80070002
    Sysprep'ing the machine failed, hr=80070002
    I've searched the smsts.log file hundreds of times for errors, nothing there... 
    Can anyone give me a clue or just something...? I really don't know what my next step, to make this work, could be...
    Thanks!

    The error Torsten pointed out gave me some clue... After much digging around on the web, I've stumbled upon this
    article which led me into adding the following TS-variables:
    SMSTSDownloadRetryCount: 5
    SMSTSDownloadRetryDelay: 15
    It seems to be working now on all types of hardware...
    Case closed, thank you for the assistance! 
    Let's hope this article can save someone a couple of days... :)
    Wesley

  • Client getting an IP lease on the 64-bit LiteTouch boot image, but not the 32-bit version.

    MDT 2012 U1.  No problem with PXE booting so WDS is not the issue.
    The NIC in question is the Intel I217-LM, which resides on both the new Dell Optiplex 9020 and the Latitude E7440.  I downloaded the Dell drivers and then the Intel drivers and imported them into the WindowsPE drivers folder in the workbench.  Updated
    the boot images to make sure the new drivers were injected.  Both yielded the same result.  I can do everything I need to do when booting to the 64-bit LiteTouchPE_x64.wim boot image,  but not the 32-bit version.  When booting to the 32-bit
    version, I get no IP configuration info at all.  
    When looking at the drivers in MDT, I see only one difference:  the supported OS versions.  The 64-bit driver supports 6.1, 6.1.1, and 6.2.  The 32-bit driver supports only 6.1.1 and 6.2.  Not sure if that's the issue.
    Tried using drvload within 32-bit WinPE to manually inject the NIC driver.  Still no luck.  Ipconfig yields no configuration at all.
    If I can't get these machines to boot to the 32-bit boot images, I can't deploy 32-bit images, unless there's a way of which I'm unaware.
    EDIT:  A little extra background.  My WindowsPE folder has two subfolders called x86 and x64.  Obviously, 32-bit drivers go into the x86 folder and 64-bit drivers go into the x64 folder.  Then in the properties of the deployment share a
    selection profile is selected which points to the architecture-specific folders.

    Specifically what do you see when you are in WinPE, press the F8 button, and run ipconfig.
    1. ipconfig shows no network adapters (see:
    http://myitforum.com/cs2/blogs/rpedersen/clip_image002_53DA17D4.jpg ). This means you still have not loaded the correct device drivers, check the c:\windows\system32\wpeinit.log file.
    2. ipconfig shows an "autoconfiguration IPv4 Address" with a netmastk of 255.255.0.0. This means that the client did not get an IP address from the DHCP server. Double check the connection between the client and the DHCP server.
    3. ipconfig shows a correct address. There is no problem. :^)
    Keith Garner - keithga.wordpress.com
    I get the first result.  Absolutely no network adapters, which I assumed indicated no appropriate device driver.
    This is the result of the wpeinit.log from the machine booting to the 32-bit boot image:
    Info      WPEINIT is processing the unattend file [X:\unattend.xml]
    Info      Spent 1747ms initializing removable media before unattend search
    Info      ==== Initializing Display Settings ====
    Info      Setting display resolution 1024x768x32@60: 0x00000000
    Info      STATUS: SUCCESS (0x00000000)
    Info      ==== Initializing Computer Name ====
    Info      Generating a random computer name
    Info      No computer name specified, generating a random name.
    Info      Renaming computer to MININT-TFRU2BT.
    Info      Acquired profiling mutex
    Info      Service winmgmt disable: 0x00000000
    Info      Service winmgmt stop: 0x00000000
    Info      Service winmgmt enable: 0x00000000
    Info      Released profiling mutex
    Info      STATUS: SUCCESS (0x00000000)
    Info      ==== Initializing Virtual Memory Paging File ====
    Info      No WinPE page file setting specified
    Info      STATUS: SUCCESS (0x00000001)
    Info      ==== Initializing Optional Components ====
    Info      WinPE optional component 'Microsoft-WinPE-HTA' is present
    Info      WinPE optional component 'Microsoft-WinPE-MDAC' is present
    Info      WinPE optional component 'Microsoft-WinPE-WMI' is present
    Info      WinPE optional component 'Microsoft-WinPE-WSH' is present
    Info      STATUS: SUCCESS (0x00000000)
    Info      ==== Initializing Network Access and Applying Configuration ====
    Info      No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
    Info      Acquired profiling mutex
    Info      Install MS_MSCLIENT: 0x0004a020
    Info      Install MS_NETBIOS: 0x0004a020
    Info      Install MS_SMB: 0x0004a020
    Info      Install MS_TCPIP6: 0x0004a020
    Info      Install MS_TCPIP: 0x0004a020
    Info      Service dhcp start: 0x00000000
    Info      Service lmhosts start: 0x00000000
    Info      Service ikeext start: 0x00000000
    Info      Service mpssvc start: 0x00000000
    Info      Released profiling mutex
    Info      Spent 749ms installing network components
    Info      Spent 1669ms installing network drivers
    Error     QueryAdapterStatus: no adapters found.
    Info      Spent 0ms confirming network initialization; status 0x80004005
    Info      WaitForNetworkToInitialize failed; ignoring error
    Info      STATUS: SUCCESS (0x003d0001)
    Info      ==== Applying Firewall Settings ====
    Info      STATUS: SUCCESS (0x00000001)
    Info      ==== Executing Synchronous User-Provided Commands ====
    Info      Parsing RunSynchronousCommand: 1 entries
    Info        Command 0: 0x00000000
    Info      Successfully executed command 'wscript.exe X:\Deploy\Scripts\LiteTouch.wsf' (exit code 0x00000000)
    Info      STATUS: SUCCESS (0x00000000)
    Info      ==== Executing Asynchronous User-Provided Commands ====
    Info      STATUS: SUCCESS (0x00000001)
    Info      ==== Applying Shutdown Settings ====
    Info      No shutdown setting was specified
    Info      STATUS: SUCCESS (0x00000001)
    At first I thought the first bolded section might be relevant, but when I booted to the x64 boot image, which works fine, I get the same message in its wpeinit.log file.  The only difference between the two log files is that the x64 boot image actually
    shows successful installation of a driver where the second bolded section is.

  • Selected boot image did not authentica​te. Press enter to continue

    I just removed the stock HDD that came with my M4-1015x and now I'm trying to install windows 7 to the SSD that I replaced it with. However, upon boot up I get the message "Selected boot image did not authenticate. Press <enter> to continue" when the laptop attempts to read the OS from the disc. I've never seen this before... any help? (It's a legitimate DVD copy of Windows 7)
    Thanks.
    This question was solved.
    View Solution.

    I fixed it. Had to disable secureboot and enable legacy boot mode to get it to run.

  • Can't open my note book. It says Selected boot image did not authenticate.

    I dropped my note book on the floor, later when I turned it on it appears to give the message 'selected boot image did not authenticate. Press enter to continue' When I pressed enter the device shut downs. Please help with this problem. 

     your problem is due to Secure Boot it  is a technology where the system firmware checks that the system boot loader is signed with a cryptographic key authorized by a database contained in the firmware in your case boot loader is damaged.
    temporary solution:
    go to bios and disable secure boot.
    may this help
    to use secure boot feature again you have to repair your boot loader.
    click on thumbs up if i help and mark as answer if i solve your problem

  • [SOLVED][unprofessional] Selected boot image didi not Authentificate

    Hi I try to install Arch on HP-Envy 15
    a 64 bi machine
    with uefi
    and ran in many bootloaderproblems "Selected boot image didi not Authentificate"
    this is what i did:
    gdisk /dev/sda
    gdisk /dev/sda
    p
    something like
    sda1 300 G linux filesystem
    sda2 10G swap
    sda128 470 Mib EF00
    w
    mkfs.ext4 /dev/sda1
    mkswap /dev/sda2
    mkfs.fat -F32 /dev/sda128
    partitions were mounted like the beginners guide tells
    pacstrap -i /mnt base base-devel
    genfstab -U -p /mnt >> /mnt/etc/fstab
    arch-chroot /mnt /bin/bash
    I did some of the local settings
    made hostname...
    Ok but the problem will come here i think
    pacman -S dosfstools efibootmgr grub
    grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=arch_grub --recheck
    mkdir /boot/EFI/boot
    cp /boot/EFI/arch_grub/grubx64.efi /boot/EFI/boot/bootx64.efi
    grub-mkconfig -o /boot/grub/grub.cfg
    after exit reboot i run into the error i told.
    the  comuper might recognize anything because if nothin is on the harddrive it says something diffrent.
    Can anyone help me to install?
    is anything better than grub?
    did i do something wrong?
    ps. installing from archiso ran into errors too
    Last edited by kwatrecht (2014-11-18 12:06:15)

    Ok short update i tried the lasy Bootloaderfix trick i installed Kubuntu on /dev/sda3 told the bootPartition is /dev/sda128 and let them manage it
    now arch runns

  • SCCM 2012 Matching Processor Architecture Boot Image (0) not found

    SCCM2012 SP1 ,One Site, 3DP.
    one DP can not install os with PXE boot. when start PXE F12, system crush with code 0x00000f. and Log like this
    "00:0C:29:90:D1:C0, 291241B9-AB25-4400-B746-99E018F70F1A: device is in the database. SMSPXE 2014/10/1 2:28:11 4504 (0x1198)
    Warning: Matching Processor Architecture Boot Image (0) not found SMSPXE 2014/10/1 2:28:11 4504 (0x1198)"
    The BOOT.wim file works well in ither DP.
    I have try to redeploment the PXE and reload the Boot.Wim file in this DP, but can not reslove this problem.
    I'm afried reset the Boot.wim will take other 2 DP can not work too.
    Please Help.

    Hi Pazza,
    As Torsten said,  please ensure that you have an x86 and x64 boot image configured and deployed, regardless of the architecture of the OS that
    you wish to deploy. Secondly, ensure that the boot images for both architectures have the network drivers for the respective model that you are imaging injected.
    Otherwise, please review the link below:
    ConfigMgr PXE Boot Warning: Matching Processor Architecture Boot Image (0) not found
    http://www.systemcentercentral.com/configmgr-pxe-boot-warning-matching-processor-architecture-boot-image-0-not-found/
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • PS CS6 has a different set of installed fonts than my old PS CS4.  How do I get my old fonts back?  Don't like most of the CS6 fonts.  Dell Precision, Windows 7.  Does PS use the fonts in the Windows directory or does it use its own?  A lot of my preferre

    PS CS6 has a different set of installed fonts than my old PS CS4.  How do I get my old fonts back?  Don't like most of the newer CS6 fonts.  Dell Precision, Windows 7.  Does PS use the fonts in the Windows directory or does it use its own?  If so, where are they in the directory?  A lot of my preferred fonts show in the Windows directory but not in Photoshop, which does not display them within the program.  Please help.  If I get free fonts (NOT CC fonts) from elsewhere, where do I put them for Photoshop[ CS6 to use them?  Thanks.

    All versions of Photoshop get their fonts from your OS.  Just install any missing font wherever Windows keeps fonts.
    I don't do windows myself.

Maybe you are looking for