0

I was using a Macbook Pro 2015 with a 20 GB partition for Linux and rest Mac OS X.

I had a security update for MacOS Sierra and did that. After that my reFind boot loader stopped showing up.

Then I tried recovering my 19 GB by going to disk utilities but I got an error. I went ahead with my work. Next day I turned on my machine and I got a reFind window(no Mac OS). I went to recovery(Cmd+R) and then erased my disk.

I tried installing MacOS again by using Internet Recovery tools and external bootable drive.

Internet recovery keeps on breaking and external bootable keeps giving me this error:-

The operation couldn't be completed (com.apple.osinstallersetup.LinkFileDownload error 3.)

Please see my disk details below and if there is a way I can fix this.

Details:-

General Info

-bash-3.2# diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *251.0 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS MacOsX                  250.7 GB   disk0s2

/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *32.0 GB    disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS Install macOS Sierra    31.7 GB    disk2s2

/dev/disk3 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +5.9 GB     disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS OS X Install ESD        5.5 GB     disk3s2

/dev/disk4 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +2.1 GB     disk4
   1:                  Apple_HFS OS X Base System        2.0 GB     disk4s1

/dev/disk5 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +5.2 MB     disk5

/dev/disk6 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk6

/dev/disk7 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk7

/dev/disk8 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk8

/dev/disk9 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk9

/dev/disk10 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk10

/dev/disk11 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk11

/dev/disk12 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +6.3 MB     disk12

/dev/disk13 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk13

/dev/disk14 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +1.0 MB     disk14

/dev/disk15 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk15

/dev/disk16 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk16

/dev/disk17 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk17

/dev/disk18 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +1.0 MB     disk18

/dev/disk19 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +6.3 MB     disk19

/dev/disk20 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk20

Disk Details:-

-bash-3.2# gpt -r show /dev/disk0
      start       size  index  contents
          0          1         PMBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6         
         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640  489562928      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  489972568     262151         
  490234719         32         Sec GPT table
  490234751          1         Sec GPT header
-bash-3.2# 
  • What does "After that my reFind boot loader stopped showing up." mean? This says what the computer did not do, but I need to know what did the computer do? Next, you state you are using the disk utilities. So, am I to assume the computer booted to the disk utilities instead of rEFInd? – David Anderson Mar 14 '18 at 17:53
  • And, what are the disk utilities? Is this the command disktuil? Or perhaps this is 'gpt', 'fdisk', 'gdisk', etc.... Maybe, the Disk Utility application, but this would require first booting to a macOS, macOS recovery, internet macOS recovery, a USB macOS installer, another computer via Target Disk mode, an external disk with macOS installer or one of many other ways to get an OS. – David Anderson Mar 14 '18 at 17:53
  • The reFind loader stopped showing up means that the OS straight away started booting from MacOS, with no prompt being shown that was shown initially, to choose from MacOS or Linux. – harsh2301 Mar 14 '18 at 18:24
  • When my computer stopped showing MacOS, I used Cmd+R that straight away went to Internet Recovery Tool. I then erased my drive with JHFS type and then started downloading chunks which kept failing. – harsh2301 Mar 14 '18 at 18:25
  • The commands are used in the recovery mode Terminal window.Yes the command is diskutil . The recovery mode was achieved using an external bootable USB. I hope I was clear. – harsh2301 Mar 14 '18 at 18:27
1

From your question and comments, this is how I chronologically pieced together events.

Note: Apple macOS refers to the volume, where the file the EFI firmware is suppose to load resides, as the startup disk. In the case of a BIOS boot (on models the can BIOS boot), the firmware always executes software on the Master Boot Record (MBR) provided the drive has a valid hybrid partitioning scheme.

  1. A security update for macOS Sierra was installed. The default startup disk was changed to the volume where macOS resides.

  2. The diskutil command failed to merge all or part of the space occupied by Linux back to the partition where macOS is installed.

  3. On startup, the Mac was unable to boot to the default startup disk (the macOS volume). This caused the firmware to search for any software that may be bootable. This resulted in a boot of rEFInd.

  4. The Mac was rebooted to macOS Recovery over the Internet. The diskutil command, given below, was used to erase the entire internal drive. An attempt to install macOS on an external drive lead to failure.

    diskutil  eraseDisk  JHFS+  MacOsX  GPT  disk0
    

There are may ways the default startup disk can be changed from rEFInd. Below is a list some of the possible ways.

  • From the firmware Startup Manager
  • From macOS System Preferences
  • From the Windows Control Panel (Requires Boot Camp)
  • From the Windows System Tray (Requires Boot Camp)
  • By reseting the NVRAM (PRAM)
  • By executing the bless command
  • By installing or reinstalling macOS (OS X)
  • By the installation of a software update.

The last item, in this list, caused rEFInd to initially disappear at startup. Steps 2 through 4 were not only unnecessary, but lead to the corruption.

You asked "Please see my disk details below and if there is a way I can fix this?" Well, there is nothing to fix. Evidently, you erased everything. At this point, just reinstall macOS.

| improve this answer | |
  • I tried re-installing macOS. I keep on getting the error I mentioned above. I used the same external USB to install MacOS on an external Hard Disk and I am able to use that. However my internal SSD keeps on giving me the error ,using the same external USB. – harsh2301 Mar 16 '18 at 5:54
  • Is there any other good software that can repair my disk? Because both the first Aid and the apple diagnostics by running D key while startup report no errors. Also while booting up from external hard disk, my internal SSD shows up in Finder. – harsh2301 Mar 16 '18 at 5:59
  • And why do you say steps 2 through 4 were un-necessary? Before when I downloaded MacOS High Sierra update I could not install it and the installer gave me an error, "Cannot install on this disk", so I figured I will have to delete my Linux partition. And I took this opportunity to clean install MacOS on my internal SSD – harsh2301 Mar 16 '18 at 6:11
  • No where in your question have you mentioned the installation of the update failed. The main difficulty in answering your question is not knowing what actually happened. You seem to only post what you what to without knowing if something you left out is important. – David Anderson Mar 16 '18 at 6:16
  • I posted in my answer based on what I read from your question and comments. I believe what you actually did differs somewhat. Can you read my answer and confirm these were the steps taken? – David Anderson Mar 16 '18 at 6:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .