× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Wow!  Ok, trivia king - what's the type for?  I was looking for it the
other day, and I swore I've seen it before (like for example, 6707-070-x
- what's x mean?) but I can't find it.

Model - Level - Type, I believe it what disks are represented as.  Below
are levels, IIRC.


--
Justin C. Haase - Solution Engineer
IBM Certified Systems Expert - System i
Kingland Systems Corporation

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Leif Guldbrand -
Think400.dk
Sent: Wednesday, January 03, 2007 3:00 PM
To: Midrange Systems Technical Discussion
Subject: Re: Removing a failed drive permanently

And for the archieves - Disk models (may not be up to date):

030 - Unprotected or mirrored unit of a type not supported in HA
controller parity set 
      (520-byte device).

050 - Unprotected or mirrored unit of a type supported in HA controller
parity set membership
      (522-byte device). Data compression inactive

060 - Unprotected or mirrored unit of a type supported in HA controller
parity set membership
      (522-byte device). Data compression active

070 - Non-parity unit of parity set (full capacity, 522-byte device).
Data compression inactive

072 - Parity unit in parity set with 8 parity units (7/8 capacity,
522-byte device). Data
      compression inactive

074 - Parity unit in parity set with 4 parity units (3/4 capacity,
522-byte device). Data
      compression inactive.

080 - Non-parity unit of parity set (full capacity, 522-byte device).
Data compression active

082 - Parity unit in parity set with 8 parity units (7/8 capacity,
522-byte device). Data
      compression active

084 - Parity unit in parity set with 4 parity units (3/4 capacity,
522-byte device). Data
      compression active

Regards
Leif
----- Original Message -----
From: "Larry Bolhuis" <lbolhuis@xxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: 3. januar 2007 21:27
Subject: Re: Removing a failed drive permanently


If the drive is a model 070 then you can remove it from the ASP and
then 
from the RAID set and then from the system. If it's any other 07x
number 
then you need to remove it from the ASP, then end RAID, then remove
it, 
then restart RAID.

  - Larry

Pete Helgren wrote:
I have replaced a failed drive with a new drive before but I'd like
to 
pull one that I have no intention of replacing.  The system is at
only 
20% and losing a 8GB drive will make virtually no difference in
overall 
capacity (this is a seldom used test/development system).

Once I pull the failed drive, what do I run so that the RAID set
"knows" 
that the drive won't replaced and that it has to rebuild the "lost" 
drive using the remaining drives in the set?

Thanks,

Pete Helgren




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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