Driver in boot image

Hi all,
I add some drivers for Wi-Fi and video, in boot image. I update distribution point. I see how the new drivers was injected in the image. I recreate the task with involved image. I create a new .iso file for offline deployment. But after installation
computer don't have installed drivers. Manually I update the drivers with some drivers used to add to the image and works.
Were I mistake ?
Thanks.

Parsing step node: Apply Driver Package TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Description: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
ContinueOnError: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
SuccessCodeList: 0 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582) TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
No condition is associated with the step. TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Disable: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Run in attribute: WinPE TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Timeout: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
DefaultVarlist found TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Variable name: OSDAllowUnsignedDriver TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Action command line: osddriverclient.exe /install:NTM0003C /unsigned:%OSDAllowUnsignedDriver% TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Adding instruction at 7 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Processed all elements TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Adding end group instruction at 8 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
The next instruction after group will be at 9 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Processing group TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Parsing group node: Setup Operating System TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Description: Setup Operating System TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
ContinueOnError: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Disable: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582) TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
No condition is associated with the step. TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Adding begin group instruction at 9 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
There are 1 first level steps or groups TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Parsing step node: Setup Windows and Configuration Manager TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Description: Actions to setup Windows and Configuration Manager client TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
ContinueOnError: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
SuccessCodeList: 0 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)

Similar Messages

How to identifiy Faulty Driver in Boot Image (Reverse Engineering of Adding a Driver to Boot Image)

Hello SCCM'lovers
I'm having a new EliteBook 820 G2 here which Fails PXE boot due to a false corrupted
Intel Advanced Network Service Virtual Adapter-Driver.
The PROBLEM now is how to determine under Boot Images - Properties - Drivers ... the correct one.
(see pic)
Over the months, I injected different ones. smsts.log indicates me that this driver is the problem but how can I reverse engineer it to find the correct version/timestamp whatever it on my DP

in theory at least there is a way.
The driver loading in windows will select the best driver based on the PNP-id, version of driver, if it's signed and so on.
you can find the PNP deviceID for that hardware on a installed system by looking in device manager.
After that you can follow the same rules that the system uses to determine which driver it would load by reading the inf files for each driver.
Would it be faster to just create a new one - most likely.
I also would recommend that you create a dedicated driver folder and category in SCCM for WinPE and only add the drivers you need. I prefer to use Original vendor drivers here (aka nicdrivers straight from Intel instead of DELL or HP or ... repackaged
versions

MDT boot image and when we try to PXE boot it won't get the IP Address.

We created a custom MDT boot image and when we try to PXE boot it won't get the IP Address.
I press F8 and type IPCONFIG we get Windows IP Configuration. We are using vmxnet3 network adapter.
I think I need to inject 32-bit vmxnet3 driver to the custom MDT boot image which is 32-bit.
We are using it to deploy Windows Server 2008 R2 with SP1 operating System.
Can I just use the 32-bit custom MDT boot image or do I need to use 64-bit Custom MDT Boot Image?
Also Is there a blog on how to inject vmxnet3 driver to boot image?

You can try this:
http://mwesterink.wordpress.com/2013/12/03/configmgr-2012-obtaining-vmxnet3-nic-drivers-for-vmware-virtual-machines/
Honestly, your best bet is to use a different adapter (E1000). I personally have had no luck getting the vmxnet3 driver to work properly in WinPE. It's either really, really slow or it simply doesn't load at all.

Boot Image - Driver Path

I have another question on drivers and the boot image. I changed the UNC path of a driver and updated the driver itself with the new path. I thought all was good however that driver is in one of my boot images and now I am unable to update the
DP with the boot image as it fail for a that driver with the old path... I verified that the driver in the drivers list has the new path however the boot image still see the 'old' path. this does not make since as I would assume it would just reference
the 'driver' and thus see the new path but I guess it holds its own driver information?.. weird
Is there anyway to see/change the path of a driver listed in the boot image?

Hi,
Based on my test, you could resolve this issue by delete the driver from the list and re-add it.
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.

HT1948 USB drive with install image is showing in Startup Manager on a Mac Pro, but wont boot. Showing circle with cross strip, and shut down automatically. USB device are made and work on two different MacBook Pro, but used on Mac Pro. Any help?

USB drive with install image is showing in Startup Manager on a Mac Pro, but wont boot. Showing circle with cross strip, and shut down automatically. USB device are made and work on two different MacBook Pro, but used on Mac Pro. Any help?

OS X installers have always been fairly specific, hardware-wise. I haven't read anything reflecting that situation with the Recovery HD, so it may be that the Recovery HD created for the MacBook Pro does not have the necessary drivers for the Mac Pro. Obviously, nothing definitive here, but a possibility.

Driver Signing for Boot Images - 2008r2 Site Server

I was trying to update a driver in our boot image due to instability in the previous version. This new driver officially supports Server 2012 R2 (as well as 2012, in a single driver) and is digitally signed.
However, the certificate is not recognized by our Site Server which runs on 2008r2 (because it is a 2012 driver), and DISM.log is flagging the driver as Unsigned, and I cannot update the boot image - it fails every time.
I'm able to work around this by injecting it myself with /forceunsigned, but it doesn't seem to be the "correct" way of handling this. I can also do the mount and driver add on my 8.1 workstation, and not need /forceunsigned (thus proving
it IS signed.)
While it's flagging almost every other driver as unsigned (which is incorrect) - those other drivers aren't deemed "boot-critical", so it allows them.
This one is a SCSI driver, hence it blocking it.
Signature status of driver \\SCCMServer\ConfigMgrDrivers\Server 2012\SCSIAdapter\hpsa2_62.8.0.64\hpsa2.inf is: UNSIGNED - CDriverPackage::InitSignatureStatus
Cannot install non-signed boot-critical drivers on amd64 images. Use /forceunsigned switch to override. \\SCCMServer\ConfigMgrDrivers\Server 2012\SCSIAdapter\hpsa2_62.8.0.64\hpsa2.inf - CDriverManager::CheckClientAddDriverScenarios(hr:0x80070032)
For those of us who have our site servers on 2008r2, I'd call this a bug. Anyone else getting this? Is my workaround the supported solution for people not running site servers on Server 2012 / 2012 R2?

I had similar problem with one driver in the past. The way I 'fixed' my situation was that I manually injected the driver to .wim -image with DISM and then re-added the Boot Image to ConfigMgr 2012. The driver won't show up in the properties of the boot
image but I didn't really care, because I just wanted to get this thing working.

Most reliable external drive for booting and imaging

Hey everyone.
I'm looking for an external drive to boot from and create/distribute Mac Pro, Mac Mini, and maybe a couple iMac images. The hard drives range from 200-500GB maximum capacity. I'm assuming I need a firewire hard drive. The more reliable the better .

Im not sure i quite understand.
Are you saying you have external hard drives already or are they internal?
because basically my suggestion is this;
DIY. Get a firewire Sata enclosure, and obtain Sata drives for it.
heres what i recently got and it works marvels for me:
FW400 Case:
http://www.newegg.com/product/product.aspx?Item=N82E16817198004
very similar to the macpro drive sleds, a sled pops out screw in the drive slide it back in no cables to mess with plug it in and your good to go.
HDDS:
i picked up a 7500AAKS 750gb, a 5000AAKS 500Gb from newegg.com
they also have extremely cheap 250Gb drives for under 90$
thinking of doing that for a future project, cant go wrong there!
goodluck! andhope that helped!

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.

0xc0000135 while adding driver packages to boot image

Hi, I am currently having issues adding driver packages to the boot image.
Currently running Server 2008 R2 and have MDT 2013 installed.
Tried searching for the error but no luck. No matter if I choose the specific driver I want to add or if I just start from the beginning it just constantly fails. Does anybody have any clue as to what could be causing it to not accept either from the boot image
created from MDT Deployment Share or even using a generic boot image?

Hi,
First make sure you are using the correct version of DISM
Secondly look at this http://social.technet.microsoft.com/Forums/en-US/ff8509ec-0ddd-4ad8-9e53-ecf527a80919/dismexe-is-failing-to-add-drivers-to-a-mounted-image-file?forum=w7itproinstall

Prepare an usb thumb drive, to boot windows 7 or 8 in UEFI mode

Purpose of this post:
Prepare an usb thumb drive, to boot windows 7 in UEFI mode and install the system in pure UEFI mode.
Why am I writing this:
I had a hard time finding out how to make a custom installation of windows 7 in pure UEFI mode, and avoid using the factory restore disks. After hours of research, experiments etc I finally got the point and found a solution. And I'm happy to share my research with you. I hope this will be of help. If something is not clear, or more information is needed, I will be glad to explain things further.
History:
As most of you already know, BIOS was developed for PC in early eighties and has remained unchanged in recent years. But, since 2000, Intel started working on a new firmware interface, called Extensible Firmware Interface, abbreviated EFI. And since 2005 United EFI Forum has been handling the responsibility for development, management and promotion of UEFI specifications. Bigger companies like Intel, AMD, Microsoft and Dell have already started to bring out their products in accordance to UEFI standards which has more stable, secure and easier to use interface.
How does UEFI works (in a nutshell):
Once you power on the UEFI based PC, the Pre-EFI is executed which initializes only the CPU, memory and the chipset. This followed by Driver Execution Environment (DEX) where other hardware is initialized.
Advantages of UEFI:
    It can integrate various drivers this will not require to load during booting so saves time.
   PC can connect to network without OS.
   Also integrated drivers allow rendering GUI based control panel which out dates the old school bluish BIOS screen.
   Not all the installed hard drives are scanned as boot drive is set during the installation of OS in UFFI.
   Applications like anti-virus and diagnostic tools can be stored on virtually any non-volatile storage devices attached to a PC.
For a system to boot and install in UEFI the partition table of the HDD should be GPT (GUID Partition Table), not the old school MBR (master boot record). GPT has many advantages, can have virtually an unlimited number of partitions (windows will allow only 128) and impressively big partitions.
Since UEFI has a lot of advantages why not having a system install and boot in UEFI mode? AFAIK new Lenovo notebooks/netbooks are UEFI capable and OS’s are already installed in pure UEFI mode.
So, let’s go now to the point. Do you want to have more control over your HDD? Let say, you have a 320GB HDD and you have divided it in two partitions, one of 50GB, for your Windows 7, and the remaining for your data. If something goes wrong and you need to restore your system to factory default, with the recovery disks, it will wipe your partition scheme, set the system to default and this way your data will be lost.
You may want to make a “vanilla” installation of windows from a USB thumb drive and avoid using factory recovery disks. Now here things get complicated. A standard preparation of the USB with Microsoft’s software (Windows 7 USB/DVD Download Tool), or other tools, will give you a bios installation, not a UEFI one. So for the system to boot, you will need to change some settings in bios, and changing it from UEFI to legacy bios. The installation will prepare the HDD in MBR partition table, and you will lose all the advantages of UEFI, described above.
Now this can be avoided, by properly preparing an USB to boot and install in UEFI mode. Here are the steps:
Step by step tutorial:
1.   In a windows computer, download a legal copy (although trial) of the windows 7 os. You can do this from here: http://www.mydigitallife.info/official-windows-7-sp1-iso-from-digital-river/
Be sure to download the same version that came preinstalled in your computer. For example, if you have a Lenovo x120e, with a Windows 7 professional, 64bit, download an iso image of the Windows 7 professional 64bit.
2.   Once downloaded burn the iso to a USB thumb (at least 4GB) using Windows 7 USB/DVD Download Tool.
3.   After preparing this, create a folder on your computer, name it whatever (i.e. W7pro64bit). Go to the root of your USB
and select all the files and folders there (9 in total) copy, and paste to your folder you created, W7pro64bit.
4.   Using windows format the usb again in FAT32. Windows 7 USB/DVD Download tool, formats it in NTFS. We need a FAT32 formatted disk to achieve our goal. Formating again the USB in FAT32 will not touch the MBR of the USB thumbdrive. And after copying back the files (see step 6) the USB will still be bootable. (nice, and simple, isn't it?)
5.   Now go to the folder W7pro64bit and do the following:
a.   Browse to W7pro64bit\sources\ and open install.wim file. It’s a big file, and can be opened as an archive with 7zip (free software). Do not extract it, do not modify it, just browse the file with 7zip. Just to be sure you do not mess with that file, you can copy it somewhere else in your computer, and than procede.
b.   Browse this file (install.wim) to \1\Windows\Boot\EFI\ and locate the file bootmgfw.efi. Do not move, delete it, but just drag that file to the desktop. (if you have copied the file install.wim to another place in your computer, than you are safely do whatever you want with that file ) Close the 7zip program to release the install.wim file.
c.   Rename the file you just copied to the desktop from bootmgfw.efi to bootx64.efi.
d.   Now go back to w7pro64bit folder and browse \efi\Microsoft. Form there copy the folder boot and paste it one level up, on the folder: \efi. It will look like this: \efi\boot.
e.   Now copy the file you saved on your desktop and renamed (bootx64.efi) to \efi\boot (inside the boot folder you copied on step 5d
6.   Now go to the root of the folder W7pro64bit and select all folders and files (9 in total) copy, and paste all those files back to your USB thumb drive. (see step 4 for more info)
7.   Go to the computer that you are going to reinstall, and before restarting it, use the program ABR (activation backup and restore) to backup the license of your windows os. (use google to find ABR). Advanced Tokens Manager (ATM ) is great too. This link may be of help: Backup and restore W7 activation. After the program finishes its magic, it will create a few files inside the folder where the program itself reside. Copy these files to a new folder in your usb. Rename it to ABR so you will quickly find it later. (if you decide to use ATM, the procedure may be a little different. But you are smart enough to figure out how to use it)
8.   Backup to an external storage all your data before continuing.(reminder: are you sure you saved the license as explained in step 7, to a safe place? To a external drive, to another computer? If you are sure, than go on with step 9)
9.   Now restart your laptop, and enter your bios settings. Go to the boot settings, and set the computer to boot in UEFI only. Not both, not UEFI first, or legacy, BUT UEFI only. Save and restart.
10.   Press f12 (or the corresponding key for your machine) to choose the boot device and chose to start from the USB thumb drive with your windows 7 pro 64 bit.
11.   If everything is done correctly, your computer will boot from the USB.
12.   Follow the wizard and choose a custom install, not upgrade. At the disk partition window delete all the partition you see there until you have only one unallocated space.
13.   Select it, and click next to install windows, without making partition in this point. The installer will create a GPT partition table not a MBR since the USB booted in UEFI mode.
14.   Immediately after the first restart remove your USB thumb, and the installation will continue from the HDD. Wait until installation finishes.
15.   When you will be finally on your desktop, on the installed OS plug your USB go to the ABR folder and click on restore.exe. It will restore your license and your copy of windows will be activated.
16.   Now you can go in computer management/disk management and shrink the HDD to create your partitioning scheme. Make sure to leave enough space to your windows os. (30gb or more for extra programs you will install at your choice)
17.      Download from lenovo.com thinkvantage system update and update your system. Windows update too can install all the necessary drivers, if you need only basic drivers support.
Note: if tvsu will fail to work, see this:
http://forums.lenovo.com/t5/ThinkVantage-Technologies/ThinkVantage-System-Update-Servers-down-the-wh...
It may look a looong tutorial, but once you do this for the first time, it will look a piece of cake.
Final words:
From now on, you can install windows 7 in UEFI mode with your special USB without changing your partition scheme anymore. If you have a data partition beside your os partition (see the example above), when you reinstall the system using your USB thumb drive, at the disk partition window chose the partition where windows is installed, delete it, and reinstall windows to the unformatted area. Your partition with your data will be intact and the installation will automatically mount your data partition to the system. And, all the scope of this procedure, you will always have a pure UEFI installation of the system, with all its benefits.
Have fun!
abvasili
Moderator note: changed subject to match new content. Was: Prepare an usb thumb drive, to boot windows 7 in UEFI mode
I'm just a volunteer. I like to help others where I can. Do my ideas work? I hope so. o_O
Who helped you today? Do not forget to thank him.
My hardware: TP x120e 0596-2ru. Windows 7, sp1, 64Bit, English, installed in UEFI mode.

seanare wrote:
Thank you, as I noted here, your post was the key to my getting a Windows 8 SecureBooting setup on a W530.
In the case of Windows 8, I needed to copy the files away, reformat my USB key as FAT32 and copy the files back, and viola I was able to boot from my USB install media with the BIOS set to only boot UEFI. From there, there rest was easy (for Windows 8, the copying and renaming is not necessary, the key is having a FAT32 partition on the USB media, rather than an NTFS one; the EFI files are already in the right location).
Thank you again good sir.
You are welcome... and I'm happy that the change of the file system helps with windows 8 too. Thanks for confirming that.
abvasili
I'm just a volunteer. I like to help others where I can. Do my ideas work? I hope so. o_O
Who helped you today? Do not forget to thank him.
My hardware: TP x120e 0596-2ru. Windows 7, sp1, 64Bit, English, installed in UEFI mode.

Can I install windows 7 on a potable Hard Drive using boot camp? or any other way to do so?? need help for college please

I need to use windows in order to use Visual C++ for college but I don't have enough space in my internal Hard Drive so I want to install windows 7using boot camp or any other method on a portable hard drive and boot from it.
Please help I need it as soon as possible for school. Thanks

You can't boot Windows natively except on internal drives.
You can use a VM and put the VM image (VHD) anywhere any drive you want.
You are way too low on disk space, seriously so. And no room - even Windows and Mac OS should be warning and balking already.
"emulator" is an old-school term, even true, running a Guest OS under Mac's as a virtual machine, shared resources (RAM, processor) is easier but not the same performance level as running natively.
Comparison of VMware Fusion Parallels VirtualBox
This just posted, an FAQ for Lion and Boot Camp 4.0
Boot Camp 4.0, OS X Lion: Frequently asked questions

Hi, I have a hard disk failure so to recover my data I am using disk utility to restore the data on an external drive while booting from a second external hard drive. When I perform the operation it gives me an input/output error and stops. Any tips?

Hi, I have a hard disk failure so to recover my data I am using disk utility to restore the data on an external drive while booting from a second external hard drive. When I perform the operation and after having selected both my destination and source drives, the operation begins but soon fails due to input/output error. If I try to create an image of the drive it gives me the same error message. Any help would be much appreciated.

Disk Utility only creates a image of the drive, so it's no help getting exactly what you want, which is your files. If the file structure is messed up or the drive is failing then it's no help.
If you have a external boot drive and you can't access the internal non-booting drive though the typical Finder and windows to transfer your files via drag and drop methods, then you need to install Data Rescue on the external boot drive and it will do as best as it can to recover your files. (works on non-encrypted/non-Filevaulted drives only)
.Create a data recovery/undelete external boot drive
Are you sure you have hard drive failure, or that OS X isn't merely not booting?
Because if the drive is working physically, then there is a host of fixes
..Step by Step to fix your Mac
https://discussions.apple.com/community/notebooks/macbook_pro?view=documents#/

Having issues with Surface Pro 3 downloading boot image over PXE

Hi,
We've recently started to buy the new Surface Pro 3 with the new USB 3.0 Gigabit Ethernet adapter and we have some issues deploying them through SCCM. Basically, with the Pro 2 and Fast Ethernet adapter we have no issue at all, of course the deployment is
a bit longer than on any other computer, but it is still quite faster than the latest Surface.
We have the new 8.13.414.2014 driver injected in the Win 8.1 boot image for the USB 3.0 Gigabit adapter and all the drivers assigned to the new Surface in SCCM.
The problem occurs when we try to load the boot image after choosing PXE, it takes more than an hour to load it when it shouldn't take more than 5 minutes.
I tried rolling back to the old driver (8.6.128.2013) and use the Fast Ethernet adapter, use the Fast Ethernet adapter with the new driver and use the new adapter with the old driver, but it's still slow in any case, so
I'm pretty sure it has something to do with the new Surface and not the Ethernet adapter.
Anyone have an idea what could be the problem here? Anyone having issues with Surface Pro 3 and SCCM 2012?

I would imagine you have upgraded to R2, have you also applied KB2905002.
This hasn't got anything to do with the TFTP loading phase of the boot image.
Similar thread to this can be found here:
http://social.technet.microsoft.com/Forums/en-US/a6d80714-dc26-43db-a071-93eaee267122/surface-pro-2-surface-ethernet-adapter-super-slow-pxe?forum=configmanagergeneral
I already asked in that thread the same question, but how about normal PCs that are connected to the same network segment as the Surface devices, do they boot slow also?

[SOLVED] CD Drive causing boot problems

I'm trying to install Arch, but booting the install disk causes these errors to come up:
Loading /arch/x86_64/vmlinuz.....
Loading /arch/x86_64/archiso.img.............ready.
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
: : Starting udevd...
done.
: : Running Hook [udev]
: : Triggering uevents...[ 19.934456] usb 5-1.6: device descriptor read/64, error -110
[ 35.098044] usb 5-1.6: device descriptor read/64, error -110
[ 36.869505] ata8.00: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe frozen
[ 36.869549] ata8: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
[ 36.869598] ata8.0: failed command: IDENTIFY PACKET DEVICE
[ 36.869639] ata8.0: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
[ 36.869640] res 40/00:00:00:00:00/00:00:00:00:00 Emask 0x56 (ATA bus error)
[ 36.869721] ata 8.0: status: { DRDY }
It just stops there and won't continue to boot. Disconnecting the SATA cable from my CD drive and using a flash drive to boot fixes these issues, but I didn't continue with the install because I wasn't sure if I would be unable to boot with the drive plugged in later. This is my CD drive. It's connected to a SATA 6GB/s port on my motherboard. The drive works perfectly in Windows.
Also, if anyone knows anything about the USB error, help would be appreciated. That was the only error that did not go away after disconnecting my CD drive. I only have a keyboard, mouse, and WiFi dongle plugged in.
Last edited by nigh (2012-05-29 09:28:01)

Your issue with the SATA disc drive is a problem with Udev. Namely that some SATA disc drives do not support 16-byte pass-through commands coming from Udev. See this post for a longer explanation and the correct workaround:
https://bbs.archlinux.org/viewtopic.php?pid=895404
Other guides online will say to comment out parts of Udev's 60-persistent-storage.rules file, but I have found that to not only not work, but mess up detection of the SATA hard drives.
So, after, or during, Arch installation using your USB stick:
Add
options libata atapi_passthru16=0
to /etc/modprobe.d/modprobe.conf
Add
FILES="/etc/modprobe.d/modprobe.conf"
to /etc/mkinitcpio.conf
Rebuild kernel image with:
mkinitcpio -p linux
reboot
To narrow down your USB issue, maybe you could try booting with only one plugged in at a time to identify which one has the issue. Do they all three work even though one gives this message?

Cannot backup Windows 7 (dual-boot) image to external HD (formated as Mac OS Extended)

I cannot backup my Windows 7 (dual-boot) image to my external HD (formated as Mac OS Extended). I installed MacDrive 8.0 hoping to solve the problem but Windows 7 gives me an error when I try to create a backup: "...drive is not formatted as NTFS, cannot use as backup...".
I also tried making an Image of the Windows 7 partition through Disk Utility but was not allowed to do so.
I am not sure where else to go from here. I need to keep my external hard drive formatted as Mac OS Extended but I also need to backup my Windows 7 partition. I only have the single external at the moment. Is there a way to backup my Windows 7 partition?
Thanks

Winclone will backup your Windows partition to a Mac formatted drive.
Just search for Winclone on this forum and on Goggle.

Driver in boot image

Similar Messages

Maybe you are looking for