receiving excessive errors from the I/O subsystem

[Seidel_1]

Hi,

I wanted to restore an IGNITE tape to one of our rp-server but it is not working due to the following error:

======= 01/16/06 11:12:08 EST HP-UX Installation Initialization. (Mon Jan 16
11:12:08 EST 2006)
@(#) Ignite-UX Revision C.6.0.109
@(#) install/init (opt) $Revision: 10.303 $
* Scanning system for IO devices...
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.
* Querying disk device: 0/1/1/0.0.0 ...
* Querying disk device: 0/1/1/0.1.0 ...
* Querying disk device: 0/4/1/0.50.0.0.0.0.0 ...
* Querying disk device: 0/4/1/0.50.0.0.0.0.1 ...
* Querying disk device: 0/4/1/0.50.0.0.0.0.2 ...
* Querying disk device: 0/4/1/0.50.0.0.0.0.3 ...
* Querying disk device: 0/4/1/0.50.0.0.0.0.4 ...
* Querying disk device: 0/4/1/0.50.0.0.0.0.5 ...
* Querying disk device: 0/4/1/0.50.0.0.0.0.6 ...
* Querying disk device: 0/4/1/0.50.0.0.0.0.7 ...
* Querying disk device: 0/4/1/0.50.0.0.0.1.0 ...
* Querying disk device: 0/4/1/0.51.1.0.0.0.0 ...
* Querying disk device: 0/4/1/0.51.1.0.0.0.1 ...
* Querying disk device: 0/4/1/0.51.1.0.0.0.2 ...
* Querying disk device: 0/4/1/0.51.1.0.0.0.3 ...
* Querying disk device: 0/4/1/0.51.1.0.0.0.4 ...
* Querying disk device: 0/4/1/0.51.1.0.0.0.5 ...
* Querying disk device: 0/4/1/0.51.1.0.0.0.6 ...
* Querying disk device: 0/4/1/0.51.1.0.0.0.7 ...
* Querying disk device: 0/4/1/0.51.1.0.0.1.0 ...
Recovery tape created from system: nurara on Fri Oct 21 18:33:14 2005


WARNING: The configuration information calls for a non-interactive
installation.

Press within 10 seconds to cancel batch-mode installation:
* Using client directory: /var/opt/ignite/clients/0x00306E4B0A97
* Checking configuration for consistency...

WARNING: The disk at: 0/1/1/0.0.0 (COMPAQ_BF0368A4CA) appears to contain a file
system. Continuing the installation will destroy any existing data on
this disk.
WARNING: The disk at: 0/4/1/0.50.0.0.0.0.1 (HITACHI_DF600F) appears to contain
a file system. Continuing the installation will destroy any existing
data on this disk.
WARNING: The disk at: 0/4/1/0.51.1.0.0.0.1 (HITACHI_DF600F) appears to contain
a file system. Continuing the installation will destroy any existing
data on this disk.

Press within 10 seconds to cancel batch-mode installation:
* Continuing despite above warnings.
* Attempting a non-interactive installation.
* Loading configuration utility...
* Beginning installation from source: /dev/rmt/0m
======= 01/16/06 11:13:27 EST Starting system configuration...
* Configure_Disks: Begin
* Will install B.11.11 onto this system.
* Creating LVM physical volume "/dev/rdsk/c4t0d1"
(0/4/1/0.50.0.0.0.0.1).
* Creating LVM physical volume "/dev/rdsk/c6t0d1"
(0/4/1/0.51.1.0.0.0.1).
* Creating LVM physical volume "/dev/rdsk/c2t0d0" (0/1/1/0.0.0).
* Creating volume group "vg00".
* Creating volume group "vgdb".
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 2.
LVM: Restored PV 0 to VG 2.
LVM: Lost quorum in vg[2], too many PVs missing!
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 2.
* Creating logical volume "vg00/lvol1" (/stand).
* Creating logical volume "vg00/lvol2" (swap_dump).
* Creating logical volume "vg00/lvol3" (/).
* Creating logical volume "vg00/lvol4" (/opt).
* Creating logical volume "vg00/lvol5" (/tmp).
* Creating logical volume "vg00/lvol6" (/var).
* Creating logical volume "vg00/lvol7" (/usr).
* Creating logical volume "vg00/lvldap" (/var/opt/netscape).
* Creating logical volume "vg00/lvnmsopt" (/d/nmsopt).
* Creating logical volume "vgdb/lvol1" (/d/db).
lvcreate: The logical volume "/dev/vgdb/lvol1" could not be created:
No such device or address
ERROR: Command "/sbin/lvcreate -A n -n lvol1 -C n vgdb" failed.

The configuration process has incurred an error, would you like
to push a shell for debugging purposes? (y/[n]): LVM: Restored PV 0 to VG 2.
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 2.
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 2.


What could that mean, could it be that the fibre channel cable to the SAN is broken or the whole I/O ?

Thanks

Andree

P.S. This thread has been moevd from Disk to HP-UX > ignite. - Hp forum moderator

[Alzhy]

It simply means the component disks needed to create volume Group /dev/vgdb is lacking. Do you include non-OS stuff in your Ignite backup?

[Seidel2]

Hi,

yes, we always include non-OS stuff in our Ignite backup.

But the question was more related to this part:
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.

Does that mean I have a problem with the whole I/O system/card/whatsoever ?

Or could it be just one fibre channel cable to the SAN solution, even the internal disks are also mentioned ?


Thanks

Andree

[Alzhy]

Yes it is SAN related. We do get the same exact messages once in a while.