Getting 2 TB HD back to life - and getting back programs; re-editing CoreStorage Physical Volume Set

Hello community!


Background:

The former internal HD (2 TB) from my iMac27 = iMac (Retina 5K, 27″, End 2015) seems to have died.

It got replaced with 2 TB SSD.

The former internal HD now hangs on one of these USB hubs, awaiting further corrective action.

For policy, data are always stored on external HDs here.

I am addressing the recovery of my old programs here. Maximum hope: Get this old HD back to be bootable.

So I do not need to recover JPGs, documents and the like.

I do want to get the old programs back to life.

FileVault was never activated. Encryption: no.


Finder does not recognise the disk.

Apples Disk Utility program does.

And running 1st aid reveals the following output:

"Logical Volume group ... spans 2 devices" and

"Incomplete or inconsistent CoreStorage Physical Volume Set" and

error code (-69716).


2 runs for recovery with wondershare recovery were done, tons of files copied onto another hard disk, but except for the Parallel data, the Mac programs do not show up. (The former internal HD was never used for booting with different OS. No bootable Windows partition. All windows apps were inside a Parallel "box".)


Time for Terminal then.


Terminal runs show:

On command "diskutil list":

...

/dev/disk2 (external, physical):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      GUID_partition_scheme                        *2.0 TB     disk2

   1:                        EFI ⁨EFI⁩                     209.7 MB   disk2s1

   2:          Apple_CoreStorage ⁨Macintosh HD⁩            2.0 TB     disk2s2

   3:                 Apple_Boot ⁨Recovery HD⁩             650.0 MB   disk2s3

...

On command "diskutil info disk2"

@Wolfgangs-iMac /volumes % diskutil info disk2


   Device Identifier:         disk2

   Device Node:               /dev/disk2

   Whole:                     Yes

   Part of Whole:             disk2

   Device / Media Name:       D ST2000DM001


   Volume Name:               Not applicable (no file system)

   Mounted:                   Not applicable (no file system)

   File System:               None


   Content (IOContent):       GUID_partition_scheme

   OS Can Be Installed:       No

   Media Type:                Generic


   Protocol:                  USB

   SMART Status:              Not Supported


   Disk Size:                 2.0 TB (2000398934016 Bytes) (exactly 3907029168 512-Byte-Units)

   Device Block Size:         512 Bytes


   Media OS Use Only:         No

   Media Read-Only:           No

   Volume Read-Only:          Not applicable (no file system)


   Device Location:           External

   Removable Media:           Fixed


   Solid State:               Info not available

   Virtual:                   No

(end of terminal output).


Now, as it has been the bootable internal HD with MacOS before, these data are "demanding".


Next Terminal command&output:

@Wolfgangs-iMac /volumes % diskutil cs list


CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group E2B0BDE6-ECB2-4D35-BFB1-F5015C7BC927

    =========================================================

    Name:         Macintosh HD

    Status:       Offline

    Size:         1999539175424 B (2.0 TB)

    Free Space:   -none-

    |

    +-< Physical Volume 8B6569D4-36A9-45DA-A0D4-BAB7828FFDDB

    |   ----------------------------------------------------

    |   (No properties)

    |

    +-< Physical Volume B8F4B18C-4E54-4B74-8CE4-2C89FDA26AF1

        ----------------------------------------------------


        Index:    1

        Disk:     disk2s2

        Status:   Checking

        Size:     1999539175424 B (2.0 TB)

(end of terminal output)


My question:

=> Any helpful commands to re-write the complained "CoreStorage Physical Volume Set"? <=


I ran "sudo gpt recover /dev/disk2" without improvement.


There are some web pages addressing similar events

(e.g. https://nbalkota.wordpress.com/2013/01/13/recovering-a-non-readable-disk-on-mac-os-x/)

but it may be better to get sentiment here.


Thanks in advance!

iMac (2017 – 2020)

Posted on Dec 20, 2023 11:34 AM

Reply

Similar questions

3 replies

Dec 21, 2023 9:33 AM in response to WolfyinBavaria

@Jack-19 is correct about the Fusion Drive. It is possible the Fusion Drive was already broken before you removed the hard drive portion because the hard drive is failing & broke the Fusion Drive linked setup on its own.


If you did not have a Fusion Drive, but only a single internal hard drive, then that hard drive has likely failed anyway. Recovering data from a failed hard drive which was not part of a Fusion Drive is difficult enough depending on the severity of the drive failure.


If the hard drive is failing, then normal utilities (even data recovery utilities) won't be able to recover any data since they cannot deal with the errors produced by a failing hard drive. In fact any attempt to access the data will likely result in the hard drive failure becoming worse...even to the point where even a professional data recovery service will be unable to recover any data. It takes specialized software to even attempt to recover data from a failing hard drive.


You can check the health of the hard drive by using DriveDx (free trial available) and posting the complete DriveDx text report here using the "Additional Text" icon which looks like a piece of paper so I can review it. You will need to install a special USB driver to even attempt to access the external drive's health information, but even with this special USB driver, sometimes the USB adapter, drive dock, or enclosure can prevent the necessary communication to access this information on the external drive.

Dec 21, 2023 12:07 AM in response to WolfyinBavaria

Addendum:

Advices found in the net refer to first unmount the disk before proceeding.

However, commands like "diskutil unmountDisk force disk2" do NOT work properly but show "at least one volume could not be unmounted".

As this HD was internal boot HD before, it has Apple_Boot Recovery HD on it.

Sometimes (!), terminal command "sudo lsof|grep disk2 " shows 3 processes (bit without an ID!, so can't kill). Today not (NO process), but unmounting still impossible.

Force unmount of single volumes on HD would probably help, but how?




Dec 21, 2023 12:11 AM in response to WolfyinBavaria

Hey there!


Sorry, but what you're trying to do isn't supported. A Fusion Drive is only operable when both the SSD and hard disk are installed in and running from the same Mac. There's no way to recover data from just the hard disk or SSD. Any data recovered would be corrupted, as some parts of apps and files are spread across the two physical disks.


Sorry about that.


-Jack

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Getting 2 TB HD back to life - and getting back programs; re-editing CoreStorage Physical Volume Set

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.