SRDB ID   Synopsis   Date
17643   Recovering from a failed FCAL boot disk   7 Dec 2001

Status Issued

Description
A host that boots from a non-mirrored FCAL disk (either an A5000 or the E3500
internal disks) will have to overcome the hard-coded World Wide Number (WWN)
that each of these disks uses as an integral part of their device path.

On failure of the boot disk the systems administrator must ensure that this 
WWN is correctly updated throughout the system to ensure it will reboot.      
SOLUTION SUMMARY:
Procedure :

1) The boot disk fails and is replaced by another disk with a different
   WWN.

2) Boot the system into single user from the cdrom or network.

3) Label the replacement disk to match the slices from the failed one.

4) Create filesystems on all the slices to be restored.

5) Mount the root filesystem and restore the data from backups.

6) Install the boot block onto the recovered root slice using the
   "installboot" command.

7) With root mounted under "/a" run the following commands to re-build
   the devices tree :

   drvconfig -r /a/devices -p /a/etc/path_to_inst

   cd /devices
   find . -print | cpio -pduVm /a/devices

   disks -r /a
   devlinks -r /a

NOTE: It is currently necessary to use both "drvconfig" and "find | cpio" due
to bugid 4161768, drvconfig does not work properly with socal disks.

8) Configure the "boot-device" parameter in the EEPROM using the 
   "luxadm set_boot_dev /dev/dsk/{root slice entry}" command.

9) Restore the other filesystems on that disk, or comment out the 
   entries for them from /a/etc/vfstab. At least you must have all the 
   Solaris filesystems (root, /var, /usr, /opt, etc.) recovered.

10) Reboot the system from the recovered disk.      
APPLIES TO: Hardware/Disk Storage Subsystem/StorEdge Disk Array/StorEdge A5000 ATTACHMENTS:


Copyright (c) 1997-2003 Sun Microsystems, Inc.