Patch-ID# 107028-02 Keywords: MAA3182S MAB3091S MAB3045S 18GB 9GB 4GB disk firmware Synopsis: Hardware, 18/9/4GB disks: Download program and MAA3182S/MAB3091S/MAB3045S 2107 firmware Date: May/11/2000 Solaris Release: 2.5.1 2.6 7 SunOS Release: 5.5.1 5.6 5.7 Unbundled Product: Hardware/Disk Unbundled Release: Fujitsu_MAA3182S:MAB3091S:MASB3045S_18-9-4GB_disks Xref: Topic: Relevant Architectures: sparc BugId's fixed with this patch: 4175722 4336161 Changes incorporated in this version: 4336161 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: NOTE: Fujitsu MAA3182S 18GB disks, Fujitsu MAB3091S 9GB disks, Fujitsu MAB3045S 4GB disks NOTE: Solaris 2.5.1 103640-32 or higher 2.6 105568-16 or higher 105580-08 or higher (for Ultra-30/60) 7 106980-10 or higher Obsoleted by: Files included with this patch: .download MAA3182S.2107.fw README.107028-02 download download32 download64 patchinfo Problem Description: [ 107028-02 upgrades rev. 1907 drive firmware ] 4336161 download64 ALWAYS wants to relabel disks with valid labels Added Patchpro patchinfo file. [ 107028-01 upgrades rev. 1907 drive firmware ] 4175722 Fujitsu 9.1Gb disk gives spurious LUN 8 on ISP controller Enables SMART reporting. ************************************************************************** ************************************************************************** **WARNING:****WARNING:****WARNING:****WARNING:****WARNING:****WARNING:** 1. The system MUST BE IDLE during the download process! No other programs should be running while using this utility is being used. Failure to do so may cause the devices being upgraded to fail or the system to crash. Volume managers such as Veritas, SDS, Arraymon, and Vold must be idle and any disks unconfigured. Note, due to an open/close accounting bug (see bug 4129295) in sd and ssd drivers, you must reboot the system after unconfiguring any disks used by them. This accounting bug prevents the upgrade utility from acquiring sole ownnership of the disk so it will not be eligible for upgrade. Note, Arraymon will be disabled during download startup and enabled on exit. Any other computers sharing the same I/O bus as the host system must be either disconnected or offline to prevent possible disruption of the firmware download process. 2. If any upgrade failures occur, do not continue upgrading devices. Loss of power during download can result in damage to the devices under upgrade and require replace. If any failures occur, please collect the following log files: "./download.log" or "/var/tmp/download.log", "/var/adm/messages", and an explorer dump. Please forward these files to your service provider for analysis. 3. This package will only upgrade the identified Sun disks. 4. If the High Availability kernel device polling is running, it will be disabled. It will not be re-enabled. 5. If using Veritas, "deport" the volume to release the volume from Veritas control. Do not "remove" the volume as this will erase the data stored on the Volume. 6. If you have reconfigured A1000/3000 SCSI systems, the /dev directories may become corrupted. Download will detect this problem and ask for permission to repair the problem. If not repaired, affected devices will not be eligable for upgrade. 7. If you have dual-active A1000/3000 controllers and one of the controllers has no luns, they will not be eligable for upgrade. This is because an access path is only provided if a controller has luns. Without an access path, the controller cannot be accessed and both controllers are required for upgrade operations. The faster responding dual-active controller will be displayed. So, there can be some display variation. This does not impact download operation as it uses both controllers. 8. Follow the instructions given below. You may program one drive, a range of drives, or all drives at once with this tool. ************************************************************************** ************************************************************************** Patch Installation Instructions: -------------------------------- 1. General guidelines for upgrading: BACK UP ALL FILESYSTEMS. STOP ALL APPLICATIONS. The system must be idle during the firmware upgrade process. UNMOUNT all file systems on the drives to be upgrade. Disks with mounted file systems are not eligible for upgrade. UNCONFIGURE devices from volume manager. REBOOT THE SYSTEM if you unconfigured any disks from volume manager (e.g. Veritas). Otherwise, you will not be able to upgrade any previously configured disks. UPGRADE the disks. Follow the given instructions in the procedure section below. In case of any disruption or unforeseen events happening on the relevant bus during the firmware download process, it may be that the upgraded disk becomes non-functional. In this event, it will be necessary to swap out the disk. This would happen as a result of an incomplete or corrupted firmware file being downloaded. Loss of power during the upgrade process would also damage the disk. **NOTE** If you cannot upgrade devices due to volume manager interference, try booting of the Solaris 2.6 release CD. **NOTE** If a system disk is to be upgraded, the upgrade utility will allow it to be upgraded if the system is in single-user mode (e.g. "boot -s"). Otherwise, the system disk will not be eligible for upgrade. RECONFIGURE devices to volume manager. **NOTE** As Download disables kernel high availability device polling, it may be necessary to reboot the system to restart it. 2. Procedure: The procedure to be used for upgrading the drive firmware is explained below. Upgrade time will be approximately 2 minutes for system except for A3000/1000. A3000/1000''s will take up to 60 minutes. The long upgrade time is due to a controller limitation of these subsystems. a) Unpack the patch (through tar) into any directory, say . (Note, if the patch ends in a ".Z" suffix, you will need to first uncompress it.) So, you would type: % su root # cd # tar xf b) In the patch directory, as root, type the "download" command: # ./download c). Select the devices to be upgraded (see example below). **NOTE** Any device that is in-use by another application will not be upgraded. The following warning message will be issued: c1t3d0s0: Open failed, you must be the sole user! **NOTE** This upgrade can result in error messages in the console window and/or the terminal "download" window. It is normal for the FC-AL link to go offline for a few seconds and then return to the online state. The disk mode pages will also be restored to the default values. **NOTE** For A3000/1000''s, the internal disk "C" and "T" numbers are derived from the first active controller found. The "D" number is encoded to indicate it''s position using the following formula: D = (tray_number * 100) + target_id. d). After the devices have been upgraded, the displayed device list will be refreshed. Devices remaining to be upgraded or failed devices will be displayed. Failed devices will be marked with a "****" in the rev field. **NOTE** If all devices have been upgraded, the following message will be displayed: No devices found to upgrade! e). To display the full list of devices including the upgrades ones, type ''inquiry'' (see example below). **NOTE** Only the first two digits of the firmware version number will change. The last two digits will not change. So, a disk with 0410 firmware would report revision 1078 for example. f). Quit the "download" program by typing ''quit'' (see example below). ************************************************************************** ************************************************************************** EXAMPLES: # ./download Firmware Download Utility, V3.27 ************************** 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 it''s data backed up. *************************************************************** Searching for devices... DISK DEVICES: Device Rev Product c0t9d0-c0t10d0: 1907 FUJITSU MAB3091S -- SUN9.0G c0t11d0-c0t12d0: 1907 FUJITSU MAA3182S -- SUN18G c0t13d0-c0t14d0: 1907 FUJITSU MAB3045S -- SUN4.2G Total Devices: 6 # ######################################### # # Single disk upgrade example: # ######################################### # Enter command: c0t9d0 Upgrading disks... c0t9d0: Successful download c0: recovery delay, 54 sec. c0: recovery delay, 54 sec. c0t9d0: Page 28(0x1c) defaulted DISK DEVICES: Device Rev Product c0t10d0: 1907 FUJITSU MAB3091S -- SUN9.0G c0t11d0-c0t12d0: 1907 FUJITSU MAA3182S -- SUN18G c0t13d0-c0t14d0: 1907 FUJITSU MAB3045S -- SUN4.2G Total Devices: 5 # ######################################### # # Single controller upgrade example: # ######################################### # Enter command: c0t0d0-c0t14d0 Upgrading disks... c0t11d0: Successful download c0t14d0: Successful download c0t13d0: Successful download c0t10d0: Successful download c0t9d0: Successful download c0t12d0: Successful download c0: recovery delay, 48 sec. c0: recovery delay, 48 sec. c0t10d0: Page 28(0x1c) defaulted c0t9d0: Page 1(0x1) defaulted c0t9d0: Page 28(0x1c) defaulted c0t11d0: Page 28(0x1c) defaulted c0t12d0: Page 28(0x1c) defaulted c0t13d0: Page 28(0x1c) defaulted c0t14d0: Page 28(0x1c) defaulted DISK DEVICES: No devices found to upgrade! # ######################################### # # Entire system upgrade example: # ######################################### # Enter command: program Upgrading disks... c0t13d0: Successful download c0t10d0: Successful download c0t14d0: Successful download c0t9d0: Successful download c0t12d0: Successful download c0t11d0: Successful download c0: recovery delay, 47 sec. c0: recovery delay, 48 sec. c0t10d0: Page 28(0x1c) defaulted c0t9d0: Page 1(0x1) defaulted c0t9d0: Page 28(0x1c) defaulted c0t11d0: Page 28(0x1c) defaulted c0t12d0: Page 28(0x1c) defaulted c0t13d0: Page 28(0x1c) defaulted c0t14d0: Page 28(0x1c) defaulted DISK DEVICES: No devices found to upgrade! # ######################################### # # To view upgraded drives after upgrade: # ######################################### # Enter command: inquiry DISK DEVICES: c0t0d0: 0728 SEAGATE ST39102LC -- SUN9.0G, 001144 c0t9d0: 2107 FUJITSU MAB3091S -- SUN9.0G, 9741001872 c0t10d0: 2107 FUJITSU MAB3091S -- SUN9.0G, 9744002300 c0t11d0: 2107 FUJITSU MAA3182S -- SUN18G, 9746002822 c0t12d0: 2107 FUJITSU MAA3182S -- SUN18G, 9746002545 c0t13d0: 2107 FUJITSU MAB3045S -- SUN4.2G, 9843M24659 c0t14d0: 2107 FUJITSU MAB3045S -- SUN4.2G, 9843M24638 Total Devices: 7 # ######################################### # # To exit: # ######################################### # Enter command: quit Special Install Instructions: ------------------------------------------------------ If you have an A3X00 in Independent Controller Mode, where each controller is attached to a different host system, the drives will only be upgraded if one of the two hosts is shutdown and the controller it is attached to is removed from the A3X00. To accomplish this you will need to determine which disks are owned by which controller through RM6. To upgrade the disks on the first host, shutdown the second host and remove its connected A3X00 controller. On the first host specify its disks for upgrade. If you specify a disk owned by the removed controller, download will fail. Once you have upgraded the disks behind the first controller, you need to repeat the process on the disks behind the second controller. Re-insert the second controller and boot the host it is attached to. Shutdown the first host and remove its connected A3X00 controller. On the second host specify its disks for upgrade and when completed re-insert the first controller and boot the host. README -- Last modified date: Tuesday, February 13, 2001