I would like to understand a bit more how this all works. I replaced the HD in my MacBook with an SSD. To do that I did the following:
- installed the SSD in an external USB drive enclosure
- installed Yosemite 10.10.2 from scratch on that external SSD
- restored all files from my TM backup
Only once I was satisfied that the SSD booted fine and was OK did I remove the internal HD and replace it with the SSD. I then mounted the old internal HD into the external USB enclosure.
Now I want to use that external drive as a regular drive, and I would like to erase it. But I observe the following:
1) When I plug in the external HD, it does not appear in the "Devices" section of the Finder. But the drive mounts fine (it is in /Volumes, on the desktop and also as a "Removable Volume" and I can access all files.
2) Exactly like described above, when I look at the drives in Disk Util, I see that the external drive only has the "First Aid" and "Partition" choices. No "Erase", "Raid" or "Restore" choices. And the drive appears as a "Logical Volume Group". On the other hand my internal SSD I boot from appears as a regular drive. The partition appears as a "Logical Partition". I can erase that partition, but I cannot erase the drive proper or repartition it.
Here is the output of "diskutil list"
$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh SSD 499.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *750.2 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_CoreStorage 749.3 GB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS External *748.9 GB disk3
Logical Volume on disk2s2
7EE41451-8421-44AE-A249-343E1A3CCB25
Unencrypted
It shows that the old HD used Core Storage, and that is why I cannot use it as I expect, but using the diskutil command line I expect to be able to clean it out just like you explained. "diskutil cs list" shows:
$ diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group B0341F77-1A3C-42EE-9FE2-209CE49CED8A
=========================================================
Name: Macintosh HD
Status: Online
Size: 749296615424 B (749.3 GB)
Free Space: 18939904 B (18.9 MB)
|
+-< Physical Volume EA971DCF-EFB3-40F2-8B8A-18507B794476
| ----------------------------------------------------
| Index: 0
| Disk: disk2s2
| Status: Online
| Size: 749296615424 B (749.3 GB)
|
+-> Logical Volume Family 602297D8-5616-41AC-A639-2BA43C50DB4C
----------------------------------------------------------
Encryption Status: Unlocked
Encryption Type: None
Conversion Status: NoConversion
Conversion Direction: -none-
Has Encrypted Extents: No
Fully Secure: No
Passphrase Required: No
|
+-> Logical Volume 7EE41451-8421-44AE-A249-343E1A3CCB25
---------------------------------------------------
Disk: disk3
Status: Online
Size (Total): 748925353984 B (748.9 GB)
Conversion Progress: -none-
Revertible: Yes (no decryption required)
LV Name: External
Volume Name: External
Content Hint: Apple_HFS
The thing I am not clear with is:
* why was the HD configured that way ? My MacBook was pre-installed with Lion when I got it, and I upgraded it regularly through the later versions all the way to Yosemite.
* why did the clean install on the SSD not build the same structure using Core Storage ? I thought that this was done automatically during the upgrade to Yosemite ? But not during a clean install ?
Thanks for any clarifications.