Tag Archive for 'diskwarrior'

19
Dec

The continuing PowerBook saga

It’s been over a month since I wrote anything about the boot failure issues on my PowerBook. It hasn’t been for lack of material; rather, no single issue has warranted a post of its own. But looking back, I now have a month of experiences (mostly bad) to relate.

DiskWarrior wasn’t able to recover my disk. I tried DataRescue, and it seemed to work. (More details below.) I was hoping to wait until I verified DataRescue’s performance before I wrote about it, but I haven’t been able to restore my data yet. Why? Well…

We purchased 3-year warranties when we bought our PowerBooks. Some time during the first year, you have to fill out the AppleCare warranty registration. I did this, but I made a mistake on the paperwork. They claim to have notified me of this, and I have to give them the benefit of the doubt. (My desk is buried under about 3 feet of crap, which could easily be hiding the notification letter.) So now, since my PowerBook died after the first year, I had to jump through several hoops to get my additional two-year warranty activated. This took about 1.5 weeks to get straightened out.

While I was waiting for my AppleCare warranty paperwork, I stopped by my local Apple store. I wanted to find out if I could keep my busted disk drive for a few days after they gave me a replacement drive, in order to attempt recovery of the drive’s data. The person I spoke with at the retail counter assured that this was possible. When I finally got my warranty authorization, I took my laptop to the GeniusBar. They ran some diagnostics to verify the disk failure and began filling out a work authorization when I asked about keeping my old disk. Now I was told that there was no way I could keep my old disk. Grrrr! So I took my baby home for one final data recovery session. (Lesson learned: Never ask warranty questions at the retail counter! Always head to the Genius Bar for this sort of thing.)

By now, it’s early December. My PowerBook G4 has been dead for over two months! I had received the copy of DataRescue II that I ordered, so I hooked up a FireWire drive and booted DR2. (The DiskWarrior CD was still in the drive. In order to eject the CD-ROM, I had to hold down the mouse button while powering up the laptop.) DR2 seemed to work great. It took several hours to examine the disk, but it beat the pants off DiskWarrior! Since I was going to permanently lose the disk, I ran several recovery passes using nearly every trick that DR2 provided, saving both the file/directory structure as well as “content-based recovery” which is able to recognize JPEG, MP3, PNG, et cetera, files based on their content. When the AppleStore opened the next morning, I was able to make an appointment at the GeniusBar using the Concierge service. (Requires Flash.) They didn’t have a replacement disk available at the store, so they suggested sending it in for “depot repair” since it would probably take a day or two longer for them to order a replacement disk and perform the repair at the store.

On December 4, I finally got my laptop in for repair. That was a Sunday, so it should have been shipped out on Monday. The “repair” is merely replacing the hard drive, which ought to take under an hour. Then the unit was going to be shipped back to me. This should have been finished in about a week, right? Wrong! Problem number 1: some chowderhead at the depot accused me (via a customer service person) of installing a non-Apple hard drive, so my warranty was void. I assured the CS rep that I hadn’t opened the case, so she asked the repair tech to send her photos of the “unauthorized” drive. A day later, I got another call from the CS rep telling me that the Apple sticker was clearly visible in the photo so she graciously reinstated my warranty and authorized the repair. (There went at least two days.) I was told to expect my system back early the following week (12-14 December). Well, it didn’t arrive last Monday, and I was meeting with a vendor all day Tuesday, Wednesday and Thursday. On Friday morning, (16 Dec 2005), I still hadn’t seen my baby so I called Apple. It turns out that they had been sitting on my repair because they didn’t have the exact same part in stock, and they won’t do anything (beyond ordering the part) until two weeks have passed! I guess last Friday was close enough to the 2-week limit that they initiated a “thorough inventory check” to see if there are any identical hard drives stashed away somewhere. They will supposedly wait two business days for a response on this, before they allow substitution by an upgraded part. So my PowerBook should be repaired tomorrow and shipped back to me, but the PowerBook G4 Support page still shows “On hold - Part on order” as the current status.

Once I actually receive my laptop, I’ll finally get to see how well Data Rescue performed. More to come…

09
Nov

DiskWarrior wasn’t able to help me

About 1.5 months ago, I had a boot failure on my PowerBook. I’ve tried recovering the hard drive with DiskWarrior several times. In fact, my most recent attempt has lasted over six weeks, which is probably a record for perseverance. But today I’m throwing in the towel. I’m going to the local Apple Store to pick up a replacement HD and start from scratch. :cry:

Here’s what I should have done:

  1. Run DW’s S.M.A.R.T. diagnostics, instead of relying on Apple’s diagnostics.
  2. If the S.M.A.R.T. diagnostics indicate imminent disk failure, abandon DW and try using DataRescue instead.
  3. Finally, most obvious yet oft-forgotten — backups!

My only complaint about DiskWarrior is that I think it should automatically run the S.M.A.R.T. diagnostics and recommend against continuing with DW if the diagnostics indicate disk failure.

06
Oct

DiskWarrior finally completed “step 5″

Sometime Tuesday night/Wednesday morning, DiskWarrior finally completed “Step 5: Locating directory data…” which gives an elapsed time of 200-216 hours or almost 9 days! It’s currently working on “Step 6: Overlapped files detected: 146″ which translates to quite a bit of manual effort for me. :( Step 6 has been running for somewhere between 26-41 hours as of this post.

Lessons learned:

  1. Backups!
  2. Don’t trust Apple’s disk diagnostics. Run the S.M.A.R.T. diagnostics from the DW CD before attempting recovery with DW!
  3. If the diagnostics indicate disk failure, don’t use DW. Try DataRescue instead. There’s no point running DW on failing hardware.
  4. Backups!

I’ll update this post as steps are finished.

Update 2005-10-06 23:58:27 UTC: It’s been on step 6 all day, now up to 186 overlapped files detected, sigh. I’m about to leave for the night. Hopefully tomorrow will be the day I get my data back…

Update 2005-10-10 15:48:55 UTC: It spent all weekend on step 6, now up to 675 overlapped files after more than 5 days. Ugh!

Update 2005-10-11 15:40:36 UTC: Step 6 has been running 6 days. Overlaped files detected: 807. And counting… :(

Update 2005-10-12 14:34:20 UTC: 7 days, 935 overlapped files. I am so screwed…

Update 2005-10-14 00:37:53 UTC: It’s now been almost 9 days since step 5 completed. Step 6: Overlapped files detected: 1124 :cry:

Update 2005-10-17 15:26:00 UTC: 12 days on step 6 now, 1605 overlapped files. I’ve got a lot of time invested in this, but I’m starting to wonder if it’ll be worth it. (Of course, my co-workers have been telling me to bail on this process for quite a while now. Considering that I’ve been running DW for three weeks, they have some reason.)

Update 2005-10-24 17:23:46 UTC: Step 6 is on its 19th day, 2512 overlapped files. I’ve been running DiskWarrior for 4 weeks straight. I’m really missing my laptop (whimper). I’ll be crossing the 1-month boundary this week, and if it’s not done by then I’m giving up.

Update 2005-11-09 18:09:25 UTC: After more than five weeks (and 4586 overlapped files) on “Step 6,” I’m giving up.

28
Sep

Still rebuilding my laptop disk

In an earlier post/comment I started running DiskWarrior in an attempt to recover my laptop’s failed harddrive. Still running after 47 hours, but no sign of progress (or failure) yet…

25
Sep

PowerBook boot problem revisited

I connected my laptop to another system with FireWire and booted my laptop into “Target mode” — hold down the T key while powering on the laptop. This effectively turns the laptop into a very expensive external FW enclosure. I ran DiskWarrior from the other system, and it recognized the “external” FW drive. I started a DW recovery on this drive at about 16:30 PDT. If it’s anything like the previous run, it should be done with “Step 5″ by about 07:15 tomorrow morning. (crosses fingers)

Update: Well, I let that run all night (about 16 hours), and DW looks like it hung soon after I got it started. Alsoft’s support phone still says something about hurricane Rita, even though it’s now Monday morning (when they indicate that they’ll be back) — terrible timing on my part, having a drive fail right as a hurricane strikes Alsoft. :( I’ve booted the laptop with the DiskWarrior CD, with an external FW drive. DW can “see” both the internal (failing) drive as well as the external FW drive. Let’s see how it goes…

24
Sep

PowerBook boot failure

Update 2005-11-10 20:55:29 UTC: Posts concerning my Powerbook boot failure are tagged with powerbook and boot_failure. Posts about my experiences with DiskWarrior are tagged diskwarrior.

Nooooo! My trusty PowerBook won’t boot this morning. The screen lights up, the Apple logo appears, and the spinner starts spinning — and it hasn’t stopped after more than an hour. A little googling turned up a post on how to boot a PowerBook in single-user mode, so I held down Command-S while powering on. That worked, cool! Then I tried /sbin/fsck -y. It turns out that my disk has journaling enabled (I didn’t know that), so I had to use the “force” option, /sbin/fsck -f, which gives Bad News:

localhost:/ root# sbin/fsck -f
** /dev/rdisk0s9
** Root file system
** Checking HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
   Invalid key length
(4, 4341)
** Volume check failed.

So, time to try the Disk Utility from the install CD — hold down the Option key while powering up. This gives me three options: boot from local disk (which I already know doesn’t work); boot the install CD (which I’ll try in a minute); and Apple Hardware Test, which sounds like something I should try right now.

Apple Hardware Test (PowerBook version 2.0.6) loaded and I selected the Extended Test. After about 3.5 minutes, the utility reported that the Mass Storage system had passed hardware test, so it looks like my hard drive is okay, although the data on it appears to be corrupted. I let the rest of the hardware test run, just for kicks. My PowerBook has 1 GiB of memory, which took about 26 minutes to test. Total test time was 33.5 minutes, with everything passing. (phew!)

I rebooted holding down the Option key again, this time booting from the installer CD which took about a minute to load. When the “Install Mac OS X” window opens, select the Installer menu then Open Disk Utility... item. In the Disk Utility, I selected the disk device (vs “Macintosh HD”) and clicked Verify Disk on the First Aid tab. It reported:

Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
{red}Invalid key length
The volume Macintosh HD needs to be repaired.

Volume check failed.

Error: The underlying task reported failure on exit (-9972){/red}

1 volume checked {green}0 HFS volumes verified{/green} {red}1 volume failed verification{/red}

(Looks very much like the fsck -f output.) So I tried “Repair Disk” and got the following:
Repairing disk for “Macintosh HD”
Mounting Disk(S,”Checking HFS Plus volume.”,0)
Checking Extents Overflow file.
Checking Catalog file.
{red}Invalid key length
Volume check failed.

Error: The underlying task reported failure on exit (-9972){/red}

Repair attempted on 1 volume {green}0 HFS volumes repaired{/green} {red}1 volume could not be repaired{/red}

This post suggests using Disk Warrior. I can’t use a download version, since I need a bootable CD to repair the non-bootable drive in my laptop, so I’m off to CompUSA to pick up a physical copy.

Back from CompUSA, with my wallet $100 lighter, ouch! This had better work… I booted the DW version 3.0.3 CD (hold down the C key while powering on and insert the CD). The single-sheet instructions indicate that it will take 5-15 minutes to boot. In my case, it took about 6 minutes. After a few prompts, the software got to work. It got through the first few steps quickly, but then started “Step 5″, something about locating directory information. A message appeared on the progress window, “(Speed inhibited by disk malfunction)”. I assume this means file structure corruption, as opposed to a hardware malfunction of the actual disk. Well, the speed was definitely inhibited! It took 14.75 hours to complete “Step 5″ on a 75 GiB disk which was approximately half full. The worst part about this was a complete lack of any sort of progress indicator. The only way I could tell that anything was happening was to put my ear right on the laptop case over the disk, so I could hear the disk chattering once in a while. (Fortunately it wasn’t the cyclic series of sounds that a failing disk makes; instead, it was the purposeful sound of a disk doing random seeks. If you’ve listened to disks, you know what I’m talking about.)

After the excruciatingly slow “Step 5″, the next step, “Constructing optimized replacement directory…”, went relatively quickly. I didn’t keep track of its elapsed time, since I was trying to get ready to go to work and I missed the transition from step 6 to 7. In fact, steps 6, 7, and 8 all completed too quickly for me to note their elapsed time, but they took about an hour total. I started to hope that maybe I might have my PowerBook operational very soon, but then “Step 9: Recording any file or folder differences…” started. This took about 3 hours, but at least this step had a progress bar!

DiskWarrior has finally finished, after about 19 hours. After reviewing the log file and the new directory structure, I accepted the changes (as if I really had a choice). It took about 40 minutes to update the disk, then reported: DiskWarrior encountered an unexpected error while attempting to show the disk “Macintosh HD” on the desktop. Rebuild this disk again. Preview the disk and backup all files from the preview disk (2168, 4203). ARRRGHHH!!! After doing some post-DW diagnostics, it appears that the disk was hanging by a thread, and the heavy disk activity caused by DW was too much for it. The system will no longer boot into single-user mode. :cry:

This post is getting too long already, so I’ll publish it in it’s current “unresolved” state. I haven’t given up yet, though…




March 2010
M T W T F S S
« Dec    
1234567
891011121314
15161718192021
22232425262728
293031  

Tags

a wok for all seasons abramoff accessibility acetylene active directory activism adodb aerial photo afrofunk aim4tree air america airport express alite alito amtrak andante andy antenna anti failure any browser apache appetizer apple apple pie applescript arden arcade arden park ariana arnold artichoke ashland astronomy attic attika audio avid reader backup baen bart bash batch bathroom bbq bee beef begonia bgg bike bike hikers bike journal bikejournal biketalk bill oreilly bittorrent blacklist blog bloggercode blogroll blueberry boardgamegeek boardgames bonjour book bookcrossing boot failure bootcamp borderline chaos bugmenot bush business card butter cabinetry caira caitlin california callsign candamir caroline carpet cat cateye cdrom celebration cellular phone century cfengine cheese chicken chico chimney chinese chipotle chocolate christmas chumby city bikes civilization cjd claire club club fed co op coconut coffee comfort food community computer concord congress conquest conservation consumer reports copyright costco crazybikerchick crepe crock pot cruftbox css csus curl currency custard cvntrak dagoba daniel goetz darwinports database datarescue date format death delicious monster democracy now Democrat demolition dessert dhcp dickens diff disaster discrimination discworld dishwasher disk mirror diskutil diskutility diskwarrior dixie belle dock doors downing street memo drm dryer drywall dtv dump ed burke eff eggs eject election electric car electric truck electrical electricity elvgren emacs email energy efficiency eric meyer esr etext euthanasia facebook family faq faux news fcc feed feedreader fence finder firefox fireworks first4internet first amendment fishmeal flash flickr flooring fondue foreign exchange foundation fox and goose framing freebsd freedback freetds fsck fundraiser fyq garage garden geek geotag geourl ginger gnutar go gonuls google google earth google maps gpl gracenote graywater greek green group concat gtd gunthers gutters gwbush gymnastics hacking halloween ham ham radio handspring hardwood harry potter headmeta heimdal high speed photograph high tech inv hoax hobbies hobby hodgins holiday holly home power magazine horcrux houseblogs how to html humor hvac ilovejackdaniels imac impeach init inspection insulation intel internet iostat ipod ipodder iq iraq isight iso itunes ivins iwantsandy java city javascript jean reno jet lag joint chiefs joseph jott journalized blue judges cup juliette binoche kctc kerberos khs kimkerry kitchen kyocera la salles la times labor landscape laundry law leatherbys legal lego leopard lhc liberal library linkedin ljurban lodi logic logo lungren lynx maaloufs mac macaroni macbook mafc mailinator make.conf malware map marin markdown martin yan mason media media clip media reform meetup metric mexican microsoft mike comfort military milonic mindstorms mlk model railroading modoc hall monterey morning sedition motorcycle movie moving mssql munchkin murray mushroom music mynetflix mysql n3jim nagios naked lounge nerd score netflix network new urbanism new year New Yorker nofollow nut nutella oatmeal obama obcz occidental occupation omni openssl oracle organic osx owp paint pair palast palm panasonic parallels party patch peak adventures peak oil pear pedestrian village perl petaluma php ping pingback pingomatic pingomation pingqueue pirate pl sql planet bike plasma playroom entertainment plugin plugin:preview theme plugin:text control plugin:ultimate tag warrior plumbing podcast podsite politics portaudit portmaster ports portupgrade postfix potato powerbook Pozsars printer programming project gutenberg pryde punk puzzle qiana qrz quilt quilt shop quiz quote r5 records racism radio RAID railroad recent comments recipe redalt remodel repairmirror resaurant resolution restaurant restore review richmond rio americano robotics roger niello ron montana roof rootkit rss sacbee sacog sacramento sacramento spotlight magazine salad samba san francisco sandwich santa cruz scam scandal school days scplugin screen security session report shakespeare shuffle sigma siriradha sitemap slim jim snl snopes social social network software soma somafab sonicchicken sonicchicken blog sony spam spam karma spellcheck spinach spinner spirit spoiler etiquette spring hill cheese sql sqlserver stairs standards statcounter stephen king stop loss stucco stunt subversion sudo sudoku superbowl superhero supreme court sushi svn sysadmin tacoma tags plugin takara technology telephone television template terms and conditions textcontrol thai kitchen thanksgiving the well seasoned wok theater theme theme:borderline chaos theme:elvgren theme:elvgren wordpress google code theme:fluid blue theme:fullwidth theme:head theme:journalized theme:journalized blue theme:psycho theme:redoable theme:sharepoint like theme:simple green theme:spirit theme:steam theme:wuhan theme:yadda theme switcher thomas tigris euphrates tile tinfoil hat toc tofu tower theater training transit transit oriented development tribute u haul uneasy rhetoric university village unix ad notes ups van zant veal veterans day video vie viking hobby vote smart w3c wall warboss washer washington post weather web web developer web server wikipedia windows windows server 2003 wishlist woodworking wordpress workplace wpblacklist wpgatekeeper wsj xserve yaaarr yard