Lovely. I've seen this before as well. Problem is that the new units haven't been identified yet. Usually the Initialize and format will wake them up but you're getting an error. Try the other and see if it's the same because maybe the disk really is bad or possibly is OK but didn't properly connect.

Seems like another thing I've done is to leave the slots empty for a few hours and then insert the new drives. Something must trigger the system to know the 70s are gone so that when it sees new drives it checks them out and doesn't just assume they are the 70s coming back.

- Larry

On 9/14/2012 11:25 AM, rob@xxxxxxxxx wrote:
Thank you.

I used the Concurrent Maintenance and removed all four.
Stuck the four new ones about half way in.
Did Concurrent Maintance on the first two and got them shoved in and it
says ok. Read a bunch of email, did some sample sql to reply to someone's
email, etc. Configuration status still shows the four old S/N's and
models and non configured. Figured WTH and went on.
3. Work with disk units
3. Work with disk unit recovery
2. Disk unit problem recovery procedures
1. Initialize and format disk unit
Still shows those darn 4327's
Serial Resource
Number Type Model Name Status
68-0C69B15 4327 050 DD016 Non-configured
68-0A7335D 4327 050 DD015 Non-configured
21-93EBE 4327 050 DD017 Non-configured
21-015FF28 4327 050 DD018 Non-configured
Picked this one
68-0A7335D 4327 050 DD015
Since it was in the first slot of the two disks that I put in.
Cannot determine if unit possibly configured
F10=Ignore problems and continue
Press F10 to confirm your choice for 1=Initialize and format.
Error or Problem
Disk unit I/O failure, check reference code
The system encountered an error while it was attempting to
read or write to a disk unit.
Contact your service representative with the following
--Reference Codes--
Serial Resource I/O
Number Type Model Name Processor Device
68-0A7335D 4327 050 DD015 0000 3002

Rob Berendt

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page