Welcome, Guest
Username: Password: Remember me

Search Micromat Forum

Keyword

TOPIC: OSX 10.12.2 doesn't work with tech tool pro 9 in edrive

OSX 10.12.2 doesn't work with tech tool pro 9 in edrive 16 Dec 2016 00:59 #7930

After updating to latest OS, Mac was sluggish so I tried to use festive to optimize, can't unmounted HD. Making tech tool pro useless at the moment.

Any ideas?
The administrator has disabled public write access.

OSX 10.12.2 doesn't work with tech tool pro 9 in edrive 16 Dec 2016 01:17 #7931

The optimization should be done in two stages. First, use the File Optimization tool, which does not require unmounting the volume to be optimized. Then, to run the Volume Optimization tool, restart from another volume that has an installation of Mac OS X and TechTool Pro on it, such as an eDrive or a Protogo device.

There are some rare cases in which even after restarting from another volume, the volume to be optimized by the Volume Optimization tool cannot be unmounted.

The most common reason why a volume cannot be unmounted is that it contains open files. Below are our instructions for using the lsof command to locate the open files. Each line of the output of the command refers to one open file. The name of the process that has the file open is at the start of the line, and the pathname is at the end. The instructions can be summarized as:

Use the lsof command to find the open files on a volume that does not unmount or eject.

Open Terminal, located in /Applications/Utilities. Type:

sudo lsof | grep

Leave a space after the p, then drag the icon of the volume to the Terminal window. The pathname for the volume is pasted in for you; press Return. Then enter your administrative password at the prompt, and press Return.

If the Macintosh is booted from an eDrive and the startup items copied to the eDrive are causing files to be open on the volume that served as the Mac OS X Source Volume, try logging in as another user, rather than attempting to find the open files and then the processes that have them open.



Here is part of an earlier thread on this topic. The output of the lsof command is these three lines:

coreservi 68 root 10u VREG 14,32 5632 54 /Volumes/Maxtor_BU09/Desktop DB
coreservi 68 root 11u VREG 14,32 38082 55 /Volumes/Maxtor_BU09/Desktop DF
RetroRun 26448 root 25u VREG 14,32 214780244 11347 /Volumes/Maxtor_BU09/Main Backup/Maxtor_BU09.cat


Each line of the output of the lsof command refers to one open file. The name of the process that has the file open is at the start of the line, and the pathname is at the end.

In the example above, the process named RetroRun shown on the last line (a process used by the Retrospect backup program) has a file named Maxtor_BU09.cat open on the volume Maxtor_BU09. The file is in a folder named Main Backup. The user quit Retrospect (either in the Finder or by using Activity Monitor, located in /Applications/Utilities) and the volume was then able to be unmounted.

You can ignore any references to the files DesktopDB and DesktopDF; the operating system can close them.


Spotlight indexing can cause files to be open:

Spotlight consists of two processes, according to Bombich Forums moderator Andreas:

mdimport user process

mds root process


Any process that is launched by launchd will relaunch if you hesitate between quitting the process and unmounting the volume on which the process was running. Launchd is Apple's method of launching processes at login, and is supposed to make sure that the processes it controls are promptly relaunched if they quit or crash. For example, if you use Activity Monitor to inspect SystemUIServer, you see that its parent process (the one that launched it) is launchd.
MicroMat Inc
Makers of TechTool
Last Edit: 16 Dec 2016 01:21 by micromattech3.
The administrator has disabled public write access.
Time to create page: 0.281 seconds