failed boot HP9000/K460

[Mike_Ca Li]

I'm experiencing similar issue after I replaced a SCSI disk. Old thread is "failed boot HP9000/D350"
Originaly I had 4 X 9 GB with IDs 3, 4, 5, 6
I had /dev/vg00 on /dev/dsk/c0t1d0 and /dev/dsk/c0t2d0 (mirrored)
and vg01 on /dev/dsk/c0t3d0 and /dev/dsk/c0t4d0
I broke the mirror for vg01 and vg01 only had c0t3d0.
I want to replace c0t4d0 with a 36 GB disk

I disconnected disks with IDs 5 and 6 and replaced with new SCSI HD ID 6.
Getting the WARN 80F5 error and can't find the boot device (cannot find ENTRY_TEST).
I did a SEA to search for a boot path:
P0 10/0.8 fwscsi.8 Random access media
P1 10/0.4 fwscsi.4
P2 10/0.3 fwscsi.3
P3 10/12/5.0 sescsi.0

Pri is set to 10/0.6 , my question is that did I replace/disconnected the boot devices?
Anyone has idea how SCSI Id is related to fwscsi.## ? Thank you

[Andrew Rutter]

hi,

what you appear to have done is removed 2 discs with an id of 1 and 2 and replaced it with 1 disc with an id of 8.

your output shows that vg00 was 2 discs with id 1 and 2
I had /dev/vg00 on /dev/dsk/c0t1d0 and /dev/dsk/c0t2d0

and vg01 with 2 discs with id 3 and 4

you have removed discs id 1 and 2 which is the vg00 and your boot discs.
you need to put the 2 boot discs back in and remove the disc with id4 if thats the one you want to change. check the jumpers on the drive to work out which is id4. If you have 4 discs in there you will need to check there scsi id's aswell as there is a conflict on the scsi bus. thats why you only show 3 disks?

This is why you have got the error trying to boot.
Also I would change the pri boot path to the correct one for your boot drive.

The scsi id is the same as the fwscsi number and the target number shown in c0tXd0

X= id number of disk in binary

Andy

[Victor BERRIDGE]

Hi,
Lookd like you removed vg00...
The default on K class with mirrored system disk would be for example:
disk 13 10/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c1t5d0 /dev/rdsk/c1t5d0
disk 0 10/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c1t6d0 /dev/rdsk/c1t6d0

2) the scsi ID is related to the target t while the controller is c

All the best
Victor

[Victor BERRIDGE]

I would like to add I dont see why you coulnd install vg00 elsewhere... I do...
# ioscan -funC disk|more
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
disk 3 8/0.1.0 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c4t1d0 /dev/rdsk/c4t1d0
disk 6 8/0.1.1 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c4t1d1 /dev/rdsk/c4t1d1
disk 7 8/0.1.2 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c4t1d2 /dev/rdsk/c4t1d2
disk 8 8/0.1.3 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c4t1d3 /dev/rdsk/c4t1d3
disk 9 8/0.3.0 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c4t3d0 /dev/rdsk/c4t3d0
disk 10 8/0.3.1 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c4t3d1 /dev/rdsk/c4t3d1
disk 11 8/4.1.0 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c5t1d0 /dev/rdsk/c5t1d0
disk 14 8/4.1.1 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c5t1d1 /dev/rdsk/c5t1d1
disk 15 8/4.1.2 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c5t1d2 /dev/rdsk/c5t1d2
disk 16 8/4.1.3 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c5t1d3 /dev/rdsk/c5t1d3
disk 17 8/4.3.0 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c5t3d0 /dev/rdsk/c5t3d0
disk 18 8/4.3.1 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c5t3d1 /dev/rdsk/c5t3d1
disk 19 8/8.0.0 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk 20 8/8.0.1 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c6t0d1 /dev/rdsk/c6t0d1
disk 2 8/8.2.0 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c6t2d0 /dev/rdsk/c6t2d0
disk 5 8/8.2.1 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c6t2d1 /dev/rdsk/c6t2d1
disk 21 8/12.0.0 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 22 8/12.0.1 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c0t0d1 /dev/rdsk/c0t0d1
disk 4 8/12.2.0 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c0t2d0 /dev/rdsk/c0t2d0
disk 12 8/12.2.1 sdisk CLAIMED DEVICE HITACHI DF400
/dev/dsk/c0t2d1 /dev/rdsk/c0t2d1
disk 13 10/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c1t5d0 /dev/rdsk/c1t5d0
disk 0 10/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c1t6d0 /dev/rdsk/c1t6d0
disk 1 10/12/5.2.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5701TA
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
dims2:home/lgdm # vgdisplay -v vg00|grep dsk
PV Name /dev/dsk/c0t0d0
PV Name /dev/dsk/c6t0d1

E.G: On external subsystem

All the best
Victor

[malvin drakley]

Hi Mike it might be you have got several devices with the same address and or they are not the right interface type. The hard drives on a K460 are of the fast wide differential type and the drive you put in must conform to that same standard. These drives are also known as HVD.(High-voltage differential) and you cannot mix up other types of drive with this kind of interface. I enclose a page with the link settings for the rear of the drive it is of some help.
hope this helps a bit. If you want a good guide to scsi types go to www.paralan.com/scsi.html
hope this helpd
malvin

[Mike_Ca Li]

Thanks for replies, I have ST19171WD and check the jumper settings of the 4 disks. I thought they had SCSI IDs 3, 4, 5, 6? How come it's c0t1d0 to c0t4d0 ?

So 10/0.2 and 10/0.1 (fwscsi.2 and fwscsi.1) each had SCSI Ids of 5 and 6?

[Mike_Ca Li]

I have the new ST36704LCV which I want to use to replace one of the ST19171WD on a K460
Is that compatible?

[Andrew Rutter]

hi again,

I think you missed a number out of the st part number

If its ST336704LCV then no its not compatible. This drive is LVD scsi and not HVD like what you need for the K class.
however if its the LCV version this is actually 80 pin sca connection so would not even physically fit into the server. The internal discs in the K class are 68pin connection.
Also these disks are 10k rpm and the supported drives are only 7200rpm, so you could run into heat issues possibly.

Is it internally to the K class you installing them or in external storage?

If its internal it wont fit/work.

andy