Disk util error bootstrap transaction group:23102

So out of know where my MacBook Pro (13-inch, Mid 2012 10.10) is having problems. Its hanging up on a lot of things like safari, lagging when I turn the volume down, and more. When I try to boot to recovery mode using option nothing shows but my hd, when I do CMD R i am able to go to disk utill. When I tried verifying disk I get these messages. If I hit repair on the top mac had drive(see pic) it just keeps telling me to repair. If I do a verify disk in the second mac hd that is under it and indented it tells me to back up my stuff and reinstall. This transaction group error changes on me many times.
Also I have my fire fault turned off It was on but i turned it off

MRDJones wrote:
… I replaced hard drive …
That was sensible.
… I used a external enclosure on the failed hard drive but I get the same error when trying to use disk utility on it. … The drive will not mount.
Those symptoms are consistent with a failing or failed hard drive.
Related
Storage problems, Core Storage, Disk Utility, checksums, fsck_cs and cksum mismatches

Similar Messages

HT4790 My Mac OS Lion 10.7 FileVaulted HD does not boot, prohibitory sign, stop sign appears some minutes after boot starts. Disk Utility repair shows four error messages: Unable to bootstrap transaction group 2517: inconsistent crosscheck (the same with

My Mac OS Lion 10.7 FileVaulted HD does not boot, prohibitory sign, stop sign appears some minutes after boot starts. Disk Utility repair shows four error messages:
Unable to bootstrap transaction group 2517: inconsistent crosscheck
No valid commit checkpoint found
The volume xxxxxxxxxxxxxx(here it shows physical volume number) was found corrupt and can not be repaired.
Problems were encountered during repair of the partition map
Error: Storage system verify or repair failed.
(the same with 2518, 2519 and 2520 transaction group)
I suppose it is serious bug in Mac OS Lion managing FileVault and wonder what the help could be?

Most likely culprit is your Lacie drives which are notorious for flaky power supplies which cause just the sort of erratic behaviour that you describe. Have had similar issues myself. Lacie has been good about replacing my power converter-- twice. If you have seven of them, good luck finding the bad one or more. Like I said, the behaviour is erratic. Sometimes it'll work sometimes not. I can't comment on Samsung drives because I've never used them and have never heard anything about them. Same with Softraid. Why not just use Disk Utility. Sounds like you're ready for an external hardware raid. This will be much faster, much more reliable, and may even be cheaper than seven firewire drives. Check out G Tech, and Maxx Digital for starters.
Best of luck
Terry

Disk Utiliy error on Disk Repair - Unable to bootstrap transaction group cksum mismatch

When I try to Repair my Hard Disk on Disk Utility (command+R recovery mode) it shows this error:
My hard disk is encrypted with filevault 2 and Disk Utility seems to be unable to decrypt it.
Can I do something with bash? Thank you.
Checking volume.
disk0s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
Invalid Disk Label @ 319200587776: cksum mismatch
Invalid Disk Label @ 319204782080: cksum mismatch
Logical Volume Group 573A27F3-05AE-45D8-8C36-C2190AA709A0 spans 1 device
Logical Volume Group has a 16 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 Volumes
Load and verify EBE1F6D9-1560-4837-BFE4-A8C45CE0252A
Load and verify 1F61CB62-C529-4301-AF2E-B71933C040C3
Unable to bootstrap transaction group 2601: cksum mismatch
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 Volumes
Load and verify EBE1F6D9-1560-4837-BFE4-A8C45CE0252A
Load and verify 1F61CB62-C529-4301-AF2E-B71933C040C3
Unable to bootstrap transaction group 2600: cksum mismatch
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 Volumes
Load and verify EBE1F6D9-1560-4837-BFE4-A8C45CE0252A
Load and verify 1F61CB62-C529-4301-AF2E-B71933C040C3
Unable to bootstrap transaction group 2599: cksum mismatch
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
Unable to bootstrap transaction group 2596: cksum mismatch
No valid commit checkpoint found
The volume 573A27F3-05AE-45D8-8C36-C2190AA709A0 was found corrupt and
needs to be repaired.

MRDJones wrote:
… I replaced hard drive …
That was sensible.
… I used a external enclosure on the failed hard drive but I get the same error when trying to use disk utility on it. … The drive will not mount.
Those symptoms are consistent with a failing or failed hard drive.
Related
Storage problems, Core Storage, Disk Utility, checksums, fsck_cs and cksum mismatches

Unable to bootstrap transaction group 7845 when attempting to fix harddrive with disk utility

Hello,
I recently tried burning a cd from the Mac. I pressed cancel because do forgot to put it at the right speed. So I kept clicking cancel them eventually shut it down. I started it up and I got a "prohibited" sign.
The topic title is their error I get.
(unable to bootstrap transaction group 7845)

No
I dont have enough money to buy one of those "time machine" thingys.
But it's ok. The only thing that is valuble to me was my documents, and they're all sent to my email .
BDAqua wrote:
I was afraid of that after posting then re-reading your title! (
Do you have a Backup?

DiskUtility error: unable to bootstrap transaction group

I get this bootstrap error with a checksum mismatch but searching only found 1 other person with 'chksum mismatch' with 1 reply which was not of use.
"Unable to bootstrap transaction group 611: cksum mismatch
Unable to bootstrap transaction group 609: cksum mismatch"
MacBook Pro 13" early 2011, 10.7.2, Kingston 60 GB SSD as boot volume. FileVault full disk encryption is enabled.
I get this error when use Verify Disk when booted from the volume or even when I try to Repair Disk when I boot from a Lion flash drive or in target mode.
I also get the green OK messages at the end but when I Verify/Repair again, it still shows the same bootstrap errors. Why does this happen? Why doesn't DiskUtility fix it? Is it a bad error? Seems odd that it says OK at the end but still shows the errors.
Thanks.

I'm seeing this issue too. Disk repair wont fix it:
Verifying volume “Macintosh HD”
Checking storage systemChecking volume.
disk0s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
Logical Volume Group 2008965E-D094-4248-A616-CCADC11CCCFE spans 1 device
Logical Volume Group has a 16 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
Load and verify Transaction Segment
Incorporate 1 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Unable to bootstrap transaction group 2149: 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
Unable to bootstrap transaction group 2148: 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
Unable to bootstrap transaction group 2147: 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
Unable to bootstrap transaction group 2146: inconsistent crosscheck
No valid commit checkpoint found
The volume 2008965E-D094-4248-A616-CCADC11CCCFE was found corrupt and needs to be repaired.
Error: Storage system verify or repair failed.

Unable to bootstrap transaction group: inconsistent crosscheck

Disk Utility reports the following errors when I run it on my startup disk 'Macintoch HD'. When I click 'repair' it is not able to complete the repair and suggests to reboot from the recovery disk. When I do that and run DU on 'Macintosh HD', it reports no errors and shows a green result message. I can repeat the reboots and checks with the same results.
What does this mean and how do I resolve it, shy from reinstalling everything?
Verifying partition map for “TOSHIBA MK7559GSXF Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Checking Core Storage Physical Volume partitions
Checking storage system
Checking volume.
disk0s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
Logical Volume Group 6BE3FFB1-1BA7-4853-9AD3-3E896542D4D7 on 1 device
disk0s2: Scan for Metadata Volume
Logical Volume Group has a 16 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 A92E6BFF-144E-4BE7-99B0-D25B2F01B4BF
Load and verify 1D173D02-CDDD-4262-A070-69FB6B2DDE16
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Unable to bootstrap transaction group 5913: 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 A92E6BFF-144E-4BE7-99B0-D25B2F01B4BF
Load and verify 1D173D02-CDDD-4262-A070-69FB6B2DDE16
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Unable to bootstrap transaction group 5912: 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 A92E6BFF-144E-4BE7-99B0-D25B2F01B4BF
Load and verify 1D173D02-CDDD-4262-A070-69FB6B2DDE16
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Unable to bootstrap transaction group 5911: 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 A92E6BFF-144E-4BE7-99B0-D25B2F01B4BF
Load and verify 1D173D02-CDDD-4262-A070-69FB6B2DDE16
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Unable to bootstrap transaction group 5910: inconsistent crosscheck
No valid commit checkpoint found
The volume 6BE3FFB1-1BA7-4853-9AD3-3E896542D4D7 was found corrupt and needs to be repaired.
Problems were found with the partition map which might prevent booting
Error: This disk needs to be repaired. Click Repair Disk.

hshshs wrote:
I had exactly the same problem with Disk Utility reporting "Unable to bootstrap transaction group xxxx: inconsistent crosscheck" errors when booted from Macintosh HD but no errors when booted from the Recovery HD. The following resolved it for me:
1. Turn off FileVault; decrypting the drive took about an hour
2. Run Disk Utility - reported two Macintosh HD, one greyed out
3. Reboot (to see if it resolved 2)
4. Run Disk Utility from Macintosh HD again; only one Macintosh HD and no errors reported
5. Turn on FileVault; encryption took another hour or so
6. Reboot again
7. Run Disk Utility from Macintosh HD again; no errors reported
No reformatting, reinstalling or replacing hard drives, as other reports have suggested.
MacBook Air, 13-inch, Late 2010, OS X 10.8.4, 256GB SSD
Thanks! Worked for me.

Disk Utility Error: The underlying task reported failure on exit 1

    #!/bin/bash
      # Author : Bill Hernandez
    # Location : Plano, Texas
    # Updated : Saturday, June 6, 2009 (1:48 PM)
    # script name : setdisk_ownerenabled
    # make sure to set permissions to execute
    <hr>
    # Description :
    <hr>
    # I've noticed that sometimes when using disk utility I cannot repair permissions, or I might get :
    # ERROR: The underlying task reported failure on exit 1
    # This shell script seems to have solved the problem.
    # It worked very well for me,
    # IF YOU USE THIS SCRIPT, IT IS AT YOUR OWN RISK...
    # DO NOT USE IT UNLESS YOU UNDERSTAND WHAT IT DOES
    # After running it, it is best to restart before using Disk Utility again
    <hr>
    # Details :
    <hr>
    # After partitioning a disk using "Disk Utility", and then begin using it, at some point I would get
    # an arror message when trying to save to one of the partitions, yet when I looked at the permissions
    # everything looked fine. I would then try to use Disk Utility to repair permissions and end up with a
    # cryptic error that pretty much told me nothing.
    # I noticed that while in Disk Utility, if I selected a partition the lower LH corner of the dialog
    # showed : Owners Enabled : No
    # I tried selecting the partitions at the Desktop and doing a (CMD-I) and at the very bottom of each
    # info dialog there was a checkbox :
    # [ ] ignore ownership of this volume
    # which I would check, even after logging in as root, and I couldn't seem to get a consistent way
    # to get rid of the permissions dialog failure, so I found the vsdbutil command which can be used
    # as follows to get partition, or disk info :
    # $ vsdbutil -c /Volumes/driveor_partitionname
    # ----> Permissions on '/Volumes/driveor_partitionname' are enabled.
    # if it is not enabled you can enable the disk or partition using :
    # $ vsdbutil -a /Volumes/driveor_partitionname
    # It will set "Owners Enabled : Yes"
    # This below script loops through the mounted disks, partitions, etc. and gives you information.
    # You can leave the three flags below all set to TRUE, or selectively use what you want and change
    # the rest to false...
    <hr>
    # CHOOSE {"TRUE", "FALSE"}
    <hr>
    getvolumestatus="TRUE"         # get "Owners Enabled : (Yes|No)" status
    setvolumestatus="TRUE"         # set "Owners Enabled : Yes"
    list_volumes="TRUE"                   # show volume names
    <hr>
    # DO NOT CHANGE ANYTHING BELOW HERE
    <hr>
    if [ $getvolumestatus == "TRUE" ]; then
     echo '============================='
     echo '$getvolumestatus'
     echo '============================='
     # get "Owners Enabled : (Yes|No)" status
     for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
     vsdbutil -c $i
     done
    fi
    <hr>
    if [ $setvolumestatus == "TRUE" ]; then
     echo '============================='
     echo '$setvolumestatus'
     echo '============================='
     sudo echo -n
     # set "Owners Enabled : Yes"
     for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
     sudo vsdbutil -a "$i"
     echo "setting Owners Enabled : Yes for ---> $i"
     done
    fi
    <hr>
    if [ $list_volumes == "TRUE" ]; then
     echo '============================='
     echo '$list_volumes'
     echo '============================='
     for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
     echo $i
     done
    fi
    <hr>


As it turns out, this didn't completely solve the problem, it solved part of the problem.
Here is a summary to the root cause of the problem.
SUCCESS...
Problem Summary : The system crashed and would hangup during boot, tried many things, until I eventually erased the disk and started over again.
iMacG5 24 GHZ Intel with One internal disk partitioned into 3 logical drives
Cub_1 OS X 10.5.7
Cub_2 OS X 10.5.7 (Carbon Copy Cloner backup of Cub_1)
Cub_3 OS X Server 10.5.7 (standard os x server setup)
At some point after setting up standard preferences, OS X Server crashed.
When I tried to restart, the machine would hang up during boot.
Finally after several attempts, ran Disk Utility from install dvd and repaired Cub_3
When I tried to run "Repair Permissions" on Cub_3 from install dvd, I got an error
Disk Utility Error: The underlying task reported failure on exit 1.
Rebooted, and started in single user mode (CMD-S) during boot until I saw the unix commands on the screen
RAN : root # fsck -fy
Then I began seeing the same command filling the screen :
posix_spawnp("/usr/sbin/mDNSResponder") could not find file or directory
Called Enterprise Support and spoke to Frank Alcorn, he said this was most likely a permissions problem and asked me to try repairing permissions from the install dvd. I told him about the error, but nevertheless I tried it again and got the same Disk Utility Error: The underlying task reported failure on exit 1..
He asked me to try booting into single user mode again, and to try
root # chmod 775 /
root # reboot
During the reboot process the machine got hung up again, and could not get the single user mode to work at all.
Frank said the command needed to be :
root # chmod 1775 /
Frank asked me if I had changed anything in file sharing, and I told him I had. He asked me what I had shared, and I said the entire drive Cub_3. He asked me what I had done for permissions, if I had denied permissions to anyone. I told him that I had set myself up as the only user that could have access to it, and when he said that's where the problem was the lightbulb went off, and it made sense.
Shortly after I set the sharing preferences is when the server crashed. It all makes sense now...
Frank said not to share the entire disk, only portions (share points) of it. I had done this in Panther Server, and Tiger Server and it worked fine, but apparently Leopard Server works a little differently, maybe more secure.
It seems to me that if sharing the entire disk, which is what I needed would cause such a problem there should have been some sort of warning from the operating system, but there wasn't. I had run into this problem several times over the past three weeks since I had started working with Leopard Server, but in each case I ended up re-installing OS X Server and starting over again.
I told him I would try to reboot from the OS X partition (Cub_1) and try it from there.
He asked me to let him know if it worked, and I said I would...
Problem FIX :
I booted back into the partition containing OS X (Cub_1) and did the following via the Terminal.
$ su - root
$ chmod 1775 /
$ reboot
During the reboot process I held down the (OPTION) key, and selected Cub_3 (the os x server partition) and sure enough after a few minutes of holding my breath the login window magically appeared. So I logged in, and did not have to re-install the server. Hallellujah....
This solved the boot hang problem. It is great to finally have an answer. In retrospect it makes sense, but that's why its hindsight...
The reason for sharing the entire disk in my mind was that since I was the only user on the system, it was easier to have one disk mounted on my workstation rather than several folders. It made sense to me, it still does. I don't need a bunch of folders, just one disk is easier...

Disk Utility error when verifying DIY fusion drive

Hi,
It has been a while since I had to post a problem, but I need others advice on this if you can help. When 10.8.3 came out I installed an M4 512gb ssd in my main drive bay of 2008 unibody aluminium macbook and put a 1tb spinner in the optibay. Created a fusion drive, migrated data and all has been great. Decided to run disk utility today to check for any errors as I had a sleep issue with the 10.8.4 update which I ended up solving by changing the sleep settings in terminal - the issue had caused a few forced shutdowns. I have Disk Utitliy Version 13 (450). The Fusion drive is shown as the logical volume group followed by the volume disk. When I run a verify disk on the volume itself it is all ok:
Verifying volume “Cybernet”
Checking storage systemChecking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 2170 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
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 6 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 309877EC-EA53-443C-A75C-63C159B04EF3
Load and verify 5388E543-6974-4251-BDBD-FA850C121897
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.
Checking file systemPerforming live verification.
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 Cybernet appears to be OK.
When I run it on the LVG it comes up as:
Verifying partition map for “M4-CT512M4SSD2 Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Checking Core Storage Physical Volume partitions
Checking storage system
Checking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 2170 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
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 40 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 309877EC-EA53-443C-A75C-63C159B04EF3
Load and verify 5388E543-6974-4251-BDBD-FA850C121897
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.
Incorrect size for volume “Cybernet”
Problems were found with the partition map which might prevent booting
Error: Incorrect size for logical volume.
Verifying partition map for “WDC WD10JPVT-00A1YT0 Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Checking Core Storage Physical Volume partitions
Checking storage system
Checking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 2170 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
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 43 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 309877EC-EA53-443C-A75C-63C159B04EF3
Load and verify 5388E543-6974-4251-BDBD-FA850C121897
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.
Incorrect size for volume “Cybernet”
Problems were found with the partition map which might prevent booting
Error: Incorrect size for logical volume.
I got the same when I did a safe boot and when rebooted from the recovery partition.y question is, do I repair or could it damage my setup? eg is Disk Utility being accurate and it can repair the error, or is it a phantom issue that should be ignored bearing in mind it's a DIY fusion drive and it could end up getting mashed?
Thanks!

Hi,
The computer's running fine since I sorted the sleep issue. No issues as far as I can tell, which is why I was surprised to see the error. What does the error actually mean - is it saying that the volume is a different size than the computer thinks it should be and therefore it'll just change a few values? In which case I suppose a repair is harmless? I just don't want to repair and then reboot to find the volume corrupted.

Disk Utility error -206

I am building a restorable image of 10.4.9 - or rather, trying to build an image, as I just ran into error -206 for the 2nd time.
I add stuff to my source in logical groups, then make and test an image. The error occurs at the end of a block restore, when Disk Utility is comparing checksums (running in dutch, so this may not be the wording in english). There is no error message, aside from the number. The target volume is unmountable after this. File restore is OK, except for the odd invisible file turning visible. Block restore appears fine when I skip the checksum comparison.
The 1st time it happened I made my 'install portions' smaller, and found that the error occurred after adding iTunes 7.1.1 to the image. However, now that it happened again with some 3rd party software I am really puzzled.
My work volume runs 10.4.4, the source partition is on the internal drive, and my test partition is on a Lacie Porsche drive.
So what's this error -206??
Imac G5 Mac OS X (10.4.4)
Imacs G3 & G5 Mac OS X (10.4.4)

Cornelius,
Both of your links seem to apply to OS 9.
Yet, there may be something here, as they both indicate a problem with 'sound'; the msg itself claims a corrupt snd resource, and the app "Error codes" says it's a Sound Manager error.
So I went looking in iTunes.
In its Resources folder there's "Complete.aif".
When I doubleclick this, it shows up in iTunes as "sappy.snd".
Now I am really puzzled.
FWIW: DiskWarrior 3 had a problem with the same aif file when Quicktime was updated to 7.0.x (forgot which one).
I will see what happens when I remove this aif file, then post back.
Another open point; I found I could block-restore an image with iTunes 7.1.1 if I checked 'skip checksum' in Disk Utility. The man page for asr calls this 'dangerous' but doesn't specify the dangers. Would you know anything about this?
About my setup: I do not update my working volume. Instead, I start from scratch on a spare partition, then migrate when this turns out OK. I make and test images while building.
Thanks (again) for your help.
Imacs G3 & G5 Mac OS X (10.4.4)
Imacs G3 & G5 Mac OS X (10.4.4)

Disk utility error message

My daughter told me her Mac mini isn't booting up past the grey screen. I put in the install disk and started it up pressing "C" and used Disk Utility to attempt to figure out what's up. I got the following error message:
Could not repair due to underlying task failure on exit (-9972)
Does this mean the hard drive is toast? I don't have any HD repair software-with all my Macs I've never run across a problem that the boards here or Disk Utility couldn't fix for me. I don't know if she damaged the drive (she claims the cat chewed on the edge of the mini-sounds a bit like the "dog ate the homework"), or if it failed. It was purchased last year when Tiger was released, so it should still be under warranty. Any ideas about what I could try next?
Thanks
~margaret
17 iMac G4 1.25GHz 160GIG HD Mac OS X (10.4.3) G4 iBook, Mac mini, 10G iPod, iPod mini (pink!), Apple IIGS

Dale, although the -9972 error is probably some serious data error on the drive, which can sometimes be solved by an Erase & Install of Mac OS X, the fact that the Hardware Test reports an issue probably means that the data error was caused by physical damage on the drive.
I have to say that I find your post(s) most unhelpful. It' true that the informatin contained in them can be useful, however, you could have made the effort to sort it for iMargB. The fact that you didn't, plus your posting of the exact same post in two different threads, makes me feel that you are in a hurry, and that you sacrifice quality to quantity. Trying to help as many people as possible is a good thing, however, we are here to help (or to be helped), not to overwhelm people with information, hoping that they will figure it all out on their own.
iMargB, the Hardware Test is not part of Mac OS X, it is a system-specific volume, which explains why it is included on your original disc rather than on the Tiger one. Your guess of using the latest OS's Install disc was a good one though, when it comes to using Disk Utility for example : attempting to repair a Tiger installation with a Panther disc is not a good idea, as it might damage it instead, because of the differences between Panther and Tiger.
Although I know little about the Hardware Test's error messages, the "Master" part is not what would worry me, as it could just be the position of your hard drive's jumper (which could be Master, Slave, or Cable Select). However, if the Mass Storage test is failing, I would suspect a hardware issue with the drive itself. Hardware Test is known to miss a few things sometimes, but the reverse isn't true. Thus if it reports a bad drive, I think it is safer to assume that there is an issue than to assume that Hardware Test is wrong. Moreover, the "Invalid Node Structure" is very likely due to physical damage (as I already said), therefore, zeroing out all data and reisntalling Mac OS X or using Disk Warrior could be very temporary fixes.
If you have a FireWire cable, I would suggest booting your Mini in FireWire Target Disk Mode to retrieve as much data as you can, with another Mac such as your iMac or iBook. Instructions can be found here. There may still be a chance that the other Mac could see the drive, so not all your data would be lost. Then, I would take it to Apple for repair, as the drive could be failing.

MacBook Pro Stuck in Recovery Loop; Disk Utility Error

I am getting the error: Disk Utility Stopped Repairing "disk0s2" - says disk utility can't repair the disk and I will need to reformat the disk and restore my files. This appears to be the startup disk (could be wrong) - as I am currently in recovery mode and any time I reboot, I am taken back to recovery mode and there are no start-up disks available to be selected.
When I run Disk Utility on my Internal HD (or what appears to be - this is 250 GB Hitachi) - I get the all clear that everything appears to be working correctly.
I do have TMbackups saved to a NAS. My MacBook Pro has been running very slowly as of recent (slight boost after upgrading to Yosemite, but then returned to slow performance).
I am running OS X Server on it - and have considered migrating that to a Mac Mini (yet to be purchased) - but want to get a better idea of options before I pull that trigger. I also want to make sure my MacBook Pro is recoverable and can still be used.
1. What is the risk of reformatting just the startup disk "disk0s2"? Is that even possible?
2. Is MacBook Pro in need of service at the apple store? Or can this be completed by me? (I have above average ability, but no wizard)
3. My logic on best practice to recover MBP and then add Mac Mini, migrating OS X Server to it: (all recommendations/suggestions welcome)
a. reformat MBP startup disk
b. restore TMbackup
c. use migration wizard to migrate OS X Server to Mac Mini
d. reformat MBP again, starting from scratch and install fresh copy of Yosemite
I had also considered just a fresh build of OS X Server on a new Mac Mini and starting fresh with the MBP. I don't use a ton of services on OS X Server so think my rebuild would be less time intensive than most.
Appreciate all the feedback.

Well, your hard drive (flash storage) is good, at least. Here's what I would try next (before making a trip to the Apple Store or an AASP):
Boot into your Recovery partition and reinstall OS X. This won't damage or erase any of your user files, etc., just give you a fresh installation of Mountain Lion. Since your hardware seems to be OK, it could be that the system has just become corrupt and reinstalling it may 'fix' the problem.
Call back if that doesn't work...
Clinton

Disk Utility Error "no valid packages"

Hi,
I have a PowerBook G4 with 1GB RAM.
I've noticed a significant system slowdown lately. Programs take longer to open and respond, and it's rather annoying. I came to the forums to seek some remedy, and tried to run a Disk Utility to check that everything there is at least okay. But when I click on verify permissions, I get an error that says "no valid packages." Does anyone know what this means and how to fix it (if it needs fixing; I'm assuming this isn't a good thing, whatever it is!).
Thanks.
Lori

Hi librarygirl and Welcome to the Discussions!
Mac OS X 10.3, 10.4: Disk Utility shows a "No Valid Packages" alert
Disk Utility can't verify or repair permissions on the Mac OS X 10.3 or 10.4 volume if the "BaseSystem.pkg" file is not in /Library/Receipts.
This alert appears when you try to repair permissions with Disk Utility:
"First Aid failed
"Disk Utility stopped repairing permissions on '(volume name)' because the following error was encountered: No valid packages"
In the Disk Utility text window, this message appears in red text:
"Error: No valid packages (-9997)"
This happens when the BaseSystem.pkg file is not in /Library/Receipts.
Solution
If you've moved this file, move it back to /Library/Receipts. You shouldn't normally remove any files from /Library/Receipts.
If the file has been deleted, replace it by copying it from a different computer that uses Mac OS X 10.3 or 10.4, or by reinstalling Mac OS X 10.3/10.4 from an installation disc.
"Reinstall" means you can install 10.3 or 10.4 from a disc, if it's the same version of 10.3/10.4 (such as 10.3.3 on both the installation disc and computer). If the version of 10.3/10.4 on the computer is newer than what's on the install disc, then use the install disc to perform an Archive and Install installation instead, then update to a later version of Mac OS X.
Joe

Disk Utility Error-Please Help

I tried to repair my hard disk. I couldn't repair straight away as the repair button was greyed out so I varified the HD. The message came up:
*Disk Utility*
*First Aid*
*Disk Utility stopped verifying “Macintosh HD” because the following error was encountered:*
*The underlying task reported failure on exit*
The result of the varifacation was:
*Verifying volume “Macintosh HD”*
*Checking HFS Plus volume.*
*Checking Extents Overflow file.*
*Checking Catalog file.*
*Incorrect size for file objects.nib*
*(It should be 0 instead of 4514)*
4514
*ng multi-linked files.",0)*
*Checking Catalog hierarchy.*
*Checking Extended Attributes file.*
*Checking volume bitmap.*
*Checking volume information.*
*he volume %@ needs to be repaired.",1)*
*Macintosh HD*
*Error: The underlying task reported failure on exit*
*1 HFS volume checked*
* Volume needs repair*
Could someone please advise me how to fix this.
Thank you.
Simon

You can only Repair Disk from a different boot volume so boot from your Tiger installer disk, select your language and then from the menu>Utilities>Disk Utility. select your hard drive and then Repair Disk. If Disk Utility can't repair it you will need a stronger utility like DiskWarrior to rebuild the directory.

Disk utility error when erasing an external hard drive

Hi,
Not sure if this is the most appropriate fourm list to post this but I thought I'd give it a try.
I am running snow leopard on my MBP and am trying to use disk utility to erase and format an ext. HD. While the disk icon does not show up on the desktop when I connect it to my mac, Disk utility does show the ext. hd in the left column, but no matter what format I try, even just using one partition and selecting zero out all data, I get the following error: "disk erase failed with the error: POSIX reports: The operation couldn't be completed. Cannot allocate memory".
Is the hd dead? Are there other options? I do have disk warrior, version 4.1.1 and it does not regonize the ext. hd.
Please advise.
Thanks,

Thanks for the reply. Yes, I did select the ext hd as the one I wanted to erase (my internal hd is my start up drive). After I selected the ext hd, (there is no volume listed under it so the only thing I can select is the hd itself). that is when I selected erase and then Mac journaled, then named the hd and then after selecting erase, I got the error. Also as a matter of note, if I select firstaid, both the repair and verify permissions are dimmed, so I can't even try to repair the disk. That is when I tried disk warrior hoping that could examine the hd, but since it is not mounted on the d/t, it doesn't show as a drive to check. I don't understand why the ext hd shows up in disk utility, but not the d/t. Also of note is the fact that when I connect that ext had to my Mac with a fw cable, a window opens saying that the drive is not readable and do I want to initialize it or ignore. I choose to initialize and that is when I get the error. Also of note is that I have tried both security options of "don't erase data" and "zero out data" and still get the same error.
Hope this clarifies things a bit.

Is my HD Dead? Reformat Disk Utility Error: secure disk erase failed with the error could not open disk.

Hi,
Fed up with seeing the spinning beach ball I decided to reformat my MacBook Pro...
After backing up everything on an external hard drive I put in the OSX install DVD, restarted the machine and held down 'C'.
I followed the install prcedure, clicking next a few times etc...
I then went into Utilities > Disk Utility. I chose 7-Pass to erase the Macintosh HD and set it off erasing.
I checked the process an hour in and message on screen read:
Secure disk erase failed with the error:
could not open disk
The internal hard drive no longer exists in the disk utility so I cant retry erasing it.
The only thing that appears in disk utility is the OSX install DVD.
I can't even shut down the mac as everything under the apple tab is greyed out!
I'm guessing this means my hard drive is broken right?
If anyone has any other ideas of what to try I'd really appreciate that.
How do I turn the machine off?
If my hard drive is gone then should I consider getting an SSD drive?
Any recommendations for such a drive would be great.
Hope you can help!

Did you partition the drive?
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder. If you need to reformat your startup volume, then you must boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the volume(s) mount on the Desktop.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Steps 4-6 are optional but should be used on a drive that has never been formatted before, if the format type is not Mac OS Extended, if the partition scheme has been changed, or if a different operating system (not OS X) has been installed on the drive.

Disk util error bootstrap transaction group:23102

Similar Messages

Maybe you are looking for