I have a Volume Rebuild that has been running for 18 hours. The rebuild light is flashing and the core bars are moving. How can I tell if it is actually working. How long should this take?

I do have a TimeMachine Backup from a day ago. Now wondering if it would be faster to just wipe the disk and lode the backup.

I am on a MacBook Pro 3ghz with a 500gig internal booted from the CD.

The forums are moderated. Postings do not appear here until a moderator approves them.

There is no way to predict how long it should take to rebuild a new disk directory. It depends on processor speed, bus speed, drive speed, and the number of files and how many extents (pieces) they have.

What I can suggest is that you not attempt to rebuild the disk directory while the Macintosh is running from the bootable DVD. In such a case, virtual memory cannot be used, and no log files can be written. The entire new disk directory (Catalog B-Tree and Extents B-Tree), part of Mac OS X, and code from Techtool Pro must be able to be held in RAM or in a virtual memory swapfile.

You should create an eDrive on a USB memory stick or SD card of at least 32 GB capacity, formatted with a GUID partition map and a Mac OS X Extended (journaled) volume. Apple has instructions for reformatting the volume:

Mac OS X 10.5: Time Machine stops backing up to external disk. It is odd that the best instructions for changing the partition map scheme to GUID are in this article, but if you can remember this search string, it is not difficult to find:

Mac OS X Time Machine GUID

I suggest that before you attempt to rebuild the disk directory, you run the Surface Scan to check the drive for unremapped bad blocks. That process can be run using the copy of TechTool Pro on your usual startup volume, because it does not require unmounting the volume. The Surface Scan is a read-only test.

Cannot boot from the internal drive. I am going to try to install a bootable copy of the OS on an external drive and then run techtool on the internal. I have some of the docking systems for HDs and a couple of raw drives on hand. At about 22 hours, I am ready to try something else. When I get done, eDrive is the first thing I am going to do.

Kevin

It is good to see that you have a backup, and the hardware needed to get a bootable installation of Mac OS X and TechTool Pro installed.

Did the Volume Structures test in TechTool Pro or the Verify Disk feature of Disk Utility find disk directory errors in the volume from which you cannot boot?

If the internal drive is still under warranty, run the Surface Scan to check for unremapped bad blocks, and if any are found, make a screen capture of the result, which will facilitate your warranty claim. Also, run the S.M.A.R.T. test to check the internal drive.

Verify disk gave errors. I have had tech tool for quite some time. I am now kicking myself for not installing eDrive on this box. Doing the install right now. I wii give you an update later.

Thanks for the help

From my phone

Kevin

You are welcome, and thanks for the update.

So far no luck. Volume rebuild runs but I taking a long time in Rechecking structures. Stopped here once and the drive would not mount. Letting it run to see if will complete this time surface scan checked out with no errors. The other checks I ran in TT worked as well. More later. Any suggestions?

Purchase and am using TT 6 now.

Kevin

You might be able to get a detailed diagnosis if you use fsck_hfs to examine the volume. Apple has complete instructions. This is mostly of academic interest now, because the free read-only tool that could be used to identify files by their catalogue node ID number has been replaced by a $79 utility, fileXray.

I finally gave up and reloaded my backup. TTP 6 kept hanging in the latter stages of anything I tried. Volume Rebuild repeatedly reported 499Gb when there was only about 340gb on the drive. (500GB drive)

I have now purchased and moved to TTP 6. When I attempt to mount the eDrive it will not stay mounted. I have tried in TTP using the button and in Disk Utility.

Also, Surface Scan reports no bad blocks.

Kevin

Thanks for the update and upgrade. It is good that you had a backup.

If you have enough volumes and disk space, I would suggest that you not update the backup you used to restore the files, but leave it as an archive for a while, just in case some rare hardware problem with the internal drive caused its disk directory to be irreparably damaged. Use another volume to make new backups, and check the disk directory of the internal volume frequently for a few days.

The eDrive is not intended to remain mounted unless it is the active startup volume. When TechTool Pro is properly installed on the active startup volume, the eDrive mounts briefly at the end of the boot, and then is automatically unmounted by the TechToolProDaemon background process. If you need to keep the eDrive mounted for some reason, use the Mount eDrive button in the eDrive pane of the TechTool Pro application, and leave the TechTool Pro application running. The eDrive should mount and remain mounted until you quit the TechTool Pro application. At that point, the eDrive should unmount automatically.

It will be quite a while before the backup I used would go away. It is on a network Raid with plenty of space and many backups.

All the hardware tests pass but I will be watching closely for the next little while.

Thanks for the edrive info. I am putting it on my 3 computers now.

Thanks for all your help. Just wish that TTP would have fixed it the first time.

Kevin

You are welcome.

It is always disappointing to find irreparable directory damage. All disk repair utilities rely on exploiting the redundancy built into the HFS+ disk directory, and progress continues to be made with the utilities, but there will always be directories so damaged that they cannot be repaired. It will be interesting to see reports on how well ZFS on the Macintosh is working.

The new Time Machine backup did not want to run to the existing drive as in incremental backup. My computer wanted to make a complete backup and did not seem able to delete the oldest backup from the previous incarnation. I hooked up another drive to my server so the March 1 backup that I restored from will be preserved. I will let it run this way for a little while until I am confident that everything is working properly. I will then return to the previous drive and delete or copy off the backup file. Don't want to leave my temp solution running since it is just an interface for naked drives.

Thanks for everything.

Kevin

You are welcome, and I think you have a good plan.

I know that there are many tutorials online for modifying Time Machine backups so they will continue to work after a major system change, but I do not see one that allows for an incremental backup after restoring all files from a backup, and I am not sure that can be done.

Hi Micromattech3,

Tech Tool web documentations should clearly explain that bootable Tech Tool Pro 6 DVD is not useful for fixing errors (particularly, rebuilding volume).

Knowing that, I would have known that it was not going to help me fix my wife's work iMac (she is freelance graphic designer). I wold have not buy TechTool nor expend many hours... useless. TechTool is "rechecking structures" since 3 hours long now. And it is not telling me that it crashed or run out of memory, what may probably be the case. I don't have logs nor the opportunity to use Applications/Utilities because the problem is that the harddisk does not boot.

I have not been that lucky to have an external disk with enough space to build an eDrive and try that way. Nor a firwire cable to connect my own macbook with the iMac ...

It is very disappointing. I will have to re-format and re-install all, my wife needs to start working ASAP.
I hope you will manage to get such important piece of information like described by you publc in a way people read it before buying.

If you know the magic TechTool thing I have not discovered but can use to fix the hardisk, I do appreciate you tell it to me asap. It is evening here and I have to get the computer working before tomorrow moring.

Thanks, regards

One of the main new features in TechTool Pro 6 is that it can make an eDrive by splitting the active startup volume, so you do not need to boot from another drive, or have a bootable external drive in order to have an eDrive. A full backup of all volumes on the drive containing the active startup volume should be made before the attempt to create the eDrive.

As soon as I did read your message, I canceled volume rebuild.
I will try to create eDrive in problematic hard disk right now.
But the issue I am facing now is that the problematic hard disk is not shown to create the eDrive. Same thing happened to me when trying to rebuild volume. Only when I plugged an external USB drive, the internal drive got enabled to run "rebuild volume". No clue why.

Any tip will be highly appreciated.
Thanks again.
Regards

You cannot create an eDrive by splitting a volume that has directory damage. The volume to be split must have a disk directory that is free of errors.

You should run the Surface Scan test to make sure that the drive does not have unremapped bad blocks. I know you want to get the files restored, but if the drive is failing, that will prove to be a waste of time.

I did run surface scan early today, and it stated there were bad blocks. I canceled it before if finished (it will take long for 250GB drive, won't it? ) . So far, surface scan had found about 35 bad blocks but said nothing about unremapped bad blocks...

Not clear to me if "bad block" means "unremapped bad block"...
I do appreciate your prompt answer once again.

Thanks,
Regards

You are welcome.

You should stop dealing with this drive and replace it. The magnetic media is defective. Take a screen capture or a digital photograph of the results of the Surface Scan as evidence, if the drive is still under warranty.

A bad block is one that cannot be read or written to. TechTool Pro's Surface Scan can detect bad blocks that have not already been remapped to spare blocks, which are called unremapped bad blocks. The details are in the thread Surface Scan.

Here is another recent thread which turned out to be about the Surface Scan:

A Suite of Tests.

Well, without a clean drive to create eDrive, and reading your comment, I decided to re-format disk and install aaaall again. I am in such process now. And I will probably buy a new disk soon.
Still, I believe it will be good if Micromat indicates in the documentation (that buyer reads) that bootable Tech Tool Pro 6 DVD is not useful for fixing errors (particularly, rebuilding volume).
I would have probably bought Tech Tool anyway, but also a firewire wire to use my other Mac as eDrive host (ie: it was late to buy firewire when I found forum item).

Last, if you allow me to suggest an enhancement: Tech Tool can easily include an option to let user (ie: me) see progress and error output rather than trying to convince myself that 2 red lights blinking really means such thing even after waiting 4 hours ... (please remember my case was running from bootable DVD)

Thanks for your help
Kind regards

You are welcome.

The magnetic media on the disk platters is flaking off. Please replace the drive. Reformatting a drive with defective media was standard approach ten years ago, and leads to catastrophic failure in many cases.

The Surface Scan does indicate the number of errors (unremapped bad blocks) in real time.

I am seeing this same behavior in relation to Volume Rebuild, though I am running it on an external drive, not my boot drive. I get the feeling that it would literally run for days, if I let it.

It always seems to hang on the last part, which is replacing the examined volume structures (if I have my terminology right) with the rebuilt and optimized ones.

I can only suggest that you run the Surface Scan, and check the All Messages log (or the system and console logs) of the boot volume that was in use when the Volume Rebuild was being done. The logs can be read conveniently by using the Console application, located in /Applications/Utilities.

If you stop the replacing of the disk directory, you may lose the volume. On the other hand, you clearly cannot let the process run indefinitely. You should always have a backup of any volume on which you rebuild the disk directory or run the disk optimizer.

hi I've been reading thru this tread trying to find out whats going on with similar stuff when Optimizing the Volume on my boot drive. I'm using an eDrive created with TTP6, and have gone through the steps suggested by TTP prior to this step (steps suggested prior to Defragging and Optmizing, etc). but it's been going since 615am, now 345 - 10+ hours, and the needle is stuck on 89% complete.

Contiguous Free Space Count:
keeps bouncing back & forth between 4,938 and 4,937

Fragmented Files:
remains a constant at 3,135 -> 38.83 GB

Current Step:
bounces back and forth between Locating and Moving Used Space

What's going on? The only issue that arose with the other processes were there were some damaged files - like 5, and an "empty" .plist file - which I planned to get rid of these of AFTER I rebooted back into the normal disk mode. But I didn't think a few "bad" files would have any effect on Optimizing.

Attached screen shot and Console log (hope its the right log - I'm not too adept at the Console or Terminal language/usage yet).

thanks.

hi I've been reading thru this tread trying to find out whats going on with similar stuff when Optimizing the Volume on my boot drive. I'm using an eDrive created with TTP6, and have gone through the steps suggested by TTP prior to this step (steps suggested prior to Defragging and Optmizing, etc). but it's been going since 615am, now 345 - 10+ hours, and the needle is stuck on 89% complete.

Contiguous Free Space Count:
keeps bouncing back & forth between 4,938 and 4,937

Fragmented Files:
remains a constant at 3,135 -> 38.83 GB

Current Step:
bounces back and forth between Locating and Moving Used Space

What's going on? The only issue that arose with the other processes were there were some damaged files - like 5, and an "empty" .plist file - which I planned to get rid of these of AFTER I rebooted back into the normal disk mode. But I didn't think a few "bad" files would have any effect on Optimizing.

Attached screen shot and Console log (hope its the right log - I'm not too adept at the Console or Terminal language/usage yet).

thanks.

The forums are moderated. New postings do not appear here until a moderator approves then.

Your console log did not appear. For some reason, the screen capture does not display in the thread, but I can see it by clicking its icon. It shows that the largest unused block, which is the largest piece of free, contiguous (all in one piece) disk space, is 4.45 GB. The disk optimizer cannot defragment any fragmented file larger than the largest unused block.

If you click the large X button to stop the optimization, the optimizer should finish the one file it is working on, update the disk directory, and remount the volume. That probably will not not happen in your case. If you force quit the optimizer, the consequences depend on exactly what the optimizer is doing when it is forced to quit. They can range from nothing, to loss of a file, loss of a folder, to loss of the entire volume in the rare case in which a piece of the disk directory itself is being moved. The program instructs the user to make a backup when it is launched.


Before running the volume optimization, a file optimization should be done, as is mentioned in the manual. It is a good idea to check the disk directory with the Volume Structures test or Disk Utility before performing any optimization, and to run the Surface Scan to check the drive for unremapped bad blocks. Never attempt to optimize a volume without making a backup first.

Attempting to optimize a volume with damaged disk directory entries is a bad idea, but damaged files are simply bad data, and do not pose a problem for an optimizer.

Please send the console log and a link to this thread to This email address is being protected from spambots. You need JavaScript enabled to view it. . You will receive a reply by email on Monday, and may be asked to send in an Apple System Information report. Thank you.

micromattech3 & the rest -
just realized I got this triple-post thing going!?
dunno what happened but I'll try to keep futures
to a single post
very sorry about that...

No apology needed. I just have to be really careful with the Delete button, and then the Permanently Delete button.

thanks for the reply.

You lost me with your instructions to: "click the large X button" - to "that will probably not happen in your case"....

But I did click the X and TTP did stop. the job says the result was incomplete. So what should I do now? I'll attach a screenshot of the finished - but the graphic looks the same as the last one I sent. (after I submit this quick reply).

as stated, I followed all TTPs instructions for going through the various tools. I have backup. I've file optimized before volume optimization. I checked the disk directory with the Volume Structures and Disk Utility (more than once). And ran Surface Scan. All were good results.

will email the Console logs and other as you've suggested.

thank you again.

right on

...and here's the latest screenshot...

"It shows that the largest unused block, which is the largest piece of free, contiguous (all in one piece) disk space, is 4.45 GB. The disk optimizer cannot defragment any fragmented file larger than the largest unused block."

largest unused block = 4.45GB
ttp can't defragment a single file than the largest unused block

I'm sure both these statements are true.
but how does this apply here?
I don't see anything that says I've got a defragmented file that's larger than 4.45GB.

??

Thanks for letting me know you have a backup. Thanks for having a backup.

To defragment a fragmented file of a given total size, there must already be on the same volume a piece of free disk space that is all in one piece, and that is at least as large as the fragmented file.

If you are certain that the disk directory is free of errors, because you ran the Volume Structures test or Disk Utility to check the disk directory after stopping the optimization, then you could try again. I suggest that before making another attempt, you try to find some files larger than 4.45GB that are not fragmented and move them temporarily to another volume, deleting the copies on the volume you are trying to optimize, in an attempt to make the largest unused block larger. There are shareware utilities such as WhatSize that show files sorted by size.

super. I'll give that a try...

When you add an attachment, use the Add File button first, then the Insert button. That should make the file appear online within the thread. I can fix the lack of using the Insert button by using the Edit button, then the Insert button.

I've tried to follow your instructions for uploading, and took this screen shot to show you that the shot appears on my end?: Screen shot 2012-05-05 at 5.37.22 PM.png

what's strange is that this is what I see when adding an attachment (i'm using Safari still booted from the eDrive): Screen shot 2012-05-05 at 5.40.44 PM.png
• C:\fakepath? - the "C:\" seemed odd to me - I'm on a Mac not Windows!
• and also "fakepath" after what appears to be the drive also has thrown me for a loop - but I just figured it was something on your server's end.

maybe its on my end?
...no idea...

OK, well it looks like i've got more problems than I (and we) thought.

I was able to quit the Optimize process as you instructed, and then ran Volume Structures test.
Its gotten all the way to Volume Bitmap (solid green) and is blinking green at Volume Information.

I went back to Console, under the Database Searched tab, and selected Console Messages. Here's a cut-n-paste of what the log says from the just BEFORE I started the Volume Structures Test (I think after canceling Optimize), to the moment AFTER I clicked the Volume Structures test:

5/5/12 5:27:13 PM com.apple.launchd[1] (com.apple.metadata.mds[8315]) Exited with exit code: 1
5/5/12 5:27:13 PM com.apple.launchd[1] (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds
5/5/12 5:27:23 PM com.apple.launchd[1] (com.apple.metadata.mds[8316]) posix_spawn("/System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds", ...): No such file or directory
5/5/12 5:27:23 PM com.apple.launchd[1] (com.apple.metadata.mds[8316]) Exited with exit code: 1
5/5/12 5:27:23 PM com.apple.launchd[1] (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds
5/5/12 5:27:33 PM com.apple.notifyd[14] EV_DELETE failed for file watcher 139
5/5/12 5:27:33 PM com.apple.notifyd[14] EV_DELETE failed for file watcher 136
5/5/12 5:27:33 PM com.apple.notifyd[14] EV_DELETE failed for file watcher 135
5/5/12 5:27:33 PM com.apple.notifyd[14] EV_DELETE failed for file watcher 134
5/5/12 5:27:33 PM com.apple.notifyd[14] EV_DELETE failed for file watcher 131
5/5/12 5:27:33 PM com.apple.notifyd[14] EV_DELETE failed for file watcher 138
5/5/12 5:27:33 PM com.apple.notifyd[14] EV_DELETE failed for file watcher 137
5/5/12 5:27:33 PM com.apple.notifyd[14] EV_DELETE failed for file watcher 132
5/5/12 5:27:34 PM com.apple.launchd[1] (com.apple.metadata.mds[8321]) posix_spawn("/System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds", ...): No such file or directory
5/5/12 5:27:34 PM com.apple.launchd[1] (com.apple.metadata.mds[8321]) Exited with exit code: 1
5/5/12 5:27:34 PM com.apple.launchd[1] (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds
5/5/12 5:27:44 PM com.apple.launchd[1] (com.apple.metadata.mds[8323]) posix_spawn("/System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds", ...): No such file or directory
5/5/12 5:27:44 PM com.apple.launchd[1] (com.apple.metadata.mds[8323]) Exited with exit code: 1
5/5/12 5:27:44 PM com.apple.launchd[1] (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds
5/5/12 5:27:54 PM com.apple.launchd[1] (com.apple.metadata.mds[8324]) posix_spawn("/System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds", ...): No such file or directory
5/5/12 5:27:54 PM com.apple.launchd[1] (com.apple.metadata.mds[8324]) Exited with exit code: 1
5/5/12 5:27:54 PM com.apple.launchd[1] (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds
5/5/12 5:28:04 PM com.apple.launchd[1] (com.apple.metadata.mds[8325]) posix_spawn("/System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds", ...): No such file or directory


I have no idea what this all means.
I hope you do!

The "fake path" looks as it should. Just click the Insert button after you see the "fakepath" appear.

mds is one of the processes used by Spotlight. We had to remove Spotlight from the eDrive system software, because it was preventing volumes from being unmounted. I would not be concerned about those error messages.

found an 8.58 GB file named sleepimage in private/var/vm/
any idea what that might be?

The sleepimage file stores some of the contents of RAM when the computer is put to sleep. I do not see why there would be a problem with deleting the one that is not in use. Make sure the file is on the volume you are trying to optimize, not the active startup volume. Never make any changes to /private/var on the active startup volume. The folder is private for good reasons. The virtual memory files are in /private/var/vm.

Unfortunately, there is no simple and free way to know whether the sleepimage file is in one piece.

ok. well I' still not sure what I should be doing now.
the VolStructures test was hanging or couldn't complete, so not sure what to do next.

I assume that the directory needs to be rebuilt and as I think I recall you earlier said that if the directory is not solid, than there's really not much one should be doing on the drive because that would just make matters worse. do I have that right?

if so, how do I fix the directory problems?

What I wrote was that if the disk directory contains errors, the volume should not be subjected to any optimization.

You could use the Volume Rebuild tool to attempt to rebuild the disk directory. When you use it, the Technical Comparison window appears, and if the total number of files and folders and the total amount of disk space occupied by the files in the original directory and the proposed rebuild matches, it should be safe to replace the disk directory. I would not be surprised if it did not work in your case, but if you want to try, read the relevant section of the manual first.

The present disk directory may contain some section that is unreadable. You would have to check the All Messags log, or the system and console logs, to see what errors were reported when you ran the Volume Structures test.

If you have run the Surface Scan today, and the S.M.A.R.T. test shows no failures, it would be faster and simpler to erase the original volume with Disk Utility and then restore the files from the backup. The restored files would be in one piece each from that approach.

...back from getting some eats...

OK. well, it looks like indeed mds is more of a culprit and problem then you folks realize. maybe you folks should reconsider leaving this out of the mix:

5/5/12 10:33:02 PM com.apple.launchd[1] (com.apple.metadata.mds[10521]) Exited with exit code: 1
5/5/12 10:33:02 PM com.apple.launchd[1] (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds
5/5/12 10:33:12 PM com.apple.launchd[1] (com.apple.metadata.mds[10522]) posix_spawn("/System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds", ...): No such file or directory
5/5/12 10:33:12 PM com.apple.launchd[1] (com.apple.metadata.mds[10522]) Exited with exit code: 1
5/5/12 10:33:12 PM com.apple.launchd[1] (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds
5/5/12 10:33:22 PM com.apple.launchd[1] (com.apple.metadata.mds[10523]) posix_spawn("/System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds", ...): No such file or directory
5/5/12 10:33:22 PM com.apple.launchd[1] (com.apple.metadata.mds[10523]) Exited with exit code: 1
5/5/12 10:33:22 PM com.apple.launchd[1] (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds


THERE'S OBVIOUSLY AN ISSUE WITH MDS


the above-pasted report is from the Apple Disk Utility itself. After trying your route several times to no avail, I decided to run good ole Disk Utility to see what that revealed, and I got the above info during a volume repair.

I went with TTPs because of its history with being bundled with older Mac OSX system software and more recent items that I've read. But thus far, down in the trenches and getting dirty, TTPs is not handling this well at all.

When I jumped into this post (after purchase and already knee deep in these problems that mostly started after running TTPs tools), it was on the heels of the OP Diego Balbi, who had many viable points about how Micromat should be advising its users, especially when it comes to alerting them that using a burned DVD to reboot isn't going to work (I know now as well, because it didn't work for me either - in fact I was pretty pissed that not only did that not work, in addition, even though the documentation states to use a 12 GB USB drive to make an eDrive disk, in truth that doesn't work either in TTPs v6. No, you need more like 32GB for it to build a successful disk under TTPs6. Again, this is a poor loophole Micromat seems to be hiding in. Its documentation AND recommendations are seemingly incorrect.) I've been in his shoes before in older OS' (classic and OSX) in trying to solve various issues that come about especially with some processessor-intensive apps like graphic design requires, and using disk utility tools to keep drives running smoothly at that time for me was standard. So I've played on the field even if I can't speak all the proper lingo.

I've wasted 2+ days on working with TechTool Pro v6 and am really not at all happy about it.

Any time launchd is set up to launch a process, and the process is not available, error messages such as those you posted appear. They are harmless.

The need for the USB memory stick to be at least 32GB in capacity is new with Lion, and is caused by changes Apple made to system software tools.

I am sorry that the optimization of your volume, which had very badly fragmented free space, had a bad outcome. If your 8 GB sleepimagefile was fragmented, and the size of the largest unused block was 4.45 GB, the program should have cancelled the optimization.

I have forwarded your posting to the beta administrator for TechTool Pro.

I recently updated to TechTool Pro 6. I would not have updated if the fact of non repair from the DVD was on the web page.

What the web page says, implying that it can solve directory problems.

Volume Rebuild

TechTool Pro will test and rebuild damaged directories on corrupted hard drives, and optimize the data directories when they are repaired. Volume Rebuild will display a comparison chart before directory data is replaced. Use Volume Rebuild to keep your drives operating at their peak performance. See Volume Rebuild screenshots

What it says in the manual stating that you can do so with the DVD.

NOTE In order to rebuild the volume structures of a volume, it must be unmounted. This means that you cannot do a volume structure rebuild of the current startup volume. To do this, you must reboot the computer and run TechTool Pro from another volume, such as from an eDrive or the TechTool Pro DVD.

What it doesn't say in the manual or on the web page:

Sorry, you shouldn't use the DVD as stated because that won't work very well if at all .... instead you require a minimum 32Gb USB drive to make into a recovery drive.

A DVD is a locked volume. When the Macintosh is booted from a locked volume, virtual memory cannot be used, and no log files can be written. 32 GB USB memory sticks are no longer expensive, and work considerably faster than a DVD drive.