Installation failed

[slvrscoobie]

Oh boy. Well here we go:
Installed the El Capitan beta and let it do its thing.
Now it says its failed: File Verification failed.
Not sure wtf that means but I cant boot into anything else now. Im trying recovery and the verification fails (Continuity tool??)
What should I do? How do i get back or at least, I guess maybe into a command line to restore the continuity tool backups if thats the problem?
please help!

 

[Apple_Robert]

Do you happen to have a Carbon Copy Cloner or TimeMachine backup you can boot from? If so, do that and then check your HD or SSD via Disk Utility. If not, did you check your drive in Disk Utility via the Command+R route? I may be wrong here but, it sounds like you have some disk errors.

Maybe someone with more experience will chime in.

 

[slvrscoobie]

I do but I dont really want to have to do a fresh install and migrate just for that. I know i have the kexts backed up if thats the issue, just need to get to them. I tried Verbose mode and it ended up right back into the ***** installation sequence again. I dont understand why I cant just stop that!

 

[!!!]

I do but I dont really want to have to do a fresh install and migrate just for that. I know i have the kexts backed up if thats the issue, just need to get to them. I tried Verbose mode and it ended up right back into the ***** installation sequence again. I dont understand why I cant just stop that!

Well can you get into the recovery HD?

 

[slvrscoobie]

Not sure what you mean. I just got into single user mode which would have the backups..just not very good with my unix command line tools any more

 

[slvrscoobie]

im in the Single user and there is a 'install OS X El capitan public beta.app' - deleting that wont help right..?

 

[!!!]

im in the Single user and there is a 'install OS X El capitan public beta.app' - deleting that wont help right..?

No. Get into Recovery HD. Single user mode won't help.

 

[slvrscoobie]

I was already in there. I can verify the system, but the repair button is greyed out
Can you give me some advice on what I need to do in Recovery

 

[briankeith513]

Yeah, I'm not getting an error message, and although it redeems, and says its downloading, I see nothing showing that its downloading.

 

[!!!]

Yeah, I'm not getting an error message, and although it redeems, and says its downloading, I see nothing showing that its downloading.

Not related.

I was already in there. I can verify the system, but the repair button is greyed out
Can you give me some advice on what I need to do in Recovery

Does the verification show it is Ok? You should then be able to go and reinstall the beta. Select your drive and reinstall it. It'll download the beta and then it will install it over the failed one. You won't loose any data.

 

[slvrscoobie]

no it says theres a problem and it needs to be repaired (repair greyed out)

Aw man, I was able to use disk utility to get to the directory and see the files i bet are my problem :
IO80211FAMILY.KEXT and IOBLUETOOTHFAMILY.Kext If only I could get finder to move them back..!

 

[slvrscoobie]

ok, tried to repair the disk in CMD+R.
Its saying that it stopped repairing the disk, because it cant repair it. Back up, reformt, and restore ??

WTF is going on here?!

 

[!!!]

ok, tried to repair the disk in CMD+R.
Its saying that it stopped repairing the disk, because it cant repair it. Back up, reformt, and restore ??

WTF is going on here?!

Your disk is failing. Erase and reinstall as new. You won't be able to restore any data unless you know how to in terminal (on recovery HD) or using single user.
Unless you backed up devote you installed the beta (which you should have), then just restore.

 

[slvrscoobie]

I fail to believe my SSD is dying at the same exact time i have a bad install from a beta OSX
Is restoring from this AM going to put everything back - its like 200GB and its a network backup. Im gonna be really pissed if I delete my current install and spend all night putting it back to find out thats its only the OS and I have to reinstall all the apps, and concurrent non-sense on my desktop
i know i know, beta, but honestly, ive been on many betas and never once needed to completely reformat the HDD because of it. Seems like theres a glitch in the install. It hasnt even COPIED anything, its just verifying things, seems like I should be able to kick it out and just go back for F's sake.

BTW :fsck in single user mode says everything looks ok.

 

[!!!]

I fail to believe my SSD is dying at the same exact time i have a bad install from a beta OSX
Is restoring from this AM going to put everything back - its like 200GB and its a network backup. Im gonna be really pissed if I delete my current install and spend all night putting it back to find out thats its only the OS and I have to reinstall all the apps, and concurrent non-sense on my desktop
i know i know, beta, but honestly, ive been on many betas and never once needed to completely reformat the HDD because of it. Seems like theres a glitch in the install. It hasnt even COPIED anything, its just verifying things, seems like I should be able to kick it out and just go back for F's sake.

BTW :fsck in single user mode says everything looks ok.

The install failed because of the bad drive.

 

[slvrscoobie]

Nothing so far has indicated that it's failing. Why now?

 

[!!!]

Nothing so far has indicated that it's failing. Why now?

I don't know. I'm not inside your hard drive deciding when to fail. When you verify, it should show you the different parts it is checking, what is the last thing it checks before it alerts you it failed? Sometimes there is red text explaining he issue.

 

[slvrscoobie]

It said it cannot verify the system check and needs to be repaired. Its a SSD so again, i think its unlikely that it decided to fail right now, where as I feel the 'hacked' bluetooth Kext that I am running is a much more likely cause. Ive removed the offending kext from system/extentions but cant seem to get it to copy the 'directory' for the kext from the location in the /users/kextbackup to system/extention.
"The volume could not be verified completely"
whatever that means.

 

[!!!]

It said it cannot verify the system check and needs to be repaired. Its a SSD so again, i think its unlikely that it decided to fail right now, where as I feel the 'hacked' bluetooth Kext that I am running is a much more likely cause. Ive removed the offending kext from system/extentions but cant seem to get it to copy the 'directory' for the kext from the location in the /users/kextbackup to system/extention.

It's may not be the SSD that's failed but the file system. It may be corrupted.
How are you deleting the kexts? If you remove them, you can restore them by reinstalling from the Recovery HD.

 

[slvrscoobie]

i did it by hand in terminal. very laborious. Ok so your saying the installation could have borked up the file system. That makes a bit more sense. Im doing one more try now that I reinstalled the kexts, if that doesnt work, im going to time machine it. I dont think ill really lose anything because it 'Should' come back in the same exact state I left it basically as of 8am this morning...

 

[slvrscoobie]

aaaaaaaaand time machine it is.... soab!

 

[slvrscoobie]

time machine put about 98% of everything back where it was. Downloaded El Cap again, and installed. I did run a disk permission check and fix, and a file system check before doing it though. Not sure what the problem was. Im going to chalk it up to an upgrade bug. Very glad I had my synology NAS with a current backup though. My latest disk backup was about 2 weeks old.