Contribute
Register

Dell Inspiron 7437 Yosemite installer glitches (clover)

Status
Not open for further replies.
just tried another usb stick/usb port and setting clover from scratch/Yosemite from scratch. On second reboot, I get a "OSX could not be installed on your computer"... This is so unpredictable. I will re download the installer I guess...
 
Now It's getting worse, I've tried more than 10 times to install (by reformatting the ssd each time), with 2 different usb sticks and 2 different usb ports, and now It won't even complete the first step. I'm getting the following screens:

Photo 1-24-2015, 1 37 24 AM.jpg
Photo 1-24-2015, 1 37 04 AM.jpgPhoto 1-24-2015, 1 37 16 AM.jpg
I tried "verifying" the ssd and it says that the volume couldn't be verified, then I try repairing as suggested and it can't repair... I'm out of ideas now, all this leads to the SSD being bad, but this is unlikely as it is brand new, and in in Windows it gets recognized and other utilities like crystal disk info in windows tell me it is a healthy SSD. I guess this escapes your hands rehabman, as it doesnt have to do with the installation but maybe the partition table is corrupted or something like that (maybe a result of my first installation attempt?). Thanks for your help, and if you have any suggestions, please let me know. I'll try erasing/zeroing the drive or something.
 
shesmovedon said:
...I'll try erasing/zeroing the drive or something.
Click to expand...

Good idea. Start over. You must have corrupted the volume somewhere along the way.

Make sure your SSD firmware is up-to-date. Which SSD is it?
 
RehabMan said:
Good idea. Start over. You must have corrupted the volume somewhere along the way.

Make sure your SSD firmware is up-to-date. Which SSD is it?
Click to expand...

It is a crucial mSATA M550. I will try updating the firmware... Just tried again after letting the garbage collection do its thing the whole night and got "an error occurred while updating system extension information". Will paste the log. Also both the USB sticks I've tried are USB3... I've read it can cause problems, will try getting a 2.0 one.

edit: firmware update and still no luck. I will try creating 2 partitions and see if I can install Windows to it (to discard failed ssd)

edit2: Every attempt fails. To this date, I have updated the FW of the SSD, zeroed the drive (NAND flush), repartitioned, tried installing windows (wouldn't let me install/format the partition I created for it in Mac). This is the last part of the install log:

Code: 
Jan 24 13:47:04 localhost OSInstaller[418]: PackageKit: Extracting file:///System/Installation/Packages/BaseSystemBinaries.pkg (destination=/Volumes/Macintosh/.OSInstallSandboxPath/Root, uid=0)
Jan 24 13:50:22 localhost OSInstaller[418]: PackageKit: Using / as external payload root for package com.apple.pkg.BaseSystemResources
Jan 24 13:50:22 localhost OSInstaller[418]: PackageKit: Extracting file:///System/Installation/Packages/BaseSystemResources.pkg (destination=/Volumes/Macintosh/.OSInstallSandboxPath/Root, uid=0)
Jan 24 13:54:11 localhost OSInstaller[418]: PackageKit: Extracting file:///System/Installation/Packages/Essentials.pkg (destination=/Volumes/Macintosh/.OSInstallSandboxPath/Root, uid=0)
Jan 24 15:14:01 localhost OSInstaller[418]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=110 "An error occurred while extracting files from the package “Essentials.pkg”." UserInfo=0x7f944a427380 {NSUnderlyingError=0x7f945cd529e0 "The operation couldn’t be completed. Input/output error", NSFilePath=/Volumes/Macintosh/.OSInstallSandboxPath/Root, NSURL=Essentials.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution, PKInstallPackageIdentifier=com.apple.pkg.Essentials, NSLocalizedDescription=An error occurred while extracting files from the package “Essentials.pkg”.} {
        NSFilePath = "/Volumes/Macintosh/.OSInstallSandboxPath/Root";
        NSLocalizedDescription = "An error occurred while extracting files from the package \U201cEssentials.pkg\U201d.";
        NSURL = "Essentials.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution";
        NSUnderlyingError = "Error Domain=NSPOSIXErrorDomain Code=5 \"The operation couldn\U2019t be completed. Input/output error\" UserInfo=0x7f945cd79690 {destinationPath=/Volumes/Macintosh/.OSInstallSandboxPath/Root, NSFilePath=/Volumes/Macintosh/.OSInstallSandboxPath/Root//System/Library/PrivateFrameworks/ManagedClient.framework/Versions/Current, offset=14117208, type=BOMCopierFatalFileError, sourcePath=/System/Installation/Packages/Essentials.pkg}";
        PKInstallPackageIdentifier = "com.apple.pkg.Essentials";
    }
Jan 24 15:14:01 localhost OSInstaller[418]: OSIInstallElement <OSIInstallElement: 0x7f945cf8fd80> errored out:Error Domain=PKInstallErrorDomain Code=110 "An error occurred while extracting files from the package “Essentials.pkg”." UserInfo=0x7f944a427380 {NSUnderlyingError=0x7f945cd529e0 "The operation couldn’t be completed. Input/output error", NSFilePath=/Volumes/Macintosh/.OSInstallSandboxPath/Root, NSURL=Essentials.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution, PKInstallPackageIdentifier=com.apple.pkg.Essentials, NSLocalizedDescription=An error occurred while extracting files from the package “Essentials.pkg”.}
Jan 24 15:14:01 localhost OSInstaller[418]: ------- Install Failed -------
Jan 24 15:14:01 localhost OSInstaller[418]: Operation: Install packages failed, Failure Reason: Error Domain=PKInstallErrorDomain Code=110 "An error occurred while extracting files from the package “Essentials.pkg”." UserInfo=0x7f944a427380 {NSUnderlyingError=0x7f945cd529e0 "The operation couldn’t be completed. Input/output error", NSFilePath=/Volumes/Macintosh/.OSInstallSandboxPath/Root, NSURL=Essentials.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution, PKInstallPackageIdentifier=com.apple.pkg.Essentials, NSLocalizedDescription=An error occurred while extracting files from the package “Essentials.pkg”.}
Jan 24 15:14:37 localhost OSInstaller[418]: open on /Volumes/Macintosh/System/Library/LaunchDaemons/com.apple.installer.osmessagetracing.plist: No such file or directory
Jan 24 15:14:37 localhost OSInstaller[418]: Enabling system idle sleep.
Jan 24 15:18:15 localhost OSInstaller[418]: GetDYLDEntryPointWithImage(/System/Library/PrivateFrameworks/CacheDelete.framework/CacheDelete,CacheDeleteCopyPurgeableSpaceWithInfo) failed.
Jan 24 15:18:15 localhost Unknown[404]: 2015-01-24 15:18 OS X Installer[418] (FSEvents.framework) FSEventStreamStart: ERROR: FSEvents_connect() => Unknown service name (1102)
Jan 24 15:18:26 localhost OSInstaller[418]: Connection to sharingd became invalid
Jan 24 15:18:26 localhost OSInstaller[418]: Connection to sharingd became invalid
Jan 24 15:18:27 localhost Unknown[404]: 2015-01-24 15:18:27.128 OS X Installer[418:65852] Communications error: <OS_xpc_error: <error: 0x10bc8cc60> { count = 1, contents =
Jan 24 15:18:27 localhost Unknown[404]:     "XPCErrorDescription" => <string: 0x10bc8cf70> { length = 18, contents = "Connection invalid" }
Jan 24 15:18:27 localhost Unknown[404]: }>
Jan 24 15:18:27 localhost OSInstaller[418]: Folder Manager is being asked to create a folder (docs) while running as uid 0
Jan 24 15:18:28 localhost OSInstaller[418]: CoreServices logging is enabled,
Jan 24 15:18:28 localhost OSInstaller[418]: SFL Favorites initialized.
Jan 24 15:18:34 localhost OSInstaller[418]: Failed to write log file to /private/var/root/Installer Log 01-24-15.txt
Jan 24 15:18:42 localhost Unknown[404]: 2015-01-24 15:18:42.239 OS X Installer[418:65909] Metadata.framework [Error]: couldn't get the client port
Jan 24 15:18:46 localhost Unknown[404]: 2015-01-24 15:18 OS X Installer[418] (FSEvents.framework) FSEventStreamStart: ERROR: FSEvents_connect() => Unknown service name (1102)
Jan 24 15:18:46 localhost OSInstaller[418]: Connection to sharingd became invalid
Jan 24 15:18:46 localhost OSInstaller[418]: Folder Manager is being asked to create a folder (docs) while running as uid 0
Jan 24 15:19:01 localhost OSInstaller[418]: Failed to write log file to /Volumes/Untitled/Installer Log 01-24-15.txt
Jan 24 15:19:05 localhost Unknown[404]: 2015-01-24 15:19:05.040 OS X Installer[418:65830] Metadata.framework [Error]: couldn't get the client port
Jan 24 15:19:08 localhost Unknown[404]: 2015-01-24 15:19 OS X Installer[418] (FSEvents.framework) FSEventStreamStart: ERROR: FSEvents_connect() => Unknown service name (1102)
Jan 24 15:19:08 localhost OSInstaller[418]: Connection to sharingd became invalid
Jan 24 15:19:08 localhost OSInstaller[418]: Folder Manager is being asked to create a folder (docs) while running as uid 0
Jan 24 15:19:22 localhost OSInstaller[418]: Failed to write log file to /Volumes/Image Volume/Installer Log 01-24-15.txt
Jan 24 15:19:24 localhost Unknown[404]: 2015-01-24 15:19:24.689 OS X Installer[418:67440] Metadata.framework [Error]: couldn't get the client port
Jan 24 15:19:27 localhost Unknown[404]: 2015-01-24 15:19 OS X Installer[418] (FSEvents.framework) FSEventStreamStart: ERROR: FSEvents_connect() => Unknown service name (1102)
Jan 24 15:19:27 localhost OSInstaller[418]: Connection to sharingd became invalid
Jan 24 15:19:27 localhost OSInstaller[418]: Folder Manager is being asked to create a folder (docs) while running as uid 0

I'm starting to think the drive was DOA (even though it clearly shows it is healthy on S.M.A.R.T, and I even wrote some files in Windows to see if it worked, and it did...). As a last test, I will rebuild the partition table and attempt to install Windows 8.

Final edit: Just installed Yosemite on the mechanical drive. My ssd is unfortunately DOA and I will proceed to RMA it. IT was really helpful getting your help rehabman, I'm very grateful.
 
After further investigations (I returned the mSATA ssd for a new one, same model), I confirmed that the problem is not the mSATA ssd but the way it gets "read" by the installers... Basically, I think nor Yosemite nor Windows nor Linux can recognize the internal data bus for the mSATA ssd and thus the installations go wrong in unexpected/random parts (I had the yosemite installer fail in some japanese localization files one time, or straight up write/read error at the beginning, same for windows).

Is there a way/kext that can enable the normal functioning of a mSATA drive?
 
shesmovedon said:
After further investigations (I returned the mSATA ssd for a new one, same model), I confirmed that the problem is not the mSATA ssd but the way it gets "read" by the installers... Basically, I think nor Yosemite nor Windows nor Linux can recognize the internal data bus for the mSATA ssd and thus the installations go wrong in unexpected/random parts (I had the yosemite installer fail in some japanese localization files one time, or straight up write/read error at the beginning, same for windows).

Is there a way/kext that can enable the normal functioning of a mSATA drive?
Click to expand...

I don't think there is anything fundamentally wrong/unsupported with mSATA. For example, the-darkvoid is using an mSATA and SATA drive in a software raid0 config (on a Dell, no less).

Perhaps there is some setting in your BIOS or something specific about the mSATA drive you're using?
 
hmm my bios settings are the standard ones for installing Osx

- Disk: AHCI
- Intel Rapid Storage: Disabled
- UEFI Boot: Enabled
- Secure Boot: Disabled
- Legacy Rom: Disabled

At this point I might as well return both drives and get a proper SSD. What a fiasco these mSATA drives.
 
hi, have u made it?
i have the same laptop model as you are. i tried several times but no luck...
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top