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.

Similar Messages

Airport causing kernel panics and kp in safe boot.

Last week I got my first kernel panic in years. It happened while I was asleep and checking an extrenal drive for bad blocks with TechTool. It turns out that the drive indeed had bad blocks and found that the cpu was shut down when I awoke. I started up the computer and it wasn't able to stay on for more than 10 min max before the next kernel panic. I checked here for more advice on kernel panics and started to try to narrow the number of culprits. Everything was unplugged and still kp. Instaled a new drive with a week older system from Time Machine and still kp. Reset NVRAM and replaced pyhsical RAM and still kp. Removed the Airport Extreme card and still kp. Booted into Safe Mode after all of the previously mentioned and still kp. I'm now going to take the drive and swap it into another body that I have to see if the root is actually on the drive on the physical hardware of the cpu.
I was interested in this thread and read all of the links that jpl posted. Airport causing Kernel Panic (?) Jason then replied that it had been solved due to a "permissions problem" I wish he gave more info on what exactly he did to resolve the problem as it's been almost a week now without any work being done for me.
I've also noticed this very strange behavior that might shed some light onto the issue. When I open System Prefs and close the window there is a strange colored pattern that will always flash after the window has been closed. I tried to post it to my me page but for somereason it wouldn't play for me so there's that and the YouTube version too.
https://www.me.com/gallery/#100008/Prefs%20Screen
http://www.youtube.com/watch?v=2zrTt88YdBo
In addition when the computer has started up and the system loads. Checking Activity Monitor shows that there are 50 or more threads active for the the kernel_task. Inspecting this doesn't seem to show any useful information.
Finally here are a few of the recent crashes I hope that someone might be able to shed some light on this extremely frustrating problem for me.
Tue Oct 25 18:54:16 2011
panic(cpu 0 caller 0x000AE584): "Uncorrectable machine check: pc = 00000000000A388C, msr = 0000000000141000, dsisr = 42000000, dar = 0000000000272008\n" " AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000\n" "     L2FIR = 0000000000000000, BusFir = 0000000080000000\n"@/SourceCache/xnu/xnu-1228/osfmk/ppc/trap.c:975
Latest stack backtrace for cpu 0:
      Backtrace:
         0x0009AD18 0x0009B6BC 0x00029DC4 0x000AE584 0x000AE804 0x000B22F8
Proceeding back via exception chain:
   Exception state (sv=0x2fc12c80)
      PC=0x000A388C; MSR=0x00141000; DAR=0x00272008; DSISR=0x42000000; LR=0x000A37C8; R1=0x2E947B40; XCP=0x00000008 (0x200 - Machine check)
      Backtrace:
0x00000000 0x000A09C8 0x0009E2EC 0x0006B3C0 0x0006C728 0x0003BE1C
         0x0029361C 0x0029364C 0x0030924C 0x000B24C8 0x00000000
   Exception state (sv=0x249dba00)
      PC=0x9195435C; MSR=0x0000F030; DAR=0x00272000; DSISR=0x42000000; LR=0x00001FA8; R1=0xBFFFFB00; XCP=0x00000030 (0xC00 - System call)
BSD process name corresponding to current thread: PubSubAgent
Mac OS version:
9A581
Kernel version:
Darwin Kernel Version 9.0.0: Tue Oct 9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
Tue Oct 25 19:09:54 2011
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000FFFFFFFF PC=0x0000000000040DE4
Latest crash info for cpu 0:
   Exception state (sv=0x3c19ca00)
      PC=0x00040DE4; MSR=0x00001030; DAR=0xFFFFFFFF; DSISR=0x40000000; LR=0x00040D94; R1=0x33B63D50; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x0293EA14 0x0004147C 0x0001EB60 0x00025960 0x000B264C 0x00000000
Proceeding back via exception chain:
   Exception state (sv=0x3c19ca00)
      previously dumped as "Latest" state. skipping...
   Exception state (sv=0x3297b500)
      PC=0x919419D8; MSR=0x0000D030; DAR=0x0073C000; DSISR=0x42000000; LR=0x91948900; R1=0xF00807A0; XCP=0x00000030 (0xC00 - System call)
BSD process name corresponding to current thread: mdworker
Mac OS version:
9A581
Kernel version:
Darwin Kernel Version 9.0.0: Tue Oct 9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): copyin/out has no recovery point
Latest stack backtrace for cpu 0:
      Backtrace:
         0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEB88 0x000B22F8
Proceeding back via exception chain:
   Exception state (sv=0x3c19ca00)
      PC=0x00040DE4; MSR=0x00001030; DAR=0xFFFFFFFF; DSISR=0x40000000; LR=0x00040D94; R1=0x33B63D50; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x0293EA14 0x0004147C 0x0001EB60 0x00025960 0x000B264C 0x00000000
   Exception state (sv=0x3297b500)
      PC=0x919419D8; MSR=0x0000D030; DAR=0x0073C000; DSISR=0x42000000; LR=0x91948900; R1=0xF00807A0; XCP=0x00000030 (0xC00 - System call)
BSD process name corresponding to current thread: mdworker
Wed Oct 26 15:31:02 2011
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000FFFFFFFF PC=0x0000000000040DE4
Latest crash info for cpu 0:
   Exception state (sv=0x3c19ca00)
      PC=0x00040DE4; MSR=0x00001030; DAR=0xFFFFFFFF; DSISR=0x40000000; LR=0x00040D94; R1=0x33B63D50; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x0293EA14 0x0004147C 0x0001EB60 0x00025960 0x000B264C 0x00000000
Proceeding back via exception chain:
   Exception state (sv=0x3c19ca00)
      previously dumped as "Latest" state. skipping...
   Exception state (sv=0x3297b500)
      PC=0x919419D8; MSR=0x0000D030; DAR=0x0073C000; DSISR=0x42000000; LR=0x91948900; R1=0xF00807A0; XCP=0x00000030 (0xC00 - System call)
BSD process name corresponding to current thread: mdworker
Mac OS version:
9A581
Kernel version:
Darwin Kernel Version 9.0.0: Tue Oct 9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): copyin/out has no recovery point
Latest stack backtrace for cpu 0:
      Backtrace:
         0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEB88 0x000B22F8
Proceeding back via exception chain:
   Exception state (sv=0x3c19ca00)
      PC=0x00040DE4; MSR=0x00001030; DAR=0xFFFFFFFF; DSISR=0x40000000; LR=0x00040D94; R1=0x33B63D50; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x0293EA14 0x0004147C 0x0001EB60 0x00025960 0x000B264C 0x00000000
   Exception state (sv=0x3297b500)
      PC=0x919419D8; MSR=0x0000D030; DAR=0x0073C000; DSISR=0x42000000; LR=0x91948900; R1=0xF00807A0; XCP=0x00000030 (0xC00 - System call)
BSD process name corresponding to current thread: mdworker
Wed Oct 26 22:17:42 2011
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000010 PC=0x0000000000082EF8
Latest crash info for cpu 0:
   Exception state (sv=0x2514ea00)
      PC=0x00082EF8; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x00082ECC; R1=0x24F6BB60; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x00000000 0x000848C0 0x00077BD0 0x0007823C 0x0007920C 0x0006B718
         0x0006C728 0x00296378 0x0030924C 0x000B24C8 0x00000000
Proceeding back via exception chain:
   Exception state (sv=0x2514ea00)
      previously dumped as "Latest" state. skipping...
   Exception state (sv=0x2509d500)
      PC=0x9194AF64; MSR=0x0000D930; DAR=0xE1000000; DSISR=0x42000000; LR=0x9194CC90; R1=0xBFFFE9A0; XCP=0x00000030 (0xC00 - System call)
BSD process name corresponding to current thread: launchd
Mac OS version:
9A581
Kernel version:
Darwin Kernel Version 9.0.0: Tue Oct 9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
      Backtrace:
         0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEA90 0x000B22F8
Proceeding back via exception chain:
   Exception state (sv=0x2514ea00)
      PC=0x00082EF8; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x00082ECC; R1=0x24F6BB60; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x00000000 0x000848C0 0x00077BD0 0x0007823C 0x0007920C 0x0006B718
         0x0006C728 0x00296378 0x0030924C 0x000B24C8 0x00000000
   Exception state (sv=0x2509d500)
      PC=0x9194AF64; MSR=0x0000D930; DAR=0xE1000000; DSISR=0x42000000; LR=0x9194CC90; R1=0xBFFFE9A0; XCP=0x00000030 (0xC00 - System call)
BSD process name corresponding to current thread: launchd
Thu Oct 27 11:28:35 2011
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000004 PC=0x00000000000848E0
Latest crash info for cpu 0:
   Exception state (sv=0x248ff500)
      PC=0x000848E0; MSR=0x00009030; DAR=0x00000004; DSISR=0x42000000; LR=0x000848AC; R1=0x30063BB0; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x000848C0 0x00077BD0 0x0007823C 0x0007920C 0x0006B718 0x0006C728
         0x00296378 0x0030924C 0x000B24C8 0x00000000
Proceeding back via exception chain:
   Exception state (sv=0x248ff500)
      previously dumped as "Latest" state. skipping...
   Exception state (sv=0x248fd280)
      PC=0x9194AF64; MSR=0x0000D030; DAR=0xE1000000; DSISR=0x42000000; LR=0x9194CC90; R1=0xBFFFE7F0; XCP=0x00000030 (0xC00 - System call)
BSD process name corresponding to current thread: launchd
Mac OS version:
9A581
Kernel version:
Darwin Kernel Version 9.0.0: Tue Oct 9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
      Backtrace:
         0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEA90 0x000B22F8
Proceeding back via exception chain:
   Exception state (sv=0x248ff500)
      PC=0x000848E0; MSR=0x00009030; DAR=0x00000004; DSISR=0x42000000; LR=0x000848AC; R1=0x30063BB0; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x000848C0 0x00077BD0 0x0007823C 0x0007920C 0x0006B718 0x0006C728
         0x00296378 0x0030924C 0x000B24C8 0x00000000
   Exception state (sv=0x248fd280)
      PC=0x9194AF64; MSR=0x0000D030; DAR=0xE1000000; DSISR=0x42000000; LR=0x9194CC90; R1=0xBFFFE7F0; XCP=0x00000030 (0xC00 - System call)
BSD process name corresponding to current thread: launchd
Thanks in advance,
Max

My vision is pretty poor, still cant see it, but...
At this point I think you should get Applejack...
http://www.macupdate.com/info.php/id/15667/applejack
After installing, reboot holding down CMD+s, (+s), then when the DOS like prompt shows, type in...
applejack AUTO
Then let it do all 6 of it's things.
At least it'll eliminate some questions if it doesn't fix it.
The 6 things it does are...
Correct any Disk problems.
Repair Permissions.
Clear out Cache Files.
Repair/check several plist files.
Dump the VM files for a fresh start.
Trash old Log files.
First reboot will be slower, sometimes 2 or 3 restarts will be required for full benefit... my guess is files relying upon other files relying upon other files! :-)
Disconnect the USB cable from any Uninterruptible Power Supply so the system doesn't shut down in the middle of the process.

PS Extended CS6 causing kernel panics

I've been getting one or two a week. Haven't figured out yet what triggers it, but it only happens in CS6. I did recently reinstall the entire OS, so that's clean. Here's the latest panic info the reboot generates to send to Apple. Doesn't mean anything to me, other than the panic notation near the top of the info tells you what it thinks happened.
Interval Since Last Panic Report: 141469 sec
Anonymous UUID:                    44199F46-5B6B-42C5-9E13-29CB09291223
Mon Sep 24 14:40:11 2012
panic(cpu 2 caller 0xffffff80002094e7): "thread_invoke: preemption_level -1, possible cause: unlocking an unlocked mutex or spinlock"@/SourceCache/xnu/xnu-1504.15.3/osfmk/kern/sched_prim.c:1471
Backtrace (CPU 2), Frame : Return Address
0xffffff8149e83d70 : 0xffffff8000204d15
0xffffff8149e83e70 : 0xffffff80002094e7
0xffffff8149e83ef0 : 0xffffff8000209acb
0xffffff8149e83f60 : 0xffffff800053b02d
0xffffff8149e83fa0 : 0xffffff80002c8527
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10K549
Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64
System model name: MacPro5,1 (Mac-F221BEC8)
System uptime in nanoseconds: 26760035257178
unloaded kexts:
com.apple.iokit.IOFireWireSBP2          4.0.6 (addr 0xffffff7f80e4a000, size 0x73728) - last unloaded 25651433036012
loaded kexts:
com.aladdin.kext.aksfridge          1.0.2
com.dvdfab.kext.fabio          1
com.hzsystems.terminus.driver          4
com.microsoft.driver.MicrosoftKeyboardUSB          8.2
com.microsoft.driver.MicrosoftKeyboard          8.2
com.Logitech.Control Center.HID Driver          3.6.0
com.apple.filesystems.afpfs          9.7.1 - last loaded 23445647212129
com.apple.nke.asp_tcp          5.0
com.apple.driver.AppleHWSensor          1.9.3d0
com.apple.driver.AppleTyMCEDriver          1.0.2d2
com.apple.driver.AGPM          100.12.31
com.apple.driver.AppleUpstreamUserClient          3.5.7
com.apple.driver.AppleMCCSControl          1.0.20
com.apple.driver.AppleMikeyHIDDriver          1.2.0
com.apple.kext.ATIFramebuffer          6.3.6
com.apple.driver.AppleHDA          2.0.5f14
com.apple.driver.AppleMikeyDriver          2.0.5f14
com.apple.driver.AudioAUUC          1.57
com.apple.filesystems.ntfs          3.4
com.apple.ATIRadeonX3000          6.3.6
com.apple.filesystems.autofs          2.1.0
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.AudioIPCDriver          1.1.6
com.apple.driver.ACPI_SMC_PlatformPlugin          4.7.0a1
com.apple.driver.AppleLPC          1.5.1
com.apple.iokit.IOAHCIBlockStorage          1.6.4
com.apple.iokit.SCSITaskUserClient          2.6.8
com.apple.BootCache          31.1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.driver.AppleFWOHCI          4.7.3
com.apple.driver.AppleUSBOHCI          4.2.0
com.apple.driver.AppleUSBHub          4.2.4
com.apple.driver.AirPortBrcm43224          428.42.4
com.apple.driver.AppleAHCIPort          2.1.7
com.apple.driver.Intel82574L          2.1.8b1
com.apple.driver.AppleUSBEHCI          4.2.4
com.apple.driver.AppleUSBUHCI          4.2.0
com.apple.driver.AppleEFINVRAM          1.4.0
com.apple.driver.AppleRTC          1.3.1
com.apple.driver.AppleHPET          1.5
com.apple.driver.AppleACPIButtons          1.3.6
com.apple.driver.AppleSMBIOS          1.7
com.apple.driver.AppleACPIEC          1.3.6
com.apple.driver.AppleAPIC          1.4
com.apple.driver.AppleIntelCPUPowerManagementClient          142.6.0
com.apple.security.sandbox          1
com.apple.security.quarantine          0
com.apple.nke.applicationfirewall          2.1.14
com.apple.driver.AppleIntelCPUPowerManagement          142.6.0
com.apple.driver.AppleProfileReadCounterAction          17
com.apple.driver.DspFuncLib          2.0.5f14
com.apple.driver.AppleProfileTimestampAction          10
com.apple.driver.AppleProfileThreadInfoAction          14
com.apple.driver.AppleProfileRegisterStateAction          10
com.apple.driver.AppleProfileKEventAction          10
com.apple.driver.AppleProfileCallstackAction          20
com.apple.iokit.IONDRVSupport          2.2.1
com.apple.driver.AppleSMBusController          1.0.10d0
com.apple.kext.ATI5000Controller          6.3.6
com.apple.kext.ATISupport          6.3.6
com.apple.iokit.IOFireWireIP          2.0.3
com.apple.iokit.IOSurface          74.2
com.apple.iokit.IOBluetoothSerialManager          2.4.5f3
com.apple.iokit.IOSerialFamily          10.0.3
com.apple.iokit.IOAudioFamily          1.8.3fc2
com.apple.kext.OSvKernDSPLib          1.3
com.apple.driver.AppleHDAController          2.0.5f14
com.apple.iokit.IOGraphicsFamily          2.2.1
com.apple.iokit.IOHDAFamily          2.0.5f14
com.apple.iokit.AppleProfileFamily          41
com.apple.driver.AppleSMC          3.1.0d5
com.apple.driver.IOPlatformPluginFamily          4.7.0a1
com.apple.driver.AppleSMBusPCI          1.0.10d0
com.apple.driver.BroadcomUSBBluetoothHCIController          2.4.5f3
com.apple.driver.AppleUSBBluetoothHCIController          2.4.5f3
com.apple.driver.IOBluetoothHIDDriver          2.4.5f3
com.apple.iokit.IOBluetoothFamily          2.4.5f3
com.apple.iokit.IOUSBHIDDriver          4.2.0
com.apple.driver.AppleUSBMergeNub          4.2.4
com.apple.driver.AppleUSBComposite          3.9.0
com.apple.driver.XsanFilter          402.1
com.apple.iokit.IOSCSIMultimediaCommandsDevice          2.6.8
com.apple.iokit.IOBDStorageFamily          1.6
com.apple.iokit.IODVDStorageFamily          1.6
com.apple.iokit.IOCDStorageFamily          1.6.1
com.apple.iokit.IOFireWireFamily          4.2.6
com.apple.iokit.IOAHCISerialATAPI          1.2.6
com.apple.iokit.IOSCSIArchitectureModelFamily          2.6.8
com.apple.iokit.IO80211Family          320.1
com.apple.iokit.IOUSBUserClient          4.2.4
com.apple.iokit.IOAHCIFamily          2.0.6
com.apple.iokit.IONetworkingFamily          1.10
com.apple.iokit.IOUSBFamily          4.2.4
com.apple.driver.AppleEFIRuntime          1.4.0
com.apple.iokit.IOHIDFamily          1.6.6
com.apple.iokit.IOSMBusFamily          1.1
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          6
com.apple.driver.DiskImages          289.1
com.apple.iokit.IOStorageFamily          1.6.3
com.apple.driver.AppleACPIPlatform          1.3.6
com.apple.iokit.IOPCIFamily          2.6.5
com.apple.iokit.IOACPIFamily          1.3.0
Model: MacPro5,1, BootROM MP51.007F.B03, 6 processors, 6-Core Intel Xeon, 3.33 GHz, 16 GB, SMC 1.39f11
Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.10.131.42.4)
Bluetooth: Version 2.4.5f3, 2 service, 12 devices, 1 incoming serial ports
Network Service: Ethernet 2, Ethernet, en1
PCI Card: pci104c,823f, sppci_ieee1394openhci, Slot-3@6,0,0
PCI Card: pci1033,35, sppci_usbopenhost, Slot-3@8,0,0
PCI Card: pci1033,e0, USB Enhanced Host Controller, Slot-3@8,0,1
PCI Card: pci1033,35, sppci_usbopenhost, Slot-4@11,0,0
PCI Card: pci1033,35, sppci_usbopenhost, Slot-4@11,0,1
PCI Card: pci1033,e0, USB Enhanced Host Controller, Slot-4@11,0,2
PCI Card: ATI Radeon HD 5770, sppci_displaycontroller, Slot-1
Serial ATA Device: HL-DT-ST DVD-RW GH61N
Serial ATA Device: HL-DT-ST BD-RE GGW-H20L
Serial ATA Device: WDC WD1001FALS-41Y6A1, 931.51 GB
Serial ATA Device: Hitachi HDS722020ALA330, 1.82 TB
Serial ATA Device: WDC WD3200AAKS-00VYA0, 298.09 GB
USB Device: Hub, 0x0409 (NEC Corporation), 0x005a, 0xfd300000 / 2
USB Device: EIZO USB HID Monitor, 0x056d (Eizo), 0x0002, 0xfd330000 / 3
USB Device: USB 2.0 Hub [MTT], 0x1a40 (TERMINUS TECHNOLOGY INC.), 0x0101, 0x40400000 / 2
USB Device: HASP4 USB 1.33, 0x0529 (Aladdin Knowledge Systems), 0x0001, 0x00200000 / 3
USB Device: SII Smart Label Printer 200, 0x0619 (Seiko Instruments Inc.), 0x0104, 0x00100000 / 2
USB Device: HASP4 USB 1.33, 0x0529 (Aladdin Knowledge Systems), 0x0001, 0xff100000 / 2
USB Device: HASP HL 3.25, 0x0529 (Aladdin Knowledge Systems), 0x0001, 0xfe200000 / 2
USB Device: Natural® Ergonomic Keyboard 4000, 0x045e (Microsoft Corporation), 0x00db, 0x1a200000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x5a100000 / 2
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0x5a110000 / 3
USB Device: USB Receiver, 0x046d (Logitech Inc.), 0xc52f, 0x1d100000 / 2
FireWire Device: built-in_hub, Up to 800 Mb/sec
FireWire Device: unknown_device, 0xD016, Up to 200 Mb/sec

Only OS bugs, driver bugs, or hardware problems can cause kernel panics.
Yes, that is normally the case. I brought this up here because while working in PS is the only time this happens. I know it doesn't make sense, but there it is.
Not sure why the crash report stated 10.8.0. It's incorrect on two counts. For one, I'm working in Snow Leopard, 10.6.8. I do have Mountain Lion installed on a separate drive for testing, but that already is at 10.8.2. Regardless, it's not the OS I was even in, so I don't know why it reported 10.8.0 as the kernel.
Anyway, I noticed (after posting this of course) that there was a 13.0.1 update for PS CS6. I applied that and we'll see how it goes from there as the update is noted as fixing a number of crashing problems.

Using 2 memory modules causes kernel panic

In early 2009 I upgraded my memory from 512 to 2 GB, 2 modules of 1GB each. This past January (just shy of 2 years later) I got a kernel panic. I tested running with a single module, and one module caused panic, the other was fine. Both slots function with the good module. So I got two new matched replacement chips from OWC, put them in and got kernel panics during the boot process. Yesterday I spent testing memory configurations and found this:
1. chip 1 alone runs fine and passes all Rember memory tests in slot 1.
2. chip 2 alone runs fine in slot 1 and 2, passes all memory tests in slot 2.
3. chips 1 and 2 together, in either slot, cause kernel panics before the OS is loaded.
Has anyone seen this problem? Will it go away if I use top of the line (Apple) memory chips?
When the kernel panics started back in January, an AppleCare advanced advisor said he had the same problem and he had to remove one module to stop the kernel panics. Running on 1GB doesn't work for me because I tend to max out the memory and programs like Mail, Safari, Photoshop, etc. become unreponsive all together.
thanks -

I have spent more time on the phone with OWC about this than I care to remember. Their latest request is that I use an eraser to clean the metal contacts on the chips; if that fails, I get to send the chips back. Whether I get a refund or yet another set of replacement chips, I don't know. They are not experts on Apple machines, that is clear.

External Drive causes Kernel Panic

I've been struggling with Time Machine on a Seagate external 1TB drive. Backups have failed consistently since I upgraded to Lion, taking a really long time or generating error messages and failing.
I read Pondini ( http://pondini.org/TM/D2.html ), and tried installing http://support.apple.com/kb/DL1599, which apparently worked, according to the log:
Starting standard backup
Backing up to: /Volumes/BIG_NEW/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Waiting for index to be ready (101)
Deep event scan at path:/ reason:must scan subdirs|new event db|
Finished scan
17.49 GB required (including padding), 438.01 GB available
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 "The file “SaveSMPWizard-SoloStaff.nib” couldn’t be opened." UserInfo=0x7f9931b65480 {NSURL=/Volumes/BIG_NEW/Backups.backupdb/Jon’s MacBook/2012-10-23-005106/Macintosh HD/Applications/Finale 2011.app/Contents/Resources/English.lproj/SaveSMPWizard-SoloStaff.nib, NSFilePath=/Volumes/BIG_NEW/Backups.backupdb/Jon’s MacBook/2012-10-23-005106/Macintosh HD/Applications/Finale 2011.app/Contents/Resources/English.lproj/SaveSMPWizard-SoloStaff.nib, NSUnderlyingError=0x7f9931b6b8b0 "The operation couldn’t be completed. Resource busy"}
Copied 236946 files (6.4 GB) from volume Macintosh HD.
1.41 GB required (including padding), 431.36 GB available
Copied 2013 files (17.7 MB) from volume Macintosh HD.
Starting post-backup thinning
Deleted /Volumes/BIG_NEW/Backups.backupdb/Jon’s MacBook/2012-09-29-013720 (296.8 MB)
Deleted /Volumes/BIG_NEW/Backups.backupdb/Jon’s MacBook/2012-09-28-013251 (55.1 MB)
Deleted /Volumes/BIG_NEW/Backups.backupdb/Jon’s MacBook/2012-10-23-002733 (3.8 MB)
Deleted /Volumes/BIG_NEW/Backups.backupdb/Jon’s MacBook/2012-10-22-225513 (4.1 MB)
Deleted /Volumes/BIG_NEW/Backups.backupdb/Jon’s MacBook/2012-10-22-215519 (5.7 MB)
Post-back up thinning complete: 5 expired backups removed
Backup completed successfully.
OK. Then, I woke up to a frozen machine with a kernel panic showing, and another kernel panic on restart. The most recent backup message was:
Starting standard backup
Backing up to: /Volumes/BIG_NEW/Backups.backupdb
1.33 GB required (including padding), 434.63 GB available
Waiting for index to be ready (101)
Waiting for index to be ready (100)
Copied 2506 files (19.4 MB) from volume Macintosh HD.
1.33 GB required (including padding), 434.60 GB available
The panic log shows that it freaks trying to mount the hfs volume -
Wed Dec 26 11:53:41 2012
panic(cpu 1 caller 0xffffff80002c4794): Kernel trap at 0xffffff800050b6c2, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000001de1b000, CR4: 0x0000000000000660
RAX: 0x0000000000000000, RBX: 0x0000000000000000, RCX: 0x0000000000000000, RDX: 0xffffff8078f02b6e
RSP: 0xffffff8078f02b50, RBP: 0xffffff8078f02c10, RSI: 0xffffff8078f02a18, RDI: 0xffffff800ade4460
R8: 0xffffff8078f02b90, R9: 0xffffff8078f02bd0, R10: 0x0000000000000000, R11: 0xffffff800063dc04
R12: 0x0000000000000001, R13: 0xffffff80198ec408, R14: 0xffffff8019fc7a80, R15: 0xffffff800c376808
RFL: 0x0000000000010297, RIP: 0xffffff800050b6c2, CS: 0x0000000000000008, SS: 0x0000000000000010
CR2: 0x0000000000000000, Error code: 0x0000000000000000, Faulting CPU: 0x1
Backtrace (CPU 1), Frame : Return Address
0xffffff8078f02800 : 0xffffff8000220792
0xffffff8078f02880 : 0xffffff80002c4794
0xffffff8078f02a30 : 0xffffff80002da55d
0xffffff8078f02a50 : 0xffffff800050b6c2
0xffffff8078f02c10 : 0xffffff8000506608
0xffffff8078f02c50 : 0xffffff80004fc01e
0xffffff8078f03090 : 0xffffff80004fdcf3
0xffffff8078f03610 : 0xffffff80004f77a1
0xffffff8078f036f0 : 0xffffff80004f998c
0xffffff8078f037b0 : 0xffffff800030fbbd
0xffffff8078f03af0 : 0xffffff8000310860
0xffffff8078f03f10 : 0xffffff80003108e6
0xffffff8078f03f50 : 0xffffff80005ce4cb
0xffffff8078f03fb0 : 0xffffff80002daea3
BSD process name corresponding to current thread: mount_hfs
Mac OS version:
11G63
Kernel version:
Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64
Kernel UUID: FF3BB088-60A4-349C-92EA-CA649C698CE5
System model name: MacBook6,1 (Mac-F22C8AC8)
System uptime in nanoseconds: 2444502654101
last loaded kext at 2442664671789: com.apple.iokit.IOSCSIBlockCommandsDevice          3.2.1 (addr 0xffffff7f80825000, size 86016)
last unloaded kext at 147764894033: com.apple.driver.AppleUSBTCKeyEventDriver          227.6 (addr 0xffffff7f8228b000, size 8192)
loaded kexts:
org.pqrs.driver.KeyRemap4MacBook          7.5.32
jp.co.roland.RDUSB0014Dev          1.0.0
com.Cycling74.driver.Soundflower          1.5.1
com.apple.driver.AppleUSBCDC          4.1.22
com.apple.filesystems.smbfs          1.7.2
com.apple.driver.AppleBluetoothMultitouch          70.12
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.driver.AudioAUUC          1.59
com.apple.driver.AppleMikeyHIDDriver          122
com.apple.driver.AppleHDA          2.2.5a5
com.apple.driver.AppleMikeyDriver          2.2.5a5
com.apple.driver.AGPM          100.12.75
com.apple.driver.AppleUpstreamUserClient          3.5.9
com.apple.GeForce          7.3.2
com.apple.driver.SMCMotionSensor          3.0.2d6
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.iokit.IOBluetoothSerialManager          4.0.8f17
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.AudioIPCDriver          1.2.3
com.apple.driver.ApplePolicyControl          3.1.33
com.apple.driver.AppleLPC          1.6.0
com.apple.driver.ACPI_SMC_PlatformPlugin          5.0.0d8
com.apple.driver.AppleBacklight          170.2.2
com.apple.driver.AppleMCCSControl          1.0.33
com.apple.filesystems.autofs          3.0
com.apple.driver.AppleUSBTCButtons          227.6
com.apple.driver.BroadcomUSBBluetoothHCIController          4.0.8f17
com.apple.driver.AppleUSBTCKeyboard          227.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          33
com.apple.iokit.SCSITaskUserClient          3.2.1
com.apple.iokit.IOAHCISerialATAPI          2.0.3
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.1.0
com.apple.driver.AppleAHCIPort          2.3.1
com.apple.driver.AirPort.Brcm4331          561.7.22
com.apple.nvenet          2.0.17
com.apple.driver.AppleUSBHub          5.1.0
com.apple.driver.AppleSmartBatteryManager          161.0.0
com.apple.driver.AppleUSBEHCI          5.1.0
com.apple.driver.AppleUSBOHCI          5.1.0
com.apple.driver.AppleEFINVRAM          1.6.1
com.apple.driver.AppleRTC          1.5
com.apple.driver.AppleHPET          1.7
com.apple.driver.AppleACPIButtons          1.5
com.apple.driver.AppleSMBIOS          1.9
com.apple.driver.AppleACPIEC          1.5
com.apple.driver.AppleAPIC          1.6
com.apple.driver.AppleIntelCPUPowerManagementClient          195.0.0
com.apple.nke.applicationfirewall          3.2.30
com.apple.security.quarantine          1.4
com.apple.security.TMSafetyNet          8
com.apple.driver.AppleIntelCPUPowerManagement          195.0.0
com.apple.iokit.IOSCSIBlockCommandsDevice          3.2.1
com.apple.iokit.IOUSBMassStorageClass          3.0.3
com.apple.driver.AppleMultitouchDriver          231.4
com.apple.driver.IOBluetoothHIDDriver          4.0.8f17
com.apple.driver.DspFuncLib          2.2.5a5
com.apple.nvidia.nv50hal          7.3.2
com.apple.NVDAResman          7.3.2
com.apple.iokit.IOSurface          80.0.2
com.apple.iokit.IOSerialFamily          10.0.5
com.apple.iokit.IOAudioFamily          1.8.6fc18
com.apple.kext.OSvKernDSPLib          1.3
com.apple.driver.AppleHDAController          2.2.5a5
com.apple.iokit.IOHDAFamily          2.2.5a5
com.apple.driver.AppleSMC          3.1.3d10
com.apple.driver.IOPlatformPluginLegacy          5.0.0d8
com.apple.driver.IOPlatformPluginFamily          5.1.1d6
com.apple.driver.AppleSMBusPCI          1.0.10d0
com.apple.driver.AppleGraphicsControl          3.1.33
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.iokit.IONDRVSupport          2.3.4
com.apple.driver.AppleSMBusController          1.0.10d0
com.apple.iokit.IOGraphicsFamily          2.3.4
com.apple.kext.triggers          1.0
com.apple.driver.AppleUSBHIDKeyboard          160.7
com.apple.driver.AppleHIDKeyboard          160.7
com.apple.driver.AppleUSBBluetoothHCIController          4.0.8f17
com.apple.iokit.IOBluetoothFamily          4.0.8f17
com.apple.driver.AppleUSBMultitouch          230.5
com.apple.iokit.IOUSBHIDDriver          5.0.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.2.1
com.apple.iokit.IOBDStorageFamily          1.7
com.apple.iokit.IODVDStorageFamily          1.7.1
com.apple.iokit.IOCDStorageFamily          1.7.1
com.apple.driver.AppleUSBMergeNub          5.1.0
com.apple.driver.AppleUSBComposite          5.0.0
com.apple.iokit.IOSCSIArchitectureModelFamily          3.2.1
com.apple.iokit.IOAHCIFamily          2.0.8
com.apple.iokit.IO80211Family          420.3
com.apple.iokit.IONetworkingFamily          2.1
com.apple.iokit.IOUSBUserClient          5.0.0
com.apple.iokit.IOUSBFamily          5.1.0
com.apple.driver.NVSMU          2.2.9
com.apple.driver.AppleEFIRuntime          1.6.1
com.apple.iokit.IOHIDFamily          1.7.1
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          177.8
com.apple.kext.AppleMatch          1.0.0d1
com.apple.driver.DiskImages          331.7
com.apple.iokit.IOStorageFamily          1.7.2
com.apple.driver.AppleKeyStore          28.18
com.apple.driver.AppleACPIPlatform          1.5
com.apple.iokit.IOPCIFamily          2.7
com.apple.iokit.IOACPIFamily          1.4
Some additional background:
I disabled spotlight on the external, except for the backups.
I had installed MicroMat's CheckMate. I'm wondering if there was some sort of collision between Checkmate and Time Machine that could have trashed the external drive.
This is a drag, because my iTunes and iPhoto libraries are also on that same external drive. I would like to find out how to recover the external drive... is there way to plug it in without it mounting in order to repair it with Disk Utility, for example?

Most likely, one of these are the culprits.
org.pqrs.driver.KeyRemap4MacBook          7.5.32
jp.co.roland.RDUSB0014Dev          1.0.0
com.Cycling74.driver.Soundflower          1.5.1.
Boot into safe mode and see if the problem persists. If so, Zap the PRAM and Reset the SMC, then try again. If not, then reboot normally and see
About kernel panics,
Technical Note TN2063: Understanding and Debugging Kernel Panics,
Mac OS X Kernel Panic FAQ,
Resolving Kernel Panics, and
Tutorial: Avoiding and eliminating Kernel panics for more details.

Upgrade to osx 10.6.8 causes kernel panic on reboot

Hi friends,
Am reposting this as I have more infomration now.
Problem: Having installed the 10.6.8 upgrade, (currently running osx 10.6 on a 2009 iMac) then on reboot the machine undergoes a kernel panic.
General Observations; The machien has given ZERO problems since I bought it. The only peripherals are an USB apple keypad and an apple USB Mouse connected to the keyboards ancillary USB port.
Diagnostic actions to date;
1. Completely erased disk, created new partition, verified disk and also verified disk permissions (all good).
2. Re-installed Snow Leopard.
3. Cleared PRAM using the option-command-P-R (waited for 4 Apple Chimes).
Result: Nada !
System still crashes.
Geranal Notes: As I live in Malaysia, Lion DVD installation kit is still nto available here. So I have to upgrade to Lion via the net. However, I cannot upgrade to Lion unless I first complete ythe other 10.6 related upgrades (this is my undertanding).
Question: Anyone out there with any ideas ? What about the folks over at Apple. This is fairly basic stuff. An Apple mandated Upgrade renders an Apple Hardware platform inoperable.

A: If your machine had a completely erased hard drive and a fresh install of OS x 10.6 (no other software installed) and you got kernel panic's then it's the 10.6 disk, you'll need to clean it or get a new one from Apple.
If the new disk also produces the same problem, then it's got to be the hardware.
B: If your machine is like A, but the kernel panics started when you updated to 10.6.8 (no other software installed) then it's a bad update. Reinstall with the 10.6.8 Combo Update instead. Also c boot off the 10.6 disk and Repair Disk, the 10.6.8 update did something to the drive that it needs repair.
C: If your machine was fine on 10.6, installed third party software worked, then kernel panics started after the 10.6.8 update. Then it's compatability issues with kext files and 10.6.8 changes.
The 10.6.8 update borked a lot of third party kernel extension files (kext) installed in OS X.
What you can do is this:
Hold the Shift key down to boot into Safe Mode, this will disable the kext files from loading, backup your files off the machine (not TimeMachine) and disconnect all drives.
Go around and update all your third party software so it's compatible with 10.6.8,
If you need a clue, look in your System/Library/Extensions and usually the names of the companies are on the kext file names. Sometimes copy protected software will use another companies copy protection system, so it will be under another name.
Funny thing about kext files, they are not all in the System/Library/Extensions folder to load upon boot, they can be located anywhere the program decides and loaded when the program loads.
If you have programs that are auto-launching at log-in then naturally so does it's kext files.
10.6 will run all your present software and drivers for hardware just fine, 10.7 will not and is NOT advised for older hardware. Early 2011 or later Lion is just fine, but you'll likely have to buy all new software to work with it.
Despite 2GB of RAM being Lion's minimum, 4GB is advised. Also you will need a 64 bit Intel Mac, not a 32 bit Intel Mac (no Lion for Core Duo's)
Tested, Lion is a hair slower than Snow Leopard
Check this site to make sure your third party programs are updated for Lion, not many are yet.
Some are undergoing a rewrite because Apple introduced a MacAppStore and likely told all the developers their programs will eventually have to comply with the restrictions placed there to run on Apple hardware, this means Apple is likely going to close up and we can't install software of our choice just like it is on iPads and iPhones.
http://roaringapps.com/apps:table

RAID mirror with software utility caused kernel panic every time

Using disc utility to make a mirror of 2 drives, click create and i get kernel panic and have to power off machine. if i try to start the machine with either of the two disks in it (together or individually) i get same kernel panic and have to power off.
The disks are in an external storage array (sonnet d500). I have a second storage array with raided disks in and i have raided disk inside the mac too. these all work fine..
originally 2 weeks ago i had the 2 disks working in a group of 4 disks set as a mirror of 2 striped disks. One disk in this setup failed and with this config you can never 'recover'or rebuild it - you get a degraded mirror and you can backup the data, but you must completely rebuild the raid again as the mirror of stripes never lets you add a new disk in again.period. not good.
I replaced the failed disk and rebuilt the mirror of stripes. this lasted a day until a second disk failed (all 4 were bought at same time so i was kind of expecting that to happen once one failed).
i replaced the second faulty hdd and thought about my disk usage and decided i would not make another mirror of stripes and i would make 2 mirrors instead for safe-ish storage and then transfer data to a striped raid set for editing from instead of direct from the mirror of stripes volume.
i tried to delete the raid but got a kernel panic
if i started the machine with any of the 4 disks i would get a kernel panic.
i moved the disks one by one into an older G5 running Tiger and managed to erase the raid info on 2 of them. The two new ones had some strange raid info and the Tiger machien thought there was an extra disk in the machine and would not erase or partition or allow me to destroy the raid whatever i tried.
I will be moving these now into an old XP PC to try to erase the boot records etc and erase them to be able to use them again in either mac pro or G5. painful..
so.. i ended up with 2 erased drives and have 2 new drives with dodgy raid info that causes kernel panics on the leopard machine and wont go in the Tiger machine.
The two erased drives are what ive now been trying to use in the mac pro to create a mirror - this now caused kernel panics when creating the mirror to start with and when installed in the machine at all. so i will be erasing them again in the tiger machine soon (its busy erasing with zeros another new disk that i added to the Tiger machine 2 weeks ago which seems to have some fault when raided!!! but thats another story).
so.. is anyone else having problems with creating basic mirror in 10.5.4 or is it just me??
i have a sonnet tempo e4p card with 2 external sata disk enclosures, latest firmware for the e4p card. all other previously existing raid volumes are working fine. i have one set of 2 striped disks, one set of 3 striped disks and one set of 2 stripes which are mirrored - all happy and working fine. but i cant make a new mirror of 2 disks...
I phoned Apple support and they said all raid info was kept on the disk itself and nothing on the actual machine and suggested i take the machine to an apple care centre for some tlc (although its disk i am having a problem with). since all my other disk arrays work fine i don't really want to rebuild the whole machine from scratch if i can avoid it.
Any suggestions of what i can try ??

well it turns out the new disk i bought just werent any good. my g5 powermac raid mirror issue was related to one new disk with lots of bad blocks (speed tools showed that up) so i have learnt my lesson on cheap non raid disks for raid..
am waiting on a couple of new ultrastar enterprise disks to tuen up so i can go back to the macpro and try to add a mirror again.
i am still stuck wih several new disks that i cannot format now in the macpro on leopard or on the g5 powermac with tiger.
ive tried softraid and that cant do it, speedtools pcformat util cant do it, disk utility crashes when i try to eras them and diskutil from termianl starts then doenst get anywhere and my pc sata card doesnt work so my last resort pc option still doesnt help me clear the partition map on these drives - ones that diskutility on leopard made for me - and drives which still cause kernel panics on the macpro if i put them in it..
here is what diskutil says on my g5:
/dev/disk0
#: type name size identifier
0: GUIDpartitionscheme *465.8 GB disk0
1: EFI 200.0 MB disk0s1
2: Apple_RAID 465.4 GB disk0s2
3: Apple_Boot 128.0 MB disk0s3
/dev/disk1
#: type name size identifier
0: Applepartitionscheme *233.8 GB disk1
1: Applepartitionmap 31.5 KB disk1s1
2: Apple_HFS Macintosh HD 233.6 GB disk1s3
/dev/disk2
#: type name size identifier
0: *465.4 GB disk2
/dev/disk3
#: type name size identifier
0: Applepartitionscheme *931.5 GB disk3
1: Applepartitionmap 31.5 KB disk3s1
2: Apple_HFS backup1T 931.4 GB disk3s3
/dev/disk4
#: type name size identifier
0: Applepartitionscheme *931.5 GB disk4
1: Applepartitionmap 31.5 KB disk4s1
2: Apple_HFS tempi 931.4 GB disk4s3
disk0 is the one with the bad partition info.
it thinks it has a double raid as the console shows on startup:
(both store45 and cache it thinks are on this disk - cache was my old mirror of stripes set on other machine, store45 was new name for my mirror, so seems like it hadnt deleted the original raid partition info before making new info which now kernel panics)
Jul 18 18:48:05 localhost kernel[0]: AppleRAID::degradeSet - starting the set "STORE45" (B9C48619-6B2C-4547-A01E-4864754EA7E2).
Jul 18 18:48:35 localhost kernel[0]: AppleRAID::degradeSet - starting the set "CACHE" (64F914A5-5556-4A44-AEE2-DC437868766B).
Jul 18 18:48:35 localhost kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002c2 detected for set "STORE45" (C0E139A4-2A6D-49C6-8F77-202AF7F9285D), member 50207BE5-E487-410E-8E8E-C4C4DCD2687B, set byte offset = 999527018496.
Jul 18 18:48:35 localhost kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002c2 detected for set "CACHE" (64F914A5-5556-4A44-AEE2-DC437868766B), member C0E139A4-2A6D-49C6-8F77-202AF7F9285D, set byte offset = 999527018496.
so currently i have 2 new 500gb disks which cant be partitioned back to anything at all on either machine. looks like i will have to buy a new pc to reformat them..
any suggestions of how to clear the partition map info and get them back to freespace ??

Scanner Causing Kernel Panics

I have an old Agfa SnapScan 1212u USB scanner and up until today it has worked fine. Then suddenly it started causing Kernal Panics. It happens about 30% of the time. It scans the first 10% then throws up the Kernel Panic message and I'm forced to restart. I have run the Disk Repair Utility, repaired permissions, reinstalled the Agfa Scanwise driver, deleted all scanner related preferences and disconnected all other USB devices but nothing seems to work. The only software update I've done recently is the August and Java Security updates. Could either of these things be the problem? This is the first time I've had Kernel Panics on my Mac Mini. I doubt it's caused by the ram. It has worked flawlessly since I put in the 1GB module in July.
Does anyone have any ideas?
Cheers
djon

Well, I downloaded Vuescan and set it up but now I have another problem. Vuescan constantly crashes. Sometimes it crashes when I'm changing settings and sometimes is crashes after a scan. I set the memory settings very high so it shouldn't be a memory issue. I've tried just about everything to get this scanner working with Vuescan. I even installed a fresh copy of Panther on my Firewire drive but it only reduced the crashes not eliminate them. I'd like to get Vuescan working because it seems to make better scans than Scanwise did. At least it doesn't cause Kernel Panics. Does anyone have any idea what's going on? I'm beginning to think that it might be a hardware problem with the scanner.
djon

Battery Update Causing Kernel Panics?

It seems that ever since I installed the Battery Update it's been causing Kernel Panics on my MBP. Three since yesterday in fact. Has anyone else been experiencing this?
MacBook Pro 1.83 GHz Mac OS X (10.4.9) 1 GB RAM, 80 GB HDD, ATI Radeon X1600

Hmm I have seen multiple posts on the computer not booting the OS (gets to the grey apple with spinning gear screen) but so far I think you are the first I have seen reporting kernel panics.
Can you boot to the install cd? I'd try running the disk utility from the install disk and verify/repair permissions and verify the disk as well. (repair disk if verification fails)
Here is an article that may help ya:
Resolve startup issues and perform disk maintenance with Disk Utility and fsck
http://docs.info.apple.com/article.html?artnum=106214

Readynas duo mounted over ethernet causes kernel panics

I've found out what is causing kernel panics on my machines, but i'm not sure how to resolve it. I have a g4 laptop and a new mac mini, both mount the readynas via mount_afp using a LoginHook. When the laptop or the mini go to sleep, the ethernet connection is powered off and at some point the readynas goes to sleep as well. So, when the laptop/mini wake from sleep, they have trouble re-establishing the mount to the readynas (as it needs time to spin it's drives up) and then the laptop/mini kernel panic...shouldn't this really be just a lost connection message, rather than a full fledged panic!

This is where we have a difference of opinion...If i can mount an external box over ethernet/firewire/usb and it causes the machine to kernel panic, then the software is not robust enough to handle the exception cases. Running 10.4.x for years with the same external hardware never yielded such results.

IMac 27" with Wireless G network causes Kernel Panics

I bought a 27" iMac Jan 8th 2010
At home i'm running a Wireless G network through a linksys WRT54G V7.0 router
From day one i was running into Kermnel Panics several times a day
When i was provided a new machine the same thing happened
The machine has been away for repair for 2 weeks and nothing was found.
As soon as the machine was back home the Kernel Panics started again
A clean install has ben done, and when setting up the network for the build in airport, the machine died again in a kernel panic
After further discussions with apple repair they stated the the Kernel Panics were caused by the Wireless G network, and was advised to get myself a wireless N router
I got myself a wirelees N router (apple airport extreme), and no more Kernel Panics were seen
Now the questions are :
Did anybody else ran into this issue ?
Is somebody have this same issue and also have a linksys router ?
Would anybody be able to explain why my Linksys WRT54g V7.0 router running Wireless G cuase the Kernel Panics on my machine ?
Ok quite a story, but hope to get some constructive answers.
thnx
Paul

I took home a 27" i5 iMac on 7th of Mar 2010 and immediately two days later i had my first kernel panic.
When i called Apple Support the next day i was led through a barrage of file deleting and the usual Disk Utilities Repair Disk actions. Two days later another kernel panic happened but this time the computer display remained blank. I brought it back to the department store where i purchased it and, they agreed to replace my unit (still within the store's seven days warranty).
Five days later my new unit arrives and the moment i turned on the wireless connectivity i had another kernel panic. I was ****** - NOT looking forward to carrying the 38lb computer back to the store again. Called Apple again and the guy had me reinstall OSX. One day later kernel panics still there.
Then i experimented by not turning on the wireless internet, for two days no kernel panics. The moment i did, a kernel panic would occurs, i got suspicious. That's when i stumbled on luupski's post (I'm real glad i found it). I also was using a linksys WRT54G router and getting the same kernel panics as everyone on this thread. Now that the root cause has been identified, i decided to save my SGD258 (apple airport express) and instead invested SGD18 in a Cat5e 20m ethernet cable. My mac now works perfectly apart from the lack of wireless network, which i can grudgingly bear.
Real glad to see genuine and useful posts in a forum like this. I will be giving a heads up to the Apple support guys, they seem to be totally oblivious about this issue. Its weird since the WRT54G seems to be quite popular here in Singapore.
Thanks,
simon

WD Hard drive causing Kernel Panics

I recently came home to find one of my hard drives missing from the desktop, I restarted and the drive reappeared. Ran Disk Utility on the drive and it's reported as fine, also S.M.A.R.T. says its fine. But within 2 to 6 minutes the computer will kernel panic (sometimes only getting a 3rd of the way down the screen), panic.log is never updated either so I can't post that info. I've reset PRAM to no avail. When I restart the drive sometimes doesn't appear at all or takes some time to appear.
The only thing that stops the kernel panic is to remove the offending 500GB Western Digital sata in bay 3. I need to to get the information off of that drive but can't keep the computer on long enough before a KP happens again. Disk Warrior and Drive Genius report no errors though running a hardware test in Disk Warrior immediately freezes the machine.
Occasionally the drive will appear and occasionally it won't show up anywhere - not even Disk Utility. I must have some sort of HD controller issue with the drive.
Does anyone know how I could get the info from the drive - maybe put it into a USB caddy? Anyone else experienced anything like this? It certainly doesn't seem very common.

Thanks, The hatter, I'll get a enclosure tomorrow, I need the data off the drive more than anything else. Perfectly happy to trash said WD drive afterwards, I've come close already
I only get k/ps when drive is in bay. Drive occasionally won't show up with Disk Utility and sometimes will, which strikes me that it's a serious hardware problem. Root mode boot and safe mode change nothing - sometimes I'll get a Kernel panic while the apple logo is still showing. Take drive out and system is perfectly fine.
Have started to get data off but get k/p after about 5 mins so will take a while. Some is backed up (it's my iTunes library but I backed it up 4 months ago), but could do with around 250Gb of raw firewire movie files dumped from (now blanked) tape that I've yet to process. The data seems fine, just something is causing the k/p. Reboot occasionally shows drive, occasionally doesn't in Disk Utility...
Also tried MacDrive on Bootcamp partition - but XP crashes pretty quickly with a freeze. Will check out WDs Windows/Dos utitlity now you've mentioned it, it is a WD drive after all. So not much better under XP.
Have done extensive RAM tests just to make sure it wasn't that, including reseating and PRAM and SMC reset, but things are fine without drive in bay (and I've another 3 drives in bays working fine including my main Boot drive).
I'd let Disk Warrior do it's work if I didn't think I'd get a kernel panic halfway through... which worries me.. I'd tried booting from Disk Warrior's bootdisk CD and got a kernel panic during boot.
I've now been using this mac for 5 hours now without drive in bay so it's not the mac itself.
Is there anyway of deleting possibly corrupt journal (spotlight does seems to constantly re-index on startup - but only when said drive is in bay) maybe with Terminal?
I'm wary of repartioning as I'll surely get a k/p during the process...

Rt3062 causing kernel panics

Hi all,
I've got an rt3062 chipset wireless card and it's been causing kernel panics ever since the upgrade to linux-3.0.
I was using the driver and firmware supplied by ralink and compiling it as the rt3562sta driver and it used to work great but it doesnt seem to support anything higher than kernel 2.6.39.
I'm not exactly sure which error logs to post, so...
Anybody else having this issue? and maybe find a workaround?
Thanks

I am using the same combination, successfully, with kernel 3.0.7-1. I do not recall having to do anything special to get it to work.
06:00.0 Network controller: Ralink corp. Device 3062
Subsystem: Ralink corp. Device 3062
Flags: bus master, slow devsel, latency 32, IRQ 19
Memory at fbdf0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Kernel driver in use: rt2860
Kernel modules: rt3562sta, rt2800pci
Tim

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

Upgraded and now get Kernel Panic

Upgraded tonight and immediately got Kernel Panic's and now cannot boot from disk or in safe mode. Please please help. This is why I didn't want to upgrade.

I've been running SL for over a year on my 24" iMac. SL isn't the issue; most likely, bad RAM.
See
What is a kernel panic,
Technical Note TN2063: Understanding and Debugging Kernel Panics,
Mac OS X Kernel Panic FAQ,
Resolving Kernel Panics, and
Tutorial: Avoiding and eliminating Kernel panics for more details.

Lion NetBoot and NetInstall causing kernel panic

Similar Messages

Maybe you are looking for