hey guys, long time lurker, first time poster here :
I need some help, My boss kidnly asked me if I "could bring some life to his old mac pro 1.1" with some effort and lots of reading I managed to change both cpu for quadcore' 3.0Ghz which pretty much doubled its multicore geekbench score, installed 32GB of ram, added a sata SSD and a radeon 280X, managed to build and install patched boot.efi version of El Capitan, and ran the scripts to protect it in case of "updates"
Computer has worked fine for over a month, but last night, the boss did "something" and the computer is stuck on a boot loop, in where the chime would sound and then it would reboot, i've already discarded ram issues or video card issues. as i managed to boot into recovery mode.
I'm hoping its a corrupted boot.efi thats acting up, since the other options could mean a fried SMC chip, from what ive gathered.
could you help me a bit?
any way to fix the boot.efi from recovery mode? try to use target boot ?
should i just try to backup the HD and try a fresh install ? thats a bit complicated should i just build a new capitan installer and try to reinstall over the old HD? will that delete his user data?
i'd like to not have to reinstall all the software and have to recover all his stuff again
I need some help, My boss kidnly asked me if I "could bring some life to his old mac pro 1.1" with some effort and lots of reading I managed to change both cpu for quadcore' 3.0Ghz which pretty much doubled its multicore geekbench score, installed 32GB of ram, added a sata SSD and a radeon 280X, managed to build and install patched boot.efi version of El Capitan, and ran the scripts to protect it in case of "updates"
Computer has worked fine for over a month, but last night, the boss did "something" and the computer is stuck on a boot loop, in where the chime would sound and then it would reboot, i've already discarded ram issues or video card issues. as i managed to boot into recovery mode.
I'm hoping its a corrupted boot.efi thats acting up, since the other options could mean a fried SMC chip, from what ive gathered.
could you help me a bit?
any way to fix the boot.efi from recovery mode? try to use target boot ?
should i just try to backup the HD and try a fresh install ? thats a bit complicated should i just build a new capitan installer and try to reinstall over the old HD? will that delete his user data?
i'd like to not have to reinstall all the software and have to recover all his stuff again