-
All replies
-
Helpful answers
-
Sep 15, 2011 8:40 AM in response to dmkellmanby Allan Eckert,Sounds like it is time to call in the heavy guns and take it to Apple for repair.
Allan
-
Mar 18, 2012 3:06 PM in response to dmkellmanby DrLikes,Hey, did you ever get this problem resolved? I am having the EXACT same problem right now. Please reply! Thanks.
-
Mar 18, 2012 3:09 PM in response to DrLikesby Grant Bennet-Alder,I/O Error is usually caused by Bad Blocks. Your drive may be dying.
Sometimes, you can revive a drive and buy yourself some time by Zeroing the drive (this erases all data).
Regardless. a new drive and an external enclosure are in your future.
-
Mar 18, 2012 3:35 PM in response to DrLikesby dmkellman,I ended up resolving it by replacing the hard drive. Not the solution you're looking for, I'm sure. I hope you have a backup.
-
May 10, 2013 7:08 AM in response to dmkellmanby Samurai2k,My iMac starts up slow and often stops working during the day after these errors. I run the Disk Utility frequently and it never finds any errors, but it is only a bandaid. How do I fix the issue ?
My iMac
24-inch, Early 2008
Processor 3.06 GHz Intel Core 2 Duo
Memory 4 GB 800 MHz DDR2 SDRAM
I can not add anymore physical ram
Graphics NVIDIA GeForce 8800 GS 512 MB
Software OS X 10.8.3 (12D78)
-
May 10, 2013 8:53 AM in response to Samurai2kby Grant Bennet-Alder,1) The quick fix is to replace the drive, which is what almost any technician will do because it always works and provides rapid resolution.
2) Once you have some time, you MAY be able to revive the drive by erasing with Security Options, Zero all data (one pass). But this removes all data, and you need somewhere to park an additional Backup, so option 1 has more appeal as the first step.
Disk Utility only checks Directory Integrity, it does not read ANY non-Directory blocks. A more accurate command would be ( Repair Directory) rather than ( Repair Disk). If the Bad Blocks are not in the Directory, Disk Utility will not find them, but SMART Status sometimes does.