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?

Similar Messages

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

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

I'm trying to backup a my harddrive with disk utility but I'm getting an error Unable to create Backup.dmg" (input/output error). Is there any other way to save my data? I believe my hard drive is failing or corrupt file. I can't boot up. Grey screen

I'm trying to backup a my hard drive with disk utility but I'm getting an error Unable to create Backup.dmg" (input/output error). Is there any other way to save my data? I believe my hard drive is failing or corrupt file. I can't boot up. Grey screen and spinning wheel. I've tried everything https://discussions.apple.com/message/20580424#20580424
any help will be greatly appreciated.

Check here. Also have you done a TimeMachine back up?
http://support.apple.com/kb/TS2570

Error message when trying to create DMG with Disk Utility

Have a highly confidential folder on my drive, so am driving to convert to a DMG file, with password protection. It gets nearly done with the DMG process then generates Error - 49168.
Anyone know what means?
1.I choose read-write as my access options
2.Under encryption I choose the AES setting. It asks me to create a password and I create one (unchecking the "remember password option, of course")
3. It seems to get through 95% of the process, then produces that error message.
-- david in KC

A little Googling suggests that Norton Anti-Virus can cause this problem by trying to scan the image as it's being created. The fix seems to be to turn off NAV while creating the image.
If that doesn't work, I'd suggest rebooting from the system disk and having Disk Utility repair the disk, to make sure all is in good working order.

HT3275 I continue to get the following error message: Unable to complete back up.an error occurred while creating backup folder. It's a brand new drive. When I attempt to repair it using disk utility I get:unable to repair disk cannot unmounted

I have been trying to use time machine on a new lacie 2tb usb 2 drive for back up. I continue to get: "unable to complete backup.An error occured while creating backup folder". When I use disk utility to repair I get another error message: unable to repair disk unmountable.
Help me Obie One Canobie you are my last hope

I have confused myself with the facts! Started out keeping track of every step and every variable but have sort of lost it as we progress here. First I quit all applications then swapped connections between mouse port and backup disk port to influence possible bad connections question. Changed power outlet receptacle for the backup disk. Disabled the put-the-HD-to-sleep option. Then powered down the computerator.
Next started up computerator. Turned Time Machine ON and experienced multiple successful backups! Then I started up a few applications, Mail and Text Edit (but not Safari so far). Had a few more successes. After each backup, I used Disk Utility to verify the backup disk is still OK. This because the error about unable to unmount the backup disk seems to go hand in hand with Disk Utility finding the backup disk to be bad.
Put computer to sleep for the night. Upon starting up in the morning, and before doing anything else, I did a backup disk verification... BAD! Did a restart and verified the backup disk... OK.
Did a few Sleep-bad, Restart -OK repetitions.
It seems consistent: Sleeping the computer apparently messes up the backup disk but doing a Restart "repairs" it.
=============================
Now then, I don't understand everything I know here. Methinks that maybe keeping the HD from sleeping during lulls in activity has allowed successful backups through the day but manually putting everything to sleep for the night causes a return to the problem of spinning-back-up-too-slowly (which was explained earlier). Is there any truth in this?
I may abandon this Seagate thing for something more compatible. What's out there that we know works reliably for us?

Unable to create an encrypted disk image with Disk Utility

Hi:
With our upgrade to Lion a few weeks ago, we're now unable to create an encrypted disk image of any type using Disk Utility any more. This problem occurs on 3 different machines, and is reproducible whether one is using an internal HD or an external FW HD. We can successfully create nonencrypted disk images.
This is a duplicate post with all the details here: https://discussions.apple.com/message/18469359#18469359
We haven't had any luck with a solution trying various permissions fixes as helpfully suggested by other readers in response to the error message # (-60008 error), so I'm hoping that someone else has run across a solution from the encrypted disk image perspective and that this tag line will generate some help.
Thank you!

Save As: 01 (on Desktop)
Name: 01
Size: 100 MB
Format: Mac OS Encrypted (Journaled)
Encryption: 256-bit AES
Partitions: Single partition- Apple Partition Map
Image Format: read/write disk image
At the password window that pops up I enter: 1234567890
This says password strength is "Weak"
All works fine
Then I repeated this using:
Save As: 02 (on Desktop)
Name: 02
Size: 100 MB
Format: Mac OS Encypted (Journaled)
Encryption: 256-bit AES
Partitions: Single partition- Apple Partition Map
Image Format: read/write disk image
At the password window that pops up I enter: 1234567890 and when I start to enter the next "1" I get the "Unable to create "02.dmg." (error -60008)
OS 10.7.4
Disk Utility Version 12.1.1 (353)

External hard drives UNMOUNT when verifying with disk utility

I have two external Lacie hard drives attached to my iMac. One is just for general backup purposes. The other is for Time Machine.
Today when I got home, for some reason the Time Machine drive was not appearing on my desktop. I rebooted the computer, the Time Machine drive reappeared, I ran a back up, everything seemed to be working fine.
To make sure the disk was ok - I ran disk utility. When I selected "verify drive" from disk utility - the disk suddenly UNMOUNTED itself, at the point of cataloging the hard drive, and the verification process stalled. What was originally a 1 minute verification suddenly changed to a 17 minute, then a 33 minute, etc.
I tried booting up in recovery mode (Command -R at startup) and the same thing happened. Are the drives going bad?

Actually - I think when disk utility verifies the disk - disk utility itself actually "unmounts" the disk during the verification process. Probably so the disk cannot be accessed by anything else but disk utility.
I feel sort of silly, because what I thought was "stalling" was really just the disk utility going through its proper verification of the catalog file, multi-linked file, directories, etc.

When burning iso with disk utility, the audio is off!

I have an ISO file that works fine when I mount it or watch it on VLC. If I burn it using windows (in parallels) it is fine...
But when I burn it with disk utility, the audio is off by a second or so. I can't figure this out since it is a disk image. there shouldn't be a way to dissociate the audio. I did have a previous version of the iso file that was off.. Is it possible that I am trying to burn an iso file and it is burning a mounted version from before (even though I am choosing this from the finder?)
Any thoughts or suggestions?
I though macs just work. Seems a bit more complicated.

I don't recall for sure about "disk utility" and DVD and/or Bluray. It seems to me that Toast is usually used.

I get an input/output error when i try to restore a functioning backup from my external harddrive to my new internal harddrive through disk utility?

my hardrive Had a smart status warning so i made a backup of it on my external harddrive through disk utility. i checked to make sure that the backup was working and i had no problems with it. i then bought a new internal harddrive and swaped it out but when i was in recovery mode to try to restore my new hardrive i kept getting an error message saying restore error, input/output error

The big dilemma with a new Internal drive is separating Drive operation from 'inside the MacBook' operation. If you had an External Enclosure, you could do all the work (including booting up from the new drive) using the External enclosure.
Then if a know-good drive develops problems only when moved inside the MacBook, it is time to try a replacement cable.

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

I keep getting "unable to connect to web services" when attempting to use them.

I purchased an HP Envy 114. I have connected to the network and am able to print from mulitple computers with no problem. When attempting to connect and authorize web services it asks me to accept the terms, then "checking for product updates". It always comes back saying "Unable to connect to web services. Confirm internet access and try again.". I have set up the wireless and it diesplays the IP Address and Network name. I'm not sure what else to try at this point. There is no help after that, I just keep getting sent in circles.
This question was solved.
View Solution.

Hello davidarmstrong.
Try replacing the DNS server's IP address to 8.8.8.8 and 8.8.4.4.
For this, you will need to enter the printer's EWS by typing the printer's IP address in the URL in any internet browser (Internet Explorer or Firefox).
If you have any doubt, please let me know.
Cheers!
Wixma.
I am an HP employee.
Say thanks by clicking the Kudos star in the post.
If my reply resolved your problem, please mark it as as Accepted Solution so that it can be found easier by other people.

NoSuchMethodError when attempting to obtain InitialContext with WLS 8.1

I am receiving the following exception when attempting construct an initial context
in a WebLogic 8.1 client. Any ideas?
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://localhost:7001
java.lang.NoSuchMethodError: weblogic.utils.Debug.getCategory(Ljava/lang/String;)Lweblogic/utils/DebugCategory;
at weblogic.utils.classloaders.GenericClassLoader.<clinit>(GenericClassLoader.java:52)
at weblogic.rmi.internal.ClientRuntimeDescriptor.<clinit>(ClientRuntimeDescriptor.java:49)
at weblogic.jndi.WLInitialContextFactoryDelegate.<clinit>(WLInitialContextFactoryDelegate.java:173)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:131)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)

I am receiving the following exception when attempting construct an initial context
in a WebLogic 8.1 client. Any ideas?
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://localhost:7001
java.lang.NoSuchMethodError: weblogic.utils.Debug.getCategory(Ljava/lang/String;)Lweblogic/utils/DebugCategory;
at weblogic.utils.classloaders.GenericClassLoader.<clinit>(GenericClassLoader.java:52)
at weblogic.rmi.internal.ClientRuntimeDescriptor.<clinit>(ClientRuntimeDescriptor.java:49)
at weblogic.jndi.WLInitialContextFactoryDelegate.<clinit>(WLInitialContextFactoryDelegate.java:173)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:131)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)

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

Similar Messages

Maybe you are looking for