topic Re: Problem when adding a new drive in Operating System - HP-UX

Problem when adding a new drive

James Colby — Mon, 29 Sep 2003 15:05:45 GMT

Hi everyone -

I have recently replaced a failed external hard drive on my L4000. I am not able to use the pvcreate command or the diskinfo command on the new drive. Those commands just hang and I have to kill them. I have verified that the device is terminated and that termpower is being supplied. I did however find an error in my syslog. The error tells me to run resdata, does anyone have idea what this means or how to fix it?

CURRENT MONITOR DATA:

Event Time : Mon Sep 29 15:08:39 2003
Hostname : xxx IP Address : xxx.xxx.xxx.xxx
Event Id : 0x003f78833700000000 Monitor : disk_em
Event # : 100091 Event Class : I/O
Severity : CRITICAL

Disk at hardware path 0/0/1/0.0.0 : Software configuration error

Associated OS error log entry id(s):
0x3f78833700000000

Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100091

Description of Error:

The device is in a condition where it requires action on the part of the
device driver or a human operator.
Probable Cause / Recommended Action:

The device has been reset by a Bus Device Reset message, a hard reset
condition, or a power-on reset.

If this is the case, no action is necessary.

Alternatively, a removable medium has been loaded or replaced.

If this is the case, no action is necessary.

Alternatively, the mode parameters, microcode, or inquiry data for the
device have been changed.

If this is the case, no action is necessary.

Alternatively, the installed version of the device driver does not match
that of the installed version of HP-UX. Install the correct version of the
driver.

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v

Product/Device Identification Information:

Logger ID.........: sdisk
Product Identifier: SCSI Disk
Product Qualifier.: SEAGATEST173404LWV
SCSI Target ID....: 0x00
SCSI LUN..........: 0x00

I/O Log Event Data:

Driver Status Code..................: 0x0000000B
Length of Logged Hardware Status....: 22 bytes.
Offset to Logged Manager Information: 24 bytes.
Length of Logged Manager Information: 30 bytes.

Hardware Status:

Raw H/W Status:
0x0000: 00 00 00 02 70 00 06 00 00 00 00 0A 00 00 00 00
0x0010: 29 01 01 00 00 00

SCSI Status...: CHECK CONDITION (0x02)
Indicates that a contingent allegiance condition has occurred. Any
error, exception, or abnormal condition that causes sense data to be
set will produce the CHECK CONDITION status.

SCSI Sense Data:

Undecoded Sense Data:
0x0000: 70 00 06 00 00 00 00 0A 00 00 00 00 29 01 01 00
0x0010: 00 00

SCSI Sense Data Fields:Bit Fields:
Filemark : 0
End-of-Medium : 0
Incorrect Length Indicator : 0
Sense Key : 0x06
Information Field Valid : FALSE
Information Field : 0x00000000
Additional Sense Length : 10
Command Specific : 0x00000000
Additional Sense Code : 0x29
Additional Sense Qualifier : 0x01
Field Replaceable Unit : 0x01
Sense Key Specific Data Valid : TRUE
Sense Key Specific Data : 0x00 0x00 0x00

Sense Key 0x06, UNIT ATTENTION, indicates that the target has been
reset by a BUS DEVICE RESET message, a hard reset condition, or by a
power-on reset. If not a reset, then one of the following may have
occurred.
1. A removable medium may have been changed.
2. The mode parameters in effect for this initiator have been
changed by another initiator.
3. The version or level of microcode has been changed.
4. Tagged commands queued for this initiator were cleared by
another initiator.
5. INQUIRY dat 7. A change in the condition of a synchronized spindle.
8. Any other event that requires the attention of the initiator.

SCSI Command Data Block: (not present in log record)

Manager-Specific Data Fields:
Request ID.............: 0x00001069
Data Residue...........: 0x00000000
CDB status.............: 0x3F788337
Sense Status...........: 0x00000000
Bus ID.................: 0x3F
Target ID..............: 0x78
LUN ID.................: 0x83
Sense Data Length......: 0x37
Q Tag..................: 0x2F
Retry Count............: 29556
a has been changed.
6. The mode parameters in effect for this initiator have been
restored from non-volatile memory.

Error Code : 0x70
Segment Number : 0x00

Re: Problem when adding a new drive

Michael Steele_2 — Mon, 29 Sep 2003 15:11:36 GMT

I'm sorry, the question issss.....

Re: Problem when adding a new drive

James Colby — Mon, 29 Sep 2003 15:14:15 GMT

Sorry for not being clear. I was wondering if this error could be the reason why I can't use my newly installed disk drive. And if so if anybody had any suggestions/recommendations on how to resolve the problem.

Re: Problem when adding a new drive

Sundar_7 — Mon, 29 Sep 2003 15:20:06 GMT

What is the ioscan status for the drive ?

May be execute a mediainit on the drive and try pvcreate again.

Re: Problem when adding a new drive

TC ITEMS Unix Admin — Mon, 29 Sep 2003 15:22:46 GMT

By the way:
1. Is the drive hotswappable? ie did you reboot the server after replacing the drive?
2. What does ioscan -fnC disk show as the status of the drive?

Re: Problem when adding a new drive

James Colby — Mon, 29 Sep 2003 15:22:58 GMT

This is the output from ioscan.

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 5 0/0/1/0.0.0 sdisk CLAIMED DEVICE SEAGATE ST173404LWV
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0

Re: Problem when adding a new drive

Michael Steele_2 — Mon, 29 Sep 2003 15:25:15 GMT

Your device is obviously not installed or Dead On Arrival. DOA. Use '...ioscan -fnkC disk..." and check for "CLAIMED" states. If you see a "NO_HW" state then the a HW problem exists.

First rule of being an HP-UX S.A., its a HW problem if its "NO_HW" in '...ioscan...".

Also, these messages are generated from EMS. Logs for EMS reside in /etc/resmon/log. Use '...ls -lrt...' to see what logs are being written to last.

Also, the solution listed from:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100091

...mentions to ignore all cases but the following:

"...Alternatively, the installed version of the device driver does not match that of the installed version of HP-UX. Install the correct version of the driver..."

With this in mind, please attach the above listed 'ioscan' so the drivers can be check, as well as the disk part number. Each disk links to a particular driver and you may need to load this driver via a patch. This process requires a new kernel and reboot.

Re: Problem when adding a new drive

Michael Steele_2 — Mon, 29 Sep 2003 15:30:30 GMT

OK, ioscan looks ok.

So it can also be an disk controller or SCSI cable. Provide a full 'ioscan' now and grep for 'NO_HW'.

ioscan -fnk | grep "NO_HW"

Also check syslog.log,

grep -i vmunix /var/adm/syslog/syslog.log

Also check dmesg:

dmesg

Also check logtool and PLEASE ATTACH THE REPORT:

STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > VIEW > RAW SUMMARY

Re: Problem when adding a new drive

James Colby — Mon, 29 Sep 2003 15:33:04 GMT

Here is the ouput of the ioscan:

# ioscan -fnkC disk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 5 0/0/1/0.0.0 sdisk CLAIMED DEVICE SEAGATE ST173404LWV
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 0 0/0/1/1.0.0 sdisk CLAIMED DEVICE SEAGATE ST39103LC
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
disk 1 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ST39103LC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 2 0/0/2/0.0.0 sdisk CLAIMED DEVICE SEAGATE ST39103LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 3 0/0/2/0.2.0 sdisk CLAIMED DEVICE IBM DMVS09D
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 4 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 304
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0

Re: Problem when adding a new drive

James Colby — Tue, 30 Sep 2003 08:06:50 GMT

My ioscan -fnk | grep "NO_HW" does show anything

Here is the output from stm:

-- Logtool Utility: View Raw Summary --

Summary of: /var/stm/logs/os/log45.raw.cur

Date/time of first entry: Fri Sep 26 12:45:30 2003

Date/time of last entry: Mon Sep 29 16:39:33 2003

Number of LPMC entries: 0
Number of System Overtemp entries: 0
Number of LVM entries: 0
Number of Logger Event entries: 0

Number of I/O Error entries: 568

Device paths for which entries exist:

(24) 0/0/1/0.0.0
(18) 0/7/0/0
(18) 0/4/0/0
(508) 0/0/2/0.2.0

Products for which entries exist:

(24) SCSI Disk
(36) Fibre Channel Interface
(508)

Product Qualifiers for which entries exist:

(24) SEAGATEST173404LWV
(36) HP5158A_Tachyon_TL
(508)

Logger Events for which entries exist:

(36) td
(532) sdisk

Re: Problem when adding a new drive

Michael Steele_2 — Tue, 30 Sep 2003 08:27:12 GMT

Excellent! Let's concentrate on these entries. From your ioscan 0/0/2/0.2.0 cross references to for this is your culprit:

disk 3 0/0/2/0.2.0 sdisk CLAIMED DEVICE IBM DMVS09D
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0

Start a HW call and refer to the information listed below for (508) errors in three days is way, way too much. Also try :

dd if=/dev/dsk/c2t2d0 of=/dev/null count=1000000
*******************************************
*
*******************************************

Date/time of first entry: Fri Sep 26 12:45:30 2003
Date/time of last entry: Mon Sep 29 16:39:33 2003

Number of I/O Error entries: 568

(508) 0/0/2/0.2.0

(532) sdisk

Re: Problem when adding a new drive

TC ITEMS Unix Admin — Tue, 30 Sep 2003 09:01:54 GMT

Could you take a step back? Did you hotswap the disk or did you actually power down the server, plug the disk in and power it up again? Which version of HPUX are you running?

Re: Problem when adding a new drive

James Colby — Tue, 30 Sep 2003 09:04:19 GMT

I powered down the server swapped out the failed drive and powered the machine back up. I am using HP-UX 11.0

Thanks everyone for your help!