System Check Exit Code is 0. How do I Resolve this?

Question

Level 1

20 points

System Check Exit Code is 0. How do I Resolve this?

I cloned my 10.9.x main drive to run Mac OS 10.10 installer on the cloned drive.

The drive was blessed and even ran fsck -f in single user mode. But every time I try to install 10.10 It hangs at the last step saying File System Check Exit Code is 0.

I run Disk Utility and it says the boot volume is ok. Then the last line is "File system check exit code is 0"

The data is still on the drive but It will not boot, not can I do a reinstall on this cloned drive.

Can anyone tell me how to resolve this issue?

I need to see what apps will not work in 10.10 before I upgrade my main drive.

Thank you!

iQuack

Mac mini, OS X Mavericks (10.9.5), Dual Core i7

Posted on Oct 26, 2014 6:29 PM

Reply

Answer 1

Kappy

Level 10

362,007 points

Oct 26, 2014 6:50 PM in response to iQuack2

I don't think you understand. The fact that your installation isn't working or has failed is not done in Disk Utility which can only test if the disk is corrupted. It is not. Hence, any install problem you have is due to a failed installation. Nothing to do with Disk Utility. In virtually all programming languages an exit code of 0 means it's OK.

Reply

Answer 2

iQuack2 Author

Level 1

20 points

Oct 28, 2014 9:53 AM in response to iQuack2

So far no go. The error's I had before seem to come from USB/FireWire/eSATA combo cases. I have used three different types for 2.5 inch drives. With and without power supplies. The only 2.5 inch drive that I have been able to Upgrade has been the mini's internal drive. The only other drive I was able to upgrade was a 3.5 inch drive inside an OWC MEPD (Mercury Elite Pro Dual) case. That uses thunderbolt.

I still get the Exit 0 Error followed by an unlock error. Then there is a statement about not being able to upgrade the drive.

This time the OS X install screen says OS X could not be installed on this drive.

Building Boot Caches on boot helper partition failed.

Quit the installer and reboot and try again.

Which ends in the same messages.

Can anyone help resolve this issue.?

If I do a clean install it is fine But it will not let me upgrade the hard drive.

Reply

Answer 3

Kappy

Level 10

362,007 points

Oct 26, 2014 6:37 PM in response to iQuack2

This exit code just means there were no errors. There is nothing to resolve.

Reply

Answer 4

iQuack2 Author

Level 1

20 points

Oct 26, 2014 6:40 PM in response to Kappy

This error code is not Present on the original. And the install FAILS to install the entire 10.10. When I install this on a drive that is not been cloned. It works fine. There is no Exit error Code on those drives.

When it reboots to that drive it keeps trying to install. This needs to be resolved. I have tried to install 22 times on 22 differ configs of cloned hard drives.

10.10 will not install cause it can't Exit or even unmount the drive.

Reply

Answer 5

iQuack2 Author

Level 1

20 points

Oct 26, 2014 7:06 PM in response to Kappy

Maybe you are not understanding me. This shows in error list on the install of 10.10 as well. No the drive is not crupted.

I Use data backup 3 and I Rebless the system and run DiskWarrior on the clone to ensure all is well.

It lists this as an error. And then it tries to unmount the drive it has installed 10.10. It errors out and says I have to reinstall. It won't even reboot

i have to hold the power botton down to get out. once it reboots it tries to reinstall 10.10. so this is an error. It reports it as such.

Reply

Answer 6

Kappy

Level 10

362,007 points

Oct 26, 2014 7:20 PM in response to iQuack2

Sorry, but the installer does not produce such output except, perhaps, in the Console log where it still has the same meaning. I don't have a clue what you are trying to do, but there is no error. The installer has finished properly, but the installation has not. They are not the same. But if you wish to argue about this you're welcome to do so, but I don't see the point. You ask a question; you get an answer; then you argue that the answer is wrong. If you know that already, then why did you bother to ask the question?

Reply

Answer 7

iQuack2 Author

Level 1

20 points

Oct 26, 2014 7:35 PM in response to Kappy

Kappy, I am telling you what I see. I ran applejack on that drive and it said there was no virtual memory file. That was fixed. But still have the error of system check exit code is 0.

I am gonna take a photo of the error on this install to show you. Disk Utility even shows this same error. It is coming up as an error. all I want to know is how do I get past this error so I can I stall 10.10

not trying to get to get smart about it. It is showing as an error. And only on the cloned hard drives. 22 times. Now on 23. It says six mins remaining til it goes to the main install.

Reply

Answer 8

iQuack2 Author

Level 1

20 points

Oct 27, 2014 2:53 AM in response to jaigieese1863

Hello Jaigieese1863,

When I would try this, many times, it would not allow the hard drive to unmount so that repairs could be performed.

I have only been able to install 10.10 on two external drives. One was a clean install, that was install number 5 and 23 was an update to a cloned system drive. Install 24 was a bust. I have an idea of the cause for the failed installs but not the un-mounting issue. I am prepping for install 25. 2 Mins before I launch the installer. :/

Reply

Answer 9

Jan 11, 2017 5:42 PM in response to iQuack2

I Had the same problem too, running and WD 1TB external drive, but if i placed the drive in a HD-Caddy it would preform normally.

Eventually after some logical deduction i switched the usb-3-cable with another usb-3-cable (brand cable unknown),
Loh and behold, no more problems.

so yes, either the casing and/or the cable, or the connection of both with the mac doesn't work properly.

Hope this helps.

Reply

Answer 10

Oct 26, 2014 10:06 PM in response to iQuack2

I had this System check exit code 0 pop up when I ran a "verify disk" in Disk Utility. I booted into the Recovery partition, ran Disk Utility within that and restarted and it fixed the issue.

Reply