topic Re: read of super-block on /dev/vg00/* failed in Operating System - HP-UX

read of super-block on /dev/vg00/* failed

Seidel_1 — Thu, 12 Jan 2006 12:40:31 GMT

Hi,
after failure of root disk(vg00) which was mirrored and replacement of the faulty disk,
I get the following during reboot of the server:

Logical volume 64, 0x3 configured as ROOT
LVM : Failure in attaching PV (0/1/1/0.0.0) to the root volume group.
Cross device link. The disk is not a LVM disk.
Logical volume 64, 0x2 configured as SWAP
WARNING: Logical volume for Dump expected but not found.
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; ignored - can't read device
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
Starting the STREAMS daemons-phase 1
Checking root file system.
file system is clean - log replay is not required
Root check done.
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' We
d Nov 8 19:24:56 PST 2000 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 6289408 Kbytes, lockable: 4927208 Kbytes, available: 5665024 Kbytes

/sbin/ioinitrc:
: Cannot read from the device/dev/vg00/lvol1: unrecognized file system
Unable to mount /stand - please check entries in /etc/fstab
Skipping KRS database initialization - /stand can't be mounted

/sbin/bcheckrc:
Checking for LVM volume groups and Activating (if any exist)
vxfs fsck: sanity check: root file system OK (mounted read/write)
Checking hfs file systems
/sbin/fsclean: Could not read superblock of /dev/vg00/lvol1: I/O error
fsclean RETURNED AN ERROR, CONTINUING, BUT CHECK /etc/fstab FILE
Checking vxfs file systems
/dev/vg00/lvldap :
vxfs fsck: read of super-block on /dev/vg00/lvldap failed: I/O error
vxfs fsck: read of super-block on /dev/vg00/lvldap failed: I/O error
file system check failure, aborting ...
/dev/vg00/lvnmsopt :
vxfs fsck: read of super-block on /dev/vg00/lvnmsopt failed: I/O error
vxfs fsck: read of super-block on /dev/vg00/lvnmsopt failed: I/O error
file system check failure, aborting ...

System is not coming up any idea what I could do now, before I start a IGNITE restore ?

Thanks

Andree

Re: read of super-block on /dev/vg00/* failed

Mario_66 — Thu, 12 Jan 2006 13:17:10 GMT

Hi,

you have not mentioned on which system this happened?

What steps did you take during replacement?

Have you tried to boot system from old disk only?

M.

Re: read of super-block on /dev/vg00/* failed

Mario_66 — Thu, 12 Jan 2006 13:46:38 GMT

Hi,

I assumed that you did all necessary steps before. E.g. pvcreate -B, mkboot, lvlnboot, lif ...

Before you start ignite, try to boot in maintanance mode and execute command:

#lvlnboot -R

Maybe it can help.

Regards,
Mario.

Re: read of super-block on /dev/vg00/* failed

Devender Khatana — Fri, 13 Jan 2006 01:58:08 GMT

Hi,

The disk through which the system is trying to boot is either faulty or has got coppution due to failure in other disk. What happens if you boot of the other disk?

HTH,
Devender

Re: read of super-block on /dev/vg00/* failed

Seidel_1 — Fri, 13 Jan 2006 02:02:08 GMT

Hi,

I did the following, just now(hpux -lm):

# lvlnboot -R
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c2t0d0":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c2t1d0":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t0d0":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c6t0d0":
The specified path does not correspond to physical volume attached to
this volume group
.
.
The specified path does not correspond to physical volume attached to
this volume group
vgcfgbackup: Warning: couldn't query physical volume "/dev/dsk/c6t1d0":
The specified path does not correspond to physical volume attached to
this volume group
vgcfgbackup: Warning: couldn't query all of the physical volumes.
vgcfgbackup: Volume group not activated.
# pvcreate -B /dev/rdsk/c2t0d0
pvcreate: The physical volume "/dev/dsk/c2t0d0" is already recorded in the "/etc/lvmtab" file.
# pvcreate -B /dev/rdsk/c2t1d0
Couldn't stat physical volume "/dev/rdsk/c2t1d0":
Physical volume can be created only on whole disk.
# pvcreate -B /dev/rdsk/c2t1d0
pvcreate: The physical volume already belongs to a volume group

I cannot bot from any of the disks, some more ideas ?

Thanka

Andree

Re: read of super-block on /dev/vg00/* failed

Devender Khatana — Fri, 13 Jan 2006 02:04:56 GMT

Hi,

Having boot in LVM maintenancemode can you post

#vgdisplay -v /dev/vg00
&
#lvdisplay -v /dev/vg00/lvol*
&
#mountall
&
#bdf

HTH,
Devender

Re: read of super-block on /dev/vg00/* failed

Seidel_1 — Fri, 13 Jan 2006 02:16:46 GMT

OK, I tried to boot from the disk which was not broken:

ISL> hpux -lm

Boot
: disk(0/1/1/0.1.0.0.0.0.0;0)/stand/vmunix
12406784 + 2093056 + 15248016 start 0x202d68

alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3f900000.
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: nfs3_link(): File system was registered at index 3.
NOTICE: cachefs_link(): File system was registered at index 7.
[Osxinit]: Allocated ots_timeout_lock [4074c380]
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/4/1/0
igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0

System Console is on the Built-In Serial Interface
Logical volume 64, 0x3 configured as ROOT
WARNING: Logical volume for Dump expected but not found.
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - no room
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
Starting the STREAMS daemons-phase 1
Checking root file system.
log replay in progress
replay complete - marking super-block as CLEAN
Root check done.
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUP
I80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 6289408 Kbytes, lockable: 4927268 Kbytes, available: 5665024 Kbytes

/sbin/ioinitrc:
Can't open /dev/vg00/lvol1, errno = 6
/dev/vg00/lvol1: CAN'T CHECK FILE SYSTEM.
/dev/vg00/lvol1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/vg00/lvol1: No such device or address
Unable to mount /stand - please check entries in /etc/fstab
Skipping KRS database initialization - /stand can't be mounted

INIT: Overriding default level with level 's'

INIT: SINGLE USER MODE

INIT: Running /sbin/sh

# vgdisplay -v /dev/vg00
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg00".
# vgdisplay -v /dev/vg00/lvol1
vgdisplay: Volume group "/dev/vg00/lvol1" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "/dev/vg00/lvol1".
# vgdisplay -v /dev/vg00/lvol2
vgdisplay: Volume group "/dev/vg00/lvol2" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "/dev/vg00/lvol2".
# vgdisplay -v /dev/vg00/lvol3
vgdisplay: Volume group "/dev/vg00/lvol3" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "/dev/vg00/lvol3".
# vgdisplay -v /dev/vg00/lvol4
vgdisplay: Volume group "/dev/vg00/lvol4" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "/dev/vg00/lvol4".
# vgdisplay -v /dev/vg00/lvol5
vgdisplay: Volume group "/dev/vg00/lvol5" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "/dev/vg00/lvol5".
# vgdisplay -v /dev/vg00/lvol6
vgdisplay: Volume group "/dev/vg00/lvol6" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "/dev/vg00/lvol6".
# mountall
mountall: /dev/vg00/lvol6 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: Cannot open /dev/vg00/lvol6: No such device or address
mountall: cannot fsck /dev/vg00/lvol6
mountall: diagnostics from fsck
file system check failure, aborting ...
No such device or address
mountall: /dev/vg00/lvol6 failed in fsck
mountall: /dev/vg00/lvol6 cannot be mounted
mountall: cannot mount /dev/vg00/lvldap
mountall: /dev/vg00/lvol7 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: Cannot open /dev/vg00/lvol7: No such device or address
mountall: cannot fsck /dev/vg00/lvol7
mountall: diagnostics from fsck
file system check failure, aborting ...
No such device or address
mountall: /dev/vg00/lvol7 failed in fsck
mountall: /dev/vg00/lvol7 cannot be mounted
mountall: /dev/vg00/lvol5 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: Cannot open /dev/vg00/lvol5: No such device or address
mountall: cannot fsck /dev/vg00/lvol5
mountall: diagnostics from fsck
file system check failure, aborting ...
No such device or address
mountall: /dev/vg00/lvol5 failed in fsck
mountall: /dev/vg00/lvol5 cannot be mounted
mountall: /dev/vg00/lvol1 is seriously damaged
mountall: diagnostics from fsck
Can't open /dev/vg00/lvol1, errno = 6
mountall: cannot mount /dev/vg00/lvol1
mountall: /dev/vg00/lvol4 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: Cannot open /dev/vg00/lvol4: No such device or address
mountall: cannot fsck /dev/vg00/lvol4
mountall: diagnostics from fsck
file system check failure, aborting ...
No such device or address
mountall: /dev/vg00/lvol4 failed in fsck
mountall: /dev/vg00/lvol4 cannot be mounted
mountall: /dev/vg00/lvnmsopt has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: Cannot open /dev/vg00/lvnmsopt: No such device or address
mountall: cannot fsck /dev/vg00/lvnmsopt
mountall: diagnostics from fsck
file system check failure, aborting ...
t: No such device or address
mountall: /dev/vg00/lvnmsopt failed in fsck
mountall: /dev/vg00/lvnmsopt cannot be mounted
mountall: cannot mount 172.25.122.35:/SUTELAB/ups/maint
mountall: diagnostics from mount
crt0: ERROR couldn't open /usr/lib/dld.sl errno:000000002
mountall: cannot mount 172.25.122.35:/SUTELAB/ups/etc
mountall: diagnostics from mount
crt0: ERROR couldn't open /usr/lib/dld.sl errno:000000002
# bfd
sh: bfd^[[3~^[[3~: not found
# bdf
sh: bdf: not found
# /usr/bin/bdf
sh: /usr/bin/bdf: not found

Looks not good correct ?

BR

Andree

Re: read of super-block on /dev/vg00/* failed

Devender Khatana — Fri, 13 Jan 2006 02:20:43 GMT

Hi,

Forget to mention that before all these also use

#vgchange -a y -q n /dev/vg00

And then try these commands. Also try running fsck manually and see what happens.

But get ready to use the recent gnite backup. Try a few things before finally going for it.
How critical is the system/downtime?

HTH,
Devender

Re: read of super-block on /dev/vg00/* failed

Seidel_1 — Fri, 13 Jan 2006 02:26:22 GMT

# vgchange -a y -q n /dev/vg00
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c2t0d0":
Cross-device link
Activated volume group
vgchange: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgchange: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgchange: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgchange: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgchange: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgchange: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgchange: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgchange: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgchange: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
Volume group "/dev/vg00" has been successfully changed.
# vgdisplay -v /dev/vg00
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 2
Act PV 1
Max PE per PV 5000
VGDA 2
PE Size (Mbytes) 8
Total PE 4340
Alloc PE 4314
Free PE 26
Total PVG 1
Total Spare PVs 0
Total Spare PVs in use 0

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/stale
LV Size (Mbytes) 504
Current LE 63
Allocated PE 126
Used PV 1

.
.
.
.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg00/lvol6
LV Status available/stale
LV Size (Mbytes) 10000
Current LE 1250
Allocated PE 2500
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg00/lvol7
LV Status available/stale
LV Size (Mbytes) 2000
Current LE 250
Allocated PE 500
Used PV 1

--- Physical volumes ---
PV Name /dev/dsk/c2t1d0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 4340
Free PE 26
Autoswitch On

--- Physical volume groups ---
PVG Name scsi2_1
PV Name /dev/dsk/c2t1d0
# vgdisplay -v /dev/vg00/lvol1
vgdisplay: Volume group "/dev/vg00/lvol1" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "/dev/vg00/lvol1".
# vgdisplay -v /dev/vg00/lvol2
vgdisplay: Volume group "/dev/vg00/lvol2" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "/dev/vg00/lvol2".
# vgdisplay -v /dev/vg00/lvol3
vgdisplay: Volume group "/dev/vg00/lvol3" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "/dev/vg00/lvol3".
# vgdisplay -v /dev/vg00/lvol4
vgdisplay: Volume group "/dev/vg00/lvol4" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "/dev/vg00/lvol4".

# mountall
mountall: /dev/vg00/lvol6 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: read of super-block on /dev/vg00/lvol6 failed: I/O error
mountall: cannot fsck /dev/vg00/lvol6
mountall: diagnostics from fsck
file system check failure, aborting ...
g00/lvol6 failed: I/O error
mountall: /dev/vg00/lvol6 failed in fsck
mountall: /dev/vg00/lvol6 cannot be mounted
mountall: cannot mount /dev/vg00/lvldap
mountall: /dev/vg00/lvol7 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: read of super-block on /dev/vg00/lvol7 failed: I/O error
mountall: cannot fsck /dev/vg00/lvol7
mountall: diagnostics from fsck
file system check failure, aborting ...
g00/lvol7 failed: I/O error
mountall: /dev/vg00/lvol7 failed in fsck
mountall: /dev/vg00/lvol7 cannot be mounted
mountall: /dev/vg00/lvol5 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: read of super-block on /dev/vg00/lvol5 failed: I/O error
mountall: cannot fsck /dev/vg00/lvol5
mountall: diagnostics from fsck
file system check failure, aborting ...
g00/lvol5 failed: I/O error
mountall: /dev/vg00/lvol5 failed in fsck
mountall: /dev/vg00/lvol5 cannot be mounted
mountall: cannot fsck /dev/vg00/lvol1
mountall: diagnostics from fsck
: Cannot read from the devicemountall: cannot mount /dev/vg00/lvol1
mountall: /dev/vg00/lvol4 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: read of super-block on /dev/vg00/lvol4 failed: I/O error
mountall: cannot fsck /dev/vg00/lvol4
mountall: diagnostics from fsck
file system check failure, aborting ...
g00/lvol4 failed: I/O error
mountall: /dev/vg00/lvol4 failed in fsck
mountall: /dev/vg00/lvol4 cannot be mounted
mountall: /dev/vg00/lvnmsopt has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: read of super-block on /dev/vg00/lvnmsopt failed: I/O error
mountall: cannot fsck /dev/vg00/lvnmsopt
mountall: diagnostics from fsck
file system check failure, aborting ...
g00/lvnmsopt failed: I/O error
mountall: /dev/vg00/lvnmsopt failed in fsck
mountall: /dev/vg00/lvnmsopt cannot be mounted
mountall: cannot mount 172.25.122.35:/SUTELAB/ups/maint
mountall: diagnostics from mount
crt0: ERROR couldn't open /usr/lib/dld.sl errno:000000002
mountall: cannot mount 172.25.122.35:/SUTELAB/ups/etc
mountall: diagnostics from mount
crt0: ERROR couldn't open /usr/lib/dld.sl errno:000000002
#

# fsck
** /dev/vg00/rlvol1: Cannot read from the devicelog replay in progress
replay complete - marking super-block as CLEAN
vxfs fsck: read of super-block on /dev/vg00/lvol4 failed: I/O error
file system check failure, aborting ...
vxfs fsck: read of super-block on /dev/vg00/lvol5 failed: I/O error
file system check failure, aborting ...
vxfs fsck: read of super-block on /dev/vg00/lvol6 failed: I/O error
file system check failure, aborting ...
vxfs fsck: read of super-block on /dev/vg00/lvol7 failed: I/O error
file system check failure, aborting ...
vxfs fsck: read of super-block on /dev/vg00/lvnmsopt failed: I/O error
file system check failure, aborting ...
vxfs fsck: read of super-block on /dev/vg00/lvldap failed: I/O error
file system check failure, aborting ...

Is it time for Ignite ?

Re: read of super-block on /dev/vg00/* failed

Devender Khatana — Fri, 13 Jan 2006 02:46:01 GMT

Hi,

Is it time for ignite?

Yes you can start restoring ignite. But first replace the disk. Also first tell with which disk the system is currently booted? and is other disk removed or still inserted?

If only one disk is currently inserted then try LVM maintenance boot from the other disk and retry these steps.

Has you removed the wrong disk?
Also what is the criticality of the system?

What is the output of

#strings /etc/lvmtab

If vg00 is not listed here then run vgscan to recreate lvmtab.

HTH,
Devender

Re: read of super-block on /dev/vg00/* failed

Seidel_1 — Fri, 13 Jan 2006 03:11:05 GMT

Hi,

I am always booting from the good old disk which was not broken:

Boot
: disk(0/1/1/0.1.0.0.0.0.0;0)/stand/vmunix
12406784 + 2093056 + 15248016 start 0x202d68

I am quite sure that we replaced the right disk as we plugged the disk out when the system was running and this was fine until I started to reboot the wholoe server.

The system is not so critical as it is a cluster system and currently the whole stuff is runing on the second node.

Thanks for your help we will try to restore an Ignite tape(still need to find it somehow exactly that tape disappeared :-()

Thanks again

Andree

Re: read of super-block on /dev/vg00/* failed

Seidel_1 — Fri, 13 Jan 2006 06:01:23 GMT

Hi,

now I tried to restore an IGNITE tape from a different server and get the following:

HARD Booted.

ISL Revision A.00.43 Apr 12, 2000

ISL booting hpux (;0):INSTALL

Boot
: tape(0/1/1/1.5.0.0.0.0.0;0):WINSTALL
10850304 + 1794136 + 2598144 start 0x1ff0e8

Firmware Version 44.24

Duplex Console IO Dependent Code (IODC) revision 1

Stored message buffer up to panic:
PDC_MODEL_CPU_ID returned 0x14

System Panic:

linkstamp: Tue Apr 30 16:59:06 MDT 2002
_release_version: @(#) $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80
_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: set_machine_parameters_64: Unidentified cpu type returned from PDC_MODEL

PC-Offset Stack Trace (read across, top of stack is 1st):
0x00210028 0x002630e8 0x00262f08
0x004ab1ac 0x0020516c 0x001ff6b4
End Of Stack

*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.

ERROR: Your system crashed before I/O and dump configuration was complete.
A crash dump cannot be taken under these circumstances without
special configuration. Contact your HP support representative.

Is my problem eventual no disk problem ?

Thanks

Andree

Re: read of super-block on /dev/vg00/* failed

Devender Khatana — Fri, 13 Jan 2006 06:26:24 GMT

Hi,

The message indicates that probably you are not restoring the backup of this system to it. That is why it is giving unidentified CPU type now.

Have you replaced disk before trying restore?

HTH,
Devender

Re: read of super-block on /dev/vg00/* failed

Seidel_1 — Fri, 13 Jan 2006 06:48:05 GMT

Hi,

yes the root-disk is still replaced and as I couldn't find the Ignite tapes of the faulty system, now I tried to take an IGNITE backup of the other working server(just vg00) and want to restore that one to the faulty system.

Of course I would change the system parameter.

In the past that was possible, shouldn't that work ?

Thanks

Andree

Re: read of super-block on /dev/vg00/* failed

Devender Khatana — Fri, 13 Jan 2006 06:53:33 GMT

Hi,

Perhaps the other system has a different tyoe of hardware or the Ignite on the server is not updated. That is causing this.

Keep the recently removed disk also intact so that if required you can find some files from that.

HTH,
Devender

Re: read of super-block on /dev/vg00/* failed

Dennis Robinson_2 — Wed, 28 Apr 2010 18:37:23 GMT

I recently recovered from a similar error. We had the following:

/sbin/ioinitrc:
Can't open /dev/vg00/lvol1, errno = 6
/dev/vg00/lvol1: CAN'T CHECK FILE SYSTEM.
/dev/vg00/lvol1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/vg00/lvol1: No such device or address
Unable to mount /stand - please check entries in /etc/fstab
Skipping KRS database initialization - /stand can't be mounted

Earlier in the boot the following error was shown:

panic: lv_fixrootlv: Stale extent array overflow
Stack Trace:

The problem was we had upgraded to HP-UX 11.31 from version 11.23.

We resolved the issue by:

1. Split the mirror on vg00
2. Reboot
3. Re-establish the mirror on vg00

We also had some critical volumes which where non-contigous ( lvol1, lvol2 ). We used pvmove to make them completely contigous.

In your case, I would attempt to reduce all the mirrors down to "0" on vg00. Then reboot and re-establish the mirrors.