Through analyse the detailed startup logs with FC connection & without FC connection, found some information from the logs with FC where the server hanges.
02.10.12 18:02:32,388 mds (Error) ImportServer: <MDSImporterWrangler: 0x7ff36aa112b0> still waiting for plug-in info from mdworker
02.10.12 18:02:32,838 mds (Error) ImportServer: <MDSImporterWrangler: 0x7ff36ac16c40> still waiting for plug-in info from mdworker
02.10.12 18:04:34,549 hidd Timeout waiting for IOKit to be quiet
02.10.12 18:08:34,560 WindowServer Timeout waiting for IOKit to be quiet
Google give some details about this this two issues. so suppose there maybe two reasons cause this issue:
1.mac is INDEXing for OS Filesystem
2.the driver of FC HBA may be installed mismatching
The I/O Kit is a collection of system frameworks, libraries, tools, and other resources for creating device drivers in OS X. It is based on an object-oriented programming model implemented in a restricted form of C++ that omits features unsuitable for use within a multithreaded kernel. By modeling the hardware connected to an OS X system and abstracting common functionality for devices in particular categories, the I/O Kit streamlines the process of device-driver development.
mdworker is short for ‘metadata server worker’ and if you’re still confused don’t feel bad. mdworker is basically the core technology behind Mac OS X’s awesome search engine Spotlight, it spiders meta data from your Mac and its files and creates a readable index so that you can find things practically instantaneously via Spotlight (command-spacebar). Here are some common questions and answers regarding mdworker, inspired by my recent switcher friend Daryl, who tweeted me asking why mdworker is taking up so much CPU.
What is mdworker?
As mentioned above, mdworker is part of Spotlight, which is basically a search engine for your Mac (think Google but locally, for your own files).
mdworker is slowing down my Mac with 60% CPU usage!
Yes, mdworker will sometimes cause your Mac to be slow and have high CPU usage, this is totally normal. You should just let it run until it’s finished, and CPU usage will be back to normal.
How long does mdworker take to finish?
This is entirely dependent on the last time that your Mac filesystem was indexed and the amount of new files since indexing. If you just plugged in a loaded external hard drive, expect it to take a while. 15 minutes to well over an hour are not uncommon amounts of time for mdworker to run.
Should I kill mdworker? What happens if I kill mdworker?
No you shouldn’t kill mdworker, because it’s doing you a service by indexing your Macs contents. If you do kill mdworker, your Mac filesystem will not be completely indexed and it’s searchability will be greatly reduced until mdworker runs again and completes a full indexing. There is no serious problem with killing mdworker, it’s just not recommended.
How can I stop mdworker or disable mdworker?
Since mdworker is part of Spotlight, you’ll have to disable Spotlight to disable mdworker. Again, this is not recommended, but if you want to disable mdworker here’s a how-to guide:
How to Disable Spotlight
What about mds? Is this tied to mdworker?
Yes, mds is the parent metadata server that runs the child process mdworker, the two usually run concurrently. You can read specifically about mds and Mac OS for more information.