0

I'm attempting to set up a software RAID1 of 2*8TB drives and after encountering the incredibly slow syncing of Windows' mirroring system (both drives are empty) in disk management I looked around and found Storage Spaces.

They seem great, especially when combined with ReFS for data security, however my attempts are failing at creating the storage space with the 8TB drives. My 2TB drive works fine but I can not add my 8TB drives.

Attached some images that might be of help.

Disk Management

Storage Space Creation Attempt

Hope someone can point me in the right direction, can't find any information as to why this shouldn't work.

Kind regards.

EDIT: Adding nicely formatted output of Get-PhysicalDisk

PS C:\WINDOWS\system32> Get-PhysicalDisk | ft FriendlyName, UniqueId -auto

FriendlyName         UniqueId
------------         --------
WDC WD20EFRX-68AX9N0 {4d4b3dd5-ff79-b54d-0b87-0100a3693c37}
INTEL SSDSC2BW120A4  {4d66a2c5-77f9-9346-919a-db8a23713050}
WDC WD20EFRX-68AX9N0 {b75e5e0c-0cf9-b454-aa9a-d4751b92821f}
WDC WD80EFZX-68UW8N0 {c57323a1-8798-e4c2-993a-9d43a88b1831}
WDC WD80EFZX-68UW8N0 {dbabd8d1-6444-e528-9d87-fe2ef46091fb}
Improve this question
9
  • What settings on the storage pool did you select?
    – Ramhound
    Commented Oct 16, 2016 at 9:01
  • There's no settings to be chosen; Open storage space manager -> Create new storage pool (none made before) -> UAC prompt -> Shows my unassigned HDDs -> The error you see.
    – roger.siegenthaler
    Commented Oct 16, 2016 at 12:03
  • I must warn you: I’ve experienced ReFS fail in strange ways. Because it’s so awesome, there are no official recovery tools available. A reboot solved it, but it almost gave me a heart attack. Do not use ReFS.
    – Daniel B
    Commented Oct 16, 2016 at 15:29
  • Execute the following command in PowerShell and provide the output: Get-PhysicalDisk | ft FriendlyName, UniqueId -auto. Also, what controller are the disks connected to?
    – Daniel B
    Commented Oct 16, 2016 at 15:32
  • Ok, I wasn't set on ReFS and after reading into it more I'll wait until Server 2016 gets released with (probably) an updated version that'll trickle down to Windows Pro as well. FriendlyName UniqueId ------------ -------- WDC WD20EFRX-68AX9N0 {4d4b3dd5-ff79-b54d-0b87-0100a3693c37} INTEL SSDSC2BW120A4 {4d66a2c5-77f9-9346-919a-db8a23713050} WDC WD20EFRX-68AX9N0 {b75e5e0c-0cf9-b454-aa9a-d4751b92821f} WDC WD80EFZX-68UW8N0 {c57323a1-8798-e4c2-993a-9d43a88b1831} WDC WD80EFZX-68UW8N0 {dbabd8d1-6444-e528-9d87-fe2ef46091fb}
    – roger.siegenthaler
    Commented Oct 16, 2016 at 15:39

1 Answer 1

Reset to default
0

So after playing around with VHDs and finding out it works perfectly fine with 2*8TB VHDs, I proceeded to add my two physical 8TB drives to the storage space containing the 2 VHDs and that worked.

After I decided to try my luck and after removing the VHDs and the storage space tried only my two 8TB WD HDDs and lo and behold, it worked without a problem.

Thanks for the help guys but it seems it just fixed itself somehow.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .