crwdns2933423:0crwdne2933423:0
crwdns2918538:0crwdne2918538:0

crwdns2934243:0crwdne2934243:0 Dan

crwdns2934249:0crwdne2934249:0:

-cNet had the answer for me. Apparently your startup disk setting is pointing to a disk that's no longer in your system. I'm guessing the OS can't find it and is waiting for it to spin up. It doesn't try the new SSD until a timeout occurs. Go to system preferences and set your startup disk to be the new disk and I'll bet that changes everything. It did for me.
+The internet had the answer for me. Apparently your startup disk setting is pointing to a disk that's no longer in your system. I'm guessing the OS can't find it and is waiting for it to spin up. It doesn't try the new SSD until a timeout occurs.
+
+Go to system preferences and set your Startup Disk setting to be the new disk and I'll bet that changes everything. It did for me.

crwdns2915684:0crwdne2915684:0:

open

crwdns2934241:0crwdne2934241:0 EBarnhart001

crwdns2934249:0crwdne2934249:0:

cNet had the answer for me.  Apparently your startup disk setting is pointing to a disk that's no longer in your system.  I'm guessing the OS can't find it and is waiting for it to spin up.  It doesn't try the new SSD until a timeout occurs.  Go to system preferences and set your startup disk to be the new disk and I'll bet that changes everything.  It did for me.

crwdns2915684:0crwdne2915684:0:

open