Patch Name: PHSS_27098 Patch Description: s700_800 11.11 RAID 4Si Patch Creation Date: 02/06/26 Post Date: 02/07/25 Hardware Platforms - OS Releases: s700: 11.11 s800: 11.11 Products: I2ORAID B.11.11.00 B.11.11.01 Filesets: I2ORAID.I2ORAID-RUN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP I2ORAID.I2ORAID-RUN,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP I2ORAID.I2ORAID-MAN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP I2ORAID.I2ORAID-MAN,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP Automatic Reboot?: No Status: General Release Critical: No (superseded patches were critical) PHSS_26530: PANIC HANG Category Tags: defect_repair enhancement general_release critical firmware panic halts_system Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27098 Symptoms: PHSS_27098: 1. ( SR:8606257079 CR:JAGae21389 ) Seagate disks go offline when irdiag -v is run just after power on or bus reset. 2. ( SR:8606262415 CR:JAGae26750 ) Whenever the RAID configuration changes, irmd does not save the configuration to a file. 3. ( SR:8606262417 CR:JAGae26752 ) irdiag -v output does not include disk drive failure history 4. ( SR:8606262418 CR:JAGae26753 ) irdiag -v output does not include vendor spec from disk drive inquiry 5. ( SR:8606171695 CR:JAGad40959 ) IRM says that a drive is Ready, but irmd and irdiag say it is failed if: The firmware says it is failed SCSI inquiry succeeds The disk is not in a span This can happen if a drive fails and a hotspare takes over (therefore removing the failed disk from the span), and the disk is replaced (which means SCSI inquiry will succeed). In these cases, irmd and irdiag say the new disk is failed, when in fact it is Ready. PHSS_26530: 1. ( SR:8606217232 CR:JAGad86386 ) Intermittent HPMC pointing to RAID 4Si card as the suspect component. This occurs about every 21 days. 2. ( SR:8606223719 CR:JAGad92815 ) The cacheline resource exhaustion leads to I/O hang and, after reboot, HPMC. 3. ( SR:8606228845 CR:JAGad97898 ) When the SC10 Megatron JBOD is set in SAF-TE mode, the firmware will continuously loop on a Request Sense, but the JBOD will return Illegal Command. 4. ( SR:8606228847 CR:JAGad97900 ) Cache flush does not always occur on reboot. 5. ( SR:8606228849 CR:JAGad97902 ) Reconstructions on multiple channels can cause system crash. 6. ( SR:8606228850 CR:JAGad97903 ) A drive that does not respond to Test Unit Ready will hang the firmware. 7. ( SR:8606228851 CR:JAGad97904 ) While running heavy I/O, if rebuild is started (with rebuild rate > 20), then the I/O would not continue. 8. ( SR:8606228852 CR:JAGad97905 ) Battery charge is sometimes not complete. 9. ( SR:8606228853 CR:JAGad97906 ) The sense key of the request sense is sometimes lost when the data is received by the host. This means that irdiag doesn't show the right information. 10. ( SR:8606228854 CR:JAGad97907 ) A defect in the RAID 4Si firmware caused the quetag to become 1. Defect Description: PHSS_27098: 1. ( SR:8606257079 CR:JAGae21389 ) When irdiag is run after power on or bus reset, it sends commands to the disk drives in a way that violates the SCSI protocol. The disk drives go offline until another bus reset or power cycle occurs. Resolution: The problem is resolved by sending a untagged Request Sense to the target in Contingent Allegiance. 2. ( SR:8606262415 CR:JAGae26750 ) Whenever the RAID configuration changes, irmd does not save the configuration to a file. This makes it difficult to track the historical configurations since the previous configuration info is no longer available, whenever the configuration changes. Resolution: Whenever irmd detects a change in configuration on a RAID adapter, it executes a shell script - save_4si_config. This script runs irdiag -v on that adapter and saves the output in a file in /var/opt/raid4si. This directory can contain a maximum of 99 configuration files and are named as irdiag_out_XY.txt, where XY is a number from 00 - 99. A soft link called latest points to the latest file in the directory. After 99 files, the oldest file in the directory is overwritten. 3. ( SR:8606262417 CR:JAGae26752 ) irdiag -v should display the disk drive failure index and history. This is useful in determining the cause of disk failure. Resolution: For each physical drive connected to the HBA, the drive fail history is queried by `irdiag -v'. The drive failure history is displayed only if the drive is in FAILED state. 4. ( SR:8606262418 CR:JAGae26753 ) irdiag -v should display the vendor specific field returned by disk drive inquiry. This field usually contains the disk drive's serial number. Resolution: Modification is made to irdiag -v tool to display vendor spec information. 5. ( SR:8606171695 CR:JAGad40959 ) Firmware does not detect that hotspare has taken over for the failed drive and the status remains FAILED. Resolution: Modification made to irdiag and irmd to check whether a FAILED physical drive is still part of a logical drive. If not and SCSI inquiry succeds, that physical drive is changed to READY. PHSS_26530: 1. ( SR:8606217232 CR:JAGad86386 ) The HPMC occurs when the RAID firmware disables the PCI bus for too long. Resolution: The firmware does not disable the PCI bus anymore. This was included for the support of an old chip not used anymore. 2. ( SR:8606223719 CR:JAGad92815 ) The F/W we can handle a command with a maximum data transfer size equal to 100* STripe size. This could not be ensured in the HP-UX driver resulting in the F/W only taking a part of the data and puttting it in the cache. A hang happened when more than 100 cache line worth of data was being moved. Resolution: The fix is for the RAID firmware to split I/O's that are going to cause resource exhaustion. 3. ( SR:8606228845 CR:JAGad97898 ) The firmware issues a Request Sense in a form that is not understood by the SAF-TE processor. Resolution: The format of the "Read Device Slot Status" Buffer changed according to new specs. The contents of this buffer will now be used in saf-te monitoring. 4. ( SR:8606228847 CR:JAGad97900 ) The firmware does not always do cache flush on reboot. Resolution: A fix was made to enforce cache flushing on reboot. 5. ( SR:8606228849 CR:JAGad97902 ) During Reconstruction, the f/w creates a ghost logical drive which is used as a temporary buffer. This is later deleted and the whole process internally calls write-config operation twice per reconstruction. The LCT table is also updated during write-config. This is corrupting the LCT and eventually system crash. Resolution: A fix was made to ensure that reconstructions on multiple channels will succeed. 6. ( SR:8606228850 CR:JAGad97903 ) The firmware waits drives that don't give a SELECTION_TIMEOUT forever. Resolution: A fix is made to ensure that the firmware will not hang, even if the drive does not respond to Test Unit Ready. 7. ( SR:8606228851 CR:JAGad97904 ) When starting rebuild at rate greater than 20, not enough processing time is given to concurrent I/O causing the I/O to hang. Resolution: The rebuild process is delayed depending upon the rebuild rate. If rebuild rate is < 20%, then the next row rebuild is 200/rebuild_rate which is in milliseconds. If rebuild rate is 0, then it is set to 800 milliseconds. This will give time for other I/O requests to continue. 8. ( SR:8606228852 CR:JAGad97905 ) The battery pack capacity increased from 650mAh to 900mAh. Resolution: The battery fast charge is now done in 4 cycles instead of 2. 9. ( SR:8606228853 CR:JAGad97906 ) Whenever a drive is inserted, a Power-On-Reset is generated, which in turn will generate the corresponding Sense key data. The FW was using this Sense key data as a trigger to perform a Mode Sense/Mode Select. Now, as it was not desirable for the FW to repeat this operation, this data was being initialised. This resulted in the "lost" data, as observed from the host. Resolution: The FW is still keys on the Sense key data, but will now not clear it. 10. ( SR:8606228854 CR:JAGad97907 ) After removal and insertion of a drive, the maximum quetag of the drive becomes 1. This would happen whenever a new drive is inserted, as the FW does not know how many Q-tags the drive can handle. Resolution: the FW will now issues a DCDB (Inquiry) command to the drive itself, after insertion of the drive, instead of previously waiting for one of the online utilities to do it. Enhancement: Yes PHSS_27098: Utilities were added few options. SR: 8606217232 8606223719 8606228845 8606228847 8606228849 8606228850 8606228851 8606228852 8606228853 8606228854 8606257079 8606262415 8606262417 8606262418 8606171695 Patch Files: I2ORAID.I2ORAID-RUN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: I2ORAID.I2ORAID-RUN,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP: /opt/raid4si/firmware/a5856a_u_01_06.img /opt/raid4si/firmware/a5856a_u_01_06.txt /sbin/irdiag /sbin/irmd /sbin/save_4si_config I2ORAID.I2ORAID-MAN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: I2ORAID.I2ORAID-MAN,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP: /usr/share/man/man1m.Z/irdiag.1m /usr/share/man/man1m.Z/irmd.1m what(1) Output: I2ORAID.I2ORAID-RUN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: /opt/raid4si/firmware/a5856a_u_01_06.img: None I2ORAID.I2ORAID-RUN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: /opt/raid4si/firmware/a5856a_u_01_06.txt: None I2ORAID.I2ORAID-RUN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: /sbin/irdiag: irdiagB.02.01 I2ORAID.I2ORAID-RUN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: /sbin/irmd: irmd B.02.01 I2ORAID.I2ORAID-RUN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: /sbin/save_4si_config: None I2ORAID.I2ORAID-MAN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: /usr/share/man/man1m.Z/irdiag.1m: None I2ORAID.I2ORAID-MAN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: /usr/share/man/man1m.Z/irmd.1m: None cksum(1) Output: I2ORAID.I2ORAID-RUN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: 2887924503 1048576 /opt/raid4si/firmware/a5856a_u_01_06.img I2ORAID.I2ORAID-RUN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: 3562290475 5908 /opt/raid4si/firmware/a5856a_u_01_06.txt I2ORAID.I2ORAID-RUN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: 2266783371 73728 /sbin/irdiag I2ORAID.I2ORAID-RUN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: 1650138633 45056 /sbin/irmd I2ORAID.I2ORAID-RUN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: 4137106679 2140 /sbin/save_4si_config I2ORAID.I2ORAID-MAN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: 4144597407 2210 /usr/share/man/man1m.Z/irdiag.1m I2ORAID.I2ORAID-MAN,fr=B.11.11.01,fa=HP-UX_B.11.11_64,v=HP: 1229644933 6466 /usr/share/man/man1m.Z/irmd.1m Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_26530 Equivalent Patches: PHSS_27097: s700: 11.00 s800: 11.00 Patch Package Size: 1200 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_27098 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_27098.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_27098. If you do not wish to retain a copy of the original software, include the patch_save_files option in the swinstall command above: -x patch_save_files=false WARNING: If patch_save_files is false when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. For future reference, the contents of the PHSS_27098.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_27098.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_27098.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: This patch delivers an updated firmware for the A5856A Card (RAID). Note that applying this patch will NOT download the firmware onto the card. Some additionnal actions have to be taken in order to upgrade the firmware. A complete description of the procedure can be found in the file /opt/raid4si/firmware/a5856a_u_01_06.txt once the patch has been installed.