Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1008580.1
Update Date:2011-03-03
Keywords:

Solution Type  Problem Resolution Sure

Solution  1008580.1 :   Recovering from a failed FCAL boot disk  


Related Items
  • Sun Blade 2000 Workstation
  •  
  • Sun Fire 280R Server
  •  
  • Sun Enterprise 3500 Server
  •  
  • Sun Storage A5000 Array
  •  
  • Sun Storage A5200 Array
  •  
  • Sun Netra 20 Server
  •  
  • Sun Blade 1000 Workstation
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - Other
  •  

PreviouslyPublishedAs
211723


Symptoms
A host that boots from a non-mirrored FCAL disk (either a Sun StorEdge[TM] A5000 or the Sun Enterprise[TM] 3500 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 system administrator must ensure that this
WWN is correctly updated throughout the system to ensure it will reboot.



Resolution
Procedure :
1) The boot disk fails and is replaced by another disk with a different

WWN.

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

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

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. Refer to the installboot manpage for the syntax.

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

  /usr/sbin/drvconfig -r /a/devices -p /a/etc/path_to_inst
  cd /devices
/usr/bin/find . -print | cpio -pduVm /a/devices
  /usr/sbin/disks -r /a
/usr/sbin/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.

NOTE: In Solaris[TM] 8 FCS or higher releases, you can use devfsadm in place of the commands in step 7 as follows:

  # /usr/sbin/devfsadm -c disk -r /a -p /a/etc/path_to_inst

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 the very least, you must have all the
Solaris filesystems (root, /var, /usr, /opt, etc.) recovered.

10) Reboot the system from the recovered disk.

Pls take note of the above steps are applicable for Sun Fire v480 Server, Sun Fire V490 Server, Sun Fire V880 Server and Sun Fire V890 Server also.



Product
Sun StorageTek A5000 Array
Sun Enterprise 3500 Server
Sun Fire 280R Server
Sun Blade 2000 Workstation
Sun Blade 1000 Workstation
Netra 20 Server
Sun StorageTek A5200 Array
Sun StorageTek A5100 Array

Internal Comments
Document ID 17658 is merged into this document.



boot, disk, failure, WWN, FCAL, drvconfig, set_boot_dev
Previously Published As
17643

Change History
Date: 2007-02-23
User Name: 95826
Action: Approved
Comment: - verified metadata : new product list ok
- changed review date to 2008-02-23
- checked audience : contract
Publishing
Version: 6
User Name: 98025
Action: Approved
Comment: As per cu request sunfire product has been added into the contents of the doc, pls perform final review on this doc, thanks.
Regards,
Prabhu.

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback