Note: This question is part of a series of questions that use the same set of answer choices. Each
answer choice may be used once, more than once, or not at all.
You have a computer named Computer1 that has storage configured as shown in the following table.
Pool1 contains a storage space named Space1 that is 300 GB.
Pool3 contains a storage space named Space2 that is 100 GB.
Pool2 is empty.
You discover that Distc2 experiences physical errors.
You need to ensure that all of the data in Space1 is stored on other disks in the storage pool only.
What should you use?
A.
Add-PhysicalDisk
B.
Diskpart
C.
New-VirtualDisk
D.
Remove-PhysicalDisk
E.
Resize-VirtualDisk
F.
Set-StoragePool
G.
Subst
H.
Update-Disk
D
Set-StoragePool -EnclosureAwareDefault
https://technet.microsoft.com/en-us/itpro/powershell/windows/storage/set-storagepool
thanks Moo for your comment!
The Remove-PhysicalDisk cmdlet removes a physical disk from a specified storage pool.
If sufficient space does not exist in the storage pool to tolerate this removal, then data loss can result (the user is warned about this). If the user configuration allows, then the user should add a replacement physical disk to the pool prior to removal of the old one.
I fail to see what your option would do to solve the issue.
Sounds like D to me.
I am for D, the Set-StoragePool -EnclosureAwareDefault, “Specifies that the storage pool should use enclosure awareness by default when creating storage spaces.”
We are not creating the storage space now, so this command shouldn’t do anything related to our case.
Storage spaces should automatically detect errors and retire the disk if necessary
“Storage Spaces re-directs the failed write to any of the remaining disks in the pool and the data that was on the disk that failed is similarly re-allocated”
https://social.technet.microsoft.com/wiki/contents/articles/17947.how-storage-spaces-responds-to-errors-on-physical-disks.aspx
that done, you should replace the disk with a new one
at least that is how i see it
I going for F.
“In the event that a disk cannot be written to or read from, but never returns an error, Storage Spaces treats the condition as a transitory failure. The action that Storage Spaces takes is configurable and defined by the Set-StoragePool -RetireMissingPhysicalDisks cmdlet; “Auto” is the default:”
https://social.technet.microsoft.com/wiki/contents/articles/17947.how-storage-spaces-responds-to-errors-on-physical-disks.aspx
Leo,
Looks like our Google-fu took us in the same direction.
I’m still trying to come up with an answer to this one, but the following two documents provide a great deal of help in understanding Storage Spaces.
https://social.technet.microsoft.com/wiki/contents/articles/17947.how-storage-spaces-responds-to-errors-on-physical-disks.aspx
—————————–
This article explains that when there are physical errors on a disk in a Storage Space/Pool, it is automatically handled by moving the failed write to unused space on another disk in the pool. Furthermore, it will mark the disk as “unhealthy” and the Storage Space as “degraded”. If future writes to the disk succeed, the disk returns to “healthy” and the Storage Space will remain “degraded” antil a user-initiated repair or re-synchronization occurs.
https://technet.microsoft.com/en-us/library/dn782852%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396
——————————
This article goes into great detail on the process of replacing a failed disk. Essentially, you add the new disk to the pool using “Add-PhysicalDisk –StoragePool $Pool -PhysicalDisks $NewDisk -Usage Automatic”, you identify the failed disk and use “Set-PhysicalDisk –Usage Retired” to take the failed disk offline, then use “Get-StoragePool –FriendlyName | Get-Virtualdisk | Repair-VirtualDisk -Asjob” to repair the pool.
So… It looks like Windows will automatically begin the process of using disks other than the failed disk as soon as failed writes begin. The first step in the process of remediating the failed disk is to add another.
Did I muddy the waters enough? 😉