Honestly, I’m suspicious of this. Motherboard suddenly dies. Encrypted disk but you don’t have the encryption key and you don’t know your password.
Maybe everything is on the up-and-up but truth be told, I’m skeptical of this whole story. ---- Andy > On Apr 10, 2019, at 5:59 PM, Carl Hoefs <[email protected]> > wrote: > > Thanks, George & Macs. The mobo's fried. I tried booting from an USB stick, > and it craps out that way too. > > If I transfer the internal 500GB HDD to another MacBook, will it work there? > It's encrypted with FileVault, and I don't know where I placed the volume > key. Would it "just work" or am I screwed without the pwd? > > -Carl > > >> On Apr 10, 2019, at 7:00 AM, George N. White III <[email protected]> wrote: >> >> On Tue, 9 Apr 2019 at 23:12, Macs R We <[email protected]> wrote: >> Could be faulty memory. Could be motherboard. >> >> Others have reported this error from a failed boot drive, e.g., >> https://forums.macg.co/threads/probleme-kernel-panic.1295906/ >> >> First, try zapping the PRAM. You never know. >> >> If it still fails, I'd boot it off an external drive with a good system on >> it (I keep one for each release). If you have another Mac with the proper >> system on it, you can always throw it into Transfer Disk mode and then boot >> the bad one off it. >> >> If it still fails, it's hardware. If removing the memory chips one at a >> time doesn't fix it, I'd write it off. >> >> It can be helpful to try booting a live Linux distro. If it works then you >> can try reinstalling MacOS. I had a similar vintage macbook pro with >> failed graphics hardware. MacOS refused to run, but Ubuntu was able to boot >> to a text console from which it is possilbe to tweak the configuration to >> work around the failed hardware. Linux `dmesg` often has details of >> hardware issues found at startup. >> >> >>> On Apr 9, 2019, at 4:09 PM, Carl Hoefs <[email protected]> >>> wrote: >>> >>> If I try booting up my 2010 MacBook Pro 7,1 I get a gray screen of death. >>> >>> <IMG_0965x.jpeg> >>> >>> "unexpected SIGKILL of init with reason -- namespace 9 code 0x1 description >>> none" >>> >>> Does this mean a mobo issue, or the HDD is kaput? >>> >>> There's no recovery partition, and the HDD is FileVaulted with >>> who-knows-what password. >> >> -- >> George N. White III >> > > _______________________________________________ > MacOSX-talk mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/macosx-talk _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
