After getting my OS right on the SSD, getting my audio card and UAD2 good, getting SPLAT and more apps running, I hooked up extra drives to back things up (good, right?!?). Apparently, they had drive names shared with current drives, which turned parts of my old OS drive and my Samples drive RAW. No idea why. Just more hoops to jump through for sonic nirvana...
 
I picked up easeUS and tried recuva ( which didn't leave the directory fully intact - pic in next post)) to work on the RAW partitions to hopefully recover them and get back to normal. I scanned the 1TB (600GB used space) old OS drive to find a total of 3.5 TB or so files recovered. WTH? is this compressed? if so, how do I put the geni back in the bottle? If I'm looking at this all wrong, I apologize.... If not, I may need a whole Sonar team to deal with it.
I have (1) 2 TB drive for backup of what I thought would be enough for 92) halfish filled 1TB drives. " />

I believe this confirms my fears. " />

You might want to change the thread title to attract Win 10 users. The drive conflict makes no sense to me since I have always done exactly that (but never gone beyond 7). One of the old drives was a bootable OS drive? I am not sure how Win 10 reacts to such or if the BIOS boot options played into it, but some Win 10 expertise is in order.

Might get more results in the Computer forum.

Should I double post or wait for a mod to move all this?
 
As an update til the time that's sorted....
 
I found an executable called testdisk. It apparently is capable of fixing the disk so that recovery isn't necessary.  In it I've found this info about one of the disks in question, but have zero clues about where to go from this point. Has anyone used testdisk? Thanks " />

Moved here as suggested by mudgel and indicated above by jshep0102.

Much thanks to you!

I don't think the duped volume names is an issue. The name the OS uses internally is drv letter + vol name + disk ID.
One thing you may want to do is change the attributes of the data drive partitions so they are not active. This really should not be necessary (I have a win8.1 C: and an XP D: where I can boot XP from D: via the bios boot sel and still use D: as data for win8.1 c: ) but you are having issue I have never had so it might not hurt.
The fact that one drive has a partition conflict is troublesome. Any partitionng tools I have used will not even let you do this. Is this the orig failing drive that had W7 on it ?

It never 'failed'. IT was upgraded from 7 to 10 successfully. But it was slowing me down considerably, now that I have the SSD to compare it to. I have a logfile created by testdisk that may or may not tell you anything. It says i'm on W8, I'm on 10. Should I run this on compatibility mode for 7?
 
http://forum.cgsecurity.org/phpBB3/post18703.html#p18703
 
 Way beyond my understanding.

From what I can tell, your PC is booting or trying to boot from OLD win10x64 which is listed as the C: DRIVE. Did you adjust the boot order in the bios as suggested.