KP "ATA Device recovery failed"

Hi

I have done a search of Discussions for Sonnet Tempo, results at link below:

http://discussions.apple.com/search.jspa?threadID=&q=Sonnet+Tempo&objID=&dateRan ge=last90days&userID=&numResults=15&rankBy=10001

Anything at http://thexlab.com/faqs/kernelpanics.html helpful to do with your KP issue?

Steve

I am having similar problems with my G5, freezes, and warnings telling me to restart. Have you had any luck with this?

I'm finding this error happening on my 12" PowerBook G4. It started happening just a day or so ago and the machine has been running Leopard since Sunday.

I've run the ADT program and that has found no issues with the machine (ran the long and short test) so far.

The machine was an Erase/Install and a Migration Assistant from a SuperDuper Image to restore apps and accounts. My other machine is the PMac G5 and it has had no issues like this so far (fingers crossed).

I'm taking the PB back to Tiger to see if the issue is OS related or not. If it's HW - I would expect it will show it's head again.

Apple is advertising a sale tomorrow for Black Friday - maybe it's time to upgrade to a MBPro...

My KP is pasted below in case the fact that my PB is suffering the same issue and my KP data helps.

Thu Nov 22 16:52:39 2007
panic(cpu 0 caller 0x010606B4): "ATA Device recovery failed\n"@/SourceCache/IOATABlockStorage/IOATABlockStorage-200.1.8/IOATABlockSt orageDriverV2.cpp:2325
Latest stack backtrace for cpu 0:
Backtrace:
0x0009AD18 0x0009B6BC 0x00029DC4 0x010606B4 0x010608D4 0x0098F0E8 0x0098F81C 0x00992CF8
0x009A0170 0x009A10DC 0x00992AF0 0x00992774 0x00992704 0x003566C0 0x009926AC 0x009994C0
0x0098DBAC 0x01060624 0x01060748 0x010608D4 0x0098F0E8 0x0098F81C 0x00992CF8 0x009A0170
0x00992F20 0x009991D8 0x009A01A0 0x00992E24 0x0099A0B0 0x0003F8D8 0x000AFE54
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOATABlockStorage(2.0.0)@0x105d000->0x106ffff
dependency: com.apple.iokit.IOATAFamily(1.7.3f1)@0x98c000
dependency: com.apple.iokit.IOStorageFamily(1.5.2)@0x832000
com.apple.driver.AppleKauaiATA(1.2.1f4)@0x99e000->0x9a2fff
dependency: com.apple.iokit.IOPCIFamily(2.4)@0x7a5000
dependency: com.apple.iokit.IOATAFamily(1.7.3f1)@0x98c000
com.apple.iokit.IOATAFamily(1.7.3f1)@0x98c000->0x99dfff
Proceeding back via exception chain:
Exception state (sv=0x2a7efc80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9B18

Kernel version:
Darwin Kernel Version 9.1.0: Wed Oct 31 17:48:21 PDT 2007; root:xnu-1228.0.2~1/RELEASE_PPC

My Tiger revert was a bust. The drive was having trouble formatting and being accessed. Re-ran AHT on the machine and it pegged the drive as faulty 😟 Interesting that the SMART system doesn't peg the drive that way.

The drive is very unreliable now and I have the machine booted from a Firewire drive running the older Tiger image until I decide on my repair options. It's out of warranty so I'll have to pay for a repair one way or another. I've downloaded a repair manual and the steps seems OK - just way to many of them.

Sean, condolences for all the trouble. I just had a comment about s.m.a.r.t. related to my experience with my iBook--the drive went from living to dead in 90 minutes (the only "suffering" was mine) giving me barely enough time to back-up latest data on the external which had a recent clone. Those times that I could actually see the drive, s.m.a.r.t. never said a word about "failing." That led me to think that this technology won't detect every imminent disaster. I got a new drive put in, and there was nothing recoverable on the old drive. Go figure. So this is why I have a "double" backup system--a clone, and various items on DVD. Once I get another external I will engage time machine.

Good luck.

I don't think it's Leopard - since it seems HW not SW related at this point. Though the coincidence of the Leopard install and then the drive dying is not lost on me. The only saving grace is that it didn't die right away but several days later but still...

I could upgrade the FW partition I'm using now to Leopard and see if anything untoward happens...

I too have several backups (the Tiger disk backup before the Leopard upgrade as well as a full Timemachine backup for the days it was at Leopard). Data loss is not the issue right now (thankfully) but the hassle of repairs etc.

Thanks guys for your thoughts and help.

Sean

Hey guys,

Did the problem go away? Did you guys go back to Tiger? Get new HDs? I thought I had fixed the problem with a Combo Update, repaired permissions, and a SMU reset, but it happened again tonight. I get a kernel panic report VERY close to Macone's, but pointing to cpu 0 instead of cpu 1.

What did you do?

CMF

Message was edited by: Smileswearily

I'm getting the HD replaced Friday (tomorrow) and then will take the machine back to Leopard. It's running on an external running Tiger - the system image I took before my upgrade to Leopard.

The machine has been rock steady on Tiger (though slower with the FW boot). The internal drive is totally whacked and can't be formatted or used by the system at all. I still believe it is HW and not Leopard. Though I'll let you know if it goes bad once I get the drive replaced.

Sean

Macone,

Super strange coincidence! I did some support articles reading, and it suggested that some intermittent KPs can be caused by third-party software. What do you have running at start-up? I had iTunes, a temperature monitoring program, the Adobe Daemon and the MSOffice Daemon. I got rid of everything but iTunes . . . wondering if some incompatable code in the two daemons or the temp. program caused leopard to hang on load . . . but I don't think that explains the ATA error.

Before installing leopard, I installed a new Seagate HDD. I think the problem is caused by some sort of compatability between Leopard and the HDD . . . Is it possible I got a bad harddrive? It's like the HDD isn't waking up when the PCU is telling it to wake up. Is it just that Leopard's HDD drivers aren't controling the HDD as they should?

A problem like this is very troubling, because it's not clearly an OS problem . . . so apple might have plausable deniability and not clearly a hardware problem (the HDD works well 75% of the time), so Seagate might also deny any reponsibility.

I have done several searches for Seagate/Leopard incompatability, but I have found no reports that suggest their HDDs are no more or less compatable with Leopard then anything else. Anyone have any infromation that suggests otherwise?

CMF