Category: Solaris

VxVM vxplex ERROR V-5-1-10870 fsgen/vxplex: Warning: vxsync exited with exitcode 42

Migrating data to a new storage. Instead of using vxevac we mirrored the volumes

After receiving confirmation that everything is ok, we started removing one side of the mirror.

root@solaris:/ # vxplex -g bkpdg det dat.bkpdg-01
VxVM vxsync INFO V-5-1-4514 VX_FREEZE_ALL ioctl failed
VxVM vxplex ERROR V-5-1-10870 fsgen/vxplex: Warning: vxsync exited with exitcode 42:
Volume data may not be flushed to all plexes

Checking the disk group

root@solaris:/ # vxprint -htg bkpdg
DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME RVG KSTATE STATE NVOLUME
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
SR NAME KSTATE

dg bkpdg default default 3000 1222439090.134.prd007-sbc

dm bkpdgnew01 san_vc0_13 auto 16127 104792064 –
dm bkpdgnew02 san_vc0_28 auto 3839 16766976 –
dm bkpdgnew03 san_vc0_25 auto 16127 1048510464 –
dm bkpdgnew04 san_vc0_27 auto 3839 16766976 –
dm bkpdgnew05 san_vc0_14 auto 16127 104792064 –
dm bkpdgnew06 san_vc0_8 auto 3839 62904320 –
dm bkpdgnew07 san_vc0_21 auto 16127 146735104 –
dm bkpdgnew08 san_vc0_7 auto 16127 104792064 –
dm bkpdgnew09 san_vc0_24 auto 16127 209649664 –
dm bkpdgnew10 san_vc0_4 auto 16127 104792064 –
dm bkpdgnew11 san_vc0_6 auto 16127 104792064 –
dm bkpdg01 ibm_ds8x000_1153 auto 81663 106823680 –
dm bkpdg02 ibm_ds8x000_1167 auto 66943 18800640 –
dm bkpdg03 ibm_ds8x000_1164 auto 81663 1050542080 –
dm bkpdg04 ibm_ds8x000_1166 auto 66943 18800640 –
dm bkpdg05 ibm_ds8x000_1154 auto 81663 106823680 –
dm bkpdg06 ibm_ds8x000_1148 auto 81663 64880640 –
dm bkpdg07 ibm_ds8x000_1160 auto 81663 148766720 –
dm bkpdg08 ibm_ds8x000_1147 auto 81663 106823680 –
dm bkpdg09 ibm_ds8x000_1163 auto 81663 211681280 –
dm bkpdg10 ibm_ds8x000_1144 auto 81663 106823680 –
dm bkpdg11 ibm_ds8x000_1146 auto 81663 106823680 –

v dat.bkpdg – ENABLED ACTIVE 2025293824 SELECT – fsgen
pl dat.bkpdg-01 dat.bkpdg DETACHED STALE 2025293824 CONCAT – RW
sd bkpdgnew01-01 dat.bkpdg-01 bkpdgnew01 0 104792064 0 san_vc0_13 ENA
sd bkpdgnew02-01 dat.bkpdg-01 bkpdgnew02 0 16766976 104792064 san_vc0_28 ENA
sd bkpdgnew03-01 dat.bkpdg-01 bkpdgnew03 0 1048510464 121559040 san_vc0_25 ENA
sd bkpdgnew04-01 dat.bkpdg-01 bkpdgnew04 0 16766976 1170069504 san_vc0_27 ENA
sd bkpdgnew05-01 dat.bkpdg-01 bkpdgnew05 0 104792064 1186836480 san_vc0_14 ENA
sd bkpdgnew06-01 dat.bkpdg-01 bkpdgnew06 0 62904320 1291628544 san_vc0_8 ENA
sd bkpdgnew07-01 dat.bkpdg-01 bkpdgnew07 0 146735104 1354532864 san_vc0_21 ENA
sd bkpdgnew08-01 dat.bkpdg-01 bkpdgnew08 0 104792064 1501267968 san_vc0_7 ENA
sd bkpdgnew09-01 dat.bkpdg-01 bkpdgnew09 0 209649664 1606060032 san_vc0_24 ENA
sd bkpdgnew10-01 dat.bkpdg-01 bkpdgnew10 0 104792064 1815709696 san_vc0_4 ENA
sd bkpdgnew11-01 dat.bkpdg-01 bkpdgnew11 0 104792064 1920501760 san_vc0_6 ENA
pl dat.bkpdg-02 dat.bkpdg ENABLED ACTIVE 2025293824 CONCAT – RW
sd bkpdg10-01 dat.bkpdg-02 bkpdg10 0 106823680 0 ibm_ds8x000_1144 ENA
sd bkpdg11-01 dat.bkpdg-02 bkpdg11 0 106823680 106823680 ibm_ds8x000_1146 ENA
sd bkpdg08-01 dat.bkpdg-02 bkpdg08 0 106823680 213647360 ibm_ds8x000_1147 ENA
sd bkpdg06-01 dat.bkpdg-02 bkpdg06 0 64880640 320471040 ibm_ds8x000_1148 ENA
sd bkpdg01-01 dat.bkpdg-02 bkpdg01 0 106823680 385351680 ibm_ds8x000_1153 ENA
sd bkpdg05-01 dat.bkpdg-02 bkpdg05 0 106823680 492175360 ibm_ds8x000_1154 ENA
sd bkpdg07-01 dat.bkpdg-02 bkpdg07 0 148766720 598999040 ibm_ds8x000_1160 ENA
sd bkpdg09-01 dat.bkpdg-02 bkpdg09 0 211681280 747765760 ibm_ds8x000_1163 ENA
sd bkpdg03-01 dat.bkpdg-02 bkpdg03 0 1050542080 959447040 ibm_ds8x000_1164 ENA
sd bkpdg04-01 dat.bkpdg-02 bkpdg04 0 15304704 2009989120 ibm_ds8x000_1166 ENA

We ignored the message and removed the plex. In the support page for Veritas it asks to stop the volume and after it shows that the volume is clean, you disassociate the plex. Check Veritas support page if you want to follow their instructions

root@solaris:/ # vxplex -g bkpdg -o rm dis dat.bkpdg-01

root@solaris:/ # vxprint -htg bkpdg
DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME RVG KSTATE STATE NVOLUME
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
SR NAME KSTATE

dg bkpdg default default 3000 1222439090.134.prd007-sbc

dm bkpdgnew01 san_vc0_13 auto 16127 104792064 –
dm bkpdgnew02 san_vc0_28 auto 3839 16766976 –
dm bkpdgnew03 san_vc0_25 auto 16127 1048510464 –
dm bkpdgnew04 san_vc0_27 auto 3839 16766976 –
dm bkpdgnew05 san_vc0_14 auto 16127 104792064 –
dm bkpdgnew06 san_vc0_8 auto 3839 62904320 –
dm bkpdgnew07 san_vc0_21 auto 16127 146735104 –
dm bkpdgnew08 san_vc0_7 auto 16127 104792064 –
dm bkpdgnew09 san_vc0_24 auto 16127 209649664 –
dm bkpdgnew10 san_vc0_4 auto 16127 104792064 –
dm bkpdgnew11 san_vc0_6 auto 16127 104792064 –
dm bkpdg01 ibm_ds8x000_1153 auto 81663 106823680 –
dm bkpdg02 ibm_ds8x000_1167 auto 66943 18800640 –
dm bkpdg03 ibm_ds8x000_1164 auto 81663 1050542080 –
dm bkpdg04 ibm_ds8x000_1166 auto 66943 18800640 –
dm bkpdg05 ibm_ds8x000_1154 auto 81663 106823680 –
dm bkpdg06 ibm_ds8x000_1148 auto 81663 64880640 –
dm bkpdg07 ibm_ds8x000_1160 auto 81663 148766720 –
dm bkpdg08 ibm_ds8x000_1147 auto 81663 106823680 –
dm bkpdg09 ibm_ds8x000_1163 auto 81663 211681280 –
dm bkpdg10 ibm_ds8x000_1144 auto 81663 106823680 –
dm bkpdg11 ibm_ds8x000_1146 auto 81663 106823680 –

v dat.bkpdg – ENABLED ACTIVE 2025293824 SELECT – fsgen
pl dat.bkpdg-02 dat.bkpdg ENABLED ACTIVE 2025293824 CONCAT – RW
sd bkpdg10-01 dat.bkpdg-02 bkpdg10 0 106823680 0 ibm_ds8x000_1144 ENA
sd bkpdg11-01 dat.bkpdg-02 bkpdg11 0 106823680 106823680 ibm_ds8x000_1146 ENA
sd bkpdg08-01 dat.bkpdg-02 bkpdg08 0 106823680 213647360 ibm_ds8x000_1147 ENA
sd bkpdg06-01 dat.bkpdg-02 bkpdg06 0 64880640 320471040 ibm_ds8x000_1148 ENA
sd bkpdg01-01 dat.bkpdg-02 bkpdg01 0 106823680 385351680 ibm_ds8x000_1153 ENA
sd bkpdg05-01 dat.bkpdg-02 bkpdg05 0 106823680 492175360 ibm_ds8x000_1154 ENA
sd bkpdg07-01 dat.bkpdg-02 bkpdg07 0 148766720 598999040 ibm_ds8x000_1160 ENA
sd bkpdg09-01 dat.bkpdg-02 bkpdg09 0 211681280 747765760 ibm_ds8x000_1163 ENA
sd bkpdg03-01 dat.bkpdg-02 bkpdg03 0 1050542080 959447040 ibm_ds8x000_1164 ENA
sd bkpdg04-01 dat.bkpdg-02 bkpdg04 0 15304704 2009989120 ibm_ds8x000_1166 ENA

Source: VxVM vxplex ERROR V-5-1-10870 fsgen/vxplex: Warning: vxsync exited with exitcode 42: Volume data may not be flushed to all plexes” appears when attempting to dissociate a plex for a volumed

scstat libsecurity: create of rpc handle to program rgmd_receptionist (100141) failed, will not retry

root@solaris10:/ # scstat -g
libsecurity: create of rpc handle to program rgmd_receptionist (100141) failed, will not retry
scstat: unexpected error.

I’m running a Sun Cluster 3.1 that gave me the error about libsecurity

root@solaris10:/ # pkginfo -l SUNWscnmr
PKGINST: SUNWscnmr
NAME: Sun Cluster name (Root)
CATEGORY: application
ARCH: sparc
VERSION: 3.1.0,REV=2005.07.18.14.37
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: Sun Cluster name (Root)
PSTAMP: 07/18/2005.14:43:46
INSTDATE: Oct 25 2008 20:23
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 3 installed pathnames
2 shared pathnames
2 directories
1 blocks used (approx)

They were complaining that the server was unavailable but I was able to login so I took a look at the runlevel

root@solaris10:/ # who -r
. run-level 3 Oct 6 13:20 3 0 S

Running svcs -xv I saw numerous services that haven’t started yet

root@solaris10:/ # svcs -xv
svc:/milestone/multi-user:default (multi-user milestone)
State: offline since Tue 06 Oct 2015 01:23:54 PM BRT
Reason: Start method is running.
See: http://sun.com/msg/SMF-8000-C4
See: man -M /usr/share/man -s 1M init
See: /var/svc/log/milestone-multi-user:default.log
Impact: 23 dependent services are not running:
svc:/system/webconsole:console
svc:/system/boot-config:default
svc:/application/stosreg:default
svc:/application/sthwreg:default
svc:/application/management/common-agent-container-1:default
svc:/system/cluster/cl-svc-enable:default
svc:/system/cluster/spm:default
svc:/system/cluster/cl-svc-cluster-milestone:default
svc:/system/cluster/scdpm:default
svc:/system/cluster/rpc-pmf:default
svc:/system/cluster/rgm:default
svc:/system/cluster/scsymon-srv:default
svc:/system/cluster/rpc-fed:default
svc:/system/cluster/pnm:default
svc:/system/cluster/cl-event:default
svc:/system/cluster/cl-eventlog:default
svc:/system/cluster/cl-ccra:default
svc:/milestone/multi-user-server:default
svc:/system/basicreg:default
svc:/system/zones:default
svc:/application/graphical-login/cde-login:default
svc:/system/vxvm/vxvm-recover:default
svc:/application/cde-printinfo:default

svc:/application/print/ipp-listener:default (Internet Print Protocol Listening Service)
State: maintenance since Tue 06 Oct 2015 01:22:52 PM BRT
Reason: Start method died on Killed (9).
See: http://sun.com/msg/SMF-8000-KS
See: man -M /usr/share/man -s 4 mod_ipp
See: /var/svc/log/application-print-ipp-listener:default.log
Impact: This service is not running.

Long time passed but didn’t start. Looking at the Fault Management Facility, it was executing a script. Killed the script and the services started being processed

root@solaris10:/ # cat /var/svc/log/milestone-multi-user:default.log
Executing legacy init script “/etc/rc2.d/S74osddownt”.
OSD DownTime is being started.

Solaris 10 – passwd: password is based on a dictionary word.

root@solaris10:/ # passwd emerson
New Password:
passwd: password is based on a dictionary word.

Edit file /etc/default/passwd and comment DICTIONLIST and DICTIONDBDIR

root@solaris10:/ # vi /etc/default/passwd
#DICTIONLIST=/usr/share/lib/dict/words
#DICTIONDBDIR=/var/passwd

Source: On passwords – Part 3: Using a password policy

Solaris 10: emlxs0:WARNING:1540: Firmware update required. (A manual HBA reset or link reset (using luxadm or fcadm) is required

If you are seeing these messages requiring a HBA reset on /var/adm/messages

root@solaris10:/ # tail /var/adm/messages
Sep 3 05:49:32 solaris10 scsi: [ID 243001 kern.info] /pci@0,600000/pci@0/scsi@1 (mpt0):
Sep 3 05:49:32 solaris10 mpt_get_sas_device_page0 config: IOCStatus=0x22 IOCLogInfo=0x30030501
Sep 3 09:24:06 solaris10 emlxs: [ID 349649 kern.info] [ 1.0340]emlxs7:WARNING:1540: Firmware update required. (A manual HBA reset or link reset (using luxadm or fcadm) is required.)
Sep 3 09:24:15 solaris10 emlxs: [ID 349649 kern.info] [ 1.0340]emlxs5:WARNING:1540: Firmware update required. (A manual HBA reset or link reset (using luxadm or fcadm) is required.)
Sep 3 09:24:25 solaris10 emlxs: [ID 349649 kern.info] [ 1.0340]emlxs3:WARNING:1540: Firmware update required. (A manual HBA reset or link reset (using luxadm or fcadm) is required.)
Sep 3 09:24:28 solaris10 emlxs: [ID 349649 kern.info] [ 1.0340]emlxs1:WARNING:1540: Firmware update required. (A manual HBA reset or link reset (using luxadm or fcadm) is required.)
Sep 3 09:24:57 solaris10 emlxs: [ID 349649 kern.info] [ 1.0340]emlxs6:WARNING:1540: Firmware update required. (A manual HBA reset or link reset (using luxadm or fcadm) is required.)
Sep 3 09:24:58 solaris10 emlxs: [ID 349649 kern.info] [ 1.0340]emlxs4:WARNING:1540: Firmware update required. (A manual HBA reset or link reset (using luxadm or fcadm) is required.)
Sep 3 09:24:59 solaris10 emlxs: [ID 349649 kern.info] [ 1.0340]emlxs2:WARNING:1540: Firmware update required. (A manual HBA reset or link reset (using luxadm or fcadm) is required.)
Sep 3 09:25:00 solaris10 emlxs: [ID 349649 kern.info] [ 1.0340]emlxs0:WARNING:1540: Firmware update required. (A manual HBA reset or link reset (using luxadm or fcadm) is required.)

List all the HBA ports

root@solaris10:/ # fcinfo hba-port | grep Device
OS Device Name: /dev/cfg/c11
OS Device Name: /dev/cfg/c12
OS Device Name: /dev/cfg/c9
OS Device Name: /dev/cfg/c10
OS Device Name: /dev/cfg/c4
OS Device Name: /dev/cfg/c5
OS Device Name: /dev/cfg/c2
OS Device Name: /dev/cfg/c3

And then run luxadm -e forcelip on the OS Device Name and wait 60 seconds

root@solaris10:/ # luxadm -e forcelip /dev/cfg/c11; sleep 60
root@solaris10:/ # luxadm -e forcelip /dev/cfg/c12; sleep 60
root@solaris10:/ # luxadm -e forcelip /dev/cfg/c9; sleep 60
root@solaris10:/ # luxadm -e forcelip /dev/cfg/c10; sleep 60
root@solaris10:/ # luxadm -e forcelip /dev/cfg/c4; sleep 60
root@solaris10:/ # luxadm -e forcelip /dev/cfg/c5; sleep 60
root@solaris10:/ # luxadm -e forcelip /dev/cfg/c2; sleep 60
root@solaris10:/ # luxadm -e forcelip /dev/cfg/c3; sleep 60

Sun Fire E25K domain In Recovery status. How to check if it is progressing

You ran showplatform in the system controller and the E25k domain shows the status In Recovery

Domain configurations:
======================
Domain ID Domain Tag Solaris Nodename Domain Status
A – – Powered Off
B – – Powered Off
C – – Powered Off
D – – Powered Off
E domain5 – In Recovery
F – – Powered Off
G – – Powered Off
H – – Powered Off
I – – Powered Off
J – – Powered Off
K – – Powered Off
L – – Powered Off
M – – Powered Off
N – – Powered Off
O – – Powered Off
P – – Powered Off
Q – – Powered Off
R – – Powered Off

To check the progress of why it is taking a long time to boot the domain, check the post process running

roo@systemcontrollern1:~ # ps -ef | grep post
sms-svc 5398 198 0 15:48:02 pts/2 0:00 grep post
sms-dsmd 27458 26817 39 15:34:33 ? 3:14 /opt/SUNWSMS/SMS1.6/bin/hpost -d E -Q

roo@systemcontrollern1:~ # truss -p 27458

HPOM – SOL_mon is warning about a network interface

UXMON: genunix: [ID 408789 kern.warning] WARNING: ce1: fault detected external to device; service degraded

Node : solaris10_node1.setaoffice.com
Node Type : Sun SPARC (HTTPS)
Severity : major
OM Server Time: 2015-06-23 09:22:58
Message : UXMON: genunix: [ID 408789 kern.warning] WARNING: ce1: fault detected external to device;

service degraded
Msg Group : OS
Application : SOL_mon
Object : hardware
Event Type :
not_found

Instance Name :
not_found

Instruction : “The Fault Management agent has identified a HW

or OS related problem with the severity presented by the ticket.
The problem(s) can be viewed and managed with the command – fmdump
To get a better understanding of the problem and on how to resolve it, locate the event that generated
the ticket in the syslog file /var/adm/messages, a URL will be found (http://sun.com/msg/xxx-nnnn-yy),
follow the link using your Oracle portal account for instructions.”

Check /var/adm/messages for mentions about this network interface

root@solaris10_node1:/ # grep ce1 /var/adm/messages
Jun 23 10:20:59 solaris10_node1 genunix: [ID 408789 kern.warning] WARNING: ce1: fault detected external to device; service degraded
Jun 23 10:20:59 solaris10_node1 genunix: [ID 451854 kern.warning] WARNING: ce1: xcvr addr:0x01 – link down

Also check dmesg

root@solaris10_node1:/ # dmesg | grep ce1
Jun 22 14:26:02 solaris10_node1 genunix: [ID 408789 kern.warning] WARNING: ce1: fault detected external to device; service degraded
Jun 22 14:26:02 solaris10_node1 genunix: [ID 451854 kern.warning] WARNING: ce1: xcvr addr:0x01 – link down
Jun 22 14:26:05 solaris10_node1 genunix: [ID 408789 kern.notice] NOTICE: ce1: fault cleared external to device; service available
Jun 22 14:26:05 solaris10_node1 genunix: [ID 451854 kern.notice] NOTICE: ce1: xcvr addr:0x01 – link up 10 Mbps half duplex
Jun 22 14:26:11 solaris10_node1 genunix: [ID 408789 kern.warning] WARNING: ce1: fault detected external to device; service degraded
Jun 22 14:26:11 solaris10_node1 genunix: [ID 451854 kern.warning] WARNING: ce1: xcvr addr:0x01 – link down
Jun 22 14:26:12 solaris10_node1 genunix: [ID 408789 kern.notice] NOTICE: ce1: fault cleared external to device; service available
Jun 22 14:26:12 solaris10_node1 genunix: [ID 451854 kern.notice] NOTICE: ce1: xcvr addr:0x01 – link up 10 Mbps half duplex
Jun 23 10:20:59 solaris10_node1 genunix: [ID 408789 kern.warning] WARNING: ce1: fault detected external to device; service degraded
Jun 23 10:20:59 solaris10_node1 genunix: [ID 451854 kern.warning] WARNING: ce1: xcvr addr:0x01 – link down

If you don’t need monitoring, configure /var/opt/OV/conf/OpC/dmsg_mon.cfg to suppress this alarm.

How to remove files with strange characters

To remove files that contain symbols and unknown characters, list the files with ls -li and take note of the inode number

root@linux:~ # ls -li
total 4420
2495260 -rw——- 1 root root 13810 Jan 28 2011 ????!
2495249 -rw——- 1 root root 13810 Jan 28 2011 ????!

Run the find command and see if it shows the desired file

root@linux:~ # find . -inum 2495260
./????!

And then complete the find command to search, find and remove the file.

root@linux:~ # find . -inum 2495260 -exec rm -i {} \;
rm: remove regular file `./20\36406\b!’? y

Setup a SVM mirror in Solaris 10

In a Solaris server there are two local disks

root@solaris10:~ # echo | format
Searching for disks…done

AVAILABLE DISK SELECTIONS:
0. c0t0d0
/pci@0,600000/pci@0/scsi@1/sd@0,0
1. c0t1d0
/pci@0,600000/pci@0/scsi@1/sd@1,0
Specify disk (enter its number): Specify disk (enter its number):

Specify disk (enter its number): 1

Verify partition table

selecting c0t1d0
[disk formatted]

FORMAT MENU:
disk – select a disk
type – select (define) a disk type
partition – select (define) a partition table
current – describe the current disk
format – format and analyze the disk
repair – repair a defective sector
label – write label to the disk
analyze – surface analysis
defect – defect list management
backup – search for backup labels
verify – read and display labels
save – save new disk/partition definitions
inquiry – show vendor, product and revision
volname – set 8-character volume name
!<cmd> – execute , then return
quit
format> p

Display disk partitions

PARTITION MENU:
0 – change `0′ partition
1 – change `1′ partition
2 – change `2′ partition
3 – change `3′ partition
4 – change `4′ partition
5 – change `5′ partition
6 – change `6′ partition
7 – change `7′ partition
select – select a predefined table
modify – modify a predefined partition table
name – name the current table
print – display the current table
label – write partition map and label to the disk
!<cmd> – execute , then return
quit
partition> p

Partition 0 is /
Partition 1 is swap
Partition 3 is /var
Partition 7 is where metadevice state database

Current partition table (original):
Total disk cylinders available: 14087 + 2 (reserved cylinders)

Part Tag Flag Cylinders Size Blocks
0 root wm 2061 – 4121 20.00GB (2061/0/0) 41945472
1 swap wu 4122 – 10716 64.00GB (6595/0/0) 134221440
2 backup wm 0 – 14086 136.71GB (14087/0/0) 286698624
3 var wm 0 – 2060 20.00GB (2061/0/0) 41945472
4 unassigned wm 10717 – 11026 3.01GB (310/0/0) 6309120
5 unassigned wm 11027 – 11233 2.01GB (207/0/0) 4212864
6 usr wm 11234 – 11749 5.01GB (516/0/0) 10501632
7 unassigned wm 11750 – 11755 59.62MB (6/0/0) 122112

partition>

Checking metadevice state database

root@solaris10:~ # metadb
metadb: solaris10: there are no existing databases

In the example below I’m going to create three copies on partition 7 of disk c0t1d0

root@solaris10:~ # metadb -a -f -c3 /dev/dsk/c0t1d0s7

Checking metadevice state database

root@solaris10:~ # metadb
flags first blk block count
a u 16 8192 /dev/dsk/c0t1d0s7
a u 8208 8192 /dev/dsk/c0t1d0s7
a u 16400 8192 /dev/dsk/c0t1d0s7

Creating the metadevice with disk partitions

root@solaris10:~ # metainit -f d12 1 1 c0t1d0s0
d12: Concat/Stripe is setup
root@solaris10:~ # metainit -f d22 1 1 c0t1d0s1
d22: Concat/Stripe is setup
root@solaris10:~ # metainit -f d32 1 1 c0t1d0s3
d32: Concat/Stripe is setup

Metadevices created

root@solaris10:~ # metastat -p
d32 1 1 c0t1d0s3
d22 1 1 c0t1d0s1
d12 1 1 c0t1d0s0

Setting up Solaris Volume Manager mirror.

root@solaris10:~ # metainit d10 -m d12
d10: Mirror is setup

Setting up to boot with the mirror

root@solaris10:~ # metaroot d10

Setting up the rest of metadevices as mirror as well

root@solaris10:~ # metainit d30 -m d32
d30: Mirror is setup

root@solaris10:~ # metainit d20 -m d22
d20: Mirror is setup

Checking the status

root@solaris10:~ # metastat -p
d20 -m d22 1
d22 1 1 c0t1d0s1
d30 -m d32 1
d32 1 1 c0t1d0s3
d10 -m d12 1
d12 1 1 c0t1d0s0

root@solaris10:~ # shutdown -y -g0 -i0

After the reboot, check if the server is using the metadevice using df -h

Then create the metadevices for the other side of the mirror and attach them

metainit -f d11 1 1 c0t0d0s0
metainit -f d21 1 1 c0t0d0s1
metainit -f d31 1 1 c0t0d0s3

metattach d10 d11
metattach d20 d21
metattach d30 d31

Create the database replicas on the other disk as well

metadb -a -f -c3 /dev/dsk/c0t0d0s7

sccli – Sun StorEdge 3000 Family Command Line Interface

Some examples of what you can do with sccli

root@solaris8:/ # sccli
Available devices:

1. /dev/rdsk/c4t216000C0FF89C9A5d0s2 [SUN StorEdge 3510 SN#09C9A5] (Primary)
2. /dev/rdsk/c4t256000C0FFC9CBB4d0s2 [SUN StorEdge 3510 SN#09CBB4] (Primary)

Please enter selection: 1

sccli> show logical-drives
LD LD-ID Size Assigned Type Disks Spare Failed Status
————————————————————————
ld0 716D7329 408.70GB Primary RAID1 11 0 1 Rebuilding
Write-Policy Default StripeSize 128KB

sccli> show disks
Ch Id Size Speed LD Status IDs Rev
—————————————————————————-
2(3) 32 68.37GB 200MB ld0 ONLINE FUJITSU MAW3073FCSUN72G 1303
S/N 000710B0LLG6
WWNN 500000E014CC09D0
2(3) 33 68.37GB 200MB ld0 ONLINE FUJITSU MAW3073FCSUN72G 1203
S/N 000613B0CJAU
WWNN 500000E011DD1100
2(3) 34 68.37GB 200MB ld0 ONLINE FUJITSU MAW3073FCSUN72G 1203
S/N 000613B0CJAY
WWNN 500000E011DD1130
2(3) 35 68.37GB 200MB ld0 ONLINE FUJITSU MAW3073FCSUN72G 1203
S/N 000613B0CJBF
WWNN 500000E011DD1230
2(3) 36 68.37GB 200MB ld0 ONLINE FUJITSU MAW3073FCSUN72G 1203
S/N 000613B0CJB0
WWNN 500000E011DD1140
2(3) 37 68.37GB 200MB ld0 REBUILD FUJITSU MAW3073FCSUN72G 1303
S/N 000710B0LJYG
WWNN 500000E014C882C0
2(3) 38 68.37GB 200MB ld0 ONLINE FUJITSU MAW3073FCSUN72G 1203
S/N 000614B0CU9N
WWNN 500000E011E1D5B0
2(3) 39 68.37GB 200MB ld0 ONLINE FUJITSU MAW3073FCSUN72G 1203
S/N 000613B0CJ9K
WWNN 500000E011DD06A0
2(3) 40 68.37GB 200MB ld0 ONLINE FUJITSU MAW3073FCSUN72G 1203
S/N 000613B0CJ9F
WWNN 500000E011DD0660
2(3) 41 68.37GB 200MB ld0 ONLINE FUJITSU MAW3073FCSUN72G 1203
S/N 000614B0CUB5
WWNN 500000E011E1D880
2(3) 42 68.37GB 200MB ld0 ONLINE FUJITSU MAW3073FCSUN72G 1203
S/N 000613B0CJ9H
WWNN 500000E011DD0680
2(3) 43 68.37GB 200MB ld0 ONLINE FUJITSU MAW3073FCSUN72G 1203
S/N 000614B0CUBC
WWNN 500000E011E1D8F0

Solaris Auditing facility on a Solaris 9 Brandz

Showing this message on /var/adm/messages file

Jan 22 11:45:01 solaris9brandz C0047233: [ID 702911 daemon.alert] audit failed to start because it cannot read or write the system’s audit state. This may be due to a configuration error. Must reboot to start auditing!

Apparently no problems in the file /etc/system

root@solaris9brandz:/ # grep audit /etc/system
set c2audit:audit_load = 1

Starting audit shows lots of error messages

root@solaris9brandz:/ # /etc/init.d/audit start
Starting BSM services.
auditconfig: auditon(2) failed.
auditconfig: error = Invalid argument(22)
auditconfig: auditon(2) failed.
auditconfig: error = Invalid argument(22)
auditconfig: auditon(2) failed.
auditconfig: error = Invalid argument(22)
auditconfig: auditon(2) failed.
auditconfig: error = Invalid argument(22)

Checking /etc/security/audit_control file doesn’t show any irregularities

root@solaris9brandz:/ # cat /etc/security/audit_control
#
# Copyright (c) 1988 by Sun Microsystems, Inc.
#
# ident “@(#)audit_control.txt 1.4 00/07/17 SMI”
#
dir:/audit
flags: lo,ad,ex
minfree: 20
naflags: lo,ad,ex

Checking System Administration Guide: Oracle Solaris 9 Containers
Shows Limitations Specific to solaris9 Branded Zones
The following limitations apply to solaris9 branded zones:

Solaris Auditing and Solaris Basic Security Module Auditing, described in bsmconv(1M) and auditon(2), are not supported. The audit subsystem will always appear to be disabled.