11-27-2006
VxVM/Hba cards/Solaris 10 FS issue
Hi all,
I have a compatibly issues with a new hardware
My config is the following one :
Solaris 10
V490 Hardware
2 X HBA Qlogic 2310f cards
An HP EVA 5000 for storage ...
Veritas VxVM 4.1 MP1
When I reboot my server, VxVM is trying to mount/use the volume before it's discovered/available with the SAN.
The Temp solution is to mount manually all the volumes with the following command : vxvol -g loc1vg startall & mountall
The other workaround is to reboot my server each time with the command : reboot -- -r
If I reboot my server with Init 6 :
hba1: QLogic Fibre Channel Host Adapter fcode version 2.00.09
hba1: Firmware v3.3.12 (ipx)
QLogic Fibre Channel Driver v4.20 Instance: 2
hba2: QLogic Fibre Channel Host Adapter fcode version 2.00.09
hba2: Firmware v3.3.12 (ipx)
Hostname: svdlux69
NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk
cpqccl288: found array controller device at tgt32, lun0
cpqccl288: Vendor/Product ID = COMPAQ HSV110 (C)COMPAQ
cpqccl291: found array controller device at tgt35, lun0
cpqccl291: Vendor/Product ID = COMPAQ HSV110 (C)COMPAQ
cpqccl33: found array controller device at tgt33, lun0
cpqccl33: Vendor/Product ID = COMPAQ HSV110 (C)COMPAQ
cpqccl34: found array controller device at tgt34, lun0
cpqccl34: Vendor/Product ID = COMPAQ HSV110 (C)COMPAQ
NOTICE: VxVM vxdmp V-5-0-148 enabled path 118/0x30 belonging to the dmpnode 282/0x18
NOTICE: VxVM vxdmp V-5-0-148 enabled path 118/0x38 belonging to the dmpnode 282/0x10
Nov 22 09:28:45 spagent[418]: Starting spagent.
checking ufs filesystems
/dev/vx/rdsk/bootdg/opt: is clean.
checking vxfs filesystems
Running parallel replay fsck ...
/dev/vx/rdsk/loc1vg/loc1lv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/opttivlv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/tivlv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/ccmslv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/bgslv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/toolslv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/ecclv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/crashlv:file system check failure, aborting ...
The following filesystems could not be repaired :
/dev/vx/rdsk/loc1vg/loc1lv
/dev/vx/rdsk/loc1vg/ccmslv
/dev/vx/rdsk/loc1vg/opttivlv
/dev/vx/rdsk/loc1vg/tivlv
/dev/vx/rdsk/loc1vg/toolslv
/dev/vx/rdsk/loc1vg/bgslv
/dev/vx/rdsk/loc1vg/ecclv
/dev/vx/rdsk/loc1vg/crashlv
fsckall failed with exit code 1.
WARNING - Unable to repair one or more filesystems.
Run fsck manually (fsck filesystem...).
I tried to put Sleep commands on all the scripts files (veritas+ Hp) without success ....
Any ideas ??
Thanks,
Fabien
10 More Discussions You Might Find Interesting
1. Solaris
Has anyone ever relocated an HBA card after already having it configured in another PCI slot? I've found that the HBA instance #'s start incrementing past the previous. It results in me having to have my instance numbers in /kernel/drv/qla2300.conf be 4,5,6,7 instead of 0,1,2,3. Cleanup with... (5 Replies)
Discussion started by: kduffin
5 Replies
2. Solaris
Due to speed mismatch, the server kept crashing. Sun suggests that I need to move the two HBA cards from the 66Mhz to the 33Mhz slots. There are tons of disks that are connected to these HBAs and I have Veritas volume manager.
Does anyone have a list of what I need to do prior/after moving to... (3 Replies)
Discussion started by: kiem
3 Replies
3. UNIX for Advanced & Expert Users
Hi,
I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine.
The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards.
Can anyone suggest how to determine my HBA hardware ?
Thanks,
Ron.
... (3 Replies)
Discussion started by: ronbarak
3 Replies
4. Solaris
Hi,
I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine.
The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards.
Can anyone suggest how to determine my HBA hardware ?
Thanks,
Ron.
... (4 Replies)
Discussion started by: ronbarak
4 Replies
5. Solaris
Hiii... Every one....
I want to know the command to get the details and number of HBA cards
attached to a server.
I know that we can use "powermt display", but nither my cards are connected to the storage nor powerpath is active.
I am using SUN server with Solaris -9.
Thanks in... (4 Replies)
Discussion started by: Reboot
4 Replies
6. Solaris
Hi,
Quick question if anyone knows this. Is there a command I can use in Veritas Volume manager on Solaris that will tell me what the name of the SAN I am connected to? We have a number of SANs so I am unsure which one my servers are connected to. Thanks. (13 Replies)
Discussion started by: gwhelan
13 Replies
7. BSD
Hi,
The title is a bit misleading, but it seems I can't re-edit the title after creating the post - apologies.
I have been handed a variety of servers, whereas quite a few of these are older FreeBSD (4.8, thank you legacy). I now have one of these servers which has a HBA card installed, and... (0 Replies)
Discussion started by: brightstorm
0 Replies
8. Solaris
This is going to mean nothing to most....
I'm working on a E4500 server running Solaris 2.5.1 and VXVM 2.5.5 :eek:
I've replaced the rootmirror and would like to monitor progress of the resync
It's only a 2Gb /partition so it shouldn't take too long.
In later versions
vxtask list
... (5 Replies)
Discussion started by: Martincorneuk
5 Replies
9. Red Hat
hi all,
I am trying to view the hba cards on a rhel7 server (storage says they are there, but I am not seeing them.
I tried lspci -nn | grep -i hba
lspci |grep qla
I tried looking in /sys/class/fc_host.. but it is empty.
I am not sure if I am looking in the right spot... (0 Replies)
Discussion started by: gartie
0 Replies
10. Solaris
hi everone
i am experiencing disconnectivity from storage to My database machines. i have doubt on my FC cards in my sparc T4-2 machines. i want to know how should i check from my solaris that whether the cards are ok or not because once the disks get disconnect from SAN so it come back again but... (5 Replies)
Discussion started by: janakors
5 Replies
LEARN ABOUT HPUX
vxinstall
vxinstall(1M) vxinstall(1M)
NAME
vxinstall - menu-driven Veritas Volume Manager initial configuration procedure
SYNOPSIS
vxinstall
DESCRIPTION
The vxinstall utility provides a menu driven interface to configure Veritas Volume Manager (VxVM). If you install the Veritas Volume Man-
ager software package using the operating system's package administration commands, you can run vxinstall to configure VxVM for initial use
on your system.
Note: If you use the Veritas software installation scripts, do not run this utility.
OPERATIONS
Licensing
vxinstall first asks if you want to view the Veritas licenses already installed on the system. Answering "yes" is equivalent to exe-
cuting the vxlicrep command (see vxlicrep(1)).
You are then asked if you want to add licenses for other Veritas products. Answering "yes" is equivalent to running the vxlicinst
command (see vxlicinst(1)). and entering a license key.
Enclosure-Based Naming
You can choose whether you want to use disk access names that are based on the device names assigned by the operating system, or that
are based on names that you assign to enclosures.
System-Wide Default Disk Group
You can enter the name for the default disk group (defaultdg). This is an alias for the disk group name that should be assumed if the
-g option is not specified to a command, or if the VXVM_DEFAULTDG environment variable is undefined. By default, defaultdg is set to
nodg (that is, no disk group).
NOTES
From release 4.0 of VxVM, it is no longer necessary to run vxinstall to configure the rootdg disk group. Disks and disk groups may be
added to VxVM by running commands such as vxdiskadm(1M) or by using the graphical user interface without first running vxinstall. The
operation of VxVM does not require any disk groups to have been configured, and a disk group named rootdg does not need to be present on
the system. Any disk group may be configured as the default disk group that is to be used with VxVM commands. Any disk group named rootdg
has no special significance to VxVM. See the vxdg(1M) manual page for further details.
SEE ALSO
vxdctl(1M), vxdg(1M), vxdiskadm(1M), vxintro(1M), vxlicinst(1), vxlicrep(1)
VxVM 5.0.31.1 24 Mar 2008 vxinstall(1M)