Re: Removing a failed drive from a parity set without replacement

Thanks Patrik,

Yes, that helps.  So I can use SST to remove the failed drive?  I am seeing a couple of instructions that seem to require DST....

Navigating through SST I can't seem to find either a "remove" option under parity protection nor a stop parity protection option.  I see "start" for parity protection and I see "add" for adding a disk but nothing that allows me to stop or remove...

I don't have any external backup device on this system.  I have thought about using using virtual tape for backup but haven't configured it or used it.  So, no way to backup the system right now.


Pete Helgren
www.petesworkshop.com
CISSP - MSCM
GIAC Cloud Penetration Tester
AWS Certified Cloud Practitioner
Microsoft Certified: Azure Fundamentals

On 2/1/2026 6:51 PM, Patrik Schindler wrote:

Hello Pete,

Am 01.02.2026 um 22:01 schrieb Pete Helgren <pete@xxxxxxxxxx>:

A bit of reading says I can remove the drive by using SST to exclude the drive from the parity set and then restart parity protection. Is that all there is to it or is there something else that needs to be done?

I was in a similar situation some time ago.

The most important thing is to realize that stripe set and ASP membership of a drive are distinct functions.

You first need to remove the failed drive from the ASP. This works at runtime, but lessens the ASP size accordingly. Only then you can safely stop parity protection, and restart it, forcing a rebuild and again loss of some space in the ASP. Because the drive failed, it won't be included in parity protection.

When another drive fails during your reconfigurations, you're doomed. I suggest to have a recent save 21.

Does that help?

:wq! PoC