tag:blogger.com,1999:blog-5670048373005177198.post4186722874439268446..comments2023-03-03T09:41:25.812+01:00Comments on Core four: Replacing a vSAN caching disklarstrhttp://www.blogger.com/profile/05963794523825848062noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5670048373005177198.post-29763468387048028502015-11-21T20:26:00.683+01:002015-11-21T20:26:00.683+01:00Thanks for your good input here, Christian. I thin...Thanks for your good input here, Christian. I think we already tried to do what you suggest, but had an error message(?). I'm no longer having a system with this problem and I'm unable to verify it. Will try again next time. larstrhttps://www.blogger.com/profile/05963794523825848062noreply@blogger.comtag:blogger.com,1999:blog-5670048373005177198.post-76278146642893351432015-11-21T19:57:25.271+01:002015-11-21T19:57:25.271+01:00Hi, this is Christian from the VSAN Engineering te...Hi, this is Christian from the VSAN Engineering team. You don't need to use partedUtil. You can't delete the "Absent" disk, but you don't have to. In this case you know the drive is dead and won't return, and what you want to do is make sure you free up the capacity tier drives so that you can reuse them to build a new disk group with a new cache SSD. To do that, simply click on the capacity tier drives in the UI and hit the "Remove" button (note, if you are in "Automatic" claim mode at the cluster level then this button is hidden, so be sure to switch to Manual). This allows you to free up those drives and repurpose them, e.g. for a new disk group. Once all the capacity drives are freed up, the "Absent" SSD will automatically disappear. It was just shown in the UI so we could still represent the old disk group in a meaningful way. Christian Dickmannhttps://www.blogger.com/profile/12436493288031924353noreply@blogger.com