I can't log in to my laptop after loading Sierra
Turn on, get log on screen, type in password, log in screen comes back up, start typing password again and keyboard and mouse freeze. I can't log on!
471869
2个答案
已选择的解决方案
声誉积分: 497.3千
35
339
975
I suspect your HD has some corruption or the HD SATA cable is failing. Odd behaviors like this often happen when the system tries opening a lot of files at once after an upgrade.
The best thing here is to find a second Mac system which you can connect in Target Disk Mode so you can salvage anything important or create a backup. Once done, you can try to reformat the drive from the other system and then reinstall the OS and restore your backup.
Let us know how it goes so we can guide you which way to go next.
这个答案有帮助吗？
得分
2
最有帮助的答案
声誉积分: 48.8千
7
66
97
Start the laptop up in Safe Mode.
Hold down "SHIFT" while turning on the computer from an "powered off" state.
If you can login in safe mode, Follow Dan's advise and backup your stuff, then format and reinstall the OS from scratch.
This will require a bootable thumb drive installer for Sierra or High Sierra.
这个答案有帮助吗？
得分
2
@avanteguarde - If he has a second Mac no need for the Installer thumb drive as he can do it from the other Mac. Think of it this way the OP's Mac is nothing more than an external HD from the controlling Mac system in Target Disk Mode. If you see it that way the steps to make an external disk bootable are the same!
@danj he should upgrade/install Sierra/High Sierra natively on the Mac he intends to use. There is a very important EFI firmware update that only installs on a proper install.
Thats only true if he upgrades to High Sierra at this point. Reread the title "after loading Sierra"
I'm assuming he is sticking with Sierra for now and during that upgrade process to Sierra the firmware has already been upgraded. So we don't need to worry here.
@danj Sierra also updates the EFI firmware.
True! But its done BEFORE the user gets the OS back to use: When the person is greeted with the User Login screen or Desktop.
So bottomline its done during the OS upgrade not after!
What is likely happening is the Indexer task is running wild as the drive is highly fragmented (HDD setup) or the HD SATA cable is breaking down (HDD or SSD setup)
