unable to update VM to Mojave; "disk" verification problems

Discussion in 'macOS Virtual Machine' started by BrianToby, Dec 22, 2018.

  1. BrianToby

    BrianToby Junior Member

    Messages:
    10
    I have cloned my current OS X install (10.12.6) to a new VM so I can update the VM to Mojave (10.14) but I am running into problems with the formatting of the VM disk image. I get a message "The installer could not verify the disk... run First Aid". First Aid finds "corruption" (full messages below) but says it can't repair it unless I run from Recovery. I used the Parallels boot manager to select to boot from Recovery, and it brings up the utilities menu but it appears to still boot from the same partition and the first aid still fails with a message that the volume cannot be repaired when it is use. I am at a loss on how to go forward with this. I could toss this VM and start again, but it seems likely I'd end up in the same place.

    Running Version 12.2.1 (41615) of Parallels (licensed). Suggestions? Thanks in advance.

    Brian

    Output from Disk Utility "First Aid"
    Checking prerequisites
    Checking the partition list
    Checking the partition map size
    Checking for an EFI system partition
    Checking the EFI system partition's size
    Checking the EFI system partition's file system
    Checking the EFI system partition's folder content
    Checking all HFS data partition loader spaces
    Checking booter partitions
    Checking booter partition disk0s3
    Verifying file system.
    Checking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Checking multi-linked files.
    Checking catalog hierarchy.
    Checking extended attributes file.
    Checking volume bitmap.
    Checking volume information.
    The volume Recovery HD appears to be OK.
    File system check exit code is 0.
    Checking Core Storage Physical Volume partitions
    Verifying storage system
    Checking volume
    disk0s2: Scan for Volume Headers
    disk0s2: Scan for Disk Labels
    Logical Volume Group B124685D-3D22-49B8-B2B7-BDF1E0334D1B on 1 device
    disk0s2: Scan for Metadata Volume
    Logical Volume Group has a 24 MB Metadata Volume with double redundancy
    Start scanning metadata for a valid checkpoint
    Load and verify Segment Headers
    Load and verify Checkpoint Payload
    Load and verify Transaction Segment
    Incorporate 0 newer non-checkpoint transactions
    Load and verify Virtual Address Table
    Load and verify Segment Usage Table
    Load and verify Metadata Superblock
    Load and verify Logical Volumes B-Trees
    Logical Volume Group contains 1 Logical Volume
    Load and verify B29164AE-DE6E-4573-A622-3283E8F037F7
    Load and verify D6761AA3-94DF-45E9-A1BA-ECC7295EEF3C
    Load and verify Freespace Summary
    Load and verify Block Accounting
    Blocks on device 84043139-A9F3-4FD9-8B46-A1673E79C6ED are not accounted for by CoreStorage
    Unable to bootstrap transaction group 5: inconsistent crosscheck
    Continue scanning metadata for an older checkpoint
    Load and verify Segment Headers
    Load and verify Checkpoint Payload
    Load and verify Transaction Segment
    Incorporate 0 newer non-checkpoint transactions
    Load and verify Virtual Address Table
    Load and verify Segment Usage Table
    Load and verify Metadata Superblock
    Load and verify Logical Volumes B-Trees
    Logical Volume Group contains 1 Logical Volume
    Load and verify B29164AE-DE6E-4573-A622-3283E8F037F7
    Load and verify D6761AA3-94DF-45E9-A1BA-ECC7295EEF3C
    Load and verify Freespace Summary
    Load and verify Block Accounting
    Blocks on device 84043139-A9F3-4FD9-8B46-A1673E79C6ED are not accounted for by CoreStorage
    Unable to bootstrap transaction group 4: inconsistent crosscheck
    Continue scanning metadata for an older checkpoint
    Load and verify Segment Headers
    Load and verify Checkpoint Payload
    Load and verify Transaction Segment
    Incorporate 0 newer non-checkpoint transactions
    Load and verify Virtual Address Table
    Load and verify Segment Usage Table
    Load and verify Metadata Superblock
    Load and verify Logical Volumes B-Trees
    Logical Volume Group contains 1 Logical Volume
    Load and verify B29164AE-DE6E-4573-A622-3283E8F037F7
    Load and verify D6761AA3-94DF-45E9-A1BA-ECC7295EEF3C
    Load and verify Freespace Summary
    Load and verify Block Accounting
    Blocks on device 84043139-A9F3-4FD9-8B46-A1673E79C6ED are not accounted for by CoreStorage
    Unable to bootstrap transaction group 3: inconsistent crosscheck
    Continue scanning metadata for an older checkpoint
    Load and verify Segment Headers
    Load and verify Checkpoint Payload
    Load and verify Transaction Segment
    Incorporate 0 newer non-checkpoint transactions
    Load and verify Virtual Address Table
    Load and verify Segment Usage Table
    Load and verify Metadata Superblock
    Load and verify Logical Volumes B-Trees
    Logical Volume Group contains 1 Logical Volume
    Load and verify B29164AE-DE6E-4573-A622-3283E8F037F7
    Load and verify D6761AA3-94DF-45E9-A1BA-ECC7295EEF3C
    Load and verify Freespace Summary
    Load and verify Block Accounting
    Blocks on device 84043139-A9F3-4FD9-8B46-A1673E79C6ED are not accounted for by CoreStorage
    Unable to bootstrap transaction group 2: inconsistent crosscheck
    No valid commit checkpoint found
    The volume B124685D-3D22-49B8-B2B7-BDF1E0334D1B was found corrupt and needs to be repaired
    Storage system check exit code is 1.
    Problems were found with the partition map which might prevent booting
    Operation successful.​
     
  2. BrianToby

    BrianToby Junior Member

    Messages:
    10
    Nevermind. Sigh, I see its time to update to a new Parallels version.
     
  3. Arun@Parallels

    Arun@Parallels Parallels Support

    Messages:
    1,356
    Hi @BrianToby , please let us know if the issue still persists, even after upgrading Parallels Desktop for mac.
     
  4. BrianToby

    BrianToby Junior Member

    Messages:
    10
    I was not able to figure out how to use the VM created in 12.2.1 but I updated to 14.1.0 (we have a site license) created a new VM and that updated to 10.14.2 just fine. So all is now good. Thanks Arun.
     

Share This Page