restore Striped disks after accidentally setting as GPT

[arasqueal]

my home PC has a SSD for win10, and two 2 tb hdds for storage.

I've been regretting making separate partitions on my ssd for data and for OS, but havn't been able to merge them without going through the process of backing up the data and deleting the data partition.

Today i tried to use EaseUS to merge partitions without losing data. when I opened up windows Disk Management to see if my EaseUS changes went through Disk management threw me a message saying something like: "disks have changed since last scanned, how would you like these disks to be read? MBR or GPT?"


I selected GPT, and now my striped hdds are no longer reading: see image
https://imgur.com/a/eTm5K

summary: I think my computer is no longer reading the two disks as paired dynamic. Is there a way to tell it to revert


things I've tried:

restarting computer
unplugging sata cables
changing RAID settings in bios (all this did is made the ssd unbootable)
manually putting the drives online
chkdisk on all drives and volumes
right click-> reactivate in disk management
messing with EaseUS in attempts to get the same message as before
restore points; i have none

 

[SkyNetRising]

So you reinitialized Disk 2, right?
And Disk 1 - is it in GPT or MBR partitioning scheme?

Not sure, if that can be recovered.
Try R-Tools R-Studio. It supposedly has support for windows LDM recovery.

 

[arasqueal]

honestly i'm not sure- was partialyl hoping someone would know exactly what I must have done wrong

 

[USAFRet]

ooo..so many things wrong with that configuration.

1. 33GB partition for the OS? Much too small.
2. No actual backup of all your data
3. The 2 x HDD in a striped RAID? With no backup?

 

[arasqueal]

yes indeed! the 32 gb for os was what i was trying to initially solve. The striped raid i did because none of the data on there is important, which is lucky in this case it's looking like

 

[USAFRet]

yes indeed! the 32 gb for os was what i was trying to initially solve. The striped raid i did because none of the data on there is important, which is lucky in this case it's looking like

At this point, I'd just start over.
Clean install on the SSD, with 1 single partition for the whole 250GB space.
HDD's just as individual drives and drive letters.

And then create and implement a strong backup solution.

 

[ArtPog]

1. First of all, IT IS ALWAYS WISE FOR A USER THAT BEFORE UNDERTAKING MAJOR CONFIGURATION CHANGES IN THE SYSTEM'S DRIVE(S) EITHER USING A WINDOWS BUILT-IN UTILITY OR A THIRD-PARTY PARTITION MANAGEMENT PROGRAM, THAT THE USER CLONE THE CONTENTS OF HIS/HER EXISTING DRIVE(S) TO ANOTHER DRIVE, SO THAT IN THE EVENT THE OPERATION GOES AWRY (NOT AN UNCOMMON EVENT!) THE USER HAS THE WHEREWITHAL TO RETURN THE SYSTEM TO ITS ORIGINAL STATE. CAPICHE?

2. Second of all, we're assuming your present system, i.e., the 250 GB (SSD) boot drive boots & properly functions. If that is NOT the case, then stop right here.

3. It's difficult to determine why you ran into problems you related using the EaseUS partition management program. It's ordinarily a pretty cut & dried process merging adjacent partitions. Did you repeat the operation?

2. You're reasonably sure you've properly used the program? Your boot drive is apparently GPT-partitioned, but that should pose no problem at all. I would give the EaseUS program another shot.

3. Following the successful merging of the two partitions (C & D), it's a simple matter to utilize Disk Management to extend the C partition to encompass that 48+GB of unallocated disk-space remaining on that 250 GB boot drive.

4. After you've accomplished the preceding it will be time to take care of that ghastly setup of your two 2 TB drives. Fortunately there's no data on either of those drives, thank goodness. I would strongly recommend you employ the Windows built-in DiskPart utility to "clean" both of those drives. After they've been cleaned, initialize each to the GPT-partitioning scheme. Are you with me?
(BTW, don't forget to create Basic Disks for those 2 TB drives; you DO NOT WANT TO CREATE DYNAMIC DISKS!)

If you don't know how to use DiskPart I'll walk you through it. It's a simple procedure. But you should do a Google search on using DiskPart; it's a valuable utility and should be in the "toolbox" of every PC user.