Tag Info

New answers tagged

0

Your CoreStorage Volume Group doesn't contain a complete stack which also includes a Logical Storage Family and Logical Volume(s) besides the existing Logical Volume Group and the Physical Volume(s). Probably that's the reason why the command fails. But there is no need to resize the stack since it's useless as it is configured now: it doesn't contain a ...


0

Why Disk Utility does it this way is a good question, but when both the drive and volume show like this, its a CoreStorage volume. These terminal commands should put it back to the old way if it isn't encrypted: diskutil cs list - find the "Logical Volume" (not Group) and copy the long "number" at the end of the line (it looks like this: ...



Top 50 recent answers are included