I was installing 12c database a few days ago when I came across a strange error. Installation stuck in the “copying files” (about 19% of total progress) with this error:

Funnily enough, the only thing I found in the log was (log is from re-run so hexa string do not match the screenshot, rest of the message is identical):

INFO: invalid entry CRC (expected 0xeaa593bf but got 0xe89a6bf9)
SEVERE: oracle.sysman.oii.oiif.oiifb.OiifbEndIterateException: invalid entry CRC (expected 0xeaa593bf but got 0xe89a6bf9)
	at oracle.sysman.oii.oiic.OiicInstallAPISession.doOperation(OiicInstallAPISession.java:490)
	at oracle.sysman.oii.oiic.OiicAPIInstaller.doOperation(OiicAPIInstaller.java:1010)
	at oracle.sysman.oii.oiic.OiicAPIInstaller.doOperation(OiicAPIInstaller.java:971)
	at oracle.install.driver.oui.OUISetupDriver.setup(OUISetupDriver.java:360)
	at oracle.install.driver.oui.SetupJob.call(SetupJob.java:320)
	at oracle.install.driver.oui.SetupJob.call(SetupJob.java:53)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:682)

INFO: Update the state machine to STATE_READY
INFO: isSuccessfullInstallation: false
INFO: isSuccessfullRemoteInstallation: true
INFO: Adding ExitStatus FAILURE to the exit status set
INFO: Shutting down OUISetupDriver.JobExecutorThread
SEVERE: [FATAL] invalid entry CRC (expected 0xeaa593bf but got 0xe89a6bf9)
   CAUSE: No additional information available.
   ACTION: Refer to the logs or contact Oracle Support Services
   SUMMARY:
       - invalid entry CRC (expected 0xeaa593bf but got 0xe89a6bf9).

This usually happens when you have dying disk or (more probably) borked download archive - and internet is full of those posts stating “download it again”. Yeah, that was not my case, all cksums were matching.

The lead for what is actually happening was in the same log:

INFO: Setting checkpoint object
INFO: config-context initialized
INFO: InstallProgressMonitor: Total Bytes to Install 14,337,868,214
INFO: Synchronizing inventory. Please wait...
INFO: Synchronizing inventory. Please wait...

As I was installing it in virtual lab, I was a bit short on resources (being stingy on system resources is not a good idea at all when it comes to Oracle, BTW) and gave the virtual machine 40GB disk in total. My df -h output before installation:

[root@db1 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/db1-root   37G   23G   13G  37% /
/dev/sda1             477M  128M  320M  29% /boot
... // just entries for tmpfs here (not important for us)

Small disk volume with 13GB of free space where the installer tried to fit about 13GB of files (not mentioning the linking mayhem which would have happened thereafter) and, obviously, did not succeed. Comparing checksums it then probably found an error because of badly copied file and decided to give up whole installation. Certainly my bad not giving it more space, but it still baffles me why the hell there was no easily-comprehensible “you don't have enough space” error (or check).

Needless to say, enlarging the virtual machine HDD did the trick.