Mac Boot Disk I O Error
Contents |
can not post a blank message. Please type your message and try again. RoadRunn3r Level 1 (0 points) Q: Can you fix disk0s2: I/O error errors on your HD? I recently mac disk1 i/o error had problems with my IMac starting up after numerous safeboots and reboots
Disk0s2 I/o Error Mac
I finally got it working again but I was looking at my kernal log in Console and kept seeing how to fix disk0s2 i o error disk0s2:I/O error is there a way to fix this or does my hardrive need to be replaced? iMac, Mac OS X (10.7.3) Posted on Feb 12, 2012 9:04 AM I
Imac I/o Error
have this question too by rkaufmann87,Solvedanswer rkaufmann87 Level 9 (58,949 points) Photos for Mac A: RoadRunn3r wrote:Now I should hit Command+R on bootup or after?When you hear the startup tone. Posted on Feb 12, 2012 10:03 AM See the answer in context Close Q: Can you fix disk0s2: I/O error errors on your HD? All replies Helpful answers by babowa,★Helpful babowa disk io error mac Feb 12, 2012 9:15 AM in response to RoadRunn3r Level 7 (32,295 points) iPad Feb 12, 2012 9:15 AM in response to RoadRunn3r Don't know if your Mac came with Lion preinstalled or you upgraded, so try either of these two:boot up with your original install disk (while holding C key), go to Utilities, and run repair disk in Disk Utility.and/orHit Command + R keys and use Lion recovery partition > Disk Utility > repair disk.If Disk Utility cannot repair the disk, you can try something "stronger" such as Disk Warrior, but there is no guarantee. Your disk may be on the way out.Important: before you attempt anything: make sure you have a backup!!!!And, here is something I found googling:http://hintsforums.macworld.com/showthread.php?t=134145 Helpful (1) Reply options Link to this post by RoadRunn3r,★Helpful RoadRunn3r Feb 12, 2012 10:01 AM in response to babowa Level 1 (0 points) Feb 12, 2012 10:01 AM in response to babowa Now I should hit Command+R on bootup or after? Helpful (1) Reply options Link to this post by rkaufmann87,Solvedanswer rkaufmann87 Feb 12, 2012 10:03 AM in response to Road
Miniguide to fixing Volume-Filesystem errors Apr 29, '11 07:30:00AM • Contributed by: santa97298 There are many drive/filesystem errors that can occur on a Mac. Here are some common symptoms that are indicative of some of them:
Diskos2 Io Error Mac
Not able to boot the system: You tried to boot. Apple logo appeared, and
Error 0xe00002ca
wheel spun for about 15-20 seconds, then machine turned off. This repeated every time you tried to boot the system. (REASON: disk0s2 i/o error invalid node structure The system does not find your HD and thus the OS to boot). Everything seems to work fine till your system hangs briefly and in an unpredictable way. You wait for a while, and the https://discussions.apple.com/thread/3730727?tstart=0 system magically comes back to normal. But after another while, the same thing re-occurs! (This cycle repeats in the current session). You can do these simple things to check for other possible causes: Run Activity Monitor to see that this is NOT due to temporarily high CPU and/or Memory usage. Check the system log using Console.app or running tail -f /var/log/system.log in Terminal. If your system is having some I/O error http://hints.macworld.com/article.php?story=20110216112523818 then it is sure that there is an HD failure issue. I don't claim to be an expert on this subject matter, just an (over)enthusiast Mac user. This guide is purely based on my personal experience and is bound to contain errors. So, USE IT AT YOUR OWN RISK! [crarko adds: Consider this hint to also serve as a reminder to check your backups...]Possible problems: Your HD Volume/FileSystem is corrupted Verification: Use Disk Utility and run "verify" to check it. 2. Your HD is dying. Verification: Use Disk Utility and see the SMART status of your HD, although this isn't always reliable. Before making any repair of the disk, make sure that you have the latest backups. Repair might let loose the volume/filesystem info all together and then there will be no other choice than to recover the data by some data rescue s/w like Data Rescue! If you don't have a current backup, you can try booting in Single-User mode by holding Command+S on startup. Then try doing a manual backup using commandline tools like cp or ditto. Note: The disk usually gets mounted in read-only. This could be good to get a manual backup by cp. But if everything else fails and you want to remove the important/perso
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads http://superuser.com/questions/335140/boot-problems-mac-os-x-not-booting with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a http://balloflightning.com/2010/12/io-error-os-x-hard-drive-failing/ question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Boot problems - Mac OS X not booting up vote 3 down vote favorite 1 I am having trouble with my Macbook Pro (late 2008, o error OS X 10.5) at boot. Here is an outline of my problems and attempted solutions: As the computer was going to sleep it got stuck such that when I tried waking it up, I got a black screen with the mouse cursor. I tried opening and closing the lid of the MBP to get it to sleep but that did not change the state. I did a hard shutdown and then tried flashing the p-RAM. I booted into verbose safe mode (shift-cmd-v) and after i o error about 45 minutes I am stuck with repeating messages that look like this: - disk0s2: I/O error. HFS resolvelink: can't find iNode79913 disk0s2: I/O error. HFS resolvelink: can't find iNode80152 This error message is mixed in with other more typical boot messages: Auth result for :
Colin My Macbook (late 2008 Unibody) turned two years old a few days before Christmas. The day after it's birthday (the only reason I know this is because I was checking where it fell in terms of warranty, but AppleCare is only one year, not two from purchase date so this was pretty irrelevant anyways) I started to suffer from a myriad of issues during use. Beachballing. Bouncing programs in the dock. Random freezes in Firefox when browsing. Connection dropouts. The works. I initially thought this was the work of an outdated program failing to play nice with the newest version of Snow Leopard (10.6.5) which I had installed days before. I began turning off plugins in Firefox and ditching programs from the startup menu to attempt to cure whatever sickness had taken over my laptop. Every reboot cycle gave me the same problem- the computer would run for about 30 seconds, but then any use and it started beachballing. Finally, it just didn't reboot. The computer hung at the grey screen with the Apple logo and the spinning ball. No peripherals (external hard drive, USB mouse, etc.) were attached so that was immediately ruled out. To attempt to diagnose the problem, I attempted to boot into safe mode. Not happening. Tried resetting the PRAM and NVRAM. Nada. Finally, the next series of steps allowed me to salvage my hard drive and let my Macbook live to see another day (minus a $700 data recovery charge). Boot into single-user mode (sometimes called verbose mode) (hold down Control-V as soon as the Mac chime sounds after pressing the power button). You should now be in an environment that looks like this: At the command line type: /sbin/fsck -fy and press Return. You will receive messages about the disks use and fragmentation as fsck will now go through five phases of disk utility. If you get: disk0s3: I/O Error then you have a problem with bad sectors on the hard drive. Eventually, fsck will probably tell you: ***** FILE SYSTEM WAS MODIFIED ***** Repeat the fsck process above. Keep repeating the above process until ***** FILE SYSTEM WAS MODIFIED ***** does not appear. Even after this message disappears, repeat one more time. If this message doesn't disappear, and you continue to get disk0s3