From: Shiva Nagaraj (snagaraj@datawave.com)
Date: Thu Jun 01 2006 - 19:00:19 EDT
Hello Again,
Thanks for many for suggesting various things in the morning.
But I still have this problem. These are the steps I followed today
1. Install Solaris 8 02/04 with kernel 108528-29 level on a SUN fire
V880 (OBP=4.17.1). Please note that I have also tried installing the
latest 8 Recommended patch cluster (117350-38) & didn't do any good. So,
this time I just left the o/s unpatched.
2. Install all the required Veritas patches 111413-18, 111095(latest),
111412(latest). Did not reboot after these patch install since I had
rebooted the system earlier couple times & system would panic while
booting.
3. Tried installting veritas volume manager v 4.1 & went all the way
thru (steps are pasted below the panic message).
4. Ran installvm -configure command to encapsulate the root disk & that
requires a reboot. And when I rebooted.....there goes again....system
panic.
What I noted is that vxvm while doing a precheck pointed out
that veritas patches 115209 & 115210 as "not installed". And I have no
access to sunsolve account to see what that patch is for, any ideas?
This is killing me, I'm working on this for the last 2 days with no
resolution. Any advice, suggestions are welcome.
Thanks
Shiva
Initializing 8GB of memory at addr a000000000 \
Rebooting with command: boot
Boot device: /pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cfb45d19,0:a
File an
d args:
SunOS Release 5.8 Version Generic_108528-29 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
VxVM sysboot INFO V-5-2-3390 Starting restore daemon...
VxVM sysboot INFO V-5-2-3409 starting in boot mode...
NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk
configuring IPv4 interfaces: ce0.
Hostname: ur
Configuring /dev and /devices
panic[cpu0]/thread=2a100105d20: BAD TRAP: type=31 rp=2a1001053d0
addr=e800000018 mmu_fsr=0
sched: trap type = 0x31
addr=0xe800000018
pid=0, pc=0x783fec88, sp=0x2a100104c71, tstate=0x480001606, context=0x0
g1-g7: 70dae7, 30003a9b520, 0, 0, 0, 0, 2a100105d20
000002a100104fe0 unix:die+a4 (31, 2a1001053d0, e800000018, 0,
2a1001053d0, c4022018)
%l0-3: 0000000000000004 0000000000000192 0000030003aa9d68
000002a100013d20
%l4-7: 0000000000000192 00000300062b2d70 0000000000002000
0000000000000000
000002a1001050c0 unix:trap+8b8 (e800000000, 1, 5, 0, 2a1001053d0, 0)
%l0-3: 0000000000000001 0000030000199dd8 00000000104241a0
0000000000000000
%l4-7: 0000000000000031 0000000000000000 0000000000010000
0000030006216c80
000002a100105200 unix:sfmmu_tsb_miss+66c (10428fa0, 0, 300001aff88, 0,
300001aff88, 19)
%l0-3: 000000e800000000 0000000000000004 0000000000000000
00000310002bf100
%l4-7: 000000e800000000 0000000000000000 0000000000000000
000000e800000003
000002a100105320 unix:prom_rtt+0 (e800000000, cf70dae71044fa40,
ffffffffffffffff, 30000035080, 30006171818, 1)
%l0-3: 0000000000000007 0000000000001400 0000000480001606
000000001001a7d0
%l4-7: 0000000000000000 0000000000000003 0000000000000000
000002a1001053d0
000002a100105470 fcip:fcip_rt_update+170 (783fead4, 3000508e028,
3000508e000, 0, 30000188120, 3000508e000)
%l0-3: 0000000000000005 ffffffffffffffff 0000000000000003
0000030004fa4fd0
%l4-7: 0000000000000000 0000030000188008 0000000000000000
0000030006171818
000002a100105530 fcip:fcip_handle_topology+84 (3000508e000, 23b8,
30000188008, 30004fa4fd0, 30004fa4fd0, 300061b8580)
%l0-3: 000000001043a1f0 0000000000000260 00000300061b8900
0000000000000008
%l4-7: ffffffffffffffff 0000000000000008 0000030004a06aa0
0000000000000001
000002a100105640 fcip:fcip_init_port+194 (78293c00, 30000188060,
30000188008, 1e0, 30004fa4fd0, 0)
%l0-3: 0000000078294000 00000000101157ec 0000000000000000
0000000000000000
%l4-7: 0000000000000000 00000000104241a0 0000030004fcca40
000002a100105650
000002a100105710 fcip:fcip_port_attach_handler+d8 (78293c00, 78294048,
30000188008, 30004fa4fd0, ffffffffffffffff, 1)
%l0-3: 0000000078403df8 ffffffffffffffff 000002a10045e000
000002a10045e000
%l4-7: 0000000000000000 0000030000393f88 0000000000000000
0000031013da5140
000002a1001057c0 fcip:fcip_port_attach+484 (30000188008, 2a100105938,
78294048, 0, 78293dd0, 0)
%l0-3: 0000030000188060 0000000000000002 0000030004fa4fd0
0000030000393f88
%l4-7: 0000000000000005 0000000000000000 000002a10045e000
0000000000000000
000002a100105880 fctl:fctl_attach_ulps+1b4 (300002b4ed8, 300002b4ec8,
300002b4ec8, 3000614f5d8, 30003a91000, 0)
%l0-3: 00000000783fe244 0000000000000001 0000000000008000
000002a100013d20
%l4-7: 0000000000000000 00000000104241a0 0000000000000000
0000000000000000
000002a100105990 fp:fp_ulp_port_attach+14 (300060da238, 1, 20, 1, 0, 0)
%l0-3: 0000030000034900 000003000019c4a8 0000000000000000
000000001000a408
%l4-7: 0000000000000000 0000000000000000 0000000000000000
000002a10003d7d0
000002a100105a40 genunix:taskq_thread+18c (30003ab1a48, 0, 104241a0,
10000, 30003ab1a7a, 30003ab1aa0)
%l0-3: 000000001023c460 0000030003ab1a78 0000030003ab1a70
0000030003ab1a48
%l4-7: 0000030003ab1a68 0000030003aaf048 000000000000001a
0000000000000001
syncing file systems...
panic[cpu0]/thread=2a100105d20: panic sync timeout
dumping to /dev/dsk/c1t0d0s1, offset 3356360704
Type 'go' to resume
{0} ok
# ./installvm
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
Copyright (c) 2005 VERITAS Software Corporation. All rights reserved.
VERITAS, the VERITAS Log o and all other VERITAS product names and
slogans are trademarks or
registered trademarks of VERITAS Software Corporation. VERITAS and the
VERITAS Logo Reg.
U.S. Pat. & Tm. Off. Other product names and/or slogans mentioned herein
may be trademarks
or registered trademarks of their respective companies.
Enter the system names separated by spaces on which to install VxVM: ur
Checking OS version on ur
.................................................. SunOS 5.8
Checking VRTSvxvm package
.............................................. not installed
Initial system check completed successfully.
Press [Return] to continue:
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
VERITAS Infrastructure package installation:
Installing VERITAS Infrastructure packages on ur:
Checking VRTScpi package .................................. version
4.1.0.92 installed
Checking VRTSvlic package ................................ version
3.02.005k installed
VERITAS Infrastructure packages installed successfully.
Press [Return] to continue:
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
installvm can install the following optional VxVM packages:
VRTSobgui VERITAS Enterprise Administrator
VRTSvmman VERITAS Volume Manager Manual Pages
VRTSvmdoc VERITAS Volume Manager Documentation
VRTSvrw VERITAS Volume Replicator Web Console
VRTSvrdoc VERITAS Volume Replicator Documentation
VRTSap VERITAS Action Provider
VRTStep VERITAS Task Provider
1) Install all of the optional packages
2) Install none of the optional packages
3) View package descriptions and select optional packages
Select the optional packages to be installed on all systems? [1-3,q,?]
(1)
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
installvm will install the following VxVM packages:
VRTSperl VERITAS Perl 5.8.0 Redistribution
VRTSob VERITAS Enterprise Administrator Service
VRTSobgui VERITAS Enterprise Administrator
VRTSvxvm VERITAS Volume Manager Binaries
VRTSvmman VERITAS Volume Manager Manual Pages
VRTSvmdoc VERITAS Volume Manager Documentation
VRTSvmpro VERITAS Volume Manager Management Services Provider
VRTSfspro VERITAS File System Management Services Provider
VRTSalloc VERITAS Volume Manager Intelligent Storage Provisioning
VRTSddlpr VERITAS Device Discovery Layer Services Provider
VRTSvrpro VERITAS Volume Replicator Client Extension and Provider for
VERITAS Enterprise Administrator
VRTSvcsvr VERITAS Cluster Server Agents for VVR
VRTSjre VERITAS Java Runtime Environment Redistribution
VRTSweb VERITAS Java Web Server
VRTSvrw VERITAS Volume Replicator Web Console
VRTSvrdoc VERITAS Volume Replicator Documentation
VRTSap VERITAS Action Provider
VRTStep VERITAS Task Provider
Press [Return] to continue:
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
Checking system installation requirements:
Checking VxVM installation requirements on ur:
Checking VRTSperl package
.............................................. not installed
Checking VRTSob package
................................................ not installed
Checking VRTSobgui package
............................................. not installed
Checking VRTSvxvm package
.............................................. not installed
Checking VRTSvmman package
............................................. not installed
Checking VRTSvmdoc package
............................................. not installed
Checking VRTSvmpro package
............................................. not installed
Checking VRTSfspro package
............................................. not installed
Checking VRTSalloc package
............................................. not installed
Checking VRTSddlpr package
............................................. not installed
Checking VRTSvrpro package
............................................. not installed
Checking VRTSvcsvr package
............................................. not installed
Checking VRTSjre package
............................................... not installed
Checking VRTSweb package
............................................... not installed
Checking VRTSvrw package
............................................... not installed
Checking VRTSvrdoc package
............................................. not installed
Checking VRTSap package
................................................ not installed
Checking VRTStep package
............................................... not installed
Checking required SunOS patch 111413-06 ..........................
111413-18 installed
Checking required SunOS patch 108993-18 ..........................
108993-31 installed
Checking required SunOS patch 108528-18 ..........................
108528-29 installed
Checking VERITAS patch 115209
.......................................... not installed
Checking VERITAS patch 115210
.......................................... not installed
Checking for any Solaris patch issues
........................................... None
Checking file system space ............................... required
space is available
Checking for any AP driver issues
............................................... None
Stopping VVR processes on host ur
............................................... Done
Checking vxsvc process
................................................... not running
Checking VRTSweb process
................................................. not running
Installation requirement checks completed successfully.
Press [Return] to continue:
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
Installing Volume Manager 4.1 on ur:
Installing VRTSperl 4.0.12 on ur ..................................
Done 1 of 20 steps
Installing VRTSob 3.2.514.0 on ur .................................
Done 2 of 20 steps
Adding patch 115209-16 on ur ......................................
Done 3 of 20 steps
Installing VRTSobgui 3.2.514.0 on ur ..............................
Done 4 of 20 steps
Adding patch 115210-16 on ur ......................................
Done 5 of 20 steps
Installing VRTSvxvm 4.1 on ur .....................................
Done 6 of 20 steps
Installing VRTSvmman 4.1 on ur ....................................
Done 7 of 20 steps
Installing VRTSvmdoc 4.1 on ur ....................................
Done 8 of 20 steps
Installing VRTSvmpro 4.1 on ur ....................................
Done 9 of 20 steps
Installing VRTSfspro 4.1 on ur ...................................
Done 10 of 20 steps
Installing VRTSalloc 4.1 on ur ...................................
Done 11 of 20 steps
Installing VRTSddlpr 4.1 on ur ...................................
Done 12 of 20 steps
Installing VRTSvrpro 4.1 on ur ...................................
Done 13 of 20 steps
Installing VRTSvcsvr 4.1 on ur ...................................
Done 14 of 20 steps
Installing VRTSjre 1.4 on ur .....................................
Done 15 of 20 steps
Installing VRTSweb 4.2 on ur .....................................
Done 16 of 20 steps
Installing VRTSvrw 4.1 on ur .....................................
Done 17 of 20 steps
Installing VRTSvrdoc 4.1 on ur ...................................
Done 18 of 20 steps
Installing VRTSap 2.00.023 on ur .................................
Done 19 of 20 steps
Installing VRTStep 1.20.028 on ur ................................
Done 20 of 20 steps
Volume Manager installation completed successfully.
Press [Return] to continue:
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
VxVM Licensing Verification:
Checking VxVM license key on ur
......................................... not licensed
Enter a VxVM license key for ur: [?]
8EPU-OPBU-NNBP-8O4O-4UPP-PCPZ-C6PN-P
Registering VERITAS Volume Manager DEMO key on ur
Do you want to enter another license key for ur? [y,n,q,?] (n)
VxVM licensing completed successfully.
Press [Return] to continue:
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
It is optional to configure VxVM now. If you choose to configure VxVM
later, you can either
do so manually or run the installvm -configure command.
Are you ready to configure VxVM? [y,n,q] (y) n
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
Installation of Volume Manager 4.1 has completed successfully.
The installation summary is saved at:
/opt/VRTS/install/logs/installvm601122106.summary
The installvm log is saved at:
/opt/VRTS/install/logs/installvm601122106.log
Volume Manager cannot be started without configuration.
Run installvm -configure when you are ready to configure VxVM.
Veritas Volume manager 4.1 Installation.
# ./installvm -configure
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
Copyright (c) 2005 VERITAS Software Corporation. All rights reserved.
VERITAS, the VERITAS Logo and all other VERITAS product names and
slogans are trademarks or
registered trademarks of VERITAS Software Corporation. VERITAS and the
VERITAS Logo Reg.
U.S. Pat. & Tm. Off. Other product names and/or slogans mentioned herein
may be trademarks
or registered trademarks of their respective companies.
Enter the system names separated by spaces on which to configure VxVM:
ur
Checking OS version on ur
.................................................. SunOS 5.8
Checking VRTSvxvm package ......................................
version 4.1 installed
Initial system check completed successfully.
Press [Return] to continue:
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
VxVM Licensing Verification:
Checking VxVM license key on ur ..................................
Volume Manager Demo
VxVM licensing verified successfully.
Press [Return] to continue:
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
The enclosure-based naming scheme is a feature of Volume Manager. It
allows one to
reference disks using a symbolic name that is more meaningful than the
operating system's
normal device access name. This symbolic name is typically derived from
the array name.
Do you want to set up the enclosure-based naming scheme? [y,n,q,?] (n) n
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
Configuring Volume Manager:
Volume Manager configured successfully.
Press [Return] to continue:
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
Note: The vxconfigd daemon will be started, which can take a while
depending upon the
hardware configuration.
Disabling enclosure-based naming on ur
.......................................... Done
Starting vxconfigd for VxVM on ur
............................................ Started
Volume Manager default disk group configuration:
Many Volume Manager commands affect the contents or configuration of a
disk group. Such
commands require that the user specify a disk group. This is
accomplished by using the -g
option of a command or setting the VXVM_DEFAULTDG environment variable.
An alternative to
these two methods is to configure the default disk group of a system.
Do you want to set up the default disk group for each system? [y,n,q,?]
(y) n
Volume Manager default disk group setup and daemon startup
You declined to set up the default disk group for ur.
Starting vxcached on ur
...................................................... Started
Volume Manager was started successfully.
Press [Return] to continue:
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
Configuration of Volume Manager 4.1 has completed successfully.
The configuration summary is saved at:
/opt/VRTS/install/logs/installvm601151412.summary
The installvm log is saved at:
/opt/VRTS/install/logs/installvm601151412.log
#
#
# vxdiskadm
Volume Manager Support Operations
Menu: VolumeManager/Disk
1 Add or initialize one or more disks
2 Encapsulate one or more disks
3 Remove a disk
4 Remove a disk for replacement
5 Replace a failed or removed disk
6 Mirror volumes on a disk
7 Move volumes from a disk
8 Enable access to (import) a disk group
9 Remove access to (deport) a disk group
10 Enable (online) a disk device
11 Disable (offline) a disk device
12 Mark a disk as a spare for a disk group
13 Turn off the spare flag on a disk
14 Unrelocate subdisks back to a disk
15 Exclude a disk from hot-relocation use
16 Make a disk available for hot-relocation use
17 Prevent multipathing/Suppress devices from VxVM's view
18 Allow multipathing/Unsuppress devices from VxVM's view
19 List currently suppressed/non-multipathed devices
20 Change the disk naming scheme
21 Get the newly connected/zoned disks in VxVM view
22 Change/Display the default disk layouts
23 Mark a disk as allocator-reserved for a disk group
24 Turn off the allocator-reserved flag on a disk
list List disk information
? Display help about menu
?? Display help about the menuing system
q Exit from menus
Select an operation to perform: 1
Add or initialize disks
Menu: VolumeManager/Disk/AddDisks
Use this operation to add one or more disks to a disk group. You can
add the selected disks to an existing disk group or to a new disk
group
that will be created as a part of the operation. The selected disks
may
also be added to a disk group as spares. Or they may be added as
nohotuses to be excluded from hot-relocation use. The selected
disks may also be initialized without adding them to a disk group
leaving the disks available for use as replacement disks.
More than one disk or pattern may be entered at the prompt. Here are
some disk selection examples:
all: all disks
c3 c4t2: all disks on both controller 3 and controller 4, target
2
c3t4d2: a single disk (in the c#t#d# naming scheme)
xyz_0 : a single disk (in the enclosure based naming scheme)
xyz_ : all disks on the enclosure whose name is xyz
Select disk devices to add: [<pattern-list>,all,list,q,?] list
DEVICE DISK GROUP STATUS
c1t0d0 - - online invalid
c1t1d0 - - online invalid
Select disk devices to add: [<pattern-list>,all,list,q,?] c1t0d0
Here is the disk selected. Output format: [Device_Name]
c1t0d0
Continue operation? [y,n,q,?] (default: y)
You can choose to add this disk to an existing disk group, a
new disk group, or leave the disk available for use by future
add or replacement operations. To create a new disk group,
select a disk group name that does not yet exist. To leave
the disk available for future use, specify a disk group name
of "none".
Which disk group [<group>,none,list,q,?] (default: none) rootdg
There is no active disk group named rootdg.
Create a new group named rootdg? [y,n,q,?] (default: y)
Create the disk group as a CDS disk group? [y,n,q,?] (default: y)
Use a default disk name for the disk? [y,n,q,?] (default: y)
Add disk as a spare disk for rootdg? [y,n,q,?] (default: n)
Exclude disk from hot-relocation use? [y,n,q,?] (default: n)
A new disk group will be created named rootdg and the selected disks
will be added to the disk group with default disk names.
c1t0d0
Continue with operation? [y,n,q,?] (default: y)
One or more partitions of the following disk device are in use as
a mounted file system. The disk cannot be initialized, but you can
encapsulate the existing disk partitions as volumes.
Output format: [Device_Name]
c1t0d0
Encapsulate this device? [y,n,q,?] (default: y)
The following disk has been selected for encapsulation.
Output format: [Device_Name]
c1t0d0
Continue with encapsulation? [y,n,q,?] (default: y)
A new disk group rootdg will be created and the disk device c1t0d0
will
be encapsulated and added to the disk group with the disk name
rootdg01.
Enter desired private region length
[<privlen>,q,?] (default: 2048)
VxVM vxencap INFO V-5-2-0 Updating /etc/vfstab ...
The c1t0d0 disk has been configured for encapsulation.
The first stage of encapsulation has completed successfully. You
should now reboot your system at the earliest possible opportunity.
The encapsulation will require two or three reboots which will happen
automatically after the next reboot. To reboot execute the command:
shutdown -g0 -y -i6
This will update the /etc/vfstab file so that volume devices are
used to mount the file systems on this disk device. You will need
to update any other references such as backup scripts, databases,
or manually created swap devices.
Add or initialize other disks? [y,n,q,?] (default: n) n
Volume Manager Support Operations
Menu: VolumeManager/Disk
1 Add or initialize one or more disks
2 Encapsulate one or more disks
3 Remove a disk
4 Remove a disk for replacement
5 Replace a failed or removed disk
6 Mirror volumes on a disk
7 Move volumes from a disk
8 Enable access to (import) a disk group
9 Remove access to (deport) a disk group
10 Enable (online) a disk device
11 Disable (offline) a disk device
12 Mark a disk as a spare for a disk group
13 Turn off the spare flag on a disk
14 Unrelocate subdisks back to a disk
15 Exclude a disk from hot-relocation use
16 Make a disk available for hot-relocation use
17 Prevent multipathing/Suppress devices from VxVM's view
18 Allow multipathing/Unsuppress devices from VxVM's view
19 List currently suppressed/non-multipathed devices
20 Change the disk naming scheme
21 Get the newly connected/zoned disks in VxVM view
22 Change/Display the default disk layouts
23 Mark a disk as allocator-reserved for a disk group
24 Turn off the allocator-reserved flag on a disk
list List disk information
? Display help about menu
?? Display help about the menuing system
q Exit from menus
Select an operation to perform: q
Goodbye.
# Broadcast Message from root (console) on ur Thu Jun 1 15:23:36...
THE SYSTEM ur IS BEING SHUT DOWN NOW ! ! !
Log off now or risk your files being damaged
Shiva Nagaraj
UNIX Consultant
snagaraj@datawave.com
------------------------------------------------------------------------
-----------------
This message (including any attachments) is confidential, may be
privileged and is only intended for the person to whom it is addressed.
If you have received it by mistake please notify the sender by return
e-mail and delete this message from your system.
Any unauthorized use or dissemination of this message in whole or in
part is strictly prohibited. E-mail communications are inherently
vulnerable to interception by unauthorized parties and are susceptible
to change. We will use alternate communication means upon request
------------------------------------------------------------------------
-----------------
This message (including any attachments) is confidential, may be privileged
and is only intended for the person to whom it is addressed. If you have
received it by mistake please notify the sender by return e-mail and delete
this message from your system. Any unauthorized use or dissemination of this
message in whole or in part is strictly prohibited. E-mail communications are
inherently vulnerable to interception by unauthorized parties and are
susceptible to change. We will use alternate communication means upon
request.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:40:00 EDT