Disk Warrior hangs in 10.4.7 too
I originally posted this in April, when I was using 10.4.6 - no replies then so I'm hoping someone's found a solution since. I just updated to 10.4.7 but the problem remains unchanged. (Not sure if this should be posted here or in the Powerbook section, since it only happens on the PB.)
Original post:
I've read just about every post relating to Diskwarrior here, but this seems to be a new wrinkle. Recently I took my G4 Powerbook (15" aluminum 1.25 GHz) from 10.3.9 in steps up to 10.4.6. No problems, did all the recommended things (repair permissions before and after each update, etc.). The volume is journaled. No issues with Firewire external drives. Apps seem to run OK.
Today I bought DW 3.0.3 rev 39 thinking that now with Tiger I'd need that revision. (I had been using rev 38 with 10.3.9, no problems.) It boots from the CD fine, but when I run it it hangs up during the final "looking for differences in files/folders" stage. It may get only to 2-300 tests, it may get to 90,000 tests, but then it just hangs. The blue progress bar continues to "ripple" but no further progress happens. If I hit "skip" it'll go to the report, telling me (in red) that some repairs have been made, and that "nnn files will now be accessible."
I hit "cancel", then quit DW to reboot the Powerbook. I can boot from the OS X install DVD and run Disk Utility to verify the hard drive as OK, and to repair permissions (one more time). According to DU, everything's fine - and the 'book does appear to run normally. It's just that DW always hangs at that last stage.
Someone suggested that even if I skip the remainder of the DW process I can go ahead and replace the rebuilt directory. I've done that a couple of times but it leaves me with a very hinkety feeling.
Thanks in advance for any help!
For everyone's info, I got a reply in another thread on this problem and am paraphrasing it here: The suggestion was to go back to DW 3.0.3 rev 38 for the Powerbook, rather than rev 39. The difference between the revisions apparently has only to do with allowing the CD to boot newer hardware, and the actual DW software is the same. I did not know - or forgot if I did read it somewhere - that it's the boot issues that are changed, and not the actual DW-function software. Luckily I'm a packrat so I still had my 3.0.3 rev 38 CD available and when I booted from it on the Powerbook, all the tests, etc. ran fine.
Similar Messages
-
I originally posted this in the Tiger section in April, when I was using 10.4.6 - no replies then so I'm hoping someone's found a solution since. I just updated to 10.4.7 but the problem remains unchanged. It only seems to be an issue on the Powerbook; Powermac desktops running Tiger have no problems running the complete Disk Warrior routine.
Original post:
I've read just about every post relating to Diskwarrior here, but this seems to be a new wrinkle. Recently I took my G4 Powerbook (15" aluminum 1.25 GHz) from 10.3.9 in steps up to 10.4.6. No problems, did all the recommended things (repair permissions before and after each update, etc.). The volume is journaled. No issues with Firewire external drives. Apps seem to run OK.
Today I bought DW 3.0.3 rev 39 thinking that now with Tiger I'd need that revision. (I had been using rev 38 with 10.3.9, no problems.) It boots from the CD fine, but when I run it it hangs up during the final "looking for differences in files/folders" stage. It may get only to 2-300 tests, it may get to 90,000 tests, but then it just hangs. The blue progress bar continues to "ripple" but no further progress happens. If I hit "skip" it'll go to the report, telling me (in red) that some repairs have been made, and that "nnn files will now be accessible."
I hit "cancel", then quit DW to reboot the Powerbook. I can boot from the OS X install DVD and run Disk Utility to verify the hard drive as OK, and to repair permissions (one more time). According to DU, everything's fine - and the 'book does appear to run normally. It's just that DW always hangs at that last stage.
Someone suggested that even if I skip the remainder of the DW process I can go ahead and replace the rebuilt directory. I've done that a couple of times but it leaves me with a very hinkety feeling.
Thanks in advance for any help!If you have DW v3.0.3 Revision 38 (and not DW 3.0.2 in any revision because 3.0.2 was for OS X 10.3.x), you can use that on your machine. You can use v3.0.3 on any version of OS X from 10.2.1 to 10.4.x.
Alsoft updates DiskWarrior for the sake of new hardware that is released with updated Boot ROMs. The new revisions are created so that they will be able to boot the new machines. The software itself is the same.
For example, I use the original 3.0.3 version of DW on my G5 iMac, but since the DW disc won't boot the iMac, I use a version that's installed on a boot volume I keep on an external for the purpose of maintenance.
Good luck! -
FYI: New version of Disk Warrior seems to hang when run with Snow Leopard
FYI: It seems that the new version of Disk Warrior hangs when run in Snow Leopard
I have been using DW 4.2 on 10.5.8 and the speed-up was the first thing I noted, too, so it isn't just SL.
Now if it would only 'come up for air' and respond to input to move window (so I can put it where I can see it if needed) I'd like that.
There is a 23 page review of Snow Leopard on Ars. On page 22:
People sometimes ask what, exactly, is wrong with HFS+.
Aside from its obvious lack of the features just listed, HFS+ is limited in many ways by its dated design, which is based on HFS, *a twenty-five year-old file system.*
To give just one example, the centrally located Catalog File, which must be updated for each change to the file system's structure, is a frequent and inevitable source of contention. Modern file systems usually spread their metadata around, both for robustness (multiple copies are often kept in separate locations on the disk) and to allow for better concurrency.
Practically speaking, think about those times when you run Disk Utility on an HFS+ volume and it finds (and hopefully repairs) a bunch of errors. *That's bad, okay?* +*That's something that should not happen*+ with a modern, thoroughly checksummed, always-consistent-on-disk file system unless there are hardware problems (and a ZFS storage pool can actually deal with that as well). And yet it happens all the time with HFS+ disks in Mac OS X when various bits of metadata to get corrupted or become out of date.
Apple gets by year after year, tacking new features onto HFS+ with duct tape and a prayer, but at a certain point there simply has to be a successor—whether it's ZFS, a home-grown Apple file system, or something else entirely. My fingers are crossed for Mac OS X 10.7.
If Disk Utility was reliable in mapping out weak sectors (it is not) and report/log errors. But it doesn't and I trust my data to other file systems when possible. We've come to expect and depend on 3rd party utilities and that Apple First Aid doesn't fix every possible error.
Scanning one drive for errors can take a long time. Maybe it needs to be done, maybe in the background. With 2TB drives it gets worse. Spending hours to scan for errors??? I've set TechTool Pro to concurrently scan anywhere from one to a dozen volumes at once.
An ounce of prevention, as they say, is worth a pound of cure. -
Disk Warrior/Disk Utility Hangs with External HD
okay, so i will try to make this as quick as possible.
last year, i had an external hard drive that i had been saving all my audio work on. one day i had to restart (i was having a lot of problems with my then IBook G4) so i did, and the drive was no where to be found. made sure there was no connection problems (ie my USB ports) and everything seemed fine. let it sit for a while, thinking maybe it was just tired or something. tried again, same story, and it also made disk utility hang. tried it on a friends mac, same issue.
i also had a a lot of video/music that i watched with my xbox 360. i could still access those files with the xbox, which was weird.
so then my ibook eventually died, and here i am with a newer G5 quad. i tried it again, and still the disk utility hangs, and ive also tried Disk warrior 4. this also hangs.
also, i have tried switching the enclosure to no avail.
its not the end of the world if i cant get the data back, but i would REALLY like to.
any suggestions?System Profiler shows the same thing: "Manufacturer: PI-236" for each of these HDs. I'm not sure how to rename these drives (I'm not talking about the partitions on them, which I've given descriptive names).
The strange thing is that on my MacBook Air (upgraded to Lion) one of these HDs (now connected via USB) shows up in Disk Utility as "Ext Hard Disk Media" instead of "PI-236". Still not a whole lot of information, you'll notice.
Another external HD (partitioned earlier under Snow Leopard) is shown correctly as "SAMSUNG HD501LJ Media" on both computers. -
Disk utility hanging/ not responding.
so i've been having some drive issues recently. one of the manifestations of this is while trying to open Disk Utility to repair permissions, verify disk, etc. it hangs as soon as the superdrive makes it's noise. it's usually fixed by a restart, but invariably happens again. it's usually coupled by some other funkiness when accessing a disk internal or external (ex. reconnecting media in FCP or choosing system settings in FCP)
i have had slight quirks from the super drive. it wont read blank CDs or DVD-DL. DVDs and blank DVDs have been fine, CDs with media on them have been fine too.
as far as disk maintenance, i recently reformatted my startup disk and reinstalled SL and restored from a back up. have run disk warrior, repaired the disk from SL install disk and permission repairs.
any help appreciatedHI,
Go to ~/Library/Preferences then move the com.apple.DiskUtility.plist file to the Trash.
~ (Tilde) represents your Home Folder.
Then restart your Mac.
Carolyn -
Since installing PS CC 2014 I have had serious problems.
Problems one could expect from a 'new' software.
However, having my drives' directories damaged due to Scratch Disks is something I have never seen before.
I had PS use an SSD as Scratch Disk. As this became full, I assigned another scratch disk (This time a RAID0).
As it ran full (200GB of PS Scratch) All the other files on that drive vanished. And photoshop was no longer able to even save the current document
(event though the destination had enough space avail.) See screenshot:(Watch the finder status in the back, the doc to be saved was 200MB and my disk had 3.38 GB avail.
But PS would not let me save due to scratch disks full)
Anyway, back to the serious problem. The RAID0 scratch disk, after I quit PS, was not longer mountable.
Trying to repair it with DU reported:
And trying with terminal This:
** /dev/rdisk13
Executing fsck_hfs (version hfs-226.1.1).
** Checking Journaled HFS Plus volume.
** Checking extents overflow file.
** Checking catalog file.
** Rebuilding catalog B-tree.
CreateNewBTree returned -34
Disk full error
So I went ahead and did some research and found Disk Warrior.
It was able to rebuild my catalog and I am up an running again.
But having to spend $99 on a PS bug is not so nice. I have been able to recreate this problem 3 times the past hours.
The problem occurs only when PS is using the RAID as Scratch disk. If I try to fill the drive by writing to it via terminal or Finder,
i just get a Disk is Full. PS on the other hand will blow the catalog and make the disk unmountable...
Any Ideas ?Thanks for your reply, Chris Cox. I've checked the Windows System Event Log and here are the details:
Details (Tab) of same error (Photoshop)
I noticed since Jan 5, 2015, Photoshop has crashed a lot. I run Adobe Illustrator with it but it doesn't give the same errors. Other applications run fine too, so I'm not sure if it as you mentioned that it is the "system" that is crashing so often.
(You seem to have suggested a video card upgrade. I will work on that next. Thanks)
I hope you or anyone who can, help me with this problem with Photoshop and the issue with my account in Creative Cloud.
Looking forward to your help. Thank you. -
Running a G5 IMac with 10.5.1. Tried to repair permissions and Disk Utility hangs up at about 25% of the way through the process. Ran Disk Warrior. Still hangs up. Started up form Leopard Install and tried to repair permissions. Still hangs up. Otherwise the system seems to be running OK. Any help or thoughts would be appreciated.
Disk Warrior is NOT compatible with Leopard at this time.
I would not use my Disk Warrior.
Permissions take from 10 to 30 minutes with 10.5.1
Give it time.
It seems like it just sits there on "Less than 1 minute" but it will eventually finish.
Again, give it time. -
Disk Warrior 3.0.3 on OSX 10.6.8?
I'm having major problems with my iMac (2.4 Ghz Intel Core 2 Duo/2 GB 66 MHz DDR2 SDRAM/running OSX version 10.6.8). Very, very slow to login, hangs up during normal use, slows to a crawl, etc. I did some searching on this forum and have tried some suggestions offerred to people with similar problems, such as running Disk Utility. When I ran it off the hard drive it went through the process with no real error messages (found a few "damaged files" and put them in folder named the same). Then I tried running it off my Snow Leopard install disk and got the message:
Disk Utility stopped repairing "Macintosh HD" Disk Utility can't repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
Next on my list, before going so far as reformatting/restoring (I use Time Machine to back up my system onto a 500 GB external hard drive) I want to run Disk Warrior. Here at the office we have a very old version (3.0.3). Will it work with Snow Leopard? I popped the disk into a Mac running Lion and it had the slash through the icon, indicating that it isn't compatible. However, I popped it into my work iMac, which is running the same OS as my problem iMac at home, and it looks as though it may work.
Obviously the most recent version would be ideal but will this one at least run for me? If it will I think I'll give it a shot. If it doesn't work I'll look into getting an upgrade. Anyone know?
One other thing...never could locate the S.M.A.R.T. info in my Disk Utility. Saw that mentioned several times in posts but it doesn't appear on my version. I did download an app called SMARTReporter and ran that. All indications were that my hard drive is OK.I'm unclear what you did after re-reading your original post. Did you do this:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard 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 Utilities menu. 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 click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X. -
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?
ThanksR 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 -
Kappy was helping me with my MBP problem with my MacIntosh HD. He recommended, as did others to get the Disk Warrior which I did. I ran it a couple of times last night after I talked with Apple Care support on line-he couldn't figure out what was wrong. I am asking for someone to review this, in particular the File errors down below and give me an interpretation.
I appreciate your help.
Time: 12/7/08 2:17:32 PM DiskWarrior Version: 4.1
DiskWarrior has successfully built a new optimized directory for the disk named "MacIntosh HD." The new directory is ready to replace the original directory.
Notes: All file and folder data was easily located.
Comparison of the original and replacement directories indicates that there will be changes to the number, the contents and/or the attributes of the files and folders. It is recommended that you preview the replacement directory and examine the items listed below. All files and folders were compared and a total of 13,919,576 comparison tests were performed.
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.
File: "日本語.html"
Repaired Text Encoding Location: "MacIntosh HD/Applications/Adobe Bridge/Legal.localized/"
Explanations: Text Encoding: File and folder names are stored in Unicode characters. The text encoding value indicates the method used to convert the file name to Unicode. Repairs prevent the name from being displayed incorrectly.
Disk Information:
Files: 510,953
Folders: 135,461
Free Space: 79.31 GB
Format: Mac OS Extended (Journaled)
Block Size: 4 K
Disk Sectors: 311,909,984
Media: FUJITSU MHW2160BHPL
Time: 12/7/08 8:29:49 PM DiskWarrior Version: 4.1 DiskWarrior scanned the disk named "MacIntosh HD" checking all files and folders for damage and potential compatibility problems.
Disk: "MacIntosh HD" Location: "Desktop"
The Property List data was checked in 10,101 files.
The Resource Data was checked in 6,340 files.
The maximum Folder Depth on this disk is 21. This does not exceed the maximum recommended depth.
File: ".cdc.mk4e.plist" Detected that Property List data is damaged and cannot be repaired.
XML parser error: Unexpected character at line 1
Old-style plist parser error: Unexpected character '0x4' at line 1 Location: "MacIntosh HD/Users/goldenmr2w/Library/Preferences/"
File: "com.apple.scheduler7098.plist" Detected that Property List data is damaged and cannot be repaired. Conversion of data failed. The file is not UTF-8, or in the encoding specified in XML header if XML. Location: "MacIntosh HD/Users/goldenmr2w/Library/Preferences/"
File: "com.apple.iphotomosaic.plist" Detected that Property List data is damaged and cannot be repaired. Conversion of data failed. The file is not UTF-8, or in the encoding specified in XML header if XML. Location: "MacIntosh HD/Users/goldenmr2w/Library/Preferences/"
Explanations Folder Depth: This number indicates how many folders are nested inside each other. If a disk contains only three folders and Folder A is inside Folder B and Folder B is inside Folder C, then this disk has a maximum folder depth of three. Folders nested too deeply can cause software compatibility problems.
Property List: This is a standard file format for storing data and is often used to store preferences. The names of these files normally end with a .plist file extension. Corrupt property list files can cause system instability.
Resource Data: This is an older file format for storing data and was often used to store preferences. The names of these files normally end with a .rsrc file extension. Corrupt resource data files can cause system instability.
Thank You Again,
golden2 DenverMr. Kappy-I did not see your name on board, and thank you so much.
I just ran a repair disk permissions and got:
Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
which is a whole lot better than all the stuff I was getting yesterday before Disk Warrior.
So maybe that is why the Apple Care person could not find anything wrong.
Okay, I really promise this time not to touch anything I am not supposed to.
May I ask one thing-do you recommend downloading Disk Warrior and have it run routine maintenance as well? And it is okay if I can figure that our for myself, too.
I appreciate your very understandable explanations and recommendations.
golden2 Denver -
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 -
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.
- robertHi, 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 -
'Invalid node structure', 'Invalid B-tree node size', Disk Warrior useless
Hi everyone, I am getting sick of this, it's the second time it's happened to me in a relatively short space of time, the first time with an Iomega external 500GB drive, this time with a 1.5TB Western Digital.
I gave the Western Digital drive two partitions, (as I did for the previous Iomega drive), one for doing backups of my MacBooks internal drive, the other for random media, mostly VIDEO_TS folders.
After going away for a couple of weeks, I returned home, plugged in the Western Digital drive via USB, the Internal backup partition showed in Finder, the other did not. Obviously I ran Disk Utility which was only able to show an error report with the usual 'Invalid node structure etc' message.
I tried running Disk Warrior 4.2 (supposedly the version which works with Snow Leopard) from the DVD, (holding down the C key after restart), and..... nothing, just the grey screen and spinning wheel showing, so I gave up on that and installed DW to the Utilities folder. Now it starts up, the corrupt drive showed up, I hit the Rebuild button in DW, things seemed to be happening, but then the Beach Ball appeared and there was a (very) long hang before I decided to Force Quit.
I am assuming that if DW can not fix the drive, it is done for, and may as well be used as a door stop.
I am prepared to buy yet another drive, but can someone please give me an idea about why this has happened to me twice now, and what I can do to prevent it from happening again?Just erase the partition. Nothing yet suggests the drive is bad. When you got the drive did you prep it correctly? Usually bare drives are pre-formatted for Windows. You might consider doing this:
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to two and size them as you prefer. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Repeat Steps 4-6 for the other partition. Alternatively, you can start with a single volume. After the zero data erase you can then re-partition the drive. -
Disk Warrior - Anyone feeling clever??
Ran Disk Warrior and just as it was about to save its report it crashed and dumped. Strange thing is, I had FastDVDCopy do the same thing when trying to burn a DVD too. Can anyone decipher the dump below :- I think it crashed trying to set an RGB colour, but surely not??!
Thanks in Advance.
Date/Time: 2006-10-26 18:25:40.856 +0100
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: DiskWarrior
Path: /Applications/Utilities/DiskWarrior.app/Contents/MacOS/DiskWarrior
Parent: WindowServer [65]
Version: 3.0.3 (3.0.3)
PID: 292
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000017
Thread 0 Crashed:
0 com.apple.QD 0x917515dc SetPortRGBForeColor + 48
1 com.apple.QD 0x91757658 RGBForeColor + 48
2 com.apple.QuickTime 0x947ed898 TaskMovie_priv + 3016
3 com.apple.QuickTime 0x948aea94 frequentlyTaskMovies + 228
4 com.apple.CoreFoundation 0x907f0550 __CFRunLoopDoTimer + 184
5 com.apple.CoreFoundation 0x907dcec8 __CFRunLoopRun + 1680
6 com.apple.CoreFoundation 0x907dc47c CFRunLoopRunSpecific + 268
7 com.alsoft.diskwarrior 0x0000882c 0x1000 + 30764
8 com.alsoft.diskwarrior 0x0000e344 0x1000 + 54084
9 com.alsoft.diskwarrior 0x0000e130 0x1000 + 53552
10 com.apple.CoreFoundation 0x907f0550 __CFRunLoopDoTimer + 184
11 com.apple.CoreFoundation 0x907dcec8 __CFRunLoopRun + 1680
12 com.apple.CoreFoundation 0x907dc47c CFRunLoopRunSpecific + 268
13 com.apple.HIToolbox 0x93208740 RunCurrentEventLoopInMode + 264
14 com.apple.HIToolbox 0x932ecd40 GetNextEventMatchingMask + 116
15 com.apple.HIToolbox 0x9330fa58 EventAvail + 92
16 com.alsoft.diskwarrior 0x0000e240 0x1000 + 53824
17 com.alsoft.diskwarrior 0x0000dec4 0x1000 + 52932
18 com.alsoft.diskwarrior 0x0000de7c 0x1000 + 52860
19 com.alsoft.diskwarrior 0x0000de34 0x1000 + 52788
20 com.alsoft.diskwarrior 0x00002dc8 0x1000 + 7624
21 com.alsoft.diskwarrior 0x00002ab4 0x1000 + 6836
22 com.alsoft.diskwarrior 0x00002934 0x1000 + 6452
Thread 1:
0 libSystem.B.dylib 0x90054ae8 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90071168 pthreadcond_timedwait_relativenp + 556
2 ...ple.CoreServices.CarbonCore 0x90bf5500 TSWaitOnSemaphoreCommon + 176
3 ...ickTimeComponents.component 0x997947c4 ReadSchedulerThreadEntryPoint + 5300
4 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 2:
0 libSystem.B.dylib 0x90054ae8 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90071168 pthreadcond_timedwait_relativenp + 556
2 ...ple.CoreServices.CarbonCore 0x90bf5500 TSWaitOnSemaphoreCommon + 176
3 ...ple.CoreServices.CarbonCore 0x90bfffa8 AIOFileThread(void*) + 520
4 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 3:
0 libSystem.B.dylib 0x9000ab48 machmsgtrap + 8
1 libSystem.B.dylib 0x9000aa9c mach_msg + 60
2 com.apple.CoreFoundation 0x907dcb78 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x907dc47c CFRunLoopRunSpecific + 268
4 com.apple.audio.CoreAudio 0x9145463c HALRunLoop::OwnThread(void*) + 264
5 com.apple.audio.CoreAudio 0x914543dc CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 4:
0 libSystem.B.dylib 0x90054ae8 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90071168 pthreadcond_timedwait_relativenp + 556
2 com.apple.audio.CoreAudio 0x91465794 CAGuard::WaitFor(unsigned long long) + 204
3 com.apple.audio.CoreAudio 0x914656a4 CAGuard::WaitUntil(unsigned long long) + 304
4 com.apple.audio.CoreAudio 0x914638e8 HP_IOThread::WorkLoop() + 852
5 com.apple.audio.CoreAudio 0x91463580 HPIOThread::ThreadEntry(HPIOThread*) + 16
6 com.apple.audio.CoreAudio 0x914543dc CAPThread::Entry(CAPThread*) + 96
7 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 5:
0 libSystem.B.dylib 0x9002bcb8 semaphorewaittrap + 8
1 ...ickTimeComponents.component 0x99cda274 QTThreadWaitSignal + 100
2 ...ickTimeComponents.component 0x998142dc audioprepThreadEntry + 76
3 ...ickTimeComponents.component 0x99cd9f34 start_thread + 84
4 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 0 crashed with PPC Thread State 64:
srr0: 0x00000000917515dc srr1: 0x100000000000f030 vrsave: 0x0000000000000000
cr: 0x22442244 xer: 0x0000000000000000 lr: 0x0000000091757658 ctr: 0x0000000090b8d9d0
r0: 0x0000000091757658 r1: 0x00000000bfffea10 r2: 0x00000000ffffffff r3: 0x0000000015af1680
r4: 0x00000000000eb108 r5: 0x00000000bfffeb54 r6: 0x0000000000000001 r7: 0x0000000000002000
r8: 0xffffffffd0900000 r9: 0x00000000bfffea50 r10: 0x00000000000f4240 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
r16: 0x0000000000000001 r17: 0x000000000000017a r18: 0x0000000000000000 r19: 0x0000000000000410
r20: 0x0000000000000000 r21: 0x00000000002fa8dc r22: 0x0000000015af1680 r23: 0x00000000002fa884
r24: 0x0000000000304760 r25: 0x0000000020000000 r26: 0x0000000000000001 r27: 0x0000000000000400
r28: 0x0000000001885c00 r29: 0x00000000bfffeb54 r30: 0x0000000015af1680 r31: 0x00000000947ecce8
Binary Images Description:
0x1000 - 0xd3fff com.alsoft.diskwarrior 3.0.3 /Applications/Utilities/DiskWarrior.app/Contents/MacOS/DiskWarrior
0x159f2000 - 0x159f3fff com.apple.aoa.halplugin 2.5.6 (2.5.6b5) /System/Library/Extensions/IOAudioFamily.kext/Contents/PlugIns/AOAHALPlugin.bun dle/Contents/MacOS/AOAHALPlugin
0x15f15000 - 0x15f3ffff com.apple.iSightAudio 7.1.3 /Library/Audio/Plug-Ins/HAL/iSightAudio.plugin/Contents/MacOS/iSightAudio
0x1b205000 - 0x1b2e1fff com.divxnetworks.DivXCodec 5.1.1 /Library/QuickTime/DivX 5.component/Contents/MacOS/DivX 5
0x1b326000 - 0x1b35ffff com.apple.audio.SoundManager.Components 3.9.1 /System/Library/Components/SoundManagerComponents.component/Contents/MacOS/Soun dManagerComponents
0x1b365000 - 0x1b3a4fff com.apple.QuickTimeFireWireDV.component 7.1.3 /System/Library/QuickTime/QuickTimeFireWireDV.component/Contents/MacOS/QuickTim eFireWireDV
0x70000000 - 0x700fcfff com.apple.audio.units.Components 1.4.3 /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
0x8fe00000 - 0x8fe51fff dyld 45.3 /usr/lib/dyld
0x90000000 - 0x901bcfff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x90214000 - 0x90219fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x9021b000 - 0x90268fff com.apple.CoreText 1.0.2 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
0x90293000 - 0x90344fff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x90373000 - 0x9072dfff com.apple.CoreGraphics 1.258.38 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x907ba000 - 0x90893fff com.apple.CoreFoundation 6.4.6 (368.27) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x908dc000 - 0x908dcfff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x908de000 - 0x909e0fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
0x90a3a000 - 0x90abefff libobjc.A.dylib /usr/lib/libobjc.A.dylib
0x90ae8000 - 0x90b58fff com.apple.framework.IOKit 1.4 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90b6e000 - 0x90b80fff libauto.dylib /usr/lib/libauto.dylib
0x90b87000 - 0x90e5efff com.apple.CoreServices.CarbonCore 681.7 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x90ec4000 - 0x90f44fff com.apple.CoreServices.OSServices 4.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x90f8e000 - 0x90fcffff com.apple.CFNetwork 129.18 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x90fe4000 - 0x90ffcfff com.apple.WebServices 1.1.2 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore
0x9100c000 - 0x9108dfff com.apple.SearchKit 1.0.5 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x910d3000 - 0x910fdfff com.apple.Metadata 10.4.4 (121.36) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x9110e000 - 0x9111cfff libz.1.dylib /usr/lib/libz.1.dylib
0x9111f000 - 0x912dafff com.apple.security 4.5 (28992) /System/Library/Frameworks/Security.framework/Versions/A/Security
0x913d8000 - 0x913e1fff com.apple.DiskArbitration 2.1 /System/Library/PrivateFrameworks/DiskArbitration.framework/Versions/A/DiskArbi tration
0x913e8000 - 0x91410fff com.apple.SystemConfiguration 1.8.3 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x91423000 - 0x9142efff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
0x91433000 - 0x9143bfff libbsm.dylib /usr/lib/libbsm.dylib
0x9143f000 - 0x914bafff com.apple.audio.CoreAudio 3.0.4 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x914f7000 - 0x914f7fff com.apple.ApplicationServices 10.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x914f9000 - 0x91531fff com.apple.AE 1.5 (297) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE
0x9154c000 - 0x91619fff com.apple.ColorSync 4.4.4 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x9166e000 - 0x916fffff com.apple.print.framework.PrintCore 4.6 (177.13) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0x91746000 - 0x917fdfff com.apple.QD 3.10.21 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x9183a000 - 0x91898fff com.apple.HIServices 1.5.3 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x918c7000 - 0x918ebfff com.apple.LangAnalysis 1.6.1 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x918ff000 - 0x91924fff com.apple.FindByContent 1.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent
0x91937000 - 0x91979fff com.apple.LaunchServices 181 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
0x91995000 - 0x919a9fff com.apple.speech.synthesis.framework 3.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x919b7000 - 0x919f9fff com.apple.ImageIO.framework 1.5.0 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
0x91a0f000 - 0x91ad7fff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
0x91b25000 - 0x91b3afff libcups.2.dylib /usr/lib/libcups.2.dylib
0x91b3f000 - 0x91b5dfff libJPEG.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x91b63000 - 0x91bd2fff libJP2.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x91be9000 - 0x91bedfff libGIF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x91bef000 - 0x91c4efff libRaw.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRaw.dylib
0x91c53000 - 0x91c90fff libTIFF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x91c97000 - 0x91cb0fff libPng.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
0x91cb5000 - 0x91cb8fff libRadiance.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x91cba000 - 0x91cbafff com.apple.Accelerate 1.2.2 (Accelerate 1.2.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x91cbc000 - 0x91da1fff com.apple.vImage 2.4 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x91da9000 - 0x91dc8fff com.apple.Accelerate.vecLib 3.2.2 (vecLib 3.2.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
0x91e34000 - 0x91ea2fff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x91ead000 - 0x91f42fff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x91f5c000 - 0x924e4fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x92517000 - 0x92842fff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x92872000 - 0x928fafff com.apple.DesktopServices 1.3.4 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x9293b000 - 0x92b66fff com.apple.Foundation 6.4.6 (567.27) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x92c84000 - 0x92d62fff libxml2.2.dylib /usr/lib/libxml2.2.dylib
0x92d82000 - 0x92e70fff libiconv.2.dylib /usr/lib/libiconv.2.dylib
0x92e82000 - 0x92ea0fff libGL.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x92eab000 - 0x92f05fff libGLU.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x92f23000 - 0x92f23fff com.apple.Carbon 10.4 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x92f25000 - 0x92f39fff com.apple.ImageCapture 3.0 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x92f51000 - 0x92f61fff com.apple.speech.recognition.framework 3.4 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x92f6d000 - 0x92f82fff com.apple.securityhi 2.0 (203) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x92f94000 - 0x9301bfff com.apple.ink.framework 101.2 (69) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x9302f000 - 0x9303afff com.apple.help 1.0.3 (32) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x93044000 - 0x93071fff com.apple.openscripting 1.2.5 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x9308b000 - 0x9309bfff com.apple.print.framework.Print 5.0 (190.1) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x930a7000 - 0x9310dfff com.apple.htmlrendering 1.1.2 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
0x9313e000 - 0x9318dfff com.apple.NavigationServices 3.4.4 (3.4.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
0x931bb000 - 0x931d8fff com.apple.audio.SoundManager 3.9 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
0x931ea000 - 0x931f7fff com.apple.CommonPanels 1.2.2 (73) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x93200000 - 0x9350dfff com.apple.HIToolbox 1.4.8 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x9365c000 - 0x93668fff com.apple.opengl 1.4.7 /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x93700000 - 0x93720fff libmx.A.dylib /usr/lib/libmx.A.dylib
0x94191000 - 0x94254fff com.apple.audio.toolbox.AudioToolbox 1.4.3 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x942a6000 - 0x942a6fff com.apple.audio.units.AudioUnit 1.4 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x942a8000 - 0x9447bfff com.apple.QuartzCore 1.4.9 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x94516000 - 0x94566fff libGLImage.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
0x9470a000 - 0x94719fff libCGATS.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x94721000 - 0x9472dfff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x94773000 - 0x9478bfff libRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x94792000 - 0x94a61fff com.apple.QuickTime 7.1.3 /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
0x94b24000 - 0x94b95fff libstdc++.6.dylib /usr/lib/libstdc++.6.dylib
0x9745a000 - 0x97479fff com.apple.vecLib 3.2.2 (vecLib 3.2.2) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x97c7f000 - 0x97c8cfff com.apple.agl 2.5.6 (AGL-2.5.6) /System/Library/Frameworks/AGL.framework/Versions/A/AGL
0x9977d000 - 0x9a134fff com.apple.QuickTimeComponents.component 7.1.3 /System/Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTim eComponents
Power Mac G5 2.0DP/2.5Gb/320GB HD/iSight/iPod MacBook 2.0 Mac OS X (10.4.8)Oh yes, almost for certain, any open file, which there are hundreds to thousands at a time in or silly OSX/Disk Based OS... & 2, 3, 4 times in a row without repairing the HD can be catastrophic sometimes.
Either use DW, DU or install & Use Applejack with a boot into Single User Mode each time it happens if you don't like more trouble than a Cat trying to coverup you know what on a Marble Floor!
For emergency purposes, though DW is a little to a lot better, 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 5 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 UPS so the system doesn't shut down in the middle of the process. -
Disk Utility Hangs When Creating a New Partition
Hello,
I recently purchased a Late 2005 Power Mac G5. My problem is, that the hard drive is 250 MB and only one partition appears in the disk utility of 37 GB. I try to add a new partition, but it hangs on "modifying partition map". Any Help?
Additional info -
Main Disk
Name : WDC WD2500JD-41HBC0
Type : Disk
Partition Map Scheme : Apple Partition Map
Disk Identifier : disk0
Media Name : WDC WD2500JD-41HBC0 WDC WD2500JD-41HBC0
Media Type : Generic
Connection Bus : Serial ATA
Connection ID : Device 0, "A (upper)"
Device Tree : first-boot/@0:0
Bay : "A (upper)"
Writable : Yes
Ejectable : No
Mac OS 9 Drivers Installed : No
Location : Internal
Total Capacity : 232.9 GB (250,059,350,016 Bytes)
S.M.A.R.T. Status : Verified
Disk Number : 0
Partition Number : 0
Partition -
Name : Mac OSX 10.5
Type : Volume
Disk Identifier : disk0s3
Mount Point : /
File System : Mac OS Extended (Journaled)
Connection Bus : ATA
Device Tree : first-boot/@0:3
Writable : Yes
Universal Unique Identifier : 989D8CCE-3C5D-3ECC-9A12-C025D2DF23F2
Capacity : 37.1 GB (39,873,503,232 Bytes)
Free Space : 24.5 GB (26,274,824,192 Bytes)
Used : 12.7 GB (13,598,679,040 Bytes)
Number of Files : 484,775
Number of Folders : 110,579
Owners Enabled : Yes
Can Turn Owners Off : Yes
Can Repair Permissions : Yes
Can Be Verified : Yes
Can Be Repaired : Yes
Can Be Formatted : Yes
Bootable : Yes
Supports Journaling : Yes
Journaled : Yes
Disk Number : 0
Partition Number : 3
ThanksHave you tried doing this first:
Repair 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 Utilities menu. 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 click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
If there are no errors reported then try the routine I suggested rather than trying to expand the existing partition just try to Add a second partition as you have tried before.
If this still gets you nowhere, then I'm afraid you're left with having to repartition from scratch. You'll want to backup the existing files if you don't wish to lose them. I would then do this:
Drive Preparation
1. 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 Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
When the above is completed quit DU and return to the installer. Complete the OS X installation.
Maybe you are looking for
-
This is a stupid question but I needed to ask because I don't want to go there and not being able to buy it, but can I get the iPhone 5 brought straight there when I go to an apple store?
-
Music writing program similar to MusicMaker
Years ago when I had my 512k Mac I used a program called MusicMaker (I think). Easy to use, no manual required, it would play written music in up to four parts, and print it on my imagewriter. I thought it was a wonderful program. So much so that I t
-
First, I apologise if this has been asked before - there just were too many pages to search! I accidentally deleted Applications from my Dock. How do I put it back?
-
My FaceTime crashes every time i open it
why overtime i open FaceTime on my iMac it crashes it comes up with loads of waffle like below!!!!!!!!!!!!!! rashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000
-
Installing photoshop on new computer
I have purchased a new computer with Windows 8 and wish to install my copy of my Photoshop Extended CS6 onto it. Can I do this or do I have to get permission from your company to perform this operation. My customer identification number from a prev