Problem booting: DIAGNOSTIC SYSTEM WARNING

[Rafael Moran_1]

Hello,

When booting a K360 I obtain the following message:

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.

lv_readvgdats: Could not read VGDA 1 header & trailer from disk H/W path 10/0.3.0 (error = 5)

I don't know what it means excesive errors from I/O subsystem if I just rebooted.
About the 10/0.3.0 disk I checked it once inside the system and everything seems ok.

Anyone can help me please ?

Thank you all

[Sachin Soni_1]

Hi rafael,

make me more clear , is it your root disk.?

actually it seems like a disk problem...i guess.

Best of luck.
Sachin

[Sanjay_6]

Hi Rafeal,

Here are a a thread for you to look at.

http://us-support.external.hp.com/cki/bin/doc.pl/sid=3f9fc5a50fe32182cc/screen=ckiDisplayDocument?docId=200000015248061

You may be missing some LVM patch on your system. Download the latest LVM patch for your system and it might solve your problem.

hope this helps.

Thanks

[Christopher McCray_1]

hello,

We had a problem just like this this past weekend. We found it to be a failed hard drive. Hope this helps.

Chris

[Uday_S_Ankolekar]

Hi,

Looks like Disk problem.. Check with glance for any disk bottlenecks.

Good luck

USA..

[Rafael Moran_1]

Hi Sachin,

Actually this internal disk is the mirror of the boot disk

[Rafael Moran_1]

Thank you Sanjay,

The patch was already installed on the system
(PHKL_16751)

I still Have the problem I supose that It is a HW problem. Probably I will replace the disk this WeekEnd, because this is a production system

Thank you also to Christopher and Uday

[Sachin Soni_1]

Hi ,
I think its prob with mirrored disk.
and u need to replac it.

u can try few things:-

u can try to remove mirror from that disk.
and check whether it works.

check disk i/o using sar -d and sar -u
check for i/o waiting.

Regards,
sachin S.

[Sanjay_6]

Hi Rafael,

Here is the list of LVM patches i have on my system. It may be that you are missing some patch on your system.

My system was last patched some three weeks back. You may not need all of them. I have Mirror-UX on the box, so you may not need the one related to that. Have a look.

# LVM B.11.00 LVM
LVM.LVM-ENG-A-MAN B.11.00 LVM-ENG-A-MAN
LVM.LVM-KRN B.11.00 HP-UX Kernel support for the Logical Volume Manager
LVM.LVM-MIRROR-RUN B.11.00 LVM-MIRROR-RUN
LVM.LVM-RUN B.11.00 LVM-RUN
PHCO_18901.LVM-RUN 1.0 LVM.LVM-RUN
# PHCO_19479 1.0 LVM commands cumulative patch
PHCO_19479.LVM-ENG-A-MAN 1.0 LVM.LVM-ENG-A-MAN
PHCO_19479.LVM-MIRROR-RUN 1.0 LVM.LVM-MIRROR-RUN
PHCO_19479.LVM-RUN 1.0 LVM.LVM-RUN
# PHCO_23076 1.0 LVM commands cumulative patch
PHCO_23076.LVM-ENG-A-MAN 1.0 LVM.LVM-ENG-A-MAN
PHCO_23076.LVM-MIRROR-RUN 1.0 LVM.LVM-MIRROR-RUN
PHCO_23076.LVM-RUN 1.0 LVM.LVM-RUN
# PHCO_24437 1.0 LVM commands cumulative patch
PHCO_24437.LVM-ENG-A-MAN 1.0 LVM.LVM-ENG-A-MAN
PHCO_24437.LVM-MIRROR-RUN 1.0 LVM.LVM-MIRROR-RUN
PHCO_24437.LVM-RUN 1.0 LVM.LVM-RUN
# PHKL_20333 1.0 LVM Cumulative patch
PHKL_20333.LVM-KRN 1.0 LVM.LVM-KRN
# PHKL_23127 1.0 LVM Cumulative Patch
PHKL_23127.LVM-KRN 1.0 LVM.LVM-KRN
PHKL_24268.LVM-KRN 1.0 LVM.LVM-KRN
# PHKL_24646 1.0 LVM cumulative patch, performance upgrades
PHKL_24646.LVM-KRN 1.0 LVM.LVM-KRN

Hope this helps.

Thanks

[Deshpande Prashant]

HI
Check if the disk is still accessable using ioscan. If this is mirror disk check for lv status (current/stale) in vg00.
#lvdisplay -v /dev/vg00/lvol* |pg

Thanks.
Prashant.

[Rafael Moran_1]

Thank you Prashant,

I have checked it but all the lvols are ok, they show current status

[Deshpande Prashant]

HI
Any errors noted in dmesg or syslog?

Check info in cstm for the disk if possible.


Thanks.
Prashant.

[Rafael Moran_1]

Hi Prashant,

The message I wrote on the first message is the one it appears when booting and it is registered on dmesg and syslog.
I also checked with cstm but nothing strange

Thank you

[Sanjay_6]

Hi Rafael,

Try to increase the timeout for the disk/pv that is giving you this problem. The default timeout is 30seconds. Increase it to 3 minutes and see if it helps.

pvchange -t 180 pv_path

The maximum timeout can be 5 minutes (300 seconds). Also check and see if any conenction is loose or the termination is missing.

Hope this helps.

thanks

[linuxfan]

Hi Raphael,

Did you try increasing the timeout and did it seem to fix the problem?

Here is another thread which looks very similar(error numbers are different though)
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xbb86663ce855d511abcd0090277a778c,00.html

It would be interesting if Mark could tell us if it indeed was a bad disk and replacing that fixed the problem.

-Regards
Ramesh

[Rafael Moran_1]

Finally I changed the disk and now everyting is fixed and ok.
Thank you all for your answers.