We all know that storage is key requirement for any server environment and the requirement for storage is always dynamic in nature. When we talk about the cost, providing highly redundant storage to each server is most expensive task for any organization and no company want to waste the storage with fixed allocation to each server. And  Companies  had huge requirement for the applications which has capability to dynamically add or reduce storage to the servers without affecting the operations.  And this requirement increased the demand for user friendly and effective volume manager tools.  Both the Operating System Vendors and third party vendors started providing volume manager tools to the industry, and below are some of the major Volume manager tools in place right now:

• Solaris native Volume manager tools – SVM  and ZFS
• Linux  native volume manager tools – LVM
• Symantic native volume manager tools  – VxVM Full Story

Error while adding  replaced disk to the root mirror

Solaris:/etc/vx/bin> vxdg -g rootdg -k adddisk rootdisk=c1t4d0s2

VxVM vxdg ERROR V-5-1-10127 associating disk-media rootdisk with c1t4d0s2:    Disk public region is too small

Resolution: 

Solaris :/etc/vx/bin> vxdisk list

• DEVICE       TYPE            DISK         GROUP        STATUS
• c1t4d0s2     auto:sliced     -            -            online                   replaced disk
• c2t0d0s2     auto:none       -            -            online invalid
• c2t1d0s2     auto:sliced     localdg01    localdg      online
• c2t2d0s2     auto:sliced     rootmirror   rootdg       online nohotuse   existing root mirror
• c2t3d0s2     auto:sliced     localdg02    localdg      online
• c2t5d0s2     auto:sliced     -            -            online
• c3t176d0s2   auto:sliced     loachdg73    loachdg      online
• c3t176d1s2   auto:sliced     loachdg74    loachdg      online
• c3t176d2s2   auto:sliced     loachdg75    loachdg      online
• c3t176d3s2   auto:sliced     loachdg76    loachdg      online
• c3t176d4s2   auto:sliced     loachdg77    loachdg      online
• c3t176d5s2   auto:sliced     loachdg78    loachdg      online
• c3t176d6s2   auto:sliced     loachdg79    loachdg      online
• c3t176d7s2   auto:sliced     loachdg80    loachdg      online
• c3t176d63s2  auto:sliced     loachdg61    loachdg      online
• c3t176d64s2  auto:sliced     loachdg62    loachdg      online
• c3t176d65s2  auto:sliced     loachdg63    loachdg      online
• c3t176d66s2  auto:sliced     loachdg64    loachdg      online
• c3t176d67s2  auto:sliced     loachdg65    loachdg      online
• c3t176d68s2  auto:sliced     loachdg66    loachdg      online
• c3t176d69s2  auto:sliced     loachdg67    loachdg      online
• c3t176d70s2  auto:sliced     loachdg68    loachdg      online
• c3t176d71s2  auto:sliced     loachdg69    loachdg      online
• c3t176d72s2  auto:sliced     loachdg70    loachdg      online
• c3t176d73s2  auto:sliced     loachdg71    loachdg      online
• c3t176d74s2  auto:sliced     loachdg72    loachdg      online Full Story

Below procedure explains you about ‘ booting from an alternate boot disk’

Full Story

To replace disk for a failed boot disk must have at least as much storage capacity as was in use on the disk being replace. It must be large enough to accommodate all subdisks of the original disk at their current disk offsets

# vxprint -g rtdg -st -e ‘sd_disk=”rtdg01″‘

Disk group: rtdg

SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE

…

sd rtdg01-01 swapvol-01 rtdg01 0 1045296 0 c0t0d0 ENA

sd rtdg01-02 rootvol-01 rtdg01 1045296 16751952 0 c0t0d0 ENA

From the output, add the DISKOFFS and LENGTH values for the last subdisk listed for the disk. This size is in 512 byte sectors. Divide this number by 2 for the size in KB. Full Story

This procedure removes the root disk from DiskSuite control while leaving all other data under DiskSuite intact.

A. Boot system from CD-ROM or Single User Mode ( using Single usermode, you have to be careful to not miss any of the configuration changes).

B. Restore or modify necessary files.

C. Disable DiskSuite on the root partition(s).

D. Boot system.

E. Re-mirror root disk. Full Story

Possible reasons for a boot failure:

1. The boot device cannot be opened.
2. The system cannot be be booted from unusable or stale plexes.
3. A UNIX partition is invalid.
4. There are incorrect entries in /etc/vfstab.
5. Configuration files are missing or damaged

Full Story