SATA problem at boot and resume: softreset failed (1st FIS failed)

Hi all,
Since a kernel update about a month ago, and an accompanying reboot, I've been seeing "softreset failed (1st FIS failed)" messages at boot time. These slow boot by twenty seconds or so and, at times, I see messages about reducing SATA speed to 1.5Gb/s. I see similar messages on resuming from sleep.
I want to know if this problem suggests HDD or SATA controller failure. Smartmon tools isn't showing problems with the drive, as far as I can tell. I don't know how to test the motherboard, controller or link speed.
So:
1) Is anyone else seeing this?
2) What is FIS?
3) What other tests can I do?
Thanks!

I am having the same issue. This started after upgrading from kernel 3.16.4-1-ARCH to 3.17.1-1-ARCH.
[root@sirschmoopy ~]# journalctl -b | grep ata10
Nov 08 04:32:40 sirschmoopy kernel: ata10: SATA max UDMA/133 abar m8192@0xfe7fe000 port 0xfe7fe180 irq 18
Nov 08 04:32:40 sirschmoopy kernel: ata10: softreset failed (1st FIS failed)
Nov 08 04:32:40 sirschmoopy kernel: ata10: softreset failed (1st FIS failed)
Nov 08 04:32:40 sirschmoopy kernel: ata10: softreset failed (1st FIS failed)
Nov 08 04:32:40 sirschmoopy kernel: ata10: limiting SATA link speed to 1.5 Gbps
Nov 08 04:32:40 sirschmoopy kernel: ata10: softreset failed (1st FIS failed)
Nov 08 04:32:40 sirschmoopy kernel: ata10: reset failed, giving up
[root@sirschmoopy ~]# lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0)
00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 4)
00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 5)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 41)
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40)
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0)
00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control
01:00.0 VGA compatible controller: NVIDIA Corporation GF100 [GeForce GTX 470] (rev a3)
01:00.1 Audio device: NVIDIA Corporation GF100 High Definition Audio Controller (rev a1)
02:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
03:00.0 SATA controller: JMicron Technology Corp. JMB361 AHCI/IDE (rev 02)
03:00.1 IDE interface: JMicron Technology Corp. JMB361 AHCI/IDE (rev 02)
04:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Last edited by dmartins (2014-11-08 10:32:15)

Similar Messages

Boot error - ata7: softreset failed (1st FIS failed)

Hello,
Since I last upgraded my system with pacman -Syu, when booting these "ata7: softreset failed(1st FIS failed)" appear 3 times in my boot and consume substantial time.
How can I solve it?
(don't know what logs I have to post, if you people could say to me, I'll post them gladly)

Hello,
Since I last upgraded my system with pacman -Syu, when booting these "ata7: softreset failed(1st FIS failed)" appear 3 times in my boot and consume substantial time.
How can I solve it?
(don't know what logs I have to post, if you people could say to me, I'll post them gladly)

SATA problem in Win9x and WinME

Hi, i have a question about SATA devices. I bought a new MOBO yesterday MSI K7N2 DELTA2-LSR and my old MOBO is ECS KT600-A this two boards both support SATA devices. My old board works very fine in all Operating System i install but the new MOBO only works well with WinXP. When i insall a Win9x or WinME on K7N2 it boots and work ok but im worried about the system performance cause when i look my hardware devices the Harddisk Controller shows My Primary and Secondary IDE controller is only Single fifo and two Standard Dual PCI IDE controller. My old MOBO shows Dual Fifo. also my problem is the Hard Drive shows GENERIC DISK TYPE00. Does this affect system performance. Is there any solution through this problem. But they work fine in winXP. thAnkz
K7N2 Delta2-LSR
AthlonXP 2600+ Barton (default)
Thermaltake Volcano 7+ running at Medium speed (5000+rpm)
512 MB 2x256 RAM DDR400
Geforce FX5500 128mb 128-bit
Seagate 80gb 7200rpm barracuda SATA
Lite-On Combo Drive 52x32x52x16

Hi,
Why aren't you using XP all the time?
I can't understand why you are trying to use 98/ME with this board as it is not advised!
Axel

Sata problems, slow booting

Hi,
we gotta fujitsu-siemens desktop at work running arch and were having some problems booting the machine. The computer works fine after it has booted but booting takes a very long time. This is the error msg were getting
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: configured for UDMA/100
ata4: EH complete
ata4.00: exception Emask 0x40 SAct 0x0 SErr 0x800 action 0x2
ata4.00: (irq_stat 0x40000001)
ata4.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x25 data 8 in
res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
ata4: soft resetting port
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: configured for UDMA/100
ata4: EH complete
The sata controller, output from lspci
00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA
Boots fine if booted from the install-cd, so I guess were missing some kernel boot-time parameters or sumtin'.
Thanks for any help.

I have got a similar output on my server with intel-chipset:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd 35/00:00:cf:26:4e/00:04:05:00:00/e0 tag 0 cdb 0x0 data 524288 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1: soft resetting port
ata1.00: configured for UDMA/100
ata1: EH complete
SCSI device sda: 120103200 512-byte hdwr sectors (61493 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA

SOLVE strange problem with suspend and resume with gnome-power-manager

I have pm-utils and gnome installed.
Suspending and hibernation works well from the command line ($ pm-hibernate and $ pm-suspend). Resuming works without any problems.
Suspending from gnome "Shutdown dialog" works perfectly as well.
However, if suspending is initiated by gnome-power-manager something strange happens: After pressing the power button resuming switches to hibernation and my laptop turns off. Resuming from disk works fine again.
Now, suspending works fine again if I change and save any config file in /etc/pm/.
Here comes the strange thing: It doesn't really matter what I change as long as I save it.
However, as soon as I reboot resuming fails again the way I described above.
Anyone have a clue what's going on?
I get no error messages and I've tried all sorts of boot entries.
Last edited by mehldutt (2007-12-26 19:42:31)

After some try and error my guess is that "HAL" is responsible for this problem:
I deinstalled ACPID and 'pm-utils' and switched to 'uswsusp'.
I made the appropriate changes to the appropriate hal-scrips
usr/lib/hal/scripts/hal-system-power-suspend:
#!/bin/sh
/sbin/s2ram --force
usr/lib/hal/scripts/hal-system-power-hibernate:
#!/bin/sh
/sbin/s2disk
After these changes I still have the same problem: immidiatly after resuming form suspend (via power-button) my laptop hibernates (s2disk).
However, if I delete all entries in "usr/lib/hal/scripts/hal-system-power-hibernate" resuming from suspend works fine again, but hibernate doesn't of course. So, some script must be calling "usr/lib/hal/scripts/hal-system-power-hibernate" emmediatly after resuming from suspend.
A couple of weeks ago everything worked fine. My guess is that one of the recent hal-updates is causing this.
How can I figure what script is calling "usr/lib/hal/scripts/hal-system-power-hibernate" after resuming from suspend?

Problems with Booting and Reliability

Hi all I just recently purchased an AMD 64 3400 and an MSI K8T NEO mobo. First off I have had nothing but problems. This was an upgrade from an old Athlon 1700XP and a Gigabyte board so I expected some hiccups. First I had some boot problems from the start. That ended up being a PSU problem and I am now the proud owner of an Antec True Power 550. Boot problem solved.
Next I began experiencing stability problems. It started out being a stutter here or there during the occasional gaming session. It eventually got worse. Mostly freezes no hard crashes or BSOD.
Well it got so bad that the computer would no longer POST reliably. So began the long troubleshooting process. I have had some heat issues in the past so that is where I began. I cleaned up cables, re-routed several, and added a PCI slot fan. This made a smidge of improvement and I thought that my problem was video card related as my GeForce4 4600ti is beginning to show its age but I was even having problems surfing the internet.
Well after reading several post on these forums and the AMD forums I realized that my old DDR266 PC2100 RAM may be the problem.
When I purchased the system in spring 2002 I bought 512 megs of Samsung RAM according to the chips on the stick anyways (I admit I do not know the actual manufacturer of the stick). Well this did not seem to be enough for games such as Star Wars Galaxies so I bought another stick of DDR266 PC2100 512 megs (again not sure of the stick maker but the chips are Infineon). So this is where I began trouble shooting. I swapped wo sticks for one with no luck. Then I tried swapping the sticks and I got a POST beep (beepage good!) and the computer booted. So I thought problem solved. Well it would last for anywhere between 10 minutes and several hours before another freeze.
Well today I stopped into Worst Buy and picked up a stick of Crucial PC3200. With trepidation I plugged the stick in and no POST...nothing. With the Samsung stick I am able to get a proper boot about 10% of the time.
I have seen lots of posts regarding newer faster RAM and compatibilty issues with them. I dont see any problems with older RAM. My question is: Is my problem RAM related or am I barking up the wrong tree (tree...RAM stick...get it?). Even with the newer Crucial PC3200 I am still having problems. If anyone could assist me I would greatly appreciate it.
Thanks in advance.

Quote
next put ram in slot 1 and 3 if you onlly have 2 sticks.
try limiting ram speed to 333 see if that helps.
try using only one stick
disable onbaord stuff you dont need, l
i wasnt having much luck with onboard network , that was 1st to go.
ike parallel ports, if you have a usb printer,
if heat is an issue try running with case cover off.
unless your cpu cooler was not mounted well (rubed off thermal pad having trouble locking it). but i doubt that and would lead to more trouble checking , becuse you would have to remout with artic silver or something.
Well my original RAM is only 266 so the limiting to 333 wont help that. Using one stick is the only way that I can actually get the thing to boot at all but with limited reliability.
I run with the cover off constantly because I am constantly fiddling with the thing. I have taken the HSF off, cleaned it, put new paste on and replaced. My CPU temps have never been above 43 degrees celsius. I have replaced the stocker HSF with a Thermal Take Venus 12.
Thanks for the reply.

K7t Pro 2a problem (it boots and after 1 hour it stops)

Hey,
Since 1 week now I have a problem with my MSI K7T Pro 2a mainboard.
When I'm working the first hour(s) my pc works ok, but at a certain moment I hear a 'whistle' (somebody told me it's a condenser that works bad). When that sound is over (in less then a minute) my pc stops working.
The only way to shutdown my pc is to press the powerbutton for a couple of seconds.
When I press the powerbutton again it wont boot anymore. I could wait some time or I can unplug my pc and it works again for only 1 minute. After a couple of hours I can work further.
I check everything (powersupply, cpu, memory, hd) but I know for 100% that it is the mainboard.
I bought this on the 01/feb/2001.
Please help me.
Greets!
Rope (sorry for my bad english)

Hi, what have you done finally?Quote
Originally posted by foosman
Rope,
My motherboard is out of warranty...just barely. So, I decided to take a try at fixing it today. I noticed a capacitor that visually looked bad (it looked kind of rusty on top and was bowed out). I pulled it and a 2nd capacitor which was also connected in parallel with it. They were 2700uf capacitors...according to my meter, one measured 8000uf and the other 4100uf. I assumed these were bad and replaced them. I did not have any 2700uf, so instead used some larger 4400uf I had. I assumed these are bulk capacitors for power regulation and the size wasn't too critical. I still have the same problem. This did not fix it. Machine is behaving the same way. I'm getting close to giving up.
Can you tell me what you mean by condenser?
Regards,
Foosman
:]

How can I turn off HDD power management at boot and resume?

From what I understand, putting 'hdparm -B 255 /dev/sda' in /etc/rc.local is not the way to do it (and probably won't work for resume from suspend). What is the recommended way to do this?

You could try https://aur.archlinux.org/packages/systemd-hddapm

HP Pavilion g6-2330dx. "No Boot Device. Insert boot disk and press any key" Memory test failed

Hi. So I am trying to help a friend with her laptop. It's a HP Pavilion g6-2330dx.
Product #: D1C01UA#ABA
Serial #: [Personal Information Removed]
Windows 8
ADATA 4GB RAM
Toshiba 640GB HDD from the looks of it.
The laptop is unable to boot into Windows, so I suspect the hard drive. But I ran the hard drive test and it passed all the tests. The SMART test and both the short and long test. I ran the tests multiple times and it passed each time. I tried reseating the hard drive and still no go. I also removed the HDD and connected it to my desktop PC to see if it detects and it did. Ran the Windows 7 own HDD test and it passed.
Currently, there doesnt seem to be any operating system at all on the HDD. When I check, there is a C: drive of ~90GB partition that is ~90GB free, but inside there are Windows files/folders. There is also a D: drive Recovery partition that says ~26GB with only ~2GB free, but when I go inside there's only ~350MB worth of data.
So then I ran the memory test (in BIOS) and it failed immediately. I reseated the RAM module. I tried the other slot. It still failed. So is it safe to say the memory is the cause of this problem?
Pressing the F11 key that is supposed to take me to the System Recovery only leads me back to the black screen with "No Boot Device. Insert boot disk and press any key"
I even tried to install Windows 7 to see if it'll work. I was able to get the laptop to boot/read off the Windows 7. But when I click to install, it asks for a boot device driver or something like that.
My friend doesn't have the recovery disk either. I guess she lost it.
Anyway, is it as simple as replacing the memory or could it actually be the HDD (even though it passes)?
EDIT: This is what the System Log in BIOS says
0021           Time: 10/13/2014
03F0           Time: 10/13/2014
03F0           Time: 10/13/2014
The date was the first time I ran the tests. I havent received those numbers (error codes?) since.
EDIT: Just for kicks, I ran Memtest 2.11 just now (forgot I had the disc) and it immediately went red with thousands of errors, hah.

Hi bghs,
Welcome to the HP Forums!
It is a fantastic place to find answers and information.
For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
I understand that you were unable to boot into Windows, and you suspected the hard drive and tested it, but it passed both short and long test. With that being said and the fact that it also passed leads me to believe the hard drive is fine.
You tested the memory and it failed. You tried reseating and swapping slots but they still failed the test.
I would test each card individual with the memtest to determine if it is just one or both cards that have an issue.
When you installed it in another computer, you did see the recovery partition. Once the memory issue is resolved, if you are still unable to boot into Windows, I suggest you do a recovery with the minimized image.   Here is a link to Performing an HP System Recovery (Windows 8) to assist you with that process.
I hope this helps.
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

This mini is operating OSX 10.6.8 and trying to update to Mountain Lion but upgrade stops and a black overscreen displays saying to power off and power on. The upgrade fails. What's the problem?

This mini is operating OSX 10.6.8 and trying to update to Mountain Lion but upgrade stops and a black overscreen displays saying to power off and power on. The upgrade fails. What's the problem?

Hi Fred,
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at the top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair. Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)

Halt/Reboot fails if triggered after Suspend and Resume

I'm using arch linux with gnome-shell and pm-utils. Halt/Reboot works alright normally, but when the sytem suspends and resumes, and then is halted/rebooted, the same fails.
The screen shows an indication (message on console) that it's halting/rebooting, but it gets stuck there. There aren't any indication of failures/errors.
Is there someone else facing the same problem? The cause? I'll be happy to give any relavant information required for this matter, in the form of system information or any logs,
but at this point i'm not sure what would be relavant.

Sorry this seems to be an existing issue in the forum: https://bbs.archlinux.org/viewtopic.php?id=113985
Will update if any of the suggestion in the above mentioned thread fixes the problem.

Mountain Lion fails to install saying it cannot create the recovery; I had a similar problem with Lion and the Apple Store that helped me resolve it gave me an installable version of Mountain Lion on a flash drive for my inconvenience....

Mountain Lion fails to install saying it cannot create the recovery; I had a similar problem with Lion and the Apple Store that helped me resolve it gave me an installable version of Mountain Lion on a flash drive for my inconvenience....is there some trick I am missing or do I need to make an appointment with a genius...

I have the MacIntosh volume and the Boot Camp partition only. I know that when I installed Lion, I had to go through a whole back-up and recovery of Windows and then re-format the drive.
The tech at the Apple Store had a previous life as a MSCE and was very helpful. I believe he even said that I should not have htis problem with Mountain Lion which is why they gave me the flash with it onboard. I was in the process of starting a new job when I went to Lion, so I have waited to do this next and probably last upgrade to this old MBP since I doubt Apple will support this MBP in Maverick.
I do not have another installation, so that is not an option. I will try to create an external, I have plenty of hard drives around and see if I can get it done that way. It might take me a week or two to get back to it, but I will comment back upon completion of that effort. Thanks for your help....Dave Iverson

K9AGM2 board and sata problem

Sorry if this sounds stupid. I have just bought and built a system with the K9AGM2 board with 2 sata drives, 2 gig ram and 4200 dual core 64 athlon.
I did a fresh install and because i didn't have a floppy i had to set the sata drives to Standard IDE .
All installled fine but is it true I'm not getting optimal performance out of the in this mode , they do seem a bit sluggish.
I then tried to enable raid in the bios and as it went to the windows loading screen it kept rebooting itself so i assume that's a driver conflict or missing driver.
I looked on the website and there is only a sata floppy disc for when you install xp from disc , is there anyway i can get sata performance from the drives without getting a floppy and reinstalling all the system.
Cheers for any info if you can help.

Hello and welcome!
There's a bit of a myth about SATA-performance in RAID. Using a RAID-0 array (two disks working together, reading/writing at the same time) on an onboard RAID-controller with only two disks is hardly worth the effort. I tried it with many onboard controllers .... and yes, I went back to using two SATA's as stand-alone (IDE) drives. It performs just fine.
If you really want RAID, you cannot convert your existing setup to RAID-0. It is impossible. However, there is a workaround for this and no, you will not need a floppy drive. There is always a risk involved: it could not work, so backup your data.
First of all, you can slipstream a SATA-driver into your Windows Setup CD and use that CD to install Windows: >> read this <<.
Then you could try the following:
1. install the SATA/RAID-driver from MSI's website. Just install it and don't let Windows call off the action. You do need the driver later, although your raid-controller is not active yet.
2. Now, make a full image with a backup program that has good recovery tools. You do need one that has a bootable CD to load the recovery program from. Acronis True Image Home is a good example. NOTE THIS: You need an IMAGE, not a backup!
3a. make the boot-media (backup program);
3b. test the media to see that it actually works;
3c. Look under 4: set RAID temporarily to check that the boot-media recognizes your RAID-controller. If it does not, you can now stop... No use continuing. However, most backup tools will be able to work with the controller.
3d. boot into Windows and make the image from C-drive. It's easiest to do it through a home network to some other PC or on a spare or external HDD.
4. Now, reboot and enter bios -> set SATA-controller to RAID and configure as RAID-0 (you need to save changes to bios first, reboot then and enter SATA setup bios next to configure RAID!);
5. Exit the RAID-config screen and reboot from your backup program's bootup CD.
6. Now, put the image back to your new RAID-drive that you just created. When it's finished, take out all media and reboot. Windows should boot now. If it does not, well, then you weren't lucky.....
I did this a few times and it always worked for me with acronis. Be aware that Norton Ghost is very bad with RAID-controllers!
Be aware that using RAID-0 has a risk:
- if one drive fails, you lose all data! What RAID-0 does is the following: when writing 128kb to a RAID-array that is configured into 32k blocks, it simply chops up the 128kb into 4 x 32kb pieces and writes 2x32kb pieces at the same time to each disk. So, your file is chopped up and laying all over the place... In theory, this should improve performance. In daily live, it hardly does. Not with two disks, that is. With 4 it gets better, but if you want real performance, you need a PCI RAID-controller with it's own cpu and RAM.
So, I wouldn't bother and leave it like it is....
(Is that why I wrote this all down?? )

OSD to Surface fails to PXE Boot and returns PXEGetPXEData Failed with 0x80004005

Scenario: When trying to Image Windows 8.1 to a Surface Pro, Surface Pro 2 and Surface Pro 3 I have downloaded the latest Surface Firmware and Drivers (August 18th 2014 I believe), the NIC's are in the x64 PXE Boot Image. I have verified that no DHCP Option
67 is set, and that SpanningTree PortFast is enabled. All other Images function correctly, Windows 7 Sp1 works. We use the Microsoft USB NIC, and we PXE boot and download the PXE Image fine, then it comes into windows and goes to detect the NIC, at which point
it fails and reboots.
The Surface has had Firmware update on it to the latest.
It appears the NIC just stops working, which makes me think that the latest Driver pack for Surface does not contain the PXE boot versions for their NIC.
Trying the Docking Station (which utilizes NIC ASIX AX888772) exhibits the same problem.
The NIC stays active until the OSD Screen comes up, it fails trying to load the Surface NIC though (or the NICs in the Driver pack they just released do not include a PXE Boot Driver...the Drivers once imported do not show any as being Boot Critical...which
make me think this is the case even more so.
Doing a USB PXE Boot also fails to load the NIC.
Going to F8 and doing IPCONFIG /RENEW verifies the NIC is not active.
I see tons of postings on the Surface being a nightmare to image.
Errors:
Failed to Download pxe variable file. Code (0x0000001)
PXEGetPXEData Failed with 0x80004005
Anybody having any other experiences out there, or have anything else they could think to try?
David Baur

(or the NICs in the Driver pack they just released do not include a PXE Boot Driver...the Drivers once imported do not show any as being Boot Critical...which make me think this is the case even more so.
There are no "PXE boot versions" of drivers at all. What you described just indicates that there is no driver in winpe that matches the hardware. WinPe is based on the respective version of the full os so you have to add Win8.x drivers to the boot image.
The architecture also has to match. Have you added NIC drivers to the boot image at all?
NIC drivers are never boot critical if I am not mistaken.
Torsten Meringer | http://www.mssccmfaq.de

CCC or Disk Utility to clone a Mac HD of one new iMac to another, over ThunderBolt, we are getting I/O errors. Even though the clone fails, the destination system does boot and log in, however, the logins take a very very very long time.

When using CCC (Carbon Cophy Cloner) or Disk Utility to clone a Mac HD of one new iMac to another, over ThunderBolt, we are getting I/O errors. Even though the clone fails, the destination system does boot and log in, however, the logins take a very very very long time.
Thoughts.
Edit: Already ran Disk Utility. Also reinstalled a fresh OS on top of the cloned OS and it seemed to remedy the problem. Then, cloned to next machine in the row of the lab. Same problem.

OK, by that I assume that you used Disk Utility to repair the subject disk and it reported "The volume (name) appears to be OK" in green.
Also verify you followed the instructions here: http://help.bombich.com/kb/usage-scenarios/i-want-to-clone-my-entire-hard-drive- to-a-new-hard-drive-or-a-new-machine
If so, the Thunderbolt connection begins to look suspicious.
Reinstalling OS X subsequent to the "clone" operation may be an acceptable workaround but you should not have had the I/O errors you describe, nor should the login times (subsequent to the initial login, that is) be unacceptably long. It calls into question the integrity of all the information that was transferrred.
I'll try to attract the attention of a CCC expert who will likely provide more competent assistance. You can also try the Bombich support site: http://help.bombich.com

SATA problem at boot and resume: softreset failed (1st FIS failed)

Similar Messages

Maybe you are looking for