Forum Discussion

bradn2k1's avatar
bradn2k1
Novice I
3 years ago

We are building out a PureArray environment. Here's

We are building out a PureArray environment. Here's my issue: I created a volume based on volume on a machine1, when i tried to connect that new volume to machine1 it shows up for about 30 second and just disconnect. Does anyone know what the issue is? I'm able to connect this new volume to another machine without any issues.
  • Get-Disk | ? { $_.SerialNumber -eq $diskSerial } | Set-Disk -IsOffline $False
  • thank you - i tried out that diskpart script and when i online the drive - it's still complaining that the disk is read only. --> Set-Disk -IsOffline $False then the disk just disappears and dont;' show up in diskpart anymore. Not sure why that's the case
  • Are you including the _attributes disk clear readonly_ part as well?
  • Try going through manual process first before automating… Also try sending it to a intermediary server first, and re-signaturing it there, and bringing it back
  • For any disk refresh solutions, I almost always direct customers to leave the original source machine alone, and use another server as the data refresh location. Then we just resignature as the disk lands and never have to worry about GUID conflicts. Not sure what your use case for this copy is though.
  • high-level: we have a machine that get log restores from prod data. We want to clone that volume then mainpulate files on new clone number i.e. rename files. Then clone this new volume to attach to other dev machines.
  • Can you rename the files once the drive is attached to final server? Is this part of like a datascrub to remove production information before it hits dev/test??