Sponsored Content
Operating Systems Solaris VxVM/Hba cards/Solaris 10 FS issue Post 302097610 by unclefab on Monday 27th of November 2006 01:01:51 PM
Old 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

Moving HBA cards to different PCI slots

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

Help! Moving HBA cards to different slots

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

How do I know which HBA cards' hardware I have (on Solaris 10) ?

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

How do I know which HBA cards' hardware I have (on Solaris 10) ?

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

Command to get the details and number of HBA cards

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

VxVM on 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

HBA cards on older FreeBSD's

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

Solaris and vxvm ( really old versions)

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

Command for viewing hba cards on rhel7

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

Issue with Fiber Channel cards in 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
vxdiskadd(1M)															     vxdiskadd(1M)

NAME
vxdiskadd - add one or more disks for use with Veritas Volume Manager SYNOPSIS
vxdiskadd disk_address_pattern_list DESCRIPTION
The vxdiskadd utility configures disks for use by Veritas Volume Manager (VxVM). Disks must already have been formatted. vxdiskadd prompts the user for a disk group name and disk name for the disks. If no disk group name specified, the disks will be left as unassigned replacement disks for future use. A new disk group may be created that will become the disks' disk group. If a disk group is specified for the disks, the user is prompted for whether the disks should be designated as spares for the disk group. For new disks, all space on the disk becomes free space in the disk's disk group. vxdiskadd interactively allows initialization to be done for all the disks specified or allows the user to ask to make the decision for each disk individually. One or more disks may be specified with a disk_address_pattern_list. The basic form of a disk address is c#t#d#. Any leading portion of this address may be specified to indicate that all disks that match that leading portion should be used. For example c2t0 may be used to specify all disks on controller 2, target 0. More than one disk address or address pattern may be specified on the command line. In case of enclosure-based names, the disk address will be of the form enclosurename_diskno. The enclosurename indicates that all disks in the specified enclosure are used. For example, emc1_ is used to specify all disks in the enclosure emc1. The word all may be used to specify all disks on the system. Disk address names relate directly to device node names in the /dev/dmp and /dev/rdmp directories. Here are more examples: all: all disks c3 c4t2: all disks on 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 The files /etc/vx/cntrls.exclude, /etc/vx/disks.exclude and /etc/vx/enclr.exclude may be used to exclude controllers or disks from use by vxdiskadd. Each line of cntrls.exclude specifies the address of a controller to exclude, for example, c2. Each line of disks.exclude spec- ifies a disk to exclude, for example, c0t3d0. Each line of enclr.exclude specifies the name of an enclosure to exclude, for example, enc0. All courses of action that do not involve clear failure conditions require prompts from the user, with defaults supplied as appropriate. Help is made available at every prompt. Entering ? in response to a prompt displays a context-sensitive help message. OPERATIONS
Reconnecting a drive that was temporarily inaccessible This situation is detected automatically by noting that the specified drive has a disk ID that matches a disk media record with no currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes referring the disk are restarted. This reattach action is performed by calling the vxrecover utility. Initialization of a disk with reserved regions Initialization of the disk is performed by calling vxdisksetup. Adding a disk to an existing disk group This operation can be performed independently of the initialization of the disk drive. The operation adds the disk to the group so that its storage is added to the free space pool in that disk group. The vxassist utility can subsequently allocate from that free space. Creation of new disk groups in which to import a new disk If disks are added that are required to be put into a disk group that does not exist, the option of creating the disk group is offered. Hardware-Specific Note Some environments provide guidelines to optimize VxVM's interaction with intelligent storage systems. If these guidelines are present, VxVM follows the guidelines when adding disks to disk groups. If the operation fails due to these guideline(s), you are prompted to use the force option. The force option ignores any such storage-specific guidelines. FILES
/etc/vx/cntrls.exclude Specifies the address of controllers to exclude from vxdiskadd operations. /etc/vx/disks.exclude Specifies the address of disks to exclude from vxdiskadd operations. /etc/vx/enclr.exclude Specifies the address of enclosures to exclude from vxdiskadd operations. NOTES
EFI disks cannot be added to a disk group that is compatible with the Cross-platform Data Sharing (CDS) feature, nor can they be formatted as CDS disks. SEE ALSO
vxassist(1M), vxdisk(1M), vxdiskadm(1M), vxdisksetup(1M), vxintro(1M), vxrecover(1M) VxVM 5.0.31.1 24 Mar 2008 vxdiskadd(1M)
All times are GMT -4. The time now is 02:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy