Any Mac experts?

TimmyO

anyone got any thoughts on this:?

MBPr with El Capitan.

FileVault was enabled from the get go and all was well.

Suddenly it was not possible to log in - touchpad/mouse/keyboard barely responsive - eventually it gives the option to reboot minus filevault - this fixes the issue (after it spends some time decrypting the disc)

all appears to be well, no data lost. Re-enable FV, reboot, same issue. Disable FV, reboot, all well.

so as long as I don't enable FileVault - everything is fine.

WTF?

strumjoughlamps

have you gone through repair disk routine yet to see if that helps?

beed84

Try PRAM reset:

1. Turn off mac
2. Turn on and hold down command, option, p and r
3. Hold until it reboots
4. Let go when it chimes and let it load

Hopefully that will resolve it.

digitalscream

Total shot in the dark, but could it be a potential disk problem?

In any case, the first thing you need to do is boot up without FV and do a full backup if you can.

Jalapeno

digitalscream said:

Total shot in the dark, but could it be a potential disk problem?

In any case, the first thing you need to do is boot up without FV and do a full backup if you can.

This.

bingefeller

I would boot into recovery mode and run permissions repair, verify disk etc and try rebooting again with FV on and go from there.

TimmyO

Yeah I've got a full bootable image and Time Machine backups on an external drive, I'm all good for backups ;-)

cheers will try that permissions thing

tim

Drew_TNBD

FileVault shouldn't really have anything to do with mouse or keyboard performance, and it shouldn't prevent you from logging in.

You might have a permissions error on your drive, or your drive is about to die on you.

Also, fixing permissions using Disk Utility can be a bit hit and miss. Much better to do it from within terminal.

Whitecat

Drew_fx said:

Also, fixing permissions using Disk Utility can be a bit hit and miss. Much better to do it from within terminal.

I think in El Capitan now you *have* to do it that way, they've removed that option from DU.

TimmyO

There is no fix permissions option in du or in the recovery mode du

did the other stuff.

rebooted

activated FV

rebooted - prob was back - unresponsive keyboard so can't log in.

after a while option to power cycle in to a login issues screen comes up

do that

subsequent screen asks for password to disable FV

type it in

says pw is wrong (it isn't - try many many times being super careful with typing)

stuck  I in a loop of the 6 lines above :-( 

Whitecat

Load Terminal and type this: sudo diskutil repairPermissions /

TimmyO

Is it possible to boot in to terminal ?

Whitecat

Yep, hold down Cmd+S when you restart.

TimmyO

Ok the next boot let me "reset" my password 

boot cycles now seem to take an age between chime and apple logo

Danny1969

Did you reset the NVRAM ? if not turn on hold down cmd + option + P + R keep holding until it restarts and you hear it chime a second time

TimmyO

I think I got 3 chimes when it did that key combo (I wasn't sure how long to hold but held for at least 3 chimes worth lol ) 

TimmyO

I'm stuck in a cycle of unresponsive keyboard, reboots to recovery, rejects password to disable FileVault 

Drew_TNBD

Whitecat said:

Drew_fx said:

Also, fixing permissions using Disk Utility can be a bit hit and miss. Much better to do it from within terminal.

I think in El Capitan now you *have* to do it that way, they've removed that option from DU.

Oh wow. That was news to me!

TimmyO

The terminal command didn't work - seems to have changed - googled for another and ran fix permissions

Also got a 'partition size error kit prevent boot' message running no first aid in the disk this time.

fix seems to be to change partition size then change it back, but I couldn't do this in safe mode for some reason (just errors and stopped the process)

was as about to give up and do fresh OS X install but re-did the pram reset for no particular reason. This time it booted normally - wtf.

filevault now reports encrypting the drive. Few mins remaining. The next reboot will be the important one...

TimmyO

Optimizing- 1 hour remaining.

(looks around empty office)

:-/ 

TimmyO

3 hours ....