Documente Academic
Documente Profesional
Documente Cultură
html
Initializing Memory
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
...
ok devalias
vx-rootmirror /pci@1f,4000/scsi@3/disk@1,0:a
vx-rootdisk /pci@1f,4000/scsi@3/disk@0,0:a
. . .
The administrator then boots the system from the mirror device "vx-rootmirror":
ok boot vx-rootmirror
As the system boots, Veritas volume manager detects that the volumes on the rootdisk are
not accessible, and detaches those plexes from the root volumes. In spite of this, the
system is able to boot cleanly from the mirror device with no operator action required.
ok boot vx-rootmirror
Boot device: /pci@1f,4000/scsi@3/disk@1,0:a File and args:
SunOS Release 5.8 Version Generic_108528-16 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
Starting VxVM restore daemon...
VxVM starting in boot mode...
/usr/sbin/prtconf: getexecname() failed
vxvm:vxconfigd: WARNING: Detaching plex rootvol-01 from volume rootvol
vxvm:vxconfigd: WARNING: Disk rootdisk in group rootdg: Disk device not
found
configuring IPv4 interfaces: hme0.
Hostname: pegasus
VxVM starting special volumes ( swapvol rootvol var )...
VxVM general startup...
dumpadm: no swap devices could be configured as the dump device
The system is coming up. Please wait.
starting rpc services: rpcbind done.
Setting netmask of hme0 to 255.255.255.0
Setting default IPv4 interface for multicast: add net 224.0/4: gateway
pegasus
Starting sshd...
This platform does not support both privilege separation and compression
Compression disabled
syslog service starting.
savecore: no dump device configured
savecore: no dump device configured
dumpadm: no swap devices could be configured as the dump device
Oct 28 14:06:20 pegasus savecore: no dump device configured
Print services started.
/dev/bd.off: not a serial device.
volume management starting.
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t1d0s2 sliced rootmirror rootdg online
- - rootdisk rootdg failed was:c0t0d0s2
# vxprint -ht
Disk group: rootdg
dm rootdisk - - - - NODEVICE
dm rootmirror c0t1d0s2 sliced 3359 17690400 -
# format
Searching for disks...done
Enable vxconfigd:
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 sliced - - error
c0t1d0s2 sliced rootmirror rootdg online
- - rootdisk rootdg failed was:c0t0d0s2
Now the administrator can make use of "vxdiskadm" to manage the process of replacing
the boot disk volumes.
# vxdiskadm
dm rootdisk - - - - NODEVICE
dm rootmirror c0t1d0s2 sliced 3359 17690400 -
The following disk device has a valid VTOC, but does not appear to
have
been initialized for the Volume Manager. If there is data on the disk
that should NOT be destroyed you should encapsulate the existing disk
partitions as volumes instead of adding the disk as a new disk.
Output format: [Device_Name]
c0t0d0
c0t0d0
Goodbye.
Having replaced the disk in Veritas volume manager, the disk device is now listed as
"online", and VxVM is in the process of attaching the replacement plexes to the
original volumes.
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 sliced rootdisk rootdg online
c0t1d0s2 sliced rootmirror rootdg online
# vxprint -ht
Disk group: rootdg
# vxtask list
TASKID PTID TYPE/STATE PCT PROGRESS
161 PARENT/R 0.00% 3/0(1) VXRECOVER rootdisk
162 162 ATCOPY/R 01.22% 0/13423200/163680 PLXATT rootvol
rootvol-01
After about an hour, all of the plexes have been synchronized, and full operating system
redundancy has been restored:
# vxtask list
TASKID PTID TYPE/STATE PCT PROGRESS
# vxprint -ht
Disk group: rootdg