Re: 8203-E4A RAID5 vs. ASP protection -- MIDRANGE-L

Subject: Re: 8203-E4A RAID5 vs. ASP protection
From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
Date: Thu, 29 Feb 2024 09:20:14 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Yup, the asterisks just show the drive is not added to an ASP (of any type). In order to remove that drive from the RAID set, you would need to manual IPL into DST. I’m not sure which controller you have but back in the day the minimum number of drive units was four, so I doubt it will let you remove that drive from the RAID set.

Hope not being a strategy is an axiom, but here’s hoping your system does not go castors up until after it’s no longer needed…...
--
Jim Oberholtzer
Agile Technology Architects

On Feb 29, 2024, at 9:10 AM, Patrik Schindler <poc@xxxxxxxxxx> wrote:

I found a "Work with Device Parity Protection" screen in SST where I see the ASP-removed disk displayed with asterisks, and still being part of the RAID set.

Apparently V7R2 supports removing a disk from an ASP in SST while the system is up and running, but not from a RAID set. Need to check in DST.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: 8203-E4A RAID5 vs. ASP protection , Patrik Schindler

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.