I have problems with Disk1: I/O error, and com.apple.xpc...Can anyone help me plz?

Question

Level 1

8 points

I have problems with Disk1: I/O error, and com.apple.xpc...Can anyone help me plz?

Hi,

Problem: when I put my computer to sleep, upon waking it, there is a noticeable lag in performance. Internet is slow to reconnect, and GUI is unresponsive. This happens for around 10-15 seconds, and then things come back to life.

What I tried:

I opened console, and I copied the report. I found a few warnings, of which, I post a few (out of order).

host kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (4F6A789B-E1E1-458F-908A-844CDFA246CB), pv 31458C06-C725-4647-A817-A8C8461D59A2, near LV byte offset = 242813976576.

lhost kernel[0]: disk1: I/O error.

lhost kernel[0]: Sandbox: launchd(1) System Policy: deny(1) file-write-flags /private/var/run/dyld_shared_cache_x86_64

lhost kernel[0]: Sandbox: launchd(1) System Policy: deny(1) file-write-unlink /private/var/run/dyld_shared_cache_x86_64

lhost com.apple.xpc.launchd[1] (com.apple.backupd.status.xpc): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.

lhost com.apple.xpc.launchd[1] (com.apple.cmio.AVCAssistant): ThrottleInterval set to zero. You're not that important. Ignoring.

com.apple.xpc.launchd[1] (com.apple.trustd.agent): The ServiceIPC key is no longer respected. Please remove it.

lhost com.apple.xpc.launchd[1] (com.apple.bsd.dirhelper): The TimeOut key is no longer respected. It never did anything anyway.

com.apple.xpc.launchd[1] (com.apple.ZoomWindow.running): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.

WindowServer[175]: Found 13 modes for display 0x00000000 [13, 0]

I also restarted in safe mode. The problem persists in the log.

I created a copy of the log open restarting computer in regular boot mode, and in safe boot mode. Then, I created three text files containing - log messages only in regular boot mode, log messages in safe boot mode, and log messages in BOTH.

Log Messages that appear only in regular boot

https://www.dropbox.com/s/up6nkk95768xcrb/onlyinnotnsafe.txt?dl=0

Log Messages that appear only in safe boot

https://www.dropbox.com/s/80w2od220asx7e9/onlyinsafe.txt?dl=0

Log Messages that appear in both SAFE and Regular boot

https://www.dropbox.com/s/zoifq5r4inihjaz/overlap.txt?dl=0

Can anyone help me? Should I be thinking about buying a new HD?

Also noticed - when I have headphones or anything plugged into the phone jacks, iTunes spontaneously opens. Also, in the log messages

Thanks!!

MacBook Pro (13-inch Early 2011), OS X El Capitan (10.11.3)

Posted on Jul 20, 2016 1:11 PM

Reply

Answer 1

Jul 20, 2016 1:15 PM in response to sadsdnfkas

Run Disk Utility. It's located in /Applications/Utiliites

With Disk Utility open select the startup disk on the left then click the First Aid tab then click: Run

Using Disk Utility to verify or repair disks - Apple Support

Reply

Answer 2

sadsdnfkas Author

Level 1

8 points

Jul 20, 2016 1:16 PM in response to Carolyn Samit

I ran it in both safe mode, and in regular boot mode. It didn't help. I still receive the same log messages, and I still receive the problem upon waking from sleep.

Reply

Answer 3

sadsdnfkas Author

Level 1

8 points

Jul 20, 2016 1:23 PM in response to sadsdnfkas

After running Disk Utilty in Safe Mode, and in Regular Boot Mode

Jul 20 21:01:38 kernel[0]: disk1: I/O error.

Jul 20 21:01:38 WindowServer[161]: Set a breakpoint at CGSLogError to catch errors as they are logged.

Reply

Answer 4

sadsdnfkas Author

Level 1

8 points

Jul 20, 2016 5:58 PM in response to Carolyn Samit

I also tried to run the fcsk from Single User mode. Here's the output organized alphabetically and duplicates removed. Still getting i/o errors.

https://www.dropbox.com/s/fmqndq8ijook5p0/after_SUmodefsck.txt?dl=0

Reply

Answer 5

Jul 20, 2016 11:26 PM in response to sadsdnfkas

I/O Error is not a vague generic error. It is a very specific problem.

When trying to read some data off your Drive, even after thousands of tries using the error-correction Hardware built into the drive, the data could not be read. Your disk has a Bad Block than cannot be worked around.

The fastest way to make progress is to obtain a new drive for your Mac, an external enclosure or adapter to hold it externally, and install MacOS on it from scratch (not from the bad copy on the damaged drive). Then you will have the full capabilities of MacOS available, and can also use additional Utilities to help restore or recover your data. If you have a recent Trusted Backup, you can restore your Applications and User files to the new drive.

The alternative is to initialize the drive, destroying everything on it, and write the drive with Zeroes. At best, this takes all afternoon to overnight, and using Recovery mode to do this means you computer is tied up that entire time and can do nothing else. At the end of the process, if it passes, you have a blank drive with 100 percent good blocks, but no data. If it gets "Initialization Failed!" your drive has become a doorstop, and you still need to obtain a new drive, and anything that might have been salvageable on the old drive has been completely erased.

Reply

Answer 6

sadsdnfkas Author

Level 1

8 points

Jul 20, 2016 11:26 PM in response to Grant Bennet-Alder

Grant, great answer, thanks for the help. quick question. when you say, "install MacOS on it from scratch (not from the bad copy on the damaged drive)", what do you mean? I have already - last night - downloaded from the App Store an installer (7gb) of Osx el captain. after download, I created a bootable USB with it - following instructions here Create a bootable installer for OS X - Apple Support

from what you said, it sounds like my original plan won't work - go buy a new hd, physically install it, and then run the bootable usb on the new hd.

Reply

Answer 7

Jul 21, 2016 8:00 AM in response to sadsdnfkas

A disk that throws I/O Error has a Bad block. If you get extremely lucky, a re-install on the same drive MAY proceed without error, as the drive will attempt to re-write the bad block. If not successful, the controller may substitute a spare block when new data are supplied for that block number. But you will not know whether more bad blocks are lingering (waiting to blow up in your face) without at least reading every block to check for Bad Blocks.

Sometimes recent MacBooks have experienced additional problems which led to the drive failure, such as problems with the SATA cable inside the chassis. This could end up anywhere from 'not an issue for you' to 'a complete show-stopper'. That is why I generally advise doing this with another drive in an external enclosure (your Mac can install and boot from almost any drive).

In this way, you do not disturb the internal drive, and separate its replacement from any potential issues of installation. It is easier to chase one problem at a time.

Having a USB-stick Installer on hand will make the whole process go fairly quickly and painlessly. If you also have a Trusted Backup, you can use whatever technique seems the most expedient technique, knowing that any files that go missing can quickly be replaced by Backup copies.

Reply

Answer 8

sadsdnfkas Author

Level 1

8 points

Jul 21, 2016 10:26 AM in response to Grant Bennet-Alder

Interestingly, I restarted in Recovery Mode, and I reinstalled OS X El Captain from the on-screen option to download a new copy. It took about 1 hour to reinstall, and upon waking up from a sleep, I no longer notice the long lag. Also, I looked at the console log, and I have no Disk1: I/O Error messages. In fact, the logs are much shorter now. Could it have been a software issue? I don't want to upgrade to the SSD and spend 150, if I don't need to.

Reply

Answer 9

Jul 21, 2016 5:43 PM in response to sadsdnfkas

The console log will be rolled over (copied into a numbered file with otherwise the same name) when you re-install, since old console messages are not pertinent to the new Install.

Perhaps you got lucky and the drive came clean on a re-write of the Bad Block. It sometimes happens that way.

Reply