10.5.6 and Disk Warrior

After upgrading my Core 2 Duo MacBook to 10.5.6 with Combo Updater, I have had kernel panic when I try to run Disk Warrior (version 4.1.1) after rebooting from external firewire hard drive (with OS X 10.5.5 on external drive). Disk Warrior crashes during step 5 of rebuilding directory file. This is reproducible, occuring three times in a row.
When I restart the MacBook on internal hard drive, the following error message about kernel panic is generated:
Mon Dec 15 21:03:54 2008
panic(cpu 1 caller 0x001A8CEC): Kernel trap at 0x0019807c, type 14=page fault, registers:
CR0: 0x80010033, CR2: 0x23c23000, CR3: 0x01040000, CR4: 0x00000660
EAX: 0x23c19000, EBX: 0x00003ff8, ECX: 0x00000006, EDX: 0x00003ff8
CR2: 0x23c23000, EBP: 0x3de5bc68, ESI: 0x23c23000, EDI: 0x23c1cfe0
EFL: 0x00010212, EIP: 0x0019807c, CS: 0x00000008, DS: 0x00000010
Error code: 0x00000000
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x3de5ba58 : 0x12b0fa (0x459234 0x3de5ba8c 0x133243 0x0)
0x3de5baa8 : 0x1a8cec (0x4627a0 0x19807c 0xe 0x461f50)
0x3de5bb88 : 0x19eed5 (0x3de5bba0 0x3de5bbec 0x3de5bc68 0x19807c)
0x3de5bb98 : 0x19807c (0xe 0x1950048 0x10 0x34460010)
0x3de5bc68 : 0x3edb50 (0x3d567a0 0x23c1f020 0x3ff8 0x3d63340)
0x3de5bc88 : 0x34456aaa (0x23c1f020 0x3ff8 0x195d600 0x2)
0x3de5bcf8 : 0x34456f39 (0x3fb3d00 0x3d63340 0x0 0x34463000)
0x3de5bd28 : 0x43abd3 (0x3fb3d00 0x3d63340 0x5566 0x11e42c)
0x3de5bd78 : 0x18a4f7 (0x3fb3d00 0x4054f48 0x5566 0x4184bc0)
0x3de5bdb8 : 0x12d17e (0x44fba90 0x4184b9c 0x3de5bdf8 0x11ee14)
0x3de5bdf8 : 0x126257 (0x44fba00 0x3c679e0 0x16a64b0 0x0)
0x3de5bf08 : 0x1974c2 (0x3de5bf44 0x0 0x0 0x0)
0x3de5bfc8 : 0x19f4a3 (0x440d2a0 0x0 0x1a20b5 0x4516128)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffe2a8
Kernel loadable modules in backtrace (with dependencies):
com.alsoft.Preview(4.1.1)@0x34455000->0x3445cfff
dependency: com.apple.iokit.IOStorageFamily(1.5.2)@0x824000
BSD process name corresponding to current thread: DiskWarrior
Mac OS version:
9F33
Kernel version:
Darwin Kernel Version 9.5.0: Wed Sep 3 11:29:43 PDT 2008; root:xnu-1228.7.58~1/RELEASE_I386
System model name: MacBook2,1 (Mac-F4208CA9)
Model: MacBook2,1, BootROM MB21.00A5.B07, 2 processors, Intel Core 2 Duo, 2 GHz, 2 GB
Graphics: kHW_IntelGMA950Item, GMA 950, spdisplays_builtin, spdisplaysintegratedvram
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, 1.4.8.0
Bluetooth: Version 2.1.3f8, 2 service, 0 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: TOSHIBA MK8034GSX, 74.53 GB
Parallel ATA Device: MATSHITADVD-R UJ-857D
USB Device: Built-in iSight, (null) mA
USB Device: hub_device, (null) mA
USB Device: Generic USB Audio Device, (null) mA
USB Device: Back-UPS ES 550 FW:840.B2.D USB FW:B2, (null) mA
USB Device: IR Receiver, (null) mA
USB Device: Apple Internal Keyboard / Trackpad, (null) mA
USB Device: Bluetooth USB Host Controller, (null) mA
FireWire Device: elephantdrive, Elephant Storage, 400mbit_speed

Problem solved (I hope). For reasons (present since 10.5.0 and not fixed in 10.5.6), Leopard has a problem sometimes with Spotlight (and other programs) taking over the CPU (see MacOsxHints 10.5: One fix for a runaway syslogd process <http://www.macosxhints.com/article.php?story=20071030233438149>). This creates problems with restarting and shutting down as well as difficulty doing much of anything.
The ATSserver and Syslogd processes were consuming 60-110% of the CPU at times, according to Activity Monitor. This has been a recurrent problem with Leopard and obviously still persists with 10.5.6.
I re-installed Leopard from the Leopard DVD and upgraded to 10.5.5. I will wait until the dust settles with all the many complaints about 10.5.6 before upgrading. Meanwhile, Disk Warrior works fine with the reinstalled hard drive with Spotlight turned off.

Similar Messages

  • TM and  Disk Warrior

    The past few months I have had a problem with Time Machine getting corrupted often, but not always, when I do a restart. T M resides on a partition on an external disk. After a restart it either doesn't show up or is not mounted as shown in Disk Utility. The repair permissions and repair disk options are grayed out. Sometimes I can do a Verify Disk, but it always fails. The other partition on the disk is usually fine. Often if I run a repair permissions on the main Leopard partition on the iMac's internal drive, somewhere during the process a message appears that the T M partition is not repairable but is being made available with a read only functionality.
    Disk Warrior sees the partition and will begin the repair process. After a short time a message appears in the DW window stating "speed reduced by lack of memory" The process hangs on step 5, locating directory data. I found one time that if I just let it go in background for up to 2 days, the process will finally complete, and continue on to repair the disk. T M then works fine until the next time I have to restart the iMac again. The latest repair report from DW is as follows.
    • Errors, if any, in the directory structure such as tree depth, header node, map nodes, node size, node counts, node
    links, indexes and more have been repaired.
    • 2 iNode(s) had a link count that was repaired.
    • 6 link files no longer point(s) to an original file and therefore cannot be repaired.
    • 9 files had an incorrect key that was repaired.
    • 1 folder had a directory entry with an incorrect flag that was repaired.
    • 10 folders had an incorrect item count that was repaired.
    • 29 folders had a directory entry with an incorrect custom icon flag that was repaired.
    • Incorrect values in the Volume Information were repaired.
    • Critical values in the Volume Information were incorrect and were repaired.
    • There is no blessed System Folder, you will be asked to choose a System Folder after replacing the directory.
    • 6 files could not be found.
    • 9 folders could not be found.
    • 11 folders will have more items.
    • 1 folder will have fewer items.
    • 10 files will now become accessible.
    • 4 folders will now become accessible.
    • 2 files had a Name that changed.
    Disk Information:
    Files: 2,963,472
    Folders: 427,119
    Free Space: 773.69 MB
    Format: Mac OS Extended
    Block Size: 4 K
    Does anyone know what the problem might be causing T M to get corrupted, or at least how to get DW to perform the repair in a normal timeframe of just a few minutes?
    Thanks

    R C-R wrote:
    By this, do you mean that the partition's name is the one that appears after "Name: " in the Time Machine system preference & the partition contains a root level folder named "Backups.backupdb"? Is this partition used for anything else besides TM backups?
    Yes, separate partition with no other data on it.
    Disk Utility's permissions verify & repair options should only be available for mounted volumes (partitions) that are viable boot volumes; IOW, that can be used as a startup disk. TM backups are not startup volumes (because among other reasons they have no root level system folders), so both of these options should always be grayed out for TM backup volumes unless there is also a separate installation of OS X on them. If you have ever seen them not grayed out, this would be abnormal.
    BTW, I've been under the impression even partitions that are not bootable can be repaired. I have other partitions on other disks that have no system software that disk utility will go thru the repair process. Agreed that repair permissions is not available though.
    Often if I run a repair permissions on the main Leopard partition on the iMac's internal drive, somewhere during the process a message appears that the T M partition is not repairable but is being made available with a read only functionality.
    This doesn't make any sense to me. As explained above, permissions can't be repaired or verified on a normal TM volume. If you are repairing permissions on the normal startup volume on the internal drive of the iMac (or on any other startup disk), what is on the TM volume should be immaterial.
    Doesn't make any sense to me either. It doesn't happen all the time, but it does happen. Maybe something else is going on in the background while the permissions repair is going on that causes this result.
    A few other queries:
    How/when do you power down the external drive? If you shut down the Mac, do you wait for that to complete before powering down the external?
    Restart only when necessary, such as when new or update to software requires restart. Shut down only if I am having some other problem that I think might be helped by doing so. At shutdown, externals power down automatically.
    Is Disk Warrior an up-to-date, Leopard compatible version?
    Yes - 4.1.1
    Have you (perhaps inadvertently) manually changed anything in the folders of Backups.backupdb or created aliases that might reference any of its files or folders? Any chance that something destined for the other partition on the external drive accidentally was dropped into the TM partition instead?
    Not to my knowledge.
    Message was edited by: glassetcher

  • Disk Utility and Disk Warrior error on internal hard drive....PLEASE HELP!!

    After running idefrag on my internal Western Digital 120gig hard drive. The drive did not appear after I rebooted my mac. I opened Disk Utility and the drive is there but grayed out. I used "repair disk" under First Aid and it gave me this error:
    Verify and Repair disk “HD 120”
    Checking HFS Plus volume.
    Invalid B-tree node size
    Volume check failed.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    1 volume could not be repaired because of an error
    Then I tried using Disk Warrior 3.0 to rebuild and it gave me this error:
    error ""WD 120 GB" cannot be rebuilt. The original directory is too severely damaged. The disk was not modified (2155, 2179)".
    I'm not sure if this is the right area to post this, but I need help as most of my important data is on this hard drive. What else can I do?
    I am on a g4 quicksilver with 10.4.3 installed.

    Sorry to hear about your problem but unless you are working with very large files such as with video editing, etc., using a defrag utility is not required with OS X and no defrag utility should be used on a hard drive without a backup first.
    The current Disk Warrior version for Tiger is 3.0.3 and if Disk Warrior cannot repair the drive/directory, it must be in bad shape which was caused by using idefrag.
    You can try using a data recovery utility such as Data Rescue (Prosoft Engineering) which includes a free trial version.

  • External Hard Drive won't mount - tried Disk Warrior, am backing up as a .dmg...will this work?

    Hi Guys,
    Hopefully someone can help! Fairly desperate situation here...
    I backed up around 700GB of data to an Iomega external hard drive (supplied by the client), using my Macbook Pro...all was fine when I unmounted the drive at the end of the backup.
    The client took the drive away and called me to say he mounted the drive in Windows (on a PC), and he was able to work with the files for a time, but now the drive won't mount...
    I collected the drive, hooked it up to my Mac Pro, but OSX tells me it can't mount the drive. It shows up in Disk Utility in the sidebar, but not on the desktop...
    I tried repairing the disk using Disk Utility and with Disk Warrior, both tell me the disk cannot be repaired...
    I am currently making a backup of the drive as a .dmg file, using a program called Disk Drill...it's slow as I expected, but I'm still not sure the .dmg will mount...because surely it's just making a copy of the data exactly, of which some part is not mounting (a mount directory or something???)
    Is there any way you guys can think of me somehow taking the data and backing it up onto another disk?
    Specialist recovery services seem to think there shouldn't be any problem recovering the data, and of couse, as a costly last resort, that's what I'll have to do, but does anyone know how they may go about doing it? It is something vastly complicated such as a command line thing?
    Sorry about the length of this question...just hope someone can help!
    Thanks in advance...

    You didn't say what format (filesystem type) the disk was.
    However, I'd say your analysis is probably correct. Something has corrupted the disk. You can make a disk image copy to the .dmg which will preserve the data, such as it is, but I doubt extremely if it will fix any file system corruption.
    Furthermore, if both Disk Utility and Disk Warrior have said the disk is unreadable I'm dubious that anything else will magically repair it and that recovery probably consists of snuffling through the disk block by block.
    However if the filesystem is FAT (Windows) there may be other (Windows) utilities that can fix it.
    You said you 'backed up the data'. Does that mean you still have the original data on your MBP? Are you trying to recover the client's changes?

  • Mac Pro not recognizing bootable DVDs and Disk Utility giving odd results.

    My issue is complex, but I'll try my best to explain it as I can.
    One has been resolved it seems, but I am including it so that the whole issue can be seen in context.
    Friday, May 16, 2014
    Last night, after rebooting my Mac Pro from my Bootcamp partition (I'm using Windows 7 Professional if that information is helpful) I received a kernel panic upon Mac OS X booting (Mac OS X 10.6.8).
    My first action was to launch Disk Utility to verify the Mac HD, verify was stopped by disk utility citing that I should insert my Mac OS X install DVD and repair the disk.
    I tried booting from my Snow Leopard install DVD. After the grey Apple logo appeared with the gear spinning below it remained for roughly ten to fifteen seconds (a little long) — then the Apple logo changed to. A grey prohibitory sign (circle with a diagonal line through it, the spinning gear remained. — I tried booting from the Snow Leopard DVD a few time, same result.
    Following this I tried booting using Disk Warrior, same result again.
    I tried booting both the Snow Leopard and Disk Warrior DVDs in both my upper and lower optical drives, with no change.
    I decided to leave the issue and call Apple Support in the morning
    Saturday, May 17, 2014
    This morning I woke my Mac Pro from sleep, opened Disk Utility and tried verifying the hard drive to see if it was temporary — same result, 'please insert the Mac OS X install DVD and repair the drive.' — I also tried booting the install DVD again with no result.
    I then booted my Mac into Safe Mode to check my hardware.
    Upon opening Disk Utility and verifying my Mac HD — the result "Macintosh HD appears to be OK", rand the test again to see if this was an anomaly, but disk returned another pass.
    I performed a normal restart of my system, although Finder was a little slower to load than normal, the system booted correctly. — I then launched Disk Utility and verified the Mac HD, it returned another pass.
    This confused me, after a call to Apple Support the tech explained that 'sometime a Safe Mode boot will fix problems because it disables all non-essential processes when booting. — That makes sense to me.
    However.
    The issue of my Mac not recognizing bootable DVDs remains — it reads disks correctly, it just will not boot them.
    Other steps I have taken to try and resolve this remaining issue.
    1. a PRAM reset. — No change.
    2. an SMC reset. — No change.
    3. Removal of newly installed RAM. — I have tried both running the old and new RAM separately, no change using either combination.
    4. Running bootable DVDs in different optical bays. — No change from both bays.
    a. My upper drive is an MCE Blu-Ray/DVD combo drive, but I have booted from this drive before. (Less than six months old.)
    b. My lower drive is LG DVD-RAM combo drive, I have also booted from this drive before. (Over one year old, replacement for an Apple optical drive.)
    None of the above steps have helped, I still cannot boot from my optical drives — I always receive a prohibitory sign shortly after the Apple logo.
    Other system information:
    Mac OS X 10.6.8
    8GB of RAM (4 x 2GB)
    500GB Western Digital Caviar Blue HDD (less than a year old, boot drive for Mac OS X 10.6.8)
    1TB Samsung HDD (for data storage and also containing Bootcamp partition)
    2TB HDD (cannot remember manufacturer, contains Time Machine backups, as well as data storage)
    ATI Radeon HD 5770 with 1GB of VRAM
    Sorry for the long post but I really need to be able to boot from my optical drives.

    Update: found an old Mountain Lion installation USB flash drive I created a while back.
    I am able to boot from the ML USB flash drive, but am still unable to boot from my either my Snow Leopard Install DVD or my Disk Warrior DVD. — I have verified both DVD and they pass verification tests.
    This leads me to believe that the problem resides either in the Mac, or in BOTH  the Snow Leopard and Disk Warrior DVDs.
    Since I am able to boot from a USB drive, I will look into the possibility of creating a bootable Snow Leopard drive, and perhaps also a Disk Warrior drive — at least until I can resolve the 'not able to boot from DVD' issue.

  • Disk Warrior?

    I was having a problem opening certain programs (Office programs, iTunes) after updating Quicktime. Someone suggested that I repair my disk in disk utilities. I ran the repair and got this error:
    Invalid key length
    The volume Macintosh HD needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    First of all, what does all this mean? Someone on the boards recommended I purchase Disk Warrior to fix the problem. What are the chances this will actually fix it?
    The closest Apple Store is pretty far so I don't want to take it in if I don't have to. I also don't want to invest too much money because I plan on buying a new one in the next six months to a year.

    smitchell:
    what does all this mean?
    Disk Utility reports "Underlying task reported failure" when repairing a volume is a directory/filesystem corruption which cannot be repaired by Disk Utility. The article suggested the use of a third party disk utility. Tech Tool Pro and Disk Warrior are the best utilities for the job.
    Someone on the boards recommended I purchase Disk Warrior to fix the problem.
    As noted above, this is the utility most recommended in the forums as it is a very effective tool, as is the other utility I linked above.
    What are the chances this will actually fix it?
    There is an excellent chance that DW will repair the corrupted directory. Were your only error the invalid key length I would be more sanguine of success. However, with the -9972 error, I cannot guarantee it.
    In some cases the directory issue may be hardware based. It may result from a failing or failed HDD. If that is true in your case, DW will not do the job for you. However, since we don't know whether your issue is hardware or software based, it is not easy to tell.
    In most cases you would just go ahead and run one of these utilities anyway. If you had one of these in your toolbox, I would suggest that you begin there. However, these utilities cost around $100.
    Here is an option I would personally consider. If you have the latest PowerBook G4 12" it is now 3 years old. The average life of a HDD today is 3 to 5 years. In other words, your HDD is on the brink. For $100 you can buy a pretty nice HDD and with minimal skills, install it yourself. Of course, it will be helpful if you have a good reliable backup. If you don't you will then need to recover your data from the old HDD.
    Here is a link that suggests a variety of approaches to your issue: Kappy on Error -9972.
    I realize I have not given you very specific directions. However, I thought I would lay out some options for you to consider. Please do post back with your questions and/or comments.
    cornelius

  • Disk Warrior help

    hi, here's my situation.
    2.5 dual with 3.5 gigs of RAM. Running Tiger. hard drive i believe is a Hitachi (whatever is the default drive) and is 160 gigs.
    I was editing in DVPSP 3 and it kept quiting on me. so i restarted. when i did the OS did not come up instead i got the folder with the flashing question mark. not good. it happened to me last year and i knew that i was in trouble.
    I rebooted with the install cd. i then went to disk utility and tried to repair the disk. i got an error saying, "Invalid B-tree node size." from what i researched this means the drive is corrupted but not a hard drive failure, correct? i also looked for the start up disk but the drive was not detected there as well. all i saw was the install cd.
    I also have another internal hard drive installed. a 250 gig drive that i use for all my video work. it just so happened that the drive i was working on last night was my main drive (the 160 gig drive) as the 250 gig drive was full. this drive seems to be ok.
    I bought disk warrior last night which i installed on an Imac I have. I hooked this up to the 2.5 dual via a firewire cable. from the Imac i started Disk Warrior and i could see both my drives on the 2.5 dual. i selected my damaged drive and selected "Rebuild."
    I realized it was going to take a few hours so i went to sleep. this morning it was done and i read the report, saying it had built a temporary drive. like the dummy that i am (and being half asleep didn't help) i accidently cancelled everything. i didn't click on "Replace." ah!!!
    so i re-did everything while i went to work this morning. so when i get home later today, after i click on "Replace." everything will be good? i realize some stuff might be lost but i want to at least be able to boot into my system. i have a lot of photos that i want to save and also the latest project i was working on.
    is it true you can also "Preview" the new drive and be able to back up files right then before it replaces your old drive.
    any advice will be greatly appreaciated! thanks.
    - robert

    Hi, Roberto and ds_store—
    I'm writing to share a few thoughts, fwiw, in addition to ds_store's helpful reply. Though I consider myself a relative newbie to such maladies (particularly in OS X), I've unfortunately also experienced disk corruption within the last 10 days. . .
    (1) Re: "this means the drive is corrupted but not a hard drive failure, correct?" — probably. But this is something you can easily check. I'd suggest two things:
    ](a) Booting from your Install Disc, open Disk Utility and select your HD. Note the "S.M.A.R.T. status." Hopefully, it says "verified."
    ](b) While holding down the option key, boot from your Install Disc again. This will provide you with 2 or 3 choices of "boot volumes" for startup. Select Apple Hardware Test (AHT). Run in Extended Test mode. Among other components, this will provide results evaluating your logic board, mass storage (HD), and memory (RAM).
    If Disk Utility reports S.M.A.R.T. status "verified" and AHT indicates that mass storage has "passed," these provide a strong indication that your HD probably has not suffered any significant hardware failure. (Note that this is not definitive without further diagnostics that an Apple-Authorized Service Provider can conduct.)
    (2) Another benefit of running AHT is that it may provide an indication of other factor(s) that caused your Power Mac to suffer from such significant disk directory corruption. Imho, this is a question well worth your attention. (In my case, it was bad RAM. Not only didn't DiskWarrior work initially because of this — but the directory would have probably become corrupted again because of the RAM problem, even if I had been able to replace the directory with one "rebuilt" by DW.) Assuming DW does work for you (which seems likely, based on what you've described), you may benefit from running Disk Utility and DIsk Warrior again in the near future as a means to evaluate whether there is an ongoing source of corruption. Keep in mind that DW focuses on disk directory maintenance and repair — other HD maintenance/repair functions require TechTool Pro or other utilities.
    (3) Re: "a lot of photos that i want to save and also the latest project i was working on" — if DW is successful, your data may be fine. But if it proves necessary (and directory corruption isn't too bad or is improved by DW), you may be able to recover your unsaved data using FireWire Target disk mode, with your PowerMac as target and iMac as host.
    (4) Re: "is it true you can also "Preview" the new drive and be able to back up files right then before it replaces your old drive?" — I haven't tried this personally with DiskWarrior, but it should be feasible, according to the details described in the "What to Look for During Preview" section (pp. 30-33) of the DiskWarrior Manual that you can read from its CD.
    I hope some of this is useful to you. Good luck!
    Dean

  • Mac Pro- Damaged Disk/Permissions - Disk Warrior unable to fix, please help

    Hey, I am really hoping I can solve this over the discussion board. My Mac Pro 1,1, with OSX 10.6.2 installed, has been acting up really badly lately. Random crashes, really slow, and my Radeon XT1900 is about to die, I think; the fan almost never turns off.
    But the main issue I'd like to address is my damaged home disk. I booted up from the install disk and used Disk Utility to "Verify and Repair Disk" on my home disk. It said that the "Header has some minor damage," the repair finished and DU reported that it had repaired the volume and everything was fine.
    However, after booting up from the HD, I went back into Disk Utility and did another "Verify Disk" to double check. It came up with an error stating: "Disk Utility stopped verifying 'Home' The disk needs to be repaired. Startup your computer with another disk and use DU to repair this disk."
    So I booted from the install disk again, ran Disk Utility, and it said that everything was fine. So I booted back from HD, ran DU - only for it to report the same error as before. Why is DU reporting a problem when booting from disk, but it says there is no problem when running from the install disk?
    I decided to get Disk Warrior to see if that would help. I used it to "Repair Disk Permissions" and also "Check All Files & Folders". Disk Warrior then stopped saying: "An unexpected error occurred while attempting to perform the file operations. Restart from DW disc and try again. ERROR CODE (2903, -8902)."
    Here are some screenshots of the errors from Disk Warrior and Disk Utility (booted from HD). image: !http://img683.imageshack.us/img683/9789/duerror.png!
    image: !http://img683.imageshack.us/img683/9269/dwerror.png!
    So my main question is: Why, after Disk Utility, running off the install disk, reports that it "repaired - some minor damage to the header," does it then report the "header is damaged" when booted from the system?

    Don't rely on just Apple First Aid, or trust it with finding and repairing.
    Sorry you had to wait this long to get Disk Warrior.
    You should always run DW from another hard drive.
    Install a fresh clean copy of 10.6.x on a small 30GB partition for emergency only.
    you can use that to boot from to run repairs and maintenance using Apple and Disk Warrior.
    Don't bother using DVDs or CD to boot from.
    It sounds like you are running DW and DU from hard drives, but not clear which or from where (and when).
    Always use the SAME version when repairing permissions, never use an older version OS or of Disk Utility.
    CLONE your system. Always have a couple bootable backups.
    Choice is Apple Disk Utility Restore; SuperDuper; Carbon Copy Cloner
    If a drive does have errors, be ready to restore and have backups on hand if it comes to that.
    System (OS and apps) probably only change weekly or even monthly.
    You can backup /Users to its own backup partition more often, and use Time Machine plus another method there.
    Personally, I tend to run DW directory repair first and sometimes only, and only then check files.
    TechTool Pro 5 is what I use for checking files, disk media for weak sectors, and some other problems not covered by Disk Warrior; and, because it can run concurrently on multiple volumes and drives.
    It is 'iffy' to verify a live system and get an accurate read of its health, but I'd say Disk Utility is "out of its depths, and league" when it comes to finding and repairing, and for the errors it is encountering on your system.
    Isolate the sytem from data and media files and libraries as much as you can and still easy to manage.
    Most errors are with system or boot drive.
    Radeon X1900 needs to be removed, carefully inspected, and any dust in the vents, air intake portion and exhaust, cleaned out. Right now the only real upgrade there is the ATI 4870 for now (Apple's or flashed).

  • Suggestion: Use Disk Warrior/ Disk Utility before, after 10.5.6 update

    FWIW: For years I have used a combination of Disk Warrior and then Disk Utility before and after updates, major installs, etc. Normally I boot right into Disk Warrior and let it do it's routine and after that check the disk and repair permissions using Disk Utility. Result: Many years of OS X iterations with no problems yet. Knock on wood.
    10.5.6: Same routine, no problems.
    Observations:
    Disk Warrior reported a higher number of Directory graph items out of order after being run prior to installation than most updates of this size in my opinion.
    Disk Utility: The disk checked fine and no permissions were repaired. Except that old Group 26.....
    Net: 10.5.6 seems the fastest of the Leopards so far. Safari is by far the best yet. It also seems there are a ton of 3rd party apps being updated so be sure to follow due diligence and turn off the Haxies before you begin.
    I am beginning to get excited about Snow Leopard, as Leopard's progress is really starting to show.

    I thought I was obsessive compulsive for running Repair Disk, Repair Permissions and Disk Warrior (and sometimes TechTool Pro) before installing any OS updates. It’s good to know someone else does that.
    I too have never had a problem with any updates. When I installed the first version of Leopard 10.5, it balked on my G5 1.6 GHz computer because it had non-Apple RAM in it that neither Disk Utilities nor Disk Warrior would catch (or even TechTool because it looked like good RAM, but the initially finicky 10.5 installer did not like it). The only way I figured it out was to run System Profiler from the install disk, so I added that to my list of “before installing” tasks.
    It seems many people having problems with updates don’t know to at least run Disk Utilities before an update.
    It’s good you are trying to get the word out.

  • Hard drive troubles- data rescue 3, disk warrior

    hello everyone. my internal hard drive stopped mounting and disk utility sees it but all the buttons are dimmed. a friend loaned me data rescue 3 and disk warrior. i have an external hard drive onto which i installed the OS and im booting from that.
    i heard that using disk warrior, if it doesnt work right away, might make data recovery more difficult. so i thought i would run DR3 first. i first did the quick mode, which, after a while, gave me a warning and asked to try deep scan. so ive been running deep scan for about an hour now, and at this rate, i estimate it will take data rescue about 8 years to complete scanning my hard drive. =) now that ive been observing it, it seems stuck at a particular block.
    anyway, are there any recommendations? should i try the disk warrior boot DVD prematurely if data rescue is still stuck when i wake up tomorrow? apparently, my hard drive has no hardware issues (says data rescue)...
    any response will be appreciated...there is a previous post of mine about the earlier stages of this problem if you wanna take a look.
    thanks in advance,

    I personally would use Disk Warrior before attempting to recover any data for that exact reason.

  • Mac Book Crashing Can anyone please help with this error message,  I've run Disk warrior and everthing is coming up fine, so may be a hardware issue, thank you Interval Since Last Panic Report:  22119 sec Panics Since Last Report:          14 Anonymous UU

    I've run Disk warrior, it says all the files and harddrive are fine.
    thanks for your help.  This crashing was happening before I upgraded to Lion
    Interval Since Last Panic Report:  22119 sec
    Panics Since Last Report:          14
    Anonymous UUID:                    1DA2B715-D1E5-4BF1-A47F-D31CBD8C1E78
    Wed Mar  7 13:21:17 2012
    panic(cpu 2 caller 0xffffff7f8098c907): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0x0a2910de 0x00100000 0x00000000, BAR0 0xd2000000 0xffffff80a0354000 0x0a5480a2, D0, P2/4
    Backtrace (CPU 2), Frame : Return Address
    0xffffff80a398b800 : 0xffffff8000220702
    0xffffff80a398b880 : 0xffffff7f8098c907
    0xffffff80a398b910 : 0xffffff7f80a7ca64
    0xffffff80a398b960 : 0xffffff7f80a7cb24
    0xffffff80a398b9c0 : 0xffffff7f80d29749
    0xffffff80a398bb00 : 0xffffff7f80a9bbad
    0xffffff80a398bb30 : 0xffffff7f80996282
    0xffffff80a398bbe0 : 0xffffff7f80991b84
    0xffffff80a398bdd0 : 0xffffff7f80993639
    0xffffff80a398beb0 : 0xffffff7f8092e484
    0xffffff80a398bf00 : 0xffffff7f820a47d6
    0xffffff80a398bf50 : 0xffffff7f820a4f2a
    0xffffff80a398bf70 : 0xffffff800023db2c
    0xffffff80a398bfb0 : 0xffffff8000820057
          Kernel Extensions in backtrace:
             com.apple.NVDAResman(7.1.8)[94BA87BA-B128-3310-9860-98EC67AB7FAF]@0xffffff7f809 2c000->0xffffff7f80c05fff
                dependency: com.apple.iokit.IOPCIFamily(2.6.8)[F63D4ABE-42DA-33EF-BADD-3415B0CB0179]@0xffff ff7f808b7000
                dependency: com.apple.iokit.IONDRVSupport(2.3.2)[4B3F84DC-18B3-3897-BC56-4E3940878047]@0xff ffff7f8091a000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[FE536983-1897-3D6B-965E-24B5A67080DA]@0 xffffff7f808e2000
             com.apple.nvidia.nv50hal(7.1.8)[7596DB8C-AE9D-3C87-B11A-0ED8F940CAF8]@0xffffff7 f80c06000->0xffffff7f80f27fff
                dependency: com.apple.NVDAResman(7.1.8)[94BA87BA-B128-3310-9860-98EC67AB7FAF]@0xffffff7f809 2c000
             com.apple.driver.AGPM(100.12.42)[380DAA3B-4F08-3152-A3A0-E3F8B6E4B92B]@0xffffff 7f820a3000->0xffffff7f820adfff
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[FE536983-1897-3D6B-965E-24B5A67080DA]@0 xffffff7f808e2000
                dependency: com.apple.iokit.IONDRVSupport(2.3.2)[4B3F84DC-18B3-3897-BC56-4E3940878047]@0xff ffff7f8091a000
                dependency: com.apple.iokit.IOPCIFamily(2.6.8)[F63D4ABE-42DA-33EF-BADD-3415B0CB0179]@0xffff ff7f808b7000
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    11D50
    Kernel version:
    Darwin Kernel Version 11.3.0: Thu Jan 12 18:47:41 PST 2012; root:xnu-1699.24.23~1/RELEASE_X86_64
    Kernel UUID: 7B6546C7-70E8-3ED8-A6C3-C927E4D3D0D6
    System model name: MacBookPro6,2 (Mac-F22586C8)
    System uptime in nanoseconds: 5224512131000
    last loaded kext at 1624245923653: com.apple.driver.AppleFireWireStorage    3.0.1 (addr 0xffffff7f808b3000, size 16384)
    last unloaded kext at 1739101632802: com.apple.driver.StorageLynx    3.0.1 (addr 0xffffff7f80809000, size 8192)
    loaded kexts:
    com.regularrateandrhythm.driver.RowmoteIREmu    1.0
    com.bresink.driver.BRESINKx86Monitoring    8.0
    com.AmbrosiaSW.AudioSupport    3.2
    com.apple.driver.Oxford_Semi    3.0.1
    com.apple.driver.AppleUSBDisplays    317
    com.apple.driver.AppleHWSensor    1.9.4d0
    com.apple.filesystems.autofs    3.0
    com.apple.driver.AudioAUUC    1.59
    com.apple.driver.AGPM    100.12.42
    com.apple.driver.AppleMikeyHIDDriver    122
    com.apple.driver.AppleHDA    2.1.7f9
    com.apple.driver.AppleUpstreamUserClient    3.5.9
    com.apple.driver.AppleMCCSControl    1.0.26
    com.apple.driver.AppleMikeyDriver    2.1.7f9
    com.apple.driver.AppleIntelHDGraphics    7.1.8
    com.apple.driver.AppleIntelHDGraphicsFB    7.1.8
    com.apple.driver.SMCMotionSensor    3.0.1d2
    com.apple.iokit.IOUserEthernet    1.0.0d1
    com.apple.Dont_Steal_Mac_OS_X    7.0.0
    com.apple.driver.AudioIPCDriver    1.2.2
    com.apple.driver.AppleSMCLMU    2.0.1d2
    com.apple.GeForce    7.1.8
    com.apple.driver.ACPI_SMC_PlatformPlugin    4.7.5d4
    com.apple.driver.AppleMuxControl    3.0.16
    com.apple.driver.AppleLPC    1.5.3
    com.apple.driver.AppleUSBTCButtons    225.2
    com.apple.driver.AppleIRController    312
    com.apple.driver.AppleUSBTCKeyboard    225.2
    com.apple.driver.AppleUSBCardReader    3.0.1
    com.apple.iokit.SCSITaskUserClient    3.0.3
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
    com.apple.BootCache    33
    com.apple.iokit.IOAHCIBlockStorage    2.0.1
    com.apple.driver.AppleUSBHub    4.5.0
    com.apple.driver.AppleSmartBatteryManager    161.0.0
    com.apple.driver.AppleFWOHCI    4.8.9
    com.apple.driver.AirPort.Brcm4331    513.20.19
    com.apple.iokit.AppleBCM5701Ethernet    3.0.8b2
    com.apple.driver.AppleEFINVRAM    1.5.0
    com.apple.driver.AppleAHCIPort    2.2.0
    com.apple.driver.AppleUSBEHCI    4.5.8
    com.apple.driver.AppleACPIButtons    1.4
    com.apple.driver.AppleRTC    1.4
    com.apple.driver.AppleHPET    1.6
    com.apple.driver.AppleSMBIOS    1.7
    com.apple.driver.AppleACPIEC    1.4
    com.apple.driver.AppleAPIC    1.5
    com.apple.driver.AppleIntelCPUPowerManagementClient    167.3.0
    com.apple.nke.applicationfirewall    3.2.30
    com.apple.security.quarantine    1.1
    com.apple.driver.AppleIntelCPUPowerManagement    167.3.0
    com.apple.iokit.IOFireWireSerialBusProtocolTransport    2.1.0
    com.apple.iokit.IOFireWireSBP2    4.2.0
    com.apple.driver.AppleUSBHIDKeyboard    152.3
    com.apple.driver.AppleHIDKeyboard    152.3
    com.apple.driver.AppleUSBAudio    2.8.2f5
    com.apple.kext.triggers    1.0
    com.apple.driver.DspFuncLib    2.1.7f9
    com.apple.driver.AppleSMBusController    1.0.10d0
    com.apple.iokit.IOSurface    80.0
    com.apple.iokit.IOBluetoothSerialManager    4.0.3f12
    com.apple.iokit.IOSerialFamily    10.0.5
    com.apple.iokit.IOFireWireIP    2.2.4
    com.apple.iokit.IOAudioFamily    1.8.6fc6
    com.apple.kext.OSvKernDSPLib    1.3
    com.apple.driver.AppleHDAController    2.1.7f9
    com.apple.iokit.IOHDAFamily    2.1.7f9
    com.apple.driver.ApplePolicyControl    3.0.16
    com.apple.driver.AppleSMC    3.1.1d8
    com.apple.driver.IOPlatformPluginFamily    4.7.5d4
    com.apple.driver.AppleSMBusPCI    1.0.10d0
    com.apple.driver.AppleGraphicsControl    3.0.16
    com.apple.driver.AppleBacklightExpert    1.0.3
    com.apple.nvidia.nv50hal    7.1.8
    com.apple.NVDAResman    7.1.8
    com.apple.iokit.IONDRVSupport    2.3.2
    com.apple.iokit.IOGraphicsFamily    2.3.2
    com.apple.driver.BroadcomUSBBluetoothHCIController    4.0.3f12
    com.apple.driver.AppleUSBBluetoothHCIController    4.0.3f12
    com.apple.iokit.IOBluetoothFamily    4.0.3f12
    com.apple.driver.AppleUSBMultitouch    227.1
    com.apple.iokit.IOUSBHIDDriver    4.4.5
    com.apple.iokit.IOSCSIBlockCommandsDevice    3.0.3
    com.apple.iokit.IOUSBMassStorageClass    3.0.1
    com.apple.driver.AppleUSBMergeNub    4.5.3
    com.apple.driver.AppleUSBComposite    4.5.8
    com.apple.iokit.IOSCSIMultimediaCommandsDevice    3.0.3
    com.apple.iokit.IOBDStorageFamily    1.6
    com.apple.iokit.IODVDStorageFamily    1.7
    com.apple.iokit.IOCDStorageFamily    1.7
    com.apple.driver.XsanFilter    403
    com.apple.iokit.IOAHCISerialATAPI    2.0.1
    com.apple.iokit.IOSCSIArchitectureModelFamily    3.0.3
    com.apple.iokit.IOUSBUserClient    4.5.8
    com.apple.iokit.IOFireWireFamily    4.4.5
    com.apple.iokit.IO80211Family    412.2
    com.apple.iokit.IOEthernetAVBController    1.0.0d5
    com.apple.iokit.IONetworkingFamily    2.0
    com.apple.iokit.IOAHCIFamily    2.0.7
    com.apple.iokit.IOUSBFamily    4.5.8
    com.apple.driver.AppleEFIRuntime    1.5.0
    com.apple.iokit.IOHIDFamily    1.7.1
    com.apple.iokit.IOSMBusFamily    1.1
    com.apple.security.sandbox    177.3
    com.apple.kext.AppleMatch    1.0.0d1
    com.apple.security.TMSafetyNet    7
    com.apple.driver.DiskImages    331.3
    com.apple.iokit.IOStorageFamily    1.7
    com.apple.driver.AppleKeyStore    28.18
    com.apple.driver.AppleACPIPlatform    1.4
    com.apple.iokit.IOPCIFamily    2.6.8
    com.apple.iokit.IOACPIFamily    1.4

    Please describe:
    Computer model & hardware characteristics (especially RAM).
    How much free space left on HDD.
    Any add-ons you may have added to the system (antivirus, screen eye candy, etc.)
    What applications were running when the crash occurred.
    What were you doing when the crash occurred.

  • I have a G5 imac that is using Disk Warrior as the start up disk and can't change back.

    I am using a G5 imac (OS 10.4.8 I think the last update is) and I was attempting to use Disk Warrior to recover a lost file. On my other Macs you made Disk Warrior the start up disk to use it, which I did here but I think that was a mistake. Now I can't change back to the regular start up disk.
    I tried starting in safe mode but I think I'm getting kernel panic because it goes to a gray screen and tells me to restart.

    I don't think Disk Warrior does file recovery. See:
    Basics of File Recovery
    Files in Trash
    If you simply put files in the Trash you can restore them by opening the Trash (left-click on the Trash icon) and drag the files from the Trash to your Desktop or other desired location.  OS X also provides a short-cut to undo the last item moved to the Trash -press COMMAND-Z.
    If you empty the Trash the files are gone. If a program does an immediate delete rather than moving files to the Trash, then the files are gone.  Recovery is possible but you must not allow any additional writes to the hard drive - shut it down. When files are deleted only the directory entries, not the files themselves, is modified. The space occupied by the files has been returned to the system as available for storage, but the files are still on the drive. Writing to the drive will then eventually overwrite the space once occupied by the deleted files in which case the files are lost permanently. Also if you save a file over an existing file of the same name, then the old file is overwritten and cannot be recovered.
    General File Recovery
    If you stop using the drive it's possible to recover deleted files that have not been overwritten by using recovery software such as Data Rescue II, File Salvage or TechTool Pro.  Each of the preceding come on bootable CDs to enable usage without risk of writing more data to the hard drive.  Two free alternatives are Disk Drill and TestDisk.  Look for them and demos at MacUpdate or CNET Downloads.
    The longer the hard drive remains in use and data are written to it, the greater the risk your deleted files will be overwritten.
    Also visit The XLab FAQs and read the FAQ on Data Recovery.

  • Disk Warrior and Quicktime 7.04

    I was having problems running Disk Warrior 3.03 (DW) from my cloned (using Super Duper) external firewire external hard drive (Lacie d2 HD 250GB). (NEW iMacG5 iSight)
    The problem:
    Boot from the clone and ran DW, at the completion of DW if I chose to "Replace" the directory DW crashes after replacement.
    Alsoft tech support:
    The issue is created with the installation of QuickTime 7.0.4. The actual DiskWarrior rebuild process is completed and the crash will do no harm to your data.
    The current options are:
    1) Downgrade QuickTime to 7.0.1
    Apple has released a QuickTime 7.0.1 re-install located here:
    http://www.apple.com/support/downloads/
    quicktime701reinstallerforquicktime704.html
    2) Start up from the DiskWarrior CD and rebuild the directory of the drive from the CD.
    I tested with both QT versions and sure enough everything worked as support advised from the external FW HD.
    P.S. I went back to QT 7.04
    Hope this helps someone.

    Thank you. This is definitely most helpful to me.

  • Disk Warrior and 'The Folder with the ? Mark'

    Good morning. My MacBook recently crashed and I am left with the dreaded and endlessly blinking 'Question Mark Folder'. I have tried to restart using the System Disk and running Disk Utility but the Hard Drive is nowhere to be found.
    I have read in the Discussions that running DiskWarrior may help. I have the program on my PowerBook G4 as well as on an external hard drive, but I do not have a DiskWarrior disc. Is there a way to run the program from these to repair the drive on my MacBook or retrieve my data? If not, is there a way to make a DiskWarrior disc from my .dmg file?
    Thanks for your help.
    John

    Disk Warrior comes on a bootable disc unless you downloaded it or lost yours. You cannot easily make a bootable CD or DVD, but your could put it on a bootable external hard drive that has a bootable copy of OS X (current version) and your copy of DW must be at least 4.0 for Tiger or 4.1 for Leopard.
    However, it's most unlikely that DW will help you because the question mark means that important system files are lost or corrupted. The solution is to reinstall OS X. It's possible you can do the following:
    How to Perform an Archive and Install
    An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
    1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
    2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
    3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
    4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
    5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
    6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

  • Kernel Panic PERSISTS :/ after multiple Disk Warrior and Disk Repairs

    Hey guys, I need your wisdom!
    My OS took a dump on me the other night. Finder froze up and when I restarted, I got this at boot up, (see below, after my whole explaination as to what I've tried).
    So, I bought an external drive, partitioned and installed Mavericks OS, along with Disk Warrior.
    I ran through everything on DW and it seemed to find issues and repair the problems. Then I ran it through Disk Utility and it all checked out, "ok".
    However, when I went to restart with my main OS, it gave the kernel panic error, again.
    I'm frustrated, needless to say. I've repeatedly tried to rebuild the drive, repair disk permissions, etc, and every time it seems to "work" but it doesn't.
    I am running a data recovery program and it's seeming to find all my files there. But, I really want to just try to resolve this problem to access the drive and do a backup from within.
    Please, what are you thoughts on this?
    Anonymous UUID:       B45A0F2A-373D-60AE-D2C4-25F99F9AE358
    Thu Sep 25 11:18:51 2014
    panic(cpu 0 caller 0xffffff801b9ce524): "Process 1 exec of /sbin/launchd failed, errno 8"@/SourceCache/xnu/xnu-2422.115.4/bsd/kern/kern_exec.c:3836
    Backtrace (CPU 0), Frame : Return Address
    0xffffff80ada1bdf0 : 0xffffff801b622f79
    0xffffff80ada1be70 : 0xffffff801b9ce524
    0xffffff80ada1bef0 : 0xffffff801b9ae467
    0xffffff80ada1bf10 : 0xffffff801b9e2bc1
    0xffffff80ada1bf50 : 0xffffff801b620b3b
    0xffffff80ada1bf80 : 0xffffff801b6dca73
    0xffffff80ada1bfa0 : 0xffffff801b6f3942
    BSD process name corresponding to current thread: init
    Mac OS version:
    Not yet set
    Kernel version:
    Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64
    Kernel UUID: 9477416E-7BCA-3679-AF97-E1EAAD3DD5A0
    Kernel slide:     0x000000001b400000
    Kernel text base: 0xffffff801b600000
    System model name: MacBook5,1 (Mac-F42D89C8)
    System uptime in nanoseconds: 1410682262
    last loaded kext at 1149667042: com.apple.driver.AppleUSBTCKeyEventDriver 240.2 (addr 0xffffff7f9d34d000, size 16384)
    loaded kexts:
    com.rogueamoeba.InstantOn 6.0.1
    com.apple.driver.AppleUSBTCKeyEventDriver 240.2
    com.apple.driver.AppleUSBTCKeyboard 240.2
    com.apple.driver.AppleFileSystemDriver 3.0.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeLZVN 1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
    com.apple.BootCache 35
    com.apple.driver.AppleIRController 325.7
    com.apple.iokit.SCSITaskUserClient 3.6.7
    com.apple.driver.XsanFilter 404
    com.apple.iokit.IOAHCIBlockStorage 2.6.0
    com.apple.driver.AppleUSBOHCI 656.4.1
    com.apple.driver.AppleUSBHub 683.4.0
    com.apple.nvenet 2.0.21
    com.apple.driver.AppleAHCIPort 3.0.5
    com.apple.driver.AirPort.Brcm4331 700.20.22
    com.apple.driver.AppleUSBEHCI 660.4.0
    com.apple.driver.AppleSmartBatteryManager 161.0.0
    com.apple.driver.AppleRTC 2.0
    com.apple.driver.AppleHPET 1.8
    com.apple.driver.AppleACPIButtons 2.0
    com.apple.driver.AppleSMBIOS 2.1
    com.apple.driver.AppleACPIEC 2.0
    com.apple.driver.AppleAPIC 1.7
    com.apple.driver.AppleIntelCPUPowerManagementClient 217.92.1
    com.apple.nke.applicationfirewall 153
    com.apple.security.quarantine 3
    com.apple.driver.AppleIntelCPUPowerManagement 217.92.1
    com.apple.iokit.IOUSBHIDDriver 660.4.0
    com.apple.driver.AppleUSBMergeNub 650.4.0
    com.apple.driver.AppleUSBComposite 656.4.1
    com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.6.7
    com.apple.iokit.IOBDStorageFamily 1.7
    com.apple.iokit.IODVDStorageFamily 1.7.1
    com.apple.iokit.IOCDStorageFamily 1.7.1
    com.apple.iokit.IOAHCISerialATAPI 2.6.1
    com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.7
    com.apple.iokit.IOUSBUserClient 660.4.2
    com.apple.driver.NVSMU 2.2.9
    com.apple.iokit.IOAHCIFamily 2.6.5
    com.apple.iokit.IO80211Family 640.36
    com.apple.iokit.IONetworkingFamily 3.2
    com.apple.iokit.IOUSBFamily 686.4.1
    com.apple.driver.AppleEFINVRAM 2.0
    com.apple.driver.AppleEFIRuntime 2.0
    com.apple.iokit.IOHIDFamily 2.0.0
    com.apple.iokit.IOSMBusFamily 1.1
    com.apple.security.sandbox 278.11.1
    com.apple.kext.AppleMatch 1.0.0d1
    com.apple.security.TMSafetyNet 7
    com.apple.driver.AppleKeyStore 2
    com.apple.driver.DiskImages 371.1
    com.apple.iokit.IOStorageFamily 1.9
    com.apple.iokit.IOReportFamily 23
    com.apple.driver.AppleFDEKeyStore 28.30
    com.apple.driver.AppleACPIPlatform 2.0
    com.apple.iokit.IOPCIFamily 2.9
    com.apple.iokit.IOACPIFamily 1.4
    com.apple.kec.corecrypto 1.0
    com.apple.kec.pthread 1
    Model: MacBook5,1, BootROM MB51.007D.B03, 2 processors, Intel Core 2 Duo, 2 GHz, 4 GB, SMC 1.32f8
    Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x859B, 0x435432353636344243313036372E4D313653
    Memory Module: BANK 0/DIMM1, 2 GB, DDR3, 1067 MHz, 0x859B, 0x435432353636344243313036372E4D313653
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.100.22)
    Bluetooth: Version 4.2.7f3 14616, 3 services, 23 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en1
    Serial ATA Device: ST95005620AS, 500.11 GB
    Serial ATA Device: HL-DT-ST DVDRW  GS21N
    USB Device: Built-in iSight
    USB Device: External USB 3.0
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: IR Receiver
    USB Device: BRCM2046 Hub
    USB Device: Bluetooth USB Host Controller
    Thunderbolt Bus:

    gybek wrote:
    Um, so what about the TM backup, will it not transfer over the kernel panic errors?
    Target Disk Mode requires a second Mac. It puts a "bad" Mac which may have hardware issues and cannot boot properly, in a mode where the internal drive can be mounted on a second Mac as an external Thunderbolt/Firewire drive.
    1. Power cycle Kernel-Panic MAC (KP-MAC) in TDM by holding the T key at the chime. If you see a floating FW symbol, then the KP-MAC is in TDM.
    2. Use a second Mac (Good-MAC) and  connect the KP-MAC via Thunderbolt/FW cables as appropriate. This may require a TB-to-FW adapter, a FW800-to-FW400 "gender-bender" and an appropriate cable.
    3. Once the KP-MAC drive is visible on the G-MAC, you can either create a full disk image backup of the KP-MAC Disk.
    4. You can also configure an external drive as a TM target and backup KP-MAC's internal drive via TM with appropriate TM Options.
    5. In this case the KP-MAC OS is not in use, just the hardware/firmware which is required to put it in TDM.
    This can be useful when your graphics card or display may not work properly, but the CPU/Memory/Disk ar relatively unaffected.
    How do I even do a TM backup on that original drive from my temp OS?
    As suggested earlier, TM can be used.
    Linc suggested using Disk Utility and doing it that way to make a backup and then transferring over everything to a newly installed OS that way.
    In TDM, if a TM backup is not possible, for any number of reasons, Disk Utility can create an image of KP-MAC's drive which can be moved to any desired location and files can be extracted as necessary.
    Another option is to create an external bootable OS on a USB/FW disk, boot from it, assuming that KP-MAC can be booted and does not have significant HW issues, and create a Disk Image to an external disk destination.
    It's almost 15 years of my life on there.
    Hence the need for a very good backup/restore strategy.

Maybe you are looking for

  • Color difference between PNG and JPG in Save For Web

    I am working on a website and I while building images for the site I am using a mix of png and jpg images. When I "Save for Web" the same source image creates two different color images when I save them as either png or jpg. How do I make sure the im

  • Problem with external domain name and hosting

    Hi I have my own domain name and hosting plan I want to use. However, I have trouble pointing my site from BC to my server. I found the following information but in my case "create A-Records" is not available on the "Site Domains". Please advise. Tha

  • Java Web Start and Java3D

    Hi All Do you know any free server that uses Java Web Start? I want to upload my Java3D application..... Thank u

  • Hyperion analyzer installation issue

    Hi, I am installing Hyp analyzer 7.2.5. Can any one tell me ..why the below warnings are arising The InstallShield Wizard has successfully installed Hyperion Analyzer 7.2.5. Choose Finish to exit the wizard. However, the following warnings were gener

  • Import preserving folder hierarchy

    Hi all, I have many (>100) folders (within folders) of photos on a harddisk which I would like to import into LR while preserving the folder hierarchy structure. Is there a way to import all folders at the same time while preserving the hierarchy or