Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

CoreStorageGroup::completeIORequest - error 0xe00002ca

I've just had a couple of frustrating days tackling some annoying symptoms so I thought I'd provide a fix here for anyone else Googling the same error messages.


I'm on OS X Lion 10.7.2, using Filevault 2 on a 2011 17" Macbook Pro (8GB RAM with the stock 750GB Toshiba MK7559GSXF drive).


I upgraded from Snow Leopard to Lion on my old 15" 2008 MBP and then recently migrated to the 2011 MBP using Time Machine (i.e. there was several years worth of junk lying around pre-Lion and pre-2011 MBP). OS X is up to date, even the new EFI update this week.


The symptoms were:


1) Beachball every few minutes - all applications would stop and hang for between 10 and 20 seconds. Some applications seemed more prone to triggering the problem but I think it was coincidence. The mouse cursor moved but everything else stopped.


2) The following errors appeared in the kernel log and console after the beachball event:


kernel: CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (EE74B25C-0D2C-49B5-BF7D-EFF4D0D4EA18), pv F035EDD4-32D0-4718-B83B-2D61C774E567, near LV byte offset = 320161787904.


kernel: disk1: I/O error.


Note that the CoreStorageGroup error contains a drive label, after a while I realised that my disk wasn't even called 'Macintosh HD' so an unknown application was trying to access an unknown file on a drive that didn't exist. I checked my drive ID using Macpilot and it wasn't the same as the one in the error (EE74B25C etc).


3) There were no other error messages around these messages that pointed to a specific application.


4) All disk checks reported no problems at all. Disk Utility (both from within my user account and from the Lion install disk) and fsck from single user mode were happy.


I was bracing myself for a reinstall but then I worked through some tidying up and one of these fixed the problem:


1) Went through ~/Library/Preferences and deleted some files and folders with corrupt names. I also deleted some old .plist files while I was there.


2) I thought Spotlight might be a problem (maybe an old index entry expects to see a file on 'Macintosh HD' when my drive is really called something else) so I ran 'sudo mdutil -E /' to erase and rebuild the Spotlight index from scratch. That took about 45 minutes.


3) Zapped the PRAM (Command-Option-P-R quickly after power-on).


4) Found a corrupt .m4b audiobook in my iTunes library. I stumbled across this really, I noticed that the errors were more frequent when I was listening to the audiobook. It was corrupt in some way because Finder couldn't work out what kind of file it was. I thought this might also cause problems with Spotlight so I deleted the corrupt .m4b file.


5) Used Macpilot to clear Recent Files List, Clear User Cache, rebuild Launch Services, rebuild Help Viewer Database and run the daily/weekly/monthly cron jobs.


I'm annoyed that I can't tell you which of these actually solved the problem. I'm 90% certain it was a combination of deleting the corrupt .m4b file and recreating the Spotlight index. The .plist files and PRAM zapping might have just made me feel better.


I hope this helps someone. If it does, just reply to this thread please with the actual solution :-)


Regards.

MacBook Pro, Mac OS X (10.7.2)

Posted on Oct 28, 2011 3:37 PM

Reply
18 replies

May 26, 2013 1:08 AM in response to Compact

I'm seeing something very similar, though in my case my HDD is still called "Macintosh HD" so hard to tell if that aspect is the same. Is there a way to get the UUIDs for a FileVault drive? hdiutil and Disk Utility only seem to show me non-FV drive UUIDs...


Interestingly I'm noticing the errors seem to be happening for me in small batches, separated by almost exactly an hour each time.


Today's errors, for example:


26/05/13 11:27:36.000 AM kernel[0]: disk1: I/O error.

26/05/13 11:27:49.000 AM kernel[0]: disk1: I/O error.

26/05/13 11:28:57.000 AM kernel[0]: disk1: I/O error.

26/05/13 11:29:11.000 AM kernel[0]: disk1: I/O error.

26/05/13 11:29:55.000 AM kernel[0]: disk1: I/O error.

26/05/13 11:30:09.000 AM kernel[0]: disk1: I/O error.

26/05/13 11:30:32.000 AM kernel[0]: disk1: I/O error.

26/05/13 11:30:47.000 AM kernel[0]: disk1: I/O error.

26/05/13 12:27:57.000 PM kernel[0]: disk1: I/O error.

26/05/13 12:28:11.000 PM kernel[0]: disk1: I/O error.

26/05/13 12:28:29.000 PM kernel[0]: disk1: I/O error.

26/05/13 12:28:43.000 PM kernel[0]: disk1: I/O error.

26/05/13 1:14:46.000 PM kernel[0]: disk1: I/O error.

26/05/13 1:30:23.000 PM kernel[0]: disk1: I/O error.

26/05/13 1:30:37.000 PM kernel[0]: disk1: I/O error.

26/05/13 1:31:31.000 PM kernel[0]: disk1: I/O error.

26/05/13 1:31:45.000 PM kernel[0]: disk1: I/O error.

26/05/13 1:32:51.000 PM kernel[0]: disk1: I/O error.

26/05/13 1:33:05.000 PM kernel[0]: disk1: I/O error.

26/05/13 1:33:23.000 PM kernel[0]: disk1: I/O error.

26/05/13 1:33:37.000 PM kernel[0]: disk1: I/O error.

26/05/13 2:32:49.000 PM kernel[0]: disk1: I/O error.

26/05/13 2:33:03.000 PM kernel[0]: disk1: I/O error.

26/05/13 2:33:21.000 PM kernel[0]: disk1: I/O error.

26/05/13 2:33:35.000 PM kernel[0]: disk1: I/O error.

26/05/13 3:33:03.000 PM kernel[0]: disk1: I/O error.

26/05/13 3:33:17.000 PM kernel[0]: disk1: I/O error.

26/05/13 3:33:37.000 PM kernel[0]: disk1: I/O error.

26/05/13 3:33:51.000 PM kernel[0]: disk1: I/O error.

26/05/13 4:33:03.000 PM kernel[0]: disk1: I/O error.

26/05/13 4:33:17.000 PM kernel[0]: disk1: I/O error.

26/05/13 4:33:40.000 PM kernel[0]: disk1: I/O error.

26/05/13 4:33:55.000 PM kernel[0]: disk1: I/O error.


My immediate thought is that it's something to do with Time Machine, except my TM backups were at 12:25pm 1:54pm 1:58pm and 5:29pm (odd timings due to cancelling them when I was copying some large files).


So I'm not sure what else would run about once an hour, on the half hour... give or take (except one at 1:14pm).

Edit: Just checked my boot times today:

26/05/13 11:24:45.000 AM bootlog[0]: BOOT_TIME 1369531485 0

26/05/13 1:20:32.336 PM shutdown[1942]: SHUTDOWN_TIME: 1369538432 335485

26/05/13 1:27:43.000 PM bootlog[0]: BOOT_TIME 1369538863 0

So the hourly event seems perhaps related to boot time, and preparing to shutdown may have had something to do with the 1:14pm event.


I'm hoping to test Compact's ideas one at a time, and see if any one in particular seems to fix it... I ran the mdutil -E / command to reinitialise Spotlight at 5:20pm and didn't get the error at 5:33pm so that's inspiring a little hope... but without knowing how to definitely cause/repeat the error I'm not sure when I'll really know...


Edit: hourly trigger based on boot time theory

May 26, 2013 1:21 AM in response to drfrogsplat

D'oh.


26/05/13 6:12:01.000 PM kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (452FEE91-1605-4A66-8A43-C43ED238883D), pv 93A3E6E8-939C-401F-9D89-B599A98CF297, near LV byte offset = 918551023616.

26/05/13 6:12:01.000 PM kernel[0]: disk1: I/O error.


Happened again, not at the usual hourly time, but a few minutes before Spotlight finished indexing (it ran from 5:20pm to 6:20pm). Also just the one error this time.

May 26, 2013 2:55 AM in response to drfrogsplat

Hi, I'm the original poster. I haven't had the problem since I last fixed it back when I posted.


I seem to remember that I tracked the problem down to a corrupt 'iPod Photo Cache' folder. I think the mysterious 'Macintosh HD' disk showing up in the logs is actually the disk label of the internal drive in my Apple TV v1. I sync my iPhoto library to the ATV1 via iTunes.


If you have a similar setup, try deleting the 'iPod Photo Cache' folder that is inside the 'iPhoto Library' package in your Pictures folder. The cache folder will get recreated next time you sync. Be warned though, the next time you sync your ATV1 iTunes will resync every photo all over again.


After doing this it might be worth recreating the Spotlight index as well with 'mdutil -E /' just in case this is a combination of a corrupt file and a corrupt Spotlight entry.


If it helps, I'm on OSX 10.8.3 with iPhoto 11 (v9.4.3). I haven't had the problem in months. I sympathise, this one drove me nuts!


Regards.

Mar 7, 2014 10:18 PM in response to Compact

I can confirm that on my late 2012 iMac error 0xe00002ca, often followed by a disk I/O error was being caused by bad sectors on my hard disk.


My hard disk has been replaced and so far, two weeks later, I've not had the error problem again.


My local Apple repair centre took less than 90 minutes to find the bad sectors and confirm the disk needed to be replaced.


I hope this helps.

Jul 9, 2014 9:21 PM in response to Compact

Last night my iMac 27" (Late 2012) when crazy.

The Desktop kept rebuilding (which took about 10 to 30 minutes) every time I restarted.

When I finally got in the system slowly started to fall apart.

Got a bunch of those CoreStorageGroup::completeIORequest - error 0xe00002ca errors in the console log.

After a long time on with Apple Support chat, it seems a bit better after ditching my Preference files and reloading MaxOSX, but as soon as I started Messages, it went into slow motion with lots of multi-colored pinwheels.

Finally ran a Time Machine (about 5 hours) and checked the log.

One file /Users/mystuff/Library/Messages/chat.db-wal didn't copy.

I moved Messages and copied in another Messages from another account and chown the directory to match the old.

Now, no more problems, except Time Machine can't backup the renamed Messages directory

Jul 9, 2014 10:03 PM in response to BlizzardEvil

Hi, I'm glad you have made progress towards fixing your iMac, but I'd suggest that what you have done might only be temporary.


If the only bad sector on your drive is now under the renamed file you will probably be fine but if there are others you will not know about them until you write to and then and read from them at some point in the future.


I had a number of iTunes tracks that could not be played and caused the error but after each rebuild they were ok as it depended on whether the bad sectors of the disc had been written to or not - after each rebuild it was different files that caused the problem and it some cases is was nearly two weeks after a rebuild before the problem recurred.

Nov 1, 2014 8:28 AM in response to Compact

After a couple of hours investigating this I found the solution.


My MacMini was repeatedly hanging every 20 seconds or so. I checked the system log and could see a log similar to that posted above:


kernel: CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (EE74B25C-0D2C-49B5-BF7D-EFF4D0D4EA18), pv F035EDD4-32D0-4718-B83B-2D61C774E567, near LV byte offset = 320161787904.


I knew there was nothing wrong with the drive itself — passed all test I had performed on it with numerous tools. It would seem this is happening when FileFault is enabled OR when a drive has encryption enabled, in Yosemite.


In my case the problem was occurring on a drive I had enabled encryption on several days earlier after installing a fresh copy of Yosemite. I'd done this by right-clicking on the drive and choosing 'Encrypt'. After disabling this (Right-click and choose 'Decrypt'), the error stopped and my MacMini stopped hanging.


If you're experiencing this I'd recommend decrypting the drive or disabling FileValut. I suspect there's a bug with Yosemite causing this which hopefully will be fixed soon.

Jan 4, 2015 3:16 PM in response to Compact

Can anyone help fix this error message please?

CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (228AFEBF-5471-47C9-B544-988C03F9042F), pv B157F659-AF7F-4D1A-AB42-5590A33872AC, near LV byte offset = 129923317768

disk1: I/O error .

CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (228AFEBF-5471-47C9-B544-988C03F9042F), pv B157F6

CoreStorageGroup::completeIORequest - error 0xe00002ca

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.