Aperture Kernel Panics & Fusion Disk Corruptions

We have a new iMac with the Fusion drive bought not to long ago. It has 16gb memory. Since it's back to school, we are busier than this past summer
We are editing about 200 - 400 images a day. While in Aperture we have had kernel panics and a major spinning ball freezes with a total reboot freeze that ended up with corruption on the Fusion drive.
We have ask some tech people, and all have said, when working with large raw images, which we do, the drive cannot keep up with editing, esp when using the brush tool. Also missing files sometimes, like magic their gone.
Anyone else have this.
PS we have swaped out the memory 3 times and still had issues. I don't think the drive can handle the work.

While I am runing a DIY Fusion Drive on a Mac Pro, I am a heavy user of Aperture and have noticed no problems what so ever with my current setup.
It might be helpful if you canpost a crash dump from one of your kernel panics.
Allan

Similar Messages

First Kernel Panic - failed Disk Utility volume repair - Help?

Hello!
Well, you've seen the subject. 2 nights ago, after a long day of iTunes, Photoshop, Final Cut Express, and Halo, my powerbook had it's first kernel panic. When? When I unplugged my Lexar JD Lightning flash drive. I had just copied about 200 MB of music onto it (to copy to my imac), and ejected it. Instant panic.
Well, after a reboot, I ran disk warrior on all of my external drives - 2 USB (Western Digital 120GB, Iomega Exite 80GB), my Seagate 400 GB combo drive (Firewire), with 2 volumes, and my 4G clickwheel iPod - well, it's FAT32, so it didn't check it. (For use copying files to our winbox)
It worked properly, until I tried to repair the Iomega drive. It froze. Force reboot.
So, now I ran disk utility on my internal drive. While it was running, Backup started, and everything locked up. Force reboot again.
It rebooted and loged in just fine, so I restarted to the OS X install DVD (the one that came with the Powerbook - 10.3.7). I ran disk utility on Macintosh HD (boot drive). Permissions verification showed a few "special permissions". Permissions repair worked just fine. Disk verification found issues, and repair didn't work. It gave the following error while running:
"Invalid leaf record count. Should be 1 instead of 302"
In big bold letters, repairs failed. Odd, it checked 2 volumes -
at the bottom, it said
"Repair attempted on 2 volumes: (green text) 1 HFS volume repaired. (next line, red) 1 volume could not be repaired.
Right above this, in the progress window, it stated:
"The volume Macintosh HD was repaired successfully"
So, what? Is the second volume the install DVD?
My powerbook is running just fine, so I ran backup again. (the .Mac backup application from Apple)
Then, I ran Tech Tool Deluxe (3.03) - included on the AppleCare CD that came with our Applecare subscription for my Powerbook. It found no issues at all.
So, i'm clueless. I have not noticed any other issues. At least, since the issue.
Before this happened, I've noticed a few glitches. One is that iTunes has slowed down, particularly when changing tracks. The other is the menu bar battery indicator - sometimes it disappears - rather, the indicator. The space that it occupies in the menu bar remains empty, until you click on it - then it shows up fine. What's odd is that it's only the text - it's otherwise just fine.
What happened before the issue began? Well, I installed a new PNY ram card back around Easter - if that's the culprit, shouldn't it have shown an issue before now? Second: Installs. A few widgets, and a couple of applications: OS 10.4.7 and all other updates Software Update had to offer, Toast 7.1 update, Comic Life's new Universal version (a minor update, actually), Microsoft Office update (heh, probably that), and the trial of Salling Clicker - it's quite cool - Macworld (Aug 06 - new issue) gave the right rating (5 mice!). I dont' run permission checks enough, I know.
A while back, (like 10 months ago) my Powerbook wouldn't go to sleep. It turned out that it was one particular USB 2.0 hub - disconnecting it solved the issue. Its not unlike how my Seagate FW drive will keep my iMac from booting properly every now and then.
So, here are the questions:
1. What is the "leaf record count"? Is it very critical? Is it part of the physical HDD, or the system?
2. Powerbook's running fine, and no other issues. Is it okay to run?
3. If I need to repair/reformat (eventually), will it be sooner or later?
4. This seems rather odd, and very intermittant. How do I find out what the issue is?
5. What is the second, mysterious volume? Macintosh HD is not partitioned. (Could it be Classic?)
6. if the SMART status of the internal drive reports just fine, could it be missing something?
Thanks,
Daniel
15" 1.67 Powerbook G4 (non-HiRes), Slot loading iMac DV SE Mac OS X (10.4.7) 1G RAM on PB, 384 MB iMac.

Techtool Deluxe you want to be running version 3.0.4. Version 3.0.3 is not compatible with 10.4 and may be causing the leaf count issues. Here's the link to get an updated Techtool Deluxe:
https://support.apple.com/techtooldeluxe/main?id=dl
My suggestion is to start to simplify everything here. Leave everything disconnected from the machine, and boot off the Disk Warrior 3.0.3 CD, and repair the internal drive first. Use the Option key to boot:
http://docs.info.apple.com/article.html?artnum=106178
Once you are able to do that, then see if you can repair the external drives.
RAM issues can crop up at anytime, and without warning. No test can detect all bad RAM, but once detected, then you know it is accurate.

Kernel panics, graphic file corruption with Firewire

I've been having consistent problems with Firewire since I got my Mac Pro last year. I only recently narrowed it down to Firewire so I thought I'd write it up here for the record.
I never actually solved the problem, just started using USB-2 instead and the issues went away.
--I had been getting pretty consistent kernel panics while doing backups or large file transfers to an external FW drive. I tried a few different drives and cables and the panics were consistent.
--I also noticed a strange problem where graphic files I'd backed up (TIFF, JPEG, etc.) would have these single-pixel horizontal streaks running through them. This was a little disconcerting because it wasn't picked up during verification, it was just there when I opened the backup file.
I found lots of people with FW problems in these forums but none mentioned that strange file corruption I got.
I'll try FW again after a future system software upgrade but I'm giving up on it for now.

I've been having consistent problems with Firewire since I got my Mac Pro last year. I only recently narrowed it down to Firewire so I thought I'd write it up here for the record.
I never actually solved the problem, just started using USB-2 instead and the issues went away.
--I had been getting pretty consistent kernel panics while doing backups or large file transfers to an external FW drive. I tried a few different drives and cables and the panics were consistent.
--I also noticed a strange problem where graphic files I'd backed up (TIFF, JPEG, etc.) would have these single-pixel horizontal streaks running through them. This was a little disconcerting because it wasn't picked up during verification, it was just there when I opened the backup file.
I found lots of people with FW problems in these forums but none mentioned that strange file corruption I got.
I'll try FW again after a future system software upgrade but I'm giving up on it for now.

Kernel Panic and Disk Utility

I have a 12" 1.5 gHz PowerBook that runs almost flawlessly. Today I experienced my first kernel panic while running Call of Duty. My PB has Photoshop Elements 4, Popcorn 2, Dreamweaver MX, Macaroni, Tinkertool, and LittleSnitch as the only software other than what came with it. I am running 10.4.7. I also recently downloaded and installed the firmware update for my superdrive.
When I did the update to 10.4.7, I did all the things to make it go right, no problems until today and I don't think it is the update. I ran disk utility, verified disk, it indicated it needed repair so I attempted to repair it. It had something about 8 or 20 leaf? in the window and when it completed repair, it said HFS was repaired but volume could not be? Now when I verify, it says, "Incorrect number of extended attributes? and it won't repair. Now I am flummoxed. Ran TechTool Deluxe since I am on Applecare and it could not find anything, and I assume that the problem is something it won't find or repair. What is my next step? The PB is running well and this is the first time it has had a kernel panic. El P

hi el perdido--
did you try running disk utility a number of times?? also, you should repair disk and then select the first drive (not macintosh hd, but the other one) to see if smart status is available. it should say "verified". smart status is not always available. if you can't get it repaired, you could always try disk warrior. and if diskwarrior doesn't fix it, you will have to back up all info (which you should do right now anyway, if you think it's possible you can't repair your volume) and then erase and install. you can back up your info on an external drive, on disk, or if you have access to another mac, you can use firewire target disk mode. http://docs.info.apple.com/article.html?artnum=58583. let me know how it going. [ 8 ) ]

Aperture kernel panic

The trial of the latest Aperture has never come up once on my MBP with Leopard. It beachballs and then crashes with a report. I had tried out a 1.something version previously but I wasn't that serious about it at the time and the trial expired. Now I have a new digital SRL and am thinking seriously about Aperture.
Assuming the new trial crashes because there are still pro preferences from the older version somewhere, can somebody suggest which plugins and plist files I should whack before reinstalling? I've reinstalled four times with the same results.

Hi! Yes, make sure all old files from previous and latest trials are removed. Last time I was unable to reinstall a new version of CS3 because old files were hidden somewhere. Simply putting the application into the trash is not enough. I learned about about Appledelete (Free Trial Version), and it worked well.
Just upgraded to Aperture 2. To avoid having any similar problems I did the same first. But this time with a trial version of AppZapper (Application), check website. Its a great and funny thing.
By the way what exactly did u do before u had the kernel crash. I had also one with using the Patch Tool, which i will not touch anymore...
Regards Michael

*Notice* - Aperture and Lacie. Disk Corruption.

Noticed an issue with Aperture Libraries on Lacie Biggest Quadra RAID drive.
Apertures get stuck in an endless loop when trying to quit. The progress dialoguebox displayed in Aperture "Updating Sharing Previews"
In Console, we have looping instances of this:
0-07-23 8:15:50 AM com.lacie.desktopmanager.service[7508] SCSIStackDevice: Remote Comms command failed [c0:s0]
10-07-23 8:15:50 AM com.lacie.desktopmanager.service[7508] Device (LaCie Biggest Quadra Media) not comms-capable

Hello Marco,
You might like to read this online artice about Referenced Masters which may help explain your problem:
http://homepage.mac.com/bagelturf/aparticles/ref/ref.html
USB2 will slow your experience of Aperture. I have a 160GB USB2 drive that takes 160 seconds to mount on my desktop. In comparison, my 1TB Firewire 800 drive takes just 9 seconds.

Receive IPv6 traffic - kernel panic?

I configured an IPv4 -> IPv6 tunnel on my firewall via he.net and set my default route for inet6 traffic to the remote side. Then I got a /64 network assigned from he.net and IP'd my internal network, include my MacBook Pro running OS X 10.4.8.
I can do a traceroute6 from my Mac to external sites just fine. It uses the IPv6 tunnel exactly as expected (I set my default route for IPv6 on my Mac to be the IPv6 address of the internal interface of my firewall). When I tried to use an external site to do a traceroute6 back to my Mac, it panicked!
Perhaps there is some problem with the Intel version of the Yukon driver (Marvell Yukon gigabit ethernet)? Has anyone else had kernel panics when on the receiving end of inbound IPv6 traffic (that wasn't in response to an outbound connection)?
Here's the crash report:
panic(cpu 0 caller 0x0035BEAC): freeing free mbuf
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x251e3db8 : 0x128d1f (0x3c9540 0x251e3ddc 0x131df4 0x0)
0x251e3df8 : 0x35beac (0x3e9c7c 0x1dfba 0x87c4b9fe 0x1dfba)
0x251e3e38 : 0x7314a4 (0x36e07600 0x0 0x251e3e68 0x1a1ec0)
0x251e3e58 : 0xa6d454 (0x237f1000 0x36e07600 0x0 0x2)
0x251e3e88 : 0xa6bad0 (0x237f1000 0x36e07600 0x0 0x38dbc80)
0x251e3ea8 : 0xa6ed7c (0x237f1000 0x0 0x1000000 0x133b25)
0x251e3f08 : 0x398a1f (0x237f1000 0x38dbc80 0x1 0x37b5d08)
0x251e3f58 : 0x397bf1 (0x38dbc80 0x135ec3 0x0 0x37b5d08)
0x251e3f88 : 0x397927 (0x38d7480 0x0 0xee6b280 0x13869f)
0x251e3fc8 : 0x19a74c (0x38d7480 0x0 0x4 0x4eae6b8) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleYukon(1.0.7b3)@0xa69000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x72a000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x5ee000
com.apple.iokit.IONetworkingFamily(1.5.1)@0x72a000
Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386
Model: MacBookPro1,1, BootROM MBP11.0055.B08, 2 processors, Intel Core Duo, 2.16 GHz, 2 GB
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairportwireless_card_type_airportextreme (0x168C, 0x86), 0.1.27
Bluetooth: Version 1.7.9f12, 2 service, 0 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
Network Service: AirPort, AirPort, en1
Serial ATA Device: ST910021AS, 93.16 GB
Parallel ATA Device: MATSHITADVD-R UJ-857
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA

MTU on the ethernet interfaces of the Mac and the inside the firewall are both 1500 (normal). My switch is only FE so the Mac's NIC auto-neg'd to 100/full. The MTU of the 4->6 tunnel is 1280. I believe that's because of the encapsulation overhead (it has to send the IPv6 packets inside IPv4 packets).
In any case, it's not using Jumbo Frames (I don't think the switch even supports them).
I was thinking it might be a problem with the longer address and endianness. For instance, maybe on the Intel platform they did a quick patch to make the address pointer move over a fixed 4 bytes, then read backwards by the length of the address. That would work fine for 4 byte (i.e. IPv4) addresses, but on 16 byte (IPv6) addresses it would go horribly wrong (shift 4 bytes, then read backwards 16 bytes, uh oh!).
Apparently it only affects some of the code paths, because I can send out IPv6 packets and accept the responses. It was only when I received an unsolicited IPv6 packet that it panicked.
It's all just a wild guess any way. I would like to experiment with it a little more, but I really don't feel like causing multiple kernel panics and possibly corrupting my file system from the resulting hard-resets.

Lion NetBoot and NetInstall causing kernel panic

I'm trying to get NetBoot and NetInstall working on a recently set up a new Mac Mini with OS X Lion Server.
We previously had Snow Leopard server and moved the existing images onto the Lion Server. However, when trying to boot off either image the machines kernel panic.
Have tried creating new images, but with the same result.
Anyone with similar issues who have managed to fix it?

Thanks for your reply. I will try what you suggest and also read through the troubleshooting tips you linked to. Cheers!
I do have have some furher information about the problem.
Definitely some strange behaviour here - I'll try to explain is as well as I can.
Started out activating one NetInstall image of Lion 10.7.2 (did not have 10.7.3 on hand). When testing with my MacBook Pro (17-inch, Mid 2009) currently runing Lion (came with Snow Leopard), I got a kernel panic. However, when choosing the NetInstall image as startup disk via System Prefrences, it boots up fine via this image.
After a while I also added a Snow Leopard NetInstall image (newly created on one of our machines still running Snow Leopard). With the Lion set to be the default netboot image. When booting my machine into startup manager, then pressing 'N' to see netboot images, I only get one additional icon (despite there being two enabled images) with the server IP underneath. When selecting that icon, the machine boots up with the Snow Leopard installer (despite Lion being set as the default).
Trying the same with an iMac without a hard drive, this iMac would have come with Snow Leopard preinstalled, shows me both NetInstall images in startup manager, but I get a kernel panic when trying to boot off the Snow Leopard image - not the Lion image. Selecting the Lion image as startup disk while booted from the SL image results in a successful boot from the Lion image.
To recap:
On MacBook Pro
Startup manager, Lion boot = kernel panic
Startup manager, SL boot = success
Startup disk chooser, Lion boot = success
Startup disk chooser, SL boot = success
On iMac
Startup manager, Lion boot = success
Startup manager, SL boot = kernel panic
Startup disk chooser, Lion boot = success
Startup disk chooser, SL boot = success
The above is true when sharing the images both over NFS and HTTP.

Kernel panics with Aperture

My partner's brand-new MBP 17" is having kernel panics whenever Aperture is put under a heavy load. Whenever she starts flicking though lots of images quickly, up comes the Grey Screen Of Death. Also, once she got video corruption - the GUI remained responsive but all the icons, menu bar etc were replaced by squares of noise, even after Aperture was quit.
Parameters:
*10.4.7 with all updates
* 2 Gig of ram - one is 3rd party but removing it doesn't fix the problem
* The library is copied across from my MBP 15" where it worked fine - and I tried rebuilding it
* Tech Tool Pro can't find any problems. No disk errors in the Console.
The only thing I can think of is that Aperture wasn't actually 'installed' - rather it came across when I used the transfer settings wizard to get here profile across from my MBP (she had her own login since her powerbook was stolen a few weeks ago). Should I try deleting every related file i can see and then reintalling from the DVD? Can anyone see anything in the kernel panic log? if there anything I should look for in the console?
Kernel panic log below;
panic(cpu 1 caller 0x0019CADF): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x000003f4, CR3: 0x00d5e000, CR4: 0x000006a0
EAX: 0x00000000, EBX: 0x00000068, ECX: 0x000000d0, EDX: 0x04466000
ESP: 0x000003f4, EBP: 0x24e7bd88, ESI: 0x04466000, EDI: 0x1ecd9448
EFL: 0x00010002, EIP: 0x00194f66, CS: 0x00000014, DS: 0x0019001c
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x24e7bc3c : 0x128b5e (0x3bc46c 0x24e7bc60 0x131bbc 0x0)
0x24e7bc7c : 0x19cadf (0x3c18e4 0x1 0xe 0x3c169c)
0x24e7bd2c : 0x197c7d (0x24e7bd40 0x24e7bd88 0x194f66 0x48)
0x24e7bd38 : 0x194f66 (0x48 0x19001c 0x24e7001c 0x19001c)
0x24e7bd88 : 0x1c42c7 (0x4466000 0x46e0048 0x46e001c 0x4469f78)
0x24e7bdd8 : 0x1c70df (0x3795d0c 0x24e7be50 0x24e7bdf8 0x198ce5)
0x24e7be28 : 0x2f6bb9 (0x3795d00 0x0 0x2f4f24 0x24e7be50)
0x24e7be88 : 0x1d62d7 (0x3795d00 0x2 0x24e7bef8 0x0)
0x24e7bed8 : 0x1c8bfe (0x3795d00 0x2 0x24e7bef8 0x1bea0b)
0x24e7bf08 : 0x1c5656 (0x3795d00 0x0 0x1 0x4761f1)
0x24e7bf48 : 0x1c8c32 (0x10 0x1c8bbc 0x0 0x351c1010)
0x24e7bf78 : 0x36de6c (0x3d935dc 0x36962e4 0x3696328 0x13d59c)
0x24e7bfd8 : 0x197ff3 (0x36997e0 0x36997e0 0x24e7bd40 0x24e7bcb0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffffe38
Kernel version:
Darwin Kernel Version 8.7.1: Wed Jun 7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386
(etc...)
Macbook Pro 17" Mac OS X (10.4.7) 2 gig RAM

Look this kernel panic.log. I have tested the mac with the complete test of the istallation DVD, result all ok.
This kernel panic after 20 min of exporting in jpeg a large modified library.
What is it?
Tue Oct 24 19:14:22 2006
panic(cpu 0 caller 0x59188CD0): Uncorrectable Fbd memory error detected. ferr = 00000020 , nerr == 00000020
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x108cd8 : 0x128d1f (0x3c9540 0x108cfc 0x131df4 0x0)
0x108d18 : 0x59188cd0 (0x5918ae64 0x20 0x20 0x8100a4)
0x108da8 : 0x59188f64 (0x7af2d00 0x7af2d00 0x2 0x820044)
0x108e38 : 0x592e1712 (0x7af2d00 0x0 0x79f8d80 0x0)
0x108e68 : 0x592e159b (0x79c7880 0x0 0x0 0x1c)
0x108e88 : 0x592f431c (0x1c 0x108ef8 0x8 0x592f5dd9)
0x108eb8 : 0x592f44c6 (0x79c411c 0x17 0x79c774a 0x78d6520)
0x108f18 : 0x5930105d (0x7994188 0x0 0x87e1ad9b 0x1729)
0x108f38 : 0x5953b4fb (0x7994188 0x0 0x77e7c80 0x0)
0x108f68 : 0x592e77c5 (0x78a7200 0x0 0x798b680 0x49)
0x108f88 : 0x592e0c1f (0x7815a00 0x0 0x798b680 0x49)
0x108fa8 : 0x3b9d21 (0x799c700 0x0 0x799c880 0x49)
0x108fe8 : 0x19aa20 (0x490e3e30 0x490e3e30 0x19ba76 0x57c000)
0x490e3f18 : 0x1a42f5 (0x10 0x1 0x490e3f38 0x6)
0x490e3f38 : 0x19d871 (0x0 0x0 0x490e3f68 0x206)
0x490e3f58 : 0x135f23 (0x0 0x0 0x0 0x19d23a) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleMCEDriver(1.1f1)@0x59185000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x5928c000
com.apple.driver.AppleAPIC(1.2.0)@0x5953a000
com.apple.driver.AppleACPIPlatform(1.0.5)@0x592df000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x59276000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x5928c000
Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386

Mac Pro Kernel Panic while booted on install disk

I have a Mac Pro with 1 year and 2 weeks on the clock. No Apple Care.
Started getting intermittent Kernel Panics about 2 weeks ago, which are becoming a real problem now. Happening every time I use the machine.
I’m running 10.6.4 and just have the original ram etc.
Having searched here for related topics, I have been trying to troubleshoot the situation.
Was looking at recent software installs or likely culprits...
Ran the normal Apple Hardware Test and passed ok.
Ran an extended test and got this error: "4HDD/11/40000004:SATA(4,0)
Repaired all internal disks as far as possible, while started up on the installation disk, and when finished I got another Kernel Panic, while still running on the disk.
Can someone confirm if this means the issue if definitely hardware rather than software?
If so is it possible to tell which hard drive is at fault - ie. which Bay number corresponds to the SATA error above, if it is the hard drives at fault?
Need to get this fixed asap, so if anyone has any thoughts on how I should best proceed, that would be really appreciated. Thanks.
Here is the Report from the last Panic:
Sun Oct 3 21:30:03 2010
Machine-check capabilities (cpu 1) 0x0000000000001c09:
family: 6 model: 26 stepping: 5 microcode: 17
Intel(R) Xeon(R) CPU E5520 @ 2.27GHz
9 error-reporting banks
threshold-based error status present
extended corrected memory error handling present
Machine-check status 0x0000000000000004:
machine-check in progress
MCA error-reporting registers:
IA32MC0STATUS(0x401): 0x0000000000000800 invalid
IA32MC1STATUS(0x405): 0x0000000000000800 invalid
IA32MC2STATUS(0x409): 0xb200000000030005 valid
MCA error code: 0x0005
Model specific error code: 0x0003
Other information: 0x00000000
Threshold-based status: No tracking
Status bits:
Processor context corrupt
Error enabled
Uncorrected error
IA32MC3STATUS(0x40d): 0x0000000000000000 invalid
IA32MC4STATUS(0x411): 0x0000000000000000 invalid
IA32MC5STATUS(0x415): 0x0000000000000000 invalid
IA32MC6STATUS(0x419): 0x0000000000000000 invalid
IA32MC7STATUS(0x41d): 0x0000000000000000 invalid
Package 0 logged:
IA32MC8STATUS(0x421): 0x0000000000000000 invalid
Package 1 logged:
IA32MC8STATUS(0x421): 0x0000000000000000 invalid
panic(cpu 1 caller 0x001A9A3E): Machine Check at 0x857d48aa, thread:0x996c3c8, trapno:0x12, err:0x0, registers:
CR0: 0x8001003b, CR2: 0xb0091fec, CR3: 0x00ec6000, CR4: 0x00000660
EAX: 0x09c2c000, EBX: 0x000003e8, ECX: 0x00088d80, EDX: 0x00000000
ESP: 0x85b9bebc, EBP: 0x85b9bec8, ESI: 0x098e1000, EDI: 0x0000091e
EFL: 0x00000206, EIP: 0x857d48aa
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x84eaffb8 : 0x12b4c3 (0x45d7fc 0x84eaffec 0x133542 0x0)
0x84eb0008 : 0x1a9a3e (0x467558 0x857d48aa 0x996c3c8 0x12)
0x84eb00e8 : 0x1a15c3 (0x84eb0100 0x401ff4ab 0x803fe956 0x7fd2ad)
0x85b9bec8 : 0x857d4c0a (0x98e1000 0x9c2c000 0x0 0x41047c)
0x85b9bee8 : 0x857cd96c (0x98e1000 0x0 0x85b9bf18 0x857cda50)
0x85b9bf18 : 0x424b61 (0x98e1000 0x0 0x1 0x19ef34)
0x85b9bf68 : 0x423cbe (0x99f2580 0x996c3c8 0x85b9bf98 0x136e83)
0x85b9bf98 : 0x4239a0 (0x9988a40 0x9988a40 0x85b9bfc8 0x126313)
0x85b9bfc8 : 0x1a055c (0x9988a40 0x0 0x1a30b5 0xa75fb40)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBEHCI(3.4.0)@0x857ca000->0x857dbfff
dependency: com.apple.iokit.IOUSBFamily(3.4.0)@0x85664000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x77db9000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9G3553
Kernel version:
Darwin Kernel Version 9.6.3: Tue Jan 20 18:26:40 PST 2009; root:xnu-1228.10.33~1/RELEASE_I386
System model name: MacPro4,1 (Mac-F221BEC8)
Message was edited by: kmahon

Hi experiencing simular issues
Initially I thought the error was related to too many different things on the machine, but have since done a clean install to 10.6 with FCP and CS4 only and the and the errors continue.
6 error-reporting banks referred to 6 of the ram chips, but i see that your report
states 9, ( you don't have 9 ram slots do you?)
Upgraded this of a volume disc so I don't have the hardware diagnostic for this machine on a disc, and would have to go back to the tiger hardware diagnostics which should not make a difference but I see on forums people claiming this is an error only with leopard and that their systems were fine under tiger. The ram has a life time warrantee (non apple) but I need to get it to fail a test other than this apple problem report.
The machine crashes are not software specific, I was hand writing with just a browser open and it requested that I would have to restart the machine. If would be easier to test any solution I I know that combo would crash the machine other than time.
I expect the next steps
are to reseat the ram
reset the p-ram
Regards
Colm

Kernel Panics, Drive Corruption, Directory Issues.

Desktop M8840LL/A Dual 1.25GHz PowerPC G4 (FW800) MDD
2GB Ram, 2 WD - 500GB IDE Drives Internal, 4 SATA Dr (2 WD - 500 GB SATA internal 1 WD 500GB SATA, One WD 640GB SATA external ), Sonnet Tempo SATA X4i PCI Card, ATI 9600Pro AGP, 1- 23in Apple Cinema Display, One 24in Samsung Display. 3 Firewire 250Gb WD external Drives.
This setup was running great for 2 years until a four year old WD drive failed 3 weeks ago and corrupted its data etc. I had the data backed up so no panic.
I decided to replaced it 3 weeks ago with a new 500GB WD IDE and reinstall 10.5 and migrate users for that drive.
Ever since I have been getting daily if not hourly kernel panics and issues with ALL drives on my system.
At one point the system loscked 4 drives and I could not access them at all.
Discussion group helped fix that issue.
I have managed to saved all my important data to a 500GB drive without a system on it and hopefully can deal with the issues at hand without worrying about the data.
Booted from my System 1.5 install disk and had a dark grey/ Must restart your mac screen while I was booting from the DVD!
Did an Apple Service diagnostics on the machine and all was great - no issues.
So I did a clean install on a drive and all looked great!
No other software installed except the system.
Rebooted OK.
I then did the apple software update and restarted.
No startup!
Rebooted with option key down - no drives??
I have been working on this for three days and seem to be going backwards at best.
I can boot sometimes and usually get a kernal panic eventually.
It can happen right away or an hour later.
Sometimes I get a message "your computer was shut down etc" sometimes I don't!?
Sometimes I get a startup chime - sometimes I don't!!??
What should I do next?
Advise whatever info you might need and I will do my best to provide it.

I stripped my Mac down to barebones incluing original 80GB Drive 512 RAM and Original Video card and started over.
To make a long procedure shorter I found that all hardware was OK and after running ASD to confirm I reinstalled all my hardware/Add ins except for drives.
I then started to check each drive individually with Applejack and then formatting and reinstalling virgin systems on each drive.
Applejack and/or the system DVD would not fix and/or install on three of the Hard Drives (1 IDE 500GB and 2 500GB SATA)due to permission corruption. I could not do anything with these drives at all!
When I had these individual drives in the computer I experienced kernel panics with every one!
All the drives were under warranty and Western Digital replaced all of them. (I cannot begin to tell you how great Western Digital was in turnaround time and cross shipping and help in this matter.) Their warranty service is the best I have ever experienced bar none!
I am now running non stop for nearly a week without any kernel panic or problem whatsoever. I have also noticed a significant speed up in my computer.
I have rebooted many times and run non stop for days at a time.
I maintain my computer with maintenance scripts once per week and do it faithfully and this type of permission issue can still occur!
Without my backups there would have been a disaster for me.
Many thanks to all the peolpe that emailed help to me from all sources.
Sometimes out of the worst of situations good prevails.

Kernel panic - hard drive or corrupt journal system?

Hi,
My powerbook G4 shut down today with a kernel panic and now won't boot up (giving a kernel panic error after reaching the gray screen). The computer has been working fine, though the battery has run down, with the exception of not shutting down properly (I would have to power off manually). I tried various things to fix this (repair permissions, check hard drive, checking logs, etc.), but all those checked out and I could never get it figured out. I have been leaving the computer running because of this and it has been working fine. It is a stock G4 with no peripherals, except for a 1 GB RAM upgrade. The RAM was installed two years ago and tested strenuously with memtest with no issues.
I did have my hard drive near full, as I didn't realize that this could case severe issues. It's probably too full to do a clean Archive and Install. My fault.
I have reset my PMU/PRAM, but the computer won't boot up in safe mode or single-user mode. I get the following message at the end of single-user mode:
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007: root:xnu-792.24.17~1/RELEASE_PPC
panic: We are hanging here ...
Unfortunately, I do not have my backup disks with me right now, as I recently moved (I will have them in a couple weeks).
There's some data on the computer it would be nice to pull off, but not absolutely essential. So my question is: Does this sound like a hard drive problem or a journal system/file system problem or something else? I hear no strange noises from the drive (the fan is a little noisy, though). What can I do at this point while I wait for my discs to arrive from across country?
If this is a file problem, I have heard these are difficult to fix or even deal with in terms of data recovery, since the disk won't mount even in firewire target mode. Should I invest in a firewire external drive in order to create a bootable second drive? Purchase DiskWarrior? Create a bootable Linux CD? Any help would be appreciated!

darksurtur:
If you have the original HDD with which the computer was bought you likely have a failed HDD and should have it replaced with a newer, faster and large capacity HDD. The average life of an internal HDD is 3 to 5 years, and although it may not suddenly stop functioning after that performance gradually decreases until the drive fails completely.
A too full drive can cause serious directory corruption which can in turn lead to data corruption and possible loss, and eventually a crash. You should maintain a minimum of 15% to total disk capacity (5 GB minimum on HDDs of 40 GB or less) as contiguous free space to allow for swap files and directory expansion.
You should always maintain a current backup of everything you do not wish to lose as even a new HDD can fail suddenly. Using an external firewire drive and making a bootable clone using a utility like SuperDuper or Carbon Copy Cloner is an excellent way to accomplish this. Dr. Smoke's FAQ Backup and Recovery has excellent tips on backup strategies.
Please do post back if you have further questions or comments.
cornelius

Corrupt Encrypted Sparseimage, PrivateFrameworks and Kernel Panics

Hi Maclovers,
After a kernel panic my encrypted sparseimage with valuable data won't mount:
# hdiutil attach sec3.bak.sparseimage
hdiutil: attach failed - Defektes Image // german for 'corrupt image'
Attaching the following string:
0000b90: 2c45 0000 0000 0000 0000 0000 0000 0000 ,E..............
0000ba0: 0000 0001 6364 7361 656e 6372 ....cdsaencr
gives:
diskimages-helper(11183) malloc: * vm_allocate(size=3190173696) failed (error code=3)
diskimages-helper(11183) malloc: * error: can't allocate region
diskimages-helper(11183) malloc: * set a breakpoint in szone_error to debug
hdiutil: attach failed - Speicher kann nicht zugewiesen werden // german for 'memory not allocable'
Okay, no problem I thought, Mac OS X builds on Open Source Software, so I can decrypt the sparseimage by hand (with perl) and rescue the needed data with a hexeditor.
But, the DiskImages Framework (/System/Library/PrivateFrameworks/DiskImages.framework/DiskImages) is not Open Source
From poking around with gdb and strings I learned that hdiutil uses sha,sha1,sha256,sha512 and md5. But I was unable to figure out
- how the password is expanded for the 128 bit aes key (plain md5/sha0,1,256,512 won't work)
- in which mode aes runs (ecb/cbc/ofb)
Do you know it and can you give me a hint?
Btw: from gdb:
openssl related
0x9194711c aes128_cbccipher
0x9196cd9a aes128_cfb128cipher
0x9196cddf aes128_ecbcipher
0x9196ce39 aes128_ofbcipher
calling from here?
0x97e6ba5e CEncryptedEncoding::encodePasswordHeader(Security::CssmData const&, Security::CssmData const&, CEncryptedEncoding::PasswordHeader&)
0x97e6bd72 CEncryptedEncoding::generateKeyBlob(Security::CssmAutoData&)
0x97e6bece CEncryptedEncoding::parseKeyBlob(Security::CssmData const&)
more functions
0x91946660 AESset_encryptkey
0x91946a5b AESset_decryptkey
0x9194715c AEScbcencrypt
0x919473df AES_encrypt
0x91947880 AES_decrypt
0x9194dd91 AEScfb128encrypt
0x9194de42 AEScfbr_encryptblock
0x9194df86 AEScfb1encrypt
0x9194e046 AEScfb8encrypt
0x9194e095 AESctr128encrypt
0x9194e20b AESecbencrypt
0x9194e232 AES_options
0x9194e242 AESofb128encrypt
Here's some debug info:
si hdiutil attach -debug sec3.bak.sparseimage calling DIHLDiskImageAttach with
<CFDictionary 0x3161a0 [0xa08011c0]>{type = mutable, count = 7, capacity = 8, pairs = (
2 : <CFString 0x42898 [0xa08011c0]>{contents = "debug"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
3 : <CFString 0x428d8 [0xa08011c0]>{contents = "drive-options"} = <CFDictionary 0x3160e0 [0xa08011c0]>{type = mutable, count = 0, capacity = 4, pairs = (
5 : <CFString 0x42888 [0xa08011c0]>{contents = "verbose"} = <CFBoolean 0xa0801884 [0xa08011c0]>{value = false}
6 : <CFString 0x42658 [0xa08011c0]>{contents = "agent"} = <CFString 0x42648 [0xa08011c0]>{contents = "hdiutil"}
7 : <CFString 0x428b8 [0xa08011c0]>{contents = "main-url"} = <CFURL 0x316390 [0xa08011c0]>{type = 0, string = sec3.bak.sparseimage,
base = <CFURL 0x3163f0 [0xa08011c0]>{type = 0, string = /Users/felix/Desktop/si/, base = (null)}}
8 : <CFString 0x428c8 [0xa08011c0]>{contents = "image-options"} = <CFDictionary 0x316110 [0xa08011c0]>{type = mutable, count = 0, capacity = 4, pairs = (
10 : <CFString 0x428a8 [0xa08011c0]>{contents = "quiet"} = <CFBoolean 0xa0801884 [0xa08011c0]>{value = false}
2006-06-13 10:44:39.197 hdiutil[11290] using helper tool at "/System/Library/PrivateFrameworks/DiskImages.framework/Resources/diskimages-he lper".
2006-06-13 10:44:39.232 hdiutil[11290] connectToFramework
2006-06-13 10:44:39.233 hdiutil[11290] connectToFramework: about to ask proxy to perform operation
status proc called: initialize
2006-06-13 10:44:39.254 diskimages-helper[11291] _imageOptions: {"enable-keychain" = 1; }
2006-06-13 10:44:39.254 diskimages-helper[11291] _driveOptions: {autodiskmount = 1; "unmount-timeout" = 0; }
2006-06-13 10:44:39.254 diskimages-helper[11291] DIHelperAttach: initializing framework
DILoadDriver: checking for disk image driver...DILoadDriver: DI_kextExists() returned 0x00000000 (0)...DIIsInitialized: returning NO2006-06-13 10:44:39.266 diskimages-helper[11291] DIHelperAttach: resolving disk image
DIIsInitialized: returning YESDIIsInitialized: returning YESDIBackingStoreNewWithCFURL: entry with
<CFURL 0x3208c0 [0xa08011c0]>{type = 15, string = file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage, base = (null)}
<CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
DIBackingStoreInstantiatorProbe: entry
<CFURL 0x3208c0 [0xa08011c0]>{type = 15, string = file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage, base = (null)}
<CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
CBSDBackingStore::newProbe score 100 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
DIBackingStoreInstantiatorProbe: probing interface 1 CRAMBackingStore
CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
CRAMBackingStore::probe: score -1000 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
DIBackingStoreInstantiatorProbe: probing interface 2 CCarbonBackingStore
CCarbonBackingStore::newProbe: setting initial rval to +100
CCarbonBackingStore::newProbe score 100 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
DIBackingStoreInstantiatorProbe: probing interface 3 CDevBackingStore
CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Users/felix/Desktop/si/sec3.bak.sparseimage).CDevBackingStore::newProbe score -1000 for
DIBackingStoreInstantiatorProbe: probing interface 4 CCURLBackingStore
CCURLBackingStore::probe: scheme is
file
CCURLBackingStore::probe: not recognized URL scheme.
CCURLBackingStore::probe: score -1000 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
DIBackingStoreInstantiatorProbe: probing interface 5 CVectoredBackingStore
CVectoredBackingStore::newProbe not "vectored" scheme.
CVectoredBackingStore::newProbe score -1000 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
DIBackingStoreNewWithCFURL: CBSDBackingStore
DIBackingStoreNewWithCFURL: instantiator returned 0
DIBackingStoreNewWithCFURL: returning 0x00000000
DIResolveURLToBackingStore: processing level 1 encodings.
DIFileEncodingNewWithBackingStore: entry for encoding level 1
DIFileEncodingInstantiatorProbe: entry for level 1
<CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
DIFileEncodingInstantiatorProbe: probing level 1 interface 0 CMacBinaryEncoding
CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
CBSDBackingStore::closeDataFork: about to close 500000000: 4e9d dbc8 b429 00eb e882 36a3 d561 9fbd | N....)....6..a.. |
00000010: ed78 e737 a8bd 55cc f2f3 ad7a 42cd 7379 | .x.7..U....zB.sy |
00000020: 0499 4256 7ae3 df72 f032 664d c214 074c | ..BVz..r.2fM...L |
00000030: 1b84 2b0a b849 18c0 c65a dfd9 0ae8 c6dd | ..+..I...Z...... |
00000040: b6db 15ee 39ce db43 f3cf 7a33 8628 d8b3 | ....9..C..z3.(.. |
00000050: fefa 725e 148d ecda e728 3889 bcb2 bb27 | ..r^.....(8....' |
00000060: 3d78 2e88 652f 8e27 71eb a44a 98ca 3148 | =x..e/.'q..J..1H |
00000070: 0780 a593 0e20 6f81 c2a7 f17d 1d87 5b48 | ..... o....}..[H |
diskimages-helper: fileNameLength $0000009D
diskimages-helper: resourceForkLength $DAE72838
diskimages-helper: dataForkLength $5E148DEC
diskimages-helper: commentLength $00008865
diskimages-helper: MacBinary III signature ?'q? (0x8E2771EB)
diskimages-helper: header CRC $00001D87
diskimages-helper: minimum decoder version $0000007D
diskimages-helper: encoder version $000000F1
no MacBinary III signature - checking for MacBinary I or IIDIFileEncodingInstantiatorProbe: probing level 1 interface 1 CAppleSingleEncoding
CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
00000000: c8db 9d4e eb00 29b4 e882 36a3 d561 9fbd | ...N..)...6..a.. |
00000010: ed78 e737 a8bd 55cc f3f2 ad7a 42cd 7379 | .x.7..U....zB.sy |
00000020: 0499 4256 7ae3 .... .... .... .... .... | ..BVz........... |
CBSDBackingStore::closeDataFork: about to close 5CAppleSingleEncoding::isAppleSingleFile loadAppleSingleHeader failed with error 22
DIFileEncodingInstantiatorProbe: probing level 1 interface 2 CEncryptedEncoding
CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
CBSDBackingStore::closeDataFork: about to close 5DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
DIFileEncodingNewWithBackingStore: returning 0x0000006A
DIResolveURLToBackingStore: level 1 encoding match failed. 106.
(continuing)
DIResolveURLToBackingStore: processing level 2 encodings.
DIFileEncodingNewWithBackingStore: entry for encoding level 2
DIFileEncodingInstantiatorProbe: entry for level 2
<CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
DIFileEncodingInstantiatorProbe: probing level 2 interface 0 CUDIFEncoding
CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
CBSDBackingStore::closeDataFork: about to close 5CUDIFEncoding::newProbe: failing because backing store is not UDIF file
DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
DIFileEncodingNewWithBackingStore: returning 0x0000006A
DIResolveURLToBackingStore: level 2 encoding match failed. 106.
(continuing)
DIResolveURLToBackingStore: processing level 3 encodings.
DIFileEncodingNewWithBackingStore: entry for encoding level 3
DIFileEncodingInstantiatorProbe: entry for level 3
<CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
DIFileEncodingInstantiatorProbe: probing level 3 interface 0 CSegmentedNDIFEncoding
checkTypeCreator: /
checkTypeCreator: returning , score 0
CSegmentedNDIFEncoding::isSegmentedNDIFFile checkTypeCreator failed
DIFileEncodingInstantiatorProbe: probing level 3 interface 1 CSegmentedUDIFEncoding
CSegmentedUDIFEncoding::isSegmentedUDIFFile backing store is not of type CUDIFEncoding
DIFileEncodingInstantiatorProbe: probing level 3 interface 2 CSegmentedUDIFRawEncoding
DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
DIFileEncodingNewWithBackingStore: returning 0x0000006A
DIResolveURLToBackingStore: level 3 encoding match failed. 106.
(continuing)
DIIsInitialized: returning YESDIDiskImageNewWithBackingStore: entry with
<CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
DIDiskImageInstantiatorProbe: entry
<CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
DIDiskImageInstantiatorProbe: probing interface 0 CDARTDiskImage
DIDiskImageInstantiatorProbe: probing interface 1 CDiskCopy42DiskImage
DIDiskImageInstantiatorProbe: probing interface 2 CNDIFDiskImage
checkTypeCreator: /
checkTypeCreator: returning , score 0
CNDIFDiskImage::checkExtension: sparseimage
CNDIFDiskImage::newProbe: checkExtension gives score -1000.
DIDiskImageInstantiatorProbe: probing interface 3 CUDIFDiskImage
CUDIFDiskImage::checkBackingStoreType: backing store is wrong type
DIDiskImageInstantiatorProbe: probing interface 5 CRawDiskImage
checkBackingStoreType returned score 0 type
checkTypeCreator returned score 0 type
CRawDiskImage::checkExtension: sparseimage
checkExtension returned score -1000 type
CRawDiskImage::newWithBackingStore: setBackingStore() failed. 106
CRawDiskImage: checkBackingStoreLength score: -100
DIDiskImageInstantiatorProbe: probing interface 6 CShadowedDiskImage
DIDiskImageInstantiatorProbe: probing interface 7 CSparseDiskImage
CSparseDiskImage::checkExtension: sparseimage
DIDiskImageInstantiatorProbe: probing interface 8 CCFPlugInDiskImage
DIDiskImageInstantiatorProbe: probing interface 9 CWrappedDiskImage
DIBackingStore::inUse: this->_fUniqueID
<CFArray 0x320590 [0xa08011c0]>{type = immutable, count = 1, values = (
0 : <CFString 0x320dc0 [0xa08011c0]>{contents = "d234881026:i316148"}
DI_kextCreateDiskImageIdentifierArray: exiting
<CFArray 0x31fd00 [0xa08011c0]>{type = mutable-small, count = 1, values = (
0 : <CFDictionary 0x321100 [0xa08011c0]>{type = fixed-mutable, count = 1, capacity = 1, pairs = (
3 : <CFString 0x321000 [0xa08011c0]>{contents = "writeable-components"} = <CFArray 0x320fe0 [0xa08011c0]>{type = fixed-mutable, count = 1, capacity = 1, values = (
0 : <CFString 0x321080 [0xa08011c0]>{contents = "d234881026:i1808676"}
DIBackingStore::inUse: checking against image dictionary array
<CFArray 0x3210f0 [0xa08011c0]>{type = immutable, count = 1, values = (
0 : <CFDictionary 0x321100 [0xa08011c0]>{type = fixed-mutable, count = 1, capacity = 1, pairs = (
3 : <CFString 0x321000 [0xa08011c0]>{contents = "writeable-components"} = <CFArray 0x320fe0 [0xa08011c0]>{type = fixed-mutable, count = 1, capacity = 1, values = (
0 : <CFString 0x321080 [0xa08011c0]>{contents = "d234881026:i1808676"}
DIBackingStore::inUse: checking our list looking for who's naughty and nice
DIBackingStore::inUse: checking image 0000
CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
syncPhysicalAndLogicalForkLengths: returning 0 (cached logEOF: 1540853760, physEOF: 1540853760)
CBSDBackingStore::closeDataFork: about to close 5CSparseFile::~CSparseFile: WARNING flushing header and index nodes failed. Invalid argument
syncPhysicalAndLogicalForkLengths: entry (cached logEOF: 1540853760, physEOF: 1540853760)
: returning 0 (new cached logEOF: 1540853760, physEOF: 1540853760)
DIDiskImageNewWithBackingStore: returning 0x00000067
DIResolveBackingStoreToDiskImage: unable to resolve to any disk image class. 103.
DIResolveURLToDiskImage: resolving disk image format failed. 103.
status proc called: attach
error code: 103
status proc called: cleanup
2006-06-13 10:44:39.684 diskimages-helper[11291] DIHelperAttach performOperation: returning 103
2006-06-13 10:44:39.684 diskimages-helper[11291] DIHelper perform_operation: returning {payload = {}; "result-code" = 103; }
2006-06-13 10:44:39.684 hdiutil[11290] connectToFramework: proxy has finished operation
2006-06-13 10:44:39.685 hdiutil[11290] results are: {payload = {}; "result-code" = 103; }
2006-06-13 10:44:39.685 hdiutil[11290] _threadResultsError is 103
2006-06-13 10:44:39.685 hdiutil[11290] connectToFramework: terminating proxy
2006-06-13 10:44:39.686 diskimages-helper[11291] terminateHelper
DIHLDiskImageAttach() returned 103
<CFDictionary 0x3245a0 [0xa08011c0]>{type = immutable, count = 0, capacity = 0, pairs = (
hdiutil: attach failed - Defektes Image
si 2006-06-13 10:44:39.786 diskimages-helper[11291] -DIHelperAgentMaster terminateUIAgentConnection
2006-06-13 10:44:39.786 diskimages-helper[11291] -exitIfPossible:0 (_drivesServed 0)
2006-06-13 10:44:39.787 diskimages-helper[11291] -exitWatchThread: trying to get exit lock
2006-06-13 10:44:39.787 diskimages-helper[11291] -exitWatchThread: got exit lock
2006-06-13 10:44:39.787 diskimages-helper[11291] -exitWatchCompleted:0
2006-06-13 10:44:40.788 diskimages-helper[11291] suicide:<NSCFTimer: 0x3217d0>
cheers, felix
MBP 15" Mac OS X (10.4.6)

The key expansion does not work with a substring of the upper hash functions. Create a sparseimage with the password asdf and try the following script:
#!/opt/local/bin/perl
use Crypt::GCrypt;
my $tmp;
my $i;
my $subkey;
# asdf
%pw = (
ph => (pack "H*", "61736466000000000000000000000000"),
pl => (pack "H*", "00000000000000000000000061736466"),
md5 => (pack "H*", "912ec803b2ce49e4a541068d495ab570"),
sha1 => (pack "H*", "3da541559918a808c2402bba5012f6c60b27661c"),
sha => (pack "H*", "71f2cbe0db64c15e9e385525ad5ef854c494898f"),
sha256 => (pack "H*", "f0e4c2f76c58916ec258f246851bea091d14d4247a2fc3e18694461b1816e13b"),
sha512 => (pack "H*", "401b09eab3c013d4ca54922bb802bec8fd5318192b0a75f201d8b3727429080fb337591abd3e44 453b954555b7a0812e1081c39b740293f765eae731f5a65ed1"),
open (INFILE, "< $ARGV[0]") or die "Could not open $filename for reading: $!";
read(INFILE,$tmp,128);
close INFILE;
foreach my $key (keys %pw) {
for($i=16;$i <= length $pw{$key};$i++) {
$subkey = substr($pw{$key},$i-16,16);
#print "------using $key with $pw{$key} and substr $subkey-------";
$cipher = Crypt::GCrypt->new(
type => 'cipher',
algorithm => 'aes',
mode => 'ecb'
$cipher->start('decrypting');
$cipher->setkey($subkey);
print $cipher->decrypt($tmp);
}

SA_MAGIC header corrupt on ZFS causing kernel panic in S11.1 SRU5.5

I have a number of Sun Fire x4500s and x4540s running S11.1 SRU5.5. One of the x4540s has recently started kernel panicking within minutes of powering on and sharing its file systems over NFS (it provides user directories for a computing cluster). If I don't share via NFS, the kernel panics do not occur.
When I run mdb on the kernel panic coredump I get:
\> ::panicinfo
cpu 1
thread fffffffc80e52c20
message
assertion failed: BSWAP_32(hdr->sa_magic) == SA_MAGIC, file: ../../common/fs/zfs/sa.c, line: 2079
\> ::stack
vpanic()
0xfffffffffbac1081()
sa_get_field64+0x96(ffffc1c0aaf34a00, 18)
zfs_space_delta_cb+0x46(2c, ffffc1c0aaf34a00, fffffffc80e52840, fffffffc80e52848)
dmu_objset_userquota_get_ids+0xca(ffffc1c1085d9008, 0, ffffc1c080796640)
dnode_sync+0xa7(ffffc1c1085d9008, ffffc1c080796640)
dmu_objset_sync_dnodes+0x7f(ffffc1c0299a5b00, ffffc1c0299a5a80, ffffc1c080796640)
dmu_objset_sync+0x1e2(ffffc1c0299a5940, ffffc1c07f0d17c8, ffffc1c030756680, ffffc1c080796640)
dsl_dataset_sync+0x63(ffffc1c0418cd300, ffffc1c07f0d17c8, ffffc1c080796640)
dsl_pool_sync+0xdb(ffffc1c0285493c0, 2c720a)
spa_sync+0x395(ffffc1c01b1f6a80, 2c720a)
txg_sync_thread+0x244(ffffc1c0285493c0)
thread_start+8()In doing some google searching, I'm able to infer from similar lines of code in OpenSolaris (and various ZFS derivatives) that the point of this line of code is to ensure that a ZFS block has a particular header with the correct endianness. Lines of code just prior to this swap the endianness if its is incorrect (at least in these derivatives). For example:
[ZFS corruption probably from bad RAM|https://github.com/zfsonlinux/spl/issues/157]
[FreeBSD kernel panic|http://lists.freebsd.org/pipermail/freebsd-stable/2012-July/068882.html]
[ZFSOnLinux Panic|https://github.com/zfsonlinux/zfs/issues/1303]
So basically, this assert ought to work unless the header was written to disk incorrectly. I've recently done a resilver since a disk had failed and I'm currently in the middle of a scrub with estimated 90h to go. It did fix about 12kb of mistakes on the scrub even though it was right after the resilver.
Nevertheless, I don't think this should be able to happen unless the redundant copies of this header were also corrupted.
I wrote a little script that loops over process IDs and addresses in the core dump and prints this for each
echo $addr | awk '{print $1,"::pfiles"}' | mdb $DMPNO
The files that are open are all device files (eg./devices/pseudo/...) or things in /var, /etc, /lib, things like that. The user directories/files do not appear to be actively open in the core dump. That said, I cannot match the thread above to a process ID. So maybe there are open files that are not captured in the core dump
Since the machine will panic when I make NFS available, I am currently doing two things to try to resolve the problem:
(1) a zpool scrub
(2) "zfs send"ing a snapshot of every filesystem straight to /dev/null
The idea behind (2) is that eventually I'll read the bad block and force the kernel panic to happen. I'll infer from the log of the script which filesystem is bad and NFS share all the others.
You should assume that I can spell mdb, but not much more than that and everything I've done thus far has been mimicking things I have found in google searching.
Thanks for any advice the community has to help me fix the bad file/filesystem. I am happy to provide more details from mdb or whatever is needed.
Tom
Edited by: 998996 on Apr 9, 2013 7:13 AM
Edited by: 998996 on Apr 9, 2013 7:13 AM
Edited by: 998996 on Apr 9, 2013 7:14 AM
Edited by: 998996 on Apr 9, 2013 7:18 AM
Edited by: 998996 on Apr 9, 2013 8:48 AM

The output of fmdump is below. On March 27th, 3 disks were automatically identified as having too many errors and were pulled from their zpools. I replaced them on April 2nd (I believe) and, while they were resilvering, kernel panics started happening on April 6th. After several panic / reboot cycles, I disabled NFS and have not experienced any panics sense. The resilver finished sometime on April 7th (I think) and I started a zpool scrub relatively soon thereafter.
Mar 27 11:21:05.6894 2b5fca6d-8a55-6a16-d59a-86abf600ce1e DISK-8000-0X Diagnosed
Mar 27 11:21:18.2224 335f323c-c723-e67f-c194-a346edde5f41 DISK-8000-0X Diagnosed
Mar 27 11:21:43.8004 f515a18e-235d-c9e8-9b11-ff7284ed1b48 DISK-8000-0X Diagnosed
Mar 31 12:27:08.8977 864387c6-9b50-6f90-d710-9e213a0ba327 SUNOS-8000-KL Diagnosed
Apr 02 15:37:45.7040 2b5fca6d-8a55-6a16-d59a-86abf600ce1e FMD-8000-58 Updated
Apr 02 15:37:45.8345 335f323c-c723-e67f-c194-a346edde5f41 FMD-8000-58 Updated
Apr 02 15:37:45.9517 f515a18e-235d-c9e8-9b11-ff7284ed1b48 FMD-8000-58 Updated
Apr 02 15:50:44.1012 2b5fca6d-8a55-6a16-d59a-86abf600ce1e FMD-8000-4M Repaired
Apr 02 15:50:44.1429 2b5fca6d-8a55-6a16-d59a-86abf600ce1e FMD-8000-6U Resolved
Apr 02 15:51:00.5162 f515a18e-235d-c9e8-9b11-ff7284ed1b48 FMD-8000-4M Repaired
Apr 02 15:51:00.5614 f515a18e-235d-c9e8-9b11-ff7284ed1b48 FMD-8000-6U Resolved
Apr 02 15:51:18.9518 335f323c-c723-e67f-c194-a346edde5f41 FMD-8000-4M Repaired
Apr 02 15:51:18.9959 335f323c-c723-e67f-c194-a346edde5f41 FMD-8000-6U Resolved
Apr 02 15:55:22.0946 1ccd6f62-7607-6f63-9069-9d947691df4b ZFS-8000-LR Diagnosed
Apr 02 15:56:14.7847 f8d032c1-5d6e-e742-f01a-e2f38ccc6ce8 ZFS-8000-QJ Diagnosed
Apr 02 15:59:05.6633 5564cf7e-3648-cd69-915f-9b6757509bae ZFS-8000-QJ Diagnosed
Apr 02 15:59:05.8154 0214c0e7-59b6-47ca-c8c6-853d76713257 ZFS-8000-D3 Diagnosed
Apr 02 16:01:14.5517 513db3ba-27a7-c8f2-f50e-8ef58c0fa71c ZFS-8000-QJ Diagnosed
Apr 06 05:49:43.6917 eddb3a8f-9117-cfa8-8784-a1fceb242f7f SUNOS-8000-KL Diagnosed
Apr 06 06:44:24.2562 6186711a-735a-67f7-9226-be419378c70e SUNOS-8000-KL Diagnosed
Apr 06 07:20:45.2416 33b36e54-c2cd-ee0e-b370-821a00d342fe SUNOS-8000-KL Diagnosed
Apr 06 08:05:29.7940 a7f6d49b-6b15-ef5a-ca58-911e2c6b1196 SUNOS-8000-KL Diagnosed
Apr 06 08:28:06.7965 e4eea2e9-c800-e1c9-bd53-c45af9b616b0 SUNOS-8000-KL Diagnosed
Apr 06 08:56:21.9017 a51779c9-549a-4334-f102-d26ff958c566 SUNOS-8000-KL Diagnosed
Apr 06 09:26:33.7999 25e4e137-7962-e70f-ea91-f77dfdd8238b SUNOS-8000-KL Diagnosed
Apr 06 09:47:56.5975 2d416320-f69e-e5c5-ea66-cafab1997546 SUNOS-8000-KL Diagnosed
Apr 06 10:19:35.7141 ae4e7ef4-bbf5-e80a-8e30-8a99bafbc352 SUNOS-8000-KL Diagnosed
Apr 06 11:07:14.7489 abc3c89c-d9f9-ee00-e546-99cbff435810 SUNOS-8000-KL Diagnosed
Apr 06 11:51:31.1321 7aa0ab5e-d54c-4201-e56f-e8a502bb063e SUNOS-8000-KL Diagnosed
Apr 06 12:17:42.4073 46d85a95-8f15-c0ea-e061-f241628d124a SUNOS-8000-KL Diagnosed
Apr 06 12:48:15.4996 d16c0c54-33d5-c463-dae8-fc8cc82e517b SUNOS-8000-KL Diagnosed
Apr 06 13:14:45.4799 021e8659-5359-edea-c7e9-8551c7de6d2c SUNOS-8000-KL Diagnosed
Apr 06 13:51:56.5406 89620151-c97f-4256-8347-f412ee416282 SUNOS-8000-KL Diagnosed
Apr 06 14:11:47.2594 b9923bc1-46d6-4fb6-ec7d-f3a1e0076419 SUNOS-8000-KL Diagnosed
Apr 07 12:54:49.3759 513db3ba-27a7-c8f2-f50e-8ef58c0fa71c FMD-8000-4M Repaired
Apr 07 12:54:49.4121 513db3ba-27a7-c8f2-f50e-8ef58c0fa71c FMD-8000-6U Resolved
Apr 07 12:54:49.5092 0214c0e7-59b6-47ca-c8c6-853d76713257 FMD-8000-4M Repaired
Apr 07 12:54:49.5368 0214c0e7-59b6-47ca-c8c6-853d76713257 FMD-8000-6U Resolved
Apr 07 12:54:49.5864 5564cf7e-3648-cd69-915f-9b6757509bae FMD-8000-4M Repaired
Apr 07 12:54:49.6064 5564cf7e-3648-cd69-915f-9b6757509bae FMD-8000-6U Resolved
Apr 07 12:54:49.6367 f8d032c1-5d6e-e742-f01a-e2f38ccc6ce8 FMD-8000-4M Repaired
Apr 07 12:54:49.6498 f8d032c1-5d6e-e742-f01a-e2f38ccc6ce8 FMD-8000-6U Resolved
Apr 07 12:54:49.7409 1ccd6f62-7607-6f63-9069-9d947691df4b FMD-8000-4M Repaired
Apr 07 12:54:49.7585 1ccd6f62-7607-6f63-9069-9d947691df4b FMD-8000-6U Resolved
The output of fmadm faulty and fmdump -eV are quite long:
https://pantherfile.uwm.edu/downes/public/fmdump_ev.txt
https://pantherfile.uwm.edu/downes/public/fmadm_faulty.txt
I note a number of events on April 9th in the output of fmdump -eV. Maybe these are the scrub fixing things?
Tom

Kernel panic - corrupt stack

My iBook g4 has a kernel panic (below text).
It did a '3 beeb, flash light 5 times' crash last week but then re-booted fine. About 4 months ago, this happened repeatedly and the 'power down now' error message appeared on a black screen. Finally it refused to boot up at all and we took it apart and found a loose connection inside (I don't know what it was), reattached it and it has worked fine since.
Am worried as I have stupidly not backed up recently and have a website on there that is due to posted. Please help!
<start>
System failure: cpu=0; code=00000001 (Corrupt stack)
Latest crash info for cpu 0:
Exception state (sv=0x19DC1000)
PC=0x000940A0; MSR0x00001030; DAR=0x00000000; DSIR=0x42000000; LR=0x00093F8C; R1=0xFFFFFEE0; XCP=0x00000098 (System failure)
Backtrace:
backtrace terminated - frame not mapped or invalid: 0xFFFFFEE0
Proceeding back via exemption chain:
Exception state (sv0x19DC1000)
PC=0x00094160; MSR=0x00001030; DAR=0x00000000; DSISR=0x42000000; LR=0x0009413C; R1=0x00000000; XCP=0x00000000C (0x300 - Data access)
Exception state (sv0x19B6CC80)
PC=0x90026BC8; MSR=0x0200F030; DAR=0x003B7018; DSISR=0x42000000; LR=0x90008DC0; R1=0xBFFFEB40; XCP=0x000000030 (0xC00 - System call)
Kernel version:
Darwin kernel version 7.9.0:
Wed Mar 30 28:11:17 PST 2005; root:xnu/xnu-517.12.7.obj-1/RELEASE_PPC
Memory access exception (1,0,0)
ethernet MAC address: 00:00:00:00:00:00
ip address: 0.0.0.0
Waiting for remote debugger connection
<end>
iBook G4 Mac OS X (10.4.10)

First, sorry for the delay, I only work a few days a week
Second, there is no panic.log on any of the machines. I looked in the console and system profiler programs in all the directories and searched in terminal using 'find / -name panic.log 2> /dev/null'. That is one reason I had to take a picture of it. I will try hard to get a panic.log.
Keep in mind that these are very hard lockups so I am wondering if the kernel even CAN sync the log to disk in this situation. However, I come from the Linux world and am fairly new to Macs so perhaps I am expecting it to be a hardware problem when software really can make a Mac Kernel lockup.
Furthermore they are networked together, we use LDAP/NFS home directories but each machine was prepared with it's own local copy of CS2. There is no sharing of the application.
Also, i tried a boot with apple-v but all went well and there were no out of place message.
Since my first posting I have also tried an fsck which revealed nothing but a clean FS.
Also, we do use radmind to help clone machines. The OS was installed manually with our application loaded using radmind templates.
We do use our Macs very heavily and use many applications at once using all RAM and heavy swap. Do the Mac Minis not like to be exercised hard? I think I may try to use a 1GB stick in a machine and see if that helps.
Also, could CS2 really cause a complete lockup of the machine with a corrupt stack? To me an application-level program should never cause the machine to freeze or should never be able to corrupt memory it doesnt own unless the OS lets it meddle with hardware.

Aperture Kernel Panics & Fusion Disk Corruptions

Similar Messages

Maybe you are looking for