URGENT : patch install errors

[Edgar_8]

Hi,

We are in the process of applying a patch bundle supplied by HP, but it seems like the install has
hung, and dmesg is having the following output "Magic number wrong (namelist mismatch?)" & syslog is
writing the following errors "vmunix: SCSI: Request Timeout; Abort -- lbolt: 278771339, dev: 1f001000, io_id: 8c633".
Do we have a faulty disk or is because a new kernel is being rebuilt? How can we resolve this issue
ASAP as this is a PRODUCTION box affecting users.

Thanks in advance!

[Steven E. Protter]

You have a bad disk.

Quick:

do a make_tape_recovery of vg00, especially if you are not mirrored.

Schedule a boot, because a power fail or unlug on a hotswap disk will trigger lbolts, but not with this message.

Identify the disk with the script I'm attaching or with mstm excercize function. The bad disk will fail.

Schedule and implement a replacement of the disk.

If you have mirror/ux mirror all the logical volumes on that disk, in case it goes.

SEP

[Mark Grant]

Have a look at this thread,

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=372506

[Naveej.K.A]

Yes...

It looks like your hard disk has gone bad...

Regards
Naveej

[Edgar_8]

Hi,

Thanks for the help guys, most appreciated. How do I identify which is the faulty disk? The script does
not indicate which disk id fauly (internal disks or disk arrays?).Can someone assist with making sense
of errors.

Thanks again!

[Steven E. Protter]

Actutally the lbolt message identifies the disk. After it fails my script will give you the regular device name.

use mstm or xstm(x)

excercize all the disks until one fails.

Thats the bad one.

ioscan

My script will only identify after it fails.
1f001000 translates from hex to a device name you may be more familiar with.

SEP

[Naveej.K.A]

Your defective hard disk is c0t1d0

This is obtained from the dev: 1f001000 in your error at syslog.

1f refers to the driver which it is talking to

the next two (00) => controller number
if its 03 means it would be c3

next two => (10) with target id one and lun number 0

i.e c0t1d0

with best wishes
naveej

[Edgar_8]

Hi,

Guys, thanks for all the help, most appreciated!! With the device being identified as the CDROM drive,it
seems that for no apparent reason it just hung during the patch install?? We decided to power off/on and
this resolved the errors and the install continued! Thanks for the help, I will definitely add the advice
to my troubleshooting doc.