Logical volume activation during bootup shows "Maps lock" errors

this started happening sometime after the creation of two lvm snapshots (including 1 root volume snapshot which, as i have since read, may be an issue) but this has never happened to me before in conjunction with snapshotting.  the following outputs before the system successfully finishes booting:
:: Running Hook [lvm2]
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised:
Scanning logical volumes...
Reading all physical volumes. This may take a while...
Found volume group "a1vg1" using metadata type lvm2
Activating logical volumes...
Internal error: Maps lock 14528512 < unlock 14532608
Internal error: Maps lock 14548992 < unlock 14553088
this is annoying but beyond that seems innocuous enough.  the system is stable.  can anyone tell me what this error means or refer me to the proper documentation?
TIA

I have also these messages. It had gone away, but few days ago it came back ...

Similar Messages

  • Good evening, Have been buying ipad4 device used by a licensed legal place in the UAE during use shows that locked the machine by the previous user's icloud I can not deal with it, please help

    Good evening,
    Have been buying ipad4 device used by a licensed legal place in the UAE during use shows that locked the machine by the previous user's icloud I can not deal with it, please help

    amr35 wrote:
    But I want to figure out a solution to this problem because I was not able to get to the first user because I did not know this person, or access to the store where you purchased the working conditions, please help because I had paid an exorbitant amount to buy
    There is no solution other than having the device cleared by the former owner. If you are trying to activate an iPad or iPhone and it is asking for a previous owners Apple ID and password, you have encountered the Activation Lock. This is a security feature that prevents thieves from setting up and using a stolen or lost iPad or iPhone. You have no alternative. You must contact the previous owner to get permission to use the device. If you cannot contact the previous owner return the device to where you bought it and get a refund. You will never be able to activate the device and no one can help you do it.

  • Creating Logical Volume during Oracle VM installation

    Hello,
    I am trying to install Oracle VM Server on a machine with 2 TB hard-disk. There are 2 disks each with 1 TB capacity.
    During Oracle VM Server 2.2.2 installation, if you go with default partitions, layout looks like this
    /dev/sda
       sda1          101M  ext3        /boot
       sda2       952737M  ocfs2       /OVS
       sda3         1027M  swap
    /dev/sdb
       sdb1         3074M  ext3        /
       Free space 950792M  Free SpaceIdeally I would like to give everything except what is needed by */ (root), /boot* and swap to */OVS*.
    So from the layout above, I also want to give Free Space to */OVS*.
    This excerpt talks about Logical Volume Creation during Oracle VM installation.
    During the Oracle VM Server installation, press Alt+F2 to use the terminal, and run the lvm command. When you have finished creating the LVM configuration, press Alt+F1 to return to the Oracle VM Server installation.
    But I couldn't figure out how to do this? Can anyone give me exact steps to achieve what I am trying to achieve.
    regards, Yora

    Hi again
    It seems I downloaded by mistake the Oracle VM Server 3.0.1 Source for x86_64 (64 bit).
    I should have downloaded the Oracle VM Server 3.0.1 for x86_64 (64 bit).
    Now I can get started
    Rudi

  • HT2434 Logical Volume - should show (locked) in sys. profile?

    I recently confirmed the GUID partition scheme- did a wipe, a re-install. I have to enter a disk password, then the passord for the account.
    Logical Volume:
      Revertible:          No
      Encrypted:          Yes
      Encryption Type:          AES-XTS
      Locked:          No   [ is this right? ]
      LV UUID: ----
    Still showing the old (original?)
    Logical Volume Group:
      Name:          7TH COMPANY
      Size:          119.17 GB (119,174,365,184 bytes)
      Free Space:          Zero KB
      LVG UUID: -----
    Hope that my SSD is working properly - that as well as the DISK UTILITY ? Although, I am not a expert user either!!

    It's not clear what the problem is. "Locked: No" means that the volume encryption key is cached in memory.

  • In tune show all summary activity during sync between nb and apple device. One of the summary is memory space status. Audio mayb3gb, photo 2gb, app with 3gb. What is other? Other consist of what type of file?

    In tune show all summary activity during sync between nb and apple device. One of the summary is memory space status. Audio mayb3gb, photo 2gb, app with 3gb. What is other? Other consist of what type of file? It show quite substantial storage capacity?? Anyone can answer what is in other??

    "Other" includes data such as contact information and photos assigned to contacts, calendar events, Safari bookmarks/cookies/history, notes created with the Notes application, SMS messages, email stored locally or cached, and 3rd party application data created and stored by the application.
    If "other" is more than say .75GB at the most, you had a corrupt sync. Try syncing again and if the problem persists, the recognized fix for this is to restore your iPad.

  • The volume controls will not show up in the music app or the lock screen music controls. What do I do?

    The volume controls will not show up in the music app or I the lock screen music controls. What do I do?

    OMG......THANK YOU THANK YOU......I been reading articles after articles and nothing was working......tryed the Crtl+S and there it was. I can not thank you enough......I appricate it    Can not believe it was that simple. I am one happy person again.....

  • 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.

  • Reformatted Mac HD but it no longer has a Logical Volume Group

    Hi Guys,
    I've reformatted my Mac Pro's main HD, prior to doing a completely new install of Yosemite.
    Having reformatted it, I noticed that in the Disk Utility, there is no longer a main hard drive at the top of the list called Macintosh HD, with a Logical Partition (below it) also called Macintosh HD.
    Instead, the main hard drive is now called by it's SSD product name, which is 1 TB Apple SSD SM10... (etc). When I highlight it, the description in the bottom of the Disk Utility window is the same (1 TB Apple SSD...), whereas it used to be called Macintosh HD and its 'type' a Logical Volume Group.
    I have also noticed also that drive beneath it, Macintosh HD, is not referred to in the description as a Logical Partition now, whereas originally it was. (I've been able to make the above comparisons using my MacBook, which has never been formatted since purchase.)
    My questions are:
    - Is there a problem in not having a Logical Volume Group, but instead just having the hard drive specs as the name?
    - If this IS a problem, what is the best way to restore the drive so that I have a Logical Volume Group and a Logical Partition, both called Macintosh HD?
    If anyone can help me out with a layman's understanding of why reformatting my hard drive has set things up differently to the original configuration, and what the impacts are, I'd appreciate it!
    Cheers,
    Mike

    Hi there,
    Thanks very much for helping out with this, much appreciated.
    Here is the info that shows up when I type distil - see below.
    Cheers,
    Mike
    Last login: Sat Mar 21 21:51:41 on console
    MJP-iMac:~ MJP$ diskutil
    Disk Utility Tool
    Utility to manage local disks and volumes
    Most options require root access to the device
    Usage:  diskutil [quiet] <verb> <options>, where <verb> is as follows:
         list                  (List the partitions of a disk)
         info[rmation]         (Get information on a specific disk or partition)
         listFilesystems       (List file systems available for formatting)
         activity              (Continuous log of system-wide disk arbitration)
         u[n]mount             (Unmount a single volume)
         unmountDisk           (Unmount an entire disk (all volumes))
         eject                 (Eject a disk)
         mount                 (Mount a single volume)
         mountDisk             (Mount an entire disk (all mountable volumes))
         enableJournal         (Enable HFS+ journaling on a mounted HFS+ volume)
         disableJournal        (Disable HFS+ journaling on a mounted HFS+ volume)
         moveJournal           (Move the HFS+ journal onto another volume)
         enableOwnership       (Treat as exact User/Group IDs for a mounted volume)
         disableOwnership      (Ignore on-disk User/Group IDs for a mounted volume)
         rename[Volume]        (Rename a volume)
         verifyVolume          (Verify the file system data structures of a volume)
         repairVolume          (Repair the file system data structures of a volume)
         verifyDisk            (Verify the components of a partition map of a disk)
         repairDisk            (Repair the components of a partition map of a disk)
         verifyPermissions     (Verify the permissions of a Mac OS X volume)
         repairPermissions     (Repair the permissions of a Mac OS X volume)
         eraseDisk             (Erase an existing disk, removing all volumes)
         eraseVolume           (Erase an existing volume)
         reformat              (Erase an existing volume with same name and type)
         eraseOptical          (Erase optical media (CD/RW, DVD/RW, etc.))
         zeroDisk              (Erase a disk, writing zeros to the media)
         randomDisk            (Erase a disk, writing random data to the media)
         secureErase           (Securely erase a disk or freespace on a volume)
         partitionDisk         ((re)Partition a disk, removing all volumes)
         resizeVolume          (Resize a volume, increasing or decreasing its size)
         splitPartition        (Split an existing partition into two or more)
         mergePartitions       (Combine two or more existing partitions into one)
         appleRAID <verb>      (Perform additional verbs related to AppleRAID)
         coreStorage <verb>    (Perform additional verbs related to CoreStorage)
    diskutil <verb> with no options will provide help on that verb
    MJP-iMac:~ MJP$

  • 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/

  • Logical Volume Group.

    My 1TB SSD main drive on my MBP Retina volume has changed to Logical Volume Group and the Partition is named Logical Partition.  Now it works fine but was wondering why it has changed from Mac OS Extended (Journaled).  If I want to partition the drive, it is grayed out with no options.  I'm not pleased that I can't control my own drive.  Any answers?

    FileVault is not activated, although it was at one point.  I deleted the partition and...
    I believe that may have caused the problem when I attempted to load the operating system on a new partition from the drive.  I deleted it and thought I reformatted it to Mac OS Extended, but I had major issues because it was locked at one point.  Just recently, I restored to a TM backup which should have formatted the drive correctly but this is what I ended up with.  Like I said, the option is grayed out now.
    Gary

  • N8 - touch-screen still active during phone calls,...

    I've made a few calls with my N8, and I'm finding that the touch-screen is still active when I hold the phone to my ear. I've accidentally hung up on people, or have inadvertently activated other apps. Is this something I can fix in tools?
    The sound during calls is also very low (even at maximum volume), which compounds the above problem even more, as I push the phone closer to my ear.
    If nothing else, the N8 should be able to function perfectly as a phone, and this is really frustrating - I never had this problem with other phones.
    Also, on the 2nd use of the photo edit program, it took a long time to save the photo, and then the phone froze. Is anyone else having problems with this?

    I too fact these problems i.e touch-screen still active during phone calls leading to unintended "hold" on the calls or screens navigating else where. Yes, the side lock bar helps, but then it is not very handy way for a costly model to be designed. Even the older cheaper nokia touch screen model did not have this problem. Let NOKIA people respond to it.
    Yes, the sound is too low even at the maximum. Nokia support centre plead helpless.
    I think we all made a big mistake in investing in this costly handset.

  • 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

  • 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.

Maybe you are looking for