Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

UltraLEL

macrumors newbie
Original poster
Sep 19, 2016
7
1
Hi guys.

I have Mac Mini with installed SSD and it worked well since one and half year.

Recently i got some trouble with it. For some reason(i don't know why),my High Sierra crashed(freezed) two times, third time reboot didn't help and seems to be OS has come to broken state :(.

Unfortunately i'm not a huge user on OS X(macOS) and i didn't tried to enter on Recovery Mode. I got impression that something is wrong with my SSD(like died controller or something other) or much worst variant with motherboard.

So the first(and wrong) solution that arrived to my mind was disassemble Mac Mini and swap with another SSD to double check if all is fine(what i have made finally). And seems to be that all is fine and SSD is not dead btw, old data is remains there.

Then i assembled back(my old problematic SSD) and started to restore with Recovery Mode(with no luck).

Command+R( all other methods) didn't helped me, like 90% scenarios was that after booting my Mac Mini i got black screen with no reaction to different hotkeys for Recover Mode(Sometimes it was like 10-20 minutes with black screen and then appears logo with rotating earth, subsequently error something similar to "-2003F").

So ok, internet recovery didn't help. Seems to be that BootLoader is dead.

What i have made next : swapped with another clean SSD(where i have successfully installed new macOS High Sierra).
Then i connected my OLD SSD with broken macOS High Sierra via Sata-to-USB and voila(!).
I was able to see all my data (any folder/any place). So i started immediately getting the whole user folder(documents/library/apps and etc) and it was second huge mistake from my side.

In fact, there is a lot of data and OS started to doing "preparing" of copying it to my new SSD.
I waited approximately 10-15 minutes and it still was on "preparing" status. I Decided to "cancel" it, because seems to be that something went wrong.

But it didn't worked, it's was like no reaction on it and i have extracted connected SSD(with broken macOS) via USB from Mac Mini.(like wrong disconnect any USB flash without ejecting properly)

As i said before, i'm not a advanced user of macOS and i agree that this action was too stupid, because now when i connect my SSD(with broken macOS),i can see the initial folders, but if i try to enter/copy/make something that is related to read/write finder becomes freezed(Not Responding),to restore it i need to extract(Disconnect) broken SSD...

I know that i got chance to restore it painless, when i connected first time via Usb-to-SATA adapter, i should run FirstAid from disk utility to restore OS, but know it's too late, because it can't help now.(it shows errors that can't unmount disk drive)

TL;DR
I need urgently to restore my macOS to extract all data from google chrome(bookmarks + passwords + other stuff) and the rest of downloaded/created that is alive on disk drive.

I still can see the whole information about disk drive via terminal command, but as i said before if i'm trying to get/explore something, finder becomes freezed(not responding).
Now something is broken with bootloader and table partition(?).

Other programs cant read information properly from disk(they freezes also).

This is what shown on Disk Utility
MacProblem 1.png


and this additional information about disk drive
MacProblem2.jpg


Also what i tried its to connect my broken SSD via USB-to-SATA and enter to recover mode to re-install new HighSerra...the result is the same, it can't be choosen as hard drive for installing(in fact it detects, but you can't do anything there).

If choose as startup, also freezes up :(
MacProblem3.jpg


So guys..what can i do in my case? Any suggestions would be appreciated !

PS Apologize for my English skills.
 
There is no need to disassemble the Mini if you have a second drive.

Just connect it "externally" using USB3 and boot that way.
 
Can you navigate down the user account level on the external drive? If yes, you can extract the info you need and copy if over the current boot drive.

UPDATE: I see you cannot browse the external. That makes things hard, especially with APFS, as so few tools are updated to support it.

What did First Aid report? It is common that First Aid fails to unmount some external drives. You can unmount from the First Aid menu (not unplug it, just unmount it) and then run First Aid.
 
There is no need to disassemble the Mini if you have a second drive.

Just connect it "externally" using USB3 and boot that way.

Adapter Usb-To-Sata i got later,when OS already died..
[doublepost=1536865290][/doublepost]
UPDATE: I see you cannot browse the external. That makes things hard, especially with APFS, as so few tools are updated to support it.

What did First Aid report? It is common that First Aid fails to unmount some external drives. You can unmount from the First Aid menu (not unplug it, just unmount it) and then run First Aid.

Yes.
First time when i have connected 'broken' macOS SSD, i got a chance to browse it properly(any folder/any directory).

But now in fact i can connect and only initial folders that are available,if i will jump somewhere there than my finder will die as Not Responding.

First Aid reported something like this : "couldn't unmount disk for repair" (i will drop screenshot later).

What means "unmount and run First Aid",what the difference? Can you explain please!

BTW,are you sure that via FirstAid you can easily unmount disk drive? Maybe it available from bash command,like this ->

PS I hope it will not format/erase the SSD :(.
 
Last edited:
You should have an Unmount button:

Qf2Xe_9hiHSWp8uv27TXrVwfxWC9ncM6n9k8dJ9naTwQiU161GabSCP3U1qwVJ75vMWv96QBfXREwuGS-8gLMWVmIxrgRNL7c3GFajFHBf0TKOAoJrTG_s74ZYRvKvproAh6nVwweqBH7syhaSuR--_eMIdwG-IJeOFwgt4_5kSb40nsxQDs9ACTkwTe-uCYKo3fvtFWVf3SPlfeNVGh6oBIbPjjNbhrgItGOH8vjIHUtqArSjjRRE_IpVZyLks-HVo0fvAbDjxelLotpyS9-mg7kj1Fz8WstaoSrkm6XH5DxieZexmN1N761UyI_0GoYPIUl49PQGdBKPhapbYUohWa7d-ZM-ln1GCFvyORtjjU9wEh4lVTKOcYlzJqSk1UgbQOYehERm3PRF-ZJ2Wat1RJhuXCfxDhkSg8N-Tl8RVDS2W35W6feiamTCsfFCP3MWKrYCNFD3e-7iuesZvForHq_ZHZbp-kEUaTGDEAkr8t2pQ9l9JmG7n5lkl_ToIHdg-K_axd3icBrmX1WT3DxAWU8UEf7WzW1ANIDIa6DhvxLkK2rHMZrR4hKmIctmwwg1zhfmYKryia5eUFjr0y5wy22eGjqDKpbWGiXvUmFAMFiH8z4621Nf72RY1lhOA=w737-h306-no


Wait for it to unmount, then use First Aid:

2XlHXLnqlZuJSZUKLJ1ebicblyQbnPBEXDXtoYZpa2RiaH5A2F7uIfLAmfHIk8auXy5EWhBkXc8kZ69eyUhNJyMerjPdaIDvEjfTVVvH8KBNde8qoHp1Ojo_wUS11GXLutlIkLPWxu1haW5xlrXeB6pIlesXxemborltYQ0UxnJW-D3O7qSd7YA_Ud962ueggZkZC4tF41RceZjs66c5H2Eido-4ib01QC85n4dKpWNrX11y9q2BFU1L9fRj3Vp6lyRRbiK_nam4Hl8SYiUTdEMp3dCYeucMGvl2GOW3YVTIRQIb1mNStTbjwe_VJ7e52t_l9X8e1rUkaKRiptdPX87fA_CbEVJR0f0shnGV8-4XPz0NhcfP-RBAm3PEYm7lE0fKKf2YeTKx6HmSD8cxq9-lwa7A3txFB5d1dJLo3ZvURAiJI70Ue1zp5a9tKk7lN_dUdZMkkUcbt8Fa0QqkwRBDC9g0Unh91FGupuW2spjpBw0BgB8e6WgGEy0nsvk9XQ50VXiKm6Kb7LlaytQS49j33kJvI93QcMlkkzxN4_eczuvGALHwortZfv9ZH9lIpmYPlLxCpS4GZZLnRHwwvKahrTzM-0VTXhS2F7nDzEc9wY_nr61VMO6xVsJbIjw=w699-h324-no


I see the automatic unmounting that should happen when trying to run First Aid will often fail, like the warning you got.

Sometimes unmounting manually first works, and then you can run First Aid.

Some external drives take as much as 30 seconds to unmount...perhaps the automated attempt gives up too soon.
 
You should have an Unmount button:

Qf2Xe_9hiHSWp8uv27TXrVwfxWC9ncM6n9k8dJ9naTwQiU161GabSCP3U1qwVJ75vMWv96QBfXREwuGS-8gLMWVmIxrgRNL7c3GFajFHBf0TKOAoJrTG_s74ZYRvKvproAh6nVwweqBH7syhaSuR--_eMIdwG-IJeOFwgt4_5kSb40nsxQDs9ACTkwTe-uCYKo3fvtFWVf3SPlfeNVGh6oBIbPjjNbhrgItGOH8vjIHUtqArSjjRRE_IpVZyLks-HVo0fvAbDjxelLotpyS9-mg7kj1Fz8WstaoSrkm6XH5DxieZexmN1N761UyI_0GoYPIUl49PQGdBKPhapbYUohWa7d-ZM-ln1GCFvyORtjjU9wEh4lVTKOcYlzJqSk1UgbQOYehERm3PRF-ZJ2Wat1RJhuXCfxDhkSg8N-Tl8RVDS2W35W6feiamTCsfFCP3MWKrYCNFD3e-7iuesZvForHq_ZHZbp-kEUaTGDEAkr8t2pQ9l9JmG7n5lkl_ToIHdg-K_axd3icBrmX1WT3DxAWU8UEf7WzW1ANIDIa6DhvxLkK2rHMZrR4hKmIctmwwg1zhfmYKryia5eUFjr0y5wy22eGjqDKpbWGiXvUmFAMFiH8z4621Nf72RY1lhOA=w737-h306-no


Wait for it to unmount, then use First Aid:

2XlHXLnqlZuJSZUKLJ1ebicblyQbnPBEXDXtoYZpa2RiaH5A2F7uIfLAmfHIk8auXy5EWhBkXc8kZ69eyUhNJyMerjPdaIDvEjfTVVvH8KBNde8qoHp1Ojo_wUS11GXLutlIkLPWxu1haW5xlrXeB6pIlesXxemborltYQ0UxnJW-D3O7qSd7YA_Ud962ueggZkZC4tF41RceZjs66c5H2Eido-4ib01QC85n4dKpWNrX11y9q2BFU1L9fRj3Vp6lyRRbiK_nam4Hl8SYiUTdEMp3dCYeucMGvl2GOW3YVTIRQIb1mNStTbjwe_VJ7e52t_l9X8e1rUkaKRiptdPX87fA_CbEVJR0f0shnGV8-4XPz0NhcfP-RBAm3PEYm7lE0fKKf2YeTKx6HmSD8cxq9-lwa7A3txFB5d1dJLo3ZvURAiJI70Ue1zp5a9tKk7lN_dUdZMkkUcbt8Fa0QqkwRBDC9g0Unh91FGupuW2spjpBw0BgB8e6WgGEy0nsvk9XQ50VXiKm6Kb7LlaytQS49j33kJvI93QcMlkkzxN4_eczuvGALHwortZfv9ZH9lIpmYPlLxCpS4GZZLnRHwwvKahrTzM-0VTXhS2F7nDzEc9wY_nr61VMO6xVsJbIjw=w699-h324-no


I see the automatic unmounting that should happen when trying to run First Aid will often fail, like the warning you got.

Sometimes unmounting manually first works, and then you can run First Aid.

Some external drives take as much as 30 seconds to unmount...perhaps the automated attempt gives up too soon.

Thanks for fast reply.

I already tried and zero reaction.

Now it's much more worse. When i connect my SSD(honestly i didn't made anything that was like "breaking changes"), i remember that last thing what i have tried it was booting MacOS with connected via Usb-To-Sata adapter and trying to re-install/startup with broken version MacOS(external SSD,the stuff is pretty much described on initial post). Anyway, i didn't manage it, because SSD with broken OS was 'uneditable' and i didn't made anything.

What i'm getting now :( it's that :
1) When connect SSD with broken MacOS (via adapter),it shows nothing
upload_2018-9-14_10-58-8.png


2) What shows Disk Utility now
upload_2018-9-14_11-4-52.png


3) When i tap to "Unmount", there is zero reaction on this button. Just nothing happens now :(

4)When i pressing on info button(left corner),it just shows this
upload_2018-9-14_11-8-1.png

(its like a infinite loading, it can't show now any information that i was able to see :( )

5)First Aid as other guys(zero reaction), like no effect(but's not freezing)
upload_2018-9-14_11-29-54.png


6) what shows DiskUtil in terminal(seems to be it can be unmounted by bash command(?) ) :
diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *250.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk1 249.8 GB disk0s2


/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +249.8 GB disk1

Physical Store disk0s2

1: APFS Volume Untitled 69.8 GB disk1s1

2: APFS Volume Preboot 21.6 MB disk1s2

3: APFS Volume Recovery 516.1 MB disk1s3

4: APFS Volume VM 4.3 GB disk1s4


/dev/disk2 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *256.1 GB disk2

1: EFI EFI 209.7 MB disk2s1

2: Apple_APFS Container disk3 255.8 GB disk2s2


/dev/disk3 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +255.8 GB disk3

Physical Store disk2s2

1: APFS Volume Macintosh HD 220.9 GB disk3s1

2: APFS Volume Preboot 32.8 MB disk3s2

3: APFS Volume Recovery 517.8 MB disk3s3

4: APFS Volume VM 2.1 GB disk3s4

PS All is bad now :( ?
 
Last edited:
There is one other possibility.

I have seen quite a few USB external docks and drives that were unstable on some Macs. Can't say why, but I would guess it is a compatiblity between some USB chipsets, and the Mac USB chipset.

I have, for example, a drive dock that has USB and FireWire. From USB, many newer macs will neither boot or or allow a solid, reliable connection (Finder freezes, drives randomly unmount).

The same dock, using the same drive is rock solid when connected to FW, or to Thunderbolt with a FW to TB adapter.

Pretty clear it is a USB issue.

Unfortunately, hard to know if your SATA to USB is the issue. It could be...
 
This is why I keep two bootable clones of my hard drive and three time machines, one offsite and 2 on the network...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.