Sie sind auf Seite 1von 3

2/16/2018 Replacing a failed bootdisk

Veritas Volume Manager


unixway > volume management > solaris > veritas > failed boot

System fails to boot


Replacing a failed bootdisk
Boot from mirror
In the following example, the host has a failed bootdisk (c0t0d0). Fortunately, the system is using Veritas volume manager, with Check extent of failures
a mirror at c0t1d0. The following sequence of steps can be used to restore the system to full redundancy. Replace failed disk and
restore redundancy
System fails to boot
When the system attempts to boot, it fails to find a valid device as required by the boot-device path at device alias "disk". It then
attempts to boot from the network:

screen not found.


Can't open input device.
Keyboard not present. Using ttya for input and output.

Sun Ultra 30 UPA/PCI (UltraSPARC-II 296MHz), No Keyboard


OpenBoot 3.27, 512 MB memory installed, Serial #9377973.
Ethernet address 8:0:20:8f:18:b5, Host ID: 808f18b5.

Initializing Memory
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
...

Boot from mirror


At this point, the administrator realizes that the boot disk has failed, and queries the device aliases to find the one
corresponding to the veritas mirror:

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":
http://unixway.com/vm/veritasvm/failedbootdisk.html 1/3
2/16/2018 Replacing a failed bootdisk

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.

No VVR license installed on the system; vradmind not started.

No VVR license installed on the system; in.vxrsyncd not started.


The system is ready.

pegasus console login:

Check extent of failures


http://unixway.com/vm/veritasvm/failedbootdisk.html 2/3
2/16/2018 Replacing a failed bootdisk

Once the reboot is complete, the administrator then logs into the system and checks the status of the system. Note that the
device c0t0d0s2 is listed as "failed", and the all plexes on that device are listed as "DISABLED/NODEVICE".

pegasus console login: ro

http://unixway.com/vm/veritasvm/failedbootdisk.html 3/3