Jump to content

New guy with common Yosemite problems


bigmacthecat
 Share

4 posts in this topic

Recommended Posts

Hail comrades,

I'm doing a dual-boot (hoping for a triple with OS X) right now so I'm avoiding a format to my SSD. To be honest, I'd rather die than format it at this point. So I've created a Yosemite installer on a VM and also on a real Mac and both manage to get to the installer, but it always fails with a "can't verify" problem. I've read online that some people have fixed it using the date command in terminal but that hasn't worked for me.

Here's a chunk of the final log file where things start going sour:


Jul 23 01:45:00 iMac.local InstallAssistant[499]: GetDYLDEntryPointWithImage(/System/Library/PrivateFrameworks/CacheDelete.framework/CacheDelete,CacheDeleteCopyPurgeableSpaceWithInfo) failed.
Jul 23 01:45:00 iMac.local InstallAssistant[499]: Could not load Software Update catalog: Error Domain=NSURLErrorDomain Code=-1009 "The Internet connection appears to be offline." UserInfo=0x7f91c44a18c0 {NSUnderlyingError=0x7f91c164e130 "The Internet connection appears to be offline.", NSErrorFailingURLStringKey=https://swscan.apple.com/content/catalogs/others/index-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog, NSErrorFailingURLKey=https://swscan.apple.com/content/catalogs/others/index-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog, _kCFStreamErrorDomainKey=12, _kCFStreamErrorCodeKey=8, NSLocalizedDescription=The Internet connection appears to be offline.}
Jul 23 01:45:00 iMac.local InstallAssistant[499]: Could not fetch SWU catalog to create SWU product
Jul 23 01:45:14 iMac.local InstallAssistant[499]: Created IATool object:c45df5c0
Jul 23 01:45:15 iMac.local InstallAssistant[499]: No available package ref for compatibility update. Ignoring.
Jul 23 01:45:23 iMac.local InstallAssistant[499]: Preventing machine sleep.
Jul 23 01:45:23 iMac.local InstallAssistant[499]: Using product IA_PKSecureNetEnabledProduct <file:///Volumes/Yosemite/OS%20X%20Install%20Data/> at distance 5
Jul 23 01:45:23 iMac.local InstallAssistant[499]: Using existing boot files dir at /Volumes/Image Volume/.IABootFiles
Jul 23 01:45:23 iMac.local InstallAssistant[499]: Using mutable product path: /Volumes/Yosemite/OS X Install Data
Jul 23 01:45:23 iMac.local InstallAssistant[499]: Using boot files path: /Volumes/Image Volume/.IABootFiles
Jul 23 01:45:23 iMac.local InstallAssistant[499]: No available package ref for compatibility update. Ignoring.
Jul 23 01:45:23 iMac.local InstallAssistant[499]: No available package ref for compatibility update. Ignoring.
Jul 23 01:45:23 iMac.local InstallAssistant[499]: No available package ref for compatibility update. Ignoring.
Jul 23 01:45:23 iMac.local InstallAssistant[499]: Retrieving 0 packages (0.000 GB)
Jul 23 01:45:23 iMac.local InstallAssistant[499]: Verifying InstallMacOSX.pkg/InstallESD.dmg
Jul 23 02:03:24 iMac.local InstallAssistant[499]: pkgdmg is not signed or altered.
Jul 23 02:03:24 iMac.local InstallAssistant[499]: pkgdmg validation has failed.
Jul 23 02:03:24 iMac.local InstallAssistant[499]: Stopped operation queue with Error Domain=IAErrorDomain Code=101 "This copy of the Install OS X Yosemite application can't be verified. It may have been corrupted or tampered with during downloading." UserInfo=0x7f91c1750390 {NSLocalizedDescription=This copy of the Install OS X Yosemite application can't be verified. It may have been corrupted or tampered with during downloading.}

I've been kicking the {censored} out of my SSD trying to install this for the past two days. Is it really corrupt after 4 attempts (two VM burns, two real Mac burns with 4 redownloads) or am I missing something? I have a hunch that the FAT32 boot partition shared with Windows 8.1 and Arch Linux has something to do with this... so I did debug mode with disk utility to make sure it was mounted before I did the installation but alas, no luck.

What do you guys think? Also, I didn't know tonymac stole code. That's kind of funny.

Sic Semper Tyrannis

 

Link to comment
Share on other sites

I really don't understand what you are doing. You seem to be using some method that is not a current "standard".

Start out with a USB installation. This doesn't give any information about the hardware you are using except an SSD.

 

What plans do you have for a triple boot? My hack has a 3TB drive and a 500GB SSD. There are two bootable OS's using CoreStorage to build Fusion drives.

 

I formatted the two devices into three partitions and build the Fusion drives within each partition.

 

What is the methodology you are trying to use?

Link to comment
Share on other sites

Heya,

Processor: i5 3570k
Motherboard: Z77E-ITX
GPU: 660 Ti
SSD: Samsung 850 Evo

I was hoping to use Clover EFI boot for a bunch of different operating systems. Right now, I have one for Windows 8.1 and Arch Linux, and now I'm trying to install Yosemite to the same drive. I'm followed instructions on how to create the bootable USB for Yosemite but during the end of installation onto my SSD, it always stalls on 

Verifying InstallMacOSX.pkg/InstallESD.dmg

And then says it cannot verify, and of course "T
his copy of the Install OS X Yosemite application can't be verified. It may have been corrupted or tampered with during downloading."

I had 70GB of free space on the end of my SSD and that's where I was pointing Yosemite. I have a complete backup of my FAT32 boot partition (where the EFI files are stored along with clover .cfg files) so in-case Yosemite overwrote it, that I could re-add all of the information to keep Clover sane and the boot-train going.

 

Am I doing this in a crazy way? I'm avoiding a format at all costs and all guides say to format.

This is just extra information but: Right now I'm re-partitioning my storage/mechanical drive so that I can install Yosemite to that, copy the partition over to my SSD tomorrow, and stealing Yosemite's boot options that will probably be created on that drive to edit and add into my SSD FAT32 boot partition so I can get clover to work. I'm probably doing this a very stupid way, I would appreciate any advice, comrade!

post-1568325-0-22128700-1437720985.gif

Link to comment
Share on other sites

  • 2 weeks later...

Please explain the process you are using to create the USB! Are you on a MAC with Mavericks or better? The error message you reference seem to me that you are using DiskUtility to create the USB?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...