Just happened to me too: a TM backup failed and "b-tree"ed my external FW disk. Not even DW can repair it.

Disk Warrior finally completed trying to repair my external HD after THREE DAYS.It showed up the following information-
50,206 (of 51,087 total) files had a damaged extended attribute that DW repaired.(Interestingly ALL these files were created by Time Machine.. :confused: the remaining 800-odd were files I already had on the HD)

But trying to 'Preview' my rescued files,I can't get my external to mount even after DW's work.Is this the end?

I'd recommend recovering only the files that are not part of the Time Machine archives and repartitioning the drive from scratch. I wouldn't trust DiskWarrior to make adjustments to Time Machine files since they didn't exist at the time the current version of DiskWarrior was created.

Trouble is I can't recover them without the 'Preview' working.After it wouldn't,DW suggested I start rebuilding again.I tried it briefly to see if it was going to take the same length of time-and it clearly was.

I wonder if this is a result of newly implemented extended attributes used in Time Machine that may seem like problems to Disk Warrior? I can see no reference to there being a problem from the Alsoft site, but I wonder if using Disk Warrior to repair a Time Machine drive was thoroughly tested? Anyone have a perfectly good Time Machine drive they'd like to test Disk Warrior on to see if it handles a known-good backup properly? This Ars Technica article gives some information about the new extended attribute for Time Machine files: http://arstechnica.com/reviews/os/ma...4#time-machine
The discussion of the new FSEvents attribute occurs about 80% down in the article. I wonder why else Disk Warrior would see EVERY Time Machine file as having a damaged extended attribute? This could be important information, I think.

Joe VanZandt

In which case maybe I'll save my drive from the trash until DW give me the Leopard update...:)