Endless spinning wheel on shut down

I don't see anything in those brief log extracts to show how they're related in time to the last shutdown. They do show that you partially uninstalled something called "Macaroni Tool" (whatever that is), leaving behind a launchd item. You should either reinstall that software, or, if you want to remove it, do so completely by following the vendor's instructions. I can't tell you how to uninstall it.

That's all I can glean from this small amount of information. Based on what you've said in this thread, I think you should reinstall the OS completely, not just the 10.6.7 update, which you don't seem to have done yet. You need to back up all your data first, and run Software Update afterward. Unless something goes wrong, your data will be undisturbed and you won't have to restore anything from backup.

No, there's no archive & install, the Installer just replaces the system files and leaves everything else as it was.

otjacob wrote:

Do you reinstall the OS by using archive and install from the original disk?

Thanks,

Jacob

Archive and Install as Linc suggested will only re-write the core OS X files. Your data should be OK. Snow Leopard contrary to the previous versions of OSX does not have a labeled "Archive and Install" from what I have read previously on these forums, according to some of the experts on installing 10.6 OSX Snow Leopard does an archive and install by default if its installed on a disc that has a version of Mac OS X installed on it already.

Then if your description is accurate, you've eliminated software as the cause. The only thing left is hardware. Take the unit to an Apple Store for testing.

otjacob wrote:

Re-installed OS X, same problem. Safe boot, same problem too.

Thanks

Based on this we have to include the possibility of a damaged piece of hardware. However, there are 3 things left to do.

Reset PRAM and NVRAM:

1. Shut down the computer.
2. Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
3. Turn on the computer.
4. Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
5. Hold the keys down until the computer restarts and you hear the startup sound for the second time.
6. Release the keys.

Reset SMC:

1. Shut down the computer.
2. Unplug the computer's power cord.
3. Wait fifteen seconds.
4. Attach the computer's power cord.
5. Press the power button to turn on the computer.

Run Apple Hardware Test

1. If the computer is already on, insert the appropriate disc into the optical disc drive, then restart. If the computer is not on, turn it on and insert the disc as soon as possible after startup.
2. Press and hold the "D" key before the gray startup screen appears.
3. It takes a minute or so for Apple Hardware Test to start up and inspect your hardware configuration. While this is taking place, an icon appears on the screen:
   
   When the process is complete, select your language and click the right arrow. If you aren't using a mouse, you can use the up and down arrows to select a language and then press the Return key.
4. The Apple Hardware Test console appears. You can choose which sort of test or tests to perform:
   • To perform all of the basic tests, click the Test button or press the "T" key or the Return key.
   • To perform a more thorough diagnostic test, select the "Perform extended testing" checkbox under the Test button before you click the Test button.

I will suggest running the extended test 2 times to avoid the posibility of false positives. Write down any error code that the hardware test display so that the Apple repair specialist can take a look.

But first try the first two troubleshooting steps I suggested.

The Apple Hardware Test is not very reliable and can't detect every problem. Take the unit to an authorized service outlet for testing.

otjacob wrote:

I ran the procedures and the double extended test, no change. Problem the same.

Thanks,

Jacob

Well you have done everything in your part. It's time for an AASP (Authorized Apple Service Provider) to take a look to your computer. It all now points to an hardware issue.

This behavior occurs if you create a new user and try it from there?

charlie

Jacob: I am experiencing the exact same problem with Snow Leopard 10.6.8 completely up to date.

If I boot up and the shut down without working with my computer, the shut down works fine. After some Xcode usage, the computer will stall showing the spinning gray wheel on a the blue shutdown background.

I believe this is a software problem, not a hardware one, probably cause by something we have installed. Jacob, do you have Parallels installed? It shows up in the logs, and may be the culprit.

These are the logs for my latest failed shutdown attempt:

system.log

---

Jul 12 22:51:06 baltimore com.apple.launchd.peruser.501[241] ([0x0-0xb00b].com.kainjow.BootChamp[282]): Exited: Killed

Jul 12 22:51:06 baltimore com.apple.launchd.peruser.501[241] (com.apple.AirPortBaseStationAgent[265]): Exited: Killed

Jul 12 22:51:09 baltimore loginwindow[114]: DEAD_PROCESS: 114 console

Jul 12 22:51:09 baltimore auditd[75120]: Auditing enabled

Jul 12 22:51:09 baltimore auditd[75120]: Got low space trigger

Jul 12 22:51:09 baltimore auditd[75120]: auditd_read_dirs(): all audit log directories over soft limit

Jul 12 22:51:09 baltimore auditd[75120]: renamed /var/audit/20110712204814.not_terminated to /var/audit/20110712204814.20110712205109

Jul 12 22:51:09 baltimore auditd[75120]: New audit file is /var/audit/20110712205109.not_terminated

Jul 12 22:51:09 baltimore _locationd[75126]: audit warning: closefile /var/audit/20110712204814.20110712205109

Jul 12 22:51:09 baltimore _locationd[75125]: audit warning: allsoft

Jul 12 22:51:09 baltimore _locationd[75124]: audit warning: soft /var/audit

Jul 12 22:51:13 baltimore shutdown[75128]: reboot by user:

Jul 12 22:51:13 baltimore shutdown[75128]: SHUTDOWN_TIME: 1310503873 368648

Jul 12 22:51:13 baltimore Parallels[75131]: Stopping Parallels Dispatcher Service

Jul 12 22:51:14 baltimore Parallels[75137]: Stopping Parallels networking

Jul 12 22:51:18 baltimore prl_naptd[204]: Exiting Parallels Network Daemon

Jul 12 22:51:21 baltimore Parallels[75190]: Unloading kernel extension prl_netbridge.kext

Jul 12 22:51:21 baltimore Parallels[75213]: Failed to unload kernel extension prl_netbridge.kext

Jul 12 22:51:21 baltimore Parallels[75218]: Unloading kernel extension prl_vnic.kext

Jul 12 22:51:22 baltimore Parallels[75241]: Failed to unload kernel extension prl_vnic.kext

Jul 12 22:51:22 baltimore Parallels[75244]: Parallels Networking was stopped

Jul 12 22:51:22 baltimore DirectoryService[11]: BUG in libdispatch: 10K540 - 1960 - 0x10004004

Jul 12 22:51:23 baltimore WindowServer[165]: hidd died. Reestablishing connection.

Jul 12 22:51:23 baltimore mDNSResponder[18]: mDNSResponder mDNSResponder-258.21 (May 26 2011 14:40:13) stopping

Jul 12 22:51:23 baltimore WindowServer[165]: Unable to create event queue via hidd: (0x10000003)

Jul 12 22:51:24 baltimore prl_naptd[266]: Exiting Parallels Network Daemon

Jul 12 22:51:24 baltimore hdiejectd[36536]: processSIGTERM_DA: calling exit(0)

kernel.log

---

Jul 12 22:51:06 baltimore kernel[0]: systemShutdown true

Jul 12 22:51:10 baltimore kernel[0]: Warning: audit space low (< 5% free)on audit log file-system

Jul 12 22:51:11 baltimore kernel[0]: systemShutdown true

Jul 12 22:51:12 baltimore kernel[0]: Warning: audit space low (< 5% free)on audit log file-system

Jul 12 22:51:14 baltimore kernel[0]: Kext loading now disabled.

Jul 12 22:51:14 baltimore kernel[0]: Kext unloading now disabled.

Jul 12 22:51:14 baltimore kernel[0]: Kext autounloading now disabled.

Jul 12 22:51:14 baltimore kernel[0]: Kernel requests now disabled.

Jul 12 22:51:14 baltimore kernel[0]: Warning: audit space low (< 5% free)on audit log file-system

Jul 12 22:51:21 baltimore kernel[0]: com.parallels.kext.prlnet 6.0.11994.637263 is unloading.

Jul 12 22:51:21 baltimore kernel[0]: Kext unloading is disabled (com.parallels.kext.prl_netbridge).

Jul 12 22:51:21: --- last message repeated 2 times ---

Jul 12 22:51:21 baltimore kernel[0]: com.parallels.kext.vnic 6.0.11994.637263 is unloading.

Jul 12 22:51:21 baltimore kernel[0]: Failed to delete address of interface: 102

Jul 12 22:51:21: --- last message repeated 1 time ---

Jul 12 22:51:21 baltimore kernel[0]: com_parallels_kext_prl_vnic_bus: wait for detach for 0

Jul 12 22:51:21 baltimore kernel[0]: com_parallels_kext_prl_vnic_bus::detach_handler for 0

Jul 12 22:51:21 baltimore kernel[0]: com_parallels_kext_prl_vnic_bus: detached 0

Jul 12 22:51:21 baltimore kernel[0]: com_parallels_kext_prl_vnic: destroyed vnic0

Jul 12 22:51:21 baltimore kernel[0]: Failed to delete address of interface: 102

Jul 12 22:51:21: --- last message repeated 1 time ---

Jul 12 22:51:21 baltimore kernel[0]: com_parallels_kext_prl_vnic_bus: wait for detach for 1

Jul 12 22:51:21 baltimore kernel[0]: com_parallels_kext_prl_vnic_bus::detach_handler for 1

Jul 12 22:51:21 baltimore kernel[0]: com_parallels_kext_prl_vnic_bus: detached 1

Jul 12 22:51:21 baltimore kernel[0]: com_parallels_kext_prl_vnic: destroyed vnic1

Jul 12 22:51:21 baltimore kernel[0]: Kext unloading is disabled (com.parallels.kext.prl_vnic).

Any other light on this matter would be welcomed. Thanks!

Unfortunatly the spinning wheel at shut down persists also in OS 10.7 (LION). I had some hope and now I am very sad...

Rolf ;-(

iMac 21.5" late 2009