10-07-2002
Our company has created a procedure for creating a backup root disk called BROOT. All new boxes are put into production with this functionality.
It was meant for an add'l recovery disk for VG00, but it can be used to copy from one disk to another, when you might ever upgrade a Disk to a larger one.
Here is the script. We have a script that creates this script, but this can be edited and reused. This should give you something to work with.
I didn't write this, but it is very good for this type of work
root:/usr/localcw/opt/broot
# cat vgbroot.script
#!/usr/bin/ksh
exec >/usr/localcw/opt/broot/vgbroot.output 2>&1
mkdir /broot
mkdir /dev/vgbroot
mknod /dev/vgbroot/group c 64 0x030000
pvcreate -fB /dev/rdsk/c0t2d0
mkboot /dev/rdsk/c0t2d0
mkboot -a "hpux -lq" /dev/rdsk/c0t2d0
lifcp /dev/dsk/c0t2d0:AUTO -
vgcreate /dev/vgbroot /dev/dsk/c0t2d0
lvcreate -s y -C y -r n -n bstand vgbroot
lvextend -L 1 /dev/vgbroot/bstand /dev/dsk/c0t2d0
lvextend -L 300 /dev/vgbroot/bstand
lvlnboot -r /dev/vgbroot/bstand /dev/vgbroot
lvlnboot -v
umount /broot/bstand
lvcreate -s y -C y -r n -n bswap vgbroot
lvextend -L 1 /dev/vgbroot/bswap /dev/dsk/c0t2d0
lvextend -L 1000 /dev/vgbroot/bswap
lvlnboot -s /dev/vgbroot/bswap /dev/vgbroot
lvlnboot -v
grep -q "/dev/vgbroot/bswap swap swap pri=0 0 0 0" /etc/fstab
if (( $? != 0 ))
then
print "/dev/vgbroot/bswap swap swap pri=0 0 0 0" >> /etc/fstab
fi
umount /broot/bswap
lvcreate -s y -C y -r n -n broot vgbroot
lvextend -L 1 /dev/vgbroot/broot /dev/dsk/c0t2d0
lvextend -L 252 /dev/vgbroot/broot
lvlnboot -r /dev/vgbroot/broot /dev/vgbroot
lvlnboot -v
umount /broot/broot
lvcreate -s y -C y -n bopt vgbroot
lvextend -L 1 /dev/vgbroot/bopt /dev/dsk/c0t2d0
lvextend -L 1200 /dev/vgbroot/bopt
mkdir /broot/bopt
newfs /dev/vgbroot/rbopt
mount /dev/vgbroot/bopt /broot/bopt
grep -q "/dev/vgbroot/bopt /broot/bopt vxfs delaylog 0 2" /etc/fstab
if (( $? != 0 ))
then
print "/dev/vgbroot/bopt /broot/bopt vxfs delaylog 0 2" >> /etc/fstab
fi
umount /broot/bopt
lvcreate -s y -C y -n busr vgbroot
lvextend -L 1 /dev/vgbroot/busr /dev/dsk/c0t2d0
lvextend -L 1200 /dev/vgbroot/busr
mkdir /broot/busr
newfs /dev/vgbroot/rbusr
mount /dev/vgbroot/busr /broot/busr
grep -q "/dev/vgbroot/busr /broot/busr vxfs delaylog 0 2" /etc/fstab
if (( $? != 0 ))
then
print "/dev/vgbroot/busr /broot/busr vxfs delaylog 0 2" >> /etc/fstab
fi
umount /broot/busr
lvcreate -s y -C y -n bvar vgbroot
lvextend -L 1 /dev/vgbroot/bvar /dev/dsk/c0t2d0
lvextend -L 1600 /dev/vgbroot/bvar
mkdir /broot/bvar
newfs /dev/vgbroot/rbvar
mount /dev/vgbroot/bvar /broot/bvar
grep -q "/dev/vgbroot/bvar /broot/bvar vxfs delaylog 0 2" /etc/fstab
if (( $? != 0 ))
then
print "/dev/vgbroot/bvar /broot/bvar vxfs delaylog 0 2" >> /etc/fstab
fi
umount /broot/bvar
lvcreate -s y -C y -n bopenv vgbroot
lvextend -L 1 /dev/vgbroot/bopenv /dev/dsk/c0t2d0
lvextend -L 2000 /dev/vgbroot/bopenv
mkdir /broot/bopenv
newfs /dev/vgbroot/rbopenv
mount /dev/vgbroot/bopenv /broot/bopenv
grep -q "/dev/vgbroot/bopenv /broot/bopenv vxfs delaylog 0 2" /etc/fstab
if (( $? != 0 ))
then
print "/dev/vgbroot/bopenv /broot/bopenv vxfs delaylog 0 2" >> /etc/fstab
fi
umount /broot/bopenv
# The following sequence of coding was modified by Peter Gunawan
# on 5/19/2001
lvlnboot -b /dev/vgbroot/bstand
lvlnboot -r /dev/vgbroot/broot
lvlnboot -s /dev/vgbroot/bswap
lvlnboot -v /dev/vgbroot
vgcfgbackup vgbroot
cp /etc/fstab /etc/fstab.19042002
grep -v ^/dev/vgbroot /etc/fstab >/tmp/fstab
cp /tmp/fstab /etc/fstab
echo "-------- dd copy completed - psg"
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
$ errpt | more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR
B8113DD1 ... (0 Replies)
Discussion started by: mcastill66
0 Replies
2. UNIX for Dummies Questions & Answers
I have a SunOS 5.8 server. I suspect there may be errors with one of the physical disks (based on someone reporting hearing a "clicking sound" during the night shift, however I do not hear anything this morning).
Which log would show this?
Thank you. (2 Replies)
Discussion started by: FredSmith
2 Replies
3. AIX
Hi,
I'm getting the errors below in the errpt report for a IBM Blade server. I'm guessing there's a problem with one of the disks but don't know how I can confirm this. Can anyone offer any suggestions?
Regards
Gareth (4 Replies)
Discussion started by: m223464
4 Replies
4. UNIX for Dummies Questions & Answers
Hi all, dummy here.... I have major errors on entering the shell. On login I get:
-bash: dircolors: command not found
-bash: tr: command not found
-bash: fgrep: command not found
-bash: grep: command not found
-bash: grep: command not found
-bash: id: command not found
-bash: [: =: unary... (12 Replies)
Discussion started by: wcmmlynn
12 Replies
5. Filesystems, Disks and Memory
so we have a solrais 9 system attached to an HP SAN.
we are using sssu to do snap clones every hour.
the only problem is the we get write errors on the solrais system every time we do a snap.
from /var/adm/messages
Apr 21 14:37:48 svr001 scsi: WARNING:... (0 Replies)
Discussion started by: robsonde
0 Replies
6. Shell Programming and Scripting
I am looking for some tips or suggestions in how to do the following.
1) From a Solaris server, I run the command iostat -En and receive output that is similiar to the following which shows your disks along with the cdrom/dvdrom:
c0t2d0 Soft Errors: 0 Hard Errors: 0 Transport... (1 Reply)
Discussion started by: sunsysadm2003
1 Replies
7. Solaris
Hi all.
I am seeing in one of our less-used servers that it crashed and now won't restart. I get the message 'continue with normal startup or boot into maintenance mode'.
I go into maintenance and run fsck on /usr0 (mentioned in error at restart) it then reboots but goes right back to... (3 Replies)
Discussion started by: jamie_collins
3 Replies
8. AIX
Hi,
The system is a Power6 8204 with an external storage 7031. OS is AIX 5.3. I replaced a failed disk hdisk28 and put it back to the volume group. Everything looks just fine. After the replacement, errpt has kept sending "Perm DISK OPERATION ERROR".
Other than the error, everything still... (1 Reply)
Discussion started by: aixlover
1 Replies
9. Ubuntu
Hi,
During start up I got the message "Your disk drives are being checked for errors". But it went so fast that I could read following messages.
Once logged I though I could find it in "dmesg" but nothing...
May someone know where I can find plese ? :) (3 Replies)
Discussion started by: xib.be
3 Replies
10. Solaris
Hi,
What are the initial checks needs to be done while observing hard errors on one of the hard disk drive.
Thanks,
Babu. (1 Reply)
Discussion started by: lbreddy
1 Replies
LEARN ABOUT OSF1
voldiskadd
voldiskadd(8) System Manager's Manual voldiskadd(8)
NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager
SYNOPSIS
/usr/sbin/voldiskadd disk-address-list
DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for
use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility.
One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp
(for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names
in the /dev/disk directory.
For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a
The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk
to exclude (for example, dsk5).
The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified,
that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for
future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the
disk group.
If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated.
Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should
not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage
Manager. For new disks, all space on the disk becomes free space in the disk's disk group.
Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target
disks for an operation.
The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions.
Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group.
This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk
group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot
spare device. Creating new disk groups in which to import new disks.
If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist-
ing contents.
This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a
disk label. Encapsulation is performed by calling volencap. 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 volrecover script.
ERRORS
You may receive the following messages when using the voldiskadd command:
Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open.
This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be
a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device.
special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data.
Would you like to continue?? [y,n,q,?] (default: n)
This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints
this message to warn that a disk partition may have valid data which could be destroyed.
If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning
message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM.
FILES
A list of disks to exclude from use by voldiskadd.
SEE ALSO
disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8)
voldiskadd(8)