Tru 64 cluster

[Shehan]

Hi All
There is a tru 64 cluster system.Unable to boot the two mechine simultaneously.When both are booted simultaneously, one is going to shutdown mode automatically.receving beloow messages.


exec: /sbin/mount_advfs -F 0x14000 cluster_root#root /
cam_logger: SCSI event packet
cam_logger: hardware_id=96 bus 6 target 2 lun 0
cdisk_check_sense
Device aborted command
Hard Error Detected
Hardware ID = 96
COMPAQ BF03685A35 HPB7
Active CCB at time of error
CCB request completed with an error
Error, exception, or abnormal condition
ABORTED COMMAND - Target aborted command

Checking for crash dumps
Initializing paging space
Mounting Memory filesystems
cam_logger: SCSI event packet
cam_logger: hardware_id=96 bus 6 target 2 lun 0
cdisk_check_sense
Device aborted command
Hard Error Detected
Hardware ID = 96
COMPAQ BF03685A35 HPB7
Active CCB at time of error
CCB request completed with an error
Error, exception, or abnormal condition
ABORTED COMMAND - Target aborted command

If any body has faced such problem ,pls let me know what did you do it recover.


/Niru

[Vladimir Fabecic]

Can you describe your hardware configuration?
Looks like a SCSI configuration problem to me.

[Ivan Ferreira]

How many nodes do you have in your cluster? do you have a quorum disk? Ensure that SCSI bus is correctly terminated (if scsi). Check your storage and ensure that the LUNS are good and in the running state. What is the data contained in the disk with Hardware ID = 96?

[Shehan]

2 nodes in the cluster
DS25 server with Tru64
There is quroum disk.
IF you can send me a correct cluster diagram ,I can confirm it.
SCSI cables are connected tightly.
yes ,LUN are good state.
How do I check the Hardware ID vs connected disk ?

I am getting a error like below
***ERROR (eie0.0.0.0.2007.0),no Link,auto negotiation didn't detect.

It should be the Ethernet controlller error.
Have seen this type of error

/nirukshitha

/Nirukshitha

[Anthon Vervoort]

Hello all,

It seem to be clear, a ID-Conflict on the SCSI-bus is here the case. Mostly a bad fitted SCSI cable or bad termination.
Look to the SCSI-ID card which mostly is used in combination with the internal SCSI-storage box, these has to be connected on the cable.

Good Luck,

Anthon