Take the 2-minute tour ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

My Mac tends to pause every now then when preforming simple tasks such as right clicking, opening menus and typing (It actually just froze when I started typing this question.).

I've read in a few places that this may be due to bad disk blocks, and that the best way to fix this is to format and overwrite the whole disk with zeroes. Obviously, this takes time and will destroy any data I have on the disk. Is there a way to check for bad blocks without formatting the drive, or even remap the disk to ignore those blocks (ultimately fixing it)?

My Mac is pretty recent (Mac Mini late 2011), so I doubt it has anything to do with low memory or swappage.

share|improve this question
The issue may not be bad blocks. Is everything slow just after booting or it takes time for the lag to appear? –  duci9y Dec 1 '12 at 12:02
It's not really slow, but things hang and I get beach balls all the time. It happens right after booting too. –  ronmrdechai Dec 1 '12 at 12:05
Try everything before you settle on bad blocks, because that is very rare. First step, Repair Permissions in Disk Utility. –  duci9y Dec 1 '12 at 12:07
Note that this can simply be that you have too little RAM and your system swaps. You can see this in Activity Monitor. –  Thorbjørn Ravn Andersen Dec 1 '12 at 13:19
I doubt it's a RAM issue. My Mac is a Mac Mini late 2011, and I have very little going on (Only about 10 apps installed, and a maximum of about 5 running at any given time.). I tried fixing permissions, the freezes still happen. –  ronmrdechai Dec 1 '12 at 13:25
show 8 more comments

8 Answers

I'll answer the "bad blocks" tack and you can ask a follow on question if you still have slowness and you have concluded that it's not simply bad blocks. (Bad blocks is almost never a slow issue - since the system can remap blocks so rapidly, that you'd need rafts and rafts of them to actually impair I/O. If you do have bad blocks, they can corrupt some of the data on the drive and a reinstall not only fixes that, it forces writes to detect more bad blocks - kind of a win/win situation).

You need no extra tools to see the health of your drive.

Open Disk Utility and select the physical drive itself (not the Macintosh HD or whatever the partition/volume is) and select info.

Disk Utility Info

If you record and watch the values under S.M.A.R.T. Status and see how they change over time, you can know pretty much anything that is detectable about storage degradation or partial failure.

share|improve this answer
So you're saying that I should reinstall either way? Also, will restoring from a Time Machine backup restore corrupt system files? (The only thing stopping me from nuking the device is that I have to wait for the backup to finish.) –  ronmrdechai Dec 1 '12 at 15:55
Say you have three files that are corrupt now. A system file, a song and a novel you are writing. Time machine will back up the corrupted versions (but hopefully have older non-corrupted versions) since it depends on the drive to send it the data correctly. The system file gets fixed, since you reinstall the OS from a download - not the backup. The other two corruptions you either revert to an older version or fix and move on. –  bmike Dec 1 '12 at 16:01
As long as you really trust your backup (and restoring it to a new clean system is really the only way to trust it) reinstalls are quite reliable since 10.6 and on. In my experience - the only bad time to erase and install is when you really are on deadline and can't install before going to bed at night and let it restore from the backup while you sleep. –  bmike Dec 1 '12 at 16:02
superuser.com/a/576370/84988 for a method of using OS X with S.M.A.R.T. with external USB and FireWire drives; discussion in MacRumors. –  Graham Perrin Apr 16 '13 at 5:54
so...what if you want to check your drive (all of it) for bad blocks, is there really no way to do that in OS X? –  rogerdpack Dec 10 '13 at 16:28
show 1 more comment

I recommend Disk Warrior or Drive Genius, both of which should offer the option to boot from external media in order to analyze your hard drive.

share|improve this answer
Do these also analyze for bad sectors? –  Greduan Mar 8 '13 at 20:38
I believe they use the term "blocks", but yes they do. Both of them. –  bispymusic Mar 8 '13 at 20:44
OK thanks! I'll check it out. :) –  Greduan Mar 8 '13 at 21:53
DiskWarrior 4.4 can read S.M.A.R.T data, but for this question: I should not rely on the very limited data that is passed to DiskWarrior. DiskWarrior is not designed to scan a disk for defective sectors. –  Graham Perrin Apr 16 '13 at 5:22
add comment

If we separate the essence of the question, from the reasons for asking …

Start Ubuntu and run badblocks

Use an Ubuntu disc that works with your Mac, then run badblocks with appropriate options.

Ubuntu Manpage: badblocks - search a device for bad blocks

… click the heading for the full answer.

Elsewhere in Stack Exchange

How to check whether there is bad sector on a USB harddisk on OS X? (2012-02-27)

  • links to another related question.

More recently, in Ask Different:

Whatever you use

Be aware that relocation (or remapping or sparing, or whatever you call it) may cause dataloss

share|improve this answer
Simply because Drive Genius 3 can show you pretty pictures and "locations" in an image doesn't mean it's sophisticated. It doesn't measure any timing parameters, which means it can't detect weak sectors and it will likely identify I/O errors caused by other things, such as faulty cables as bad sectors as well...in other words it's providing you with misinformation. –  BSD Guy Apr 16 '13 at 9:30
@BSDGuy can badblocks run without the limitations that you associate with DriveGenius 3? Consider adding some detail to your answer(s) – thanks. –  Graham Perrin Apr 19 '13 at 19:45
add comment

Before you start doing anything like this, open Console.app (I believe the English name is) which allows you to see if any I/O errors have been logged. If you see I/O errors you should immediately prepare to migrate to a new drive, as it means that your drive has run out of spare sectors for this purpose and it will only get worse. A typical way to do this is to use Time Machine to create a backup, and then change the drive and then reinstall OS X anew, and tell the installer to reestablish from Time Machine.

Personally I used a simple shell script that went through all files on disk and used dd to read them (and print any read errors while continuing). I then renamed the files containing the bad blocks so I would not use them again.

share|improve this answer
Wouldn't that take forever though? I'll try running something like this overnight. for F in "$(find /)"; do dd if=$F of=/dev/null; if [ $? -ne 0 ]; then echo "$F"; fi; done should that do it? –  ronmrdechai Dec 1 '12 at 13:38
add comment

Try to use stellar drive defrag

share|improve this answer
I would strongly advise NOT to use third party disk manipulation tools unless to cope in an emergency. You may do more damage than good. –  Thorbjørn Ravn Andersen Dec 1 '12 at 13:19
I will second the idea that defragging is probably not safer than a wipe and a reinstall. Unless there is a lot more information about how this tool really works in practice I'd stick with the provided tools. It could be an awesome tool but I'd want to hear from a few long time users on OS X document how it works. –  bmike Dec 1 '12 at 15:38
add comment

We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.

Disk Warrior is for repairing index files on drives that have corrupted index files. A corrupted index file often makes the drive unusable. Drive Genius can do some index repair but it's best known for defragmentation. Its surface scanning is very basic. An entire list of drive testing tools can be found at the following:


I'm familiar with Scannerz, because I'm cheap! :-)

share|improve this answer
DiskWarrior is not designed to check for bad sectors. Beyond the basics: DriveGenius 3 can perform extended scans (example). –  Graham Perrin Apr 16 '13 at 5:08
Do you recommend Scannerz? If so, please add some technical explanation for the recommendation; and consider a separate answer. (I can't vote up this answer whilst DiskWarrior is amongst the three products.) –  Graham Perrin Apr 19 '13 at 19:38
add comment

Do you recommend Scannerz? If so, please add some technical explanation for the recommendation; and consider a separate answer. (I can't vote up this answer whilst DiskWarrior is amongst the three products.) – Graham Perrin Apr 19 at 19:38

I'm not sure "recommending" products on this forum is really appropriate, since it might be taken as spam. What I will do is tell you my own experience with Scannerz and another "famous" much more expensive tool.

We had several older systems in house, all PPC, all running Leopard that we needed to sell. Several of these items (about 5 if my memory serves me correctly) were showing what I could only call odd behavior. They would periodically give us the spinning beach balls, lock up a little, etc. We ran the "famous" tool on them to do diagnostics, and AHT on at least 3 of them. They all came back with a clean bill of health. I thought, "Well, it must be my imagination." Within a month of selling them, we received notice from each buyer that the units were broken. We gave these things a 90 day warranty so our only option was, at the customers discretion, either refund the money and the shipping costs, or repair the systems at our expense and ship them back.

In each case, it was the exact same problem: the hard drive either failed or was in the process of failing and neither the "famous" tool or AHT picked it up. We had more units to process, and having learned my lesson, this time we ran across some more units with similar problems. This time I was aware it was likely a drive problem, so I opened up /var/log/system.log and used the "tail" command to follow what was going on. I did this while using the "famous" tool. I/O errors would show up and the "famous" tool would not so famously miss them...lots of them.

Scannerz was new on the market and it was cheap, so I figured I might as well give it a shot. Scannerz was picking up every single problem plus others! It was not missing the problems the "famous" tool missed. In addition I found that if a unit had a bad internal drive cable, I could open the unit up, start a Scannerz session, and probe the cable with a non-conductive probe and Scannerz would either start tossing out tons of errors or irregularities.

The only tools I will use are Disk Warrior for fixing drive index problems Disk Utility, for some reason, won't touch, and Scannerz for evaluating drive problems. That's my choice. Those are tools I trust. Period!!

If you need technical details regarding how Scannerz contact the people that make it. They have marketing contacts and support contacts on their web site.

share|improve this answer
Telling people to use google to find something isn't very helpful (and also a trick often used by spammers to circumvent filters). Can you please add a link to the software's website? –  patrix Apr 24 '13 at 3:39
Please: if you can't name a product, can you describe its method of testing? –  Graham Perrin May 5 '13 at 4:25
add comment

"Please: if you can't name a product, can you describe its method of testing?"

I can't blame him for not naming a tool. I have no idea where you live but in the U.S. companies can sue you for criticizing them.

However, based on his experiences with a "famous tool" I would suspect it's initials are TTP.

From what I can tell, that product doesn't seem to do a very thorough job of doing anything. I've read reports that all it was doing was a raw read of a hard drive and flagging I/O errors as sector problems whenever it felt like it. It misses drive problems. I've seen this first hand, and it costs $100.

I've never used Drive Genius so I don't know anything about it. I can, however, speak of both Spinrite and Scannerz.

Spinrite uses what I consider, at least in its re-write mode, a very, very risky procedures. It attempts to read and then re-write a sector to a drive. This is OK if the source of the problems is actually a sector failure, but intermittent cable failures can cause the exact same problem. In other words, if an intermittent cable failure corrupts data transfer between the CPU and hard drive, it could very well end up first reading corrupted data from a hard drive and then re-writing it over good data. The potential for corruption in such a case is high. Spinrite is an ancient product developed for PC's back in the early '80s.

Scannerz actually isn't actually hard drive testing software, it's fault detection software. It monitors for I/O errors and timing irregularities, and it appears to do so based on a statistical model of the drive/system performance. The "rule" with Scannerz is that if a problem is repeatable from scan to scan then the problem is with the media itself, and it will be either a bad sector or a weak sector. If the problem isn't repeatable on a scan, then it's likely another fault such as a bad cable or cracked trace in the logic board. Scannerz has an overwrite mode, but their manuals warn about using it quite heavily, as does the product which will throw out an a warning dialog about using it. Most if not all of the procedures they use for correcting problems are done using standard tools such as Disk Utility. I could teach my dog to do a basic scan on a drive with Scannerz, however to utilize it to its fullest potential requires at least a moderate amount of knowledge as to how a system works.

I have personally witnessed Scannerz picking up bad cables on an external hard hard drive. You can actually fool with a cable during a scan and watch irregularities and errors crop up as the faulty cable is moved around. To the best of my knowledge, no other tool on the market can detect that.

With all that said, regarding other tools, the idea of using an old MS-DOS based tool such as Spinrite or something from a Linux distribution is likely impractical for most Mac users. I would be willing to bet most Mac users aren't even sure what Linux is, and they often likely don't know (or want to know) how to specifically isolate a drive so a product with its origins in MS-DOS can work, and potentially damage their drive. Such tactics may be OK with hard core techies, but they're utterly impractical for most people. I would also add that applications that appear to be doing little more than exec'ing system calls to the command line version of Disk Utility aren't terribly impressive, IMHO.

share|improve this answer
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.