I/O Error

C

cb69235

When I attempt to open Entourage I get a message stating that I should it
cannot access the database and I should rebuild it. When I attempt to do that
I get an I/O error. I have verified the disk using the disk utility and all
seems fine. I tried to create another identity/database and I get an
error-36. Anyone with any ideas where to turn to next. I am using an iMac OS
X?
 
D

Diane Ross

When I attempt to open Entourage I get a message stating that I should it
cannot access the database and I should rebuild it. When I attempt to do that
I get an I/O error. I have verified the disk using the disk utility and all
seems fine. I tried to create another identity/database and I get an
error-36. Anyone with any ideas where to turn to next. I am using an iMac OS
X?

These are hardware errors:

An I/O error almost always means disk damage (hard drive, optical drive,
CD). You probably have a bad disk. Try running Disk Utility / Repair Disk.

Error -36 is often just a read/write error e.g. when copying from a bad DVD.
If you get this error when copying between hard drives you should start to
worry.

How full is your drive? Use the Activity Monitor --> Disk Usage tab at
bottom. You need a min of 10% free.
 
C

cb69235

Thanks Diane, I have already tried to run the disk utility and it says the
disk is fine. I have tried to copy the identity but it does not copy over the
database and that is when i get the error 36. I am at a loss on how to
restore entourage or access my calendar and mail etc..
 
C

cb69235

Actually I looking again when I go into the Disk Utility and highlight the HD
the "repair disk" button is greyed out. When I ran the verification process
it says it is ok.
 
D

Diane Ross

Do you have another volume where you can backup your data? Usually the
hardware errors are pretty much right on. You could then boot off the new
volume and test there.
 
C

cb69235

No I do not have anywhere else to back it up.

Diane Ross said:
Do you have another volume where you can backup your data? Usually the
hardware errors are pretty much right on. You could then boot off the new
volume and test there.
 
Top