I spanned some (3) disks together as a temporary measure in windows 10 meaning to copy all the data over to a 6 disk raid for safety’s sake, To make a sad story short , I never got around to getting the copy done and windows June update did SOMETHING to destroy the volume. After the update upon the (first) boot(s) windows would stall at the swirling circle and one of the disks in the spanned set would be at 100% usage for hours . I finally just shut the system down and have been trying to get the disks back together since. This is all part of moving to a new MOBO weeks ago (hence the temp spanned). This volume basically has about 20 years of documents,programs, taxes, etc. not to mention downloads and software from years gone by. I should mention it was just fine until rebooting from the update.
I move those disk over to the old mother board with the pre-update windows installed on it from a cloned disk (in case the move went badly moving to ssd ) not connected to the internet. Now they show as 2 sets of foreign disks to windows. The one set is showing Disk 2 and Disk 3, The other is showing Disk 1 in disk manager (which is correct). I am convinced the data on the disk is fine and hopefully the ntfs volume data too ( SMART on all 3 are good ) and that some where along the line windows screwed up the metadata for the volume or more likely just the volume signature during the update. OR they changed drivers for the PCI adapter the drives where connected to. ( It didn’t seem to act right after ) and they corrupted it that way somehow.
I Really have no clue what happened other then it don’t work now and it should , nothing changed except the update
The Actual Question : Does anyone know where or how windows stores the name of the volume group on disk ,address,offsets etc ? so I can compare them between the 2 sets and some how combine them back together as one volume then import them ? I can’t seem to find a disk map online for dynamic spanned disks but someone somewhere has surely mapped them at some point.
The alternative is to do it the really tedious way and use TestDisk or some such to get the files piecemeal as best as I can, which when dealing with around 10-15 TB of data could take days at the least months at worst.
I suppose I can DD them to my large raid array and work from there as a safety measure until if and when I can fix this volume group….sorry thinking out loud.
Any other Ideas on how to fix this volume would really be appreciated or to quickly get the data back .
