Question Storage Spaces issue, need help. How to disassemble Storage Spaces without losing data. After upgrade HDD still same size and need format.

[AlanMattano]

Hello,

I'm in my first experience two-way mirror to protect my data
Storage Spaces in Windows 10.

I need a bigger drive than my 4TB so I purchase two 12TB (WD Element). I shock them into Storage Spaces and take out the two old 4TB

Now looking in Windows, my drive D: is still only 4TB

So is not using the full 12TB space. Nonsense
I wish to change the volume from 4TB to 12TB

I ask explaining the issue in Microsoft forum and turns out the volume hasn't been formatted.
Or at least is missing the "Change" option as it should be shown in this pic

NOW at this point, what I should do?

How to disassemble Storage Spaces without losing data?
I can't use the stupid "Delete" option because will delete all my info (I presume).
I can't use the "Format" option because will delete as well.
I do not have a second PC to take out and look at what's inside the HDD (all my memories)
I can't just move (copy past) almost 4TB of data because is ridiculous and I lose info like created data.
I still have my old two 4TB. In a pandemic, I can't go out. Only one computer. Also two 12TB.
Can I build a RAID1 to clone? How? Storage Spaces will allow that.

Question
How do I proceed at this point to get out? What is The best option?
Disassemble and rebuild, format, or if possible creating a new pool and merge or other?
How do I backup the data at this point? Do I need to use Powershell to change the volume?

Thanks

 

[AlanMattano]

Exaclly:
https://superuser.com/questions/1223744/disband-two-way-mirror-storage-pool/1649002#1649002

 

[USAFRet]

I will lose all the data.

Which is why I asked "where" the data is.

 

[AlanMattano]

I can't imaging to be more specific
Sorry, I do not understand, can you give an example of the answer?

 

[USAFRet]

I can't imaging to be more specific
Sorry, I do not understand, can you give an example of the answer?

You have 4 physical drives.
2x 4TB, that used to be a mirrored pool.
2x 12TB that are a mirrored pool, but are seen as only 4TB.
The data is currently living on the 2x 12TB pool.

Is this correct?

 

[SkyNetRising]

I will lose all the data.

Why haven't you still used 4TB E: drive, you created previously?

1. Move data from D: to E: or copy using robocopy preserving timestamps;​

2. Delete 4TB pool;​

3. Recreate pool as 12TB or set up 12TB mirrored volumes using dynamic disks (instructions in post #12);​

4. Move data back or copy using robocopy preserving timestamps.​

 

[AlanMattano]

Affirmative

4 physical drives.
2x 4TB, that are actually empty. One is connected as E:
2x 12TB that are a mirrored pool, but are seen as only 4TB. (D: )
The data is currently living on the 2x 12TB pool. (D: )

 

[USAFRet]

^^^^^
Personally, I would skip Step 3.
Individual 12TB drives.

 

[USAFRet]

Affirmative

4 physical drives.
2x 4TB, that are actually empty. One is connected as E:
2x 12TB that are a mirrored pool, but are seen as only 4TB. (D: )
The data is currently living on the 2x 12TB pool. (D: )

So copy the data to the E as mentioned above.

Fix the 12TB pool. (or do away with the Pool concept completely).
Then, copy the data to one of the 12TB.

 

[AlanMattano]

Why haven't you still used 4TB E: drive, you created previously?

1. Move data from D: to E: or copy using robocopy preserving timestamps;​

2. Delete 4TB pool;​

3. Recreate pool as 12TB;​

4. Move data back or copy using robocopy preserving timestamps.​

Yes,
But if "Move" fail is a problem
If move fail creates a disaster of files spread across both.
actually moving was creating this issue I'm trying to fix using robocopy.

So what I'm thinking is to fest make a copy to one 4TB HDD
and then a robocopy move to the other 4TB HDD

 

[USAFRet]

Don't "move"...Copy.
Be it one, or both (one at a time).

You're just trying to get the data OFF the borked up 2x 12TB, so you can restructure as desired.

 

[SkyNetRising]

Don't "move"...Copy.

Copy looses timestamp info.

 

[SkyNetRising]

Answer - "yes" to that dialog prompt and also mark "Do this for all current items".

Desktop.ini file holds custom appearance and behavior settings for specific folder. The file usually is hidden.

 

[USAFRet]

Copy looses timestamp info.

Even the robocopy?

 

[AlanMattano]

^^^^^
Personally, I would skip Step 3.
Individual 12TB drives.

Yes me too because in my experience is the first time using Storage Spaces and fails at some point.
Is buggy, a mess if you read the pdf and is not simple to go out from it.
I wish to use it but I'm not going to give it a second chance.
I need more valid reliability, not more problems.

 

[SkyNetRising]

I wish to use it but I'm not going to give it a second chance.
I need more reliability, not more problems.

Then use mirrored volumes with dynamic disks.

 

[AlanMattano]

Copy looses timestamp info.

And in Windows 10 I make an experiment and also Date modified!

 

[AlanMattano]

Then use mirrored volumes with dynamic disks.

Yes, I was using that before,
but I also need a backup of that
correct?

 

[USAFRet]

I need more valid reliability, not more problems.

A real backup routine would seem to do the trick.

 

[SkyNetRising]

Yes I was using that before, but I also need a backup of that correct?

Mirror protects agains single drive failure. It is not replacement for backup.

 

[AlanMattano]

Is incredible that in 2021 still the same problems as first Windows

 

[USAFRet]

Is incredible that in 2021 still the same problems as first Windows

What "problem"?

 

[AlanMattano]

Well DS before mention:

"simple task into a giant, messy nightmare? Robocopy is a very niche thing, for people with large datasets with particular parameters and unnecessary for people without those needs."

What a normal Windows user need is a Windows button that allows copy ("move" way) one drive to another. I mean the content, not the vulture.
Without losing date stamp and user time. A "move" that does not delete the origin.

Robocopy is to complex for the average user. I'm still reading the best option and it does not include a Windows UI.

 

[USAFRet]

"most people" don't really care about the Creation date. Just the content.

Or that metadata is encapsulated in some other form.
EXIF for images, for isntance.

 

[AlanMattano]

They care but they can live with it. They do not know how to report it as a bug (and do not have the time).
And Windows developers do not care too much about fixing very old problems (example link),
They just make new features but new features with bugs are not features at all.
Yes, create a "cloud" community around that bug...
Windows thinks is an API when in reality is the data container of the memorys of all humanity.
We care about them.

 

[AlanMattano]

Even the robocopy?

What I read is that preserves it. I'm making a test to double-check if is still true.