![]() Third-party mass storage drives or PCI card issues.Third-party FireWire device or enclosure, or other peripheral devices.Technical overview of disk volume structures A disk physically malfunctions in the worst case.Įxample of an accompanied error message (DiskWarrior normally fixes 1 to 6, but cannot fix errors 7 to 10 if the symptoms are very bad.You may be unable to re-initialize the hard drive.The high level disk format (Standard format) may be unable to perform.Most likely, Disk Utility, Norton Utilities, TechTool and DiskWarrior cannot fix the issues. ![]() A target disk mode solution may not work.A folder with a flashing question mark may appear.A volume is grayed out or not mounted with or without a kernel panic.In most cases, you are unable to restart from Mac OS X. If the error occurs when an external FireWire device is connected, disconnect it until you verify the device's compatibility. This issue can also lead up to a kernel panic. Troubleshooting a solution may depend upon computer configuration and whether the -9972 error is accompanied by other critical errors. The problem can also lead to other critical errors such as "Keys Out of Order," "Invalid node structure" and/or "Invalid sibling link." The causes and scenarios vary. ![]() The error message, "Error: The underlying task reported failure on exit (-9972)" is a serious filesystem error in the Mac OS X Core Foundation. You are currently browsing the archives for the DiskWarrior category.A bit dated (pre-Tiger), but still a good deal of useful information: You can’t ask for anything better than that - and all told, it only took about 15 minutes, including the run to the store to buy the Firewire cable. Thanks to DiskWarrior, Jess now has her laptop back, with nary a file misplaced. (Though I do wish I could have skipped the $9 shipping, since I just bought it online and I don’t really need or want a copy in the mail.) (Ouch!) But for me, DiskWarrior was just the best $100 I’ve ever spent. Of course, for some people, it’s not so simple: disable_journal.c was written by an Apple user who couldn’t get even DiskWarrior to fix the problem, so instead wrote a small C app to hack the bits of the drive. So, following the advice of Some Guy On the Internet, I went ahead and bought DiskWarrior, and he’s 100% right: “Dont waste any more time. Trying to boot the computer still paniced immediately, with the same “journal magic is bad” message. Disk Utility reported that it had repaired the disk successfully, and even claimed it could mount the disk successfully, but never did. It showed up in Disk Utility, and I ran “Repair Disk” on it. I went out and bought a Firewire cable this morning and mounted the disk to my laptop. I was royally pissed at myself for failing to buy the Firewire cable and get data off of it first, but figured I’d fix it in the morning. (Sigh.) The error message was “journal magic is bad”, followed by “nfs_boot_init failed with 6”. Figuring I’d start over after the fsck and see if that let it boot any farther, I restarted… and found that my fsck had let the HFS volume figure out that the Journal really *was* bad, and that it was no longer going to even mount read only. (Before this, the disk could be mounted read-only, but not read-write.) It seemed to work, for the most part, though it complained of a bad journal, so I couldn’t mount the drive read/write. I figured out how to get into single-user mode (apple-S during startup) and ran an fsck on the disk. The symptom of this that we were able to see, by the way, was that the computer just ‘hung’ at the Apple with the spinning logo under it, because some file was unable to be written to and therefore startup hung waiting for it to come back. Trying to start it up, I found that it was unable to mount the drive read/write.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |