Thank you to all of you who responded. What the problem appears to have
ended up being was a misconfiguration of some striped volumes.
We have eight disks that are each broken down into 32 subdisks. With the
256 subdisks we create 32 8-column striped plexes (i.e. a subdisk from each
disk for each plex). Each plex is associated to a volume.
It seems that Volume Manager wants the size of the subdisk to be a multiple
of the width of the stripe (I could NOT find this documented anywhere).
Otherwise, Volume Manager seems to create volumes that overlap each other.
The clue that led us to this conclusion is that the size of the plex (and
volume) is larger than the sum of the size of the eight subdisks.
Is there anyone else out there who has experienced the same problem and can
confirm that this is a requirement by Volume Manager? We have another system
that we configured similary, but hasn't crashed yet. However, I'm guessing
that maybe it's because the part of the disk that's overlapped hasn't been
used yet.
Thanks, Steven.
On Thu, 12 Nov 1998, Steven Sakata wrote:
> Hello there Sun Gurus. I'm having a problem with a system that doesn't bring up
> all the VxVM file systems upon boot up. Attached is the part of the console
> output that I thought was related to the problem. Has anyone seen this before,
> any ideas?
>
> Thanks, in advance, Steven.
>
> ------------------------ console output ---------------------------------
> Rebooting with command: boot
>
> Port#0 received soc-status=14 Boot device: disk File and args:
> Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
> FCode UFS Reader 1.10 96/10/15 00:57:29.
> Loading: /platform/SUNW,Ultra-Enterprise/ufsboot
> Loading: /platform/sun4u/ufsboot
> SunOS Release 5.6 Version Generic_105181-05 [UNIX(R) System V Release 4.0]
> Copyright (c) 1983-1997, Sun Microsystems, Inc.
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 reducing transfer rate
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Parity Error
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 reducing transfer rate
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Parity Error
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 disabled wide SCSI mode
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 reducing transfer rate
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Parity Error
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 disabled wide SCSI mode
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 reducing transfer rate
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Parity Error
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 disabled wide SCSI mode
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 reducing transfer rate
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Parity Error
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 disabled wide SCSI mode
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 reducing transfer rate
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Parity Error
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 disabled wide SCSI mode
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 reducing transfer rate
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Parity Error
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 disabled wide SCSI mode
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 reducing transfer rate
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Parity Error
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 disabled wide SCSI mode
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 reducing transfer rate
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Parity Error
> WARNING: /sbus@3,0/QLGC,isp@0,10000 (isp3):
> Target 0 disabled wide SCSI mode
> WARNING: forceload of drv/pln failed
> WARNING: forceload of drv/soc failed
> VxVM starting in boot mode...
> configuring network interfaces: hme0 tr0.
> ip_rput: DL_ERROR_ACK for 29, errno 1, unix 0
> ip: joining multicasts failed on tr0 - will use link layer
> broadcasts for multicast
> Hostname: bohsun5
> vxvm: NOTE: Setting partition /dev/dsk/c0t0d0s1 as the dump device.
> VxVM starting special volumes ( swapvol var )...
> VxVM general startup...
> vxvm:vxvol: ERROR: Volume ds000fs26 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000fs27 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000fs28 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000fs29 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000fs30 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol00 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol01 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol02 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol03 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol04 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol05 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol06 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol07 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol08 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol09 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol10 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol11 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol12 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol13 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol14 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol15 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol16 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol17 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol18 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol19 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol20 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol21 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol22 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol23 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol24 has no complete, non-volatile ACTIVE plexes
> vxvm:vxvol: ERROR: Volume ds000vol25 has no complete, non-volatile ACTIVE plexes
> The system is coming up. Please wait.
> checking ufs filesystems
> /dev/vx/rdsk/oracledg/ds000fs26: No such device or address
> Can't open /dev/vx/rdsk/oracledg/ds000fs26
> /dev/vx/rdsk/oracledg/ds000fs26: CAN'T CHECK FILE SYSTEM.
> /dev/vx/rdsk/oracledg/ds000fs26: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> /dev/vx/rdsk/oracledg/ds000fs27: No such device or address
> Can't open /dev/vx/rdsk/oracledg/ds000fs27
> /dev/vx/rdsk/oracledg/ds000fs27: CAN'T CHECK FILE SYSTEM.
> /dev/vx/rdsk/oracledg/ds000fs27: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> /dev/vx/rdsk/oracledg/ds000fs28: No such device or address
> Can't open /dev/vx/rdsk/oracledg/ds000fs28
> /dev/vx/rdsk/oracledg/ds000fs28: CAN'T CHECK FILE SYSTEM.
> /dev/vx/rdsk/oracledg/ds000fs28: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> /dev/vx/rdsk/oracledg/ds000fs29: No such device or address
> Can't open /dev/vx/rdsk/oracledg/ds000fs29
> /dev/vx/rdsk/oracledg/ds000fs29: CAN'T CHECK FILE SYSTEM.
> /dev/vx/rdsk/oracledg/ds000fs29: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> /dev/vx/rdsk/oracledg/ds000fs30: No such device or address
> Can't open /dev/vx/rdsk/oracledg/ds000fs30
> /dev/vx/rdsk/oracledg/ds000fs30: CAN'T CHECK FILE SYSTEM.
> /dev/vx/rdsk/oracledg/ds000fs30: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
>
> WARNING - Unable to repair one or more of the following filesystem(s):
> /dev/vx/rdsk/opt /dev/vx/rdsk/rootdg/oraclevol /dev/vx/rdsk/oracledg/ds000fs26 /dev/vx/rdsk/oracledg/ds000fs27 /dev/vx/rdsk/oracledg/ds000fs28 /dev/vx/rdsk/oracledg/ds000fs29 /dev/vx/rdsk/oracledg/ds000fs30
> Run fsck manually (fsck filesystem...).
> Exit the shell when done to continue the boot process.
>
>
> Type Ctrl-d to proceed with normal startup,
> (or give root password for system maintenance):
>
>
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:52 CDT