- Joined
- Jul 12, 2011
- Messages
- 44
- Motherboard
- Maximus VIII Impact
- CPU
- i5-6600K
- Graphics
- GTX780Ti
Something seems to be corrupted on your system possibly from the boot loader causing problems initialising the Kernel. What have you done since the last good boot? Have you changed anything in the BIOS? Possible solutions is to use another installation/drive and target MultiBeast or Chimera to the defected install. Boot from a back up if you have one. If none of those are ideal solutions for you it may save you some time and reinstall. Probably not what you want to hear or do.
I've isolated the problem, and I'm more confused than ever.
Boot is prevented by having my 2TB backup drive connected to the system. It has no OS on it, nothing at all except Time Machine backups, but having it connected to the system during boot prevents any sort of startup—if it's connected, it doesn't even get to the bootloader screen.
Wtf. Have you run into this before? Why would something as harmless as a SATA drive cause this?
Oh, and for some reason, my main install works normally; I don't have to -F or -x anymore.
Everything here seems utterly illogical.
(Oh, I enabled hot plugging on the 2TB drive—I can connect it once the system starts and I run into no problems)