OS X Lion has begun to shut down VERY slowly

Sure. Next time you start up hold the ⌘ and V keys until you see a lot of text appear (Verbose Mode). Ignore what it says, just log in when the normal login screen appears.

When you shut down the same "verbose mode" messages will appear. Since it is taking so long you will have time to write down what seems to be holding it up. Post it in your response.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Console in the page that opens.

Step 1

Select "system.log" from the file list. Enter "BOOT_TIME" (without the quotes) in the search box. Note the times of the log messages referring to boot times. Now clear the search box and scroll back in the log to the time of the most recent boot when you had the problem. Post the messages logged during the time when you had the problem — the text, please, not a screenshot. For example, if the problem is a slow startup taking three minutes, post the messages timestamped within three minutes after the boot time. If the problem is a crash or a shutdown hang, post the messages from before the boot time, when the system was about to crash or was failing to shut down.

If there are runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.

Some personal information, such as the names of your files, may be included — edit that out, too, but don’t remove the context.

If the log doesn't go back far enough in time, scroll down in the Console file list to /private/var/log/system.log.0.bz2. Search that archived log, and if necessary the older ones below it, for the same information.

Step 2

Do the same with kernel.log.

Step 3

Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the most recent one, if any. For privacy’s sake, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall or hang logs — they're very long and not helpful.

Linc Davis wrote:

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Console in the page that opens.

Step 1

Select "system.log" from the file list. Enter "BOOT_TIME" (without the quotes) in the search box. Note the times of the log messages referring to boot times. Now clear the search box and scroll back in the log to the time of the most recent boot when you had the problem. Post the messages logged during the time when you had the problem — the text, please, not a screenshot. For example, if the problem is a slow startup taking three minutes, post the messages timestamped within three minutes after the boot time. If the problem is a crash or a shutdown hang, post the messages from before the boot time, when the system was about to crash or was failing to shut down.

If there are runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.

Some personal information, such as the names of your files, may be included — edit that out, too, but don’t remove the context.

If the log doesn't go back far enough in time, scroll down in the Console file list to /private/var/log/system.log.0.bz2. Search that archived log, and if necessary the older ones below it, for the same information.

Step 2

Do the same with kernel.log.

Step 3

Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the most recent one, if any. For privacy’s sake, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall or hang logs — they're very long and not helpful.

Linc,

Thanks for your offer of assistance.

For some reason, I could not find the kernel.log on my startup drive (anything). I did find a kernel.log on my alternate local drive from an old system from Sept. 2012, but it appears to be irrelevant. Note that I am running ML (Mountain Lion) 10.8.2 on a Mac Pro 3,1.

A couple of other notes:

• Doing a Permission Repair seems to alleviate theproblem, short term. It recurs.
• Doing a P-RAM reset helps for awhile.
• This same problem occurs on two other machines, MacMini Running OS 10.8 Server, a Macbook Pro (with the same client OS)
• The Crash Log saves as a new name?

Crash Log (also called filecoordinationd??)

sys.log portion (Edited)

Found other threads on discussions that seem to indicate the issue to be Parallels v7(which I had installed) to be the issue in ML. Have since fixed this and it no longer a problem.

Thanks.

Henry

for future reference and others.....

your kernel.log and others are located at

/private/var/log/kernel.log

This is a hidden directory....

Terry

Still having trouble with my MacPro not shutting down and using a later, most current version of Parallels (V8.0.12354). Not seeing any kernel.log entries of relevance. Will upload to this thread later. Anything else to try?

H