Integrity Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

Replaced bad internal disk and new device created....why?

 
SOLVED
Go to solution
dev44
Regular Advisor

Replaced bad internal disk and new device created....why?

rx6600
HP-UX 11.31

This is for VG01. We have two internal disks mirrored (c0t2d0 and c0t3d0). c0t2d0 is located in enclosure 1, bay6 and c0t3d0 is in enclosure 1, bay5.

c0t2d0 died, but all was fine due to the mirroring. So we got a replacement disk from HP (same as the old one) and I popped it in figuring it would be seen and then rebuilt - which is what always happened for any parisc system this happened on for me.

Problem was a new device was created. Even though I replaced the disk - same bay and enclosure. I called HP and we couldn't get it to go to c0t2d0 which continued to show NO_HW. We then popped the disk back out ... did rmsf of both c0t2d0 and the new device that was created c0t4d0. Popped the disk back in and still it went to c0t4d0. So basically after vgscans and vgcfgrestores, the disk rebuilt and all is fine.

So my question is why, would it create a new device? Why could I not just take the bad disk out and put the new disk in the same spot and it just rebuild/sync/etc?

Thanks,
Sally
whatever
2 REPLIES 2
Torsten.
Acclaimed Contributor
Solution

Re: Replaced bad internal disk and new device created....why?

This is pretty normal :-(

See the procedure:

http://docs.hp.com/en/5900-0112/ch04s05.html

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
dev44
Regular Advisor

Re: Replaced bad internal disk and new device created....why?

Thanks Torsten....
whatever