![]() ![]() I'm eliminating Chrome Remote Desktop from this Mini (And changed my Google password) as that's the only way I can think of that something like this would have gone down. Needeless to say, the previous SSD is toast and it has me wary of SSDs as a reliable alternative to spinning drives (although the pros do still outweigh the cons). I remain baffled as to how this all went down (hyperbolic speculation warning: some bratty kid down the block might have hacked their way into my wifi and had fun with something like Thunderstrike 2). However a fresh install of Big Sur along with a time machine restore appears to have worked. The CLOVERX64.efi file does exist in that location. The Windows 10 and Ubuntu items boot fine. The EFI Boot image still showed when starting the 2014 mini with the option key held down and a new SSD installed, even with no bootable volume. After loading this I then run sudo grub-mkconfig -o /boot/grub/grub.cfg and then sudo update-grub the menu comes up fine but when I select the Yosemite item I get errors. ![]() It crashed disk first aid and unmounted repeatedly.ģ) Gave up, installed a new SSD in the 2014 mini and restored from a time machine back up. if I change to UEFI it will not work Windows no BOOT And if I try UEFI. It proceeded to kernel panic the T2 mini repeatedly.Ģ) pulled the SSD and tried running disk first aid via a SATA to USB cable. Restart the computer and at the Alienware logo start tapping the F12 key to. You can then use the preference pane to check for future updates. Boot macOS, download the latest Clover Installer and select these options. 1) Booted the Mini in target disk mode and plugged into a newer T2 Mini via TB2 to TB3 adapter. EFI/CLOVER/kexts The file you need to worry about: EFI/CLOVER/ist Those directories will contain the contents you modify to boot properly. ![]()
0 Comments
Leave a Reply. |