10.8.4 Logial Volume Group

Discussion in 'Mac Pro' started by aminadab, Aug 2, 2013.

  1. aminadab macrumors regular

    Joined:
    May 3, 2005
    Location:
    Portland, Oregon
    #1
    i've just got a new hd and have been re-purposing the older, internal 3.5"drives, which means erasing and renaming in disk utility. i've been able to erase the disks and rename/create new volumes.

    now, however, i'm stuck with the remaining drives and the following problem: each time i select the drive and erase/rename, a logical volume group is created. i've been able to erase the group in terminal, but each time i erase/rename in disk utility, a new lvg is created. has anyone seen this before?

    these drives are for media storage only. i don't need to roll my own fusion drive and just want to format and use the disks the "regular" way.
     
  2. bist macrumors newbie

    Joined:
    Jun 13, 2013
    #2
    Try to:
    Code:
    diskutil eraseDisk JHFS+ SomeName diskX
    changing "X" for each disk you used in your core storage group.

    Of course, you'll LOSE EVERYTHING on "diskX" !!!

    PS: I also encountered weird behaviour of Disk Utility after playing with Core Storage.
     
  3. Weaselboy Moderator

    Weaselboy

    Staff Member

    Joined:
    Jan 23, 2005
    Location:
    California
    #3
    Are you (or did you) formatting the drive in Disk Util as encrypted?

    Run the command "diskutil cs list" (without quotes) in Terminal and post up the output.
     
  4. aminadab thread starter macrumors regular

    Joined:
    May 3, 2005
    Location:
    Portland, Oregon
    #4
    Thanks very much for the help. This is a really odd problem -- at least to me.

    First, when I run diskutil cs list, it claims that "No CoreStorage logical volume groups found." Yet I just tried to erase format on disk as "Mac OS Extended (Journaled)" and it created a LVG, renaming both disk and volume the same name and only giving me erase/format access to the volume.

    I've run diskutil eraseDisk JHFS+ SomeName diskX, substituting X for the Disk Description (eg. WDC WD30EFRX-XXXXXXXX) and it returns "Unknown partition scheme: diskWD30EZRX-XXXXXXX"

    Now, when I delete via diskutil coreStorage delete, I get the disk name as "normal" and an "untitled" volume underneath. I can rename the volume in Finder as I like and the disk reads and writes fine. This seems to work, but it's an odd workaround and I'd like to fix this.
     
  5. Weaselboy Moderator

    Weaselboy

    Staff Member

    Joined:
    Jan 23, 2005
    Location:
    California
    #5
    Hmmm... odd. Can you attach the drive and start Disk Util and select the drive then post a screenshot?
     
  6. aminadab thread starter macrumors regular

    Joined:
    May 3, 2005
    Location:
    Portland, Oregon
  7. Weaselboy Moderator

    Weaselboy

    Staff Member

    Joined:
    Jan 23, 2005
    Location:
    California
    #7
    I see you have a 3TB drive there. I was trying to help someone a few days ago with this same issue on a 3TB drive. He called Apple and after some back and forth an engineer called him back and acknowledged there is a bug in Disk Util with 10.8.4 where it will not format larger than 2TB internal drives and cause the logical volume issue you are seeing.

    The solution until there is a fix is to format the drive in an external caddy, then put it back in afterwards.

    Look at the post from Dave toward the bottom of this thread. If you search for this issue, you can see others having the same issue.

    You might be able to work around it by using the command line utility diskutil as explained here.
     
  8. aminadab thread starter macrumors regular

    Joined:
    May 3, 2005
    Location:
    Portland, Oregon
    #8
    That's so helpful, thanks! I can run an external caddy, so I'll try that.
     
  9. aminadab thread starter macrumors regular

    Joined:
    May 3, 2005
    Location:
    Portland, Oregon
    #9
    Quick update: I can confirm that disk utility is able to format 3TB in an external caddy, running 10.8.4. Hopefully Apple will fix this issue soon.

    Thanks again for all your help.
     
  10. Weaselboy Moderator

    Weaselboy

    Staff Member

    Joined:
    Jan 23, 2005
    Location:
    California
    #10
    Glad it worked out. :)
     

Share This Page