Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 9

78,109 points

Kernel Panics (x 2) using Disk Warrior 4.4 on latest Lion build

After updating to the latest build (11D50 > 10.7.3), I decided to make a new clone from scratch on one of my external partitions. Erased disk with Disk Utility > made clone using Super Duper (I use CCC on my other clone). Tested clone by booting into it - worked. Booted back into internal and launched Disk Warrior; graph showed directory 37% out of whack. So I hit rebuild. Within 60 seconds or so, first kernel panic. Shut down. Rebooted and everything appeared fine. Sent the kp report to Apple. Decided to try it again: within 60 seconds, the second kernel panic.

KP log is below if anyone can make some sense of it (also sent that to Alsoft this morning):

Interval Since Last Panic Report: -8 sec
Panics Since Last Report: 1
Anonymous UUID: C7B05263-F497-421C-AD7C-B0EC862C2AEF

Fri Feb 3 22:27:12 2012
panic(cpu 3 caller 0xffffff80002c266d): Kernel trap at 0xffffff80002af406, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffff813b63c000, CR3: 0x00000000216a7035, CR4: 0x00000000000206e0 RAX: 0x0000000000016fe0, RBX: 0xffffff813b631020, RCX: 0x0000000000000003, RDX: 0x000000000000aff8 RSP: 0xffffff81620dbcc8, RBP: 0xffffff81620dbcf0, RSI: 0xffffff813b63c000, RDI: 0xffffff813b652fe0
R8: 0x0000000000000000, R9: 0xffffff80008bf5e0, R10: 0xfffffe8001a96360, R11: 0x000000000017bb00 R12: 0xffffff80008df780, R13: 0xffffff802cca2b00, R14: 0x000000000000aff8, R15: 0xffffff8030b369c0
RFL: 0x0000000000010216, RIP: 0xffffff80002af406, CS: 0x0000000000000008, SS: 0x0000000000000010 CR2: 0xffffff813b63c000, Error code: 0x0000000000000000, Faulting CPU: 0x3

Backtrace (CPU 3), Frame : Return Address 0xffffff81620db980 : 0xffffff8000220702 0xffffff81620dba00 : 0xffffff80002c266d 0xffffff81620dbba0 : 0xffffff80002d7a1d 0xffffff81620dbbc0 : 0xffffff80002af406 0xffffff81620dbcf0 : 0xffffff80005e3909 0xffffff81620dbd20 : 0xffffff7f80793da4 0xffffff81620dbda0 : 0xffffff8000654830 0xffffff81620dbdf0 : 0xffffff800029f20d 0xffffff81620dbe20 : 0xffffff8000223006 0xffffff81620dbe50 : 0xffffff8000214829 0xffffff81620dbeb0 : 0xffffff800021bb58 0xffffff81620dbf10 : 0xffffff80002aedb0 0xffffff81620dbfb0 : 0xffffff80002d801e

Kernel Extensions in backtrace: com.alsoft.Preview(4.4)[B016E8B4-FE8A-B791-49C8-6FF01DF285E2]@0xffffff7f8079300 0->0xffffff7f80799fff

dependency: com.apple.iokit.IOStorageFamily(1.7)[E0606FD9-7CC1-3E36-BC0A-E0768FF988E4]@0xff ffff7f8076e000 BSD process name corresponding to current thread: DiskWarrior

Mac OS version: 11D50

Kernel version:
Darwin Kernel Version 11.3.0: Thu Jan 12 18:47:41 PST 2012; root:xnu-1699.24.23~1/RELEASE_X86_64 Kernel UUID: 7B6546C7-70E8-3ED8-A6C3-C927E4D3D0D6
System model name: iMac11,3 (Mac-F2238BAE)

System uptime in nanoseconds: 1024244228248
last loaded kext at 1024201863243: com.apple.iokit.IOAVBFamily

1.0.0d22 (addr 0xffffff7f807a4000, size 36864)
last unloaded kext at 1007434208889: com.apple.iokit.IOAVBFamily

1.0.0d22 (addr 0xffffff7f80793000, size 36864) loaded kexts:

com.alsoft.Preview 4.4
com.apple.driver.AppleHWSensor 1.9.4d0 com.apple.driver.AppleMikeyHIDDriver 122 com.apple.driver.AppleUpstreamUserClient 3.5.9 com.apple.driver.AppleMCCSControl 1.0.26 com.apple.driver.AppleMikeyDriver 2.1.7f9 com.apple.driver.AudioAUUC 1.59
com.apple.driver.AppleHDA 2.1.7f9
com.apple.driver.AGPM 100.12.42 com.apple.kext.ATIFramebuffer 7.1.8 com.apple.iokit.IOUserEthernet 1.0.0d1 com.apple.Dont_Steal_Mac_OS_X 7.0.0 com.apple.driver.AudioIPCDriver 1.2.2 com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.5d4 com.apple.driver.AppleLPC 1.5.3 com.apple.nke.webcontentfilter 3.0 com.apple.driver.AppleBacklight 170.1.9 com.apple.ATIRadeonX3000 7.1.8
com.apple.filesystems.autofs 3.0 com.apple.driver.AppleUSBCardReader 3.0.1 com.apple.driver.AppleIRController 312 com.apple.driver.Oxford_Semi 3.0.1 com.apple.AppleFSCompression.AppleFSCompressionTypeDataless

1.0.0d1 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1 com.apple.BootCache 33
com.apple.iokit.SCSITaskUserClient 3.0.3 com.apple.iokit.IOAHCIBlockStorage 2.0.1 com.apple.driver.AppleFWOHCI 4.8.9
com.apple.driver.AppleUSBHub 4.5.0 com.apple.driver.AirPort.Atheros40 502.60.2 com.apple.iokit.AppleBCM5701Ethernet 3.0.8b2 com.apple.driver.AppleEFINVRAM 1.5.0 com.apple.driver.AppleAHCIPort 2.2.0 com.apple.driver.AppleUSBEHCI 4.5.8 com.apple.driver.AppleACPIButtons 1.4

com.apple.driver.AppleRTC 1.4
com.apple.driver.AppleHPET 1.6 com.apple.driver.AppleSMBIOS 1.7
com.apple.driver.AppleACPIEC 1.4
com.apple.driver.AppleAPIC 1.5 com.apple.driver.AppleIntelCPUPowerManagementClient 167.3.0 com.apple.nke.applicationfirewall 3.2.30 com.apple.security.quarantine 1.1 com.apple.driver.AppleIntelCPUPowerManagement 167.3.0 com.apple.iokit.IOAVBFamily 1.0.0d22 com.apple.driver.AppleBluetoothHIDKeyboard 152.3 com.apple.driver.AppleHIDKeyboard 152.3 com.apple.driver.IOBluetoothHIDDriver 4.0.3f12 com.apple.driver.DspFuncLib 2.1.7f9 com.apple.driver.AppleSMBusController 1.0.10d0 com.apple.driver.AppleSMBusPCI 1.0.10d0 com.apple.iokit.IOFireWireIP 2.2.4 com.apple.driver.AppleUSBAudio 2.8.2f5 com.apple.iokit.IOSurface 80.0 com.apple.driver.AppleHDAController 2.1.7f9 com.apple.iokit.IOHDAFamily 2.1.7f9 com.apple.iokit.IOBluetoothSerialManager 4.0.3f12 com.apple.iokit.IOSerialFamily 10.0.5 com.apple.iokit.IOAudioFamily 1.8.6fc6 com.apple.kext.OSvKernDSPLib 1.3 com.apple.driver.ApplePolicyControl 3.0.16 com.apple.driver.AppleSMC 3.1.1d8 com.apple.driver.IOPlatformPluginFamily 4

Model: iMac11,3, BootROM IM112.0057.B00, 2 processors, Intel Core i3, 3.2 GHz, 12 GB, SMC 1.59f2
Graphics: ATI Radeon HD 5670, ATI Radeon HD 5670, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353637334648302D4348392020 Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353637334648302D4348392020 Memory Module: BANK 0/DIMM1, 4 GB, DDR3, 1333 MHz, 0x857F, 0x483634353155363446393333334700000000 Memory Module: BANK 1/DIMM1, 4 GB, DDR3, 1333 MHz, 0x857F, 0x483634353155363446393333334700000000 AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 4.0.61.4-P2P
Bluetooth: Version 4.0.3f12, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: ST31000528AS, 1 TB
Serial ATA Device: HL-DT-STDVDRW GA32N
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: hub_device, 0x050d (Belkin Corporation), 0x0237, 0xfd140000 / 5
USB Device: iMic USB audio system, 0x077d, 0x07af, 0xfd142000 / 8
USB Device: CTH-460, 0x056a (WACOM Co., Ltd.), 0x00d1, 0xfd145000 / 7
USB Device: Back-UPS ES 550 FW:843.K2 .D USB FW:K2, 0x051d (American Power Conversion), 0x0002, 0xfd141000 / 6 USB Device: Built-in iSight, apple_vendor_id, 0x8502, 0xfd110000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2
USB Device: MacALLY USB One Button Mouse, 0x0618 (Chia Shin Technology Corp.), 0x0301, 0xfa130000 / 5
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa120000 / 4
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0xfa111000 / 7
FireWire Device: d2 quadra (button), LaCie, 800mbit_speed

I may try this one more time later today or tomorrow; if it happens again, I will wipe that clone and re-do it with CCC and then try it again to see if it could possibly have anything to do with SuperDuper (rather than Mac OS or DW).

Edit: This should be in the Lion forum - sorry - will report myself (if I can - don't see a report button) or someone could please have it moved........ thanks.

iMac (27-inch Mid 2010), Mac OS X (10.7.2), i3 12 GB RAM | 10.6.8

Posted on Feb 4, 2012 9:55 AM

Best reply

baltwo

Level 9

62,362 points

Posted on Feb 4, 2012 3:20 PM

Ran DW 4.4 on 10.7.3 and rebuilt the directory (44% out of whack) for my Lion clone made with CCC; had no issues. Did a search for com.alsoft.Preview 4.4 and couldn't find it on my machine. All I can suggest is to reinstall Lion and run a new copy of DW 4.4.😎

View in context

33 replies

babowa Author

Level 9

78,109 points

Feb 5, 2012 9:36 AM in response to baltwo

I had sent SuperDuper an email including the KP log; here is what I got this morning:

There is absolutely nothing wrong with SuperDuper! under Lion. A kernel panic is due to system-level (low-level, kernel) issues with either I/O or other items. You'd need to investigate the actual panic report to understand what's going on...but my guess was drive problems utterly unrelated to what program copied.

He may be correct; however, since the KP only happens after having used SD! and then using DW, I'm not sure he is. So, I won't be using SD! again for a while and wait to hear from Alsoft.

Linc Davis

Level 10

209,547 points

Feb 5, 2012 9:54 AM in response to babowa

When you hear from Alsoft, please ask why it is that Disk Warrior always finds "corruption" of your volume directories. Also ask why millions of other Mac users, including me, who have never used Disk Warrior and must therefore have even worse "corruption" than you do, don't seem to notice. Finally, if there's any gain in performance from fixing the "corruption," ask them to quantify it and support their claim with test results. They should be more than willing to provide all that information, considering how much money they're asking for their product. And I want to know what I'm missing. Who knows, maybe I'll change my mind about Disk Warrior and start using it myself. Thanks in advance.

Linc Davis

Level 10

209,547 points

Feb 5, 2012 9:57 AM in response to babowa

He may be correct...

He is.

babowa Author

Level 9

78,109 points

Feb 5, 2012 10:03 AM in response to Linc Davis

Okay, so if he is:

1. why would it only happen after having used SD > DW (and not after using CCC > DW)?

2. and, what could/should I be doing to prevent future KP's?

FWIW, I will ask them about the directory corruption - that was on my list - because I find it odd having created a brand new clone on an empty partition that I wouldn't have a "perfect" system on that partition.

Linc Davis

Level 10

209,547 points

Feb 5, 2012 11:58 AM in response to babowa

1: That's a question about the internals of DW. CCC is a wrapper for rsync, while SD is proprietary. Presumably, they leave the volume catalog in a different state. One of them triggers a bug in DW, the other doesn't.

2: Not wasting your time with DW.

By the way, DW is not detecting corruption in your volume directory. It's detecting what Alsoft considers to be "fragmentation" of a certain data structure in the HFS directory (the catalog b-tree.) That condition is a completely normal and inevitable result of using the filesystem. So the problem that DW is fixing is not a problem at all. I recall that, years ago, Alsoft used to claim in its marketing material that there was a performance gain from "defragmenting" the b-tree. It no longer makes that claim on its website, perhaps for fear of being sued for false advertising.

Feb 5, 2012 1:46 PM in response to Linc Davis

As I said is each to own. Lots say repair permissions for this and that especially after updates. DW is good and lots use it. Doesn't always find corrupt volumes like you say. You hate it. I hate doing TM backups to same effect takes too long. I was just telling op that DW 4.4 work fine on 10,7,3 did not want a fight over what software you like and what I like.

Goodbye

Linc Davis

Level 10

209,547 points

Feb 5, 2012 2:22 PM in response to boyfromoz

You hate it.

I couldn't care less about it. What I do care about is seeing harmful misinformation being given on this site, that may lead naive users to waste money on software they don't need.

Feb 5, 2012 3:00 PM in response to Linc Davis

But no one has said anybody has to use it. Some off us just saying we like using it. If you don't want it or can't afford it then good. But I can afford it and use it. That is all. You probly use programs some of us think are no value.

No win argument. Op used it and asked question

Feb 6, 2012 1:03 AM in response to babowa

Please do trust the advice given by the developer of SuperDuper!.

Before I got to that quote on page two … reading page one of this topic …

In exceptional circumstances I might expect DiskWarrior to crash, but I doubt that DiskWarrior could cause a kernel panic.

For SuperDuper! I have even greater confidence that it should never cause a kernel panic.

Comparison

Maybe off-topic from the symptoms described by babowa, here's the beginning of something that I'll feed through Apple Bug Reporter:

2012-02-02 09:49:54 kernel panic — Safari in foreground, VirtualBoxVM with Lion guest in background, IOHIDFamily, IOBluetoothFamily, IOBluetoothHIDDriver and AppleBluetoothMultitouch in backtrace, last loaded kext: IOAVBFamily, last unloaded kext: IOEthernetAVBController

In both my case and babowa's case, the last loaded kext is:

com.apple.iokit.IOAVBFamily 1.0.0d22

This need not indicate an issue with that kext, but it's a starting point — and the advice from the developer of SuperDuper! is a most valuable complement.

With attention to my file

Kernel_2012-02-02-100758_macbookpro08-centrim.panic

I find it most unusual to have that combination of Apple extensions alone in the backtrace, last loaded and last unloaded areas.

There's a known minor issue with at least one of the three drives that I usually have on the FireWire bus of my MacBookPro5,2. Not an issue that I would expect to cause a kernel panic of this nature, but I keep an open mind. (I use this drive with its known issue for test purposes, not for data that's irreplaceable.)

Readers other than babowa, please note that I do not seek community help for my own issue. It's to be fed to Apple, and it should not be confused with babowa's case.

I might not revisit this topic. babowa, good luck!

Feb 6, 2012 1:14 AM in response to babowa

> If a 35% + directory corruption is reported …

Those percentages given by DiskWarrior are measures of order within a directory. Not corruption.

Included with modern versions of Mac OS X, a command line utility can recreate — from an attribute B-tree and from a catalog B-tree that are without corruption — directories that are orderly. This is off-topic from any kernel panic, I recommend a visit to Ask Different. If the answer is not there already, ask the question and I'll pick it up in due course.

Feb 6, 2012 1:40 AM in response to Graham Perrin

For personal tracking purposes: 3710426

14896/147233

babowa Author

Level 9

78,109 points

Feb 7, 2012 2:19 PM in response to Linc Davis

Here is an update:

Got a reply from Alsoft - they want me to do a PRAM reset:

This looks like a memory issue where a set of numbers is being improperly replayed. One of the key places to see this is:

>> Interval Since Last Panic Report: -8 sec

Minus eight seconds? Definitely not right.

Reset the computer's PRAM by holding down Command (Apple), Option, "P", and "R" keys while starting your machine. Continue to hold these keys until the computer makes the Startup chime three times.

Then, start up the computer from the DiskWarrior disc and run DiskWarrior again. What is the result?

And, as for the question re. a 35+% of directory:

The high percentage is usual and normal for a new operating system installation as the operating system and/or cloning software process does no optimization of the directory.

I'm certainly about as far from being an expert on this as one could be, but that strikes me as questionable. Using (maybe the wrong) logic, it would seem to me that if you write to a blank drive, it should be all neat and tidy when finished? Not haphazardly all over the place?

baltwo

Level 9

62,362 points

Feb 7, 2012 3:28 PM in response to babowa

See if the PRAM reset fixes anything. As for the directory stuff, the only way to guarantee nothing amiss is to use the block-level cloning feature. AFAIK, CCC uses multiple copies of rsync while doing its thing, which might account for this. BTW, CCC 3.4.4 is now available.😎

Feb 8, 2012 3:10 AM in response to babowa

>> new operating system installation

Two key help pages from Apple:

Mac OS X 10.7 Help: Reinstall Mac OS X, which includes a link to
Mac OS X 10.7 Help: Erase and reinstall Mac OS X.

From an iDefrag perspective:

reinstall will result in a layout of files that is less optimal than layout from a first install
erase and reinstall will result in a relatively optimal layout of files.

With an erased volume, using any third party approach to write files might be less optimal than the routines provided by Apple. An exception is block-level cloning, which includes cloning the layout (without regard to optimisation).

Whilst layout of files may be sub-optimal, at the same time all three of the following may be optimal:

attribute B-tree
catalog B-tree
extents B-tree

babowa, I'll seek answers for you in Ask Different …

babowa Author

Level 9

78,109 points

Feb 8, 2012 8:27 AM in response to Graham Perrin

Thanks; in the meantime..... I decided to do the PRAM reset (before cloning again/running DW again as a test):

Does anyone know if this is "expected" behavior:

FYI, I have two partitions on my internal hard drive: Snow Leopard and Lion and, I've rarely used SL lately - only a few times when I either wanted to run Software Update on it and/or worked in Appleworks on some designs. I was certainly running Lion yesterday when I shut it down.

So, this morning, I do the PRAM reset and to my surprise, it started itself from the Snow Leopard partition (both login screen and then the desktop). I had to go into System Prefs and choose Lion and restart.

Is this normal?

SL was the original OS on this machine - would that be the reason that it automatically used SL?

Kernel Panics (x 2) using Disk Warrior 4.4 on latest Lion build