Disk Utility Drive report anomaly

I've been trying to solve a series of crashes and odd problems on my machine. I always run Disk Utility first and I've never seen this particular item in the report before. In the stream of items reported by Disk Utility (the drive is okay, it says), I get this line:
Checking Catalog hierarchy.
I've never seen the percent sign followed by a single close parentheses.
Is this meaningful?
Dual 2.7 GHz PowerPC G5 Mac OS X (10.4.6)

Probably not. If you re-run Repair Disk do you get the same result? Are there any defects reported? Did you also repair permissions?
What odd problems are you having, specifically?

Similar Messages

Disk Utility is reporting a fatal hardware error-S.M.A.R.T. status failing. Is there hope?

OS 10.5.8 on a 1.8 GHz Power PC G5. Installed Western Digital WD1002FAEX as a second internal hard drive. I also installd the jumper needed to slow HD down for this computer. Initialized and formated the HD was able to back up a large iPhoto file and am still able to acceass the file from the new HD. Now Disk Utility is reporting a fatal hardware error-S.M.A.R.T. status failing. Is there hope?

Is that on your first drive or the new one???
Only experience I had with SMART warning was that in less than 48 hrs it was dead for good.

Disk Utility: MediaKit reports no such partition

What is up with my disk?
On my brand new mac mini, I played around with resizing partitions in Disk Utility, it worked fine, and I eventually returned it to the original single-partition state.
Then, I ran boot camp, and told it to create a 10 GB partition.
Then, I installed Linux (64-bit Ubuntu) -- from the Linux installer I deleted the windows partition, and a zero-size partition before it, and put Linux swap and ext3 partitions in that space.
Now, from the mac side, if I try to shrink the boot partition again, I get the error "MediaKit reports no such partition".
Help? One potentially related anomaly is that Disk Utility shows my Linux ext3 partition format as "MS-DOS (FAT)" but the "fdisk" command correctly lists it as "Linux files*"
Another disturbing thing is that if I type "sudo pdisk" on the Macintosh command line, and give the 'L' command to list partitions on all disks, pdisk exits with the error "Floating point exception"
Here's the log from Disk Utility:
2007-11-04 00:09:19 -0400: Disk Utility started.
2007-11-04 00:09:40 -0400: Preparing to partition disk: “Hitachi HTS541612J9SA00 Media”
2007-11-04 00:09:40 -0400: Partition Scheme: GUID Partition Table
2007-11-04 00:09:40 -0400: 3 volumes will be created
2007-11-04 00:09:40 -0400:
2007-11-04 00:09:40 -0400: Partition 1
2007-11-04 00:09:40 -0400: Name : “Macintosh HD”
2007-11-04 00:09:40 -0400: Size : 90.1 GB
2007-11-04 00:09:40 -0400: Filesystem : Mac OS Extended (Journaled)
2007-11-04 00:09:40 -0400: Do not erase contents
2007-11-04 00:09:40 -0400:
2007-11-04 00:09:40 -0400: Partition 2
2007-11-04 00:09:40 -0400: Name : “Linux Swap”
2007-11-04 00:09:40 -0400: Size : 488.3 MB
2007-11-04 00:09:40 -0400: Filesystem : Mac OS Extended (Journaled)
2007-11-04 00:09:40 -0400: Do not erase contents
2007-11-04 00:09:40 -0400:
2007-11-04 00:09:40 -0400: Partition 3
2007-11-04 00:09:40 -0400: Name : “DISK0S4”
2007-11-04 00:09:40 -0400: Size : 10.2 GB
2007-11-04 00:09:40 -0400: Filesystem : MS-DOS (FAT32)
2007-11-04 00:09:40 -0400: Do not erase contents
2007-11-04 00:09:40 -0400:
2007-11-04 00:09:40 -0400: Modifying partition map.
2007-11-04 00:09:40 -0400: Partition failed for disk Hitachi HTS541612J9SA00 Media MediaKit reports no such partition.
2007-11-04 00:09:41 -0400: Partition complete.
2007-11-04 00:09:41 -0400:
2007-11-04 00:09:41 -0400: Error with partition: MediaKit reports no such partition.

It doesn't sound like you've actually tried reformatting the entire drive, just resizing partitions. There is absolutely no reason why mountability should enter into the picture at all since you can't format a drive if any volumes are mounted.

Disk utility intermittently reports corrupt disk

As a matter of routine maintenance I like to "Verify Disk" in disk utility from time to time.
The issue I am having is that disc utility intermittently identifies that the Server drive is corrupt and needs to be repaired. Here is a typical sequence:
1) Run verify disk and it reports a corrupt disk.
2) Boot up off a different disk and re-run verify / repair disk on the problematic disk and it reports that the disk is fine.
3) Boot up on the original (problematic) disk and re-run verify disk and it reports the disk as fine.
4) Checking again the next day the original problem resurfaces - disk is corrupt.
The server appears to be running fine, but I am loathe to have an issue like this potentially simmering in the background. I am also averse to upgrades until this issue is resolved. Any pointers on getting this resolved would be much appreciated.
Coincidentally, I have run disk warrior and it reports no issues.

Here is the typical disk utility log when reporting the error:
Verifying volume “Server”
Verifying volume when it is mounted with write access.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Incorrect block count for file kdc.log
(It should be 91 instead of 92)
Incorrect number of thread records
Invalid leaf record count
(It should be 1567637 instead of 1567636)
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Volume bitmap needs minor repair for under-allocation
Checking volume information.
Invalid volume file count
(It should be 684309 instead of 684308)
Invalid volume free block count
(It should be 47746895 instead of 47747031)
Volume header needs minor repair
The volume Server was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.

Disk utility is reporting no errors

Hi,
My MBP has been reporting issues over the last few days and recommending that I verify the disk. Whenever I do this, it says that it finds errors and I should reboot with comamnd-r pressed and choose disk utility. Which I do. However when I try to verify the disk or repair the disk in this mode, it never finds any issues? Logging back in and running disk utility will again report issues and recommend repairing
What should I do?
Thanks
Liam

Just noticed other errors reported by Disk Utility ...
Incorrect block count for file lsm_map
(It should be 16129 instead of 17178)
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Volume bitmap needs minor repair for orphaned blocks
Checking volume information.
Invalid volume free block count
(It should be 27769461 instead of 27768412)

Disk Utility Not Reporting Space Correctly

I often add very large files to my system before compressing them, sending them to clients, and then deleting them. This process leaves me constantly thinking about how much disk space I have free. Disk Utility, and an Apple approved app called DaisyDisk (space visualization) typically help me accompish this. Sadly, as of this week I seem to have a problem. When I went and looked the other day Disk U was telling me that 250gb of my 320gb drive is in use. This seemed high to me, but to be safe I thought I'd delete some files I didn't need. After deleting a bunch of videos, and a backup of my Main Identity (19gb) from my system, I'd assumed I had freed up about 24gb, but when I went back into Disk U it was still showing the same 250gb in use. Yes I rebooted my system, and made sure the trash was empty. As I investigated further I did a get info on all 6 folders on the MacHD and they added up to about 170gb. That seemed more realistic, so I did a get info on my MacHD and again it showed the same thing 170 in use and 148.something available. Note: I have no partitions on this drive. But yet, still when I go to Disk U it seemed to be stuck at only 64gb free. Today when I went and looked again I am still seeing the same amount in use and free on the MacHD get info, but on Disk U now I am seeing 108 free and 211 in use. Why the difference? I would think Get Info was pulling from the same place as the mac disk utility.
Would appreciate any insight!
AG

fane_j, again thanks for the heads up on the dated profile ... it's fixed now.
1) I am running Lion, and not sure how or why I posted in the snow leopard category.
2) It says:
Filesystem                                Size   Used Avail Capacity Mounted on
/dev/disk0s2                              319G   202G   117G    64%    /
devfs                                     210k   210k     0B   100%    /dev
map -hosts                                  0B     0B     0B   100%    /net
map auto_home                               0B     0B     0B   100%    /home
localhost:/41KishPaycOkx6AG3BUu4C         319G   319G     0B   100%    /Volumes/MobileBackups
/dev/disk2s6                              750G   727G    23G    97%    /Volumes/Time

Cannot reformat new drive in disk utility, drive unformatted.

Hello everybody. I have a 2010 White MacBook unibody running Mavericks. I recently replaced the internal hard drive with a 750 gig Western Digital Black drive. After installing it, I tried to format using disk utility and it would reformat, the options were greyed out. I cannot seem to partion it either. I do have a full backup of my old drive from Carbon Copy Cloner.
Any help would be appreciated thanks!

After installing it, I tried to format using disk utility
How did you boot the computer with an unformatted drive in it?
If you still have the OS 10.6 disk that you list in your profile, boot from it by restarting with the C key held down. Then start the OS installation process and go to the second screen. In the menu bar, click Utilities and select Disk Utility. Have DU do the formatting - select Mac OS extended journaled.

Disk utility - failure reported - cannot repair

Decided to give my powerbook a thorough check over - mostly by running OnyX.
It raised an issue - which is better described when running 'Disk Utility' - I have attached the output below.
I have tried booting from disk and repairing but this did not work (it did fix one other issue - but this one remains)
What can I do, and what risks does this raise?
Thanks.
Verifying volume “Powerbook 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.
repaired.",1)
Powerbook HD
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
Perhaps I should have posted this in a generic h/w section - but I couldn't find one!

Start with http://docs.info.apple.com/article.html?artnum=106214 and http://docs.info.apple.com/article.html?artnum=302672

TS3423 my start drive not responding. getting grey screen with question mark in a folder. when i use disk utility drive wont mount

When I turn on my Mac I get a grey screen with a folder with a question mark . Have tried the disk utility to no avail as the disk has apparently dismounted and will not mount even though the mount option is available. I have recently upgraded from snow leopard go os x maverick

This could be a software/state problem or a hardware problem. In your case it sounds like the latter but you should try the steps below in case it might help.
Mac OS X: Gray screen appears during startup
http://support.apple.com/kb/TS2570

Disk utility reports "Device could not be opened" - error when trying to format a new drive in a Mac Pro 1,1

MacPro 1,1 Quadcore 3 GHz (2006 "Woodcrest")
32 GB RAM
ATI Radeon HD 5770
OS X 10.7.5 Lion
I have encountered the following behavior when trying to format a new drive with disk utility. This description has also been send via the Mac Pro feedback as a bug report to Apple.
On searching the web and forums with this particular error message and behaviour I could not find any usful results. So maybe the following description may be helpful for some users.
Best regards.
1. Drive Bay 1 contains the original 250 GB Startupdisk. It works without errors.
2. Drive Bays 3 and 4 contain each a WD Caviar Black 2 TB SATA 3 HDD. They work without errors.
3. I have purchased a third WD Caviar Black 2 TB HDD.
4. In Drive Bay 2 there has been a Seagate 750 GB HDD, which worked in conjunction with all the other drives without error.
5. I exchanged the Seagate HDD in Drive Bay 2 with the new WD Caviar Black 2 TB HDD.
6. On starting the system, it will report to initialize the new drive.
7. On trying to initialize the new drive with disk utility it reports the error [translated from German] "Erasing of the volume has failed. The device could not be opened."
8. I thought that the drive is faulty. Thus I created an RMA-Case at WD. They exchanged the drive without problems.
9. On getting the exchanged WD Caviar Black 2 TB drive I put it in Drive Bay 2 as before.
10. On trying to erase and format the exchange drive I got the same error message "Drive could not be opened."
10.1 On selecting the physical drive in the devices list, disk utility reports all information in the bottom area of its window as usual, e. g. hard disk description, connection bus, type and place, capacity, write status, SMART-status, partition scheme.
10.1 On leaving that drive selected in the devices list and clicking the info-button, disk utility will also report additional information as usual, e. g. Name, Type, partition scheme, media-identification, media name, media type, device tree, … , number of relocated sectors, etc.. All this information appears to be valid, as can be compared to the other devices information inside the other Drive Bays. Also the disk numbering scheme appears to be standard - 4 HDDs give the numbering disk0, disk1, disk2, disk3.
10.2 From that information I conclude that the SATA-bus and connectors electrically work properly, the drive has spun up and can be accessed by the system normally.
11. I powered down the computer, took out the HDDs from Drive Bays 3 and 4 and put the caddy with the new exchange drive in Drive Bay 4 [Maybe, I could have also just left it alone in Drive Bay 2, or 3].
12. After powering on the system, disk utility will quick format the exchange drive without any error message. Also, when erasing again by selecting the option to write zeros to the drive, disk utility will finish without error.
13. After disk utility finished formatting, I put back the original drives into Drive Bay 3 and 4 and put the now newly formatted drive back into Drive Bay 2.
14. After switching on the computer the system start and login proceeds without any error message. All drives appear as expected on the desktop.

If anyone is reading this still looking for what caused the issue and how to fix it here is what I discovered.
The antivirus program our company uses, Bitdefender Antivirus Plus, was causing some of the PDF files not to open. After troubleshooting the different modules and settings the culprit was..
Scan SSL in Privacy Control Settings. Turning it OFF solved the problem and all the PDF files that previously would not open now open just fine. This issue has been sent to Bitdefender for them to review. If you use a different antivirus program and are having this issue try locating the Scan SSL setting and see if turning it off solves the problem.

Disk utility reporting wrong size drive

I have a Macbook 4,1 with an 120GB Hard drive. The hard drive has 3 partitions:
12GB Linux Partition
100GB OSX Partition
1GB Linux Swap Partition
It also has 7GB of Free Space at the end of the drive
Now I want to shrink the OSX Partition down to around 80GB (It has 30GB available space) so I have 27GB of Free space to create a Windows Partition. The problem is when I go into disk utility it reports the above partition structure but it also reports I have "100.3GB Free space" at the start of the drive. This is obviously incorrect. It seems harmless enough but the problem is it causes a "The chosen size is not valid for the chosen filesystem" error when I try to resize the OSX partition because the system adds up the size of all of the partitions, realises it's 220GB and so throws the error because it's above the 120GB Drive size. I can't seem to get it to realise that there is no free space at the start of the drive. I've tried using a couple of Linux partitioning programs like GParted and they recognise the correct partition structure but they had a couple of unrelated problems.
Does anyone have any ideas how I can get Disk Utility to sort itself out?

I do not think you can use DU for resizing if you used a linux disk utility before. I never could do that, but am ready to learn how to do that.

Disk Utility: Reporting wrong size for disk after a restore

First up, hardware is G4(PPC) running OS 10.4.11
I've just purchased and installed a new 500G drive for this old workhorse as an upgrade for the previous secondary drive. Set it up with a single partition, JHFS+. No problems so far. Went to copy the files from the old drive to this new one and thought, "Why don't I try that handly looking Restore button?". +Yeah, apparently a bad idea+. The old drive is 120GB. I set its (only) volume to be the source and my newly created partition to be the target; set it going and left it alone. All appeared to be well when I came back, until I checked the available space on the new drive.
Disk Utility now reports that this new, 500G drive has a Total Capacity of 128G (137,438,952,960 bytes).
*Remedies tried so far:*
- I've tried reformatting/partitioning, but wasn't able to convince it otherwise. Also tried it booting from an install DVD just in case that made a difference.
- I downloaded a utility from the drive manufacturer which I managed to get on to an ancient, dusty w2k box. Reformatted the drive with 2 NTFS partitions. This seemed to do the trick as they both mounted when I rebooted the Mac. However, when I went to reformat the volumes to JHFS I noticed that the total disk size was still being reported as 128G. Still, they reformatted fine and I transfered my data to them. On a reboot, though, the Mac decided that it didn't want to see the second partition and only shows me disk1s10, ignoring the second partition I set up.
- I have an identical, empty drive to the 500G. I thought I might be able to use the Restore "feature" to trick it back. Set up the second 500G in a firewire box, ran the restore from the empty volume to the screwed up one. No dice.
I thought that OS X ignored any sort of BIOS info on a drive and merely looked at the physical media. Is this correct? Does it store this gathered info in a file somewhere that I can delete?
*This is a call for help.*
I have no problems playing with the command line as root, if that's the sort of suggestions you've got. I just thought I'd ask here before I fdisk/dd etc from new500 to old500. Geometry of the new500 is 60801/255/63.

Thanks! That sounds like a good short term solution for a backup.
EDIT: Cross reference link for anyone who happens to google this thread with a similar problem:
http://discussions.apple.com/thread.jspa?messageID=7230072&tstart=0
Message was edited by: mr_lunch

Can Disk Utility get SMART status from external drives?

I recently updated my backup plan with a NewerTech quad-interface dock and a WD Caviar Green hd. I'm using the FW800 interface to connect to my iMac (10.6.7) Everything works perfectly, as expected. I noticed, though, that Disk Utility cannot report the SMART status on the new WD drive. DU simply says "Not Supported" under SMART Status.
Is Disk Utility telling me that it doesn't read SMART status from external drives? Or is it telling me that the new drive doesn't support SMART (which I would find highly unusual)? And, if it's Disk Utility that can't read the status, are there any third-party apps that can report the SMART status on an external drive?
Thanks,
JimC

Unfortunately I cannot speak to the NewerTech enclosure, but in principle it appears to be possible to have SMART information displayed even for external drives if the enclosure's bridge controller chip allows it.
My experience:
I've used two MacPower Pleiades FW800/400/USB/eSATA enclosures for several years and I've now supplemented them with two additional inXtron enclosures. They all work as expected daisy-chained to the iMac.
The interesting thing is that the inXtron enclosures came with a CD with some software on it ("Smart AP") which is not available for download, notably a Dashboard Widget for displaying actual and maximum temperatures, total hours of operation, start/stop cycles, drive model and serial number.
This widget is complete garbage, though – it is a nauseating nightmare of extreme over-design at the expense of even basic usability:
http://www.inxtron.com/information-center/smart-ap-for-external-hard-drives
To make matters even worse, it can only display the above information for the first external drive connected.
BUT: This Widget internally calls a command line utility which does the actual parameter retrieval, and that one can be called from the terminal as well.
So after installing the software from CD and effectively discarding the Widget, I checked out the command line utility in the Terminal and found that this utility actually reported data about ALL my enclosures, both the inXtron and the MacPower ones (there seems to be firmware compatibility across these):
(The '$' is supposed to be Terminal's bash prompt – type in only the rest of the respective line.)
$ /Applications/MacpowerAP/GetSMART 1
29 50 13 8
53 67 645 15829
52 53 90 7105
51 52 18 13
Each line reports the following for one connected enclosure:
[temp] [maxtemp] [cycles] [hours]
The drives are reported first USB, then FireWire drives, each in the order of first connection / mounting.
$ /Applications/MacpowerAP/GetSMART 2
WD-WCA**************
WDC WD30EZRX-00MMMB0
5TE09***************
ST31000333AS-00MMMB0
5TE09***************
ST31000333AS-00MMMB0
WD-WMA**************
WDC WD30EZRS-00J99B0
Each drive gets two lines reported, first the drive's serial number ("***" blocking out my exact ones), then the drive model.
$ /Applications/MacpowerAP/GetSMART 3
29 50 13 8
WD-WCA**************
WDC WD30EZRX-00MMMB0
53 67 645 15829
5TE09***************
ST31000333AS-00MMMB0
52 53 90 7105
5TE09***************
ST31000333AS-00MMMB0
51 52 18 13
WD-WMA**************
WDC WD30EZRS-00J99B0
This combines both of the above.
$ /Applications/MacpowerAP/GetSMART 5
disk4
disk1
disk2
disk3
This reports the mounted disk names (referring not to the volume names but to the internal Unix names as in /dev/[drive]); Numbering is in connection / mounting order, the actual sequence is as always USB drives, then FireWire drives.
$ /Applications/MacpowerAP/GetSMART 6
USB
1394
1394
1394
This reports the connection interface for each drive in the same sequence as all other commands.
$ /Applications/MacpowerAP/GetSMART 7
MPT934DS1.20.0104.00
MPT934DS1.20.0104.00
This might report the firmware revision or something like that.
These are the commands I know about, and they apply only to the "Smart AP" software supplied with current inXtron enclosures, but it may be possible that other brands use it as well.
I have not been able to identify information about the self-test (early(?) failure warning), but it might be contained as well in the data reported above.
As always, your mileage may vary and you should never do such experiments without FIRST making sure you've got backups of your data and that such backup is not connected during experimentation!
Maybe this can help some people getting the information they need; And maybe there are similar capabilities with other enclosures. At the very least it demonstrates that with the proper firmware in the enclosures themselves and some software on the Mac it IS possible to get at least some of the SMART information from the drive in an external FireWire- or USB-connected enclosure.
None of that is fed into the system's "official" SMART mechanism, though, so no luck using standard mechanisms or applications for it. It's strictly a command-line affair (deservedly disregarding the mishappen Widget).
Good luck!

Disk utility reports "unused node is not erased" after installing 1TB HD

Hi there,
I just installed a brand new 1TB HD into a 2006 Intel iMac. I booted from the Snow Leopard installer DVD and tried installing the OS, but I received a kernel panic. I rebooted from the installer DVD again and ran Disk Utility which reported multiple instances of "unused node is not erased" and could not repair the disk. I re-partitioned the disk but each time Disk Utility gave the same error. I rebooted from the DiskWarrior DVD and rebuilt the directory (DW found no errors). I then rebooted from SL DVD again and ran Disk Utility which found the same "unused node is not erased" errors but this time was able to repair them! I'm now trying to reinstall the OS for a second time.
I'm wondering from this bizarre behaviour whether
a) I have a faulty (new) HD
b) there might be something else wrong with my mac causing these errors.
Any assistance would be greatly appreciated!
Cheers,
Greg

Well, I attached another good external drive via FireWire, booted the 2006 iMac from the SL installer DVD, partitioned it with DU, then ran DU Repair Disk, and Disk Utility immediately gave me "unused node is not erased" errors and was unable to repair the drive.
I attached the same good external drive via FireWire to another Mac and repeated the same procedure: this time DU gave me no errors at all.
I'm going to assume my 2006 iMac has a faulty logic board or SATA controller (with cost of repairs probably more than the computer is worth). Would you agree?
Thanks again!

Disk Utility reports "keys out of order"

The machine I have is now reporting some worrying signs, when using Disk Utility it reports "keys out of order" which I have no idea what this means.
When starting in single user mode and running sbin/fsck -f it comes back with disk0s5: I/O error keys ot of order. Also its unable to repair
Bought Drive Genius and this say unable to fix and reports
error: invalid HFS resourse fork clump size in volume header (0)
HELP, what do I need to do and does anybody know what the problem is, come to to that what should I do.
Have just bought a 160GB D2 extreme hard drive firewire extreme drive as I think this might be very handy here. Assume that back up every thing is going to be essential
Thanks in advance of possible solutions
David

This is a difficult error to repair and neither Disk Utility nor fsck may be able to repair it. In which case you would need to try Disk Warrior which may have success depending upon the extent of the problem.
Boot into single-user mode and run the command, fsck -fy, at least four consecutive times but not more than seven. If fsck finally returns with a drive OK message, then it has successfully repaired the problem. If it does not succeed, then either use Disk Warrior or reformat the drive.

Disk Utility Drive report anomaly

Similar Messages

Maybe you are looking for