Importing Windows 8.1 Storage Spaces into Windows 10

[Jorkand]

Is anyone having issues with Windows 10 not recognizing the storage spaces from Windows 8.1 Reinstalling from 7 to 8 to 8.1 gave me no issues but this time around I build a uefi/gpt installation (the only difference other than it being Windows 10) and my 3 drive storage space isn't recognized. Any idea how I can fix that? Reinstalling without uefi is also a possibility but I would like to try uefi/gpt install for once!

 

Thanks!

[The_Observer]

mmm I'm wondering..... is this a preview version or final version??

[T3X4S]

Its an alpha build, a tech preview.  It will/does have issues.

[FiB3R]

Pretty sure the guy knows it's a preview, ffs.

He's asking for others experience with storage spaces, and if anybody knows of a fix.

Edited October 13, 2014 by zhangm

[T3X4S]

There is a good chance its not ready to be fixed.  Whatever errors are out there - it will be fixed IN THE FUTURE BUILDS......BY MICROSOFT.

Edited October 13, 2014 by zhangm

[Neu B]

There is a good chance its not ready to be fixed.  Whatever errors are out there - it will be fixed IN THE FUTURE BUILDS......BY MICROSOFT.

There's nothing to get, genius! Why didn't you just tell him what you just told me. That statement would probably help Jorkand a lot, don't you think?

[Jorkand]

Sounds like other people haven't run into the same issue. I am going to try going back to a bios install and see if it fixes things. Will post back here.

[RoyalStandard]

Hi - I didn't have a problem with Storage Spaces on Win10 Preview (other than them being assigned different drive letters), but I did have a problem with Win10 Server Preview ...

My Win2012 R2 Pool & Drives/Storage Spaces all appeared offline to Win10 Server. I imported them, they worked Ok, but they then went offline after the next reboot - I tried all sorts of PowerShell Stuff, but couldn't make them survive a reboot.

 

I then tried creating a new (Win10) Storage Space and found that that stayed mounted after a reboot, so
I created a bunch of new Storage Spaces with the same attributes as my old Storage Spaces, and then moved everything across from the old Storage Spaces to the new Storage Spaces, then deleted the old Storage Spaces - a pain, but my storage Spaces are all working Ok now 

[FiB3R]

/snip

 ^ this is how you are supposed to behave.

[Jorkand]

I spent some time this morning debugging the issue and I think people would like to know. My storage pool was non-parity with 3 disks. On Windows 10 even after reinstalling without gpt I couldn't get the pool to be visible. Infact in device manager I can't even populate the volume for the disks. Reinstalling windows 8 let me get access to the pool again and I am going to try to do an upgrade and see if that allows the pool to transfer over. Eventually I'll do the same as you RoyalStandard and recreate the pool but I wanted to figure out why the discrepancy was happening. 

 

Now to the question of forums:

 

 

Its an alpha build, a tech preview.  It will/does have issues.

 

 

I understand that and this wasn't an attempted whigne, but rather a supportive debugging session. Now the community knows something interesting, microsoft knows something interesting. This is how the tech preview is supposed to work. 

[T3X4S]

There's nothing to get, genius! Why didn't you just tell him what you just told me. That statement would probably help Jorkand a lot, don't you think?

Shouldnt have to state the obvious.

[Neu B]

Shouldnt have to state the obvious.

Excuse ME Mr. Perfect!! :rolleyes:

[Jorkand]

To put in a final update. It must have been something to do with my configuration but I could never get my old storage space to show on Windows 10. Eventually I installed Win 8.1, backed up the data and deleted the pool. Reinstalled the enterprise preview and created a new pool.

[J_R_G]

If you're going to server, you have to activate storage spaces in server manager. Then there is a command in powershell to mount it at every boot: "get-virtualdisk|set-virtualdisk -ismanualattach $false". Or maybe that wasn't the problem and MS changed something so they don't currently import, don't have my storage spaces array any more so I didn't have to deal with this.