I apologize for the wall of text in advance.
I turned on my desktop mid-afternoon on the 22nd and Windows decided to do the anniversary update. The update caused my graphics card to stop working and I ended up speaking to Nvidia tech support. They weren't able to make any progress and recommended checking Windows update again to see if it would help. Unfortunately, the second Windows update left me with a machine that wouldn't boot past a black loading screen after the Windows logo. At this point, I got MS tech support involved and none of their suggestions worked, and they eventually recommended I wipe the Windows install and start fresh.
Not wanting to lose anything, I used the command prompt on the Windows install media to copy files from my 250 GB SSD to my 1 TB HDD(dynamic drive, simple partitions of 146.48 GB and 785.03 GB). I eventually got sick of the command line transfer and ended up setting up and using a Linux Mint liveUSB to be able to visually check progress instead of constantly typing commands to check. This, I believe, was the cause of my major downfall. Once in Linux, I tried to mount the TB drive, and it wouldn't work. I did some research and used ntfsfix to get it to mount for me. After a little further fiddling with the SSD, I was able to see both and was able to copy files over to the HDD.
At this point, I decided I had done enough and was confident I wasn't going to lose anything important, and went back into the Windows install media to check things, saw the command prompt didn't seem to be reading free space on the HDD correctly, but didn't think much of it. As a last test before wiping, I tried pulling my video card with the machine off and booting it up. Shockingly, the machine booted up into Windows just fine. Unfortunately, Windows was seeing the HDD as only having a capacity of 785 gigs. I freaked out a bit because that certainly wasn't as it should be, did some looking around, and couldn't fix anything.
At this point, I contacted MS tech support and began to confuse the poor rep that I was connected to. He didn't have many suggestions beyond chkdsk and disk cleanup, but confirmed that bootrec.exe /fixmbr and its other commands could probably help. I believe that this is the second major mistake in all of this. This, unfortunately, did not fix my problem. Knowing that I had been using linux and was able to see the entire drive there, he suggested I use that, back it all up wherever I could, and then reformat the drive. I disconnected and went about his suggestion. Unfortunately, Linux was now seeing the same 785 gig drive that Windows was.
That is where I'm stuck at this point. Currently, Windows Explorer and any similar program sees the drive like this. Disk Management is seeing both simple partitions as healthy, but only the 785 gig partition is viewable by Windows. After some research, my best guess is that the LDM is busted, but I have no idea if that's actually the case, and I'm not seeing anything online to help if it is the case.
Is there anything I can do to repair this dynamic disk so I can avoid losing whatever has been put on that part of the drive? Thanks in advance.
I turned on my desktop mid-afternoon on the 22nd and Windows decided to do the anniversary update. The update caused my graphics card to stop working and I ended up speaking to Nvidia tech support. They weren't able to make any progress and recommended checking Windows update again to see if it would help. Unfortunately, the second Windows update left me with a machine that wouldn't boot past a black loading screen after the Windows logo. At this point, I got MS tech support involved and none of their suggestions worked, and they eventually recommended I wipe the Windows install and start fresh.
Not wanting to lose anything, I used the command prompt on the Windows install media to copy files from my 250 GB SSD to my 1 TB HDD(dynamic drive, simple partitions of 146.48 GB and 785.03 GB). I eventually got sick of the command line transfer and ended up setting up and using a Linux Mint liveUSB to be able to visually check progress instead of constantly typing commands to check. This, I believe, was the cause of my major downfall. Once in Linux, I tried to mount the TB drive, and it wouldn't work. I did some research and used ntfsfix to get it to mount for me. After a little further fiddling with the SSD, I was able to see both and was able to copy files over to the HDD.
At this point, I decided I had done enough and was confident I wasn't going to lose anything important, and went back into the Windows install media to check things, saw the command prompt didn't seem to be reading free space on the HDD correctly, but didn't think much of it. As a last test before wiping, I tried pulling my video card with the machine off and booting it up. Shockingly, the machine booted up into Windows just fine. Unfortunately, Windows was seeing the HDD as only having a capacity of 785 gigs. I freaked out a bit because that certainly wasn't as it should be, did some looking around, and couldn't fix anything.
At this point, I contacted MS tech support and began to confuse the poor rep that I was connected to. He didn't have many suggestions beyond chkdsk and disk cleanup, but confirmed that bootrec.exe /fixmbr and its other commands could probably help. I believe that this is the second major mistake in all of this. This, unfortunately, did not fix my problem. Knowing that I had been using linux and was able to see the entire drive there, he suggested I use that, back it all up wherever I could, and then reformat the drive. I disconnected and went about his suggestion. Unfortunately, Linux was now seeing the same 785 gig drive that Windows was.
That is where I'm stuck at this point. Currently, Windows Explorer and any similar program sees the drive like this. Disk Management is seeing both simple partitions as healthy, but only the 785 gig partition is viewable by Windows. After some research, my best guess is that the LDM is busted, but I have no idea if that's actually the case, and I'm not seeing anything online to help if it is the case.
Is there anything I can do to repair this dynamic disk so I can avoid losing whatever has been put on that part of the drive? Thanks in advance.