Jump to content
gengik84

macOS Sierra 10.12.6 final is out.

100 posts in this topic

Recommended Posts

How many "partitions" should a fresh install create?

Mine created 3 boot macOS from macOS Sierra, boot macOS from Recovery HD and boot Recovery from Recovery HD. Is this normal?

 

Sent from my SM-G930F using Tapatalk

Usually it creates two partitions one for macOS and one for Recovery. Sometimes I get three partitions one for Install macOS Sierra from HDD which will be automatically deleted once the installation is complete and the other two are macOS HDD and the Recovery HDD.

If you have more than one recovery HD that's probably because you only erased the macOS HD not the whole HDD.

Share this post


Link to post
Share on other sites
Advertisement

Usually it creates two partitions one for macOS and one for Recovery. Sometimes I get three partitions one for Install macOS Sierra from HDD which will be automatically deleted once the installation is complete and the other two are macOS HDD and the Recovery HDD.

If you have more than one recovery HD that's probably because you only erased the macOS HD not the whole HDD.

And what would someone do if after the install and 8 reboots they still have 3 entries?

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

And what would someone do if after the install and 8 reboots they still have 3 entries?

 

Sent from my SM-G930F using Tapatalk

 

Can you show me the "diskutil list" result? you can send it via PM if you don't wanna share the results here.

Share this post


Link to post
Share on other sites

Can you show me the "diskutil list" result? you can send it via PM if you don't wanna share the results here.

Shanes-MBP:~ shane$ diskutil list

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.1 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:                  Apple_HFS Windows 10              249.9 GB   disk0s2

   3:          Apple_CoreStorage macOS Sierra            124.4 GB   disk0s3

   4:                 Apple_Boot Recovery HD             650.0 MB   disk0s4

   5:                  Apple_HFS macOS High Sierra       124.7 GB   disk0s5

 

/dev/disk1 (internal, virtual):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:                  Apple_HFS macOS Sierra           +124.1 GB   disk1

                                 Logical Volume on disk0s3

                                 67C6D05F-9066-4A25-AD5E-43152BE1F853

 

                                 Unencrypted

Windows and High Sierra are not installed yet.

Share this post


Link to post
Share on other sites

 

Shanes-MBP:~ shane$ diskutil list

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.1 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:                  Apple_HFS Windows 10              249.9 GB   disk0s2

   3:          Apple_CoreStorage macOS Sierra            124.4 GB   disk0s3

   4:                 Apple_Boot Recovery HD             650.0 MB   disk0s4

   5:                  Apple_HFS macOS High Sierra       124.7 GB   disk0s5

 

/dev/disk1 (internal, virtual):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:                  Apple_HFS macOS Sierra           +124.1 GB   disk1

                                 Logical Volume on disk0s3

                                 67C6D05F-9066-4A25-AD5E-43152BE1F853

 

                                 Unencrypted

Windows and High Sierra are not installed yet.

 

Couple of questions:

 

1. Do you use custom entries in config.plist?

2. you just created the partitions to install windows and High Sierra later or you had them before you installed Sierra?

Share this post


Link to post
Share on other sites

you have a corestorage...


 

Shanes-MBP:~ shane$ diskutil list

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.1 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:                  Apple_HFS Windows 10              249.9 GB   disk0s2

   3:          Apple_CoreStorage macOS Sierra            124.4 GB   disk0s3

   4:                 Apple_Boot Recovery HD             650.0 MB   disk0s4

   5:                  Apple_HFS macOS High Sierra       124.7 GB   disk0s5

 

/dev/disk1 (internal, virtual):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:                  Apple_HFS macOS Sierra           +124.1 GB   disk1

                                 Logical Volume on disk0s3

                                 67C6D05F-9066-4A25-AD5E-43152BE1F853

 

                                 Unencrypted

Windows and High Sierra are not installed yet.

 

Share this post


Link to post
Share on other sites

Some times it is created by the installer.

It can be resolved from the terminal

If installing clovers in esp, it is likely to be installed in the root of the disk .. in this case..

Share this post


Link to post
Share on other sites

Couple of questions:

 

1. Do you use custom entries in config.plist?

2. you just created the partitions to install windows and High Sierra later or you had them before you installed Sierra?

No, no custom entries yet on this machine.

Yes the partitions were created with the 10.12.6 installer prior to installing macOS.

I can see that it is corestorage but what and why is it?

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

No, no custom entries yet on this machine.

Yes the partitions were created with the 10.12.6 installer prior to installing macOS.

I can see that it is corestorage but what and why is it?

 

Sent from my SM-G930F using Tapatalk

I belive @gengik84 answered all the questions  :P

Share this post


Link to post
Share on other sites

 

terminal 

sudo diskutil cs revert 67C6D05F-9066-4A25-AD5E-43152BE1F853

Thanks, that fixed it up

 

Shanes-MBP:~ shane$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Windows 10              249.9 GB   disk0s2
   3:                  Apple_HFS macOS Sierra            124.4 GB   disk0s3
   4:                 Apple_Boot Recovery HD             650.0 MB   disk0s4
   5:                  Apple_HFS macOS High Sierra       124.7 GB   disk0s5


p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff; min-height: 13.0px}
span.s1 {font-variant-ligatures: no-common-ligatures}

Any idea what caused this? This is the first time i've seen this and had it happen.

Share this post


Link to post
Share on other sites

Thanks, that fixed it up

Shanes-MBP:~ shane$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Windows 10              249.9 GB   disk0s2
   3:                  Apple_HFS macOS Sierra            124.4 GB   disk0s3
   4:                 Apple_Boot Recovery HD             650.0 MB   disk0s4
   5:                  Apple_HFS macOS High Sierra       124.7 GB   disk0s5


p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff; min-height: 13.0px}
span.s1 {font-variant-ligatures: no-common-ligatures}

Any idea what caused this? This is the first time i've seen this and had it happen.

I cannot think of a reason to why this is happened exactly, rather than the left over partition of a previous installation maybe  :rofl:

Off-Topic

 

@gengik84 and @SavageAUS do you know how can I use the grep command to get the result of a terminal command? 

Share this post


Link to post
Share on other sites

It may be a disk utility bug or installer bug.

I've never investigate more, when that happened I used the command on the terminal...and work.  :)

 

@gengik84 and @SavageAUS do you know how can I use the grep command to get the result of a terminal command? 

About what?

Share this post


Link to post
Share on other sites

It may be a disk utility bug or installer bug.

I've never investigate more, when that happened I used the command on the terminal...and work.  :)

About what?

 

(I'm sorry I know this is off topic)

 

But in general. I want to know how can it be done

 

I just wanna know if I can read the results of command per say "spctl --status" and then use the result in a statement of a source code for the app I'm working on

e.g

 

if I run 

$ spctl --status
assessments enabled

I want to grab the "assessments enabled" and then use it in a dialog box to show the result of the command

Share this post


Link to post
Share on other sites

 

There is a variety arguments... :P

An easy thing for example
result=$(spctl --status) 
echo "The result is: $result"

echo or printf etc..

 

That's easy for you my friend  :hysterical:

I'm not a coder I'm just trying to teach myself how to write small tools using AppleScript  :angel_not:

Share this post


Link to post
Share on other sites

I cannot think of a reason to why this is happened exactly, rather than the left over partition of a previous installation maybe :rofl:

 

Off-Topic

 

@gengik84 and @SavageAUS do you know how can I use the grep command to get the result of a terminal command?

The drive had a full format prior to install. I'll create another usb installer tomorrow and wipe the drive again and see what happens. At least if it happens again I'll know how to solve it.

 

As you know at the moment I do my coding in Windows so unfortunately I'm not well versed in grep yet.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

CS is also used for the new APFS, so if you formatted High Sierra with the new file system it would be a CS drive. but seeing that it was your normal Sierra partition doesn't make sense.  

Share this post


Link to post
Share on other sites

I can't boot in safe boot with 10.12.6, stuck with kextd wait IOResources, I tried a clean install and problem is still here.

Before 10.12.6 safe boot was fine, also I can boot in normal mode without any problem, everything works.

 

Edit: I fixed it, was a kext problem.

Share this post


Link to post
Share on other sites

Because of expiring certs, Apple have re-released installers from 10.15 back to 10.10. More info on that here.

 

However, I can't get the new Sierra installer to build a usb installer. Complains that the disk is not a valid mount point. Yet all the others worked fine.

 

Has anyone tried this new Sierra installer yet and found a way around the error? I tried replacing createinstallmedia with the one from my previous 10.12.6 installer but it gave the same error.

Share this post


Link to post
Share on other sites
49 minutes ago, Riley Freeman said:

Because of expiring certs, Apple have re-released installers from 10.15 back to 10.10. More info on that here.

 

However, I can't get the new Sierra installer to build a usb installer. Complains that the disk is not a valid mount point. Yet all the others worked fine.

 

Has anyone tried this new Sierra installer yet and found a way around the error? I tried replacing createinstallmedia with the one from my previous 10.12.6 installer but it gave the same error.

The same here. it is a bug, i think.

 

You can restore BaseSystem.dmg to USB partition, and replace /Volumes/OS X Base System/Install macOS Sierra.app to be the FULL Installer App.

or use MBR BaseSystem method.

Share this post


Link to post
Share on other sites

I checked the console and there's a load of -67050 MacOS errors related to authd. So I guess they might have screwed up the cert update on that one. I'm downloading it again to see if they've updated the image. A hash on the download page would have helped.

 

Nope. Still the same image (sha1 = 9ba989d30e3548341fc8f5847e856709cb5c67c2)

Edited by Riley Freeman

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×