Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1013021.1 : Upgrading System Disk Firmware without Downtime
PreviouslyPublishedAs 217823
Applies to:Sun Fire 12K ServerSun Fire 15K Server Sun Fire E20K Server Sun Fire E25K Server All Platforms ***Checked for relevance on 11-May-2011*** GoalThis procedure describes how to upgrade system disk firmware when the disks are mirrored under LVM.SolutionThis procedure was performed on a system controller of a Sun Fire[TM] E20K Server. There are three metamirrors: d10, d20 and d30, each consisting of submirrors named d[1,2,3][1,2]. For example, d11 and d12 are submirrors of d10.PREPARATION: 1. Using the format command in combination with a search on http://support.oracle.com, the external user will be able to locate the correct patch for downloading. In this example, the disks are 72 GB drives. Each required the patch numbered 116370-XX. 2. Once the patch is located, it should be downloaded to the system where the patch will be applied. 3. Change your focus to the patch directory and work from there. (This is suggested for the convienence of the author rather than for technical reasons). 4. Determine the metadevices available: (to be brief only the first metadevice will be shown) root@ssc1-aopc # metastat d30: Mirror Submirror 1: d32 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 122223936 blocks (58 GB) d32: Submirror of d30 State: Okay Size: 122223936 blocks (58 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c0t3d0s7 0 No Okay Yes d31: Submirror of d30 State: Okay Size: 122223936 blocks (58 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c0t2d0s7 0 No Okay Yes Note: The system is using two physical devices, c0t3d0 and c0t2d0. Also, other metadevices, d10 and d20 are not displayed. 5. Either of the sub-mirrors may be detached from the mirror, provided that all detached sub-mirrors are part of the same physical device; say c0t2d0. root@ssc1-aopc # detattach d30 d31 root@ssc1-aopc # detattach d20 d21 root@ssc1-aopc # detattach d10 d11 Which frees the sub-mirrors, d11, d21, and d31 from the respective mirrors d10, d20 and d30. 6. The finall preparation will be to remove any metadb's from the the system disk slices. As seen below, metadb's exist on slices 4 and 5 of the disk to be patched: c0t2d0. root@ssc1-aopc # metadb -i flags first blk block count a m p luo 16 8192 /dev/dsk/c0t2d0s4 a p luo 8208 8192 /dev/dsk/c0t2d0s4 a p luo 16400 8192 /dev/dsk/c0t2d0s4 a p luo 16 8192 /dev/dsk/c0t2d0s5 a p luo 8208 8192 /dev/dsk/c0t2d0s5 a p luo 16400 8192 /dev/dsk/c0t2d0s5 a p luo 16 8192 /dev/dsk/c0t3d0s4 a p luo 8208 8192 /dev/dsk/c0t3d0s4 a p luo 16400 8192 /dev/dsk/c0t3d0s4 a p luo 16 8192 /dev/dsk/c0t3d0s5 a p luo 8208 8192 /dev/dsk/c0t3d0s5 a p luo 16400 8192 /dev/dsk/c0t3d0s5 r - replica does not have device relocation information o - replica active prior to last mddb configuration change u - replica is up to date l - locator for this replica was read successfully c - replica's location was in /etc/lvm/mddb.cf p - replica's location was patched in kernel m - replica is master, this is replica selected as input W - replica has device write errors a - replica is active, commits are occurring to this replica M - replica had problem with master blocks D - replica had problem with data blocks F - replica had format problems S - replica is too small to hold current data base R - replica had device read errors So, the metadb's must be removed: root@ssc1-aopc # metadb -d /dev/dsk/c0t2d0s4 root@ssc1-aopc # metadb -d /dev/dsk/c0t2d0s5 root@ssc1-aopc # metadb -i flags first blk block count a p luo 16 8192 /dev/dsk/c0t3d0s4 a p luo 8208 8192 /dev/dsk/c0t3d0s4 a p luo 16400 8192 /dev/dsk/c0t3d0s4 a p luo 16 8192 /dev/dsk/c0t3d0s5 a p luo 8208 8192 /dev/dsk/c0t3d0s5 a p luo 16400 8192 /dev/dsk/c0t3d0s5 r - replica does not have device relocation information o - replica active prior to last mddb configuration change u - replica is up to date l - locator for this replica was read successfully c - replica's location was in /etc/lvm/mddb.cf p - replica's location was patched in kernel m - replica is master, this is replica selected as input W - replica has device write errors a - replica is active, commits are occurring to this replica M - replica had problem with master blocks D - replica had problem with data blocks F - replica had format problems S - replica is too small to hold current data base R - replica had device read errors Now the preparations are complete and we are ready to continue patching the system disk c0t2d0. PATCHING THE DISK: 1. Run following command: root@ssc1-aopc # pwd /116370-13 2. Execute the download utility: root@ssc1-aopc # ./download Firmware Download Utility, V4.3.1 ************************** WARNING ************************** NO OTHER ACTIVITY IS ALLOWED DURING FIRMWARE UPGRADE!!! No other programs including any volume manager (e.g. Veritas, SDS, or Vold) should be running. Other host systems sharing any I/O bus with this host must either be offline or disconnected. Any interruption (e.g. power loss) during upgrade can result in damage to devices being upgraded. Any disk to be upgraded should first have its data backed up. *************************************************************** Searching for devices... DISK DEVICES Device Rev Product c0t2d0-c0t3d0: 0507 ST373307L -- SUN72G Total Devices: 2 **************** Although two devices show requiring this patch, only c0t2d0 will be upgraded. HELP will list the commands available in the utility. **************** Enter command: help Examples: program - program all devices program disk - program all disk devices c1 - program disk devices on c1 c1t2d0 - program disk c1t2d0 c1t2d0-c2t3d0 - program disks c1t2d0-c2t3d0 c1t2d0- - program disks from c1t2d0 rmt/0 - program tape rmt/0 inquiry - display device inquiry data list disk - display only disk devices list ? - display help for list command quit - exit Commands: program [options] - program devices list [options] - list devices inquiry [options] - list device inquiry data exclude [device] - exclude devices include [device] - include devices mode select [options] - reset all mode page values Device/Options: disk - disk devices all - all devices cd - cd devices ata - ATA devices tape - tape devices scsi - FC-AL/SCSI devices ? - command help rsm - A1000/3000 devices ************* We wish to exclude the system disk that is currently running the system: c0t3d0s0. Recall, all slices of c0t2d0 were detached. ************* Enter command: exclude c0t3d0 c0t3d0: device excluded ************* Update the firmware on the drive ************* Enter command: program Upgrading devices... c0t2d0s4: Open failed, you must be the sole user! <--------- if you see this check for more metadb's. Suppose the error did not occur, then you should see: c0t2d0: Successful download c0: recovery delay, 45 sec. ************** Listing the drives remaining to be updated ************** Enter command: list DISK DEVICES Enter command: quit ************* At this point the firmware on c0t2d0 has been upgraded. The metadbs must be recreated, the sub-mirrors, d12, d22 and d32 must be reattached, allowed to resync, and then the procedure may be safely completed using the drive c0t3d0 while running on c0t2d0. ************** RECREATING THE METADBs 1. Enter the commands: root@ssc1-aopc # metadb -c 3 -a /dev/dsk/c0t2d0s4 root@ssc1-aopc # metadb -c 3 -a /dev/dsk/c0t2d0s5 To verify that the metadbs have been created, enter: root@ssc1-aopc # metadb -i flags first blk block count a u 16 8192 /dev/dsk/c0t2d0s4 a u 8208 8192 /dev/dsk/c0t2d0s4 a u 16400 8192 /dev/dsk/c0t2d0s4 a u 16 8192 /dev/dsk/c0t2d0s5 a u 8208 8192 /dev/dsk/c0t2d0s5 a u 16400 8192 /dev/dsk/c0t2d0s5 a p luo 16 8192 /dev/dsk/c0t3d0s4 a p luo 8208 8192 /dev/dsk/c0t3d0s4 a p luo 16400 8192 /dev/dsk/c0t3d0s4 a p luo 16 8192 /dev/dsk/c0t3d0s5 a p luo 8208 8192 /dev/dsk/c0t3d0s5 a p luo 16400 8192 /dev/dsk/c0t3d0s5 r - replica does not have device relocation information o - replica active prior to last mddb configuration change u - replica is up to date l - locator for this replica was read successfully c - replica's location was in /etc/lvm/mddb.cf p - replica's location was patched in kernel m - replica is master, this is replica selected as input W - replica has device write errors a - replica is active, commits are occurring to this replica M - replica had problem with master blocks D - replica had problem with data blocks F - replica had format problems S - replica is too small to hold current data base R - replica had device read errors REATTACHING THE SUB-MIRRORS 1. Enter the following commands: root@ssc1-aopc # metattach d10 d11 d10: submirror d11 is attached root@ssc1-aopc # metattach d20 d21 d20: submirror d21 is attached root@ssc1-aopc # metattach d30 d31 d30: submirror d31 is attached 2. Verify that the sub-mirrors are resyncing. root@ssc1-aopc # metastat Feb 9 15:02:56 ssc1-aopc scman: NOTICE: scman1 Link up d30 submirror 0: d31 State: Resyncing Submirror 1: d32 State: Okay Resync in progress: 0 % done Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 122223936 blocks (58 GB) d31: Submirror of d30 State: Resyncing Size: 122223936 blocks (58 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c0t2d0s7 0 No Okay Yes d32: Submirror of d30 State: Okay Size: 122223936 blocks (58 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c0t3d0s7 0 No Okay Yes ************* Again, the display for d20 and d10 are not shown. ************* To periodically check if the syncing has completed, run the command: root@ssc1-aopc # metastat|grep % Resync in progress: 0 % done Resync in progress: 23 % done Resync in progress: 6 % done When nothing is returned, the resync of all sub-mirrors have completed. You may repeat this procedure, upgrading the remaining system disk. IMPORTANT!!! When you rerun the ./download command to upgrade the remaining disk, you must use the include c0t3d0s (in this example) in order to see and program the disk. Attachments This solution has no attachment |
||||||||||||
|