invisibleloop

Q: Failed yosemite install due to file permission errors. Now can't exit the installer.

I have tried to install Yosemite on iMac but the install failed due to file permission errors. I can't repair that disk as the option is greyed out. Options I have tried.

 

Safe boot. Loader bar stops at 50% after a few hours and never gets any further.

 

Recover mode: All options to repair are greyed out. Can't even erase the hard drive because it can't unmount the disk. Can't recover a backup from the time machine.

 

Start up manager: Only gives me the option to start using the installer.

 

Reset PRAM: Did this just incase... just get a black screen then goes to recovery tools

 

I also can't change the start up disk to the macintosh HD.

 

So I am now stuck. I can't seem to be able to do anything. If anyone understands my issue then I would love to hear from you.

 

Thanks

 

Andy

iMac (27-inch Mid 2010), null

Posted on Jan 1, 2015 8:14 AM

Close

Q: Failed yosemite install due to file permission errors. Now can't exit the installer.

  • All replies
  • Helpful answers

Page 1 Next
  • by invisibleloop,

    invisibleloop invisibleloop Jan 1, 2015 8:47 AM in response to invisibleloop
    Level 1 (0 points)
    Jan 1, 2015 8:47 AM in response to invisibleloop

    This is the output from diskutil list if that helps:

     

    -bash-3.2# diskutil list

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *1.0 TB     disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:                  Apple_HFS Macintosh HD            999.9 GB   disk0s2

    /dev/disk1

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *1.0 TB     disk1

       1:                        EFI EFI                     209.7 MB   disk1s1

       2:                  Apple_HFS Time Machine Backups    999.9 GB   disk1s2

    /dev/disk2

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:     Apple_partition_scheme                        *5.4 GB     disk2

       1:        Apple_partition_map                         30.7 KB    disk2s1

       2:                  Apple_HFS OS X Install ESD        5.4 GB     disk2s2

    /dev/disk3

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:     Apple_partition_scheme                        *1.3 GB     disk3

       1:        Apple_partition_map                         30.7 KB    disk3s1

       2:                  Apple_HFS OS X Base System        1.3 GB     disk3s2

    /dev/disk4

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *5.2 MB     disk4

    /dev/disk5

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk5

    /dev/disk6

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk6

    /dev/disk7

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk7

    /dev/disk8

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk8

    /dev/disk9

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk9

    /dev/disk10

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *6.3 MB     disk10

    /dev/disk11

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *2.1 MB     disk11

    /dev/disk12

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *1.0 MB     disk12

    /dev/disk13

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk13

    /dev/disk14

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *524.3 KB   disk14

    /dev/disk15

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *1.0 MB     disk15

    /dev/disk16

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            untitled               *6.3 MB     disk16

    -bash-3.2#

  • by david.lski,

    david.lski david.lski Jan 1, 2015 8:58 AM in response to invisibleloop
    Level 1 (85 points)
    Jan 1, 2015 8:58 AM in response to invisibleloop

    If the disk is bad and you can't wipe the disk from Recovery Mode, you'll have to use an external disc like the original install discs with Mac OS X Snow Leopard to wipe the disk before installing Mac OS X Snow Leopard and then upgrade again.

     

    Since that computer is pre-Mid-2011 model, it can't use Internet Recovery otherwise that'd be a viable option. Since you're using Recovery, you can't wipe the disk while you're using the disk.

  • by Topher Kessler,

    Topher Kessler Topher Kessler Jan 1, 2015 11:44 AM in response to invisibleloop
    Level 6 (9,866 points)
    Jan 1, 2015 11:44 AM in response to invisibleloop

    This Terminal output showing multiple devices happens because your hard drive's partition tables are corrupted. Your best bet here will be to wipe your drive and set up the partition tables again from scratch, which can be done by booting your Mac to a volume other than your boot drive, and then using a drive management tool to fix the problem at hand. This can be done by loading Internet Recovery and then using Disk Utility in the following manner (note Internet Recovery downloads the recovery files to boot off of them, so your internal drive is not used):

     

    1. Reboot your Mac and hold Option-Command-R when you hear the boot chimes
    2. Allow the recovery files to download and then boot your Mac.
    3. Open Disk Utility and then select your internal hard drive device (the item listed above any volume names)
    4. Click the Partition tab that appears
    5. Select 1 Partition from the drop-down menu
    6. Click the Options button and ensure GUID is the partition scheme to use
    7. Close and apply the changes (optionally give your new partition a name)
    8. Quit Disk Utility and then proceed with installing OS X

     

    Note that this will install the version of OS X that came with your Mac, and will wipe all data on your drive so hopefully you have a backup. If you do have a backup, then you can use the option to Restore from backup, but if not then proceed with the full clean installation of OS X. At this point you can access the App Store and re-download any OS X upgrades that you have purchased.

     

    This procedure should work, but if not then your drive might be experiencing a deep corruption that Disk Utility cannot manage. If so, then the same Terminal output listing many "/dev/disk#" devices will show up when you the "diskutil list" command. To address this, you will need to perform a deep overwrite of your drive's contents, which can be done in the Terminal using some special commands. First be sure your backup drives and any other drives are fully disconnected from your Mac. Then open the Terminal when booted in Internet Recovery mode and run the following command:

     

    cat /dev/random > /dev/rdisk0
    

     

    Hopefully this will drop the cursor below the entered command and have it just stay there. The longer you have it stay, the longer the system will write to the block device (your drive) starting from the first block. This will wipe through any logic that dictates the drive's structure and have it just appear as blank storage media to your system, ready to be partitioned and formatted for use.

     

    If this still does not work because you get persistent errors that the drive is busy, then you will need to perform this action using another Mac, and attach your current Mac to it in Target Disk mode (where you hold T down at startup to have your Mac's internal drive accessible to another Mac as an external as a FireWire or Thunderbolt device). When in this mode and with another Mac available, you can follow the instructions in that article I linked above, to perform the same actions on the drive and attempt to overwrite it using your second Mac. (disclaimer: I am the author of the linked article, and may receive compensation from it)

     

    If you are successful, then you can return to Disk Utility and follow the above procedure to repartition it and then be able to reinstall OS X.

  • by david.lski,Helpful

    david.lski david.lski Jan 1, 2015 11:58 AM in response to Topher Kessler
    Level 1 (85 points)
    Jan 1, 2015 11:58 AM in response to Topher Kessler

    This is the case if the computer was Mid-2011 or newer. Since this machine is from 2010, the firmware update doesn't include Internet Recovery. See the link that I included with my original post.

     

    In this case, he'll have to boot from the OS X Install DVD that came with the machine, or another USB installer to be able to run Disk Utility from outside the drive.

  • by Topher Kessler,

    Topher Kessler Topher Kessler Jan 1, 2015 2:02 PM in response to david.lski
    Level 6 (9,866 points)
    Jan 1, 2015 2:02 PM in response to david.lski

    Ah fair enough. In this case booting to a DVD, or using standard Recovery Mode to install to an external drive are two options. Alternatively, using Target Disk mode will allow the use of another Mac to directly access this one's boot drive.

  • by invisibleloop,

    invisibleloop invisibleloop Jan 1, 2015 2:05 PM in response to david.lski
    Level 1 (0 points)
    Jan 1, 2015 2:05 PM in response to david.lski
    In this case, he'll have to boot from the OS X Install DVD that came with the machine, or another USB installer to be able to run Disk Utility from outside the drive.

     

    Hi. Thanks for the reply. Do you know where I can find a walk-through to be able to perform the USB installer option? I don't have the original installer disks.

  • by Topher Kessler,Helpful

    Topher Kessler Topher Kessler Jan 1, 2015 2:15 PM in response to invisibleloop
    Level 6 (9,866 points)
    Jan 1, 2015 2:15 PM in response to invisibleloop

    If you have a 8+GB USB drive (16+GB is better) and can reboot your Mac into Recovery mode (hold Command-R at startup to get to this mode), then you can run the installer in recovery mode and install OS X to the USB drive. Just follow the installer's on-screen instructions and then select the USB drive as the installation destination. Your Mac will then boot off of this drive, and you can use Disk Utility on it to access your Mac's internal drive and perform the fix steps that I and david.Iski have mentioned above.

     

    ...If you cannot get into Recovery mode at all, and do not have another way to boot your Mac, then your best bet will be to take the system in to an Apple service center to have it looked at. You can use another Mac to access your current one's drive via Target Disk Mode (in the way I mentioned above), but this will require you have another Mac and the proper cabling to share a FireWire or Thunderbolt connection with your current Mac.

  • by invisibleloop,

    invisibleloop invisibleloop Jan 1, 2015 2:39 PM in response to Topher Kessler
    Level 1 (0 points)
    Jan 1, 2015 2:39 PM in response to Topher Kessler

    Thanks for the info. I will get a usb drive tomorrow and try this. I will let you know how I get on.

  • by JWDemon,

    JWDemon JWDemon Jan 1, 2015 9:05 PM in response to invisibleloop
    Level 1 (5 points)
    Jan 1, 2015 9:05 PM in response to invisibleloop

    You can use Internet Recovery...check this article, Computers that can be upgraded to use OS X Internet Recovery - Apple Support .Click on your model and it will take you to the download.

  • by david.lski,Solvedanswer

    david.lski david.lski Jan 1, 2015 10:30 PM in response to JWDemon
    Level 1 (85 points)
    Jan 1, 2015 10:30 PM in response to JWDemon

    No, he can't. Look at the original post, then look at the article you linked. His computer is too old, the firmware doesn't boot to Internet Recovery. The option to use the original install discs, or another bootable USB are the options to shoot for.

  • by JWDemon,

    JWDemon JWDemon Jan 1, 2015 10:44 PM in response to david.lski
    Level 1 (5 points)
    Jan 1, 2015 10:44 PM in response to david.lski

    Yes he can!!

     

    Copied from his original post, this is his computer.........iMac (27-inch Mid 2010), null

     

    Copied from the next to last listing on the page referred to.....iMac (21.5-inch and 27-inch, Mid 2010)

     

    Link to Download page.....iMac EFI Update 1.8

     

    Copied from Download page......About iMac EFI Firmware Update 1.8

     

    This update enables Lion Recovery from an Internet connection on iMac (Mid 2010) models.

  • by david.lski,

    david.lski david.lski Jan 1, 2015 10:55 PM in response to JWDemon
    Level 1 (85 points)
    Jan 1, 2015 10:55 PM in response to JWDemon

    That would definitely be a potential solution, but under the current circumstances we can't boot to the OS to install the update. So, for this particular scenario, it's still going to be the original boot discs or a USB.

  • by JWDemon,

    JWDemon JWDemon Jan 1, 2015 11:02 PM in response to david.lski
    Level 1 (5 points)
    Jan 1, 2015 11:02 PM in response to david.lski

    True, I just happened to run across that link on another site and remembered that you had said it was too old so I figured I should present the option but yes, unfortunately, gotta boot up to update!

  • by david.lski,

    david.lski david.lski Jan 1, 2015 11:06 PM in response to JWDemon
    Level 1 (85 points)
    Jan 1, 2015 11:06 PM in response to JWDemon

    Those two links definitely present semi-conflicting information. Going to keep that EFI update for that model in my back pocket. Glad you brought it up.

Page 1 Next