Type
to see what disks are in vg00
then again
And look at the last stanza : You should see something like:
Hoping it will tell you what disk is failing... or already dead e.g:
Also, look what you have in your /var/adm/syslog/syslog.log ! You may fins EM- critical messages...
I dont even know what raid level this is, but its raid 5 mirrored from the looks of it.
I have a failed disk (t12) within this mirror. What is the best way to replace this disk? 2 things concern me, isn't there a command to prepare the disk for a hot swap? and what should i do with the... (3 Replies)
Hi Experts,
I have configured A D40 Array. There is an faulty disk which is not part of an raid volume but shows fault in the diagnostics.
pdisk15 U0.1-P1-I1/Q1-W40AA83CC2400D
SSA160 Physical Disk Drive ( MB)
Is there a way to stop this... (2 Replies)
Hi,
Recently i came across a disk that seems to be faulty and need help. I have gathered some information by running below commands and any help on how to solve this will be great.
# uname –a
SunOS XYZ 5.7 Generic_106541-16 sun4u sparc SUNW,Ultra-4
#df -k
Filesystem kbytes used... (3 Replies)
Requirement to remove a faulty mirrored disk from hp-ux LVM
<root@pdwp1s>/etc # 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... (9 Replies)
Hi,
Have mirrored the primary disk to 3 .
Server and OS:
# uname -a
HP-UX pdwp1s B.11.11 U 9000/800 118434630 unlimited-user license
# model
9000/800/L3000-7x
# strings /etc/lvmtab
/dev/vg00
+F@<
/dev/dsk/c1t2d0
/dev/dsk/c2t2d0
/dev/dsk/c2t0d0
But now I have only 1 disk... (5 Replies)
Hi Guys,
One of two disks in my solaris machine has failed, the name is disk0, this is SUN physical sparc machine
But I work remotely, so people working near that physical server are not that technical, so from OS command prompt can run some command to bink faulty disk at front panel of Server.... (9 Replies)
Hi,
One of my disk is in 'disk missing state'. It is a sharedVG and cluster nodes.
The errpt keeps reporting stale partition error.
lvs are in open/stale state.
In this sceanario is replacing the disk the best practice?
When i do a lsdev the disk is labelled as below.
hdisk3 Available ... (2 Replies)
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (1 Reply)
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (3 Replies)
I plugged both power cables in both power supply. When I unplugged each power cable one by one, the SPARC T4-1 machine keep running. However, show faulty command shows below message. (I have also attached the picture of both power supply)
-> show faulty
Target ... (1 Reply)
Discussion started by: z_haseeb
1 Replies
LEARN ABOUT HPUX
cmdisklock
cmdisklock(1m)cmdisklock(1m)NAME
cmdisklock - manage Serviceguard cluster lock devices.
SYNOPSIS
cmdisklock check path
cmdisklock [-f] reset path
DESCRIPTION
cmdisklock is a tool to check the current state of a Serviceguard cluster lock device. It can also be used to reset the state of the clus-
ter lock device. The need to reset the cluster lock device state could arise if the cluster lock device is replaced or becomes corrupt.
A cluster lock device can be either an HP-UX LVM cluster lock or a cluster lock LUN device. HP-UX LVM cluster locks exist only on a disk
in an LVM volume group. Cluster lock LUNs exist only on disks dedicated to cluster lock. cmdisklock is useful for checking either type of
cluster lock and for re-initializing cluster lock LUN devices after a failure or corruption.
NOTE
To restore an HP-UX LVM cluster lock, use vgcfgrestore. cmdisklock will fail until vgcfgrestore is run, and cmdisklock is unnecessary as
long as vgcfgbackup was done after the cluster lock was initialized. See the Managing Serviceguard manual for details.
The syntax of the path option depends on the type of lock. For HP-UX LVM cluster lock disks, the syntax is VG:PV (for example:
/dev/vglock:/dev/dsk/c0t0d2). For cluster lock LUN disks, the path is the disk device path. For example, /dev/sdd1 (on Linux) or
/dev/dsk/c0t1d2 (on HP-UX).
Options
cmdisklock supports the following options:
check Check the current state of the cluster lock device and report the results.
reset Reset (initialize) the state of the cluster lock device. This operation should only be performed on a cluster lock
LUN device. For HP-UX LVM cluster lock, use vgcfgrestore as documented in the Managing Serviceguard manual. After
performing a reset, a check can be used to verify that the lock is cleared.
EXAMPLES
If the cluster lock LUN device becomes corrupted and the cluster is up, messages like the following will appear in syslog.
Mar 15 12:20:41 usb cmdisklockd[17599]: WARNING: Cluster lock LUN /dev/dsk/c0t1d2 is corrupt: bad label. Until this situation is cor-
rected, a single failure could cause all nodes in the cluster to crash.
Mar 15 12:20:41 usb cmdisklockd[17599]: After ensuring that all active nodes in the cluster have logged this message, run 'cmdisklock reset
/dev/dsk/c0t1d2' to repair
Mar 15 12:20:41 usb cmdisklockd[17599]: Cluster lock disk /dev/dsk/c0t1d2 is inaccessible
Once the above messages appear in syslog on all running nodes, the following command will re-initialize the cluster lock LUN:
ucd:/> cmdisklock reset /dev/dsk/c0t1d2
WARNING: Cluster lock LUN /dev/dsk/c0t1d2 is corrupt: bad label. Until this situation is corrected, a single failure could cause all nodes
in the cluster to crash.
After ensuring that all active nodes in the cluster have logged this message, run 'cmdisklock reset /dev/dsk/c0t1d2' to repair
/dev/dsk/c0t1d2 is inaccessible
Resetting cluster lock device /dev/dsk/c0t1d2
Cluster lock reset completed
/dev/dsk/c0t1d2 is accessible
cleared
After the lock is restored, a message like the following appears in syslog:
Mar 15 12:23:11 usb cmdisklockd[17599]: Cluster lock disk /dev/dsk/c0t1d2 is accessible
WARNINGS
CAUTION
For cluster lock LUN, reset is a potentially destructive operation. While cmdisklock checks for known volume manager and file system use
(overridden by -f), it does not validate that the device to be reset is actually used by any cluster. If -f is used on the wrong device
file, loss of data may result.
CAUTION
Care should be taken when doing a reset when the cluster is active as there is a remote possibility that the cluster will partition right
when this command is run and both nodes could end up thinking they have successfully acquired the lock. To avoid this situation, make sure
cmcld has logged a message in syslog on all running nodes saying the device is inaccessble, before performing a reset. Note that it is
safe to run cmdisklock when the cluster is down.
RETURN VALUE
cmdisklock returns the following values:
0 Successful completion.
1 The disk is inaccessible or is not recognized as a cluster lock.
AUTHOR
cmdisklock was developed by HP.
SEE ALSO cmapplyconf(1m), cmviewcl(1m), vgcfgbackup(1m), vgcfgrestore(1m)
Requires Optional Serviceguard Software cmdisklock(1m)