Virtual Disk disappeared

Hi there,
I have a storage pool containing 3x2TB physcial disks: one WD and two Seagate. Pool have 2 virtual disks: Data (mirrored) and Temp (Simple). After some time Temp drive disappeared from the list and I lost all data on it. Not big deal but I want to
recreate storage pool as saw somewhere that data structure or something has changed since first release of Storage Spaces (I'm using them from first official beta of Windows Server 2012).
So as I'm lost my Temp drive, I decided to do following:
1) Delete WD disk from storage pool, so data will remain on 2xSeagate (I have about 1,5 TB of data)
2) Reformat WD as single drive and copy everything to it
3) Delete old storage pool
4) Create new one
5) Create mirrored virtual disk
6) Copy data back from WD to that virtual disk
But I'm stuck on removal WD from storage pool, as Server manager says me that there is not enough space in storage pool and I should first connect spare disk.
Looks like my Temp drive disappeared, but space not has been purged. So is there any way to get my Temp dirve back or manually run cleanup?
MCSE, MCITP, CCNA Security Subscribe to my blog at http://sypalo.com

Hi,
Sorry for my mistake, I mean that the data on the mirror virtual disk is striped across the three physical disks. As you mentioned the allocated space is less than a physical disk, you want to know if there is a way to shrink the virtual disk to let the allocated
space size is larger than the size of one physical disk.
You could use Optimize-Volume command line to optimize a volume, performing such tasks on supported volumes and system SKUs as defragmentation, trim, slab consolidation,
and storage tier processing. Then use Resize-VirtualDisk
command line to resizes the virtual disk to be smaller.
But if the allocated space is still less than a physical disk, you should attach a new spare disk when delete a physical disk.
In the meantime, if the virtual disk have a lot of duplication data, you can also enable data deduplication to get more allocated space in virtual disk.
For more detailed information, please refer to the articles below:
Step-by-Step: Enabling Data Deduplication on Windows Server 2012 Volumes
http://social.technet.microsoft.com/Forums/windowsserver/en-US/441858d0-0a17-4126-a594-ba1c6483c59b/virtual-disk-disappeared?forum=winserverfiles
Introduction to Data Deduplication in Windows Server 2012
http://blogs.technet.com/b/filecab/archive/2012/05/21/introduction-to-data-deduplication-in-windows-server-2012.aspx
Regards,
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.

Similar Messages

Storage Spaces: Virtual Disk taken offline during file copy, marked as "This disk is offline because it is out of capacity", but plenty of free space

Server 2012 RC. I'm using Storage Spaces, with two virtual disks across 23 underlying physical disks.
* First virtual disk is fixed provisioning, parity across 23 physical disks: 10,024GB capacity
* Second virtual disk is fixed provisioning, parity across the remaining space on 6 of the same physical disks: 652GB capacity
These have been configured as dynamic disks, with an NTFS volume spanned across the two (larger virtual disk first). Total volume size 10,676GB. For more details of the hardware, and why the configuration is like this, see: http://social.technet.microsoft.com/Forums/en-US/winserver8gen/thread/c35ff156-01a8-456a-9190-04c7bcfc048e
I'm copying several TB from a network share to this volume. It is very slow at ~12MB/sec, but works. However, three times so far, several hours in to the file copy and with plenty of free space remaining, the 10,024GB virtual disk is suddenly taken offline.
This obviously then fails the spanned volume and stops the file copy.
The second time, I took screenshots, below. The disk (Disk27) is marked offline due to "This disk is offline because it is out of capacity". And the disk in the spanned volume is marked as missing (which is what you would expect when one of its member disks
is offline).
I can then mark the disk (Disk27) back online again, and this restores the spanned volume. I can then re-start the file copy from where it failed. There doesn't appear to be any data loss, but it does cause an outage that requires manual attention. As you
can see, there is plenty of space left on the spanned volume.
Each time this has happened, there are a few event 150 errors in the System event log: "Disk 27 has reached a logical block provisioning permanent resource exhaustion condition.". Source: Disk.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="disk" />
<EventID Qualifiers="49156">150</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-06-07T11:24:53.572101500Z" />
<EventRecordID>14476</EventRecordID>
<Channel>System</Channel>
<Computer>Trounce-Server2.trounce.corp</Computer>
<Security />
</System>
- <EventData>
<Data>\Device\Harddisk27\DR27</Data>
<Data>27</Data>
<Binary>000000000200300000000000960004C0000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
This error seems to be related to thin provisioning of disks. I found this:
http://msdn.microsoft.com/en-us/library/windows/desktop/hh848068(v=vs.85).aspx. But both these Virtual Disks are configured as Fixed, not Thin provisioning, so it shouldn't apply.
My thoughts: the virtual disk should not spuriously go offline during a file copy, even if it was out of space. And in any case, there is plenty of free space remaining. Also, I don't understand the reason for why it is marked as offline ("This disk is offline
because it is out of capacity"). Why would a disk go offline because it was out of thin capacity, rather than just returning an "out of disk space" error while keeping it online.

Interesting Thread, I've been having the same issue. I had a failed hardware RAID that was impossible to recover in place, so after being forced to do a 1:1 backup, I find myself with 5 2TB hard drives to play with. Storage Spaces seemed like an interesting
way to go until I started facing the issues we share.
So my configuration is A VM Running Windows Server 2012 RC with 5 Virtualized Physical drives using a SCSI interface, 2TB in size that make up my storage pool. A Single Thinly provisioned Disk of 18 TB (using 1 disk for parity)
Interestly enough, write speed has not been an issue on this machine (30~70MB/s, up from 256k on the beta)
Of note to me is this error in my event log 13 minutes before the drive disappeared:
"The shadow copies of volume E: were deleted because the shadow copy storage could not grow in time.Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied."Source: volsnap, Event ID: 25, Level: Error
followed by:
"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume17.(The physical resources of this disk have been exhausted.)"Source: Ntfs (Microsoft-Windows-Ntfs), Event ID: 140, Level: Warning
I figure the amount of space available to me before I start encountering physical limits is in the vicinity of about 7TB. It dropped out for the second time at 184 GB.
FYI, the number of columns created for me is 5
Regards,
Steven Blom

MD3600i Virtual Disk creation issue

I am adding a MD3600i (with MD1200 expansion) to a new Windows 2012 File Server Cluster. I have the Array connected and configured up tot he point of creating Virtual Disks. When I attempt to create a disk, the "Working" spinner pops up and then disappears almost instantly. The wizard never loads.
- I have tried MDSM from the Resource Disk versions 4, 5, and 6 - no change.
- I have removed and re-added the array multiple times.
- I have updated to the most recent Controller Firmware.
- I have tried both In-Band and Out-of-Band management connections.
- I have tried with both Pools and Groups.
- Out-of-band management stations have been both Windows 7 and 8.1
When running the Create a Pool wizard, I can create equally sized Virtual Disks at the end of the process but i cannot create additional drives in the remaining free space (more than enough available to accommodate a drive).. I need to be able to create Drives as needed, please help!

Hello, RSPatial.
It sounds like you've done a number of things, which is great. I think you're headed in the right direction. I'm curious about a couple more things: 1. You did some updates, and I'm curious if you've booted the whole stack (in the right sequence) after that. 2. What revision are the EMM's in the MD1200 on? (or did you update those too?)
It's sounding like there's a hang up between what MDSM see's and what's there which is affecting what's usable.
Another thing you might try is, closing the MDSM, stopping the "SMagent / SMmonitor" services, waiting a good minute, and then starting them again. Then relaunch MDSM.
Let me know if you have any luck.

Server 2012 - iSCSI Virtual Disks Missing After Reboot

Hi guys. I recently had to reboot my Windows 2012 Storage Server. When it came up, the physical disks that the iSCSI virtual
disks reside on were visible, as were the VHD files, but the targets were gone. I looked in the File and Storage Services -> iSCSI but it says 'There are no iSCSI virtual disks', even though the VHD files are clearly there. When I try to import
the already existing ones, it gives me an error because that file already exists in the place I want to put it. These are very large VHD files so moving them to other storage and then re-importing them could take days, if not longer.
The iSCSI targets are still visible under 'View All Targets', but they are no longer associated with their VHD files. How do I reassociate
them? And why did the list of VHD files in File & Storage Services->iSCSI disappear in the first place!?
Thanks for any help!
-Warren

Hi guys. I recently had to reboot my Windows 2012 Storage Server. When it came up, the physical disks that the iSCSI
virtual disks reside on were visible, as were the VHD files, but the targets were gone. I looked in the File and Storage Services -> iSCSI but it says 'There are no iSCSI virtual disks', even though the VHD files are clearly there. When I try
to import the already existing ones, it gives me an error because that file already exists in the place I want to put it. These are very large VHD files so moving them to other storage and then re-importing them could take days, if not longer.
The iSCSI targets are still visible under 'View All Targets', but they are no longer associated with their VHD files. How do I reassociate
them? And why did the list of VHD files in File & Storage Services->iSCSI disappear in the first place!?
Thanks for any help!
-Warren
Replying to this question to answer it with a working solution. I'm not sure what the other replies marked as answers to this post are trying to answer, but they are completely unrelated to this topic. It appears they are describing a fix for a server acting
on the initiator side connecting to a target, not a server acting as an iSCSI target hosting LUNs. Very frustrating to say the least.
I ran into this problem over a weekend maintenance project where I rebooted a Server 2012 R2 File Server to enable some updates. When I logged back in, the iSCSI section was blank and my two existing iSCSI virtual disks had vanish. Now with that said the
underlying file system that the VHDX files were located on was intact. I tried to import them and got the same error that the path was already in use.
I first tried the fix mentioned lower in this thread where you move the VHDX file into another folder to change the path. That worked, but I wanted to figure out exactly why it broke and get my old file to load as it should. Now I don't know the answer to
"why" but I found a way to clear the existing information stored that is preventing you from re-mounting the existing iSCSI files without changing the path.
From this page, there are PowerShell scripts outlined to change iSCSI parameters from the command line.
http://blogs.technet.com/b/filecab/archive/2012/06/08/iscsi-target-cmdlet-reference.aspx
This command in particular deletes the record of unassigned virtual disks that aren't assigned to a target:
$AllDisks | where {$AssignedDisks -notcontains $_} |
foreach {Remove-IscsiVirtualDisk $_ }
After running that command that broken link that had existed prior was removed and I was able to re-mount my iSCSI virtual disks without that error coming up.
As always, make sure you have a backup before you try any odd powershell commands. That one worked for me.

Using a ZFS volume with encryption on as the Virtual disk in a Sparc VM

Hi guys,
Working my way through understanding how virtualization works in VM for Sparc. One question I thought of deals with having encryption turned on in a ZFS volume. If I create a volume with encryption ON, and then attach that volume as the sole virtual disk in a guest domain, will the virtualization still work? Has anyone else dealt with a scenario like this? I'm about to try it now, I'll report back with my findings.

From my understanding, if you create a ZFS disk with encryption ON, mount it on Solaris, and after that present that to the VM, you should not have problems. The encryption will work between the volume and Solaris. To the guest vm, it should be transparent.

There is no more space for virtual disk ServerName_2.vmdk. You might be able to continue this session by freeing disk space on the relevant volume, and clicking Retry. Click Cancel to terminate this session.   Time: 30/05/2014 1:16:20 AM

Recently, our mail server crashed at about 7pm one night, with the error 'There is no more space for virtual disk ServerName_2.vmdk. You might be able to continue this session by freeing disk space on the relevant volume, and clicking Retry. Click Cancel to terminate this session.'
When we click Retry, the server starts up OK.
There are no snapshots listed in Snapshot manager for any of the virtual machines on the host.
There is also free disk space available on the host and for the VM with the disk errors.
This happened at least three more times, often at bad times. Each time, we were able to click 'Retry' and the disk/system would allow the VM to start-up successfully.
I checked the Forums, the VMware support articles and the internet as I had not seen this problem before. I have completed the VSphere 5.1 - Fast Track course and this issue was NOT covered in the training.
Most of the advice on-line and even that on the VMware web-site was pointing to snapshots being the cause of this issue. There are no snapshots enabled and I cannot see evidence of snapshots ever being used.
- We are running VMware vsphere (5.1.0) and there are (were) 4 virtual machines running on the ESX host. We are using the free version of VMware/ESXi.
- The Hard disk types we are using for this Virtual Machine are 'Thin Provisioned'.
- There are 4 [Thin Provisioned] Hard Disks for this virtual machine.
- There are 6 CPUs
- There is 20GB of RAM (memory)
- The VM is running Windows Server 2008 R2 as the guest/VM operating system. It is an Exchange 2010 SP1 mail server. There is plenty of available disk space on all the drives. The [Exchange] log files are cleaned out regularly (automated).
I decided to move one of our non-critical servers off this host and on to another host to see if this helped the problem. This took quite some time, as we are not using HA or vmotion, nor do we have VCenter Server...nonetheless, I finally managed to get the non-critical server on to another host (n.b. This was a much smaller machine with less virtual resources assigned to it).
After moving the non-critical server off this host, we decided to monitor the Host and see if the issue resolved itself.
I checked the host about 6-10 times a day, from first thing in the morning till last thing at night - monitoring the performance of not only the Virtual Machine, but the ESXi host also.
There were no adverse performance issues. The only thing I did note, was in the Summary page on the ESX Host, under Storage, was If I right-clicked on the datastore and clicked refresh, then the free disk space would drop (ie from 140GB to 125GB).
After monitoring the host and VM for about 2 weeks, we did NOT have another instance of the above error.
Sorry for the long winded post, but I wanted to give as much detail given this error has been raised before and snapshots are usually blamed as the cause.
My question is this:
If the ESX host had plenty of available disk capacity and there were no snapshots enabled on the VM (or any other VM's on the same host), then why did our Virtual machine crash with the error that 'there is not more space for virtual disk Servername_2.vmdk'?
How do we prevent this issue from happening if we don't know the underlying cause?
I would greatly appreciate any advice or suggestions.
If I have not provided enough info on the specs or environment, please let me know and I will provide more information.
Thanks all,
Kurt

The type of storage is really based on your requirements, and your ability to withstand downtime.
iSCSI as you are using with a NAS such as Synology or QNAP. NAS Selector - Support - Synology - Network Attached Storage (NAS)
I wouldn't use iSCSI for Exchange or any database. It's a bit slow.
Do you have a single physical host? Then I'd probably to an external direct attached storage. This would be a card inserted in your host server that gives you multilane SAS/SATA connectivity (www.techcable.com/SAS-SATA/SAS-SATA.pps) and an external disk enclosure/array.
For multiple hosts to a single array, I recommend a fibre channel connection to a FC capable switch, and on to a FC connected array.
We used to use a HP P2000 (on old G1), but it's since been retired. Worked pretty well once firmware was upgraded. http://www8.hp.com/us/en/products/disk-storage/product-detail.html?oid=4118559#!tab=features. They can be connected via iSCSI, Fibre Channel or 6GB SAS so they are flexible and reasonably priced.
Recommendations:
     Use RAID 6 with your large disk arrays. With large disks there is a measurable failure rate when rebuilding a failed RAID5 array based on MTBF.
     Use smaller 15K disks in RAID 0+1 for speed on databases/Exchange.
     Use slower 7.2K disks in RAID6 for file storage.
We are a small hospital and we have 3 VMware servers with dual CNA (FC and Ethernet in a single twinax cable) connections to 2 redundant Cisco Nexus 5K switches and then 4 Fibre Channel connections to an EMC VNX 5300. It's extremely fast with about 50 virtual servers, but was quite an investment. One thing we don't have to worry about is down time. If there ever is an equipment failure, we have redundant everything, including power split between two UPSs.
Our VNX has 3 tiers of performance. 3 100GB SSD "Fast Cache" in RAID 1 with hot spare, to keep the most used data ready, but it's not really a tier, however one could be built utilizing the same disks. A second tier is performance tier with a 8 600GB RAID 0+1 and hot spare. The third is a bunch of 7.2K 3TB disks in RAID6. The VNX autotiers, placing data on disks depending on where it's needed. The volumes are sliced and diced automatically in the background to make this happen and we never have to touch it. I used a demo of Solarwinds Storage Manager to monitor performance for a while and the utilization was always low, meaning all data access was fast, througout the day.
D

Can Windows Server Backup spread a single backup job across multiple disks if they are not set up as a virtual disk?

This may be a dumb question, but I can't seem to find any definitive information after having done many, many searches. Short question is - can Windows Server Backup spread a single backup job across multiple disks if they are not in a storage
pool or some other RAID/JBOD structure?
Background:
I'm running Server 2012 Essentials with all Windows Updates installed. I have been backing up approx 2.8TB of data (Bare Metal Recovery, C:, S: (shared folders), and system reserved) for the past year+ onto a storage pool made up of two-2TB external
USB drives. Backup is slow (takes approx 1.5 days to complete), but generally works. Not surprisingly I was constantly getting capacity low messages so I decided to increase my backup storage pool by adding a 3TB drive and another spare 750GB drive
for a total of 7.75TB. Instead of having four separate external USB enclosures, I bot a 4-bay enclosure - Startech.com model #S3540BU33E to simplify this (or so I thought!).
The first problem I had was adding the two new drives to the existing storage pool. I think that is because the Startech uses a JMicron USB controller that reports identical uniqueid's for all drives so only one shows up in the GUI interface for creating storage
pools. After doing research on this, I set up a new storage pool and virtual disk using all four drives via Powershell and thought I was good. However, when the backup ran, it failed after filling the first drive, saying there was no remaining capacity. In
reality there were three remaining empty drives and there storage pool reported almost 5TB of avail capacity. I assumed this was due to the identical uniqueid issue so I decided to try a different tactic.
Instead of using a storage pool that combines all four disks into one virtual disk, I just added each of them to Windows Server Backup as individual drives thinking it would manage them collectively. I.e., when a drive filled up during a particular backup,
it would just start using the next drive and so on. Apparently this was a foolish assumption because the backup failed again as soon as the first disk filled up.
So now I don't know if this is still an issue with the identical uniqueid's or if Server Backup actually can't spread a single backup across multiple individual drives that aren't in a pool or other virtual disk implementation. Hence, my original question.
My guess is that it does *not* spread them across individual disks, but I just wanted to get confirmation.
Thanks

Mandy,
Thank you for following up on my question.
Unfortunately the article you referenced doesn't address what I am trying to accomplish.
The article focuses on saving the same backup job to multiple disks and rotating the disks between on and offsite for enhanced protection. However, it still requires that an individual backup job fits on a single disk.
What I am trying to determine is if a single backup job can span across more than one physical disk (during the backup process) without those physical disks being in some type of virtual disk implementation (e.g., storage pool, RAID, etc.).
Thanks,
Gerry

Oracle VM 2.2: why virtual disk must be 1GB or larger?

I'm using Oracle VM 2.2. When I try to create a virtual disk using OVM Manager it requires that the disk be at least 1GB in size. Is there a reason for this? Or is it an arbitrary limit enforced by OVM Manager?

OK, but it seems like this arbitrary limit provides no benefit. In my case I actually do want a small disk image. I want to use it to pass small amounts of configuration information to a VM at startup, but it seems like this won't be possible via OVM interfaces (I can't create a small private disk image, I can't import an existing disk image, etc). So it looks like I'll have to go under the covers and manipulate the VM image directly.
Am I missing anything? Does OVM Manager provide any interfaces for passing configuration information to a VM at startup?

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]

Creating a Virtual Disk using Diskpart

Hi, I'm trying to study for a test on Windows 7 and I'm trying to install a Virtual disk and I keep getting the same error. The drive has been "cleaned" using the diskpart utility and is a 300 gb drive. here is the code that I used and the error
as copied from the command prompt. Any help would be great Thanks!!!!!!
DISKPART> create vdisk file="C:\test\disk1.vhd" maximum=24000
DiskPart has encountered an error: The system cannot find the path specified.
See the System Event Log for more information.

Hi, slobodan21.
Here is the web page that contains the CREATE vdisk command you have been trying:
http://technet.microsoft.com/en-us/library/gg252579.aspx
I am only guessing but... make sure you create a folder called test in the root of your C: drive.
Good luck!
Best wishes, Davin Mickelson

How to add an virtual disk device

I remember i have seen one doc describe how to add an virtual disk device in solaris system, but I forget it now, can somebody help me?

not sure what you are trying to achieve...
However you should not be referring to Luns via their logical device i.e. c0t0d0, but using the unique did device or the /global device. refer to scdidam -L which will list all the did devices across all nodes and map them to the logical device path.

Cluster Quorum Disk failing inside Guest cluster VMs in Hyper-V Cluster using Virtual Disk Sharing Windows Server 2012 R2

Hi, I'm having a problem in a VM Guest cluster using Windows Server 2012 R2 and virtual disk sharing enabled.
It's a SQL 2012 cluster, which has around 10 vhdx disks shared this way. all the VHDX files are inside LUNs on a SAN. These LUNs are presented to all clustered members of the Windows Server 2012 R2 Hyper-V cluster, via Cluster Shared Volumes.
Yesterday happened a very strange problem, both the Quorum Disk and the DTC disks got the information completetly erased. The vhdx disks themselves where there, but the info inside was gone.
The SQL admin had to recreated both disks, but now we don't know if this issue was related to the virtualization platform or another event inside the cluster itself.
Right now I'm seen this errors on one of the VM Guest:
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 3/4/2014 11:54:55 AM
Event ID: 1069
Task Category: Resource Control Manager
Level: Error
Keywords:
User: SYSTEM
Computer: ServerDB02.domain.com
Description:
Cluster resource 'Quorum-HDD' of type 'Physical Disk' in clustered role 'Cluster Group' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
<EventID>1069</EventID>
<Version>1</Version>
<Level>2</Level>
<Task>3</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-03-04T17:54:55.498842300Z" />
<EventRecordID>14140</EventRecordID>
<Correlation />
<Execution ProcessID="1684" ThreadID="2180" />
<Channel>System</Channel>
<Computer>ServerDB02.domain.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="ResourceName">Quorum-HDD</Data>
<Data Name="ResourceGroup">Cluster Group</Data>
<Data Name="ResTypeDll">Physical Disk</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 3/4/2014 11:54:55 AM
Event ID: 1558
Task Category: Quorum Manager
Level: Warning
Keywords:
User: SYSTEM
Computer: ServerDB02.domain.com
Description:
The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
<EventID>1558</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>42</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-03-04T17:54:55.498842300Z" />
<EventRecordID>14139</EventRecordID>
<Correlation />
<Execution ProcessID="1684" ThreadID="2180" />
<Channel>System</Channel>
<Computer>ServerDB02.domain.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="NodeName">ServerDB02</Data>
</EventData>
</Event>
We don't know if this can happen again, what if this happens on disk with data?! We don't know if this is related to the virtual disk sharing technology or anything related to virtualization, but I'm asking here to find out if it is a possibility.
Any ideas are appreciated.
Thanks.
Eduardo Rojas

Hi,
Please refer to the following link:
http://blogs.technet.com/b/keithmayer/archive/2013/03/21/virtual-machine-guest-clustering-with-windows-server-2012-become-a-virtualization-expert-in-20-days-part-14-of-20.aspx#.Ux172HnxtNA
Best Regards,
Vincent Wu
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.

Startup disk disappear from the desktop

Well, without any reason, The startup disk is disappear from the desktop.
(Just only the startup disk)
I found this 2 times before, once on my 8 cores Mac Pro, once on my iMac G5.
I couldn't do anything to fix them, so I formatted and re-install OS.
with my iMac, it ran Tiger before, there's no problem until I changed to Leopard,
After about 2 weeks under the new Leopard,then the startup disk disappear from the desktop,
it shown the hidden status in disk utility and could not mount it,
So I formatted and back to install old Tiger.
Everything's fine. that's really good Operating system.
Bad luck, about 2 months ago, My iMac G5 had some problem with motherboard and the harddisk also damaged, I send it to Apple Thailand, They fixed it and send back with installed Leopard inside my new hard disk.(well... again)
Now after a few weeks. it happen again.
Startup disk disappear from the desktop.
This problem never exist on my Mac Pro, just with the iMac G5.
(Please don't tell me to check the finder preference about the sidebar setting.
it's already set to show every items there even the iDisk)
I wondered why I don't see anyone have problem with this.
I'm really want to find the answer about this.
I asked this question to Apple Thailand's support team but they didn't have any idea.
Who's gonna answer this

I found a solution to the problem and posted it here:
http://discussions.apple.com/thread.jspa?threadID=1858340&stqc=true
I pasted the solution below:
from a Terminal window, type:
ls -lOd /
(That's lowercase ell, lowercase ess, space, minus, lowercase ell, capital oh, lowercase dee, space, forward slash)
You should get something like this:
hostname:~ username$ ls -lOd /
drwxrwxr-t 32 root admin - 1156 Feb 8 20:35 /
Sounds like you might see something like this instead:
hostname:~ username$ ls -lOd /
drwxrwxr-t@ 32 root admin hidden 1156 Feb 8 20:35 /
(note it says "hidden" instead of "-")
To fix this, type:
sudo chflags nohidden /
and provide your admin password. You won't get any output back from the command but the icon should now appear on your desktop, and the hidden flag should go away if you repeat the 'ls -lOd /' command.
And just in case you missed it above, you've got to be sure Hard disks are turned on in Finder General Preferences under "Show these items on the Desktop"

Two virtual disks with same name - how to safely delete one of them

I mistakenly created a disk in a repository that uses the same friendly name as an existing disk that is in use by a virtual machine.
Can I safely remove the second disk with out OVM trying to delete the original disk as well?
Thanks

Yes, you will be safe, bacause OVM uses the disk ID to identify the disk.
You can also use the little triangle just to the left of the virtual disk name. It will open a message saying if disk is in use by a Virtual machine.
Also, the GUI will not let you delete a disk which is in use.
If you want another way, you can "edit" the disk in the OVMM GUI, read its ID, cancel the edit, and go delete it from a root command shell on the VM server.
br.

Windows 2003 Guest cannot access "SCSI" virtual Disks with /PAE enabled

I created a Windows 2003 EE R2 guest with 16 GB memeory, 48 GB System disk and 4 virtual SCSI disks for Microsoft Cluster services. It all worked, but limited Windows to 3.75 GB memory. When I added the /PAE option to boot.ini, the memory was available, but the virtual SCSI disks were unavailable. Has any else seen this behavior? Is there a work-around? since I need 4 additional virtual disks for the cluster, I cannot make them all IDE drives.

/OVS is on local storage and /OVS/sharedDisks is an OCFS2 formatted logical volume mounted from a Fiber Channel SAN.
--- Logical volume ---
LV Name /dev/vievg/vie_data
VG Name vievg
LV UUID LQJc0N-HkIn-46gQ-RdXc-0eSn-iRVn-VckVbj
LV Write Access read/write
LV Status available
# open 2
LV Size 383.99 GB
Current LE 98301
Segments 3
Allocation inherit
Read ahead sectors 0
Block device 253:0
LABEL=/ / ext3 defaults 1 1
/dev/cciss/c0d1p1 /OVS ocfs2 defaults 1 0
LABEL=/boot1 /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
LABEL=SW-cciss/c0d0p3 swap swap defaults 0 0
/dev/vievg/vie_data /OVS/sharedDisk ocfs2 defaults 1 0
acpi = 1
apic = 1
boot = 'd'
builder = 'hvm'
device_model = '/usr/lib/xen/bin/qemu-dm'
disk = ['file:/OVS/running_pool/77_VHAISPMUL13A/System.img,hda,w',
'file:/OVS/sharedDisk/VHAISPCLU13_L.img,sdb,w!',
'file:/OVS/sharedDisk/VHAISPCLU13_P.img,sdc,w!',
'file:/OVS/sharedDisk/VHAISPCLU13_S.img,sdd,w!',
'file:/OVS/sharedDisk/VHAISPCLU13_Q.img,sda,w!',
'file:/OVS/iso_pool/Windows_2003/en_win_srv_2003_r2_enterprise_with_sp2_vl_cd1_X13-48610.iso,hdc:cdrom,r',
disk_other_config = []
kernel = '/usr/lib/xen/boot/hvmloader'
keymap = 'en-us'
maxmem = 16384
memory = 16384
name = '77_VHAISPMUL13A'
on_crash = 'restart'
on_reboot = 'restart'
pae = 1
serial = 'pty'
timer_mode = 1
usbdevice = 'tablet'
uuid = 'ddab0147-6dde-4a2e-2c00-b883a16058ac'
vcpus = 2
vif = ['bridge=xenbr0,mac=00:16:3E:19:C1:E9,type=ioemu',
'bridge=xenbr1,mac=00:16:3E:55:17:AC,type=ioemu',
vif_other_config = []
vnc = 1
vncconsole = 1
vnclisten = '0.0.0.0'
vncpasswd = 'passw0rd'
vncunused = 1
It works fine without the /PAE flag, so I am wondering if it is an issue with the Windows driver for the sd devices presented by the virtual machine emulator and if there is a way to select a better driver.

Virtual Disk disappeared

Similar Messages

Maybe you are looking for