Logic volume fader bug/glitch

Basically, I was on Logic Pro 9 earlier this evening. Having a bit of a jam and what not. I was happy with what I had so far so I saved it and went out. Once I got home I fancied popping back onto Logic for a bit. When I opened up the project I couldn't help but notice that one of the volume faders was up and was moving up and down a tiny bit. (Between +5 and +6). At first I thought it was dodgy automation so I went and had a look and that wasn't the problem. I started to look into other faders and what I found is that every time I clicked on a fader they would do the same bug/glitch. I've tried all sorts to resolve this issue but nothing seems to be working :/
Thanks for reading c:

ItchyDez wrote:
... every time I clicked on a fader they would do the same bug/glitch. I've tried all sorts to resolve this issue but nothing seems to be working :/
Thanks for reading c:
This usually points to a MIDI control surface malfunctioning and sending out errant messages. Unplug devices to confirm.

Similar Messages

Disk Utility formats Hard Drives as Logical Volume Group

I just replaced a hard drive which had died in my Mac Pro which has OS X 10.9.5. To format the new 3TB hard drive I went to Disk Utility. I used "Erase" in its fastest form and the drive was formatted with the Type: Logical Volume Group.
I remember this was a problem a few years ago when I first put hard drives in this computer. I think it was considered a bug in the Disk Utility in OS X 10.8 that it would automatically format drives greater than 2 TB as Logical Volume Group. The solution for me was to restart the computer with my OS X 10.6 disk and use the Disk Utility in that to reformat the drive. I never really understood why Logical Volume Group was a problem but I just obeyed what the wise ones of the Internet had to say.
So, now I am wondering if I should reformat my new Hard Drive as GUID using my OS X 10.6 optical disk again? If it was a bug in the Disk Utility of OS X 10.8 then why is it not fixed in the Disk Utility of OS X 10.9? Is there an actual problem with having disks format formatted as Logical Volume Group? Is this now just Apple's way of doing things?
Thank you.

keg55 wrote:
You could do your reformat using your 10.6 DVD. That's a decision that's up to you.
Not every bug in a previous OS gets fixed in a new OS.
I don't believe CoreStorage (Logical Volume Group) causes any sort of issues. Whenever one encrypts their Macintosh HD, the format is converted to CoreStorage. Fusion Drives are using CoreStorage and now Yosemite converts portables (laptops) to CoreStorage during the install process. As far as Yosemite is concerned, Apple seems to have gone the route of CoreStorage for portables. Even during the Setup on a portable, FileVault is offered with the default of YES being checked. So, if a customer isn't paying attention and continues with the install, they could encrypt their drive without knowing to uncheck the default checkbox.
Thank you for your reply.
I have decided to reformat my new hard drive using my 10.6 disk. I like being able to split it up into more than one volume if need be.
I understand that not every bug in a previous OS gets fixed, but this strikes me as being really a very large bug, so I think it would be good if Apple addressed it.
It is useful to know about Yosemite's behaviour. When I upgrade to Yosemite I will be a bit more prepared. In fact my MacBook Pro has FileVault on with Mavericks so Yosemite won't change anything there.

OSX Yosemite Logical Volume Group - FIX!

Hey guys,
For anyone wondering or concerned about why, when entering Disk Utility, the SSD name has been changed and you now see Macintosh HD and Macintosh HD below. The one above is listed as a Logical Volume Group with an "online" status while the one below that is your physical HDD (so normal as with previous OS's.
I must note that I do not have any recovery partition when holding option when booting (after installing straight onto Mavericks, nor when making my own bootable copy).
However, I did find a way to fix the Hard Drive name issue and revert it back to original format (I did find this fix online, and it has worked for me).
I included pictures below as well.
First one shows original Yosemite SSD name change (from Apple SSD to Macintosh HD with 18.9MB available)
Second shows your normal HHD name unchanged.
Go to Terminal and enter the following:
diskutil cs list
then you will see a bunch of volumes jump up
enter: diskutil cs revert "UUID"
under "UUID", enter the the Logical Volume code number without brackets.
Do not copy and paste it from terminal into your new terminal line. Write it out.
Hit enter and it will ask to reboot your Mac.
Once, rebooted, your old SSD/HDD name with reappear as in Mavericks.
My entire terminal line is shown in the picture attached.
Either way (SSD name changed or reverted) did not changed how the system performed. Everything is running as it should.
Final result shown in last picture!
Hopefully this is just a bug that Apple will fix.
Please ignore the DiskMaker drive (I was making a bootable copy on my external!!)

Thanks for the tip. I see its a common trouble. But i stuck a problem that cannot be solved with this method cause i dont have revertable logic volume.
SO i cannot install system now. There's no visible disk any more.

Logical Volumes Not Creating w lvcreate? Install??

After following the arch raid guide i have gotten all tge way down to creating logical volumes and i get this
lvcreate -L 20G VolGroupArray -n lvroot
/dev/VolGroupArray/lvroot: not found: device not cleared
Aborting. Failed to wipe start of new LV.
device-mapper: remove ioctl on failed: Device or resource busy
here is vgdisplay
-- Volume group ---
VG Name VolGroupArray
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 17
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 97.75 GiB
PE Size 4.00 MiB
Total PE 25024
Alloc PE / Size 0 / 0
Free PE / Size 25024 / 97.75 GiB
VG UUID rP0ooH-VdCy-fMZM-sB0g-90zi-Gv2o-gBZWC1
pls help i am now stuck

mattbarszcz wrote:So I went back to the live cd, I ran efibootmgr with no arguments, and sure enough there was only 1 entry for the Windows Boot Manager. It seems that efibootmgr commands don't seem to take effect.
Because of bugs in efibootmgr and/or EFI implementations, efibootmgr doesn't always work. Using bcfg from an EFI shell or bcdedit in Windows can be more effective on some systems. That said, if efibootmgr worked for you before, I'm not sure why it would stop working, or why an existing entry might disappear. (Some EFIs do delete entries that they detect are no longer valid. This shouldn't have happened with a whole-disk dd copy, but if you duplicated the partition table and then used dd to copy partitions, it might well have happened to you. I suppose it's conceivable that the firmware detected the change from one physical disk to another, too, and deleted the original entry because of that change.)
I referenced the rEFInd page here: http://www.rodsbooks.com/refind/installing.html#windows and followed the procedure to install an entry for rEFInd from Windows. I was able to add an entry no problem through windows.
Does anyone have any suggestions as to why this doesn't work? Nothing has changed about the system other than the disk.
It's unclear from your post whether the entry you created in Windows now works. If it does, then don't sweat it; just keep using that entry, and if you need to make changes and efibootmgr doesn't work in the future, plan to use either Windows or the bcfg command from an EFI version 2 shell.

Volume Fader and Sends have only 128 Steps Resolution ?????

Hi .
I Notice that the Volume Fader and Send´s have only 128 Steps Resolution ?????
To avoid of the REAL problem you can use the Gainer Plug in and you will get 0.1db Steps for Volume with mouse wheel support...
Why is this not fixed yet...Is Logic Pro not a Professionel Music app .
In compare to other Application like Cubase has Full mousewheel support for ALL Mixing parameter (Volume, Send, etc) with a High resolution.
Love to Mix with Logic but put every time the Gain plug in in every track to have higher Volume resolution takes time.
We need higher Resolution for Faders AND Sends, icl Mousewheel support !!..
Do somebody notice this??
G5 DUAL 2Ghz Mac OS X (10.4.5) WAVES, Powercore, Logic 7.2

logic's name's been changed to protect the guilty.
i keep on pushing that logic's audio engine needs a total re-write.(with bus modelling)
G4 450DP Mac OS X (10.4.4) digidesign, motu, apogee

Controller volume fader changes all fader levels

Hi,
I'm using an M-Audio KeyRig 49 controller.
I set up a whole concert and it worked fine. I set up the keyboard's only fader to control the master volume. But now whenever I touch the keyboard's fader to adjust the master volume each channel's level jumps to the fader level - throwing off all my levels.
I'm new to MainStage (and Logic). How do I separate them so the volume fader only controls the master volume and I can set the channel levels once and leave them?
I have to have it up and running by this weekend.
Thanks!

I may have answered my own question. Seems that when I record with the master fader on a lower level the problem is resolved.

Logical Volume Group and Logical Partition not matching up in free space

I was dual booting Windows 7 and Mountain Lion. Through Disk Utility, I removed the Windows 7 Partition and expanded the HFS+ partition to encompass the entire hard drive. However, the Logical Volume Group does not think that I have that extra free space. The main problem is that I cannot resize my partition. I am wanting to dual boot Ubuntu with this. Any ideas? Any help is appreciated. I will post some screenshots with the details. Furthermore, here are some terminal commands I ran: /dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *250.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_CoreStorage 249.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS MAC OS X *248.9 GB disk1 Filesystem 1024-blocks Used Available Capacity iused ifree %iused Mounted on
/dev/disk1 243031288 153028624 89746664 64% 38321154 22436666 63% /
devfs 189 189 0 100% 655 0 100% /dev
map -hosts 0 0 0 100% 0 0 100% /net
map auto_home 0 0 0 100% 0 0 100% /home CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 52A4D825-B134-4C33-AC8B-39A02BA30522
=========================================================
Name: MAC OS X
Size: 249199587328 B (249.2 GB)
Free Space: 16777216 B (16.8 MB)
|
+-< Physical Volume 6D7A0A36-1D86-4A30-8EB5-755D375369D9
| ----------------------------------------------------
| Index: 0
| Disk: disk0s2
| Status: Online
| Size: 249199587328 B (249.2 GB)
|
+-> Logical Volume Family FDC4568F-4E25-46AB-885A-CBA6287309B6
Encryption Status: Unlocked
Encryption Type: None
Conversion Status: Converting
Conversion Direction: backward
Has Encrypted Extents: Yes
Fully Secure: No
Passphrase Required: No
|
+-> Logical Volume BB2662B7-58F3-401C-B889-F264D79E68B4
Disk: disk1
Status: Online
Size (Total): 248864038912 B (248.9 GB)
Size (Converted): 130367356928 B (130.4 GB)
Revertible: Yes (unlock and decryption required)
LV Name: MAC OS X
Volume Name: MAC OS X
Content Hint: Apple_HFS

Here is another try via the command line:
dhcp-10-201-238-248:~ KyleWLawrence$ diskutil coreStorage resizeVolume BB2662B7-58F3-401C-B889-F264D79E68B4 210g
Started CoreStorage operation
Checking file system
Performing live verification
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Incorrect block count for file 2012.12.11.asl
(It should be 390 instead of 195)
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
Invalid volume free block count
(It should be 21713521 instead of 21713716)
The volume MAC OS X was found corrupt and needs to be repaired
Error: -69845: File system verify or repair failed

Finding whole mapping from database file - filesystems - logical volume manager - logical partitions

Hello,
Trying to make reverse engeneering of database files and their physical carriers on logical partitions ( fdisk ).
And not able to make whole path from filesystem down to partitions with intermediate logical volumes.
1. select from dba_data_files ...
2. df -k
to get the listing of filesystems
3. vgdisplay
4. lvdisplay
5. cat /proc/partitions
6. fdisk /dev/sda -l
   fdisk /dev/sdb -l
Problem I have is that not able to determine which partitions are consisten in logical volumes. And then which logical volumens are consisted in filesystem.
Thank you for hint or direction.

Hello Wadhah,
Before start the discussion let me explain I am newcommer to Oracle Linux. My genetic with dba experience of Oracle is from IBM UNIX ( AIX 6.1 ) and Oracle 11gr2.
First task is to get the complete picture of one database on Oracle Linux for future maintenance tasks and make database more flexible and
preparing for more intense work:
-adding datafiles,
-optimize/replace archive redolog files on separated filesystem from ORACLE_BASE
- separating auditing log files from $ORACLE_BASE to own filesystem
- separating diag directory on separated file system ( logging, tracing )
- adding/enlarging TEMP ts
- adding/enlarging undo
- enlarging redo for higher transaction rate ( to reduce number of switched per time perceived in alert_SID.log )
- adding online redo and control files mirrors
So in this context try to inspect content of the disk space from the highest logical level in V$, DBA views down to fdisk partitions.
The idea was to go in these steps:
1. select paths of present online redo groups, datafiles, controlfiles, temp, undo
   from V$, dba views
2. For the paths got from the step 1
   locate filesystems and for those filesystems inspect which are on logical volumens and which are directly on partitions.
3. For all used logical volumes locate the logical partitions and their disks /dev/sda, /dev/sdb, ...

Error message when installing Yosemite OS: this core storage operation is not allowed on a sparse logical volume group

I was updating my Macbook Air (i7, 4mb RAM, 256 gb) to Yosemite OS when the process was interrupted. After retry, my computer is showing the following message: "this core storage operation is not allowed on a sparse logical volume group". I tried to restart several times, but the problem goes on with error. It would be my computer damaged?

If you don't already have a current backup of all data, back up before proceeding. There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
Start up in Recovery mode. When the OS X Utilities screen appears, select Disk Utility.
In the Disk Utility window, select the icon of the startup volume from the list on the left. It will be nested below another disk icon, usually with the same name. Click the Unlock button in the toolbar. When prompted, enter the login password of a user authorized to unlock the volume, or the alternate decryption key that was generated when you activated FileVault.
Then, from the menu bar, select
File ▹ Turn Off Encryption
Enter the password again.
You can then restart as usual, if the system is working. Decryption will be completed in the background. It may take several hours, and during that time performance will be reduced.
If you can't turn off encryption in Disk Utility because the menu item is grayed out, you'll have to erase the volume and then restore the data from a backup. Select the Erase tab, and then select
Mac OS Extended (Journaled)
from the Format menu.
You can then quit to be returned to the main Recovery screen. Follow these instructions if you back up with Time Machine. If you use other backup software, follow its developer's instructions.
Don't erase the volume unless you have at least two complete, independent backups. One is not enough to be safe.

Volume encrypt and erase failed; unable to delete core storage logical volume

I was attempting to slowly migrate [MI-***] from early 2013 MBPRO to New iMac 5K w/Ceiling Level components.
Kept going through LONG process and then told me it couldn't create [MBPRO HD Home Username] "Jim" on volume or whatever. NO FileVault enabling/ still skittish from White iMac Encrypting Nightmare days... I don't even know -- I guess it's encrypted on Airport, but not on MBPRO.
Moved over Applications from outside User account fine; anything inside any User account NOT FINE.
Hooked up Thunderbolt cable between two macs and restarted MBPRO in T mode... displaying the lightning BOLT on screen that moves around to reduce Burn-in.
Was able to go onto desktop and use windows to drag n drop 190G of movies over to iMac... wondering how I was going to get all right settings over form FCP...
Bottom Line: I only have 16G left on MBPRO and need to MOVE video editing to be exclusive on 3T Fusion on Maxed out iMac 5K.
> Have concluded through whole process that I just want to clone the MBPRO and then delete most of the Larger Videos from MBPRO to recover some of my 760G SSD back.
So, I grabbed my 2T Airport Extreme and Hooked up the Cat5 LAN port to Cat5 input on back of NEW iMac; Now my MBPRO doesn't have to be locked up for days, because i can use TimeMachine backup to restore or clone the two macs... i hope.
Went into recovery mode and selected sub-Macintosh HD and attempted to erase; Result time after time after time: "Volume Encrypt and Erase failed." Reason: "Unable to delete the Core Storage logical volume." It dismounts it and I have to restart computer to get it back on. Funny thing is I don't have to use R anymore... which by the way, Command+R appears to be same as just plain old R when restarting... why is that?
This has become a "since Christmas" runaround session for me and I am sick of it.
Please help. I would've called Apple Care [and I did last night while driving... just to get advice on direction. I'm usually a pretty savvy PowerUser but this is driving me crazy.] but have to get things done for a meeting tomorrow. Can work on it after hours if someone can advise today on this post.
Thx,
Jim

I have taken some screenshots of the error I get and the state of my HDD in Disk Utility. I did have a weird thing happen after trying to repair using single user mode, where I reopened disk utility and the partitions were NOT greyed out and displayed the correct info concerning space available etc, although after verifying it then reverted back to greyed out with no info.

Logical Volume Manager

I am planning on installing Arch on a laptop soon. I have played with it in VirtualBox on a separate computer, and I am going to hope that it works with my touchpad / wireless mouse.
I might butcher some jargon in this, but this is how I think LVMs work, and I would like to make sure.
I am going to make partitions for boot, swap, /, and /home.
I know boot only needs to be around 100MB, swap is twice the RAM -- and I saw in another thread, / around 10-15GB -- and /home is the rest.
However, I read about installing on an LVM and it is easy to re-size partitions if needed.
I only have 1 HD, and I'm mostly doing this because while I do have room to have too much space on /, if I end up only using around 4GB, I would like to have that 11GB on my /home for music or videos.
So I think that means I would have something like this:
sda1: boot, around 100MB.
sda2: LVM, which contains swap, /, and /home.
pvcreate /dev/sda2 creates the physical volume on the LVM, allowing me to partition it.
After that, this is where I am confused.
The Arch Wiki says:
Create Volume group(s)
Next step is to create a volume group on this physical volumes. First you need to create a volume group on one of the new partitions and then add to it all other physical volumes you want to have in it:
# vgcreate VolGroup00 /dev/sda2
# vgextend VolGroup00 /dev/sdb1
Also you can use any other name you like instead of VolGroup00 for a volume group when creating it. You can track how your volume group grows with:
Can I skip this since I have only 1 HD? I guess that /dev/sdb1 is the LVM from the other harddrive?
I suppose I would have to do vgcreate VolGroup00 /dev/sda2 just to create the volume goup, though. Is this correct?
After this step, I am pretty much lost. Here's what the wiki says, and how I am interpreting it...
# lvcreate -L 10G VolGroup00 -n lvolhome
This will create a logical volume that you can access later with /dev/mapper/Volgroup00-lvolhome or /dev/VolGroup00/lvolhome. Same as with the volume groups you can use any name you want for your logical volume when creating it.
So later, I would turn this into my home partition during the Arch installation? I would create a lvolswap, and a lvolroot?
Then, during the installation process, I would format them to ext3, and mount them as /home, /, and then select lvolswap as my swap partition?
That's about it for now, I guess.
Last edited by COMMUNISTCHINA (2008-08-15 21:53:41)

COMMUNISTCHINA wrote:
Berticus wrote:
COMMUNISTCHINA wrote:I dunno. I tried using LVM on a virtualbox and I keep getting a kernel panic. I followed the Wiki.
If I put GRUB on /boot, it doesn't work, but I got it to work if I installed it on the / LV.
odd, to my knowledge grub can't be on an LVM. why not install grub on MBR?
I actually figured this out maybe an hour ago.
I changed my GRUB configuration file, but since it's in a virtualbox, out of habit I type arch root=/dev/sda3 on startup, but I needed to type root=/dev/VG00/lvolroot. I had grub on /boot (not on the LVM), but when I was trying to boot, I told it to go to the wrong place for root. I could probably unmount the .iso for the vbox, but whatever.
I will read a little more about RAID.
If I end up figuring out how to do it, would I need my external hooked up to it all the time? I have tote the laptop around, and I wouldn't want the external mucking up the portability.
I wasn't aware you were on a laptop. In that case, a file server would do you best. But cheapest solution would be just to stick with an external hard drive and not RAID.

Logical volume is 'not' in filesystem?

Hi,
I have installed arch linux on a PogoPlug B01, and have used lvm to configure two HDDs into a software-raid 0 logical volume, as such:
lvdisplay
--- Logical volume ---
LV Path /dev/VolGroup00/lvolpink
LV Name lvolpink
VG Name VolGroup00
LV UUID pchxXD-c2j4-phRy-v5q5-3Bfd-R1Vy-TsAete
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 0
LV Size 3.64 TiB
Current LE 953862
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
However, the LV Path does not exist, and the lv doesn't show up in /dev/mapper. The only thing within that directory is a 'control' directory. If I add the LV UUID to /etc/fstab and mount -a, I get the usual 'special device does not exist' error. Does anyone know what may be causing this?
Thanks,
Chris

Hi,
If possible , could you buy without catalogue just to eliminate a business case.
If for non catalogue purchase , the error still occurs thne you probably have a customizing error.
If it works, then we have to focus on the catalog flow side.
Kind regards,
Yann

Failed to revert logical volume group while merging partition

Hi All,
Previously, on my macbook pro, I partitioned my disk for win7 for my dual operation system and only left 120 GB for OS, now I want to delete win7 and return disk space to OS. Currently my OS is yosemite.
I have already deleted disk space for win7 and merged it back to disk0s3. And, I had a problem to merge disk0s2 with disk0s3.
I was told it is because I need to revet my Logical Volume Group. I am blocked at reverting it.
This is my disk info:
rescomp-14-251133:~ rico$ diskutil list; diskutil cs list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage                         119.3 GB   disk0s2
   3:                  Apple_HFS Recovery HD             380.6 GB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           *119.0 GB   disk1
                                 Logical Volume on disk0s2
                                 CC457129-6FE9-41A0-B0D2-F547F21A7555
                                 Unencrypted
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group F454017F-C531-43BA-B270-E2058E05BFF4
    =========================================================
    Name:         Macintosh HD
    Status:       Online
    Size:         119290187776 B (119.3 GB)
    Free Space:   4096 B (4.1 KB)
    |
    +-< Physical Volume AC7A2748-0DA1-49D6-B50C-30348838760E
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk0s2
    |   Status:   Online
    |   Size:     119290187776 B (119.3 GB)
    |
    +-> Logical Volume Family 4B7E6277-69BC-475A-BBB7-7A94D6434D9E
        Encryption Status:       Unlocked
        Encryption Type:         AES-XTS
        Conversion Status:       Converting
        Conversion Direction:    -none-
        Has Encrypted Extents:   Yes
        Fully Secure:            No
        Passphrase Required:     No
        |
        +-> Logical Volume CC457129-6FE9-41A0-B0D2-F547F21A7555
            Disk:                  disk1
            Status:                Online
            Size (Total):          118954639360 B (119.0 GB)
            Conversion Progress:   -none-
            Revertible:            Yes (unlock and decryption required)
            LV Name:               Macintosh HD
            Volume Name:           Macintosh HD
            Content Hint:          Apple_HFS
when I type unlock:
rescomp-14-251133:~ rico$ diskutil corestorage unlockVolume CC457129-6FE9-41A0-B0D2-F547F21A7555 -stdinpassphrase
CC457129-6FE9-41A0-B0D2-F547F21A7555 is already unlocked and is attached as disk1
It is already unlocked
then, I tried revert it
rescomp-14-251133:~ rico$ diskutil coreStorage revert CC457129-6FE9-41A0-B0D2-F547F21A7555
Passphrase:
Started CoreStorage operation on disk1 Macintosh HD
Error: -69750: Unable to modify a FileVault context
Does anyone how I can revert it, then merge disk0s2 and disk0s3

Here is another try via the command line:
dhcp-10-201-238-248:~ KyleWLawrence$ diskutil coreStorage resizeVolume BB2662B7-58F3-401C-B889-F264D79E68B4 210g
Started CoreStorage operation
Checking file system
Performing live verification
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Incorrect block count for file 2012.12.11.asl
(It should be 390 instead of 195)
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
Invalid volume free block count
(It should be 21713521 instead of 21713716)
The volume MAC OS X was found corrupt and needs to be repaired
Error: -69845: File system verify or repair failed

Installing OS X Yosemite has changed my Macintosh HD type to Logical Volume Group

I have just installed OS X 10.10 Yosemite on my late 2013 MacBook Pro with Retina Display,
The installation has worked perfectly and my computer is now running fine. However after opening disk utility I have noticed where previously my HD would be named "Apple SSD...." and the partition underneath would be named Macintosh HD, both are now the same. Also, previously the HD was GUID type and now they have changed to Logical Volume Group and Logical Partition.
I installed the software by creating a bootable memory stick with OS X 10.10 and completed a clean install by completely erasing the HD and then installing the new software. After the HD had been erased, Disk Utility still showed the HD as "Apple SSD...." with the partition "Macintosh HD" below and with Type: GUID. It wasn't until after the installation was complete and I had set up the computer and then gone back into Disk Utility when I released it had changed to both labels being "Macintosh HD" and the format type being Logical Volume Group and Logical Partition.
I have no clue if this is normal and was a planned changed (i.e the software was designed to change it) or if my installation has gone horribly wrong. Can the HD format type be changed back or does Yosemite have to run on Logical Partition and Logical Volume Group formatted HD's.
Any help would be appreciated as I'm not an expert and I have tried googling for hours and can't find anything helpful/useful or that will work.

It's a designed change during the Yosemite install process. John Siracusa's excellent review of Yosemite over at Ars Technica provides some commentary on the change, specifically this page: http://arstechnica.com/apple/2014/10/os-x-10-10/2/

3TB Fusion & logical volume group

I'm in the process of fully reinstalling Mavericks - erasing my internal drive and paring my system way down, to resolve some long lingering issues.
Disk Utility shows the recovery partition as separate (I've booted from it) - but when I went to erase the default Macintosh HD partition I was unable to repartition it as a single partition - it was grayed out - and the TYPE was/is logical volume group - where I was expecting to see GUID. All I could do at that point was ERASE... which I did - so it remains a logical volume group -
I'm unsure if, because of the Fusion drive, this is how they come from Apple - or the previous owner messed with it and trouble could loom wth this setup.
It's a Late 2012 iMac with stock 3TB Fusion Drive.
I'm in the process of reinstalling Mavericks from the Recovery (Internet recovery I'm guessing since it's taking 2 hours). I'm not near an Apple Store unfortunately though do have extended 3 year warranty.
Is it OK to leave the main Macintosh HD as "logical volume group"?????

Yes. That's the technical name for what Apple marketing refers to as a "Fusion Drive." Don't change it.

Logic volume fader bug/glitch

Similar Messages

Maybe you are looking for