Disk Warrior v 3.0.3 on 10.4.7

I'm booting from the DW CD and trying to rebuild the directory, it goes straight to step 5 and stalls on step 7 - it is taking ages and then I cant quit out without turning the computer off.
Has anybody else had these problems? I cant access the Alsoft Technical Help site, and may receive an email back from the Alsoft Techs in 2 days!!
imac G5 Mac OS X (10.4.7)

It was just the software that I reinstalled. The computer would not boot up at all - it was stuck on a gray screen with the spinning circle like it wasnt able to find the start up disk. As I didnt have the DW update at that point, someone suggested instead of doing a clean install and losing everything just to reload itunes, mail etc. This solved the start up probs but programs are taking a while to load. I just know its not running as smoothly as a normal Mac.
Im sure DW would sort it - maybe part of the problem is causing the Disk Warrior not to work...sorry Im not very technical and using DW is about as good as I get!! lol. DW runs the graph thats telling me nearly two thirds out of order so Im stuck...
Oh - still no reply from Alsoft!

Similar Messages

External Hard drive "not readable", does not show up in Disk Warrior either. Help me, please!

I have a 500gb G Drive Slim that is almost brand new. I accidentally pulled the cord out when it was connected, and now when I try to open it, it says "not readable by this computer." This is what I see when I go into disc utility:
I called G Drive, and they told me to download Disk Warrior 4. I did, and this is what I see when I open it:
My hard drive doesn't show up...i'm not sure if i'm doing something wrong but I just paid $100 dollars for this and I'd really like some help. I read the manual and it wasn't helpful at all.
Please help me!

Make sure it's format is Mac OS Extended (Journeled).
To check it's format, plug in the External HDD and search Disk Utility in the spotlight. Click the External HDD and go to the Partition tab. If it isn't Mac OS Extended change it and format it.
You shouldn't need any of these external applications to use it. I have one and use it like a flash drive.

PhotoShop CC 2014 - Blowing Directories on Hard Drives - Should Ship with a free Version of Disk Warrior ;-)

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.

How do I run Disk Warrior on new MacBook Pros?

I am trying to help my good friend who purchased a Late-2012 Macbook Pro 13-inch Core i5 2.5 GHz. It runs 10.8 ML. WIth reckless technical abandon, she swamped and corrupted her HD directory with repeated massive transfers of large-size photo files in and out of her laptop when the drive was already probably at least 95% full to capacity. She probably experienced repeated Out-of-Memory notifications as she would try to perform these ops while Photoshop was using almost all available free space on the same disk as Scratch Storage for its operations.
Suddenly she could not boot her MBP. She called Apple warranty support, and they convinced her the only thing she could do was to wipe the HD and reinstall the OS. Angry as **** about losing about 3 weeks of critical photo images since her last backup, she dutifully obeyed. She said the wipe operation took only a part of a minute.
So, with that background, I told her I felt the wipe was not a low-level erase at all, but just the most minimal erase procedure possible, and that I thought many of her old files may be recoverable with a tool like DiskWarrior if she did it immediately, before starting to reinstall applications and other content back onto the disk.Can anyone back me up on this?
Now, on to how I can try to do the recovery. She has considered sending the drive out to a "clean room" recovery service, but before doing so at great cost, I wanted to at least try a DiskWarrior directory repair. With no optical drive, she cannot boot from the Disk Warrior 7.X DVD, or create a bootable CD or DVD to run Disc Warrior for the same reason. How else can we force the MBP to allow the hard drive to be read by DiskWarrior? Can I load DW on a FireWire drive and use Thunderbolt-to-FW adapter on MBP to boot from it? Disk Warrior's website still says "The current DiskWarrior DVD cannot start up the new MacBook Pros introduced June 11, 2012. An updated disc that will also start up these recent Mac models will be released as soon as Apple, Inc. releases new startup files to Alsoft, Inc. and other developers." Do I still have to wait for something from Apple? Or can I put the MBP in Target Mode and run DW connected via FireWire (and Thunderbolt adapter) from my own MacBook running OSX Lion? And hopefully repair her directory? Is there hope here?

You'll need to install Windows on your Macbook. This can be done by either using Boot Camp (free, from Apple) or Parallels Desktop for Mac (free trial, $80 retail). Either approach requires that you own an additional copy of Windows (Windows XP sp2 for Boot Camp) which you will then install on your Mac.
In brief, Boot Camp sets up your Mac so you can boot into either OS X or Windows (but not have both running at the same time; you switch via a reboot), and Parallels creates a virtual machine in which you will run Windows while OS X is running. You're correct that you can't run Virtual PC on your Intel-based Mac. Parallels will give you that functionality on your Mac (and be a lot faster than Virtual PC in the process).
You might want to start with Parallels' free trial and see if that meets your needs for these CDs. Parallels doesn't require that you make changes to your partitions on your drive; it just installs an application and creates a virtual disk which to OS X is just another file (albeit a large one), and you don't need to reboot to switch back and forth between Windows and OS X. If it works, you're set.
If you have graphics adapter-intensive Windows applications (e.g., games or something that requires 3D acceleration), you'll be better off with Boot Camp, because the current version of Parallels does not support DirectX or 3D hardware acceleration.
Hopefully that will get you started. There's other info in the Discussions comparing Parallels to Boot Camp, but feel free to ask if you have questions.
Intel Mini 1.66 GHz, Mac Pro 2.66 GHz Mac OS X (10.4.8)
Vista and XP running under Parallels

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?

How do I restore files from External Harddrive - Disk warrior cannot rebuild

Hi Guys
I have a External Hard drive that I can see via Disk Ulitity and shows in finder - but I cannot see the actual files and directories, hence not being able to copy them to a new external hard drive
When I connect the External Harddrive to my Macbook I'm getting the message
"OS X can't repair the disk "Untitled"
You can still open or copy files on the disk, but you can’t save changes to files on the disk. Back up the disk and reformat it as soon as you can."
Disk Utility says I have free space so it is recognising the files. I have Time Machine backups on this external harddrive "Untitled" that I need to critical use.
Basically how do I get the files off this external harddrive before it fully stops working? I have tried rebuilding the disk with Disk Warrior but this does not work.
Thank you anyone! I hope someone can help!

Well, I would skip the Firewire since it isn't essential. Connect the backup drive to your new Retina when it arrives, but before you turn it on for the first time. When you then turn it on you will begin in the Setup Assistant where you will have an opportunity to restore your files from a backup drive or another computer. Select the appropriate option. You can then restore (migrate) your Home folder, third-party applications and support files, and system preferences. Once that is completed when the computer restarts you will be all set up in your old Home folder.
Note that you will be transferring files over a USB connection. Depending upon how much data you are transferring this may take a very long time, so be patient. A USB drive's typical transfer rate is about 12 GBs/hour.

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.

Using Disk Warrior on external drive causes MacBook crash

I work on MacBook System 10.6.7, I back up to LaCie external drive, which I partitioned so that one partition is only for backup, the other is bootable. On this partition I have a clone of Disk Warrior (4.1), to use on the MacBook .
Today I ran DW from the MacBook on the external drive for the first time, because lately it happens that the backup partition does not always appear in the finder (still performs back up though). I applied it first to the boot-partition, and it told me there were some problems. When it got to replacing the directory, the computer crashed mid way.
I performed Disk Verify on that partition through Disk Utility, and it said that it needed repair, and then that it did repair it. Checked other partition, no problem.
Tried again to rebuild directory for the external drive, and both partitions caused the MacBook to crash. I then booted from the external drive to see if it works, and ran DW on the MacBook, and had no problem there.
Anybody can tell me if it is the MacBook that caused the crash, or if the problem is with the external, and if there is anything else I can try to sort it out?
thanks,

I work on MacBook System 10.6.7, I back up to LaCie external drive, which I partitioned so that one partition is only for backup, the other is bootable. On this partition I have a clone of Disk Warrior (4.1), to use on the MacBook .
Today I ran DW from the MacBook on the external drive for the first time, because lately it happens that the backup partition does not always appear in the finder (still performs back up though). I applied it first to the boot-partition, and it told me there were some problems. When it got to replacing the directory, the computer crashed mid way.
I performed Disk Verify on that partition through Disk Utility, and it said that it needed repair, and then that it did repair it. Checked other partition, no problem.
Tried again to rebuild directory for the external drive, and both partitions caused the MacBook to crash. I then booted from the external drive to see if it works, and ran DW on the MacBook, and had no problem there.
Anybody can tell me if it is the MacBook that caused the crash, or if the problem is with the external, and if there is anything else I can try to sort it out?
thanks,

Disk Utility sees problem invisible to Disk Warrior?

Hi all,
In brief: Disk Utility seems to think I've got a big problem, Disk Warrior seems to be unable to fix it.
More detail: I ran verify disk from Disk Utility and was told I needed to repair my startup volume. So I ran Disk Utility's repair disk function from the install CD and it was unable to repair the disk. It was also unable to repair permissions.
So I reached for trusty Disk Warrior and ran that. It rebuilt the directory, reporting various changes, eventually ending with zero errors. That should have fixed it, right?
But then I re-ran Disk Utilty and was told, again, that the disk needed to be repaired.
Here's what happened when I ran DU's repair function from the install CD:
- I selected only the volume containing Mac OS X for repair and Disk Utility reported there's an "invalid leaf record count (it should be 3 instead of 525) and also that '1 HFS volume repaired' but '1 HFS volume could not be repaired'. (I'd selected only my startup volume).
- The verify disk function reports the same
- The repair disk permissions function cannot complete its task. Its error message reads: "Disk Utility internal error: disk utility has lost its connection with the disk management tool and cannot continue. Please quit and relaunch disk utility."
So, I ran Disk Warrior AGAIN (2nd time) and sure enough, it reports that it successfully rebuilt the directory but that the rebuilt version has no changes from the original version (meaning it's ok, right?).
Needless to say, if my startup disk DOES need repair, I want to do something about it. But does it need repair? And if Disk Warrior can't fix it, what can? Could it be that Disk Utility is seeing a problem that's invisible to Disk Warrior?
By the way, I ran DW's manual diagnostic and it said the drive itself was operating normally.
Very grateful if any of you can give me some insight into this.
Jason
Dual G5 2.5Ghz 2GB RAM, Powerbook G4 1.33Ghz, iPod 60GB Mac OS X (10.4.8) 500GB internal HDD

Hi Allan,
Sure thing. Here's the business.
Disk Warrior (v3.0.3)
DW reports that it's successfully rebuilt a new directory each time I run it. I've run it three times now. The first time, there were differences between the original directory and the rebuilt version and it displayed a message coloured red describing this. On the subsequent two occasions, it has displayed a message coloured green and said there are "no changes to the number or contents of the files and folders" in the rebuilt directory.
DW's manual diagnostic reports that the drive itself is "operating normally."
DU
Running DU internally (from the volume that also contains 10.4.9), it can only 'verify', of course. The volume's name is 'G5 hard drive'. The full message is:
Verifying volume “G5 hard drive”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Incorrect number of Extended Attributes
Checking volume bitmap.
Checking volume information.
d.",1)
G5 hard drive
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
Running DU (repair disk) from the install CD (for Powermac G5, OS X 10.3.5) produces the following report:
Repairing disk for "G5 hard drive"
Checking HFS plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierachy
Checking extent attributes file
Invalid leaf record count
(It should be 3 instead of 422)
Repairing volume
The volume G5 hard drive was repaired successfully
Repair attempted on 2 volumes
1 HFS volume repaired
1 HFS volume could not be repaired
So let's say that DW is doing it all right, and the copy of DU on the install CD (10.3.5) is producing an inaccurate result because it doesn't match up with Tiger, I can understand that. But why would the same problem come up with DU run internally from (in the course of the last 24 hours) both 10.4.8 and 10.4.9 (because the problem survived my upgrade)?
On the other hand, Allan, possibly DW isn't the right tool for the job. In that case, do you know what is?
Thanks,
Jason
Dual G5 2.5Ghz 2GB RAM, Powerbook G4 1.33Ghz, iPod 60GB Mac OS X (10.4.9) 500GB internal HDD

Disk Warrior not compatible with OS 10.4.6?

I purchased DiskWarrior (version 3.03) last year and used it once on my old 1.6 GHz iMac with OS 10.3.6.
I now have a 2.1 GHz non-Intel iSight iMac with Mac OS 10.4.6.
I have tried twice to start up from the DiskWarrior CD - the first time, I never got beyond the grey apple and very loud fans whirring; the second time, I got another grey icon (sort of like a traffic sign - a circle with a line through it) along with the spinning wheel. Both times I gave up after 30 minutes and turned the iMac off with the power button.
This is a bit expensive for a one time use. It seems that DiskWarrior is not compatible with OS 10.4.6 and/or the iSight iMac? I checked the Alsoft website - v. 3.03 is the latest version available.

Wow! I think that you will either need to wait until your external drive is free to be erased, or to buy another external drive to be able to do everything you want all at once.
Once you have a free drive, divide it into two partitions, including one that is only about 5GB. Install a bare system using your iMac's Install & Restore Disc 1 onto this small partition. Customize your installation by choosing not to install printer drivers, languages, iLife applications, extra fonts or X11. This installation will be a little over 2GB.
When you first visit this system's Desktop, go to Software Update and install only the 10.4.6 Combined Update, any Java updates and possibly QuickTime 7.0.4. Reboot and repair permissions. Remove everything from the Dock but Safari and System Preferences. Drag Disk Utility into the Dock from your Applications/Utilities/ folder.
Launch Safari, go to shirtpocket.com and download and install the cloning utility, SuperDuper! Drag SuperDuper!'s icon from your Utilities folder to the Dock. Register it if you want the added features, or use the unregistered version to make your clones fresh each time.
Next, insert the Disk Warrior disc (any version of Disk Warrior 3.0.3 will do here) and drag DW to your /Applications/Utilities/ folder. Drag Disk Warrior's icon in your Utilities folder to the Dock.
Now you need only boot into your small maintenance partition to launch Disk Warrior so you can run it on your iMac and/or the clone that is on the external's larger partition. And of course, you'll clone your iMac to the larger partition on your external drive by booting into the smaller partition and running SuperDuper! from there.
Simple!

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.

I tried to install Disk Warrior Electronically, but it won't begin install because I need to uncheck ignore ownership

Disk Warrior has me confused. I currently have OS X 10.6.8. I downloaded Disk Warrior 4 and I'm attempting to install it electronically. First off I don't know what to do next. All explanations of what to do next are so broad-stepped - I don't understand. I have done two things: I have saved a copy of Disk Warrior in a RAM drive that I have created on my desktop. I also have a copy saved on an external hard drive (Slim Seagate). This is what happened when attempting to install a copy of Disk Warrior from RAM drive: Disk Warrior wants me to go into Finder, Get Info, Sharing and Permission, and uncheck the ignore volume ownership block. I unchecked the ignore volume ownership block. SO WHAT NEXT? It's a mystery. Disk Warrior still prompts me to keep doing this process but I already did. What now?
I tried opening from the external Slim Seagate hard drive and it prompts me to do the exact same thing. Only there is no option to uncheck the ignore volume ownership block.
Can anyone explain this step-by-step? If you've got the time, it would be a big help if someone chatted the solution. Please keep answers on-point and concise for everyone's ease of reading and understanding. No doubt, others have had this issue.

Contact Alsoft. They have an excellent support team.
By the way, there is a separate 10.6 forum, and I've asked a moderator move your thread.

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.

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 Warrior Report

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 ﬁles and folders. It is recommended that you preview the replacement directory and examine the items listed below. All ﬁles 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 ﬁle 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 ﬁles and folders for damage and potential compatibility problems.
Disk: "MacIntosh HD" Location: "Desktop"
The Property List data was checked in 10,101 ﬁles.
The Resource Data was checked in 6,340 ﬁles.
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 ﬁle is not UTF-8, or in the encoding speciﬁed 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 ﬁle is not UTF-8, or in the encoding speciﬁed 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 ﬁle format for storing data and is often used to store preferences. The names of these ﬁles normally end with a .plist ﬁle extension. Corrupt property list ﬁles can cause system instability.
Resource Data: This is an older ﬁle format for storing data and was often used to store preferences. The names of these ﬁles normally end with a .rsrc ﬁle extension. Corrupt resource data ﬁles can cause system instability.
Thank You Again,
golden2 Denver

Mr. 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

Disk Warrior v 3.0.3 on 10.4.7

Similar Messages

Maybe you are looking for