DiskUtility unable to repair

For a few months now, whenever I run "Verify Disk" on Disk Utility, it's given me a message saying something about BitMap having problems, and telling me to run Repair. Unfortunately, when I run repair, it tell me it is unable to repair the disk.
Just recently, I also got this message after "Verify Disk" not only turned up bad results, but it couldn't finish verifying.
Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
*Volume Bit Map needs minor repair*
Checking volume information.
Checking volume information.
t",0)
*(It should be 3822613 instead of 3822612)*
*The volume Macintosh HD needs to be repaired.*
*Error: The underlying task reported failure on exit*
*1 HFS volume checked*
* Volume needs repair*
First of all, what can I do about this? Secondly, I don't have the money to buy Disk Warrior or similar software. I'm also totally fine with re-installing the OS as long as it will totally solve the problem, and I have a foolproof way of backing absolutely everything (this includes emails) up.
Thoughts? I really need help.

Disk Utility cannot repair the drive that booted the computer. Grab your OS installation disc or your system restore disc and boot up with it. After you get to the screen where you choose your language, go up to the menu bar and find the option to run Disk Utility. Now you can repair the drive because you didn't start up with it.

Similar Messages

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?

Disk Utility unable to repair disk

My IMAC started to freeze up for a couple of minutes while running Word for Mac 2004 and Entourage. Microsoft tech support suggested running rebuild database for Entourage. Rebuild database did not execute citing I/O problem. Ran Disk Utility from Install Disk and it was unable to repair one volume after repeated attempts. Also tried ckfs but that found no errors. Some posts recommend Disk Warrior or other recovery software. Any suggestions before the trip to the Genius Bar?

Disk Warrior repaired the disk on its first pass. Disk Utility confirmed the repair. No symptoms any more in Word for MAC and Entourage 2004. Still could not rebuild database. Will back up to be safe.

Unable to repair degraded Virtual disks in Storage Spaces under Hyper-V 2012 R2 Core

Hi all,
I am finding myself in the following conundrum. I have a storage pool under Hyper-V Core, with 2 2TB Seagate drives.
One of the drives completely died (wouldn't spin up, tried it in a different box, still to no avail). I sent it in to Seagate for warranty replacement, got the new drive. Installed it and went through the notions of adding it to the pool and retiring the
one that was with "Lost Communication" status.
Tried to repair the virtual disks that are showing as "Unhealthy-Detached", quickly get 100% complete, but the repair didnt work.
The storage pool is in degraded state.
Looks like metadata is corrupted.
Followed this post to upgrade Storage Spaces to latest version:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/eead59e9-5e49-4bb6-8cbb-1dafddd9576b/unable-to-repair-degraded-virtual-disks-in-storage-spaces-2012r2?forum=winserverfiles
Still, to no avail.
Couple of questions:
1) Is the data on the 3 virtual disks in state "Unhealthy: Detached" not recoverable?
2) How can I get the storage pool back to "healthy"?
Any help will be greatly appreciated.
PS C:\corefig> Get-PhysicalDisk | ? OperationalStatus -ne OK | fl
ObjectId : {1}\\HV001\root/Microsoft/Windows/Storage/Pr
oviders_v2\SPACES_PhysicalDisk.ObjectId="{95
42513c-a0d4-11e3-8123-806e6f6e6963}:PD:{7e22
245f-0cf6-11e3-b1db-806e6f6e6963}"
PassThroughClass :
PassThroughIds :
PassThroughNamespace :
PassThroughServer :
UniqueId :
AllocatedSize : 1218696970240
BusType : Unknown
CannotPoolReason : In a Pool
CanPool : False
Description :
DeviceId :
EnclosureNumber :
FirmwareVersion :
FriendlyName : PhysicalDisk-1
HealthStatus : Warning
IsIndicationEnabled :
IsPartial : False
LogicalSectorSize : 0
Manufacturer :
MediaType : UnSpecified
Model :
OperationalStatus : Lost Communication
OtherCannotPoolReasonDescription :
PartNumber :
PhysicalLocation :
PhysicalSectorSize : 0
SerialNumber :
Size : 1999575711744
SlotNumber :
SoftwareVersion :
SpindleSpeed : 0
SupportedUsages : {Auto-Select, Manual-Select, Hot Spare,
Retired...}
Usage : Retired
PSComputerName :
PS C:\corefig> get-physicaldisk
FriendlyName CanPool OperationalS HealthStatus Usage Size
tatus
PhysicalDisk4 False OK Healthy Auto-Select 73.75 GB
PhysicalDisk0 False OK Healthy Auto-Select 1.82 TB
PhysicalDi... False Lost Comm... Warning Retired 1.82 TB
PhysicalDisk2 False OK Healthy Auto-Select 930.75 GB
PhysicalDisk3 False OK Healthy Auto-Select 74.53 GB
PhysicalDisk1 False OK Healthy Auto-Select 1.82 TB
PS C:\corefig> get-virtualdisk -friendlyname 'Data' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e2229cf-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = CF29227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 548413636608
DetachedReason = Incomplete
FootprintOnPool = 1096827273216
FriendlyName = Data
HealthStatus = Unhealthy
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = False
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 1099511627776
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =
PS C:\corefig> get-virtualdisk -friendlyname 'Backups' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e22255e-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = 5E25227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 743566213120
DetachedReason = Incomplete
FootprintOnPool = 1487132426240
FriendlyName = Backups
HealthStatus = Unhealthy
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = False
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 1649267441664
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =
PS C:\corefig> get-virtualdisk -friendlyname 'Music' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e2238b9-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = B938227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 39728447488
DetachedReason = By Policy
FootprintOnPool = 79456894976
FriendlyName = Music
HealthStatus = Unknown
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = True
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 161061273600
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =
PS C:\corefig> get-virtualdisk -friendlyname 'Videos' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e2225bc-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = BC25227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 223606734848
DetachedReason = Incomplete
FootprintOnPool = 447213469696
FriendlyName = Videos
HealthStatus = Unhealthy
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = False
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 1759325978624
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =

Hi omon_77,
You can first refer the following step by step third party article and KB:
Replace Failed Disks and Repair JBODs for Storage Spaces in Windows Server
https://technet.microsoft.com/en-us/library/dn782852.aspx?f=255&MSPPError=-2147217396
Replacing a failed disk in Windows Server 2012 Storage Spaces with PowerShell
https://www.hodgkins.net.au/storage/replace-failed-disk-in-storage-spaces-pool-with-powershell/
Step By Step: How to Replace Faulty Disk In Two-Way Mirrored Storage Tiered Space
http://charbelnemnom.com/2014/09/step-by-step-how-to-replace-faulty-disk-in-two-way-mirrored-storage-tiered-space-storagespaces-ws2012r2/
More information:
Storage Spaces - Designing for Performance
http://social.technet.microsoft.com/wiki/contents/articles/15200.storage-spaces-designing-for-performance.aspx
Storage Spaces Overview
http://technet.microsoft.com/en-us/library/hh831739.aspx
Windows Server Storage Spaces: What is it and why should I use it?
http://curah.microsoft.com/5049/windows-server-2012-r2-storage-spaces-what-is-it-and-why-should-i-use-it
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Unable to 'Repair Disk' due to Error message

Routine check on the state of my HHD using Disk Utility - Permissions chks all ran fine and good, but not completing the Verify Disk process. The log file (below) was generated:
_Verifying volume “Macintosh HD”_
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
*Incorrect number of Extended Attributes*
Checking volume bitmap.
Checking volume information.
*The volume Macintosh HD needs to be repaired.*
*Error: The underlying task reported failure on exit*
1 HFS volume checked
*Volume needs repair*
unable to Repair Disk unless the full Verify Disk process has finished, is there an easy fix option, or does it signify a bigger problem?

Were you booted up from your install disk when you ran Disk Utility? If not, you'll need to try that and see if the disk can be repaired. If it can't, and you don't have a recent clone that is not damaged to replace the contents of the startup disk with, then Disk Warrior is the best option.
Francine
Francine
Schwieder

Cocktail unable to repair permissions

Hello,
when last time I ran Cocktail to repair permissions, a message popped up saying: >>unable to repair permissions, make sure " " is accessible and receipts are present in the /Library/Receipts folder<<
here is the cocktail log:
2007-06-27 12:22:54.517 Cocktail[196] Cocktail 3.8 launched.
2007-06-27 12:23:11.385 Cocktail[196] Checking for update. No new update available.
2007-06-27 12:24:37.891 Cocktail[196] Launch Services database has been rebuilt.
2007-06-27 12:24:54.226 Cocktail[196] myErrorDict={
NSAppleScriptErrorBriefMessage = "The variable diskNameForPermissions is not defined.";
NSAppleScriptErrorMessage = "The variable diskNameForPermissions is not defined.";
NSAppleScriptErrorNumber = -2753;
NSAppleScriptErrorRange = <00000000 00000000 >;
2007-06-27 12:24:59.154 Cocktail[196] Unable to repair disk permissions. Make sure " " is accessible and the receipts are present in the /Library/Receipts folder.
has somebody any idea how to fix it?
Thank you very much

Please don't post to multiple forums. It's confusing and inappropriate. Close this one and see my response to your other one.

Im getting the following message when I try to open iPhoto "iphoto was unable to repair permissioWhat should I do?

I'm trying to move photos from my Iphone to mt macbook. I'm getting the following message when I try to open iPhoto "iphoto was unable to repair permissions for the library." What should I do?

Post in the iPhoto forum area and let the users there know which version of iPhoto you are using.

After install cluster - all nodes, unable to repair /global....

I install sunCluster 3.1 Update 4 on solaris 8 :
V440 + v440 + v240 (2+1 architector, that meend that the therd node is the standBy and he atached to all disks). + 2* D1000 storageas that was splited.
I install the cluster OK, but after I check with scstat that all is OK and also the qourum is configured OK,
then I scshutdown the cluster and the the nodes came up but they stop due to message
"fsck: could not stat s5: No such file or directory - error."
there is the output on one node :
Rebooting with command: boot
Boot device: /pci@1f,700000/scsi@2/disk@0,0:a File and args:
SunOS Release 5.8 Version Generic_117350-39 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Hardware watchdog enabled
configuring IPv4 interfaces: ce1 qfe1.
Hostname: node2
The /global/.devices/node@2 file system (s5) is being checked.
fsck: could not stat s5: No such file or directory
WARNING - Unable to repair the /global/.devices/node@2 filesystem. Run fsck
manually (fsck -F ufs s5). Exit the shell when
done to continue the boot process.
Type control-d to proceed with normal startup,
(or give root password for system maintenance):
someone know what to do on this situation?
Anather Question is, befor I install the cluster I install the webcomponnet and afterr that there was a message during the boot :
ld.so.1: ifconfig: fatal: relocation error: file /usr/lib/libCrun.so.1: symbol __1cH__CimplJex_threadMget_thr_data6F_p1_: referenced symbol not found
somebody knows why it's happand?
thanks

I install all from the begining, and it's happand again !!!
I belive it's connect to the messages that apperd on each node after the first boot for the scinstall finished.
on each node this message shows :
Configuring /dev and /devices
configuring the /dev directory (campatibility devices)
/usr/cluster/bin/scdidadm: Could not load DID instance list.
Cannot open /etc/cluster/ccr/did_instances.
Booting as part of a cluster.
after all of the node rebooted OK with this messages, I check the nodes and all was OK.
but the I configured the quorum and it was also OK in the scstat -q.
then scshutdown -y -g 0
all the nodes booted with the same messages :
Rebooting with command: boot
Boot device: /pci@1f,700000/scsi@2/disk@0,0:a File and args:
SunOS Release 5.8 Version Generic_117350-39 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Hardware watchdog enabled
configuring IPv4 interfaces: ce1 qfe1.
Hostname: node2
The /global/.devices/node@2 file system (s5) is being checked.
fsck: could not stat s5: No such file or directory
WARNING - Unable to repair the /global/.devices/node@2 filesystem. Run fsck
manually (fsck -F ufs s5). Exit the shell when
done to continue the boot process.
Type control-d to proceed with normal startup,
(or give root password for system maintenance):
Do anyone know what's the problem?
thanks

Downloading mountain lion damaged my hard disc. I took my Mac Pro to apple book store. They are unable to repair it and suggest I purchase a new hard disc for $160. It was a perfectly functioning Mac Pro that got damaged by downloading mountain lion.

Downloading mountain lion damaged my hard disc. I took my Mac Pro to apple store. They are unable to repair it and suggest I purchase a new hard disc for $160. It was a perfectly functioning Mac Pro that got damaged by downloading mountain lion.

Software upgrades do not generally damage hardware; your drive's failure must be co-incidental. On most MBP's, a hard drive is very easily replaced by a user. You might want to check out this site for both hard drives as well as install videos (check which model you have so you can check the correct video):
http://eshop.macsales.com/installvideos/
hard drives:
http://eshop.macsales.com/shop/internal_storage/hard_drives_and_SSD
I just recently upgraded my MBP with an SSD; I purchased an kit with an external enclosure from OWC and cloned the current drive to the new one, installed the new drive and was done in no time.

Upgrade and Install fails after first boot. Then I am unable to repair

I don't know if anyone else has experienced this?
I've experienced the aqua screen of death with the Upgrade option and was unable to resolve it, even after trying the APE removing technique.
So, I decided to restore back to Tiger 10.4.10 (thanks to Super Dupering prior to upgrade) and try the archive and install option. All appeared to go well, installed fine, allowed me to login and run all my apps. But, upon doing my first reboot after the 'sucessful' install the system just hangs at the gray screen. I tried using Disk Utility from the Leopard DVD, but it's unable to repair permissions.
I got this error message: 'The underlying task reported failure on exit'. Tried many times, I also tried the /sbin/fsck -fy in single user mode.
I tried booting into DiskWarrior 4's. Once in DW4 I ran the Repair function there... Here I got another error message.
This error being: 'Error -9997'.
OK I thought, something random must have happened. Soooo I restored to Tiger again and ran the Archive and Install option once again.
I'm am again experiencing the exact same problems with freezing gray boot screen and the inability to repair permissions (all after doing my first boot after sucessful install and login/opening of many apps)
Please please please can anyone she some light on this problem???
I'm going to try one more option:
Upgrade after I've disable all startup options and removing anything to do with APE....
I will report back!
This is really really crap Apple, I can't believe I've spent £85 and probably 15 hours on this sloppy release. Utterly disapointed

Just me it seems then....
Right, I think it's finally resolved, only after the fifth time. I've now rebooted twice and so far so good.
There was a new message when I powered down for the first time, something along the lines of:
Please wait while your Boot Caches are updated.
This seems to be a reasuring message, I feel almost confident in restarting again.
I upgraded using the following method:
1. Disabled ALL startup items (System Preferences>Accounts>Login items)
2. Removed all traces of APE (Application Enhancer) using Finder:
/Library/Preference Panes/Application Enhancer.prefpane
/Library/Frameworks/Application Enhancer.framework
/System/Library/SystemConfiguration/Application Enhancer.bundle
/Library/Preferences/com.unsanity.ape.plist
3. Repaired Permissions
Right, before I perform a new backup I think I'll see how she runs for a week, so I'm sure the boot problem is definitely gone.

Temporarily unable to repair corrupt catalog

i'm running the current version of lightroom. it is giving me a dialog box that says:
temporarily unable to repair corrupt catalog
lightroom encountered problems reading or writing from disk when attempting to repair catalog
the operation may succeed in future attemps
if you wish to try again, please first check available disk space and close all other applications
each time i try, the same dialog box appears.
the corrupt catalog is located on a 1tb drive, 554gb used / 357gb free
what can i do to fix this?

I presume you don't have a recent-enough catalog backup (?)
I bet you won't let that happen again..
Anyway, depending on what's wrong with the catalog, you may be able to recover develop settings (only) via a plugin called WreckHover (free, by me).
In addition to catalog, settings may be stored in:
* xmp if you've saved metadata (if not, I bet you won't let that happen again either) - recovered when importing new photos, or reading metadata (Library menu) of already-imported photos.
* exported versions (if exported with all metadata) - you can recover settings from those via the same plugin: WreckHover.
Note: you'll need to restore a backup catalog first, or start a new one if no backups (really?).
Good luck,
Rob

Disk utility unable to repair disk. What next?

Disk utility unable to repair disk. What next?

I encountered the same problem. After verify disk, I got the message to repair the disk. But it was unable to complete the repair. Rather than purchase Disk Warrior, I tried something else.
What I did was reinstall the OSX (this iMac is still on Leopard). I backed up everything, naturally, before doing the reinstall. I chose the "Archive and Install" option, along with "Preserve Users and Network Settings". This method moves existing files to a folder named "Previous System" and imports existing user accounts, network settings, and home folders into the new OSX.
After the successful reinstall, I ran Disk Utility. It checked AND repaired Permissions. It verified that the disk was fine and no longer needed repair.
If this didn't work, my plan "B" was to reinstall the OSX again, this time with the "Erase and Install" option. Fortunately, I didn't have to go to plan "B".

Unable t repair disk permissions on an external FAT 32 drive

Yesterday suddenly my disk permissions on my Aperture library file changed. It's located on an external fat 32 drive. I'm unable to repair it with disk utility. Now Aperture won't run anymore until I repair this file. Are there any other options then disk utility?

DU can not repair Windows formatted drives. Need to boot into Windows and use its utilities for disk repair.
It's not a goo idea to keep Mac OS X applications or data files on a non-Mac formatted drive. FAT32's filesystem is not compatible with the Mac's. Portions of a file may be removed on the FAT32 drive and it's not fully compatible with OS X filenames and legal filename characters.

Disk Utility and diskutil unable to format or verify or repair

Hi there,
Wondering if anyone can give me troubleshooting ideas on this one:
When I try to partition or format a usb drive (actually I tried 3 models), Disk Utility does the partitioning part but just hangs (soft hang, I can still close it) when comes time to format the partitions. The progress bar just stops in the middle and doesn't move anymore.
I get this message repeated a few times in the system.log file:
diskmanagementd(1367) deny network-outbound /private/tmp/esets.sock
I eventually tried to repair my main HD, thinking that it might be a perms issue but I get a similar problem - it starts to verify and then just hangs there forever. So this issue applies to both format and verify as well as repair. and it applies to USB devices as well as SATA devices.
I was able to repair using the recovery partition but the problem remains intact.
I also tried all the operations with the command line equivalents - always the same thing, either format, verify or repair just hang forever but can wasily be killed.
Given the above log message, I am thinking that diskmanagementd may have lost the permissions it needs to write out of it's andbox - anyone have a clue how I can fix this or if I am in the right direction ?
Thanks !
Phil.

Linc Davis wrote:
Uninstall the useless ESET crapware.
I SECOND THAT, Crapware.

Can't boot up after Yosemite, not even in safe mode. Just hangs, or states unable to repair. Any ideas?

When starting up it tried to install Yosemite, got about half way throught then stated it could not repair the disk (it wasn't broken!). Now it doesn't even try to install, it just get half way through a normal boot up and hangs. Have no access to anything so can't even uninstall/delete. The boot disk that came with my Mac doesn't work either. Can anyone think of a way out of this and still save what's on the disk?

Hey there, it looks like you have a serious issue with Windows. However, as far as I can tell, Firefox is unable to cause this to your system. The update is confined to the Firefox program files, at worst it would make Firefox unusable.
Unfortunately I don't have any idea what might have caused the issue in this case, but I'd suggest asking in forums that are specifically for Windows. They might be able to help you with getting back to a functional system.
--Kadir

DiskUtility unable to repair

Similar Messages

Maybe you are looking for