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

Hello Pete,

Am 02.02.2026 um 17:47 schrieb Pete Helgren <pete@xxxxxxxxxx>:

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....

Options being available in SST in addition to DST depend on your OS release. Example: I was surprised that 7.2 has the capability to remove a drive from an ASP from with in SST — while the machine is fully running. That wasn't possible with V4R5. :-)

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 have no access to a machine running IBM i in the primary LPAR anymore. So everything I assert is from memory.

I think it's not possible to remove single devices from a RAID5. It's only possible to entirely stop RAID5 (aka parity protection), and start it. Upon starting, you might be asked which disks to include in the RAID set, but I'm not sure here, either.

Anyway, the first step to take is to remove the failed disk from the ASP. This should work from SST, see above. I can't recall if RAID management can be done from SST or must be done from DST.

Sorry for the incomplete advice.

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.

Uh, this might bite you, if another disk fails in the process of reconfiguration.

:wq! PoC