G
Geri The IT
Hello Everyone,
Before 3 month I have set up a failover cluster with 2 nodes-Windows Server 2019. The nodes and the storage are located in Azure.
The cluster is configured with Storage Direct Spaces and I have follow this link : Deploy a two-node Storage Spaces Direct SOFS for UPD storage in Azure
The cluster was working fine until yesterday.
I needed to add two extra 1TB disk on each node, but by mistake I added three 1Tb disk on each node and after seeing my mistake I deleted from the azure portal the extra 1TB disk.
And here the problem started, what I didn’t know was that the Storage Direct Spaces is auto-pooling every new disk that is added to the servers and allocating data inside. On the disks that I have deleted they were allocated around 30Gb of data. And now the 2 disks that I have deleted are in Retired state.
I have try repairing the disk but they are stuck here for hours and hours.
And when I try to remove the retired disks directly from failover cluster manager is giving this error.
Please anyone with this kind of experience, I really need help J
Continue reading...
Before 3 month I have set up a failover cluster with 2 nodes-Windows Server 2019. The nodes and the storage are located in Azure.
The cluster is configured with Storage Direct Spaces and I have follow this link : Deploy a two-node Storage Spaces Direct SOFS for UPD storage in Azure
The cluster was working fine until yesterday.
I needed to add two extra 1TB disk on each node, but by mistake I added three 1Tb disk on each node and after seeing my mistake I deleted from the azure portal the extra 1TB disk.
And here the problem started, what I didn’t know was that the Storage Direct Spaces is auto-pooling every new disk that is added to the servers and allocating data inside. On the disks that I have deleted they were allocated around 30Gb of data. And now the 2 disks that I have deleted are in Retired state.
I have try repairing the disk but they are stuck here for hours and hours.
And when I try to remove the retired disks directly from failover cluster manager is giving this error.
Please anyone with this kind of experience, I really need help J
Continue reading...