Nocandoboss.

With SAS drives IBM never recommended expanding RAID sets like we did in the SCSI days. With more recent updates I believe the capability has been removed.

Having drives with and drives without RAID data was causing issues, especially performance issues.

The next issue is the maximum drives in a RAID set is, if I recall correctly 18. So you are at the limit anyway.

As to starting a new RAID-5 with hot spare, that one doesn't make sense. If the drives are the same FC #5B11 then the hot spare from that should allow this to start with no issue.

Have you tried to initialize and format first to see if that clears anything? Would be no loss in time as the Start RAID is very fast after an init and format.

- DrF

On 11/18/2021 12:33 PM, Rob Berendt wrote:
I have these drives:
4. Display non-configured units
Serial Resource
Number Type Model Name Capacity Status
Y210ZAK156B8 5B11 105 DMP143 775912 Non-configured
Y210ZAK15A0H 5B11 105 DMP141 775912 Non-configured
Y210ZAK15ARA 5B11 105 DMP139 775912 Non-configured
Y210ZAK15AQG 5B11 105 DMP137 775912 Non-configured

I have two ESLS on a 9009-42A. Two have been added to one and two to the other. Each ESLS now has a total of 19 drives.
I have two RAID5 parity sets with hot spare.

I'd like to add these drives to these raid sets.
3. Work with disk unit recovery
5. Delete disk unit data
2. Work with disk configuration
8. Work with device parity protection
2. Include unit in device parity protection
Include Device Parity Protection Failed

There are no disk units eligible for the selected operation
due to one or more of the following reasons:

o All the device parity capable disk units are already device
parity protected.
o If there are enough number of disk units available to create
a new parity set, then those units will be eligible for 'Start
Device Parity Protection' operation and not for the 'Include
Device Parity Protection' operation. Refer to the Backup and
Recovery Guide for more details.
o All the disk units in a parity set must be the same capacity
with a minimum number of either 3 or 4 units, and a maximum
number up to 18 units (depending upon the type of adapter)
in the resulting parity set.
o An IOA is in a condition that makes the disk units attached to
it read/write protected. Examine the 'Product activity log'
for any reference codes that are logged for the IO subsystem
and follow the appropriate procedure for the reference code to
correct the problem, if necessary.
o Not all disk units attached to an advanced function IOA have
reported to the partition. Retry the operation.
o The type/model of the disk units is not supported for the
requested operation.
o The device parity units are under a type of IOA which
requires an auxiliary write cache adapter.

Not that I wanted to do it this way but
5. Start device parity protection - RAID 5 with hot spare
Also fails

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.