Hi Ronni I didn’t read the user Manual and certainly don’t fully understand the DW documentation.
I suggest there is an argument for regular DiskWarrior directory test/rebuilds. The iMac has 5 years of OS X upgrades and accumulated little glitches that may have been detected and repaired before the “catastrophic” failure on Sunday. OS X does pretty well in keeping around 750,000 files in order. What straw broke the camel’s back? Was it a power spike during AirDrop? Is the hard drive just becoming old and unhealthy? Are there “bad sectors” or whatever? End result may not be perfect, but gave me a working computer again. Fortunately it is the “No 2” Mac. I will shift the more valuable files from the internal HD. And leave Time Machine turned off rather than run a 300GB backup before I clean up. I still have full SuperDuper bootable backups Thanks again Ronni, for your help with Disk Warrior and restoration of the near-dead Mac. Cheers Alan On 24 Nov 2014, at 5:18 pm, Ronni Brown <ro...@mac.com> wrote: > Hi Alan, > > I don't think your read the DiskWarrior Manual first before using DW from > what you mentioned below. > > Open DiskWarrior.app - Go to 'Help > DiskWarrior Manual' in the Menu Bar > Then when the Manual opens in Preview - Go to File > Export - & export the > DiskWarrior Manual.pdf to your Desktop. > ----- > > "What to Look for During Preview > > When DiskWarrior presents the “preview disk,” you have the opportunity to > check and test the disk as it will appear after it is rebuilt. You can run > applications, open documents, and see if files and folders that you lost have > been recovered. > > If the original disk was visible on the desktop before you ran DiskWarrior, > DiskWarrior will display both the original disk and the preview disk in the > DiskWarrior Preview Window. Both of these disks will be locked during the > preview, so you will not be able to make any changes to either of them. Both > the original disk and the preview disk will appear within the panes of the > DiskWarrior Preview Window. > > DiskWarrior may create special folders at the root level of the disk. You > should pay particular attention to the files and folders that DiskWarrior > places in these folders. The folder called “Rescued Items” contains files and > folders whose enclosing folder could not be found. If any of these files or > folders are part of a software package, you may need to create enclosing > folders with the correct names and locations after you have rebuilt your disk > so that the software that uses these files works correctly, or you may need > to reinstall the software package. > > If DiskWarrior creates a folder titled “Damaged Items,” then this folder > contains files that were recovered but may have problems. For instance, these > files may have been truncated because blocks were missing from the file, or > the existing directory information may have indicated that two files occupied > the same block. The DiskWarrior Report created after the rebuild is completed > will tell you if two files own the same block (refer to “What to Look for in > the DiskWarrior Report” later in this document). If this is the case, then > DiskWarrior will separate the two files for you after the directory is > replaced. Once the rebuild is complete, you will need to determine which of > these files can be salvaged and which has damaged data. > > At this point in the process, if you discover that there are items missing > from the preview disk, use the Find feature of the Preview Window to search > for invisible items. Make sure the preview disk is the disk selected in the > left pane. > > In the event that critical items that you wish to recover remain missing > during the preview, it is recommended that you do not proceed with the > rebuild. Since the directory information for the items that are missing was > overwritten or deleted at some point previously, DiskWarrior could not > recover these items. You will need to send your disk to a professional > recovery service to recover your lost files. While in preview, you should > copy as many items from your disk as possible to another hard disk, FireWire > disk, USB disk, etc., using the copy feature of the Preview Window. You may > need to copy the original files to several disks, depending upon the amount > and size of the files on the source and the size of the disks to which you > are copying the files. Another option is to copy only the files that you > absolutely need, such as those that have changed since your last backup, or > only your data files if you are planning to reinstall your system and > applications. In either case, it is possible that the Preview Window will not > be able to copy all of the files you select. If the Preview Window displays > such an error, select “Continue” to continue copying the remainder of the > files you selected. When the copy operation is complete, you may want to > attempt to copy the skipped files again in case the error is intermittent and > the copy operation can be performed for those files. This will minimize the > number of items that the recovery service will need to recover for you. > > > What to Look for in the DiskWarrior Report > > After the rebuild has been completed, DiskWarrior will show you a DiskWarrior > Report. When DiskWarrior first displays the DiskWarrior Report, it defaults > to showing you a summary of all the problems found and repaired and > DiskWarrior’s recommendation to you. However, if you wish to see more detail > regarding the problems found and repaired, you can select the Details button > for this information." > > Cheers, > Ronni > > 13-inch MacBook Air (April 2014) > 1.7GHz Dual-Core Intel Core i7, Turbo Boost to 3.3GHz > 8GB 1600MHz LPDDR3 SDRAM > 512GB PCIe-based Flash Storage > > >> On 24 Nov 2014, at 4:35 pm, Alan Smith <sma...@iinet.net.au> wrote: >> >> Hi Ronni >> >> Success! >> >> DiskWarrior.app 4.4 installed OK. Used Target Mode with Firewire to scan >> the 2009 iMac. “Directory” was main area of action. On completion, DW >> asserted that the old and new directories would be on Desktop and the >> proposed changes could be viewed. This did not seem to happen so I accepted >> DW reconstructed directory (what other real choice is there!) but saved the >> log file for “later perusal”. A few exceptions were noted with the “Files” >> test and no problems with “Hardware”. >> >> iMac subsequently started up OK. Some “irregularities” noted for future >> investigation, including no startup Chime; iTunes certificates invalid; >> Dropbox on the menu bar is inactive; Sudoku is “damaged” (but I can download >> that again). >> >> Thanks for your perserverence and help. Disk Warrior certainly fixed things >> that Apple Disk Utility couldn’t. >> >> I’ll send a closing email on the original iMac "failing to start up" thread >> to make things tidy in the WAMUG archives. >> >> Cheers >> Alan >> >> >> On 24 Nov 2014, at 2:30 pm, Ronni Brown <ro...@mac.com> wrote: >> >>> Alan I've sent you an email offlist Let me know if you want me to send the >>> DiskWarrior.app v 4.4 to you please. >>> >>> Ronni >>> > > -- The WA Macintosh User Group Mailing List -- > Archives - <http://www.wamug.org.au/mailinglist/archives.shtml> > Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml> > Settings & Unsubscribe - > <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>
-- The WA Macintosh User Group Mailing List -- Archives - <http://www.wamug.org.au/mailinglist/archives.shtml> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml> Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>
