physical drives changed device numbers

[Belinda Dermody]

Hard to explain, I was replacing a old 1 gig drive in a SE6000 box on our HP9000 H50 system HP-UX 11.00. The device path at first was /dev/vg02 /dev/dsk/c0t5d0. We realized after boot that we pulled the wrong drive. We put the original drive back in and now the path shows up as /dev/dsk/c0t0d0. I can not do a vgreduce or a pvcreate for the new drive and the system is still showing us /dev/dsk/c0t5d0, although ioscan and diskinfo is showing us /dev/dsk/c0t0d0 not t5. Is there any way we can force the address or anything that we can do

[harry d brown jr]

It looks like you changed the SCSI id. Did you put the drive back in the ORIGINAL place???

live free or die
harry

[Belinda Dermody]

Yes, we did, it was completely filled we replaced a big C3010M 1 gig drive with a new barracuda 4Gig. We realized our mistake and took the 4 gig out and put the 3010M back in.

[Wim Rombauts]

This is purely a SCSI-address problem. You cannot solve this on your server, this is something you have to do on the diskbox or the disk itself.

How do you normally set SCSI addresses on your disks ? Is it with switches on the disk itself ? Maybe a jumper that has fallen off, a switch that has been touched, ...

[pap]

Hi,
This is a SCSI address problem.

You need to take out the drive again and check for the SCSI ID for that drive.

Put the SCSI address "5" and then reinstalled the drive in the machine. Hopefully you will resolve your problem....

-pap

[harry d brown jr]

James,

tear open the 6000 again and double check the cables, because each one has a scsi ID, which is set in the back of the 6000 unit. Also check your jumpers.

Also have a look at this thread:

http://bizforums.itrc.hp.com/cm/QuestionAnswer/0,,0x3bfa5f260cafd4118fef0090279cd0f9,00.html

Here's the jumper settings:

http://www.pc-disk.de/pcdisk/h/JUMPERS/361.HTM



live free or die
harry

[Mark van Hassel]

Hi James,

What you can do is vgexport the volume group and then vgimport it with the new physical volume name.

HtH,

Mark

[Vincent Farrugia]

Hello,

You removed the SCSI ID jumpers. Put them again in place. For SCSI ID 5, pins 6 and 8 should be shorted with jumpers.

HTH,
Vince

[Sandip Ghosh]

Hi James,

I think you have missed one cable which is running from the SCSI ID switches from the back to your disk. You need to attach this to the disk to set the SCSI ID. It has taken c0t0d0 because you didn't havr that small cable in place .

Sandip

[Sachin Patel]

Hi James,
Easy way to use vgimport using that new disk path.
Then vgchange, fsck and vgcfgrestore.

Sachin

[harry d brown jr]

For those of you that have never seen a 6000 rack, it has scsi addressing in the back of the rack via dip switches. There are 5 bays, each has a disk power cable and scsi cable.

The one thing you usually don't do is set the scsi address on the disk, because that is what the dip switches are for, and frankly I'm not sure what would happen (if anything), if you set addresses on the disk drives themselves.
James, did you replace the bad disk with the barracuda? If you did, did you make sure you didn't set the scsi address? If you have it set, it might be conflicting with your original good disk. Another possibility is that the dip switches need to be rocked on and off back into their original settings.

live free or die
harry