Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iMac slow boot - prohibited sign

darkweather

darkweather

macrumors regular
Original poster
Aug 8, 2013
213
54
To erase the old efs partition I used windows. That's not the case. What interesting is, when I boot holding alt key and select SSD the problem doesn't occur.
 
grahamperrin

grahamperrin

macrumors 601
Jun 8, 2007
4,942
648
Yes, I did read all the posts, including this –

Weaselboy said:
… I'm kinda out of ideas here short of either the SSD or enclosure being bad.
Click to expand...

At least one post from someone else (not Weaselboy) contains misleading information, but I chose to not draw attention to the mistake.

About the screens you see when your Mac starts up - Apple Support – the prohibitory symbol is without exception a sign that either:
  1. the Mac can not find a valid System Folder to start up from; or
  2. there's a preference to start a version of the operating system that is incompatible with the Mac.
darkweather said:
… again (the prohibited sign). …

LIpRfz.jpg
Click to expand...

To the right of those two, is there ever a third startup option?
 
  • Like
Reactions: Weaselboy
grahamperrin

grahamperrin

macrumors 601
Jun 8, 2007
4,942
648
OK, thanks … so we should think about possible causes for the Mac sometimes behaving as if an OS that was previously valid (for startup) is no longer valid.

Is FileVault 2 enabled for one or both of the disks?
 
grahamperrin

grahamperrin

macrumors 601
Jun 8, 2007
4,942
648
I see you at https://www.reddit.com/r/applehelp/comments/4fbmb0/kernel_error_but_then_normal_boot_after/ … there's also https://forums.developer.apple.com/thread/8662#23693 but (sorry) I'm not absorbing the latter.

MacRobert10 said:
Just a guess, but could it be possible that the USB device is port powered and starts off in low power mode and the system has to kick it into high power mode to start the unit up? If that's the case and the unit has a provision to be externally powered then supplying external power to the unit may stop that from happening.

This is a guess, …
Click to expand...

Adding to that guesswork (and I'm still guessing):

@darkweather I don't have relevant experience with SSD enclosures but next time you find the prohibitory sign, try disconnecting then reconnecting the drive without switching off the Mac. That might sound scary – and if it's a verbose boot, the aftermath of reconnection might appear alarmingly garbled – but I'd like to know whether the Mac can be 'forced' to progress past that sign.

(Recent https://forums.developer.apple.com/thread/49672#146867 was entertaining, but I did not bother to capture the events on video. Rotational media, not SSD. As far as I recall I resorted to a reinstallation of the OS, but that wasn't the end of it.)
 
darkweather

darkweather

macrumors regular
Original poster
Aug 8, 2013
213
54
grahamperrin said:
I don't have relevant experience with SSD enclosures but next time you find the prohibitory sign, try disconnecting then reconnecting the drive without switching off the Mac. That might sound scary – and if it's a verbose boot, the aftermath of reconnection might appear alarmingly garbled – but I'd like to know whether the Mac can be 'forced' to progress past that sign.
Click to expand...

my english is maybe not good enough to understand but as far as i can understand i disconneted the usb cable when i saw the prohibitory sign then after 4-5 sec. later i plugged it again. after that apple logo seen, after that again prohibitory sign seen and after that again apple logo seen and then recovery mode started.
 
  • Like
Reactions: grahamperrin
grahamperrin

grahamperrin

macrumors 601
Jun 8, 2007
4,942
648
Thanks, that is useful.

With Recovery OS running, use the menu bar to launch Terminal. Please enter the following command:

diskutil list

Then copy the output from the Terminal window, quit Terminal and (still in Recovery OS) use Safari to log in to MacRumors Forums. Paste to this topic.

----

Looking ahead: if you have a good backup of what is on the disk(s), then it may be useful to perform a relatively simple test of the hardware.

I sometimes use 'Parted Magic', which is included with Ultimate Boot CD (UBCD). A screenshot of the 'Disk Health' software in Parted Magic:

b03_pm-gsmartcontrol_reference.jpg


In your case I would recommend first a short self-test, followed by an extended self-test.

However, I do not know whether Parted Magic will be able to do what's recommended with a disk that is connected via USB.

The screenshot is taken from http://www.linux-magazine.com/Online/Features/Fixing-Disks-with-Parted-Magic
 
Last edited:
darkweather

darkweather

macrumors regular
Original poster
Aug 8, 2013
213
54
when i did unlplug-plug, this time system boot normally. then i shut down mac and entered recover mode with alt key.
grahamperrin said:
With Recovery OS running, use the menu bar to launch Terminal. Please enter the following command:

diskutil list

Then copy the output from the Terminal window, quit Terminal and (still in Recovery OS) use Safari to log in to MacRumors Forums. Paste to this topic.
Click to expand...
Code: 
-bash-3.2# diskutil list

/dev/disk0 (internal, physical):

  #:                       TYPE NAME                    SIZE       IDENTIFIER

  0:      GUID_partition_scheme                        *1.0 TB     disk0

  1:                        EFI EFI                     209.7 MB   disk0s1

  2:                  Apple_HFS Machintosh HD           300.0 GB   disk0s2

  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

  4:                  Apple_HFS HD2                     699.2 GB   disk0s4

/dev/disk1 (external, physical):

  #:                       TYPE NAME                    SIZE       IDENTIFIER

  0:      GUID_partition_scheme                        *120.0 GB   disk1

  1:                        EFI EFI                     209.7 MB   disk1s1

  2:                  Apple_HFS SSD                     119.2 GB   disk1s2

  3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3

/dev/disk2 (disk image):

  #:                       TYPE NAME                    SIZE       IDENTIFIER

  0:      GUID_partition_scheme                        +2.1 GB     disk2

  1:                  Apple_HFS OS X Base System        2.0 GB     disk2s1

/dev/disk3 (disk image):

  #:                       TYPE NAME                    SIZE       IDENTIFIER

  0:                            untitled               +5.2 MB     disk3

/dev/disk4 (disk image):

  #:                       TYPE NAME                    SIZE       IDENTIFIER

  0:                            untitled               +524.3 KB   disk4

/dev/disk5 (disk image):

  #:                       TYPE NAME                    SIZE       IDENTIFIER

  0:                            untitled               +524.3 KB   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               +6.3 MB     disk9



/dev/disk10 (disk image):

  #:                       TYPE NAME                    SIZE       IDENTIFIER

  0:                            untitled               +2.1 MB     disk10

/dev/disk11 (disk image):

  #:                       TYPE NAME                    SIZE       IDENTIFIER

  0:                            untitled               +1.0 MB     disk11

/dev/disk12 (disk image):

  #:                       TYPE NAME                    SIZE       IDENTIFIER

  0:                            untitled               +524.3 KB   disk12

/dev/disk13 (disk image):

  #:                       TYPE NAME                    SIZE       IDENTIFIER

  0:                            untitled               +524.3 KB   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               +6.3 MB     disk15

-bash-3.2#
 
Last edited:
grahamperrin

grahamperrin

macrumors 601
Jun 8, 2007
4,942
648
Thanks. Partly reformatted:

Code: 
-bash-3.2# diskutil list

/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Machintosh HD 300.0 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Apple_HFS HD2 699.2 GB disk0s4

/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *120.0 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS SSD 119.2 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3

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

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

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

/dev/disk5 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB 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 +6.3 MB disk9

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

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

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

/dev/disk13 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB 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 +6.3 MB disk15

-bash-3.2#

– enough to see that in this case, I think, the Mac booted Recovery OS from its internal drive.

Is your 'HD2' just user data? Or have you ever used that partition to test another system? (Sierra, maybe?)
 
grahamperrin

grahamperrin

macrumors 601
Jun 8, 2007
4,942
648
OK, I recommend a check of the hardware.

Maybe beginning with something that will work with S.M.A.R.T (e.g. Disk Health, mentioned above).

If you can not access the S.M.A.R.T. features of the drive over USB, then use something that can thoroughly check all blocks of the drive.

(It's possible for a drive with all blocks apparently good to have corruption of data, but I should not jump to that conclusion. If the drive is good and if you are lucky, a reinstallation of the operating system may resolve the problem.)
 
DeltaMac

DeltaMac

macrumors G5
Jul 30, 2003
13,749
4,572
Delaware
What kind of external enclosure do you have?
Is it self-powered (with a separate cable for power), or is it bus-powered (only a USB cable connected)?
Bus powered can be flaky with some of the "generic" brands, particularly when using as a boot drive.
 
darkweather

darkweather

macrumors regular
Original poster
Aug 8, 2013
213
54
DeltaMac said:
What kind of external enclosure do you have?
Is it self-powered (with a separate cable for power), or is it bus-powered (only a USB cable connected)?
Bus powered can be flaky with some of the "generic" brands, particularly when using as a boot drive.
Click to expand...
Only USB powered. But I mentioned before that this problem has began with early versions of 10.10
 
DeltaMac

DeltaMac

macrumors G5
Jul 30, 2003
13,749
4,572
Delaware
darkweather said:
Only USB powered. But I mentioned before that this problem has began with early versions of 10.10
Click to expand...

Exactly. Not likely a software issue, which leaves - wait for it - hardware. Try a different external enclosure.
Anker, Inateck, Oyen are all pretty good players in this market. Verify UASP support, too.
 
darkweather

darkweather

macrumors regular
Original poster
Aug 8, 2013
213
54
i tried this: (http://www.cnet.com/news/fix-slow-start-ups-in-os-x/)
sudo chown root:admin /
sudo kextcache -system-prelinked-kernel
sudo kextcache -system-caches

copied from terminal:
Code: 
iMac:~ darkweather$ sudo chown root:admin /

iMac:~ darkweather$ sudo kextcache -system-prelinked-kernel

JMicronATA.kext has no Info.plist file.

JMicronATA.kext has no Info.plist file.

JMicronATA.kext has no Info.plist file.

JMicronATA.kext has no Info.plist file.

iMac:~ darkweather$ sudo kextcache -system-caches

JMicronATA.kext has no Info.plist file.

JMicronATA.kext has no Info.plist file.

JMicronATA.kext has no Info.plist file.

JMicronATA.kext has no Info.plist file.

JMicronATA.kext has no Info.plist file.

JMicronATA.kext has no Info.plist file.
 
darkweather

darkweather

macrumors regular
Original poster
Aug 8, 2013
213
54
i did a lot of things. i found a command and get a 4814 lines of stuff. there is something interesting:

Code: 
Bad kernel extensions
    /System/Library/Extensions/AppleOSXUSBNCM.kext

any idea what is this and could be relevant to this issue?
 
grahamperrin

grahamperrin

macrumors 601
Jun 8, 2007
4,942
648
darkweather said:
any idea what is this and could be relevant to this issue?
Click to expand...

No idea, although Google finds a few discussions.

Relevance: if you attempt to start OS X in verbose + safe mode, is there any indication that the KEXT might be problematic? In some cases, safe mode allows load (or attempted load) of a KEXT that is not really safe.
 
darkweather

darkweather

macrumors regular
Original poster
Aug 8, 2013
213
54
i guess there is some incompatiblity between kingston ssd and os x 10.10.x
so there must be some setting or some code to change it but nobody knows what it is so far.
 
darkweather

darkweather

macrumors regular
Original poster
Aug 8, 2013
213
54
And it is very interesting that today last 2 times this issue didn't occur.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom