DR Testing:

["Matt Patee" <mpatee@xxxxxxx>]

I had a great time this week. I was lucky enough to find a 9406 620 that
was not being used. I began testing for our disaster recovery on Tuesday
using this machine. I ran into a few hickups along the way, including a
dead fan (IBM had to come out and replace), and one of the drives in this
system would not configure.

The system has a total of XX drives. These drives are comprised of a mix of
three differant models. When I configured the drives and started parity, it
left one of the drives out. It was completely unconfigured, and would not
configure, add to the ASP, or begin parity. I called IBM, they helped
partially. They mentioned this was a known issue. All I needed to do was
stop parity, add the drive to the ASP, and then begin parity. This
partially worked. The drive did get added to the ASP but when parity was
started, this drive was not included. I now have an ASP with one
unprotected drive.

I have tried to stop parity and start it again, this does not work. I have
tried to add this to the parity set, this does not work. I have not found
any indications that this drive is malfunctioning in any way. I will call
IBM back, but I thought I would try this forum first. Thank you in advance
for any help.

-Matt

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---