SysAdmin Blog, TechTips and Reviews

An (ex) System Administrator's Blog

Archives Posts

VxVM vxassist ERROR V-5-1-5455 Operation requires a disk group

January 27th, 2012 by elizar

On this post we will take a closer look at this veritas volume manager error when trying to display the available disk space in an existig datagroup. The error is “VxVM vxassist ERROR V-5-1-5455 Operation requires a disk group

This is a draft post as I currently have no answer yet.. Weird thing is, the vxassist command works on one server and not in the other.. which is spitting out the error in subject.

Take this example:

Working server:

# vxdg list
datadg1 enabled 1169455228.81.sgtjcpb1
datadg2 enabled 1169455429.95.sgtjcpb1
# vxassist -g datadg1 maxsize layout=concat
Maximum volume size: 390506496 (190677Mb)
# vxassist -g datadg2 maxsize layout=concat
Maximum volume size: 676767744 (330453Mb)
# vxassist -g datadg1 maxsize layout=raid5
Maximum volume size: 270483456 (132072Mb)
# vxassist -g datadg2 maxsize layout=raid5
Maximum volume size: 375160832 (183184Mb)

Looks fine right? But when I tried the same syntax on the other sever, I got this:

# vxdg -g sysdg free
sysdg05 emcpower5s2 emcpower5 16777216 2029952 n
sysdg06 emcpower3s2 emcpower3 16777216 2029952 n
sysdg07 emcpower4s2 emcpower4 167772160 2020352 n
# vxassist -d sysdg maxsize layout=concat
VxVM vxassist ERROR V-5-1-5455 Operation requires a disk group

I suspect it has something to do with the Veritas VX version or the OS it is running. Will investigate further and let you know.

UPDATE.. saw the error after 5 minutes.. saw it? I found “d” error.

Archives Posts

(ufsrestore) Make Bootable – Recovering the Root or /usr File System

January 17th, 2012 by elizar

This is some kind of a followup from the first post about ufsdump – how to backup solaris filesystem

1. Replace and partition the disk if it has failed.

2. Because the system cannot be booted from the boot disk, boot from the CD-ROM and re-create the failed file system by issuing the newfs command:

newfs /dev/rdsk/

is the name of the raw disk partition that contains the corrupted file system.

3. Check the new file system by using fsck:

fsck /dev/rdsk/

4. Mount the new file system on a temporary mount point:

mount /dev/dsk//mnt

5. Change to the /mnt directory:

cd /mnt

6. Write protect the tapes so that you don’t accidentally overwrite them.

7. Load the tape and issue the following command:

ufsrestore rf /dev/rmt/0

The entire content of the tape is restored to the file system. All permissions, ownerships, and dates remain as they were when the last incremental tape was created.

8. Verify that the file system is restored:


9. Remove the restoresymtable file that is created and used by ufsrestore to checkpoint the restoration:

rm restoresymtable

10. Change to the root (/) directory:

cd /

11. Unmount the newly created file system:

umount /mnt

12. Check the new file system with fsck:

fsck /dev/rdsk/

The restored file system is checked for consistency.

13. If you are recovering the root (/) file system, create the boot blocks on the root partition by using the installboot command:

installboot /usr/platform/’uname-I’/lib/fs/ufs/bootblk\

The installboot command installs the boot blocks onto the boot disk. Without the boot blocks, the disk cannot boot.

14. Insert a new tape into the tape drive and back up the new file system:

ufsdump 0uf /dev/rmt/n /dev/rdsk/

A level 0 backup is performed. You should immediately make a backup of a newly created file system because ufsrestore repositions the files and changes the inode allocation.

15. Reboot the system with a reconfiguration reboot:

# shutdown -y -g0 -i0
ok boot -r

The system is rebooted.

Extra Notes on UFSrestore

When you restore files in a directory other than the root directory of the file system, ufsrestore re-creates the file hierarchy in the current directory. For example, if you restore to /home files that were backed up from /users/bcalkins/files, the files are restored in the directory /home/users/bcalkins/files.

When you restore individual files and directories, it’s a good idea to restore them to a temporary directory such as /var/tmp. After you verify that you’ve retrieved the correct files, you can move them to their proper locations. You can restore individual files and directories to their original locations; however, if you do so, you should be sure that you do not overwrite newer files with older versions from the backup tape.

You should not forget to make regular backups of your operating system. Losing all the customization you dosuch as adding user accounts, setting up printers, and installing application softwarewould be disastrous. Whenever you make modifications that affect the root (/),/usr, /opt, or other operating system directories, you should bring down the system into single-user mode and perform a level 0 dump.

Filed under Solaris, Solaris 10 having No Comments »

I was here...