UPDATE:
I wiped the partition and reinstalled. Looks like CCC didn't too good of a job on the clone. So I wiped, reinstalled, used MA during initial startup to move the failing drives setup over and things have been running great ever since. I think CCC is not as ready as they profess. Yesterday I pushed a friend to it that couldn't get the Apple DMG way to work and he had to rerun the current version installer over his install to get it to work.
_________________________________________________________
I know it's a really long post, but so was this first time experience!!
Have just partially recovered from a nightmare new drive install. I was getting the warning that my main boot drive was failing. The last time I ignored the warning, the drive crashed and it was a "mission critical" drive. I was able to recover it successfully using Disk Drill. Also after letting it sit for months, it kinda worked on its own. So the other day a was finally able to get a 2TB Drive. But one thing I did notice was that is was a 5400RPM and not 7200 like the previous one. I was under the impression that all WD Blues were 7200. Anyway, got it all partitioned and the dying drive cloned to it using CarbonCopyCloner. All seemed good until I installed the drive and it wouldn't boot at all. So I dug and realized that I had formatted the drive as "Master Boot Record" instead of GUID. After repartitioning the drive this time I took advantage of CCC's multiple Task run capability. It ran all night which was longer than doing it as individual Tasks. But when all done it wasn't a good Boot transfer. This latest version is crap. I have been using CCC for years and always got perfect block level transfers. Well it looks like not anymore. It is so fancifide that it's not as drop and dash as it was, although it professes it is. The Data Partitions copied fine, but my Patched OS 10.12.6, did not come over well. I have moved all kinds of things and installs all over for years and never anything like this.
After all was said and done and I fired up my 3,1 and it came up for the most part. Kinda slow, immediately I thought the slower drive. But the transfer was not as intact as I have had in the past. So I let it run for a couple of days and fixed things as I encountered them. Yesterday it took a good portion of the day to get my machine to boot up. But once it did it ran great for a good 12 hours until I turned it off. That was after a days work and hours of finding what was eating up all the space on that partition so that I would get the "Your Disk is Full" message. First time ever. I found it and killed that. But after the day was done I decided to wipe the partition and install fresh and all was fine up until I shutdown.
Today I booted up and the progress bar got half way and the machine rebooted and rebooted and came up. But bootup was the strangest I have ever had. Again slow, but it came up, the desktops on 3 monitors came up and then they went black and the Apple and progress bar came back up, this time White on Black and the bar went from halfway to done really fast and the screens came back. So right there I was instantly cautious and gun-shy. And about 10 minutes later the machine rebooted, rebooted, rebooted and then the Power Light started flashing once a second. No tones. RAM Error. But the Self-Test Passed almost every time before. I got booted from the Patch Installer and ran Disk Util and it found some stuff that is says it fixed. I reran the Patches and upon selecting the "Force Cache Rebuild" I got the message that I "might" have to do something in Terminal when rebooted. I have never seen that message before. So I restarted, it came up and after about 2 minutes the screens went black and it rebooted and I got the Flashing Power Light again.
So I spent the day taking the whole machine apart, cleaned and reseated the RAM and Video Cards, checking the Battery, it was great, better than the new one I had for it. Upon finishing I restarted and it wouldn't boot to Sierra. I immediately tried to boot from the Flash Drive Installer hoping I could rerun the patches and get the "Terminal Message", thinking that was it. After 45 minutes, usually 20 seconds to get the progress bar to 100%, but no further. I force stopped the machine and for the heck of it I thought I would try to boot to the Recovery Drive and it worked, first time ever. I have always selected the Recovery Drive Patch. Once there, no patcher, I was just hoping and not expecting and I ran Disk Util. Again it came up with stuff. I then bit my lip and restarted, and the machine came up and . . . that's where I'm typing from now. So it's been running for a good while so I could write this book.
I have had partitions on the "old drive" with MōJāve and Catalina that ran great. I also have Leopard, Snow Leopard, Lion, Mtn Lion, Mavericks all for software I need to use that will only run in those OSs. Once I get this all settled, I will move all that to Parallels. But I have NEVER had this much trouble with any of the dd1 Patches, nor a machine.
So do I need a new 7200RPM Drive; to do the Terminal Message (if I could find out what it was) that I originally came here to look for and couldn't; do something with the install that I have never needed to before; get a newer machine (I have a 5,1 lined up); install again differently? I have become so complacent with using these Patches, making sure to keep everything up to date, that I have tried things I would never have before and all was great. Until now . . . .
Any assistance will be greatly appreciated.
Thank you for tolerating my book . . .
. . . fb