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

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

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

After getting the dreaded gray/blue screen, I tried to run disk repair on the internal disk. I got an error message saying "Disk Utility can't repair this disk and restore your backed-up files. The volume Macintosh HD could not be verified completely

After getting the dreaded gray/blue screen, I tried to run disk repair on the internal disk. I got an error message saying "Disk Utility can't repair this disk and restore your backed-up files. The volume Macintosh HD could not be verified completely." What do I do now? This is an iMac and I'm running 10.6.8.

Clean Install of Snow Leopard
Be sure to make a backup first because the following procedure will erase
the drive and everything on it. See below for how to clone a drive.
     1. Boot the computer using the Snow Leopard Installer Disc or the Disc 1 that came
         with your computer. Insert the disc into the optical drive and restart the computer.
         After the chime press and hold down the "C" key. Release the key when you see
         a small spinning gear appear below the dark gray Apple logo.
     2. After the installer loads select your language and click on the Continue
         button. When the menu bar appears select Disk Utility from the Utilities menu.
         After DU loads select the hard drive entry from the left side list (mfgr.'s ID and drive
         size.) Click on the Partition tab in the DU main window. Set the number of
         partitions to one (1) from the Partitions drop down menu, click on Options button
         and select GUID, click on OK, then set the format type to MacOS Extended
         (Journaled, if supported), then click on the Apply button.
     3. When the formatting has completed quit DU and return to the installer. Proceed
         with the OS X installation and follow the directions included with the installer.
     4. When the installation has completed your computer will Restart into the Setup
         Assistant. Be sure you configure your initial admin account with the exact same
         username and password that you used on your old drive. After you finish Setup
         Assistant will complete the installation after which you will be running a fresh
         install of OS X. You can now begin the update process by opening Software
         Update and installing all recommended updates to bring your installation current.
Download and install Mac OS X 10.6.8 Update Combo v1.1.
You may be able to backup your data if you have an erased external drive you can use. Before you do the above but after you have opened Disk Utility you can try to clone your drive:
Clone using Restore Option of Disk Utility
1. Open Disk Utility.
2. Select the destination volume from the left side list.
3. Click on the Restore tab in the DU main window.
4. Select the destination volume from the left side list and drag
       it to the Destination entry field.
5. Select the source volume from the left side list and drag it to
      the Source entry field.
6. Double-check you got it right, then click on the Restore button.
Destination means the external backup drive. Source means the internal startup drive.
Now this will only work if the drive is accessible and can be cloned by Disk Utility. Otherwise, you would need to access your drive from another Mac that you can connect via Firewire - Target Disk Mode.

Disk error - can't repair

Hi,
When I startup my Imac it takes forever to get up and running. I sit and wait for the spotlight icon and the other icons at the right top of the screen to open up. When they are present I can begin working, but it takes approximately 10 minutes.
I tried a few times to run the disk-repair app. but I get a weird message that I can't understand. This is what it says ( please note - this is a translation from Danish, so bear with me )
"Controlling the unit 'harddrive'
Controlling HFS Plus-unit
Controlling Extents Overflow-record
Controlling catalogue record
Invalid siblink link ( this line is highlighted in red )
The harddrive unit needs fixing ( this line is highlighted in red )
Error: The task reported an error at the end ( this line is highlighted in red )
1 HFS-unit checked
Units need fixing ( this line is highlighted in red )
I tried to make a disk-repair of the Tiger-DVD but with the same result.
Any help is appreciated a lot.
Imac G5 1,8, 20" 160gb hd Mac OS X (10.4.6)

Try to get your hands on a program called DiskWarrior.
http://www.alsoft.com/alssales.html
If the problem is not totally hardware it should get you back going.
If it is hardware it may help you get going again so to archive important files before replacing faulty equipment.(I had some problems with a ALS iMac that DiskWarrior helped provide time to archive before computer retired.)
I hope you are able to get it fixed.

Disk Utility "Unable to create" Disk Image "error -39"

I am trying to create a disk image using Disk Utility of my wife's user area for backup. Everytime I try, I get the same result. Disk Utility spends several hours creating the archive, then at the very end it generates an error message and terminates the process. The error message is always "unable to create "user" - error -39".
The problem follows her data and not her computer. I backed up her user to an external drive and did the image creation on another computer. Same result.
When I do the same on my computer, the process completes fine.
What problem is Disk Utility having? Where can I find the meaning of Disk Utilitility's -39 error?
PowerBook G4 Mac OS X (10.4.5)

I am still experimenting. To narrow the problem, I decided to create individual disk images of the folders in the User folder. The first one I tried was 7 GB and worked fine. Overnight, I tried one that is 13 GB. It failed with an out of room message on the startup disk! The startup disk has 17 GB free. Nothing should have been written to the startup disk!
This time, I configured Disk Utility to read from the startup disk and write to an external disk. The destination disk had more than enough space. But, I ran out of space on the source. It appears that Disk Utility is writing all or a portion of the compressed file to either the startup or the source disk and running out of room.
Previously, when I created the image of my user folder (instead of my wife's), the source was my user folder on the startup disk and the destinaion for the image was on an external disk. The difference I see is that my startup disk has enough free space for the entire compressed image file.
In my first attempt that gave me the -39, both the source and the destination disks were external. So maybe Disk Utility is creating the image on the source and at the end copying it to the destination. This would explain the difference in the error messages.
I'll try to confirm all of this in the next few days and report my findings.

Error in Disk Repair - PLS HELP

Dear All,
I have posted a message a week ago, about Error in Verifying Permission and Onyx Error -1. Then ~Bee (thanks for the suggestion, really appreciate it) replied and suggested me to try Disk Repair. I tried it this morning and the result was not very promising.
Below are the message:
Verify and Repair disk "Rich's HD"
Checking HPS Plus volumn.
Checking Extends Overflow file.
Checking Catalog file.
Invalid node structure
Volume check failed
Error: The underlying task reported failure on exit.
1 HFS volume checked
1 volume could not be repaired because of an error.
<--end of message-->
I also tried to verify Permission and it ran until 85% and it stopped without any activity until I 'stopped' the verification.
I really hope my HD is not up to something bad. What I have done were only installed CS3 (only installed Photoshop and Illustrator) and it was running fine until recently.
If anyone has any idea or suggestion, please let me know.
Thanks a lot!
Worried,
chityc.

The reason you need to boot from the DVD and run Disk Utility is that an active, mounted disk cannot be repaired.
If you want to save some time (bypassing the need for the DVD) on this and don't mind using single user mode (type a command similar to DOS on a PC) then do the following:
- Restart the Mac and hold down the Command (Apple) and 'S' keys simultaneously. This will put you into what is known as 'Single User Mode' (white text on a black background like DOS).
- At the prompt, type the command fsck -fy and press the 'Return' key.
- This will run through the same check/fix as Disk Utility.
- Repeat if errors are found (you can either retype or press the 'Arrow Up' key of the keyboard to revisit the command.
- If the error is resolved, type the command reboot and then press the 'Return' key. The Mac will reboot into its usual GUI interface.
Note 1: When in Disk Utility, look to the bottom part of the application window for the drive's 'S.M.A.R.T.' status. If it is 'Verified', your hardware is okay.
Note 2: I prefer to install a free app called AppleJack that gives you more functionality (disk check/repair, caches flush, preference checks etc..) in single user mode without needing to know the actual UNIX commands.
- If the error does not resolve (here or with Disk Utility from the DVD), your problem will require either a more powerful tool like DiskWarrior (commercial software) or backing up your present drive, reformatting it and re-installing.

Unable to access disk repair option on OSX Install CD

I tried to do a disk repair from the Install CD - I opened Disk Utility from the Installer menu, clicked on the Mac Harddrive in the left hand column and clicked on First Aid.
While the Repair Permissions was accessible, the Disk Repair option was greyed out.
I did not see any option to choose language during this process.
Can someone please help?
Thanks

That IS the version for some iBook G4s anyway, not certain which one you have though. Did this come from Apple with those Disks?
I don't understand why the Language never showed, or why it "thinks" the Hard Drive is in use, which is what causes that grayed out thing.
Does it Verify from the DVD?
Do you have an Open Firmware Password set perchance?
Tough without the Install disc, but some things to try...
Does it boot to Single User Mode, CMD+s keys at bootup, if so try...
/sbin/fsck -fy
Repeat until it shows no errors fixed.
(Space between fsck AND -fy important).
Resolve startup issues and perform disk maintenance with Disk Utility and fsck...
http://docs.info.apple.com/article.html?artnum=106214
Tough without the Tiger Disk problems, but try fsck...
To use fsck, you must run it from the command line. Unlike using your mouse to open an application to do something, you'll need to type a text command at the prompt (#) to tell fsck what to do. The Terminal application (/Applications/Utilities) and single-user mode are two examples of command-line interfaces in which you can type such commands. To use fsck:
1. Start up your computer in single-user mode to reach the command line. Hold CMD+s keys down at bootup. Note: If necessary, perform a forced restart as described in the Emergency Troubleshooting Handbook that came with your computer. On desktop computers, you can do this by pressing the reset/interrupt button (if there is one) or holding down the power button for several seconds. On portable computers, simultaneously press the Command-Control-power keys. If your portable computer doesn't restart with this method, you may need to reset the Power Manager.
2. At the command-line prompt, type /sbin/fsck -fy
(SPACE between fsck AND -fy important)
3. Press Return. fsck will go through five "phases" and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found: 
The volume (nameofvolume) appears to be OK  If fsck found issues and has altered, repaired, or fixed anything, it will display this message: *** FILE SYSTEM WAS MODIFIED ***   Important: If this message appears, repeat the fsck command you typed in step 2 until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do).
4. When fsck reports that your volume is OK, type reboot at the prompt and then press Return.
http://docs.info.apple.com/article.html?artnum=106214
Then Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.

Since hard drive restore, backup gives Disk Repair, Read-only errors

Hi all -
After a hard drive crash last week, I restored the new HD using my historically reliable wireless Time Capsule (TC) with Time Machine (TM). But ever since, backups have ceased to work. Now, TM spins for about an hour before returning the following errors in sequence:
(1) DISK REPAIR: "The disk 'Backup of [my name] Macbook' was not repairable by this computer. It is being made available to you with limited functionality. You must back up your data and reformat the disk as soon as possible."
(2) TIME MACHINE ERROR: The backup volume is read only. To select a different volume, open System Preferences and choose Time Machine."
I very much doubt there is an actual problem with the TC disk itself; my wife's iBook G4 continues to backup to it without any problem whatsoever. Related threads have suggested:
a) doing clever things with Preferences, such as deleting the com.apple.TimeMachine.plist file and re-booting. However, for some reason (perhaps related to the source of the problem?) I have no such file...
b) using Disk Utility to re-format and/or re-partition (these terms mean little to me) the TC disk. But my Disk Utility doesn't see the TC. (Perhaps related, I no longer actually see the little backup disk icon on the desktop.) And as I've said, I doubt very much it's the TC disk itself that it is the problem.
I have of course tried re-booting everything, as well as un-mounting and re-mounting the TC: Computer, heal thyself! No luck.
Any guidance is appreciated...
(PS If there's a log file I should post that might help with diagnostics, just let me know where to find it.)

I have suffered the same error messages, but without a hard disk crash before it.
I copied the backup-file from the TC to a separate drive, erased the TC, re-installed it, copied the backup-file to the TC en re-initiated TM only to be welcomed with the 'The backup volume is read only'-message again.
Beats me why this happened. Most frustrating part, however, is that I am not able to restore from the backup-file. Any suggestions are highly appreciated!

Disk Repair Errors

I generally run the Disk Repair Utility when I install new software due to some software not abiding by the rules. When I did this a few days ago I came up with the following errors:
Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
Warning: SUID file "usr/bin/lppasswd" has been modified and will not be repaired.
Group differs on "private/etc/cups", should be 0, group is 26.
Permissions differ on "private/var/spool/cups/cache/rss", should be drwxr-xr-x , they are drwxrwxr-x .
In reading most of the postings regarding this condition, there was some hope that it would be fixed in 10.5.5. This is exactly when the errors occurred for me. As soon as I updated:
2008-09-17 13:39:38 -0400: Installed "Remote Desktop Client Update" (3.2.2)
2008-09-17 13:39:40 -0400: Installed "Digital Camera Raw Compatibility Update" (2.2)
2008-09-17 13:41:05 -0400: Installed "Mac OS X Update" (10.5.5)
The modification date on the Finder.app is 2008-09-17 13:41:05, same as the 10.5.5 update. Coincidence? Not likely.
The Disk Utility blurb that these are expected did not include the Finder.app error.

Bruce --
The only real problem here is that the programmers who designed
the Repair Permisions did not have the good sense to just run the
program, and then, when everything is done, simply report
"Repair Completed," or "Everything is A-OK. Nothing to worry about."
Message was edited by: ~Bee

Disk Repair Utility Full Disk Error

Today, my MBP froze, as in it no longer responded to keypresses or moving the mouse, so I held the power button until it powered off. Whenever I try to power it back on, it comes up with the apple logo on a gray screen, and a progress bar briefly appears beneath the apple logo, flashes a few times and dissappears, then the computer turns off.
By running the disk repair utility from the OSX install disk, the OSX partition of my hard drive needs to be repaired. When I try to repair it, it gives me an error saying that the disk is too full to do a repair on (I probably have ~10GB free, so this makes sense), and I need to wipe my disk and reinstall OSX .
I have windows installed via bootcamp and I can still boot into that and see my contents of the OSX partition (e.g. I can play my music, watch movies, open documents all of which are on the OSX partition, I just can't boot to it.).
Although probably unrelated, I've run the diagnostics, and everything came up okay. I've also tried holding shift during boot (trying to get OSX into safe mode) and holding command-option-P-R (clear the PRAM) during boot, neither of which helped.
My current strategy is copy a lot of data off my OSX partition from within my windows partition to an external HDD, in order to free up space on my OSX drive, so that hopefully disk repair can do its job. Does anyone know if this will work, or if not, can anyone recommend an alternate work around?

Backup your files, if possible. Your only recourse is to reformat the drive and reinstall OS X. Do not copy or backup files from Windows. If at all possible boot from another drive like your external HDD by installing OS X on the external drive (unless it is already a bootable drive.) You can then copy your data from the faulty OS X volume before erasing it.
You should never permit your free space to drop so low. One should maintain 10-12 GBs or 10-15% of the volume's total capacity, whichever is greater.
Since this problem will likely recur I suggest you consider just replacing the drive with one that is considerably larger. I would also be sure to arrange to maintain a bootable backup on an external drive in case problems such as this one occur.

Disk Repair Error (Time Machine Partition)

For the second time, my Time Machine backup partition reports errors when I try to mount it (exists on my external hard drive via USB).
As soon as I plug in the USB external, I get this error:
*Disk Repair*
The disk "Backup" was not repairable by this computer. It is being made available to you with limited functionality. You must back up your data and reformat the disk as soon as possible.
I tried looking at it through Disk Utility, and I found "Repair Disk" grayed out, and when I click on "Verify Disk", the output is:
Verifying volume “Backup”
Checking Journaled HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Incorrect number of file hard links
Checking Catalog hierarchy.
Checking Extended Attributes file.
Incorrect number of Extended Attributes
(It should be 29855 instead of 29853)
Incorrect number of Access Control Lists
(It should be 29855 instead of 29853)
Checking multi-linked directories.
Incorrect number of directory hard links
Checking volume bitmap.
Checking volume information.
The volume Backup needs to be repaired.
Error: Filesystem verify or repair failed.
Its worked fine for about 1.5 months since it did this last. My other partition on the external hard drive has always been fine.
Any ideas on the causes of this, or how to fix this aside from reformatting every 1.5 months?
Thanks in advance for your help!

I've had a very similar problem. When I tried to put Leopard on the first time, it wiped out my hard drive directory... Disk Warrior to the rescue. I then bought a brand new internal SATA drive and an external firewire drive for the back up. I formatted both drives and did a fresh install of Leopard on the internal. So far so good-ish. All other weird Leopard bugs and issues aside for now, I am now getting the error message that my Time Machine backup drive (which has been working fine) is irreparable and needs to be formated as soon as possible.
I have the back up drive partitioned and the non-Time-Machine-backup partition, that is the normal simply-storage partition is working fine. The Verify Disk Permissions, Repair Disk Permissions, and Repair Disk are greyed out in Disk Utility. Here's what I get when I Verify Disk.
Verifying volume “G5 Backup”
Checking Journaled HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Invalid catalog record type
Volume check failed.
Error: Filesystem verify or repair failed.
Verifying volume “Scratch”
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 Scratch appears to be OK.
Is a re-format of the back up drive my only option? How did this happen? and How can I prevent this from happening again?
Thanks!
Message was edited by: Corey McNabb
Message was edited by: Corey McNabb

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

Similar Messages

Maybe you are looking for