0

so I got a really delicate situation going on. I exchanged my mechanical HDD with a SSD and turned the 1TB HDD into a external USB device. So far so good, everything works like a charm. Yesterday I decided to upgrade my Apple NVMe SSD with a Samsung Evo 970. Yes, it is possible and I did it. Also everything fine so far. Now, today I wanted to look at some files I stored on my external 1TB HDD (ex FusionDrive) and I noticed it didnt mount. After checking with diskutil cs list I got this situation here going on

  CoreStorage logical volume groups (1 found)
  |
  +-- Logical Volume Group D8991905-4ADE-464D-B28A-D421E4D53888
      =========================================================
      Name:         Macintosh HD
      Status:       Offline
      Size:         999345127424 B (999.3 GB)
      Free Space:   -none-
      |
      +-< Physical Volume CE7AA5F1-9E58-4EB9-9E07-6F0B54C949A3
      |   ----------------------------------------------------
      |   (No properties)
      |
      +-< Physical Volume B70579A0-84A6-45DE-BA00-2C45FA182FCD
          ----------------------------------------------------
          Index:    1
          Disk:     disk4s2
          Status:   Checking
          Size:     999345127424 B (999.3 GB)

To be honest I never ran the command before, hence I dont know what it looked like before, but I guess the Physical Volume CE7AA5F1-9E58-4EB9-9E07-6F0B54C949A3 was the Apple NVMe which I have removed. Now, the GUID table is all messed up.. I could format the Disk and erase everything and continue to use ist, but if someone knows a way to fix it so I dont have to erase the data that it contains - that would be awesome. Thanks

  • seems like there is no way to save the data on the mechanical harddrive without reconnecting the Apple NVMe with the iMac, so I did just that, but with an external thunderbolt enclosure. I saved myself the hussle of reopening the iMac. The drive was able to mount as soon as I hooked up the thunderbolt device. I saved my files and broke the Logical Volume Group up. I deleted it, formatted the disk and copied the data back on to it. No elegant way to save the data via UNIX commands I guess – b101 Mar 5 at 21:29

You must log in to answer this question.

Browse other questions tagged .