Is my disk bad?

[GBR]

Hello,

I'm trying to do "Cold Install HP-UX 11i v1" on my rp5430. And I'm seeing the following message at the beginning of the installation.

LVM: Restored PV 0 to VG 0.
LVM: Recovered Path (device 0x1f012000) to PV 0 in VG 0.

Can anyone tell me what this means? I think I may have a bad disk but I'm not sure how to verify this.

Is there any way I can check the disk via the GSP?

You help will be much appreciated. I will assign points.

GBR

[leelangco_1]

you installation can continue or terminate?

[GBR]

Well, I'm not sure exactly because I see the following message over and over again, every few seconds it repeats.

LVM: Restored PV 0 to VG 0.
LVM: Recovered Path (device 0x1f012000) to PV 0 in VG 0.
LVM: Restored PV 0 to VG 0.
LVM: Recovered Path (device 0x1f012000) to PV 0 in VG 0.
LVM: Restored PV 0 to VG 0.
LVM: Recovered Path (device 0x1f012000) to PV 0 in VG 0.

I have to kill the installation.

GBR

[Dino_4]

What is your installation medium?

When exactly is the message shown?

Was the Box or the harddisk in service before?

Do you have any valueable data on any disc in this server?

[Court Campbell]

IF you have the correct scsi card in a windows or linux box, you can pull the drive and hook it up to that box. Then you could use any available tools for those OSes to check if the drive has errors.

[GBR]

Dino,

1. The installation media is by DVD.

2. The message is showing up as the volume groups and logical volumes are being setup by the installer.

3. The OS was running before the installation using this disk and I was not aware of any disk issues.

4. I don't have any valuable data on the disk.

GBR

[Dino_4]

I wonder, why LVM is trying to restore any PVs into VGs?

Do you change anything regarding the disks in this "GUI" during the Installation?

Does it show the right disk on the first "page" where the boot/root disk is choosen?


To be honest, I never had this issue and I can't imagine anything (exept a misconfiguration during installation-dialog or a disk/contoller-failure) can show this error.

[Steven E. Protter]

Shalom GBR,

It could be a very busy disk that is timing out.

It could however be a disk that is getting ready to go.

dmesg
# look for lbolt data.
# If you see an lbolt, you either did a hot swap disk replacement or a disk is gonna go bad.

cstm/mstm or xstm
exercise the disk. Red light on this test is bad results.

If its a system disk do an Ignite make_tape_recovery or make_net_recovery ASAP.

SEP

[GBR]

Steven,

I can't get back into the OS. The installation process mucked that up, so now I'm faced with determining if there is a disk problem.

GBR

[Fabian Briseño]

Hello GBR

Do you have a mirror installation disk of the OS.

If you do you could try to boot from there and the do some checking on the trouble disk.

[GBR]

I tried using the second hard drive in the server to do the cold install and I get this error message:

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.

Not sure where to go from here. Does anyone know what the problem is? Could it be a disk controller?

GBR

[Fabian Briseño]

Hello GBR.

If you have an ignite backup of a similar server (another rp5430), you could try to restore the OS.

if this succeds, you can then do an ignite backup and do a backup of the aplication on your server, and then try to do a cold install.

[Dino_4]

I think it's time to call HP and have the disk or controller replaced.

[GBR]

Yup, it was a disk.