How storage spaces mirror onto multiple storage pool drives...

Tricky question to pose..
I currently have 2 * 2TB drives in a storage pool. I have a 2 TB storage space assigned to this pool (lets call them A and B). I have 2TB of mirrored storage across 4TB of drives. All is well...
If I add a third 2TB drive "C" to the storage pool, how will 2-way mirroring work now? My hope is that it will evenly mirror across each drive in the pool ( 1TB mirrored across A + B, 1TB across A+ C and 1TB across B + C) giving me effectively
3TB of mirrored storage.
If it does work as I hope, does the server rebalance the mirroring? Say I have already used 1.8GB of storage by the time I add in the 3rd drive, there is only 0.2GB on each of the morrored drives available. When I add in the 3rd drive, if the
server does not re-allocate, then I would only gain 0.4GB of storage (0.2GB A+C, 0.2GB B+C) leaving 1.4GB unusable.
If not as I hoped, how do I make use of the 3rd drive? I assume the 3rd drive is useless in that pool unless I do 3-way mirroring or I add another 4th drive?
Thanks, Mark.

Similar Messages

How to design Storage Spaces with a large number of drives

I am wondering how one might go about designing a storage space for a large number of drives. Specifically I've got 45 x 4TB drives. As i am not extremely familiar with storage spaces, i'm a bit confused as to how I should go about designing this. Here is
how i would do it in hardware raid and i'd like to know how to best match this setup in Storage Spaces. I've been burned twice now by poorly designed storage spaces and i don't want to get burned again. I want to make sure if a drive fails, i'm able to properly
replace it without SS tossing it's cookies.
In the hardware raid world, i would divide these 45 x 4TB drives into three separate 15 disk Raid 6's. (Thus losing 6 drives to parity) Each raid 6 would show up as a separate volume/drive to the parent
OS. If any disk failed in any of the three raids, i would simply pull it out and put a new disk back in and the raid would rebuild itself.
Here is my best guess for storage spaces. I would create 3 separate storage pools each containing 15 disks. I would then create a separate
Dual Parity Virtual Disk for each pool. (Also losing 6 drives to parity) Each virtual disk would appear as a separate volume/disk
to the parent OS. Did i miss anything?
Additionally, is there any benefit to breaking up my 45 disks into 3 separate pools? Would it be better to create one giant pool with all 45 disks and then create 3 (or however many) virtual disks on top of that one pool?

I am wondering how one might go about designing a storage space for a large number of drives. Specifically I've got 45 x 4TB drives. As i am not extremely familiar with storage spaces, i'm a bit confused as to how I should go about designing this. Here is
how i would do it in hardware raid and i'd like to know how to best match this setup in Storage Spaces. I've been burned twice now by poorly designed storage spaces and i don't want to get burned again. I want to make sure if a drive fails, i'm able to properly
replace it without SS tossing it's cookies.
In the hardware raid world, i would divide these 45 x 4TB drives into three separate 15 disk Raid 6's. (Thus losing 6 drives to parity) Each raid 6 would show up as a separate volume/drive to the parent
OS. If any disk failed in any of the three raids, i would simply pull it out and put a new disk back in and the raid would rebuild itself.
Here is my best guess for storage spaces. I would create 3 separate storage pools each containing 15 disks. I would then create a separate
Dual Parity Virtual Disk for each pool. (Also losing 6 drives to parity) Each virtual disk would appear as a separate volume/disk
to the parent OS. Did i miss anything?
Additionally, is there any benefit to breaking up my 45 disks into 3 separate pools? Would it be better to create one giant pool with all 45 disks and then create 3 (or however many) virtual disks on top of that one pool?
1) Try to avoid parity and esp. double parity RAIDs with a typical VM workload. It's dominated by small reads (OK) and small writes (not OK as whole parity stripe gets updated with any "ready-modify-write" sequence). As a result writes would be DOG slow.
Another nasty parity RAID characteristic is very long rebuild times... It's pretty easy to get second (third with double parity) drive failure during re-build process and that would render the whole RAID set useless. Solution would be to use RAID10. Much safer,
faster to work and rebuild compared to RAID5/6 but wastes half of raw capacity...
2) Creating "islands" of storage is an extremely effective way of stealing IOPS away from your config. Typical modern RAID set would run out of IOPS long before running out of capacity so unless you're planning to have a file dump of an ice cold data or
CCTV storage you'll absolutely need all IOPS from all spindles @ the same time. This again means One Big RAID10, OBR10.
Hope this helped a bit :) Good luck!
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Why do we not receive 5 gb of free cloud storage space for the multiple Apple devices my wife and I have purchased?

Why do we not receive 5 gb of free cloud storage space for the multiple Apple devices my wife and I have purchased? Seems only fair.

logical. fair. I can understand the confusion in policy as another fine cloud service - DropBox - has a different model for increases in free storage amounts for one account = evangelism. As many policies as there are services probably.
cya 'round o' kilted one
CCC

HT4859 does icloud mail take up storage space on my icloud storage on my ipad?

does icloud mail take up storage space on my icloud storage for my ipad?

Welcome to the Apple community.
Yes.

How do I download onto a portable zip drive?

How do I download onto a portable zip drive?

download to a portable zip drive? as in the slightly thicker floppy-looking disks?

Storage Type Search for Multiple Storage Types

Hello experts.
I have an issue that I cannot seem to resolve.
Background
- We are using kanban strategy 0006 in order to move materials from Plant A to Plant B. Plant A is warehouse-managed but Plant B is not.
- Within Plant A we have one wm-managed Storage Location with many Storage Types.
- Within Plant B we have two Storage Locations ( each one representing a separate, physical building ).
- A majority of the kanban materials in use only have one Supply Area assigned to them. However we have approximately 15 materials that have multiple Supply Areas assigned to them. This is because these materials are common parts across two different Storage Locations in Plant B. As a result, they also have two different Storage Types assigned to them in Plant A ( the source of the material ).
Problem
Because we have common materials in two different Storage Types, the Storage Type Search (defined in OMLY) does not always return the correct Storage Type for the Stock Removal Strategy.
I understand that this occurs because the Storage Type Search is defined based upon the Warehouse Number, Removal/Putaway Indicator and the Storage Strategy. Therefore both Storage Types will use the same Storage Type Search when determining the Destination Storage Type for the transfer order.
FYI, here's an example :
- Material 123ABC is defined in Plant A, Storage Location SL00, Warehouse WH1 with Storage Types ST1 and ST2.
- Material 123ABC is defined in Plant B, Storage Locations SL01 and SL02.
- Material 123ABC has Supply Area SA1 for Storage Location SL01 and Supply Area SA2 for Storage Location SL02 defined for kanban.
- Material 123ABC has Stock Removal Strategy 003 assigned in the WM1 view for Plant A, Storage Location SL00 and Warehouse WH1.
- The Storage Type Search sequence defined for Stock Removal Strategy 003 is Storage Location SL01 then Storage Location SL02.
- When I execute kanban for Material 123ABC for Supply Area SA2, the Destination Storage Type for the transfer order should be ST2. However because the Storage Type Search is based upon the Warehouse (and not the Storage Type level), the Destination Storage Type for the transfer order is ST1 because it is the first item in the Storage Type Search sequence.
So my question : does anybody know how I can resolve this issue? We don't want to adjust our master data for these materials or supply areas. Is there a USER_EXIT that we can implement that will account for this condition?

Hi Mathew,
Based on the storage location indicator you can maintan different storage types for picking and putaway. I think your scnario willl be addressed using this indicator.Please explore this option before going for User exits.

How do you find out how much space is left on your hard drive?

How do i find out how much space i have left on my computer?

Disk space can now be seen in the "About This Mac" window. Click on the Apple icon, select About This Mac then click More Info... There you will find a Storage tab that will list all connected drives in a bar graph similar to how storage is displayed in iTunes for iOS devices.

I want to find out how much space on my macbook pro hard drive is from iphoto pics

i have a macbook pro (2008) w/186 g hard drive, w/OS 10.5.8. I want to find out how much (% or # of gigabytes) of the hard drive is pics from iPhoto. does it sort by type (e.g., apps) ?

Click on Pictures in the Finder’s sidebar, select the iPhoto library, and choose Get Info from the File menu. If you’re using multiple libraries, you’ll need to do this on each one.
(108944)

[SOLVED] OSCDIMG Tool Does Not Work on Windows 10? ReadFile() fails with error code 87. (The parameter is incorrect) on ReFS Storage Space Mirror

Hello,
What could be the reason of OSCDIMG premastering tool not working in Windows 10?
I'm trying to rebuild ISO from the admin setup point and having problems with OSCDIMG failing to read files from the master folder:
E:\Images>bin\oscdimg.exe -bootdata:2#p0,e,b"D:\ISOFOLDER\boot\etfsboot.com"#pEF,e,b"D:\ISOFOLDER\efi\Microsoft\boot\efisys.bin" -o -h -m -u2 -udfver102 -lwinsetup D:\ISOFOLDER test.iso
OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility
Copyright (C) Microsoft, 1993-2012. All rights reserved.
Licensed only for producing Microsoft authorized content.
Scanning source tree (500 files in 15 directories)
Scanning source tree complete (950 files in 95 directories)
Computing directory information complete
Image file is 3591864320 bytes (before optimization)
Writing 950 files in 95 directories to test.iso
0% complete
ReadFile failed (\\?\E:\Images\ISOFOLDER\autorun.inf, off=0 len=800 status=103)
Error 87: The parameter is incorrect.
Thank you.
Well this is the world we live in And these are the hands we're given...

Figured it myself.
For some reason, the tool does NOT support source locations on ReFS formatted drives. Move the D:\ISOFOLDER location to NTFS formatted drive, and the tool works flawless:
E:\Images>bin\oscdimg.exe -bootdata:2#p0,e,b"D:\ISOFOLDER\boot\etfsboot.com"#pEF,e,b"D:\ISOFOLDER\efi\Microsoft\boot\efisys.bin" -o -h -m -u2 -udfver102 -lwinsetup D:\ISOFOLDER D:\TEMP\test.iso
OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility
Copyright (C) Microsoft, 1993-2012. All rights reserved.
Licensed only for producing Microsoft authorized content.
Scanning source tree (500 files in 15 directories)
Scanning source tree complete (950 files in 95 directories)
Computing directory information complete
Image file is 3591864320 bytes (before optimization)
Writing 950 files in 95 directories to D:\TEMP\test.iso
100% complete
Storage optimization saved 45 files, 16310272 bytes (1% of image)
After optimization, image file is 3577761792 bytes
Space saved because of embedding, sparseness or optimization = 16310272
Done
Well this is the world we live in And these are the hands we're given...

How to backup iphotos onto an external hard drive....

I have been reading through the questions on here to figure out how to backup and save my iphotos externally and i am hitting numerous brick walls...
I have tried to use the time machine but my hard drive has photos and documents on it and i do not want to wipe it to install it as my perferd divice to use in time machine.
I have tried numerous other options and i am having no luck whatsoever.
Please help!!!!!

It doesn't even let me do that. I can't copy it at all over at all. I have 1 terabite of memory available on my external hard drive.
I have also tried to individually export photos and that also comes up with an error. I have had the computer 4 months and kept up to date with all updates so im unsure as to why that is not working.
That is like "my car won't start - Why not?
We need information about what is happening, not happening, what has recently changes, error messages
Saying "it does not work" gives us nothing to help with
LN

Storage spaces + Hyper-V with multiple 1GBe nics for storage?

Hi guys!
So I just got my private cloud hardware. I actually put in the order before summer, but due to firmware and certification issues on my desired SuperMicro JBODs delivery was seriously delayed. So much that I've completely forgotten my networking ideas. I
need help/verification. Or at least a URL - most described setups are 10 GBe nowadays... Or even a "not gonna work" :-)
My setup is supposed to be a 3 JBOD, 2 head node storage spaces/sfos cluster providing storage to a 4 node Hyper-V cluster. I didn't have a budget for a 10 GBe setup, but got a great price on a lot of 1 GBe nics. After allocating management, Hyper-V, etc
I have 3x 1 GBe ports left on all Hyper-V and Storage servers.
I think my original plan was to create three subnets and add one nic from each server. And then I guess I've imagined some kind of SMB3 magic discovering these paths between Hyper-V and storage and just aggregating bandwitdh and providing fault tolerance
by sprinkling fairy dust. Must have been the heat...
So now I'm "replanning" and I realize that I'm going to create a failover cluster at the storage level providing a cluster name and IP. I'm thinking the management subnet where domain info resides is appropriate, but then what about the other three
subnets? I don't want to flood my management subnet with storage traffic, but do want bandwidth and resilience. Did I make a design error, and how do I make the best of the situation?
Disclaimer: My previous experience on virtualization clusters is ISCSI SAN and 2008 R2 Hyper-V clusters. Storage Spaces is completely new to me :-)
And due to overlapping technologies I struggled a bit on placing this thread. Hope I got it right

Hello,
i did not understand how many NICs you have in each Host. Hyper-V Cluster with 1 GBe NICs work as long as you know that it is not 10 GBe.
In this article is the complete Hyper-V Cluster design in checklist form. I think you should work with this list for some further ideas:
http://blogs.technet.com/b/askpfeplat/archive/2013/03/10/windows-server-2012-hyper-v-best-practices-in-easy-checklist-form.aspx
Sorry that i cant give a better answer, but i lack information about about your environment.
Regards,
Thomas
Thomas Hanrath [MCT | Regional Lead Germany] |
http://www.hanrath.de
Microsoft Learning Blog |
http://blog.microsoftlearning.de
MCSE | Private Cloud

Storage Space Size vs Pool Size

Hi All:
I just finished installing WS2012R2E and getting all my clients connected, transferring them from my aging WHS V1
All seems to be working well but I'm scratching my head on the fact that the Storage Pool reports 3.63Tb of storage (I have 2 x 2Tb drives) but the storage space reports 16Tb.... I tried changing the "Storage Space Size (Maximum)" to
something closer to the actual storage pool capacity but no number seems acceptable to the field.
I get it (sort of) that the storage space is different from the pool, but it seems to me that if the dashboard storage tab reports the storage space with a Capacity of 16Tb it does not give a clear picture of my storage situation.
In addition to that quirk, the dashboard storage space window, hard drives tab reports 1Tb of used space but when I click into "Manage Storage Spaces" that window reports that I'm using 2.16Tb of the 3.63Tb - ?!
I've tried searching this with no joy - maybe I just haven't stumbled across the right doc yet... Can some one enlighten or point me to a detailed description of they way this is supposed to work?
Thanks!

Hi,
It seems that you directly click “Create a storage space” in dashboard. This wizard helps you create a default storage space on the server. The new storage space can tolerate on drive failure, and its size can group up to 16 TB.
You can click “Manage Storage Spaces” in dashboard then click “create a new pool and storage space” to specific the maximum size of the storage space.
Manage Server Storage in Windows Server Essentials
http://technet.microsoft.com/en-us/library/dn550731.aspx
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Storage spaces can only use whole drives

One of the features that I was really interested in with WS2012E is storage spaces as it replaces the old driver extender of WHS v1. Having now installed WS2012E onto my WHS2011 box I am bit staggered to find that it can only use whole drives. My box came
with 2 * 2Tb drives, the first partitioned as boot, then a 60G of OS followed by the rest allocated as storage. I have successfully created a Storage space pool of the second drive but cannot find any way to add the remaining storage from the large partition
on the other drive into the pool. As the UI just shows me drives rather than partitions, I am bit challenged. I thought that storage spaces was meant to be flexible about adding drives just like the old drive extender. Even add on technolgies like DriveBender
for WHS2011 allows for a storage space to be made up from this type of set up. So we seem to be going backwards.
Plus when creating the drive pool it defaulted on a 2Tb drive to a 2Gb size! How useful is that? As soon as I started copying data to the drive it ran out of space. I then had to go in and expand it.

I note that you did this with Windows Server 2012 Essentials. I cannot seem to do this with Windows 2012 Standard. I have two 500 GB disks and 40GB of the first disk, PhysicalDisk0 is partitioned for the OS. Nothing I do makes PhysicalDisk0
show up in the Storage Pool area of Server Manager - all I can see is PhysicalDisk1. (Refer to 'Physical Disks' in the bottom right corner of the previous poster's first screen shot above. I can only see 'PhysicalDisk1', not 'PhysicalDisk0'.) If
I click 'Disks' just under 'Volumes' in the same screenshot above, I can see PhysicalDisk0, and it shows 466 GB capacity, 423 GB unallocated. PhysicalDisk1 shows 466 GB capacity, 466 GB unallocated. My intent was to mirror the remaining 423 GB
on PhysicalDisk0 with 423 GB on PhysicalDisk1. I would then allocate the leftover 43 GB on PhysicalDisk1 as a 'scratch' disk. I have tried leaving everything unallocated and have tried all variations of creating volumes and virtual disks, but nothing
I do makes a difference. I found other threads related to this issue which indicated there was a flaw in the 2012 GUI and that this process could be done via Powershell. However, there seems to be a mix of Windows 8 and Windows 2012 in these threads
and, apparently the Powershell commands I've found apply to 8 and not 2012, as I get invalid command errors when I try to use them.
Can anybody tell me how to mirror the unallocated portion of the primary disk PhysicalDisk0 (which has a partition for the OS) with a same-sized portion of PhysicalDisk1 with Windows Server 2012? Thanks!

First cluster - Server 2012 r2 - storage spaces issues

Hi Everyone
   We just purchased two new servers (Lenovo RD640's) and an external SAS JBOD enclosure (the Lenovo SA120), and we would like to set up a 2012 r2 failover cluster with clustered storage spaces as the shared storage. Currently they are
on their own domain with the virtual active directory server residing locally on one of the servers.
   Preface: I've created and destroyed the cluster and storage spaces multiple times trying to solve this issue, so I don't know if I may have "leftovers" from those attempts now causing issues for me.
I can create the cluster, and it passes validation, and can create a clustered storage pool, but every time I try to create a virtual disk (either through the Failover cluster manager, the server manager, or powershell), it won't attach. If
I try to manually attach it I get the message: "Error attaching or detaching virtual disk: Failed to attach virtual disk to <node name>. Access denied"
Finally (and I don't know if this is related or not), when in storage spaces on the server manager, there is a gold banner at the top that says "Incomplete communication with cluster <cluster name>. The following cluster nodes or clustered roles
might be offline or have connectivity issues: <cluster name>"
I'm logged in with full domain administrator credentials, and have been running my head against this wall for a few days now. Any help would be appreciated!

Thanks for your responses. Here is what I have to report:
When I destroy the cluster, and create the storage spaces on just one of the two servers (with the other server powered down), I'm able to create the storage pool - using all the HDDs and SSDs - and virtual disks (both tiered and non-tiered) without issue.
As soon as I create the cluster again, the virtual disks become "detached", and I'm back to the situation described initially.
@Apamnapat, here's the output of the powershell commandlets you suggested:
PS C:\Windows\system32> get-storagepool | fl *
Usage                             : Other
OperationalStatus                 : OK
HealthStatus                      : Healthy
ProvisioningTypeDefault           : Fixed
SupportedProvisioningTypes        : {Thin, Fixed}
ReadOnlyReason                    : None
RepairPolicy                      : Parallel
RetireMissingPhysicalDisks        : Auto
WriteCacheSizeDefault             : Auto
FileSystem                        : Unknown
Version                           : Windows Server 2012 R2
ObjectId                          : {1}\\CBC116\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StoragePool.ObjectId
                                    ="{1cca13ee-d45c-11e3-80b5-806e6f6e6963}:SP:{1cca13ef-d45c-11e3-80b5-806e6f6e6963}"
PassThroughClass                  :
PassThroughIds                    :
PassThroughNamespace              :
PassThroughServer                 :
UniqueId                          : {1cca13ef-d45c-11e3-80b5-806e6f6e6963}
AllocatedSize                     : 24962849046528
ClearOnDeallocate                 : False
EnclosureAwareDefault             : False
FriendlyName                      : Primordial
IsClustered                       : False
IsPowerProtected                  : False
IsPrimordial                      : True
IsReadOnly                        : False
LogicalSectorSize                 :
Name                              :
OtherOperationalStatusDescription :
OtherUsageDescription             :
PhysicalSectorSize                :
ResiliencySettingNameDefault      : Mirror
Size                              : 25264456597504
SupportsDeduplication             : False
ThinProvisioningAlertThresholds   : {70}
WriteCacheSizeMax                 : 107374182400
WriteCacheSizeMin                 : 0
PSComputerName                    :
CimClass                          : ROOT/Microsoft/Windows/Storage:MSFT_StoragePool
CimInstanceProperties             : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties
Usage                             : Other
OperationalStatus                 : OK
HealthStatus                      : Healthy
ProvisioningTypeDefault           : Fixed
SupportedProvisioningTypes        : Fixed
ReadOnlyReason                    : None
RepairPolicy                      : Parallel
RetireMissingPhysicalDisks        : Auto
WriteCacheSizeDefault             : Auto
FileSystem                        : Unknown
Version                           : Windows Server 2012 R2
ObjectId                          : {1}\\CBC116\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StoragePool.ObjectId
                                    ="{3407c278-597d-4d38-b877-b2eff1e8a936}:SP:{05303524-5f93-4829-b84a-44955d1eb28e}"
PassThroughClass                  :
PassThroughIds                    :
PassThroughNamespace              :
PassThroughServer                 :
UniqueId                          : {05303524-5f93-4829-b84a-44955d1eb28e}
AllocatedSize                     : 24962849046528
ClearOnDeallocate                 : False
EnclosureAwareDefault             : False
FriendlyName                      : Primordial
IsClustered                       : True
IsPowerProtected                  : False
IsPrimordial                      : True
IsReadOnly                        : False
LogicalSectorSize                 :
Name                              :
OtherOperationalStatusDescription :
OtherUsageDescription             :
PhysicalSectorSize                :
ResiliencySettingNameDefault      : Mirror
Size                              : 25264456597504
SupportsDeduplication             : False
ThinProvisioningAlertThresholds   : {70}
WriteCacheSizeMax                 : 107374182400
WriteCacheSizeMin                 : 0
PSComputerName                    :
CimClass                          : ROOT/Microsoft/Windows/Storage:MSFT_StoragePool
CimInstanceProperties             : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties
Usage                             : Other
OperationalStatus                 : OK
HealthStatus                      : Healthy
ProvisioningTypeDefault           : Fixed
SupportedProvisioningTypes        : Fixed
ReadOnlyReason                    : None
RepairPolicy                      : Parallel
RetireMissingPhysicalDisks        : Auto
WriteCacheSizeDefault             : Auto
FileSystem                        : Unknown
Version                           : Windows Server 2012 R2
ObjectId                          : {1}\\CBC116\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StoragePool.ObjectId
                                    ="{3407c278-597d-4d38-b877-b2eff1e8a936}:SP:{48e0189b-db8c-11e3-80d3-f80f41fcd134}"
PassThroughClass                  :
PassThroughIds                    :
PassThroughNamespace              :
PassThroughServer                 :
UniqueId                          : {48e0189b-db8c-11e3-80d3-f80f41fcd134}
AllocatedSize                     : 17179869184
ClearOnDeallocate                 : False
EnclosureAwareDefault             : False
FriendlyName                      : Storage Pool
IsClustered                       : True
IsPowerProtected                  : False
IsPrimordial                      : False
IsReadOnly                        : False
LogicalSectorSize                 : 512
Name                              :
OtherOperationalStatusDescription :
OtherUsageDescription             :
PhysicalSectorSize                : 4096
ResiliencySettingNameDefault      : Mirror
Size                              : 24951612506112
SupportsDeduplication             : False
ThinProvisioningAlertThresholds   : {70}
WriteCacheSizeMax                 : 107374182400
WriteCacheSizeMin                 : 0
PSComputerName                    :
CimClass                          : ROOT/Microsoft/Windows/Storage:MSFT_StoragePool
CimInstanceProperties             : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties
PS C:\Windows\system32> get-virtualdisk | fl *
Usage                             : Other
NameFormat                        :
OperationalStatus                 : Detached
HealthStatus                      : Unknown
ProvisioningType                  : Fixed
ParityLayout                      : Rotated Parity
Access                            : Read/Write
UniqueIdFormat                    : Vendor Specific
DetachedReason                    : By Policy
WriteCacheSize                    : 1073741824
ObjectId                          : {1}\\CBC116\root/Microsoft/Windows/Storage/Providers_v2\SPACES_VirtualDisk.ObjectId
                                    ="{3407c278-597d-4d38-b877-b2eff1e8a936}:VD:{48e0189b-db8c-11e3-80d3-f80f41fcd134}{
                                    c1894936-db95-11e3-80d5-f80f41fcd134}"
PassThroughClass                  :
PassThroughIds                    :
PassThroughNamespace              :
PassThroughServer                 :
UniqueId                          : 364989C195DBE31180D5F80F41FCD134
AllocatedSize                     : 7516192768
FootprintOnPool                   : 8589934592
FriendlyName                      : Disk Witness
Interleave                        : 262144
IsDeduplicationEnabled            : False
IsEnclosureAware                  : False
IsManualAttach                    : True
IsSnapshot                        : False
LogicalSectorSize                 : 512
Name                              :
NumberOfAvailableCopies           :
NumberOfColumns                   : 8
NumberOfDataCopies                : 1
OtherOperationalStatusDescription :
OtherUsageDescription             :
PhysicalDiskRedundancy            : 1
PhysicalSectorSize                : 4096
RequestNoSinglePointOfFailure     : False
ResiliencySettingName             : Parity
Size                              : 7516192768
UniqueIdFormatDescription         :
PSComputerName                    :
CimClass                          : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDisk
CimInstanceProperties             : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties

Storage Space - Inaccessible, reconnect drives

Hi
My 2 HDD Mirror Storage Space is no longer accessible. I cannot see it in explorer, and under Storage Space Manager it says Inaccessible, Reconnect drives. Both disks under Physical Disks are displaying as OK, so I'm really scratching my head.
The results from
Get-PhysicalDisk | fl *
Get-StoragePool | fl *
Get-VirtualDisk | fl *
Any help here would be appreciated, really scratching my head. Even when I connect each of the single disks on their own they don't show up
Are as follows:
Usage                            : Auto-Select
OperationalStatus                : OK
HealthStatus                     : Healthy
BusType                          : USB
CannotPoolReason                 : In a Pool
SupportedUsages                  : {Auto-Select, Manual-Select, Hot Spare, Retired...}
MediaType                        : UnSpecified
ObjectId                         : {1}\\OFFICE-PC\root/Microsoft/Windows/Storage/Providers_v2\SPACES_PhysicalDisk.Objec
                                   tId="{cef39ebe-7fba-11e3-8250-806e6f6e6963}:PD:{772e2d6a-f0f7-11e1-be68-806e6f6e6963
PassThroughClass                 :
PassThroughIds                   :
PassThroughNamespace             :
PassThroughServer                :
UniqueId                         : USBSTOR\Disk&Ven_Seagate&Prod_Portable&Rev_0130\2GHY5YD1____&0:office-pc
AllocatedSize                    : 956435529728
CanPool                          : False
Description                      :
DeviceId                         : 2
EnclosureNumber                  :
FirmwareVersion                  : 0130
FriendlyName                     : Seagate Portable USB Device
IsIndicationEnabled              :
IsPartial                        : False
LogicalSectorSize                : 512
Manufacturer                     : Seagate
Model                            : Portable
OtherCannotPoolReasonDescription :
PartNumber                       :
PhysicalLocation                 :
PhysicalSectorSize               : 512
SerialNumber                     : 2GHY5YD1
Size                             : 999385202688
SlotNumber                       :
SoftwareVersion                  :
SpindleSpeed                     : 4294967295
PSComputerName                   :
CimClass                         : ROOT/Microsoft/Windows/Storage:MSFT_PhysicalDisk
CimInstanceProperties            : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
CimSystemProperties              : Microsoft.Management.Infrastructure.CimSystemProperties
Usage                            : Auto-Select
OperationalStatus                : OK
HealthStatus                     : Healthy
BusType                          : USB
CannotPoolReason                 : In a Pool
SupportedUsages                  : {Auto-Select, Manual-Select, Hot Spare, Retired...}
MediaType                        : UnSpecified
ObjectId                         : {1}\\OFFICE-PC\root/Microsoft/Windows/Storage/Providers_v2\SPACES_PhysicalDisk.Objec
                                   tId="{cef39ebe-7fba-11e3-8250-806e6f6e6963}:PD:{795ec931-3b3a-11e2-be6d-00247e572b92
PassThroughClass                 :
PassThroughIds                   :
PassThroughNamespace             :
PassThroughServer                :
UniqueId                         : USBSTOR\Disk&Ven_Seagate&Prod_Expansion&Rev_0215\NA41HDPW&0:office-pc
AllocatedSize                    : 956435529728
CanPool                          : False
Description                      :
DeviceId                         : 1
EnclosureNumber                  :
FirmwareVersion                  : 0215
FriendlyName                     : Seagate Expansion USB Device
IsIndicationEnabled              :
IsPartial                        : False
LogicalSectorSize                : 512
Manufacturer                     : Seagate
Model                            : Expansion
OtherCannotPoolReasonDescription :
PartNumber                       :
PhysicalLocation                 :
PhysicalSectorSize               : 512
SerialNumber                     :             NA41HDPW
Size                             : 999385202688
SlotNumber                       :
SoftwareVersion                  :
SpindleSpeed                     : 4294967295
PSComputerName                   :
CimClass                         : ROOT/Microsoft/Windows/Storage:MSFT_PhysicalDisk
CimInstanceProperties            : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
CimSystemProperties              : Microsoft.Management.Infrastructure.CimSystemProperties
Usage                            : Auto-Select
OperationalStatus                : OK
HealthStatus                     : Healthy
BusType                          : SATA
CannotPoolReason                 : Insufficient Capacity
SupportedUsages                  : {Auto-Select, Manual-Select, Hot Spare, Retired...}
MediaType                        : UnSpecified
ObjectId                         : {1}\\OFFICE-PC\root/Microsoft/Windows/Storage/Providers_v2\SPACES_PhysicalDisk.Objec
                                   tId="{cef39ebe-7fba-11e3-8250-806e6f6e6963}:PD:{ad47423f-540b-5a97-e386-ceff1f53db31
PassThroughClass                 :
PassThroughIds                   :
PassThroughNamespace             :
PassThroughServer                :
UniqueId                         : SCSI\Disk&Ven_FUJITSU&Prod_MHZ2120BH_G1\4&33c29369&0&000000:office-pc
AllocatedSize                    : 120034123776
CanPool                          : False
Description                      :
DeviceId                         : 0
EnclosureNumber                  :
FirmwareVersion                  : 0084000A
FriendlyName                     : PhysicalDisk0
IsIndicationEnabled              :
IsPartial                        : True
LogicalSectorSize                : 512
Manufacturer                     :
Model                            : FUJITSU MHZ2120BH G1
OtherCannotPoolReasonDescription :
PartNumber                       :
PhysicalLocation                 :
PhysicalSectorSize               : 512
SerialNumber                     :         K60VT9226KWM
Size                             : 120034123776
SlotNumber                       :
SoftwareVersion                  :
SpindleSpeed                     : 4294967295
PSComputerName                   :
CimClass                         : ROOT/Microsoft/Windows/Storage:MSFT_PhysicalDisk
CimInstanceProperties            : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
CimSystemProperties              : Microsoft.Management.Infrastructure.CimSystemProperties
The two 1TB disks are the ones in the Pool.
Usage                             : Other
OperationalStatus                 : OK
HealthStatus                      : Healthy
ProvisioningTypeDefault           : Fixed
SupportedProvisioningTypes        : {Thin, Fixed}
ReadOnlyReason                    : None
RepairPolicy                      : Sequential
RetireMissingPhysicalDisks        : Auto
WriteCacheSizeDefault             : Auto
FileSystem                        : Unknown
Version                           : Windows Server 2012
ObjectId                          : {1}\\OFFICE-PC\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StoragePool.Objec
                                    tId="{cef39ebe-7fba-11e3-8250-806e6f6e6963}:SP:{47405101-f1b2-11e1-be68-00247e572b9
                                    2}"
PassThroughClass                  :
PassThroughIds                    :
PassThroughNamespace              :
PassThroughServer                 :
UniqueId                          : {47405101-f1b2-11e1-be68-00247e572b92}
AllocatedSize                     : 1912871059456
ClearOnDeallocate                 : False
EnclosureAwareDefault             : False
FriendlyName                      : StoragePool
IsClustered                       : False
IsPowerProtected                  : False
IsPrimordial                      : False
IsReadOnly                        : False
LogicalSectorSize                 : 4096
Name                              :
OtherOperationalStatusDescription :
OtherUsageDescription             :
PhysicalSectorSize                : 4096
ResiliencySettingNameDefault      : Mirror
Size                              : 1998770405376
SupportsDeduplication             : False
ThinProvisioningAlertThresholds   : {70}
WriteCacheSizeMax                 : 107374182400
WriteCacheSizeMin                 : 0
PSComputerName                    :
CimClass                          : ROOT/Microsoft/Windows/Storage:MSFT_StoragePool
CimInstanceProperties             : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties
Usage                             : Other
OperationalStatus                 : OK
HealthStatus                      : Healthy
ProvisioningTypeDefault           : Fixed
SupportedProvisioningTypes        : {Thin, Fixed}
ReadOnlyReason                    : None
RepairPolicy                      : Parallel
RetireMissingPhysicalDisks        : Auto
WriteCacheSizeDefault             : Auto
FileSystem                        : Unknown
Version                           : Windows Server 2012 R2
ObjectId                          : {1}\\OFFICE-PC\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StoragePool.Objec
                                    tId="{cef39ebe-7fba-11e3-8250-806e6f6e6963}:SP:{cef39ebf-7fba-11e3-8250-806e6f6e696
                                    3}"
PassThroughClass                  :
PassThroughIds                    :
PassThroughNamespace              :
PassThroughServer                 :
UniqueId                          : {cef39ebf-7fba-11e3-8250-806e6f6e6963}
AllocatedSize                     : 2000137748480
ClearOnDeallocate                 : False
EnclosureAwareDefault             : False
FriendlyName                      : Primordial
IsClustered                       : False
IsPowerProtected                  : False
IsPrimordial                      : True
IsReadOnly                        : False
LogicalSectorSize                 :
Name                              :
OtherOperationalStatusDescription :
OtherUsageDescription             :
PhysicalSectorSize                :
ResiliencySettingNameDefault      : Mirror
Size                              : 2120443895296
SupportsDeduplication             : False
ThinProvisioningAlertThresholds   : {70}
WriteCacheSizeMax                 : 107374182400
WriteCacheSizeMin                 : 0
PSComputerName                    :
CimClass                          : ROOT/Microsoft/Windows/Storage:MSFT_StoragePool
CimInstanceProperties             : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties
Usage                             : Other
NameFormat                        :
OperationalStatus                 : Detached
HealthStatus                      : Unhealthy
ProvisioningType                  : Thin
ParityLayout                      : Unknown
Access                            : Read/Write
UniqueIdFormat                    : Vendor Specific
DetachedReason                    : Incomplete
WriteCacheSize                    : 0
ObjectId                          : {1}\\OFFICE-PC\root/Microsoft/Windows/Storage/Providers_v2\SPACES_VirtualDisk.Objec
                                    tId="{cef39ebe-7fba-11e3-8250-806e6f6e6963}:VD:{47405101-f1b2-11e1-be68-00247e572b9
                                    2}{4740510d-f1b2-11e1-be68-00247e572b92}"
PassThroughClass                  :
PassThroughIds                    :
PassThroughNamespace              :
PassThroughServer                 :
UniqueId                          : 0D514047B2F1E111BE6800247E572B92
AllocatedSize                     : 955898658816
FootprintOnPool                   : 1911797317632
FriendlyName                      : Storage space
Interleave                        : 262144
IsDeduplicationEnabled            : False
IsEnclosureAware                  : False
IsManualAttach                    : False
IsSnapshot                        : False
LogicalSectorSize                 : 4096
Name                              :
NumberOfAvailableCopies           :
NumberOfColumns                   : 1
NumberOfDataCopies                : 2
OtherOperationalStatusDescription :
OtherUsageDescription             :
PhysicalDiskRedundancy            : 1
PhysicalSectorSize                : 4096
RequestNoSinglePointOfFailure     : False
ResiliencySettingName             : Mirror
Size                              : 998579896320
UniqueIdFormatDescription         :
PSComputerName                    :
CimClass                          : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDisk
CimInstanceProperties             : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties

They do not show up in Disk Manager. They're part of a Storage Space, and the Virtual Disk for said storage space is not attached for some reason. Please see the logs per above from the get-virtualdisk command, and see a brief version below
FriendlyName        ResiliencySettingNa OperationalStatus   HealthStatus        IsManualAttach
Size
                    me
Storage space       Mirror              Detached            Unhealthy
False                            930 GB

How storage spaces mirror onto multiple storage pool drives...

Similar Messages

Maybe you are looking for