Unable to repair degraded Virtual disks in Storage Spaces 2012R2

Hi all,
I have an anoying problem that I cannot seems to find a solution for.
I have a 2 node Failover Cluster with CSV-volumes consisting of 2 HP DL360 servers with 2 LSI 9300-16e HBAs each, connected to 3 Supermicro JBOD-cases with a total of 84 disks. With Storage spaces I have made 1 Pool with 6 virtual disks and 3 of these disks
are Degraded. However, when I look at the physical disks they are all fine and healthy, if I try to repair the disks it finishes without any error messages but the disk is still Degraded.
OS = Windows Server 2012R2
Anyone have an idea?
Thanks!

Hello Partner,
Thanks so much for contacting Microsoft. This is Sophia who will help you with this issue.
From your description, I learnt that the issue you are experiencing is that you failed to repair degraded Virtual disks in Storage Spaces 2012 R2. Please let me
know if I misunderstand anything.
First of all, I would like to suggest you install the following hotfix to upgrade storage related files to the newest edition. After that, please test how the issue
goes.
==========================================
Package: This is to upgrade NTFS.sys.
KB Article Number(s): 2996802
Language: All (Global)
Platform: x64
Location: (http://hotfixv4.microsoft.com/Windows%208.1/Windows%20Server%202012%20R2/sp1/Fix524134/9600/free/480025_intl_x64_zip.exe)
Package: This is to upgrade Msiscsi.sys
KB Article Number(s): 3000123
Language: All (Global)
Platform: x64
Location: (http://hotfixv4.microsoft.com/Windows%208.1/Windows%20Server%202012%20R2/sp1/Fix524132/9600/free/479758_intl_x64_zip.exe)
Package: This is to upgrade MSDSM.sys & MPIO.SYS
KB Article Number(s): 2914743
Language: All (Global)
Platform: x64
Location: (http://hotfixv4.microsoft.com/Windows%208.1/Windows%20Server%202012%20R2/sp1/Fix525821/9600/free/479581_intl_x64_zip.exe)
Best regards,
Sophia Sun
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

Unable to repair degraded Virtual disks in Storage Spaces under Hyper-V 2012 R2 Core

Hi all,
I am finding myself in the following conundrum. I have a storage pool under Hyper-V Core, with 2 2TB Seagate drives.
One of the drives completely died (wouldn't spin up, tried it in a different box, still to no avail). I sent it in to Seagate for warranty replacement, got the new drive. Installed it and went through the notions of adding it to the pool and retiring the
one that was with "Lost Communication" status.
Tried to repair the virtual disks that are showing as "Unhealthy-Detached", quickly get 100% complete, but the repair didnt work.
The storage pool is in degraded state.
Looks like metadata is corrupted.
Followed this post to upgrade Storage Spaces to latest version:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/eead59e9-5e49-4bb6-8cbb-1dafddd9576b/unable-to-repair-degraded-virtual-disks-in-storage-spaces-2012r2?forum=winserverfiles
Still, to no avail.
Couple of questions:
1) Is the data on the 3 virtual disks in state "Unhealthy: Detached" not recoverable?
2) How can I get the storage pool back to "healthy"?
Any help will be greatly appreciated.
PS C:\corefig> Get-PhysicalDisk | ? OperationalStatus -ne OK | fl
ObjectId : {1}\\HV001\root/Microsoft/Windows/Storage/Pr
oviders_v2\SPACES_PhysicalDisk.ObjectId="{95
42513c-a0d4-11e3-8123-806e6f6e6963}:PD:{7e22
245f-0cf6-11e3-b1db-806e6f6e6963}"
PassThroughClass :
PassThroughIds :
PassThroughNamespace :
PassThroughServer :
UniqueId :
AllocatedSize : 1218696970240
BusType : Unknown
CannotPoolReason : In a Pool
CanPool : False
Description :
DeviceId :
EnclosureNumber :
FirmwareVersion :
FriendlyName : PhysicalDisk-1
HealthStatus : Warning
IsIndicationEnabled :
IsPartial : False
LogicalSectorSize : 0
Manufacturer :
MediaType : UnSpecified
Model :
OperationalStatus : Lost Communication
OtherCannotPoolReasonDescription :
PartNumber :
PhysicalLocation :
PhysicalSectorSize : 0
SerialNumber :
Size : 1999575711744
SlotNumber :
SoftwareVersion :
SpindleSpeed : 0
SupportedUsages : {Auto-Select, Manual-Select, Hot Spare,
Retired...}
Usage : Retired
PSComputerName :
PS C:\corefig> get-physicaldisk
FriendlyName CanPool OperationalS HealthStatus Usage Size
tatus
PhysicalDisk4 False OK Healthy Auto-Select 73.75 GB
PhysicalDisk0 False OK Healthy Auto-Select 1.82 TB
PhysicalDi... False Lost Comm... Warning Retired 1.82 TB
PhysicalDisk2 False OK Healthy Auto-Select 930.75 GB
PhysicalDisk3 False OK Healthy Auto-Select 74.53 GB
PhysicalDisk1 False OK Healthy Auto-Select 1.82 TB
PS C:\corefig> get-virtualdisk -friendlyname 'Data' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e2229cf-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = CF29227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 548413636608
DetachedReason = Incomplete
FootprintOnPool = 1096827273216
FriendlyName = Data
HealthStatus = Unhealthy
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = False
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 1099511627776
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =
PS C:\corefig> get-virtualdisk -friendlyname 'Backups' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e22255e-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = 5E25227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 743566213120
DetachedReason = Incomplete
FootprintOnPool = 1487132426240
FriendlyName = Backups
HealthStatus = Unhealthy
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = False
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 1649267441664
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =
PS C:\corefig> get-virtualdisk -friendlyname 'Music' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e2238b9-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = B938227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 39728447488
DetachedReason = By Policy
FootprintOnPool = 79456894976
FriendlyName = Music
HealthStatus = Unknown
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = True
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 161061273600
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =
PS C:\corefig> get-virtualdisk -friendlyname 'Videos' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e2225bc-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = BC25227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 223606734848
DetachedReason = Incomplete
FootprintOnPool = 447213469696
FriendlyName = Videos
HealthStatus = Unhealthy
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = False
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 1759325978624
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =

Hi omon_77,
You can first refer the following step by step third party article and KB:
Replace Failed Disks and Repair JBODs for Storage Spaces in Windows Server
https://technet.microsoft.com/en-us/library/dn782852.aspx?f=255&MSPPError=-2147217396
Replacing a failed disk in Windows Server 2012 Storage Spaces with PowerShell
https://www.hodgkins.net.au/storage/replace-failed-disk-in-storage-spaces-pool-with-powershell/
Step By Step: How to Replace Faulty Disk In Two-Way Mirrored Storage Tiered Space
http://charbelnemnom.com/2014/09/step-by-step-how-to-replace-faulty-disk-in-two-way-mirrored-storage-tiered-space-storagespaces-ws2012r2/
More information:
Storage Spaces - Designing for Performance
http://social.technet.microsoft.com/wiki/contents/articles/15200.storage-spaces-designing-for-performance.aspx
Storage Spaces Overview
http://technet.microsoft.com/en-us/library/hh831739.aspx
Windows Server Storage Spaces: What is it and why should I use it?
http://curah.microsoft.com/5049/windows-server-2012-r2-storage-spaces-what-is-it-and-why-should-i-use-it
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Replacing a failed disk in storage space ! unable to remove a retired disk

Hi Folks
Not really asking for much !! we are using windows 2012 R2 storage space ; one disk failed
and marked as retired.
today we received replacement disk ; added that to storage pool - fine.
then I repaired all Virtual Disk - process was very quick and went to 100% like a flash.
then I tried to remove faulty disk by using following commands :
$DeadDisk=Get-PhysicalDisk -FriendlyName PhysicalDisk-1
FriendlyName CanPool OperationalStatus HealthStatus Usage
Size
PhysicalDisk-1 False Lost Communication Warning Retired 185.5
GB
Remove-PhysicalDisk -PhysicalDisks $deaddisk -StoragePoolFriendlyName storagePool
this errored out ; basically saying that the above disk is still in-use !
Any suggestions ? does repair job take some time ? it looked very fast ; when I did get-storagejob ; it showed 100 percent completed .

Hi,
Please reboot the server then set the failed disk to "Retired" and remove the retired physical disk.
You could refer to the thread below to troubleshoot the issue:
Degraded Storage Spaces Storage Pool after single HDD failure
http://social.technet.microsoft.com/Forums/en-US/3a7e2a7d-4ad7-48cc-8165-0d6673e37436/degraded-storage-spaces-storage-pool-after-single-hdd-failure
Regards,
Mandy
If you have any feedback on our support, please click
here .
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.

Can I migrate physical hard disks in storage space from Windows 2012 R2 to Windows 2012?

Hi,
We have a Windows 2012 R2 server. It's running storage space with 10 hard disk in Parity mode. We would like to move the hard disks from Windows 2012 R2 server to Windows 2012, so that we can "free" our windows
2012 R2 server to do something else. Can we just unplug the hard disks in Windows 2012 R2 and hook it to Windows 2012 server without any data lose? If we can do it, what's best "formal" procedures to do it?
Thanks,
Tak

Hi Tak,
Storage space will be recognized in different servers (and even clients) which support.
If it is just a "Parity mode", you can turn off the computer, unplug and connect these disks to the new server directly.
If any Windows Server 2012 R2 new feature is involved, it may not work in Windows Server 2012 but it should not damage your data and you can still connect these hard disks back to original server.
However, backup important files is always recommended.
If you have any feedback on our support, please send to [email protected]

Unable to repair External Drive disk permissions

I have an external harddrive which holds my itunes library. Today I have been getting permission errors and now my itunes won't access the files on the drive.
I have tried to fix the errors with disk utility but now when I try to repair it I get the error: Could not unmount the disk.
Now I can't even see the iTunes folder on the external drive (I can see others) but I know it is there as 150GB of data is unaccounted for.

I had the same problem with my Time Machine backup disk and was able to solve it without the serious computer calisthenics recommended by others on the web. I'm running Snow Leopard on an intel iMac and using an external Seagate drive. Here's how I got it fixed.
1. Unmounted the drive and unplugged it.
2. Plugged it back in after a decent interval to let the disk spin down.
3. Shut down the iMac and restarted it a few minutes later (hard reset).
4. THE DISK DID NOT SHOW UP IN FINDER. Because I had a lot of work to do, I postponed further systems programming.
5. After about 20 minutes, my Norton utilities found it and began to search it. It was back in finder with r/w permissions for me and everybody else.
Hope this helps.

Unable to Enable User Profile Disks in RDP server 2012R2

I am setting up a new Windows server that will act as an RDP server. The server has been built with Windows Server 2012R2.
I have the following roles and services working on the server: RD Web Access, RD Gateway, RD Licencing (with 30 user cal licences), the RD Connection broker, and the RD session host.
I have a SSL certificate configured and installed on the site, and both external and internal DNS are configured and working.
I have created and published an application collection and this is working. That is, when you go to https://remote.<servername>.org you are presented with a log in screen, users can log in with their domain accounts and then can connect to the published
applications, this is working both on our internal network and from the general internet.
So all the roles on the server are working and the collection itself is also working. However, what I cannot do is set it up so that we can use user profile disks with that collection. When I go through the Session Collection Wizard and I get to "User
Profile Disks" I can click on "Enable user profile disks" and then you can enter the options below.
I am entering the share location under location \\<servername>\<sharename>
I am using the default "store all user settings and data on the user profile disk"
Then I go to create the profile disks and I get the following error:
"Could not create the template VHD. Error Message: -2147024809
This has happened multiple times, I have done the following:
- installed all windows updates and rebooted the server, same error
- checked the share permissions AND the folder permission for that share, for testing purposes I have set permissions on both the folder and the share to allow full control to "everyone" (I also tried it with only "domain users") but
same error message.
- I have checked to see that no quotas are imposed on the disk where I am attempting to create the profile disks - this was because this was the closest thing I could find on Technet was this post:
https://social.technet.microsoft.com/Forums/windowsserver/ru-RU/aec30527-d742-42b9-950e-85c709c4cb45/vdi-problem-creating-user-profile-disks?forum=winserverhyperv
And that was a quota issue that I am not having.
The UPD wizard says the following "the servers in the collection must have full control permission on the user profile disk share and the current user must be a member of the local Administrators group on that server"
Both of those things are true.
I have attempted to search for that specific error message (-2147024809) and have found nothing on Technet or any other site.
I am hoping someone here has some thoughts. Thanks in advance.

I was looking at both the technet article for setting up UPD as well as this walk-through:
http://thewolfblog.com/2014/02/24/user-profile-disks-for-rds-2012-2012-r2/
The step after the creation of the disk in this walk-through is to look at who has permission on the .vhdx file, now obviously I am not at that step, but that is what led me down the trail of looking at user permissions, hence my attempts to set up shares
where 'everyone' has full permissions on both the share and the folder.
I have tried to set up multiple shares for the collection, I have tried on two different disks (volumes) on the RDP server itself, I also tried setting up a share on our fileserver (which has all kinds of shares working fine) and the same error occurred
in all cases.
I also found this Technet article:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/d6469d31-6540-4075-a85f-a6e8f7c11e89/user-profile-disk-template-cannot-be-created-when-setting-up-session-collection?forum=winserverTS
So that seems close to what I am looking for, but I have checked and the exact group policy that was causing the above linked issue is not defined in our group policies, but maybe there are other group policies that are causing the issue?

IPhone unable to work due to not enough storage space available.

It's been quite some time now that I'm having trouble with my iPhone 4s. It tells me that I don't have enough memory available. I don't have any music installed, I have very few app's installed, but I do have a lot of pictures. It's getting frustrating because the internet starts to drop off or won't even open. My text messages dissappear or won't even send. On my old iPhone 3GS, I had a lot of apps, tons of pictures, lots of music and not once did I have any issues with memory. Help needed....

What do you mean it "refuses to work using bluetooth"?
The iPhone does not support bluetooth file transfer. The only thing you can use it for with any computer is tethering the internet connection from the phone. You can not sync or transfer data with your computer via bluetooth. You can sync via cable or WiFi.

Storage Spaces - Can't recover from OS reinstall (failure to attach VHD)

I had a Windows 2012 R2 Standard server with GUI running Storage Spaces on some non-raid drives. The OS became corrupted and so I had to reinstall. Upon reinstall I go to Storage Spaces and see everything just as it should be in terms of recovery.
The problem I'm having is the reattaching of the VHD file itself that hosts all of the files. I click attach VHD and it does, nothing shows up Explorer though.
So I go to manage disk drives and it shows all of the individual drives and the large VHD set to offline. I online the drive and the machine just basically locks up.
I tried to do the same thing via powershell but have the same problem with the machine just locking up. Anybody seend this before? I don't really care to actually get the Storage Spaces working at this point, just need access the files themselves
so I can pull them off. Any help is much appreciated.

Hi,
Generically Storage Space will not be affected with reinstall operation system - if we move all disks to another computer, storage space will still be recognized.
it shows all of the individual drives and the large VHD set to offline
We should not see any disk inside a created storage space in Disk Manager - Virtual Disks created in Storage Space will be listed but not the physical disks. So I need to confirm:
a. Whether "individual drives" means physical disks, or virtual disks created in Storage Space?b.
Whether "VHD" here means virtual disks in Storage Space, or you actually created VHD on virtual disks (in storage space).
If VHD here means virtual disks, you can test to connect all disks to another system which supports Storage Space (Windows Server 2012 or 2012 R2) to see if disks could be recognized.
However it seems more likely "VHDs on Virtual disk" - VHD files could corrupt which causes your current situation and if this is true, it will be difficult to get VHD files back to work as we have less option to repair a corrupted VHD file.
If you have any feedback on our support, please send to [email protected]

Unable t repair disk permissions on an external FAT 32 drive

Yesterday suddenly my disk permissions on my Aperture library file changed. It's located on an external fat 32 drive. I'm unable to repair it with disk utility. Now Aperture won't run anymore until I repair this file. Are there any other options then disk utility?

DU can not repair Windows formatted drives. Need to boot into Windows and use its utilities for disk repair.
It's not a goo idea to keep Mac OS X applications or data files on a non-Mac formatted drive. FAT32's filesystem is not compatible with the Mac's. Portions of a file may be removed on the FAT32 drive and it's not fully compatible with OS X filenames and legal filename characters.

Storage Spaces UI missing disks when a controller reports the same UniqueID for all attached disks (e.g. Supermicro AOC-SASLP-MV8)

Summary: The Storage Spaces UI has several problems when there are more than 21 physical disks available to Storage Spaces.
I have 28 SATA disks connected over 6 controllers. 2 are used for an Intel motherboard RAID1 for OS (PhysicalDisk0), so that leaves 26 data disks for Storage Spaces. [The plan is to get to 36 data disks in due course by adding disks (this 36-bay chassis: http://www.supermicro.com/products/chassis/4U/847/SC847A-R1400LP.cfm)]
Initially, there were 23 data disks (5x 1TB, 1x 640GB, 14x 500GB, 3x 250GB) as PhysicalDisk1-23 (in that order), which I put into a storage pool. I created a parity disk over all 23 disks. It looks like it is working fine, albeit very slowly on writes.
I've now added 3 more 4TB disks, as PhysicalDisk24-26, and taken them offline, and have now noticed errors in the Storage Pools UI in the Server Manager. For example:
* No more than 21 disks ever show up in the "Physical Disks" area in the lower right. When the 23 disks are connected, only the first 21 show up in the pool I created. With 26 disks connected, only the first 20 show up in the pool, and only 1 more of the
new 3 (PhysicalDisk26) shows up in the Primordial group.
* In the Properties of the parity Virtual Disk created over the 23 disks, the disks are shown incorrectly. Again, only 21 disks are shown, and PhysicalDisk26 is incorrectly shown as part of the virtual disk. See image:
* Using the New Storage Pool Wizard, I cannot add more than 1 of the new 3 disks to a new Storage Pool (only PhysicalDisk26 is available). And the details incorrectly refer to PhysicalDisk21. See image (a WDC WD2500JD-22H is a 250GB disk, not a 4TB disk).
Thus I cannot use the new disks in a new storage pool.
According the blog post at http://blogs.msdn.com/b/b8/archive/2012/01/05/virtualizing-storage-for-scale-resiliency-and-efficiency.aspx:
Q) What is the minimum number of disks I can use to create a pool? What is the maximum?
You can create a pool with only one disk. However, such a pool cannot contain any resilient spaces (i.e. mirrored or parity spaces). It can only contain a simple space which does not provide resiliency to failures. We do test pools comprising multiple hundreds
of disks – such as you might see in a datacenter. There is no architectural limit to the number of disks comprising a pool.
However, the UI currently does not seem to correctly work with more than 21 physical disks. Please advise.
Using Server 2012 RC.
Hardware: Supermicro X8SAX (BIOS v2.0), Intel i7-920 2.67GHz, 6x 2GB DDR3-1333 (certified Crucial CT25664BA1339.16SFD)
Disk controllers: 2x RAIDCore BC4852 (PCI-X, final 3.3.1 driver) (15 ports used), 2x Supermicro AOC-SASLP-MV8 (PCIe, 4.0.0.1200 Marvell driver to allow >2TB disks) (6 ports used), Sil 3114 (PCI, latest 1.5.20.3 driver) (1 port used), motherboard Intel
in RAID mode (4 ports used for data, plus 2 for OS RAID1).

An update. I added 16x SATA disks across 2x Supermicro AOC-SASLP-MV8. All 16 disks report the same UniqueID.
I have 25 disks in the pool now (23 as parity; 2 as journal added via PowerShell). 10 of these are on the two AOC-SASLP-MV8 controllers. Only the first 16 disks show up in the UI, so 9 are missing from the UI - which is consistent with this UI bug where
only one disk per UniqueID shows up. PowerShell does work to manage the SS.
PS C:\Users\administrator.TROUNCE> Get-PhysicalDisk | format-list FriendlyName, UniqueId, ObjectId, BusType
FriendlyName : PhysicalDisk6
UniqueId : 00280000004000004FB116493C169A1A
ObjectId : {7ab38e00-ab87-11e1-bbbd-806e6f6e6963}
BusType : Fibre Channel
FriendlyName : PhysicalDisk7
UniqueId : 00280000004000001AE48E5088028D0D
ObjectId : {7ab38e02-ab87-11e1-bbbd-806e6f6e6963}
BusType : Fibre Channel
FriendlyName : PhysicalDisk8
UniqueId : 002800000040000020C9A6680224E32F
ObjectId : {7ab38e04-ab87-11e1-bbbd-806e6f6e6963}
BusType : Fibre Channel
FriendlyName : PhysicalDisk9
UniqueId : 0028000000400000FDE73E7254A60C4C
ObjectId : {7ab38e06-ab87-11e1-bbbd-806e6f6e6963}
BusType : Fibre Channel
FriendlyName : PhysicalDisk23
UniqueId : 0050430000000000
ObjectId : {7ab38e08-ab87-11e1-bbbd-806e6f6e6963}
BusType : RAID
FriendlyName : PhysicalDisk22
UniqueId : 0050430000000000
ObjectId : {7ab38e0a-ab87-11e1-bbbd-806e6f6e6963}
BusType : RAID
FriendlyName : PhysicalDisk21
UniqueId : 0050430000000000
ObjectId : {7ab38e0c-ab87-11e1-bbbd-806e6f6e6963}
BusType : RAID
FriendlyName : PhysicalDisk20
UniqueId : 0050430000000000
ObjectId : {7ab38e0e-ab87-11e1-bbbd-806e6f6e6963}
BusType : RAID
FriendlyName : PhysicalDisk5
UniqueId : 0028000000400000272BA74A52309853
ObjectId : {7ab3900f-ab87-11e1-bbbd-002590520253}
BusType : Fibre Channel
FriendlyName : PhysicalDisk19
UniqueId : 0050430000000000
ObjectId : {7ab38e10-ab87-11e1-bbbd-806e6f6e6963}
BusType : RAID
FriendlyName : PhysicalDisk4
UniqueId : 00280000004000009DE164099941430A
ObjectId : {7ab39011-ab87-11e1-bbbd-002590520253}
BusType : Fibre Channel
FriendlyName : PhysicalDisk18
UniqueId : 0050430000000000
ObjectId : {7ab38e12-ab87-11e1-bbbd-806e6f6e6963}
BusType : RAID
FriendlyName : PhysicalDisk11
UniqueId : 0028000000400000967EB0559AB4E351
ObjectId : {7ab39013-ab87-11e1-bbbd-002590520253}
BusType : Fibre Channel
FriendlyName : PhysicalDisk17
UniqueId : 0050430000000000
ObjectId : {7ab38e14-ab87-11e1-bbbd-806e6f6e6963}
BusType : RAID
FriendlyName : PhysicalDisk24
UniqueId : 0050430000000000
ObjectId : {7ab38e16-ab87-11e1-bbbd-806e6f6e6963}
BusType : RAID
FriendlyName : PhysicalDisk10
UniqueId : 0028000000400000B22A722C8AD2557B
ObjectId : {df23f916-c19f-11e1-bbf5-806e6f6e6963}
BusType : Fibre Channel
FriendlyName : PhysicalDisk16
UniqueId : 0028000000400000DA4D24536A847E52
ObjectId : {7ab38e19-ab87-11e1-bbbd-806e6f6e6963}
BusType : Fibre Channel
FriendlyName : PhysicalDisk15
UniqueId : 00280000004000005DEDFF007783A242
ObjectId : {7ab38e1b-ab87-11e1-bbbd-806e6f6e6963}
BusType : Fibre Channel
FriendlyName : PhysicalDisk14
UniqueId : 002800000040000018C9CF6EBE605911
ObjectId : {7ab38e1d-ab87-11e1-bbbd-806e6f6e6963}
BusType : Fibre Channel
FriendlyName : PhysicalDisk13
UniqueId : 0028000000400000B64436290D155A48
ObjectId : {7ab38e1f-ab87-11e1-bbbd-806e6f6e6963}
BusType : Fibre Channel
FriendlyName : PhysicalDisk0
UniqueId : IDE\DiskOS1.0.00__\4&180adc7b&0&0.0.0:Trounce-Server2
ObjectId : {df23f925-c19f-11e1-bbf5-806e6f6e6963}
BusType : RAID
FriendlyName : PhysicalDisk31
UniqueId : 0050430000000000
ObjectId : {df241daf-c19f-11e1-bbf5-002590520253}
BusType : RAID
FriendlyName : PhysicalDisk32
UniqueId : 0050430000000000
ObjectId : {df241db2-c19f-11e1-bbf5-002590520253}
BusType : RAID
FriendlyName : PhysicalDisk27
UniqueId : 0050430000000000
ObjectId : {df241cbe-c19f-11e1-bbf5-002590520253}
BusType : RAID
FriendlyName : PhysicalDisk28
UniqueId : 0050430000000000
ObjectId : {df241cc1-c19f-11e1-bbf5-002590520253}
BusType : RAID
FriendlyName : PhysicalDisk34
UniqueId : 0050430000000000
ObjectId : {df241dc4-c19f-11e1-bbf5-002590520253}
BusType : RAID
FriendlyName : PhysicalDisk29
UniqueId : 0050430000000000
ObjectId : {df241cca-c19f-11e1-bbf5-002590520253}
BusType : RAID
FriendlyName : PhysicalDisk33
UniqueId : 0050430000000000
ObjectId : {df241dcf-c19f-11e1-bbf5-002590520253}
BusType : RAID
FriendlyName : PhysicalDisk30
UniqueId : 0050430000000000
ObjectId : {df241cd3-c19f-11e1-bbf5-002590520253}
BusType : RAID
FriendlyName : PhysicalDisk2
UniqueId : 002800000040000037638531D4A17419
ObjectId : {7ab38df8-ab87-11e1-bbbd-806e6f6e6963}
BusType : Fibre Channel
FriendlyName : PhysicalDisk3
UniqueId : 0028000000400000AB7400464090110C
ObjectId : {7ab38dfa-ab87-11e1-bbbd-806e6f6e6963}
BusType : Fibre Channel
FriendlyName : PhysicalDisk1
UniqueId : IDE\DiskWDC_WD6400AAKS-00A7B2___________________01.03B01\4&180adc7b&0&0.1.0:Trounce-Server2
ObjectId : {7ab38dfc-ab87-11e1-bbbd-806e6f6e6963}
BusType : RAID
FriendlyName : PhysicalDisk12
UniqueId : 00280000004000005396CC47AA8AD97B
ObjectId : {7ab38dfe-ab87-11e1-bbbd-806e6f6e6963}
BusType : Fibre Channel

How to configure local disk on OVM Server as storage space to create VMs

Hello,
We have installed OVM Server 3.1.1 on a machine that has 250 GB of Hard disk space [Single disk].
While installing used an option - Remove all partitions and create a new default partition layout.
Around 4GB has been used and remaining 246 GB is left as free space.
From OVM Manager - the server is discovered but didn't discovered the physical disk [i.e. remaining 246 GB raw disk space].
Can someone help me to understand how to use local disk as storage space for creating and running VM's.
Thanks
Srinivas

You can? You've used every conceivable BIOS out there? You must really be full of yourself. There is absolutely no BIOS that I know of that gives this basic function. BIOSs do not "hard partition" anything. A "BIOS" is not made for such things. Do you even know what "BIOS" stands for?
I wonder why there is some many wanting to do this and are having problems.... I mean if it is such a straight forward thing to do..... It must be down right "intuitive".
You maybe speaking of a RAID "BIOS" but you obviously think you're not. Some motherboards have integrated RAID abilities. Intel RST comes to mind... BUT this isn't a feature of a MOTHERBOARD BIOS.
I've got some $50,000 servers that will not break a single hard drive up into multiple logical drives..... Now, I haven't worked on a "Stinkpad" for many years. Don't want to. However, I have never seen one that would do what you're saying you're doing.
You maybe trying to help.... but you're leading people down a wrong path.
Its just as easy to run virtual box and use the virtual box templates for Oracle VM. In fact, its more practical if you want to run Oracle VM on a laptop for testing purposes than blowing everything away and attempting to setup different LUNS on a single hard drive.
For your review...
http://www.oracle.com/technetwork/articles/servers-storage-admin/configure-vm-templates-1656261.html
Although it's more reliable to use a separate location (such as an NFS share) for a storage repository, you can use a local disk of your Oracle VM Server instead, thus taking advantage of the local storage option. Beware, though: Oracle VM Server 3.0 doesn't allow you to utilize the unused space on the physical disk it's installed on. For local storage, you'll need at least one more physical disk. In other words, you'll need a total of two disks at minimum on your Oracle VM Server host if you want to use local storage. In practice, though, local storage is not a primary use case. The major downside to this approach is that local storage, by definition, cannot be shared between different servers.
Edited by: user12273962 on Dec 10, 2012 10:40 AM

Error when expand virtual disk.

Hello everybody,
Immediately, I have facing an error message when I try to expand the virtual disk in storage 6140 as below:
A volume/volume-group reconfiguration operation cannot be performed because it involves drives having overlapping DACSTORE regions.
Please share me some ideas above issue. Thanks in advance.
Warm Regard,

You're in troubles. :-/
You can try another disk utility, but basically, the best to do, first, is a low-level formatting (format with the "zero data" option checked).
If it finish that, then reinstall a system and go ahead (keep backups up to date tho)
If it does not, you will have to get the hard disk changed.
Why reward points ?

2 Way mirror via Storage Spaces using 2xJBODS

Looking to setup 2xJBODS connected to a cluster File Servers & use 2-WAY mirror for the pool. Its clear that w. a 2way mirror that it can only handle 2 drives failing before seeing data loss but is that 2 drives between both JBODS or is that 2 driver
per JBOD? Also I know that if 1 JBOD were to completely go offline that I would need a total of 3 JBODS in order for vms,etc to not be affected but what is the expected behavior. A jbod goes offline and we lose vms but data is not loss? Once the jbod
comes back data will be back to normal?

if you are going to mirror the 2 of them yes
What are the resiliency levels provided by Enclosure Awareness?
Storage Space Configuration
All Configurations are enclosure aware
Enclosure or JBOD Count / Failure Coverage
Two JBOD
Three JBOD
Four JBOD
2-way Mirror
1 Disk
1 Enclosure
1 Enclosure
3-way Mirror
2 disk
1 Enclosure + 1 Disk
1 Enclosure + 1 Disk
Dual Parity
2 disk
2 disk
1 Enclosure + 1 Disk
REF: Storage Spaces Frequently Asked Questions (FAQ)
Storage Spaces, JBODs, and Failover Clustering – A Recipe for Cost-Effective,
Highly Available Storage
This post is provided AS IS with no warranties or guarantees, and confers no rights.
~~~
Questo post non fornisce garanzie e non conferisce diritti

Storage spaces simple mirror question

I just have a simple mirror at the moment, with just two 1tb drives in mirror mode, and it works just fine. Two things I do wonder. If one drive fails, I assume the files would be preserved on the other. I wonder however if it can be plugged
into another Windows box, a Windows 7 machine for example, and read by that machine, or if it can only be read by the machine on which it was setup?
I have assumed Storage Spaces was like hardware raid in this way, but now I wonder....

Hi,
For mirror mode, it means that Data is duplicated on two or three physical disks, and this storage layout requires at least two disks to protect you from a single disk failure.
But you can't view the content in the disk since Storage Spaces records information about pools and storage spaces on the physical disks that compose the storage pool. Therefore, your pool and storage spaces are preserved when you move an entire storage
pool and its physical disks from one computer to another.
Windows Server 2012 starts storage that could potentially be shared with a cluster in a safe state. For Storage Spaces, that means the first time Windows connects to a storage pool, the pool starts as read-only and the storage spaces will start in a detached
state. To access your data, you must set the storage pool to read-write and then attach the storage spaces.
These steps do not apply to Windows 8 – storage pools start as read-write and storage spaces start as attached.
Kate Li
TechNet Community Support

Repair Degraded Storage Spaces Virtual Disk - All physical disks show healthy

I've seen this mentioned a few times but no definitive answers. I have a Storage Pool with 8 physical disks. Each physical disk shows as healthy and auto select. I have thick provisioned Virtual Disk created on this Storage Pool in a parity configuration.
This virtual disk is configured for the maximum amount on the storage pool. 50% of the space is available on the volume of the virtual disk...I click repair it does nothing.
Tested yanking a physical disk. Virtual disk becomes unavailable. No redundancy currently. How the heck do I fix this???

Hi,
First please try to run a repair again with Powershell cmdlet:
Repair-VirtualDisk
If issue still exists please try optimize to see if it will help:
Optimize-Volume
If you have any feedback on our support, please send to [email protected].
Repair-VirtualDisk:
Runs shows a progress bar for a very short period of time. Goes back to prompt. No messages or errors. Running Get-Virtual disk still shows the VD as degraded.
Optimize-Volume:
PS C:\Users\Administrator> Optimize-Volume -driveletter D -analyze -defrag -verbose
VERBOSE: Invoking defragmentation on DATA (D:)...
Optimize-Volume : A general error occurred that is not covered by a more specific error code.
At line:1 char:1
+ Optimize-Volume -driveletter D -analyze -defrag -verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (MSFT_Volume (Ob...8-8907-3485...):ROOT/Microsoft/...age/MSFT_Volume) [Opt
imize-Volume], CimException
+ FullyQualifiedErrorId : HRESULT 0x89000000,Optimize-Volume
PS C:\Users\Administrator> Optimize-Volume -driveletter D -analyze -defrag -verbose
VERBOSE: Invoking defragmentation on DATA (D:)...
Optimize-Volume : A general error occurred that is not covered by a more specific error code.
At line:1 char:1
+ Optimize-Volume -driveletter D -analyze -defrag -verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (MSFT_Volume (Ob...8-8907-3485...):ROOT/Microsoft/...age/MSFT_Volume) [Opt
imize-Volume], CimException
+ FullyQualifiedErrorId : HRESULT 0x89000000,Optimize-Volume
PS C:\Users\Administrator> Optimize-Volume D -analyze -verbose
VERBOSE: Invoking analysis on DATA (D:)...
Optimize-Volume : A general error occurred that is not covered by a more specific error code.
At line:1 char:1
+ Optimize-Volume D -analyze -verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (MSFT_Volume (Ob...8-8907-3485...):ROOT/Microsoft/...age/MSFT_Volume) [Opt
imize-Volume], CimException
+ FullyQualifiedErrorId : HRESULT 0x89000000,Optimize-Volume
PS C:\Users\Administrator> Optimize-Volume D -Verbose
VERBOSE: Invoking defragmentation on DATA (D:)...
Optimize-Volume : A general error occurred that is not covered by a more specific error code.
At line:1 char:1
+ Optimize-Volume D -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (MSFT_Volume (Ob...8-8907-3485...):ROOT/Microsoft/...age/MSFT_Volume) [Opt
imize-Volume], CimException
+ FullyQualifiedErrorId : HRESULT 0x89000000,Optimize-Volume
Both error out...

Unable to repair degraded Virtual disks in Storage Spaces 2012R2

Similar Messages

Maybe you are looking for