Disk prob
ok so my disk utilitys said this
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Invalid leaf record count
(It should be 796836 instead of 796837)
796837
,"Checking multi-linked files.",0)
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Volume Bit Map needs minor repair
Checking volume information.
Invalid volume free block count
(It should be 1153142 instead of 1150964)
The volume the G-5 needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
and then a pop up poped up and ssaid that it had quite cuz of some thing whats up???
i-mac g5 Mac OS X (10.4.8)
Hi dast357;
If you have the protection plan, they should. That is why you paid for it.
Do make sure you have current backups because there is a good chance they will replace the drive for you.
Allan
Similar Messages
-
HARD DISK PROBS / TIME MACHINE not behaving with TC ? READ THIS!!!!
I had many probs with the hard disk and now have a happy healthy TC working great with time machine, so I though I'd share my experiences with others hoping it will save you my huge pain !
i,
I've spent hours and hours trying to get the harddisk to work properly. Set-up was easy-peasy and the Airport works great for the internet. However, when trying to use time-machine and the hard disk it was a nightmare !!! Each attempt at the back-up failed after about 4 gig with a 'unable to mount volume' error. If I re-tried, it failed. Following some of the tips on the forums, I deleted the back-up file created by time machine on the hard drive and the initial back-up started successfully but failed after about 4 gig again (I had 96 gig to back-up). There are various fixes flying around -
*_ensure you have a name for your computer - should be short and no spaces or funny characters. Same goes for your name of the timecapsule. Some people are saying you should use an ethernet cable for your first back-up but that should not matter at all.*_ I took mine back to the apple store in the end - a mac genius downloaded all the latest patches (only came out 19th march) for the time-capsule firmware, time machine software and airport express. Still didn't work, so conclusion was the time-capsule was knackered !!! SO MY RECOMMENDATION IS TO GET APPLE TO REPLACE IT BUT MAKE SURE YOU TRY THE ABOVE FIRST.
New time-capsule was attached to my imac, started up great first time. My initial back-up ran through perfectly first time through wireless - it took 15 hours but I did have 96 gig to back-up. time machine sees this no problem so it looks like everything is fine. _*I ALSO NOTICED THAT THE TC WAS MUCH MORE QUIET AND LESS HOT.*_
Good luck !!Hi,
Well, The external drive you have problem with is from a third party vendor :-)
I just looked up your model and we need to start over.
How do you connect it to your computer?
Is it plugged in to the router via ethernet and you access it over WiFi.
The drive needs to be setup as per supplied instructions.
The manufacturer says it is Time Machine compatible but from my experience I know this is not switched on by default.
The main reason why you cannot access it is you basically have to set it up for your use and most likely authenticate to it.
At this stage I'm quite sure there is no much wrong with that drive. It just need setting up.
Let me know if you have any instructions from Seagate which you can follow. -
Starting from a Snow leopard disk prob
I just upgraded to Lion, I have another startup disk that is bootable into 10.6 when I changed the startup disk from Lion to SLeopard I got the chime and the dreaded black "you must restart msg" I tried o to hold thenPwr button down got the chime again and the same problem.
Any help.
RdDate/Time: 2011-12-12 18:24:12 -0500
OS Version: 10.7.2 (Build 11C74)
Architecture: x86_64
Report Version: 9
Command: No Target
Path: No Target
Version: ??? (???)
Parent: kernel_task [0]
PID: 0
Event: shutdown stall
Duration: 0.94s
Steps: 10 (100ms sampling interval)
Pageins: 4
Pageouts: 0
Process: aksusbd [142]
Path: /usr/libexec/aksusbd
Architecture: i386
UID: 0
Thread 0x3ad
User stack:
10__select_nocancel + 10 (in libsystem_kernel.dylib) [0x95706b5e]
Kernel stack:
10 wakeup + 1024 (in mach_kernel)[0x575a00]
Thread 0x3b2 DispatchQueue 1701273966
User stack:
10 _dispatch_mgr_thread + 53 (inlibdispatch.dylib) [0x9c93b6a7]
10 kevent + 10 (in libsystem_kernel.dylib) [0x9570790a]
Kernel stack:
10 kqueue_scan + 480 (in mach_kernel)[0x5596e0]
Thread 0x3b0
User stack:
10thread_start + 34 (in libsystem_c.dylib) [0x9c9bb6de]
10 semaphore_wait_trap + 10 (inlibsystem_kernel.dylib) [0x95704c5e]
Kernel stack:
10semaphore_wait_continue + 0 (in mach_kernel) [0x234a50]
Thread 0x3b1
User stack:
10 ??? (inaksusbd) [0x639f]
10 CFRunLoopRun+ 129 (in CoreFoundation) [0x9b4dd611]
10 CFRunLoopRunSpecific + 332 (inCoreFoundation) [0x9b4cc8ec]
10 __CFRunLoopRun + 1428 (in CoreFoundation) [0x9b4cd214]
10 __CFRunLoopServiceMachPort + 170(in CoreFoundation) [0x9b4c40ea]
10 mach_msg_trap + 10 (inlibsystem_kernel.dylib) [0x95704c22]
Kernel stack:
10ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Binary Images:
0x1000 - 0x11fcb aksusbd ??? (???) /usr/libexec/aksusbd
0x956ee000 - 0x9570cff7 libsystem_kernel.dylib ??? (???)<124A6CE3-3934-3994-9D0A-E85A0C0BF082>/usr/lib/system/libsystem_kernel.dyl ib
0x9b492000 - 0x9b668fe3 com.apple.CoreFoundation 6.7.1 (635.15)<AC9F6462-6315-3D89-8075-D048DB4DBF7E> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x9c93a000 - 0x9c948fff libdispatch.dylib ??? (???)<B50C62AD-0B5B-34C3-A491-ECFD72ED505E>/usr/lib/system/libdispatch.dylib
0x9c95b000 - 0x9ca26fff libsystem_c.dylib ??? (???) <1B0A12B3-DAFA-31E2-8F82-E98D620E4D72>/usr/lib/system/libsystem_c.dylib
Process: dbfseventsd [392]
Path: /Library/DropboxHelperTools/*/dbfseventsd
Architecture: i386
UID: 0
Thread 0xb88
User stack:
Kernel stack:
2 lo_unix_scall + 279 (in mach_kernel)[0x2e4367]
2 unix_syscall + 539(in mach_kernel) [0x5f0f2b]
2read_nocancel + 163 (in mach_kernel) [0x585823]
2 write + 256 (in mach_kernel)[0x585090]
2 get_pathbuff+ 4047 (in mach_kernel) [0x33784f]
2 tsleep + 116 (in mach_kernel)[0x575cf4]
2 wakeup +685 (in mach_kernel) [0x5758ad]
2 thread_block + 33 (inmach_kernel) [0x22f771]
2 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
2 thread_continue + 1729(in mach_kernel) [0x22f3a1]
2machine_switch_context + 582 (in mach_kernel) [0x2cba26]
Binary Images:
0x1000 - 0x8ff7 dbfseventsd ??? (???) <6E6421C9-0E72-73AF-1821-754B84B964AF>/Library/DropboxHelperTools/*/dbfseventsd
Process: dbfseventsd [394]
Path: /Library/DropboxHelperTools/*/dbfseventsd
Architecture: i386
UID: 0
Thread 0xb8a
User stack:
2 ??? (indbfseventsd) [0x8575]
2__select_nocancel + 10 (in libsystem_kernel.dylib) [0x95706b5e]
Kernel stack:
2 wakeup + 1024 (in mach_kernel)[0x575a00]
Binary Images:
0x1000 - 0x8ff7 dbfseventsd ??? (???) <6E6421C9-0E72-73AF-1821-754B84B964AF>/Library/DropboxHelperTools/*/dbfseventsd
0x956ee000 - 0x9570cff7 libsystem_kernel.dylib ??? (???)<124A6CE3-3934-3994-9D0A-E85A0C0BF082>/usr/lib/system/libsystem_kernel.dyl ib
Process: diskarbitrationd [13]
Path: /usr/sbin/diskarbitrationd
Architecture: x86_64
UID: 0
Thread 0x14c DispatchQueue 1
User stack:
10 ??? (in diskarbitrationd)[0x10194439c]
10 ??? (indiskarbitrationd) [0x10194ae15]
10 CFRunLoopRun + 95 (in CoreFoundation) [0x7fff89e8c7ff]
10 CFRunLoopRunSpecific + 230 (inCoreFoundation) [0x7fff89e7cae6]
10 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff89e7d2d4]
10 __CFRunLoopServiceMachPort +188 (in CoreFoundation) [0x7fff89e74b6c]
10 mach_msg_trap + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7867a]
Kernel stack:
10ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x151 DispatchQueue 2
User stack:
10 _dispatch_mgr_thread + 54 (inlibdispatch.dylib) [0x7fff8e91414e]
10 kevent + 10 (in libsystem_kernel.dylib) [0x7fff8eb7a7e6]
Kernel stack:
10 kqueue_scan + 480 (in mach_kernel)[0x5596e0]
Thread 0x6e2d
User stack:
10start_wqthread + 13 (in libsystem_c.dylib) [0x7fff88bd3b85]
10 __workq_kernreturn + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7a192]
Kernel stack:
10workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
Thread 0x6e74
User stack:
10start_wqthread + 13 (in libsystem_c.dylib) [0x7fff88bd3b85]
10 __workq_kernreturn + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7a192]
Kernel stack:
10workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
Binary Images:
0x101943000 - 0x10195eff7 diskarbitrationd ??? (???)<F033F3D5-FF18-37D9-B9BF-59E6D4E30C10> /usr/sbin/diskarbitrationd
0x7fff88b82000 - 0x7fff88c5ffef libsystem_c.dylib ??? (???)<FF69F06E-0904-3C08-A5EF-536FAFFFDC22> /usr/lib/system/libsystem_c.dylib
0x7fff89e44000 - 0x7fff8a018fff com.apple.CoreFoundation 6.7.1 (635.15)<FE4A86C2-3599-3CF8-AD1A-822F1FEA820F>/System/Library/Frameworks/CoreFo undation.framework/Versions/A/CoreFoundation
0x7fff8e912000 - 0x7fff8e920fff libdispatch.dylib ??? (???)<712AAEAC-AD90-37F7-B71F-293FF8AE8723>/usr/lib/system/libdispatch.dylib
0x7fff8eb63000 - 0x7fff8eb83fff libsystem_kernel.dylib ??? (???)<C56819BB-3779-3726-B610-4CF7B3ABB6F9> /usr/lib/system/libsystem_kernel.dylib
Process: DiskWarriorDaemon [263]
Path: /Applications/Utilities/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon
Architecture: i386
UID: 501
Thread 0x96a
User stack:
10 ??? (inDiskWarriorDaemon) [0x1f61]
10??? (in DiskWarriorDaemon) [0x203a]
10 ??? (in DiskWarriorDaemon)[0x27a7]
10 ??? (inDiskWarriorDaemon) [0xd85d]
10 CFRunLoopRunInMode + 120 (in CoreFoundation) [0x9b4cc798]
10 CFRunLoopRunSpecific + 332 (inCoreFoundation) [0x9b4cc8ec]
10 __CFRunLoopRun + 1428 (inCoreFoundation) [0x9b4cd214]
10 __CFRunLoopServiceMachPort+ 170 (in CoreFoundation) [0x9b4c40ea]
10 mach_msg_trap + 10 (inlibsystem_kernel.dylib) [0x95704c22]
Kernel stack:
10 ipc_mqueue_receive_continue+ 0 (in mach_kernel) [0x215060]
Thread 0x98a DispatchQueue1701273966
User stack:
10 _dispatch_mgr_thread + 53 (inlibdispatch.dylib) [0x9c93b6a7]
10 kevent + 10 (in libsystem_kernel.dylib) [0x9570790a]
Kernel stack:
10 kqueue_scan + 480 (in mach_kernel)[0x5596e0]
Binary Images:
0x1000 - 0x14fd7 DiskWarriorDaemon ??? (???)/Applications/Utilities/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon
0x956ee000 - 0x9570cff7 libsystem_kernel.dylib ??? (???)<124A6CE3-3934-3994-9D0A-E85A0C0BF082>/usr/lib/system/libsystem_kernel.dyl ib
0x9b492000 - 0x9b668fe3 com.apple.CoreFoundation 6.7.1 (635.15)<AC9F6462-6315-3D89-8075-D048DB4DBF7E>/System/Library/Frameworks/CoreFo undation.framework/Versions/A/CoreFoundation
0x9c93a000 - 0x9c948fff libdispatch.dylib ??? (???)<B50C62AD-0B5B-34C3-A491-ECFD72ED505E>/usr/lib/system/libdispatch.dylib
Process: launchd [1]
Path: /sbin/launchd
Architecture: unknown
UID: 0
Thread0x10a DispatchQueue 1
User stack:
10 ??? [0x1099b625c]
10 ??? [0x1099bbcaa]
10 ??? [0x1099be33b]
10 ??? [0x7fff8eb7867a]
Kernel stack:
10 ipc_mqueue_receive_continue + 0 (inmach_kernel) [0x215060]
Thread0x136
User stack:
10 ??? [0x7fff88bd3b75]
10 ??? [0x7fff88bd08bf]
10 ??? [0x7fff8eb79df2]
Kernel stack:
10 wakeup + 1024 (in mach_kernel)[0x575a00]
Thread 0x137
User stack:
10 ???[0x7fff88bd3b75]
10 ???[0x7fff88bd08bf]
10 ???[0x1099bbd6a]
10 ???[0x7fff88b86c2c]
10 ???[0x7fff8eb79e42]
Kernel stack:
10 semaphore_wait_continue + 0 (inmach_kernel) [0x234a50]
BinaryImages:
Process: Router Manager [400]
Path: /Library/Application Support/Belkin/*/Router Manager
Architecture: i386
UID: 501
Thread 0xbd0
User stack:
10 start + 41(in Router Manager) [0x2029]
10_start + 209 (in Router Manager) [0x20fb]
10 main + 877 (in Router Manager)[0x2b2b]
10PluginPipe::~PluginPipe() + 35 (in Router Manager) [0x11c47]
10 PluginPipe::stop() + 46 (inRouter Manager) [0x10fe2]
10 boost::thread::join() + 189 (in Router Manager) [0x42f1d]
10 pthread_cond_wait + 48 (inlibsystem_c.dylib) [0x9c96382a]
10 __psynch_cvwait + 10 (inlibsystem_kernel.dylib) [0x9570683e]
Kernel stack:
10lo_unix_scall + 279 (in mach_kernel) [0x2e4367]
10 unix_syscall + 539 (in mach_kernel)[0x5f0f2b]
10 psynch_cvwait +1967 (in mach_kernel) [0x5c38bf]
10 ksyn_block_thread_locked + 77 (in mach_kernel) [0x5bed6d]
10 thread_block + 33 (inmach_kernel) [0x22f771]
10 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
10 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
Thread 0xbf7 DispatchQueue 1701273966
User stack:
10 _dispatch_mgr_thread + 53 (inlibdispatch.dylib) [0x9c93b6a7]
10 kevent + 10 (in libsystem_kernel.dylib) [0x9570790a]
Kernel stack:
10 kqueue_scan + 480 (in mach_kernel)[0x5596e0]
Thread 0xc1c
User stack:
10 thread_start+ 34 (in libsystem_c.dylib) [0x9c9bb6de]
10 _pthread_start + 335 (inlibsystem_c.dylib) [0x9c9b7ed9]
10 __select + 10 (in libsystem_kernel.dylib) [0x95706b42]
Kernel stack:
10 wakeup + 1024 (in mach_kernel)[0x575a00]
Thread 0xc40
User stack:
10thread_start + 34 (in libsystem_c.dylib) [0x9c9bb6de]
10 _pthread_start + 335 (inlibsystem_c.dylib) [0x9c9b7ed9]
10 thread_proxy + 141 (in Router Manager) [0x426cd]
10 boost::_bi::bind_t<void,boost::_mfi::mf0<void, PluginPipe>,boost::_bi::list1<boost::_bi::value<PluginPipe*> >>::operator()() + 43 (in Router Manager) [0x173b5]
10 PluginPipe::run() + 20 (inRouter Manager) [0x11058]
10 XmlClient::run() + 489 (in Router Manager) [0x41e1]
10 boolboost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex>> (boost::unique_lock<boost::mutex>&, boost::xtime const&) + 48(in Router Manager) [0x9d42]
10 boolboost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex>> (boost::unique_lock<boost::mutex>&, boost::posix_time::ptimeconst&) + 91 (in Router Manager) [0x9c87]
10 pthread_cond_timedwait +47 (in libsystem_c.dylib) [0x9c9637f5]
10 __psynch_cvwait + 10 (inlibsystem_kernel.dylib) [0x9570683e]
Kernel stack:
10lo_unix_scall + 279 (in mach_kernel) [0x2e4367]
10 unix_syscall + 539 (in mach_kernel)[0x5f0f2b]
10 psynch_cvwait +1967 (in mach_kernel) [0x5c38bf]
10 ksyn_block_thread_locked + 77 (inmach_kernel) [0x5bed6d]
10 thread_block + 33 (in mach_kernel) [0x22f771]
10 thread_block_reason + 331 (inmach_kernel) [0x22f62b]
10 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
10 machine_switch_context +582 (in mach_kernel) [0x2cba26]
Thread 0xc41
User stack:
10 thread_start + 34 (in libsystem_c.dylib)[0x9c9bb6de]
10 _pthread_start+ 335 (in libsystem_c.dylib) [0x9c9b7ed9]
10 thread_proxy + 141 (in RouterManager) [0x426cd]
10boost::_bi::bind_t<void, boost::_mfi::mf0<void, PluginPipe>,boost::_bi::list1<boost::_bi::value<PluginPipe*> >>::operator()() + 43 (in Router Manager) [0x173b5]
10 PluginPipe::PowerNotificatoinCallbackRunLoop()+ 134 (in Router Manager) [0x111e2]
10 CFRunLoopRun + 129 (inCoreFoundation) [0x9b4dd611]
10 CFRunLoopRunSpecific + 332 (in CoreFoundation) [0x9b4cc8ec]
10 __CFRunLoopRun + 1428 (inCoreFoundation) [0x9b4cd214]
10__CFRunLoopServiceMachPort + 170 (in CoreFoundation) [0x9b4c40ea]
10 mach_msg_trap + 10 (inlibsystem_kernel.dylib) [0x95704c22]
Kernel stack:
10ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x6eaa
User stack:
10start_wqthread + 30 (in libsystem_c.dylib) [0x9c9bb6fe]
10 __workq_kernreturn + 10 (inlibsystem_kernel.dylib) [0x9570702e]
Kernel stack:
10workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
Thread 0x6f04
User stack:
Kernelstack:
10 workqueue_exit + 1232(in mach_kernel) [0x5c5ea0]
Binary Images:
0x1000- 0x126fff com.Affinegy.Router_Manager Router Manager4.0.0 © 2009 Affinegy, Inc. (4.0.0)<9F5F3D7F-0354-4DC7-0400-D5059481A68C> /Library/ApplicationSupport/Belkin/*/Router Manager
0x956ee000 - 0x9570cff7 libsystem_kernel.dylib ??? (???)<124A6CE3-3934-3994-9D0A-E85A0C0BF082>/usr/lib/system/libsystem_kernel.dyl ib
0x9b492000 - 0x9b668fe3 com.apple.CoreFoundation 6.7.1 (635.15)<AC9F6462-6315-3D89-8075-D048DB4DBF7E>/System/Library/Frameworks/CoreFo undation.framework/Versions/A/CoreFoundation
0x9c93a000 - 0x9c948fff libdispatch.dylib ??? (???)<B50C62AD-0B5B-34C3-A491-ECFD72ED505E>/usr/lib/system/libdispatch.dylib
0x9c95b000 - 0x9ca26fff libsystem_c.dylib ??? (???) <1B0A12B3-DAFA-31E2-8F82-E98D620E4D72>/usr/lib/system/libsystem_c.dylib
Process: securityd [27]
Path: /usr/sbin/securityd
Architecture: x86_64
UID: 0
Thread 0x15f DispatchQueue 1
User stack:
10 start + 52 (in securityd)[0x100b428f4]
10 main + 2179(in securityd) [0x100b58df4]
10 Security::MachPlusPlus::MachServer::run(unsigned long, int) + 103 (insecurityd) [0x100b95b1b]
10Security::MachPlusPlus::MachServer::runServerThread(bool) + 676 (in securityd)[0x100b2e0e2]
10mach_msg_overwrite_trap + 10 (in libsystem_kernel.dylib) [0x7fff8eb78686]
Kernel stack:
10 ipc_mqueue_receive_continue + 0 (inmach_kernel) [0x215060]
Thread0x212 DispatchQueue 2
User stack:
10 _dispatch_mgr_thread + 54 (inlibdispatch.dylib) [0x7fff8e91414e]
10 kevent + 10 (in libsystem_kernel.dylib) [0x7fff8eb7a7e6]
Kernel stack:
10 kqueue_scan + 480 (in mach_kernel)[0x5596e0]
Thread 0x19f
User stack:
10thread_start + 13 (in libsystem_c.dylib) [0x7fff88bd3b75]
10 _pthread_start + 335 (inlibsystem_c.dylib) [0x7fff88bd08bf]
10 Security::Thread::runner(void*) + 104 (in securityd)[0x100b2dbda]
10AuditMonitor::action() + 97 (in securityd) [0x100b79153]
10 au_sdev_read_aia + 79 (inlibbsm.0.dylib) [0x7fff85d5d091]
10 fgetc + 50 (inlibsystem_c.dylib) [0x7fff88bb8dee]
10 __srget + 20 (inlibsystem_c.dylib) [0x7fff88c185e8]
10 __srefill1 + 30 (inlibsystem_c.dylib) [0x7fff88bcd166]
10 __read_nocancel + 10 (inlibsystem_kernel.dylib) [0x7fff8eb79d52]
Kernel stack:
10lo64_unix_scall + 23 (in mach_kernel) [0x2e4977]
10 unix_syscall64 + 554 (in mach_kernel)[0x5f15fa]
10 read_nocancel +163 (in mach_kernel) [0x585823]
10 write + 256 (in mach_kernel) [0x585090]
10 utf8_encodelen + 4080 (inmach_kernel) [0x3201b0]
10 VNOP_READ + 82 (in mach_kernel) [0x32a782]
10 spec_read + 110 (inmach_kernel) [0x33cd7e]
10 audit_session_setaia + 2388 (in mach_kernel) [0x5426d4]
10 _audit_cv_wait_sig + 50 (inmach_kernel) [0x5354c2]
10 msleep + 165 (inmach_kernel) [0x575e25]
10 wakeup + 287 (inmach_kernel) [0x57571f]
10 lck_mtx_sleep + 79(in mach_kernel) [0x227bcf]
10 thread_block +33 (in mach_kernel) [0x22f771]
10thread_block_reason + 331 (in mach_kernel) [0x22f62b]
10thread_continue + 1729 (in mach_kernel) [0x22f3a1]
10machine_switch_context + 582 (in mach_kernel) [0x2cba26]
Thread 0x6a63
User stack:
10thread_start + 13 (in libsystem_c.dylib) [0x7fff88bd3b75]
10 _pthread_start + 335 (inlibsystem_c.dylib) [0x7fff88bd08bf]
10 Security::Thread::runner(void*) + 104 (in securityd)[0x100b2dbda]
10Security::MachPlusPlus::MachServer::LoadThread::action() + 48 (in securityd)[0x100b2dc7c]
10Security::MachPlusPlus::MachServer::runServerThread(bool) + 676 (in securityd)[0x100b2e0e2]
10mach_msg_overwrite_trap + 10 (in libsystem_kernel.dylib) [0x7fff8eb78686]
Kernel stack:
10 ipc_mqueue_receive_continue + 0 (inmach_kernel) [0x215060]
Thread0x6bd4
User stack:
10 thread_start + 13 (in libsystem_c.dylib)[0x7fff88bd3b75]
10_pthread_start + 335 (in libsystem_c.dylib) [0x7fff88bd08bf]
10 Security::Thread::runner(void*) +104 (in securityd) [0x100b2dbda]
10 Security::MachPlusPlus::MachServer::LoadThread::action() + 48 (insecurityd) [0x100b2dc7c]
10 Security::MachPlusPlus::MachServer::runServerThread(bool) + 676 (insecurityd) [0x100b2e0e2]
10 mach_msg_overwrite_trap + 10 (in libsystem_kernel.dylib) [0x7fff8eb78686]
Kernel stack:
10 ipc_mqueue_receive_continue + 0 (inmach_kernel) [0x215060]
Thread0x6f01
User stack:
10 start_wqthread + 13 (inlibsystem_c.dylib) [0x7fff88bd3b85]
10 __workq_kernreturn + 10 (in libsystem_kernel.dylib)[0x7fff8eb7a192]
Kernel stack:
10 workqueue_exit + 1808 (in mach_kernel)[0x5c60e0]
Thread 0x6f08
User stack:
Kernelstack:
10 workqueue_exit + 1232(in mach_kernel) [0x5c5ea0]
Binary Images:
0x100b1f000 - 0x100c09fff securityd ??? (???)<B750B226-98DB-39E9-A3E5-14B8D36882D7> /usr/sbin/securityd
0x7fff85d50000 - 0x7fff85d62ff7 libbsm.0.dylib ??? (???)<349BB16F-75FA-363F-8D98-7A9C3FA90A0D> /usr/lib/libbsm.0.dylib
0x7fff88b82000 - 0x7fff88c5ffef libsystem_c.dylib ??? (???)<FF69F06E-0904-3C08-A5EF-536FAFFFDC22>/usr/lib/system/libsystem_c.dylib
0x7fff8e912000 - 0x7fff8e920fff libdispatch.dylib??? (???) <712AAEAC-AD90-37F7-B71F-293FF8AE8723> /usr/lib/system/libdispatch.dylib
0x7fff8eb63000 - 0x7fff8eb83fff libsystem_kernel.dylib ??? (???)<C56819BB-3779-3726-B610-4CF7B3ABB6F9> /usr/lib/system/libsystem_kernel.dylib
Process: spindump [1942]
Path: /usr/sbin/spindump
Architecture: x86_64
UID: 0
Thread 0x6ef4
User stack:
10 ??? (inspindump) [0x10215b814]
10 ???(in spindump) [0x10215c4b2]
10 dispatch_main + 43 (in libdispatch.dylib) [0x7fff8e914c20]
10 pthread_exit + 30 (inlibsystem_c.dylib) [0x7fff88bd227d]
10 _pthread_exit + 142 (inlibsystem_c.dylib) [0x7fff88bd1f7c]
10 _pthread_tsd_cleanup + 230 (inlibsystem_c.dylib) [0x7fff88c16942]
10 _dispatch_queue_cleanup2 +88 (in libdispatch.dylib) [0x7fff8e91686d]
10 sleep$NOCANCEL + 61 (inlibsystem_c.dylib) [0x7fff88c23ae5]
10__semwait_signal_nocancel + 10 (in libsystem_kernel.dylib)[0x7fff8eb79e56]
Kernel stack:
10 semaphore_wait_continue + 0 (inmach_kernel) [0x234a50]
Thread0x6f15 DispatchQueue 2
User stack:
10 _dispatch_mgr_thread + 54 (inlibdispatch.dylib) [0x7fff8e91414e]
10 kevent + 10 (in libsystem_kernel.dylib) [0x7fff8eb7a7e6]
Kernel stack:
9 lo64_unix_scall + 23 (in mach_kernel)[0x2e4977]
9 unix_syscall64 +554 (in mach_kernel) [0x5f15fa]
9 kevent + 114 (in mach_kernel) [0x55b112]
9 kevent_description + 1875 (inmach_kernel) [0x55af63]
9kqueue_scan + 228 (in mach_kernel) [0x5595e4]
9 thread_block_parameter + 32 (inmach_kernel) [0x22f740]
9 thread_block_reason + 306 (in mach_kernel) [0x22f612]
9 thread_cancel_timer + 640(in mach_kernel) [0x22e110]
9 processor_idle + 181 (inmach_kernel) [0x22d335]
9 machine_idle + 206 (inmach_kernel) [0x2cfbce]
1kqueue_scan + 480 (in mach_kernel) [0x5596e0]
Thread 0x6f16 DispatchQueue 6
User stack:
10 _dispatch_sig_thread + 45 (inlibdispatch.dylib) [0x7fff8e916954]
10 __sigsuspend_nocancel + 10 (in libsystem_kernel.dylib)[0x7fff8eb7a022]
Kernel stack:
10 wakeup + 1024 (in mach_kernel)[0x575a00]
Thread<multiple> DispatchQueue 18
User stack:
10start_wqthread + 13 (in libsystem_c.dylib) [0x7fff88bd3b85]
10 _pthread_wqthread + 316 (inlibsystem_c.dylib) [0x7fff88bd23da]
10 _dispatch_worker_thread2 + 198 (in libdispatch.dylib)[0x7fff8e914760]
10_dispatch_queue_invoke + 54 (in libdispatch.dylib) [0x7fff8e914f66]
10 _dispatch_queue_drain + 210 (inlibdispatch.dylib) [0x7fff8e9150d4]
10 _dispatch_queue_invoke + 71(in libdispatch.dylib) [0x7fff8e914f77]
10 _dispatch_source_invoke +635 (in libdispatch.dylib) [0x7fff8e9182b6]
10 __syscall + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7a09a]
Kernel stack:
10lo64_unix_scall + 23 (in mach_kernel) [0x2e4977]
10 unix_syscall64 + 554 (in mach_kernel)[0x5f15fa]
10 stack_snapshot+ 104 (in mach_kernel) [0x545698]
10 stack_snapshot2 + 160 (in mach_kernel) [0x545580]
Thread 0x6f28
User stack:
10start_wqthread + 13 (in libsystem_c.dylib) [0x7fff88bd3b85]
10 __workq_kernreturn + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7a192]
Kernel stack:
10workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
Thread 0x6f29
User stack:
10start_wqthread + 13 (in libsystem_c.dylib) [0x7fff88bd3b85]
10 __workq_kernreturn + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7a192]
Kernel stack:
10workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
Thread 0x6f14 DispatchQueue 13
User stack:
8 start_wqthread + 13 (inlibsystem_c.dylib) [0x7fff88bd3b85]
8 _pthread_wqthread + 316 (in libsystem_c.dylib) [0x7fff88bd23da]
8 _dispatch_worker_thread2 + 198 (inlibdispatch.dylib) [0x7fff8e914760]
8 _dispatch_queue_invoke + 54 (inlibdispatch.dylib) [0x7fff8e914f66]
8 _dispatch_queue_drain + 264 (inlibdispatch.dylib) [0x7fff8e91510a]
8_dispatch_call_block_and_release + 18 (in libdispatch.dylib)[0x7fff8e9138ba]
8??? (in spindump) [0x1021615a8]
8 ??? (in spindump)[0x102160723]
8??? (in spindump) [0x102161961]
8_dispatch_barrier_sync_f_invoke + 33 (in libdispatch.dylib)[0x7fff8e915aad]
8 ??? (in spindump) [0x102161b0d]
8CSSymbolicatorCreateWithPidFlagsAndNotification + 84 (in CoreSymbolication)[0x7fff8ec67945]
8 CSCppMachTask::symbol_owners(bool, unsigned int) + 90 (inCoreSymbolication) [0x7fff8ec3aa8e]
8CSCppDyld::symbol_owner(CSCppMachTaskContainer const&, unsigned long long, bool,unsigned int) + 62 (in CoreSymbolication) [0x7fff8ec3abd2]
8CSCppTaskMemory::CSCppTaskMemory(CSCppMachTaskContainer const&, bool) + 101(in CoreSymbolication) [0x7fff8ec3adf9]
8 task_suspend+ 71 (in libsystem_kernel.dylib) [0x7fff8eb72c3e]
8mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8eb7867a]
Kernel stack:
8 lo64_mach_scall + 23 (in mach_kernel)[0x2e4997]
8 thread_set_child +407 (in mach_kernel) [0x2b7307]
8 mach_msg_overwrite_trap + 219 (in mach_kernel) [0x21b1cb]
8 ipc_kmsg_send + 83 (in mach_kernel)[0x213fd3]
8ipc_kobject_server + 310 (in mach_kernel) [0x222d06]
8 task_server_routine + 3156 (inmach_kernel) [0x25d374]
8 task_suspend + 204 (in mach_kernel) [0x237bdc]
8 thread_wait + 349 (inmach_kernel) [0x2303ad]
8 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
8 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
8machine_switch_context + 582 (in mach_kernel) [0x2cba26]
Thread 0x6f2b
User stack:
2 thread_start+ 13 (in libsystem_c.dylib) [0x7fff88bd3b75]
2_pthread_start + 335 (in libsystem_c.dylib) [0x7fff88bd08bf]
2 cleaner_thread_main(void*) + 36 (inCoreSymbolication) [0x7fff8ec56f63]
2 __semwait_signal + 10 (inlibsystem_kernel.dylib) [0x7fff8eb79e42]
Kernel stack:
2 semaphore_wait_continue+ 0 (in mach_kernel) [0x234a50]
Thread 0x6f14
User stack:
1 start_wqthread + 13 (inlibsystem_c.dylib) [0x7fff88bd3b85]
1 __workq_kernreturn + 10 (in libsystem_kernel.dylib)[0x7fff8eb7a192]
Kernel stack:
1 lo64_unix_scall + 23 (in mach_kernel)[0x2e4977]
1 unix_syscall64 +554 (in mach_kernel) [0x5f15fa]
1 workq_kernreturn + 676 (in mach_kernel) [0x5c7304]
1 workqueue_exit + 5758 (inmach_kernel) [0x5c704e]
1thread_block + 33 (in mach_kernel) [0x22f771]
1 thread_block_reason + 306 (inmach_kernel) [0x22f612]
1 thread_cancel_timer + 640 (in mach_kernel) [0x22e110]
1 processor_idle + 181 (inmach_kernel) [0x22d335]
1 machine_idle + 206 (inmach_kernel) [0x2cfbce]
Thread0x6f27
User stack:
1 start_wqthread + 13 (inlibsystem_c.dylib) [0x7fff88bd3b85]
1 __workq_kernreturn + 10 (in libsystem_kernel.dylib)[0x7fff8eb7a192]
Kernel stack:
1 workqueue_exit + 1808 (in mach_kernel)[0x5c60e0]
Binary Images:
0x10215a000 - 0x102170ff7 spindump ??? (???)<B568C435-488D-3705-8058-83F62AD2258A> /usr/sbin/spindump
0x7fff88b82000 - 0x7fff88c5ffef libsystem_c.dylib ??? (???)<FF69F06E-0904-3C08-A5EF-536FAFFFDC22>/usr/lib/system/libsystem_c.dylib
0x7fff8e912000 - 0x7fff8e920fff libdispatch.dylib??? (???) <712AAEAC-AD90-37F7-B71F-293FF8AE8723> /usr/lib/system/libdispatch.dylib
0x7fff8eb63000 - 0x7fff8eb83fff libsystem_kernel.dylib ??? (???)<C56819BB-3779-3726-B610-4CF7B3ABB6F9>/usr/lib/system/libsystem_kernel.dyl ib
0x7fff8ec39000 - 0x7fff8eca7fff com.apple.CoreSymbolication 2.1 (66)<7CF9EF4A-262A-3009-8D42-A76F5614E372> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSy mbolication
Process: umount [1936]
Path: /sbin/umount
Architecture: x86_64
UID: 0
Thread 0x6ed2 DispatchQueue 1
User stack:
10 ??? (in umount) [0x106ce77f8]
10 ??? (in umount) [0x106ce7bc2]
10 unmount + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7af66]
Kernel stack:
10lo64_unix_scall + 23 (in mach_kernel) [0x2e4977]
10 unix_syscall64 + 554 (in mach_kernel)[0x5f15fa]
10 unmount + 251(in mach_kernel) [0x31ba2b]
10 safedounmount + 159 (in mach_kernel) [0x31b8af]
10 dounmount + 356 (in mach_kernel)[0x31b534]
9 vflush +819 (in mach_kernel) [0x30c633]
9 vnode_rele_internal + 895 (inmach_kernel) [0x30adaf]
5 vnode_rele_ext + 391 (in mach_kernel) [0x30b127]
5 ubc_msync + 227 (inmach_kernel) [0x591fc3]
4memory_object_lock_request + 220 (in mach_kernel) [0x26afac]
2memory_object_lock_page + 4723 (in mach_kernel) [0x26aba3]
1 vm_page_lookup +229 (in mach_kernel) [0x297695]
1 vm_page_lookup +206 (in mach_kernel) [0x29767e]
1 hw_lock_to + 28 (in mach_kernel)[0x2bb9ec]
1memory_object_lock_page + 2878 (in mach_kernel) [0x26a46e]
1memory_object_lock_page + 4760 (in mach_kernel) [0x26abc8]
1 memory_object_lock_request+ 64 (in mach_kernel) [0x26af10]
1 lck_rw_lock_exclusive+ 6 (in mach_kernel) [0x2bbcc6]
4 vnode_rele_ext + 504 (inmach_kernel) [0x30b198]
4 ubc_page_op + 418 (in mach_kernel) [0x591db2]
4 memory_object_destroy +40 (in mach_kernel) [0x2698d8]
4 vm_object_page_grab +4912 (in mach_kernel) [0x289830]
1 vflush + 881 (in mach_kernel)[0x30c671]
1 vfs_iterate+ 505 (in mach_kernel) [0x307fc9]
1 vnode_list_lock + 19 (inmach_kernel) [0x300c23]
1 usimple_lock + 29 (in mach_kernel) [0x2c457d]
Binary Images:
0x106ce7000 - 0x106ce8fff umount ??? (???)<0ED0E540-9302-3EC7-9B6B-B2233A6F074A> /sbin/umount
0x7fff8eb63000 - 0x7fff8eb83fff libsystem_kernel.dylib ??? (???)<C56819BB-3779-3726-B610-4CF7B3ABB6F9> /usr/lib/system/libsystem_kernel.dylib
Process: kernel_task [0]
Path: kernel_task
Architecture: i386
UID: 0
Version: Darwin Kernel Version 11.2.0: TueAug 9 20:56:15 PDT 2011;root:xnu-1699.24.8~1/RELEASE_I386
Thread 0x1
Kernel stack:
10 vm_pageout_continue + 0 (in mach_kernel)[0x295f20]
Thread 0x2
Kernel stack:
10idle_thread + 0 (in mach_kernel) [0x22cc30]
Thread 0x3
Kernel stack:
9assert_wait_deadline + 384 (in mach_kernel) [0x22fd60]
1 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
1assert_wait_deadline + 1045 (in mach_kernel) [0x22fff5]
1 thread_block_reason + 306 (inmach_kernel) [0x22f612]
1thread_cancel_timer + 640 (in mach_kernel) [0x22e110]
1 processor_idle + 181 (inmach_kernel) [0x22d335]
1 machine_idle + 206 (in mach_kernel) [0x2cfbce]
Thread 0x4
Kernel stack:
10thread_daemon_init + 288 (in mach_kernel) [0x23bc30]
Thread 0x5
Kernel stack:
10thread_create + 32 (in mach_kernel) [0x23b6e0]
Thread 0x6
Kernel stack:
10thread_call_func + 480 (in mach_kernel) [0x23e1f0]
Thread 0x7
Kernel stack:
10call_continuation + 28 (in mach_kernel) [0x2c6d0c]
10 mapping_replenish + 394 (inmach_kernel) [0x2b684a]
10thread_block + 33 (in mach_kernel) [0x22f771]
10 thread_block_reason + 331 (inmach_kernel) [0x22f62b]
10 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
10 machine_switch_context + 582(in mach_kernel) [0x2cba26]
Thread 0x8
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0xa
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0xc
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x1a
Kernel stack:
10thread_call_func + 752 (in mach_kernel) [0x23e300]
Thread 0x1b
Kernel stack:
10 wakeup +1024 (in mach_kernel) [0x575a00]
Thread 0x1d
Kernel stack:
10 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
10AppleIntelCPUPowerManagement::~AppleIntelCPUPowerManagement() + 23470 (inAppleIntelCPUPowerManagement) [0x1efbe80]
10 IOLockSleep + 39 (in mach_kernel)[0x63f2a7]
10 lck_mtx_sleep+ 79 (in mach_kernel) [0x227bcf]
10 thread_block + 33 (in mach_kernel) [0x22f771]
10 thread_block_reason + 331 (inmach_kernel) [0x22f62b]
10 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
10 machine_switch_context +582 (in mach_kernel) [0x2cba26]
Thread 0x20
Kernel stack:
10 idle_thread + 0 (in mach_kernel)[0x22cc30]
Thread 0x23
Kernel stack:
9idle_thread + 0 (in mach_kernel) [0x22cc30]
1 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
1 idle_thread + 30(in mach_kernel) [0x22cc4e]
1processor_idle + 181 (in mach_kernel) [0x22d335]
1 machine_idle + 206 (in mach_kernel)[0x2cfbce]
Thread 0x26
Kernel stack:
5idle_thread + 0 (in mach_kernel) [0x22cc30]
5 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
5 idle_thread + 30(in mach_kernel) [0x22cc4e]
5processor_idle + 181 (in mach_kernel) [0x22d335]
5 machine_idle + 206 (in mach_kernel)[0x2cfbce]
Thread 0x2b
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x65
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x6d
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x6e
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x6f
Kernel stack:
10 IOWorkLoop::threadMain()+ 0 (in mach_kernel) [0x6607d8]
Thread 0x71
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0x82
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0x85
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0x86
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0x89
Kernel stack:
9 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
1call_continuation + 28 (in mach_kernel) [0x2c6d0c]
1 IOWorkLoop::threadMain() + 97 (inmach_kernel) [0x660839]
1thread_block_parameter + 32 (in mach_kernel) [0x22f740]
1 thread_block_reason + 306 (inmach_kernel) [0x22f612]
1thread_cancel_timer + 640 (in mach_kernel) [0x22e110]
1 processor_idle + 181 (inmach_kernel) [0x22d335]
1 machine_idle + 206 (in mach_kernel) [0x2cfbce]
Thread0x8b
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0x8c
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0x9f
Kernel stack:
10 m_prepend_2 + 23184 (in mach_kernel)[0x59d400]
Thread 0xa0
Kernel stack:
10audit_worker_init + 80 (in mach_kernel) [0x544380]
Thread 0xa1
Kernel stack:
10get_aiotask + 144 (in mach_kernel) [0x549010]
Thread 0xa2
Kernel stack:
10get_aiotask + 144 (in mach_kernel) [0x549010]
Thread 0xa3
Kernel stack:
10get_aiotask + 144 (in mach_kernel) [0x549010]
Thread 0xa4
Kernel stack:
10get_aiotask + 144 (in mach_kernel) [0x549010]
Thread 0xa5
Kernel stack:
10call_continuation + 28 (in mach_kernel) [0x2c6d0c]
10 dlil_if_ref + 3518 (in mach_kernel)[0x3551de]
10 msleep + 165(in mach_kernel) [0x575e25]
10 wakeup + 287 (in mach_kernel) [0x57571f]
10 lck_mtx_sleep + 79 (inmach_kernel) [0x227bcf]
10 thread_block + 33 (in mach_kernel) [0x22f771]
10 thread_block_reason + 331(in mach_kernel) [0x22f62b]
10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
10 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
Thread 0xa6
Kernel stack:
10call_continuation + 28 (in mach_kernel) [0x2c6d0c]
10 dlil_init + 1292 (in mach_kernel)[0x355d9c]
10 msleep + 165(in mach_kernel) [0x575e25]
10 wakeup + 287 (in mach_kernel) [0x57571f]
10 lck_mtx_sleep + 79 (inmach_kernel) [0x227bcf]
10 thread_block + 33 (in mach_kernel) [0x22f771]
10 thread_block_reason + 331(in mach_kernel) [0x22f62b]
10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
10 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
Thread 0xa7
Kernel stack:
10call_continuation + 28 (in mach_kernel) [0x2c6d0c]
10 utun_register_control + 56899 (inmach_kernel) [0x384b73]
10tsleep + 116 (in mach_kernel) [0x575cf4]
10 wakeup + 685 (in mach_kernel)[0x5758ad]
10thread_block + 33 (in mach_kernel) [0x22f771]
10 thread_block_reason + 331 (inmach_kernel) [0x22f62b]
10 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
10 machine_switch_context +582 (in mach_kernel) [0x2cba26]
Thread 0xaa
Kernel stack:
10 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
10 bpf_validate +25673 (in mach_kernel) [0x34cd59]
10 msleep + 165 (in mach_kernel) [0x575e25]
10 wakeup + 287 (in mach_kernel)[0x57571f]
10 lck_mtx_sleep+ 79 (in mach_kernel) [0x227bcf]
10 thread_block + 33 (inmach_kernel) [0x22f771]
10 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
10 machine_switch_context + 582 (inmach_kernel) [0x2cba26]
Thread0xab
Kernel stack:
10 sockwall_gc_thread + 0 (in ALF)[0x219c58f]
Thread 0xad
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0xaf
Kernel stack:
9IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
1 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
1IOWorkLoop::threadMain() + 97 (in mach_kernel) [0x660839]
1 thread_block_parameter + 32 (inmach_kernel) [0x22f740]
1thread_block_reason + 306 (in mach_kernel) [0x22f612]
1 thread_cancel_timer + 640 (inmach_kernel) [0x22e110]
1 processor_idle + 181 (in mach_kernel) [0x22d335]
1 machine_idle + 206 (inmach_kernel) [0x2cfbce]
Thread0xb0
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0xbc
Kernel stack:
10 thread_call_func + 752 (in mach_kernel)[0x23e300]
Thread 0xd4
Kernel stack:
10thread_call_func + 752 (in mach_kernel) [0x23e300]
Thread 0xe0
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0xe3
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0xe6
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x109
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x10b
Kernel stack:
10call_continuation + 28 (in mach_kernel) [0x2c6d0c]
10 catch_exception_raise + 550 (inmach_kernel) [0x5cf866]
10mach_msg_receive + 165 (in mach_kernel) [0x21b415]
10 ipc_mqueue_receive + 105 (in mach_kernel)[0x214fd9]
10thread_block + 33 (in mach_kernel) [0x22f771]
10 thread_block_reason + 331 (inmach_kernel) [0x22f62b]
10 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
10 machine_switch_context +582 (in mach_kernel) [0x2cba26]
Thread 0x10c
Kernel stack:
10 vm_pageout_internal_start + 128 (inmach_kernel) [0x2937b0]
Thread0x10d
Kernel stack:
10 vm_pageout_internal_start + 1440 (inmach_kernel) [0x293cd0]
Thread0x10e
Kernel stack:
10 vm_object_page_grab + 5088 (inmach_kernel) [0x2898e0]
Thread0x13e
Kernel stack:
10 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
10sock_inject_data_in + 622 (in mach_kernel) [0x5bae7e]
10 msleep + 165 (in mach_kernel)[0x575e25]
10 wakeup + 287(in mach_kernel) [0x57571f]
10 lck_mtx_sleep + 79 (in mach_kernel) [0x227bcf]
10 thread_block + 33 (inmach_kernel) [0x22f771]
10 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
10 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
Thread 0x1bd
Kernel stack:
10 call_continuation+ 28 (in mach_kernel) [0x2c6d0c]
10 dlil_if_ref + 3518 (in mach_kernel) [0x3551de]
10 msleep + 165 (in mach_kernel)[0x575e25]
10 wakeup + 287(in mach_kernel) [0x57571f]
10 lck_mtx_sleep + 79 (in mach_kernel) [0x227bcf]
10 thread_block + 33 (inmach_kernel) [0x22f771]
10 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
10 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
Thread 0x1bf
Kernel stack:
10call_continuation + 28 (in mach_kernel) [0x2c6d0c]
10 dlil_if_ref + 3518 (in mach_kernel)[0x3551de]
10 msleep + 165(in mach_kernel) [0x575e25]
10 wakeup + 287 (in mach_kernel)[0x57571f]
10lck_mtx_sleep + 79 (in mach_kernel) [0x227bcf]
10 thread_block + 33 (inmach_kernel) [0x22f771]
10 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
10 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
Thread 0x29c
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x2a3
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x2a6
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x2ad
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x2ae
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x2cd
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x2d1
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x2d3
Kernel stack:
10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
Thread 0x2d6
Kernel stack:
10 IOWorkLoop::threadMain()+ 0 (in mach_kernel) [0x6607d8]
Thread 0x2d8
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0x2ee
Kernel stack:
10 vm_pageout_internal_start + 128 (inmach_kernel) [0x2937b0]
Thread0x32e
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0x360
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0x369
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
Thread0x36c
Kernel stack:
9 thread_call_func + 752 (in mach_kernel)[0x23e300]
1 call_continuation +28 (in mach_kernel) [0x2c6d0c]
1 thread_call_func + 990 (in mach_kernel) [0x23e3ee]
1IOSCSIMultimediaCommandsDevice::sPollForMedia(void*, void*) + 34 (inIOSCSIMultimediaCommandsDevice) [0x15be89a]
1IOSCSIMultimediaCommandsDevice::PollForMedia() + 180 (inIOSCSIMultimediaCommandsDevice) [0x15c10cc]
1IOSCSIPrimaryCommandsDevice::SendCommand(OSObject*, unsigned long) + 327 (inIOSCSIArchitectureModelFamily) [0xb485cb]
1IOSCSIPrimaryCommandsDevice::ExecuteCommand(OSObject*) + 38 (inIOSCSIArchitectureModelFamily) [0xb4755c]
1IOSCSIPeripheralDeviceNub::ExecuteCommand(OSObject*) + 33 (inIOSCSIArchitectureModelFamily) [0xb46157]
1IOSCSIProtocolServices::ExecuteCommand(OSObject*) + 220 (inIOSCSIArchitectureModelFamily) [0xb4aa2c]
1IOCommandGate::runAction(int (*)(OSObject*, void*, void*, void*, void*), void*,void*, void*, void*) + 296 (in mach_kernel) [0x66266e]
1_ZL11WaitForTaskP8OSObjectP13IOCommandGateS0_ + 81 (inIOSCSIArchitectureModelFamily) [0xb49e68]
1IOEventSource::sleepGate(void*, unsigned long) + 82 (in mach_kernel)[0x6614e4]
1 IOWorkLoop::sleepGate(void*, unsigned long) + 80 (in mach_kernel)[0x660652]
1 IORecursiveLockSleep + 61 (in mach_kernel) [0x63f25d]
1 lck_mtx_sleep +79 (in mach_kernel) [0x227bcf]
1 thread_block+ 33 (in mach_kernel) [0x22f771]
1thread_block_reason + 306 (in mach_kernel) [0x22f612]
1thread_cancel_timer + 640 (in mach_kernel) [0x22e110]
1processor_idle + 181 (in mach_kernel) [0x22d335]
1 machine_idle+ 206 (in mach_kernel) [0x2cfbce]
Thread 0x35be
Kernel stack:
10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
BinaryImages:
0x200000 - 0x768837 mach_kernel ??? (???) <C2810CF8-D672-3301-8D3F-ED56974A80E1> /mach_kernel
0xb46000 - 0xb60fdb com.apple.iokit.IOSCSIArchitectureModelFamily 3.0.1 (3.0.1)<97490326-3E01-403D-A080-666932C4412A> /System/Library/Extensions/IOSCSIArchitectureModelFamily.kext/Contents/MacOS/IO SCSIArchitectureModelFamily
0x15ba000 - 0x15ce8d7 com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.0.1 (3.0.1)<0359232F-AAA5-4588-BA79-B483F412F5A7>/System/Library/Extensions/IOSCSIA rchitectureModelFamily.kext/Contents/PlugIns/IOSCSIMultimediaCommandsDevice.kext /Contents/MacOS/IOSCSIMultimediaCommandsDevice
0x1ef6000 - 0x1f15f9b com.apple.driver.AppleIntelCPUPowerManagement 167.0.0 (167.0.0)<EB830617-53D6-4098-A9C0-11AC8EF213D5> /System/Library/Extensions/AppleIntelCPUPowerManagement.kext/Contents/MacOS/App leIntelCPUPowerManagement
0x2198000 - 0x219e0df com.apple.nke.applicationfirewall 3.2.30 (3.2.30)<6C2D82F8-137B-4117-BCDE-EBFAEA9F7BCB> /System/Library/Extensions/ALF.kext/Contents/MacOS/ALF
Kextstat:
Index Refs Address Size Wired Name (Version)<Linked Against>
1 71 0x945000 0x5d48 0x5d48 com.apple.kpi.bsd (11.2.0)
2 6 0x932000 0x35c 0x35c com.apple.kpi.dsep (11.2.0)
3 93 0x9e7000 0x1ab7c 0x1ab7c com.apple.kpi.iokit (11.2.0)
4 97 0x93c000 0x8e60 0x8e60 com.apple.kpi.libkern (11.2.0)
5 84 0x933000 0x7f0 0x7f0 com.apple.kpi.mach (11.2.0)
6 29 0x934000 0x4274 0x4274 com.apple.kpi.private (11.2.0)
7 43 0x939000 0x2924 0x2924 com.apple.kpi.unsupported(11.2.0)
8 0 0x94f000 0x25f38 0x25f38 com.apple.kernel.6.0 (7.9.9)
9 0 0xa02000 0x25f38 0x25f38 com.apple.kernel.bsd (7.9.9)
10 0 0x9c1000 0x25f38 -
Logged into and got below, Can I do a hot reseat of the drive or do I have to shut down (docs say too) before reseating? Any other thoughts would be appreciated. No directory /local/local1! Logging in with home = "/". System Initialization Finished. Disk based software not installed. Some applications may not run correctly! #sh disks details Storage array not supported. Physical disk information: disk00: Not present or not responding disk01: Not present or not responding Mounted file systems: MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE% No RAID devices present. #sh disks tech Storage array not supported. === disk00 === disk00: Not present or not responding === disk01 === disk01: Not present or not responding Thanks in advance! Rich
Hi Rich,
Disks on this system should be hot swappable so I think you can go ahead and try a reseat without any intervention.
This is mentionned under the following link: http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v431/configuration/guide/maint.html#wp1139597
It seems that both disks were lost so even if they both come back after reseating, you might need to re-install the WAAS software as the raid array would have been lost.
Regards,
Nicolas -
Hello, having some problems with my 30 gig ZenXtra.
Had it for about a year with no problems but just turned it on and it came up with the rescue screen with the options;
Clean Up
Format all
Reload OS
Reboot
I tried clean up and it made no difference, reload os came up with 'harddisk problem' and reboot made no difference.
Is there anything I can do bar formatting?
ThanksMight try removing battery for 30 seconds or so then reinsert and power up... This has worked in the past when my micro goes ga-ga.
Good Luck -
Hmmm...firstly I apologise if I may have posted something similar to this before!
Anyway my problem is:
I am having trouble accessing my maxtor 6y200m0 sata drive, the Nforce3 sata raid driver that came with my board has been corrupted on the floppy, so I have downloaded and used the one from the NVIDIA website (thanks guys!!) and the maxblast 4 file from the Maxtor site, But when I try to access it, windows tells me it needs formatting (and if I try to format it, then it crashes!...windows recognises it in "my computer" and reports it on diagnostic programs, but it wont let me access it)
I have (as far as I can tell) set up my BIOS for Sata...but didnt put the Raid on as I wasnt sure if I needed it for one Sata!
Can anyone offer any suggestions for this problem?
thanks in advanceTry HDD in other PC or try other SATA in this PC to see if it's a HDD problem.
-
Devkit-disks-probe-ata-smart causes HSM Violations on SSD
I've just experienced the same problem identified on this Ubuntu bug report:
https://bugs.launchpad.net/ubuntu/+sour … mments=all.
It seems to be a general Linux kernel problem, and there are reports of it on Arch. Is a solution on the way?
My SSD started playing up, first exhibiting bad sector errors, then suddenly becoming read only as I was using it and finally refusing to mount when I booted complaining about a possible zero length partition. It also manifested the same problems described in this bug report when I booted up. Fortunately its the drive where I have my home partition, so its recoverable (not sure about the data in it, but there's nothing I can't afford to lose, even if I'd prefer not to).
I'm running Toofishes' patched eee kernel on an Asus 900. I'm fairly up to date (a week out at most). Is there a fix already in pacman, or do I try and apply this patch to my Arch system somehow? If so, how exactly. I'm okay with modifying the file, though I think its in a different place, but I'm a bit worried about it being overwritten by future updates.
Also, any ideas for recovering the drive, or restoring it. Writing 0s all over it seems a little drastic, and I'd prefer not to lose my home drive if I can. -
Many small probs with my K8N Neo
Specs:
K8N Neo Platinum w/ newest version of BIOS (I checked)
1 GB PC3200 Kingston RAM (2x512MB)
ATI brand Radeon 9700 pro 128MB
60.0GB Maxtor 5400RPM HD
500w Viomax PSU (30A on +3.3V, 50A on +5V, 25A on 12V)
No other PCI cards installed at the moment
Problems:
1. My computer won't restart. Whenever Windows calls for a restart or I hit the button myself, the screen goes blank while everything else stays active. People here told me it was my PSU. My Radeon 9700 Pro requires an extra floppy power cable so I thought I'd test out another video card that didn't need extra power to see what would happen. My comp worked fine with a 9200. So I bought a 500w Viomax PSU, a cheap one, yes, but it got good reviews. I stuck it in there and my comp STILL wouldn't restart normally. It has changed however: it'll restart the 3rd or 4th time I hit the button, but never the first..... which it definitely should.
2. My HD wasn't recognized by my mobo. After doing the first part of installing WinXP pro, my computer restarted (well, I had to switch the PSU off then on again to get it to work) but then I got "Error loading operating system." After a while of trial and error I arbitrarily changed the "Access Mode" in CMOS to "Large" instead of "Auto". Bingo, it worked, yay. Even though it works now, I still don't like the idea that my mobo couldn't automatically recognize my HD. I tested different ribbon cables and other HDs that I knew worked fine in other computers but they all wouldn't work in mine unless I put the setting on Large. hmmm.
3. The supplied nVidia IDE driver slows down my computer and causes Video Errors. The windows logo takes FOREVER to show up (or it will freeze in the middle of its fading it for 10-15s) when those IDE drivers are installed. As soon as I uninstall them everythings chipper though. Note that this problem is IDE, which might go along with why my HD isn't recognized.
4. When I open GoodMem, a memory manager/monitor that came with the mobo, my computer drastically slows down to a point where it's literally not usable. If I close GoodMem, it goes back to normal. I tried out a 256MB stick of my sisters just to see what happens and what'da ya know, GoodMem works perfectly.
I've never built a computer before and all this really makes me wanna RMA my board....... so here's the big question.... SHOULD I?
Thanks everyone,
-Robert LeeHi
sounds more like a Disk prob, or Windows prob than Mobo or CPU,
Did you format the HDD on this comp, if it was formatted on another machine, it can cause it not to be recognised.
Virus or Spy progs can slow down a comp, Try Task Manager, Ctrl +Alt + del, see what procs are running, if there is a strange unknown one it may be cause. If you go to the processor heading, the proc idling should not be using much CPU time, if something is using a lot of CPU time and is not essential, close it and see if it helps.
For the HDD, try disk management. Right click My computer, then manage then disk management, you will see if disk are healthy, you can also check them for probs.
May need defraged, and Chkdsk run.
In device Manager, does the IDE HDD show as OK, no yellow marks. You could try updating driver,
cheers
jocko -
I have exactly the same problem as Sheilak in an earlier thread ie upgrading from 10.2.8 to retail version of tiger. i too get disk probs that cant be fixed by running disk utility.
I am going to erase the disk and start afresh but need to make sure i do things correctly.
When it comes to backing up data, how do i retain things like emails, itunes mp3s etc. I am sure there are other things too, so is there a checklist i can work from before i erase ?
I would probably then boot tiger from the disk rather than install jaguar first (the one that came with the mac). can anyone forsee any problems i may encounter ?
cheers
steHello ste:
One size does not fit all, but I can outline my own backup/recover approach. I make bootable clones (everything is copied) of my iMacs on an external firewire drive. I use a little program called SuperDuper ($20 US at www.shirt-pocket.com). In that way, I can recover from either software or hardware problems.
Having said all that however, I am not sure exactly what will work for you - the unrepairable disk problems are certainly a concern. If you have it, you should run DiskWarrior - the 'gold standard' of repairing directory problems. As an aside, I prefer an archive and install when upgrading. That approach retains all of your files and programs and installs a fresh copy of OS X.
http://docs.info.apple.com/article.html?artnum=107120
Barry -
Hi.Ive just bought an Msi K7N2 Delta.With a 3000 Athalon chip a 200gb Sata hd and 2 strips of pc3200 512 DDR Dane-elec.I installed everything fine but the machine was very unstable.I kept getting errors and it kept re booting.I narrowed it down to the strips of memory.If i took one out and left one in it ran fine and let me install some of my programs and then i left it running all night.Fine.Thought i would swap the two memory sticks to make sure it was that.It worked fine and let me instal the rest of my programs and left it running the following night.Fine.The boards manual says to put the memory in 1+3 or 2+3 with the 3 being the bank on its own.So i tried both options and the machine becomes unstable again.The last time it crashed i thought i'll put it back to one strip, at least it was running ok.
But now when ive tried to re-boot it crashes straight away and i get a blue error screen with unmountable boot volume.Ive tried booting into safe mode but get the same message.Ive changed the first boot device to cdrom and boot from the win xp disk but it wont.
What have i done wrong and what can i do to fix it?.Hi
This is the K8T 64 bit forum, you would get better help on the forum for the K7N.
However, sounds like the MBR needs reset or your comp is not seeing disks, have you altered bios settings, either set safe defaults in bios, then setup boot sequence and see if disks recognised, on this board F11 at boot brings up boot menu, you can see what disks are recognised. If you can get XP CD to post then use the recovery console to get to Dos screen, and select the boot disk prob C: then type C:> FIXMBR, it will repair the MBR, can also be done from win98 startup floppy, but use FIX MBR.
If that dont work, use win98 startup to format and re install XP cheers
jocko -
Upgrade breakage (file called /dev/tty[0-9]*)
Today I updated a laptop with the usual pacman -Syu. After the upgrade (with no errors visible in pacman.log) i rebooted into a fscked system. Instead of /dev/tty0, /dev/tty1, ... I had a file called /dev/tty[0-9]* , and when the boot process completed I was left without a gui or a console login.
I have no idea what could have caused this as I updated successfully on several other machines.
Is there a quick fix for this? I tried reinstalling the base group, reinstalling ALL packages, still no go. If possible I'd like to avoid wiping the root partition and installing/configuring all over again - any ideas?
Thanks,
schuay
Last edited by schuay (2009-09-25 19:41:12)I encountered this problem and was able to solve it using this thread, so thanks, everyone!
Also, I did quick check to see what the differences in the /etc/udev/ directory were:
liquidsunshine@ruaidhri:/etc$ diff -r udev udev-bak
Only in udev-bak: lomoco_mouse.conf
Only in udev-bak/rules.d: 10-cups-usb.rules
Only in udev-bak/rules.d: 45-libnjb.rules
Only in udev-bak/rules.d: 60-pcmcia.rules
Only in udev-bak/rules.d: 60-virtualbox.rules
Only in udev-bak/rules.d: 65-libmtp.rules
Only in udev-bak/rules.d: 80-lomoco.rules
Only in udev-bak/rules.d: 90-hal.rules
Only in udev-bak/rules.d: 97-bluetooth-serial.rules
Only in udev-bak/rules.d: 99-fuse.rules
Only in udev-bak/rules.d: device-mapper.rules
Only in udev-bak/rules.d: udev.rules
and the same for /lib/udev/:
liquidsunshine@ruaidhri:/lib$ diff -r udev udev-bak/
Only in udev-bak/: bluetooth_serial
Only in udev-bak/: check-mtp-device
Only in udev-bak/: check-ptp-camera
File udev/devices/console is a character special file while file udev-bak/devices/console is a character special file
File udev/devices/fuse is a character special file while file udev-bak/devices/fuse is a character special file
File udev/devices/kmsg is a character special file while file udev-bak/devices/kmsg is a character special file
File udev/devices/loop0 is a block special file while file udev-bak/devices/loop0 is a block special file
File udev/devices/net/tun is a character special file while file udev-bak/devices/net/tun is a character special file
File udev/devices/null is a character special file while file udev-bak/devices/null is a character special file
File udev/devices/ppp is a character special file while file udev-bak/devices/ppp is a character special file
File udev/devices/zero is a character special file while file udev-bak/devices/zero is a character special file
Only in udev-bak/: devkit-disks-dm-export
Only in udev-bak/: devkit-disks-part-id
Only in udev-bak/: devkit-disks-probe-ata-smart
Only in udev-bak/: lomoco.sh
Only in udev-bak/rules.d: 52-libmtp.rules
Only in udev-bak/rules.d: 53-sane.rules
Only in udev-bak/rules.d: 54-gphoto.rules
Only in udev-bak/rules.d: 55-hpmud.rules
Only in udev-bak/rules.d: 56-hpmud_support.rules
Only in udev-bak/rules.d: 95-devkit-disks.rules
Only in udev-bak/rules.d: 95-devkit-power-battery-recall-dell.rules
Only in udev-bak/rules.d: 95-devkit-power-battery-recall-fujitsu.rules
Only in udev-bak/rules.d: 95-devkit-power-battery-recall-gateway.rules
Only in udev-bak/rules.d: 95-devkit-power-battery-recall-ibm.rules
Only in udev-bak/rules.d: 95-devkit-power-battery-recall-lenovo.rules
Only in udev-bak/rules.d: 95-devkit-power-battery-recall-toshiba.rules
Only in udev-bak/rules.d: 95-devkit-power-csr.rules
Only in udev-bak/rules.d: 95-devkit-power-hid.rules
Only in udev-bak/rules.d: 95-devkit-power-wup.rules
Only in udev-bak/rules.d: 97-bluetooth-hid2hci.rules
Only in udev-bak/rules.d: 97-bluetooth.rules
Unfortunately, I'm not curious enough at this point to do more in-depth investigation, but it looks to me like there were quite a few left-over files lying around from previous udev upgrades... -
Disk Utility Unable to Probe Target Disk
Hi All,
iMac G5 iSight turns on to the blinking folder icon. Booted to a Tech Tools drive, tried repair disk in disk utility, it said it was unable to repair.
Booted the G5 in Target disk mode, connected over firewire to a White Macbook. Eventually, the G5's hard drive turned up in Disk Utility but not on the desktop or in Finder. Tried to Mount the HD, that failed, and DU told me to repair the volume first. Initiated a repair through DU.
The repair is taking quite a while, so I checked out console.
Here's the console messages
Oct 11 11:04:03 eva-gils-macbook diskarbitrationd[31]: unable to mount /dev/disk2s2 (status code 0x00000001).
Oct 11 11:07:48 eva-gils-macbook kernel[0]: disk2s2: I/O error.
Oct 11 11:15:18 eva-gils-macbook kernel[0]: disk2s2: I/O error.
Oct 11 11:16:03 eva-gils-macbook kernel[0]: disk2s2: I/O error.
Oct 11 11:16:03 eva-gils-macbook diskarbitrationd[31]: unable to probe /dev/disk2s2 (status code 0xFFFFFFFC).
Oct 11 11:17:33 eva-gils-macbook kernel[0]: disk2s2: I/O error.
Oct 11 11:24:18 eva-gils-macbook kernel[0]: disk2s2: I/O error.
Oct 11 11:25:03 eva-gils-macbook kernel[0]: disk2s2: I/O error.
Oct 11 11:25:03 eva-gils-macbook diskarbitrationd[31]: unable to probe /dev/disk2s2 (status code 0xFFFFFFFC).
Oct 11 11:31:48 eva-gils-macbook kernel[0]: disk2s2: I/O error.
Oct 11 11:32:33 eva-gils-macbook kernel[0]: disk2s2: I/O error.
Oct 11 11:32:33 eva-gils-macbook diskarbitrationd[31]: unable to probe /dev/disk2s2 (status code 0xFFFFFFFC).
Oct 11 11:36:18 eva-gils-macbook kernel[0]: disk2s2: I/O error.
Oct 11 11:40:03 eva-gils-macbook kernel[0]: disk2s2: I/O error.
Oct 11 11:43:48 eva-gils-macbook kernel[0]: disk2s2: I/O error.
So, lots of Input Output errors and unable to probe. I'm wondering, does anyone have experience with this? Is the drive completely hosed? Is DU first aid still my best option? I'd love to get the seven years of stuff off that computer so I can back it up and wipe the HD.As expected, the disk formatted with MacDrive was recognized OK by my iMac. As soon as I connected it Time Machine offered to use it, I accepted and my first backup completed some time last night (I left it working and went to sleep).
Any ideas about what could be happening with the hard drive? -
(10.6.8 Intel core duo 2009)
Hi,
I have a grey screen and grey rotating wheel startup probs. I have tried repairing with the disk utility, resetting PRAM, booting in safe mode (which gave a subset of the errors that 'disk repair' did- namely- 'invalid sibling link,invalid record count, invalid node structure, invalid key length) and finally trying to get to archive&install the o/s, but it cannot find the destination volume. Is an erase the only option? PS I have backed up most files individually, but my daughter did not back up any from her user account. Any help would be appreciated. JGray, Blue or White screen at boot, w/spinner/progress bar
Why is my computer slow?
..Step by Step to fix your Mac
https://discussions.apple.com/community/notebooks/macbook_pro?view=documents -
iMac 10.9.4 software updates last week is apparent cause of my Corel Painter X3 now crashing. I ran Disk Utility check - no probs there. I reinstalled Painter X3 (after first uninstalling X3), still no success. Online Mac support suggest I use MacCleaner - tried at online Mac store & was referred to 0800 tech support for guidance - still waiting for reply.
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.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if iTunes crashed, you would enter "iTunes" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful. -
Format cannot see disks but probe-scsi-all can
Hi Folks,
I have attached a Storedge with five disks to an external SCSI card and can see all the disks via the probe-scsi-all command at the OBP. However when I do a boot -r I would expect to see all the disks with the format utility but I only see the internal disks.
Has anyone had this problem? If so am I missing something obvious?
Thanks in advance.Hi
check the scsi-initiator-id in printenv on OK prompt .If it is 7 change to 6 and check whether u can see the hard disks through format command. and also u can run these three commands on root prompt to detect the hard disks
1) # drvconfig
2)# disks
3)# devlinks
Best Luck
Regards
Maybe you are looking for
-
How can i avoid displaying runtime error in intractive report
hi gurus my question is, in interactive report when i reach 20th secondary list after that am getting runtime error when i click again. So i wanted to know how can i avoid that run time error. regars imran
-
How do you display file type in PS Elements 10?
How do you display file type in PS Elements 10 in the Organizer for each photo? I know you can right click and look at meta data. In PSE 7 it was displayed under each photo.
-
Unable to import table in owb 9.2
i am using warehouse builder 9.2 and database 9i R2 the source databse is also oracle 9i R2 when i create a source module to import the required tabe metadata i found that some table did not apper in the available objects i discovered that for those
-
Setting a "private"-Flag for tasks/todos
i am using a blackberry curve 9300 with OS 6, BES with lotus notes 8.5: there is no possibility to set a private-fla g in blackberrys todo-applic ation. do you know an other third party application to create private tasks on blackberry or is there an
-
Automatically create a Delivery Order document on saving sales order
hi, i want that a delivery document should be automatically created on saving sales order. how can i configure sap to do so? thanks