Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: Mik Beats
Mik Beats Author
User level: Level 1
4 points

External HDD Crashes Finder. Can't access files.

Out of no where I connect my external Toshiba 1.5tb HDD usb 3.0 and it mounts correctly. It shows up on my desktop and ejects properly. But whenever I double click the HDD and try to access HDD files...Finder crashes. Desktop, top bar, and dock blinks away and comes back. I try many more times and same result. Seems like finder keeps crashing every time I try to access the HDD.


I tried Disk Utility...verification and repairs were successfully completed but the same thing keeps happening.


then I thought maybe its the USB connecter/shell of the HDD so I bought a new usb 3.0 case and put my HDD in the new case but still the same issue.


I'm trying to withhold from reformatting the disk as there is important information and I know I'm stupid for not backing up my back up but any tips/help would be greatly appreciated!


Macbook Pro Retina 10.9.3

2.6GHz Intel Core i7

16 GB 1600 MHz DDR3

Posted on Jul 9, 2014 1:08 AM

Reply
26 replies
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Jul 9, 2014 9:02 AM in response to Mik Beats

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.

Reply
User profile for user: Mik Beats
Mik Beats Author
User level: Level 1
4 points

Jul 9, 2014 3:40 PM in response to Linc Davis

Log List



7/9/14 3:23:03.874 PM com.apple.launchd.peruser.501[197]: (com.apple.Finder[1530]) Job appears to have crashed: Segmentation fault: 11


Process: Finder [1530]

Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder

Identifier: com.apple.finder

Version: 10.9.3 (10.9.3)

Build Info: Finder_FE-885003002000000~1

Code Type: X86-64 (Native)

Parent Process: launchd [197]

Responsible: Finder [1530]

User ID: 501



Date/Time: 2014-07-09 15:23:03.576 -0700

OS Version: Mac OS X 10.9.3 (13D65)

Report Version: 11

Anonymous UUID: 4960EC89-4B86-8D72-3F0F-EE96A682B613



Sleep/Wake UUID: 53CC17CE-F945-4799-A964-ACADB84F36AF



Crashed Thread: 5 Dispatch queue: com.apple.root.default-priority



Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008



External Modification Warnings:

Thread creation by external task.



VM Regions Near 0x8:

-->

__TEXT 000000010db4e000-000000010e01d000 [ 4924K] r-x/rwx SM=COW /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder



Thread 0:: Dispatch queue: com.apple.main-thread

0 libsystem_kernel.dylib 0x00007fff8f435a1a mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff8f434d18 mach_msg + 64

2 com.apple.CoreFoundation 0x00007fff8d425fc5 __CFRunLoopServiceMachPort + 181

3 com.apple.CoreFoundation 0x00007fff8d4255e9 __CFRunLoopRun + 1161

4 com.apple.CoreFoundation 0x00007fff8d424f25 CFRunLoopRunSpecific + 309

5 com.apple.HIToolbox 0x00007fff91573a0d RunCurrentEventLoopInMode + 226

6 com.apple.HIToolbox 0x00007fff915737b7 ReceiveNextEventCommon + 479

7 com.apple.HIToolbox 0x00007fff915735bc _BlockUntilNextEventMatchingListInModeWithFilter + 65

8 com.apple.AppKit 0x00007fff92eae26e _DPSNextEvent + 1434

9 com.apple.AppKit 0x00007fff92ead8bb -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122

10 com.apple.AppKit 0x00007fff92ea19bc -[NSApplication run] + 553

11 com.apple.AppKit 0x00007fff92e8c7a3 NSApplicationMain + 940

12 com.apple.finder 0x000000010db54770 0x10db4e000 + 26480

13 libdyld.dylib 0x00007fff8ad005fd start + 1



Thread 1:: Dispatch queue: com.apple.libdispatch-manager

0 libsystem_kernel.dylib 0x00007fff8f43a662 kevent64 + 10

1 libdispatch.dylib 0x00007fff90645421 _dispatch_mgr_invoke + 239

2 libdispatch.dylib 0x00007fff90645136 _dispatch_mgr_thread + 52



Thread 2:

0 libsystem_kernel.dylib 0x00007fff8f435a1a mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff8f434d18 mach_msg + 64

2 com.apple.CoreFoundation 0x00007fff8d425fc5 __CFRunLoopServiceMachPort + 181

3 com.apple.CoreFoundation 0x00007fff8d4255e9 __CFRunLoopRun + 1161

4 com.apple.CoreFoundation 0x00007fff8d424f25 CFRunLoopRunSpecific + 309

5 com.apple.AppKit 0x00007fff9304e05e _NSEventThread + 144

6 libsystem_pthread.dylib 0x00007fff92df2899 _pthread_body + 138

7 libsystem_pthread.dylib 0x00007fff92df272a _pthread_start + 137

8 libsystem_pthread.dylib 0x00007fff92df6fc9 thread_start + 13



Thread 3:: com.apple.NSURLConnectionLoader

0 libsystem_kernel.dylib 0x00007fff8f435a1a mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff8f434d18 mach_msg + 64

2 com.apple.CoreFoundation 0x00007fff8d425fc5 __CFRunLoopServiceMachPort + 181

3 com.apple.CoreFoundation 0x00007fff8d4255e9 __CFRunLoopRun + 1161

4 com.apple.CoreFoundation 0x00007fff8d424f25 CFRunLoopRunSpecific + 309

5 com.apple.Foundation 0x00007fff9205e967 +[NSURLConnection(Loader) _resourceLoadLoop:] + 348

6 com.apple.Foundation 0x00007fff9205e76b __NSThread__main__ + 1318

7 libsystem_pthread.dylib 0x00007fff92df2899 _pthread_body + 138

8 libsystem_pthread.dylib 0x00007fff92df272a _pthread_start + 137

9 libsystem_pthread.dylib 0x00007fff92df6fc9 thread_start + 13



Thread 4:: com.apple.CFSocket.private

0 libsystem_kernel.dylib 0x00007fff8f4399aa __select + 10

1 com.apple.CoreFoundation 0x00007fff8d471ab3 __CFSocketManager + 867

2 libsystem_pthread.dylib 0x00007fff92df2899 _pthread_body + 138

3 libsystem_pthread.dylib 0x00007fff92df272a _pthread_start + 137

4 libsystem_pthread.dylib 0x00007fff92df6fc9 thread_start + 13



Thread 5 Crashed:: Dispatch queue: com.apple.root.default-priority

0 com.apple.desktopservices 0x00007fff8add2c08 BTreeIterator::Next() + 104

1 com.apple.desktopservices 0x00007fff8add09ab TPropertyInfo::MakeProperties(TPropertyInfoList*, unsigned char*, unsigned int, bool) + 603

2 com.apple.desktopservices 0x00007fff8add036c TPropertyInfo::CreatePropertyList(TCountedPtr<TFSInfo> const&, double&, long long&, bool, bool, TPropertyInfoList*) + 392

3 com.apple.desktopservices 0x00007fff8add018b TPropertyInfo::CreatePropertyList(TCountedPtr<TCFURLInfo> const&, double&, long long&, bool, bool, TPropertyInfoList*) + 169

4 com.apple.desktopservices 0x00007fff8add000d THFSPlusPropertyStore::Open(bool, bool) const + 93

5 com.apple.desktopservices 0x00007fff8adcff97 THFSPlusPropertyStore::GetProperties(bool) const + 39

6 com.apple.desktopservices 0x00007fff8add45ea TNode::GetExtendedPropertyStore(bool) const + 216

7 com.apple.desktopservices 0x00007fff8add443f TNode::GetExtendedProperty(unsigned int, TPropertyReference&, bool) const + 41

8 com.apple.desktopservices 0x00007fff8adce8d9 TNode::GetProperty(unsigned int, TPropertyReference&, unsigned int) const + 1773

9 com.apple.desktopservices 0x00007fff8adcdf1d TNode::GetProperty(unsigned int, TPropertyReference&, OpaqueNodeRequest* const&, unsigned int) const + 69

10 com.apple.desktopservices 0x00007fff8adcde6a GetNodeProperty(OpaqueNodeRef*, unsigned int, TPropertyReference&, OpaqueNodeRequest*, unsigned int) + 190

11 com.apple.desktopservices 0x00007fff8adcdd7b GetNodePropertyAsBoolean + 79

12 com.apple.finder 0x000000010db6b52f 0x10db4e000 + 120111

13 com.apple.finder 0x000000010db70f42 0x10db4e000 + 143170

14 com.apple.finder 0x000000010dc495a3 0x10db4e000 + 1029539

15 com.apple.finder 0x000000010db70d72 0x10db4e000 + 142706

16 libdispatch.dylib 0x00007fff906461bb _dispatch_call_block_and_release + 12

17 libdispatch.dylib 0x00007fff9064328d _dispatch_client_callout + 8

18 libdispatch.dylib 0x00007fff90645082 _dispatch_root_queue_drain + 326

19 libdispatch.dylib 0x00007fff90646177 _dispatch_worker_thread2 + 40

20 libsystem_pthread.dylib 0x00007fff92df3ef8 _pthread_wqthread + 314

21 libsystem_pthread.dylib 0x00007fff92df6fb9 start_wqthread + 13



Thread 6:

0 libsystem_kernel.dylib 0x00007fff8f439e6a __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff92df3f08 _pthread_wqthread + 330

2 libsystem_pthread.dylib 0x00007fff92df6fb9 start_wqthread + 13



Thread 7:

0 libsystem_kernel.dylib 0x00007fff8f439e6a __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff92df3f08 _pthread_wqthread + 330

2 libsystem_pthread.dylib 0x00007fff92df6fb9 start_wqthread + 13



Thread 8:

0 libsystem_kernel.dylib 0x00007fff8f439e6a __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff92df3f08 _pthread_wqthread + 330

2 libsystem_pthread.dylib 0x00007fff92df6fb9 start_wqthread + 13



Thread 9:

0 libsystem_kernel.dylib 0x00007fff8f439e6a __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff92df3f08 _pthread_wqthread + 330

2 libsystem_pthread.dylib 0x00007fff92df6fb9 start_wqthread + 13



Thread 10:

0 libsystem_kernel.dylib 0x00007fff8f439e6a __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff92df3f08 _pthread_wqthread + 330

2 libsystem_pthread.dylib 0x00007fff92df6fb9 start_wqthread + 13



Thread 11:

0 libsystem_kernel.dylib 0x00007fff8f439e6a __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff92df3f08 _pthread_wqthread + 330

2 libsystem_pthread.dylib 0x00007fff92df6fb9 start_wqthread + 13



Thread 12:

0 libsystem_kernel.dylib 0x00007fff8f439e6a __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff92df3f08 _pthread_wqthread + 330

2 libsystem_pthread.dylib 0x00007fff92df6fb9 start_wqthread + 13









DIAGNOSTIC AND USAGE INFORMATION


Process: Finder [421]

Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder

Identifier: com.apple.finder

Build Info: Finder_FE-885003002000000~1

Responsible: Finder [421]

__TEXT 000000010fe54000-0000000110323000 [ 4924K] r-x/rwx SM=COW /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder

12 com.apple.finder 0x000000010fe5a770 0x10fe54000 + 26480

12 com.apple.finder 0x000000010fe7152f 0x10fe54000 + 120111

13 com.apple.finder 0x000000010fe76f42 0x10fe54000 + 143170

14 com.apple.finder 0x000000010ff25aa9 0x10fe54000 + 858793

2 com.apple.finder 0x000000010fe7e0ac 0x10fe54000 + 172204

3 com.apple.finder 0x000000010fea7959 0x10fe54000 + 342361

4 com.apple.finder 0x000000011009acee 0x10fe54000 + 2387182

5 com.apple.finder 0x000000010fe5bc70 0x10fe54000 + 31856

0x10fe54000 - 0x110322ff5 com.apple.finder (10.9.3 - 10.9.3) <904FF4B2-31A2-30F8-B606-784D38AF7232> /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder


I think I posted the right info, lmk if this helps.

Reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Jul 9, 2014 5:09 PM in response to Mik Beats

Please read this whole message before doing anything.


This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.


Step 1


The purpose of this step is to determine whether the problem is localized to your user account.


Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”


While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.


Test while logged in as Guest. Same problem?


After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.


*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.


Step 2


The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

Please take this step regardless of the results of Step 1.


Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.

Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.


Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.


The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.


Test while in safe mode. Same problem?


After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.

Reply
User profile for user: Mik Beats
Mik Beats Author
User level: Level 1
4 points

Jul 9, 2014 10:50 PM in response to Linc Davis

Okay so I followed the instructions to Step 1 and got an interesting response....


When I tried opening the HDD it blinks the same way except the attached error comes up...User uploaded file


but the thing is that error attached would keep blinking...freezing Finder...I try to relaunch but the error wouldn't stop blinking. I unplugged the HDD to see if that's what was causing the freeze and as soon as I unplug the HDD the error stopped blinking and I can actually click on either "Don't Reopen" or "Reopen". I logged out and logged back into my main account and the same error still occurred.


So I followed Step 2 and still receiving the same problem. I appreciate all the help Linc!

Reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Jul 10, 2014 7:12 PM in response to Mik Beats

This procedure will revert the Finder view options of all folders on the volume in question to the default that you’ve chosen. If you don’t want that, STOP.

You need to run a UNIX shell command. Because the command could cause data loss if not done right, we'll proceed very carefully, in two steps. This is the first step. There is no risk of data loss in this step.

Triple-click anywhere in the line below on this page to select it:

find /V*/Mik\ Beats -type f -name .DS_Store -delete

Copy the selected text to the Clipboard by pressing the key combination command-C.

Start a reply to this message. Paste into the message window by pressing command-V and post the message. There may be a considerable delay before I reply. When I do, we can go on to the second step.

Reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Jul 10, 2014 8:42 PM in response to Mik Beats

This is the second step of the two-step procedure. You've done the first step.

Open a TextEdit window and paste again. You should see exactly the same line of text as above, beginning with "find." If that's not what you see, copy the command to the Clipboard again and paste into the TextEdit window to make sure it's the same as above. If it is, continue.

Back up all data.

Launch the built-in Terminal 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 Terminal in the icon grid.

Paste into the Terminal window by pressing the key combination command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.

The command may take up to several minutes to run. Wait for a new line ending in a dollar sign ($) to appear below what you entered. You can then quit Terminal. Test.

Reply
User profile for user: gradyogrady
gradyogrady
User level: Level 1
0 points

Sep 9, 2014 2:15 AM in response to Mik Beats

I am having an identical issue, albeit with a MacBook Air.


I attempted to implement the command above, modified to reflect my hard drive's name: "Grady's 2TB"


So I entered the following command in Terminal -> Shell -> New Command:


find /V*/Grady's\ 2TB -type f -name .DS_Store -delete


All I got back was the following:


-find: /V*/Grady's\: No such file or directory

-find: 2TB: No such file or directory



[Process completed]


Did I type something in wrong?


I would appreciate any tips as how to to make this work, may thanks!

Reply

External HDD Crashes Finder. Can't access files.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up