Disk Controller error? Hard Disk error?

[GBR]

I'm trying to reinstall an OS and am getting a variety of errors.

1
----

* Making HFS filesystem for "/stand", (/dev/vg00/rlvol1).
LVM: Recovered Path (device 0x1f012000) to PV 0 in VG 0.
LVM: Restored PV 0 to VG 0.

2
---
SCSI: Async write error -- dev: b 31 0x022000, errnLVM: Recovered Path (device 0
x1f022000) to PV 0 in VG 0.
LVM: Restored PV 0 to VG 0.
LVM: vg[0]: pvnum=0 (dev_t=0x1f022000) is POWERFAILED
LVM: Recovered Path (device 0x1f022000) to PV 0 in VG 0.
LVM: Restored PV 0 to VG 0.
x ./usr/lib/nls/msg/C/dcerpc.cat, 13755 bytes, 27 tape blocks
x ./usr/lib/nls/msg/C/cpp.cat, 10542 bytes, 21 tape blocks
x ./usr/lib/libnsl.1, 602112 bytes, 1176 tape blocks
x ./usr/lib/libnsl.sl symbolic link to /usr/lib/libnsl.1
x ./usr/lib/libnss_dns.1, 20480 bytes, 40 tape blocks
x ./usr/lib/libxti.2, 110592 bytes, 216 tape blocks
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.
Async write error -- dev: b 31 0x022000, errno: 126,


LVM: vg[0]: pvnum=0 (dev_t=0x1f022000) is POWERFAILED
lv_readvgdats: Could not read VGDA 1 header & trailer from disk H/W path 0/0/2/0
.2.0 (error = 5)
LVM: Failed to restore PV 0 to VG 0!
LVM: Recovered Path (device 0x1f022000) to PV 0 in VG 0.
LVM: Restored PV 0 to VG 0.

---

I'd like to troubleshoot the issue, but I don't know how to troubleshoot if I can't get the OS loaded.

Is there any troubleshooting I can do through the Guardian Service Processor or through the ISP?

What can I do?

Thanks,
GBR

[DCE]

You are pretty limited in your testing without an OS

A powerfailed message is usually related to a disk failure (at least in my experiences)

Do you have another drive you can install the OS on? (if you are planning to mirror, there should be second drive available.)

Install the OS on the secind drive, and then run the diagnostics on the suspect drive.

[GBR]

DCE,

Thanks for the quick response. I tried using the second disk and received the same types of errors. So I'm inclined to think that this may be related to something else, maybe a disk controller. Any other suggestions?

GBR

[melvyn burnard]

check cables, termination etc. this all points to an isue on the i/o chain

[GBR]

Melvin,

I have checked the cables and termination, but I'm not sure where the problem might be with the I/O chain. Is there a way without getting into the OS to check any I/O chain issues.

This box used to be connected to a JBOD, I disconnected it and terminated the SCSI port and then tried to install a new OS off of a DVD.

Maybe I have done something wrong?

GBR

[DCE]

I agree with Melvin. Check all your cables and verify everything is terminated properly.

Did you make any recent changes to the hardware?

[DCE]

Are all the SCSI ports terminated? There should be port for the channel for the internal drives as well (depending on the server) Even if the port is supposed to self terminating, it would not hurt to add a terminator to it.

[GBR]

DCE,

I'm working with an rp5430. I don't know if you're familiar with that model, but would I ever need to install terminators inside the box??

And my next question is, are there different types of terminators? Could I be using wrong type?

GBR

[DCE]

I do not have a rp5430 to look at, but according to the server configuration guide there is an Ultra 2 SCSI port on the corei/o card - is this terminated?

Also, according to the guide, there are two internal SCSI channels, one per internal disk pair. have you tried swapping the disks to different bays and installing the OS? This should put the disks on the other internal SCSI and help you determine if it is a controller issue

[GBR]

In the end, it was a bad disk.