amd64/1.08/License.txt

@@ -0,0 +1,292 @@
+International License Agreement for Non-Warranted Programs
+
+Part 1 - General Terms 
+
+PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE PROGRAM.
+Adaptec WILL LICENSE THE PROGRAM TO YOU ONLY IF YOU FIRST ACCEPT THE
+TERMS OF THIS AGREEMENT. BY USING THE PROGRAM YOU AGREE TO THESE
+TERMS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT,
+PROMPTLY RETURN THE UNUSED PROGRAM TO THE PARTY (EITHER Adaptec OR
+ITS RESELLER) FROM WHOM YOU ACQUIRED IT TO RECEIVE A REFUND OF
+THE AMOUNT YOU PAID. 
+
+The Program is owned by (Adaptec) or a supplier of Adaptec 
+and is copyrighted and licensed, not sold. 
+
+The term "Program" means the original program and all whole or
+partial copies of it. A Program consists of machine-readable
+instructions, its components, data, audio-visual content (such
+as images, text, recordings, or pictures), and related licensed
+materials. 
+
+This Agreement includes Part 1 - General Terms and Part 2 
+Country unique Terms and is the complete agreement regarding the
+use of this Program, and replaces any prior oral or written
+communications between you and Adaptec. The terms of Part 2 may
+replace or modify those of Part 1. 
+
+
+1. License 
+
+Use of the Program 
+
+Adaptec grants you a nonexclusive license to use the Program. 
+
+You may 1) use the Program to the extent of authorizations you
+have acquired and 2) make and install copies to support the
+level of use authorized, providing you reproduce the copyright
+notice and any other legends of ownership on each copy, or
+partial copy, of the Program. 
+
+If you acquire this Program as a program upgrade, your
+authorization to use the Program from which you upgraded is
+terminated. 
+
+You will ensure that anyone who uses the Program does so only in
+compliance with the terms of this Agreement. 
+
+You may not 1) use, copy, modify, or distribute the Program
+except as provided in this Agreement; 2) reverse assemble,
+reverse compile, or otherwise translate the Program except as
+specifically permitted by law without the possibility of
+contractual waiver; or 3) sublicense, rent, or lease the
+Program. 
+
+Transfer of Rights and Obligations 
+
+You may transfer all your license rights and obligations under a
+Proof of Entitlement for the Program to another party by
+transferring the Proof of Entitlement and a copy of this
+Agreement and all documentation. The transfer of your license
+rights and obligations terminates your authorization to use the
+Program under the Proof of Entitlement. 
+
+
+2. Proof of Entitlement 
+
+The Proof of Entitlement for this Program is evidence of your
+authorization to use this Program and of your eligibility for
+future upgrade program prices (if announced) and potential
+special or promotional opportunities. 
+
+
+3. Charges and Taxes 
+
+Adaptec defines use for the Program for charging purposes and
+specifies it in the Proof of Entitlement. Charges are based on
+extent of use authorized. If you wish to increase the extent of
+use, notify Adaptec or its reseller and pay any applicable charges.
+Adaptec does not give refunds or credits for charges already due or
+paid. 
+
+If any authority imposes a duty, tax, levy or fee, excluding
+those based on Adaptec's net income, upon the Program supplied by
+Adaptec under this agreement, then you agree to pay that amount 
+as Adaptec specifies or
+supply exemption documentation. 
+
+
+4. No Warranty 
+
+SUBJECT TO ANY STATUTORY WARRANTIES WHICH CAN NOT BE EXCLUDED,
+Adaptec MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
+INCLUDING WITHOUT LIMITATION, THE WARRANTY OF NON-INFRINGEMENT
+AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+PARTICULAR PURPOSE, REGARDING THE PROGRAM OR TECHNICAL SUPPORT,
+IF ANY. Adaptec MAKES NO WARRANTY REGARDING THE CAPABILITY OF THE
+PROGRAM TO CORRECTLY PROCESS, PROVIDE AND/OR RECEIVE DATE DATA
+WITHIN AND BETWEEN THE 20TH AND 21ST CENTURIES. 
+
+The exclusion also applies to any of Adaptec's subcontractors,
+suppliers, or program developers (collectively called
+"Suppliers"). 
+
+Manufacturers, suppliers, or publishers of non-Adaptec Programs may
+provide their own warranties. 
+
+
+5. Limitation of Liability 
+
+NEITHER Adaptec NOR ITS SUPPLIERS WILL BE LIABLE FOR ANY DIRECT OR
+INDIRECT
+
+DAMAGES, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
+SAVINGS, OR ANY INCIDENTAL, SPECIAL, OR OTHER ECONOMIC
+CONSEQUENTIAL DAMAGES, EVEN IF Adaptec IS INFORMED OF THEIR
+POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
+LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE
+EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU. 
+
+
+6. General 
+
+Nothing in this Agreement affects any statutory rights of
+consumers that cannot be waived or limited by contract. 
+
+Adaptec may terminate your license if you fail to comply with the
+terms of this Agreement. If Adaptec does so, you must immediately
+destroy the Program and all copies you made of it. 
+
+You agree to comply with applicable export laws and regulations. 
+
+Neither you nor Adaptec will bring a legal action under this
+Agreement more than two years after the cause of action arose
+unless otherwise provided by local law without the possibility
+of contractual waiver or limitation. 
+
+Neither you nor Adaptec is responsible for failure to fulfill any
+obligations due to causes beyond its control. 
+
+Adaptec does not provide program services or technical support,
+unless Adaptec specifies otherwise. 
+
+The laws of the country in which you acquire the Program govern
+this Agreement, except 1) in Australia, the laws of the State or
+Territory in which the transaction is performed govern this
+Agreement; 2) in Albania, Armenia, Belarus, Bosnia/Herzegovina,
+Bulgaria, Croatia, Czech Republic, Georgia, Hungary, Kazakhstan,
+Kirghizia, Former Yugoslav Republic of Macedonia
+(FYROM), Moldova, Poland, Romania, Russia, Slovak Republic,
+Slovenia, Ukraine, and Federal Republic of Yugoslavia, the laws
+of Austria govern this Agreement; 3) in the United Kingdom, all
+disputes relating to this Agreement will be governed by English
+Law and will be submitted to the exclusive jurisdiction of the
+English courts; 4) in Canada, the laws in the Province of
+Ontario govern this Agreement; and 5) in the United States and
+Puerto Rico, and People's Republic of China, the laws of the 
+State of New York govern this Agreement. 
+
+
+Part 2 - Country-unique Terms 
+
+
+AUSTRALIA: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Although Adaptec specifies that there are no warranties, you may
+have certain rights under the Trade Practices Act 1974 or other
+legislation and are only limited to the extent permitted by the
+applicable legislation. 
+
+Limitation of Liability (Section 3): 
+The following paragraph is added to this Section: 
+
+Where Adaptec is in breach of a condition or warranty implied by the
+Trade Practices Act 1974, Adaptec's liability is limited to the
+repair or replacement of the goods, or the supply of equivalent
+goods. Where that condition or warranty relates to right to
+sell, quiet possession or clear title, or the goods are of a
+kind ordinarily acquired for personal, domestic or household use
+or consumption, then none of the limitations in this paragraph
+apply. 
+
+
+GERMANY:
+
+No Warranty (Section 4):
+The following paragraphs are added to this Section:
+
+The minimum warranty period for Programs is six months.
+
+In case a Program is delivered without Specifications, we will
+only warrant that the Program information correctly describes
+the Program and that the Program can be used according to the
+Program information. You have to check the usability according
+to the Program information within the "money-back guaranty"
+period.
+
+Limitation of Liability (Section 5):
+The following paragraph is added to this Section:
+
+The limitations and exclusions specified in the Agreement will
+not apply to damages caused by Adaptec with fraud or gross
+negligence, and for express warranty. 
+
+
+INDIA: 
+
+General (Section 6): 
+The following replaces the fourth paragraph of this Section: 
+
+If no suit or other legal action is brought, within two years
+after the cause of action arose, in respect of any claim that
+either party may have against the other, the rights of the
+concerned party in respect of such claim will be forfeited and
+the other party will stand released from its obligations in
+respect of such claim. 
+
+
+IRELAND: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Except as expressly provided in these terms and conditions, all
+statutory conditions, including all warranties implied, but
+without prejudice to the generality of the foregoing, all
+warranties implied by the Sale of Goods Act 1893 or the Sale of
+Goods and Supply of Services Act 1980 are hereby excluded. 
+
+
+ITALY:
+
+Limitation of Liability (Section 5):
+This Section is replaced by the following:
+
+Unless otherwise provided by mandatory law, Adaptec is not liable
+for any damages which might arise. 
+
+
+NEW ZEALAND: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Although Adaptec specifies that there are no warranties, you may
+have certain rights under the Consumer Guarantees Act 1993 or
+other legislation which cannot be excluded or limited. The
+Consumer Guarantees Act 1993 will not apply in respect of any
+goods or services which Adaptec provides, if you require the goods
+and services for the purposes of a business as defined in that
+Act. 
+
+Limitation of Liability (Section 5): 
+The following paragraph is added to this Section: 
+
+Where Programs are not acquired for the purposes of a business
+as defined in the Consumer Guarantees Act 1993, the limitations
+in this Section are subject to the limitations in that Act. 
+
+
+PEOPLE'S REPUBLIC OF CHINA:
+
+Charges (Section 3):
+The following paragraph is added to the Section:
+
+All banking charges incurred in the People's Republic of China
+will be borne by you and those incurred outside the People's
+Republic of China will be borne by Adaptec. 
+
+
+UNITED KINGDOM: 
+
+Limitation of Liability (Section 5): 
+The following paragraph is added to this Section at the end of
+the first paragraph: 
+
+The limitation of liability will not apply to any breach of
+Adaptec's obligations implied by Section 12 of the Sales of Goods
+Act 1979 or Section 2 of the Supply of Goods and Services Act
+1982. 
+
+
+UNITED STATES AND CANADA:
+
+No Country-unique Terms apply.
+
+
+By continuing with the installation of the Program, you are 
+accepting the terms and conditions above.
+

amd64/1.08/README.TXT

@@ -0,0 +1,693 @@
+README.TXT
+
+Adaptec maxView Storage Manager
+Adaptec Command Line Interface Utility (ARCCONF)
+
+as of May 19, 2015
+--------------------------------------------------------------------
+Please review this file for important information about issues
+and errata that were discovered after completion of the standard
+product documentation. In the case of conflict between various
+parts of the documentation set, this file contains the most
+current information.
+
+The following information is available in this file:
+
+   1. New Features in this Release
+   2. Software Versions and Documentation
+      2.1   Utility Software
+      2.2   Documentation
+   3. Installation and Setup
+      3.1   Installation Instructions
+      3.2   Supported Operating Systems
+      3.3   General Setup Notes
+      3.4   Remote Access
+      3.5   Windows 8 Setup
+      3.6   SLES Setup 
+      3.7   Ubuntu Setup
+      3.8   Bootable USB Image Security Warnings 
+      3.9   RAW Device Setup
+      3.10  maxView Plugin for VMware vSphere Web Client
+      3.11  Firmware Downgrade on Series 8 Board Revision "B1"
+      3.12  Uninstallation Issues
+   4. Known Limitations
+      4.1   Login Issues on Windows Domain Server
+      4.2   Hot Spare Issues
+      4.3   Dual-Controller Systems
+      4.4   Email Notifications
+      4.5   SGPIO Enclosures
+      4.6   Non-RAID Mode Controllers
+      4.7   RAID-Level Migrations
+      4.8   maxCache Device Migration
+      4.9   ARCCONF maxCache Device Size Issue 
+      4.10  Browser Issues
+      4.11  Remote System Issues
+      4.12  Power Management Issues
+      4.13  RAID 50/RAID 60, Max Drives
+      4.14  RAID 10 Segment Order
+      4.15  RAID 10 Rebuild Order       
+      4.16  Verify with Fix      
+      4.17  Locate Logical Drive Blink LED
+      4.18  ATA Secure Erase
+      4.19  ARCCONF Backward Compatibility
+      4.20  Adaptec Series 6 Controller Issues
+      4.21  Simple Volume Support
+      4.22  Auto-Volume Support 
+      4.23  Hot-Removing Disk Drives on Xenserver Guest OS
+      4.24  Updating Hard Disk Firmware on VMware Guest OS
+      4.25  Creating a Support Archive on a Guest OS
+      4.26  Enclosure Status Reporting
+      4.27  PHY Status on Enclosure Backplanes  
+      4.28  Special Characters in Logical Device Names   
+      4.29  Speaker Status on SuperMicro SAS2X28 Enclosures
+      4.30  Changing Read and Write Cache Settings for a Logical Drive
+      4.31  Online Help Issues 
+      
+--------------------------------------------------------------------
+1. New Features in this Release
+    
+   o Support for new operating systems
+   o Support for HDD/SSD temperature monitoring
+   o Improved SMART error logging for SAS and SATA devices  
+   o Basecode logs and Flash Backup Module hard error logs included in support archive
+   o Enhanced maxView SMTP mail client to comply with highly secured SMTP servers (Gmail, Yahoo, etc)
+   o Open Pegasus 2.13 (maxView CIM Server) upgrade 
+   o Re-design of maxView schedule dialog with advanced Primefaces calendar component
+   o Multi-level authentication and access privileges in maxView (Administrator/Standard user)
+   o Installer change: install GUI, Agent and CIM Server as separate components (saves 500MB RAM space, typical)
+   o Global Init/Uninit Physical Devices wizard
+   o Global Delete Logical Devices wizard
+   o Misc UI enhancements:
+      - Logical drive property tab shows initialization method
+      - Physical device temperature added to physical drive information
+      - Logical device long running task navigation from tree node to Tab to Task dialog
+   o ARCCONF changes:
+      - New commands: backupunit, driverupdate, setcustommode, setconnectormode
+      - Enhanced commands: identify command supports blink LED start/stop
+   o Bugfixes
+
+--------------------------------------------------------------------
+2. Software Versions and Documentation
+
+   2.1 Utility Software
+       
+       o Adaptec maxView Storage Manager Version 1.08    
+       o Adaptec ARCCONF Command Line Interface Utility Version 1.08
+
+   2.2 Documentation 
+  
+       PDF Format (English/Japanese):
+        
+       o maxView Storage Manager User's Guide               
+       o Adaptec RAID Controller Command Line Utility User's Guide
+
+       HTML and Text Format:
+
+       o maxView Storage Manager Online Help
+       o maxView Storage Manager README.TXT file
+        
+--------------------------------------------------------------------
+3. Installation and Setup
+
+   3.1 Installation Instructions
+
+       The Adaptec SAS RAID Controllers Installation and User's Guide
+       contains complete installation information for the controllers
+       and drivers. The Adaptec RAID Controllers Command Line Utility
+       User's Guide contains complete installation information for
+       ARCCONF. The maxView Storage Manager User's Guide contains  
+       complete installation information for the maxView Storage  
+       Manager software.        
+
+   3.2 Supported Operating Systems                           
+
+       Microsoft Windows: 
+  
+       o Windows Server 2012 R2, 64-bit
+       o Windows Server 2008, 32-bit and 64-bit
+       o Windows Server 2008 R2, 64-bit
+       o Windows SBS 2011, 64-bit 
+       o Windows 7, 32-bit and 64-bit
+       o Windows 8, Windows 8.1, 32-bit and 64-bit
+          
+       Linux:
+
+       o Red Hat Enterprise Linux 7.1, 64-bit
+       o Red Hat Enterprise Linux 6.6, 5.11, 32-bit and 64-bit
+       o SuSE Linux Enterprise Server 12, 64 bit 
+       o SuSE Linux Enterprise Server 11, 10*, 32-bit and 64-bit     
+       o Debian Linux 7.8, 32-bit and 64-bit  
+       o Ubuntu Linux 14.10, 14.04.1, 12.04.3, 32-bit and 64-bit
+       o Fedora Linux 21, 32-bit and 64-bit
+       o CentOS 7.1, 64 bit 
+       o CentOS 6.6, 5.11, 32-bit and 64-bit
+       
+       *See Section 3.6 for SLES 10 setup issues
+
+       Virtual OS Environments:
+        
+       o VMware ESXi 6.0, VMware ESXi 5.5
+       o Citrix XenServer 6.5 (32-bit GOS only)
+
+       Solaris:
+          
+       o Solaris 10 U11
+       o Solaris 11.2
+                           
+   3.3 General Setup Notes
+
+       o maxView Storage Manager supports Adaptec Series 8, Adaptec 
+         Series 7, and Adaptec Series 6 controllers. It is not backward
+         compatible with older Adaptec controller models. 
+
+       o maxView Storage Manager is not supported on FreeBSD. Use 
+         ARCCONF to create and manage arrays.
+   
+       o maxView Storage Manager and legacy Adaptec Storage Manager (ASM) 
+         cannot coexist on the same system.
+
+   3.4 Remote Access
+   
+       maxView Storage Manager requires the following range of ports
+       to be open for remote access: 
+       
+       o 34570-34580 (TCP)
+       o 34570 (UDP)
+       o 34577-34580 (UDP)
+       
+       See also Section 4.12 for OS-specific issues and workarounds.
+
+   3.5 Windows 8 Setup
+      
+       To log in and use maxView Storage Manager on a Windows 8 system,
+       you must create a local user account; you cannot use your
+       MS Live account. To create a local user account:
+          
+       1. Log into your MS Live account.       
+       2. Select Settings->Change PC Settings->Users->Switch to Local user.     
+       3. Provide account details.     
+       4. Start maxView Storage Manager and log in with your local user
+          account credentials.
+ 
+   3.6 SLES Setup       
+       
+       o Due to a JRE conflict, maxView Storage Manager is not 
+         supported on SLES 10 SP2/SP3 (x32, x64), and SLES 10 SP4 (x32).
+         
+         WORKAROUND: Install SLES 10 SP4 64-bit then replace the 64-bit 
+         JRE with a 32-bit JRE. Alternatively, use ARCCONF for storage
+         management on SLES 10 systems.
+       
+       o To avoid a problem with launching maxView Storage Manager on
+         SLES 11 x64 systems with DHCP enabled, ensure that the 
+         /etc/hosts file maps the server IP address to a valid host  
+         name; it is not sufficient to map the IP address to 'localhost'.
+
+   3.7 Ubuntu Setup 
+   
+       o To avoid a maxView Login failure on Ubuntu systems, you must
+         ensure that the root user account is enabled. (It is disabled,
+         by default, on Ubuntu 14.04 and later because no password is set.) 
+         
+         For example: sudo bash; sudo passwd root 
+
+       o When upgrading maxView Storage Manager on an existing Ubuntu  
+         Linux x64 installation, you must enable the upgrade switch 
+         before installing the maxView .deb package:
+
+         export maxView_Upgrade=true 
+         dpkg -i StorMan-*.deb 
+
+         To uninstall maxView after the upgrade:
+
+         export maxView_Upgrade=false 
+         dpkg -r storman        
+
+   3.8 Bootable USB Image Security Warnings
+   
+       When running maxView Storage Manager from the bootable USB 
+       image, you may be prompted with one or more with security 
+       warnings before maxView launches. In each case, acknowledge 
+       the warning and continue.
+       
+   3.9 RAW Device Setup
+    
+       On Adaptec Series 7 and Adaptec Series 8 controllers, a RAW 
+       Pass Through device is analogous to a JBOD, supported by Adaptec  
+       Series 6 controllers and older. Any drive without Adaptec RAID 
+       metadata is exposed to the OS as a RAW Pass Through device. To 
+       remove the Adaptec metadata and convert the drive to a RAW device, 
+       use the Uninitialize command in maxView Storage Manager; any 
+       existing data on the drive is destroyed. (You can also run 
+       uninit from the BIOS or ARCCONF.) For more information about 
+       working with RAW devices, see 'controller modes' in the CLI 
+       User's Guide, and BIOS 'general settings' in the RAID Controller
+       Installation and User's Guide.
+       
+  3.10 maxView Plugin for VMware vSphere Web Client
+
+       The maxView Plugin for VMware vSphere Web Client is supported
+       on VMware 5.5 only.
+
+  3.11 Firmware Downgrade on Series 8 Board Revision "B1"
+
+       Firmware downgrade from maxView Storage Manager, ARCCONF or the
+       BIOS is not supported on Adaptec Series 8 RAID controllers with 
+       Board Revision "B1" (the newest board revision). Older firmware  
+       versions do not support Board Revision "B1".
+
+  3.12 Uninstallation Issues
+       
+       o When uninstalling maxView Storage Manager on Fedora Linux, 
+         the OS displays a series of warning messages about missing
+         files. These messages can be ignored; the uninstallation 
+         completes successfully.
+
+         WORKAROUND: To avoid the warnings, uninstall maxView with
+         './StorMan-1.06-21032.i386.bin --remove' rather than
+         'rpm -e StorMan'.
+
+       o When using the 'Modify' option to uninstall maxView Storage
+         Manager on Windows, the 'Adaptec' folder is not removed from
+         the file system.         
+                               
+--------------------------------------------------------------------
+4. Known Limitations   
+
+   4.1 Login Issues on Windows Domain Server
+   
+       If the maxView login account doesn't have local administrative 
+       rights, login will fail with an error message: 'Invalid Username
+       or Password'. On domain servers running later versions of Microsoft
+       Windows Server, where no local administrator exists or can be 
+       created, maxView login is not possible. Use ARCCONF to create 
+       and manage arrays.
+       
+   4.2 Hot Spare Issues
+         
+       o After using a global hot spare to rebuild a redundant logical
+         drive, maxView Storage Manager displays an erroneous event 
+         message: "Deleted dedicated hot spare drive for logical device". 
+         In fact, the message should read "Logical device X is no longer
+         protected by hot spare drive Y".
+         	 
+       o maxView Storage Manager allows you to un-assign a global hot
+	 spare drive while copyback is in progess. This procedure is 
+	 not recommended. 
+	 
+   4.3 Dual-Controller Systems
+       
+       In dual-controller systems, the controller order in maxView
+       Storage Manager and the BIOS differs. Example: with an
+       Adaptec 72405 and 7805 installed, the BIOS reports 
+       the 72405 as controller 1 and the 7805 as controller 2; 
+       in the GUI, the controller order is reversed.
+          
+   4.4 Email Notifications
+   
+       o On Linux systems, we recommend adding the SMTP host name
+         to the /etc/hosts file. Doing so ensures that email 
+         notifications will succeed if you specify the email 
+         server in maxView Storage Manager by host name. Otherwise, 
+         email notifications (including test messages) may fail if
+         the DNS is unable to resolve the host hame. 
+         
+         WORKAROUND: specify the email server in maxView Storage
+         Manager by IP address.
+
+       o On CentOS 5.9 x64, email notifications may not be sent for 
+         logical drive creations, degraded logical drives, or logical 
+         drives that are rebuilding or fully rebuilt.
+                   
+   4.5 SGPIO Enclosures
+       
+       In this release, maxView Storage Manager does not show connector
+       information for SGPIO enclosures.
+         
+   4.6 Non-RAID Mode Controllers
+       
+       maxView Storage Manager can "see" RAID controllers operating
+       in HBA mode, Auto-Volume mode, and Simple Volume mode (Adaptec
+       Series 7 and Adaptec Series 8 controllers only). However, to 
+       change the controller mode, you must use ARCCONF or the BIOS.       
+       
+   4.7 RAID-Level Migrations
+    
+       o The following RAID-level migrations (RLM) are supported in
+         this release:
+       
+         RAID 0 to RAID 5
+         RAID 0 to RAID 10
+         RAID 5 to RAID 6
+         RAID 6 to RAID 5
+         RAID 10 to RAID 5
+         RAID 5 to RAID 10
+         RAID 1 to RAID 5
+         SIMPLE VOLUME to RAID 1
+         RAID 1 to SIMPLE VOLUME
+         
+       o When migrating a Simple Volume to RAID 1, maxView Storage
+         Manager reports the logical drive state as Impacted (rather
+         than Reconfiguring); this is normal.
+
+       o We do not recommend performing a RAID-level migration or 
+         Online Capacity Expansion (OCE) on a logical drive with 
+         maxCache SSD caching enabled.
+         
+         NOTE: maxView Storage Manager grays out the options for logical
+         drives with maxCache enabled. ARCCONF terminates the task.
+       
+       o Always allow a RAID-level migration to complete before creating
+         a support archive file. Otherwise, the support archive will 
+         include incorrect partition information. Once the migration is
+         complete, the partition information will be reported correctly.
+
+   4.8 maxCache Device Migration
+   
+       Only one maxCache Device is supported per controller. Moving
+       the maxCache Device (all underlying SSDs) from one
+       controller to another (assuming both controllers support 
+       maxCache) is supported only if (1) the new controller does not 
+       have a maxCache Device or any other maxCache Device with a 
+       conflicting device number and (2) only after a clean shutdown
+       on the old controller.
+
+   4.9 ARCCONF maxCache Device Size Issue 
+
+       ARCCONF supports >2TB maxCache Devices if you create the
+       device with the 'max' parameter. However, the functional
+       limit for the maxCache Device is 2TB, which is also the 
+       limit in maxView Storage Manager.                 
+       
+  4.10 Browser Issues
+          
+       o To run maxView Storage Manager on the supported browsers,
+         Javascript must be enabled. 
+
+       o Due to a certificate bug in Firefox 31.x, maxView login
+         may fail on RHEL systems with a "Secure Connection" error. 
+         (Firefox 31.1 is the default browser on RHEL 6.6; on 
+         RHEL 7.1, it is 31.4.)
+         
+         WORKAROUND: Upgrade to Firefox 36.
+
+       o With the default Security setting in Microsoft Internet 
+         Explorer 10 and 11, you may be unable to login to maxView   
+         Storage Manager or experience certain GUI display issues 
+         in the maxView online Help system.
+       
+         WORKAROUND: Change the default Security setting from High 
+         (or Medium-High) to Medium. Alternative: add the GUI IP 
+         address to the trusted sites list.
+
+       o With Google Chrome, the scrollbar resets itself to the top
+         after selecting a drive in the Logical Drive wizard. To 
+         select another drive, you must scroll back down to the 
+         drive location.
+
+       o With Microsoft Internet Explorer 10, the controller 
+         firmware update wizard does not show the f/w update   
+         file name when the upload completes. To refresh the
+         display, click Next then Back.
+
+       o We do not recommend using multiple browsers simultaneously
+         on the same maxView instance. Doing so may cause display
+         issues or freezes; to restore maxView, refresh the
+         display by pressing F5.
+           
+  4.11 Remote System Access on Linux and Windows
+       
+       To avoid remote system access failures from Linux and Windows 
+       clients running maxView Storage Manager, check and update one 
+       or all of the following system and network settings:
+       
+       Windows:
+       
+       o Ensure that the DNS server information is properly configured
+       
+       RHEL/Linux:
+       
+       o Set server.properties file permissions to at least read-only at all levels
+
+         1. Stop all maxView services. 
+         2. Set the Permissions of server.properties file to read and write or read-only 
+            at all levels (Owner, Group and Others). Apply and close. 
+         3. Restart all services in the given order - cim, agent, tomcat 
+         4. Now try to remote login to this system from any other system 
+       
+       o Check/update these network settings:
+       
+         1. Disable SELinux 
+         2. Disable firewall.
+         3. Disable the ipv6 in the system, if ipconfig shows both ipv4 and ipv6 address. 
+         4. Remove the virtual bridge virbr0, if present
+         5. Enter local ip address in 'localip' parameter in server.properties file 
+                   
+  4.12 Power Management Issues
+   
+       o Power management is not supported on FreeBSD.
+       
+       o Capturing support logs from maxView or ARCCONF will spin up
+         drives when power management is active. This behavior is by design.
+
+       o For logical drives comprised of SSDs only, the Power Tab in
+         maxView Storage Manager is disabled. 
+
+       o The Logical Drive Creation wizard does not save the power
+         management settings after the logical drive is created. 
+         It is always disabled. 
+         
+         WORKAROUND: Enable power management for the logical drive
+         from the Set Properties window.
+  
+  4.13 RAID 50/RAID 60, Max Drives
+   
+       The maximum number of drives in a RAID 50 or RAID 60 differ
+       between maxView Storage Manager, ARCCONF, and the BIOS:
+       
+       o BIOS and ARCCONF: 128 drives max
+          
+         RAID 50 - From 2-16 legs with 3-32 drives/leg
+         RAID 60 - From 2-16 legs with 4-16 drives/leg
+    
+       o maxView Storage Manager:  
+       
+         Assumes 2 legs for RAID 50/RAID 60 (non-selectable)
+         RAID 50 2-32 drives/leg (64 total) 
+         RAID 60 2-16 drives/leg (32 total)
+
+  4.14 RAID 10 Segment Order
+  
+       maxView Storage Manager and the Ctrl-A BIOS report the wrong
+       segment order for RAID 10s, regardless of the order in which
+       the drives are selected. 
+           
+       Example 1:  Create RAID 10 with 2 SDDs and 2 HDDs in maxView Storage Manager:
+           
+       (1a) ARCCONF and maxView Storage Manager see the following RAID segment order:
+                Device 2 (S1)
+                Device 1 (H2)
+                Device 3 (S2)
+                Device 0 (H1)
+   
+       (1b) the BIOS/CTRL-A sees the following RAID segment order:
+                Device 2 (S1)
+                Device 1 (H2)
+                Device 0 (H1)
+                Device 3 (S2)
+   
+       (1c) the correct and expected RAID segment order is:
+                Device 2 (S1)
+                Device 0 (H1)
+                Device 3 (S2)
+                Device 1 (H2)
+                
+       Example 2:  Create RAID 10 with 2 SDDs and 2 HDDs with ARCCONF:
+  
+       (2a) the BIOS/CTRL-A sees the following RAID segment order:
+                      Device 0 (H1)
+                      Device 2 (S1)
+                      Device 1 (H2)
+                      Device 3 (S2)
+  
+       (2b) ARCCONF and maxView Storage Manager see the correct RAID segment order:
+                      Device 2 (S1)
+                      Device 0 (H1)
+                      Device 3 (S2)
+                      Device 1 (H2)
+  
+  4.15 RAID 10 Rebuild Order 
+   
+       With a degraded RAID 10 logical drive, the drive is rebuilt
+       one leg at a time, not in parallel.  
+         
+  4.16 Verify with Fix
+  
+       In maxView Storage Manager and ARCCONF, the Verify with Fix
+       operation is NOT available when: 
+       
+       1. The logical drive has a non-redundant RAID level
+       2. Other tasks are in progress on the logical drive
+       3. The logical drive is in a non-optimal or impacted state
+       
+  4.17 Locate Logical Drive Blink LED
+  
+       In maxView Storage Manager, Locate Logical Drive continues to
+       blink the LED for a pulled physical drive in the array after 
+       the locate action is stopped. (For unpulled drives, the blinking
+       stops.) This issue is not seen with ARCCONF.
+                    
+  4.18 ATA Secure Erase
+  
+       In ARCCONF, the ATA Secure Erase operation cannot be aborted.
+       Once started, it continues to completion. 
+       
+       NOTE: ATA Secure Erase is also available in the Ctrl-A BIOS. 
+       and maxView Storage Manager.
+
+  4.19 ARCCONF Backward Compatibility
+
+       ARCCONF is backward compatible with older Adaptec controller
+       models. As a result, the ARCCONF user's guide and online help
+       show command options that are not supported by newer Adaptec
+       controllers, like the Adaptec Series 7 and Adaptec Series 8. 
+       
+       Example: 
+              
+       o With ARCCONF SETMAXCACHE, Adaptec Series 7 and Series 8 
+         controllers do not support ADDTOPOOL or REMOVEFROMPOOL                                     
+  
+  4.20 Adaptec Series 6 Controller Issues
+        
+       The following issues are seen only with Adaptec Series 6 RAID
+       controllers:
+                                       
+       o In maxView Storage Manager, the Preserve Cache option on the  
+         Set Properties window is not supported on Series 6 RAID
+         controllers. Attempting to set this option for the Series 6 
+         controller fails.
+
+       o Renaming a RAID volume disables the write-cache (if enabled).
+         You cannot re-enable the write-cache in maxView Storage Manager.
+          
+         WORKAROUND: Use ARCCONF to enable the write-cache.
+        
+       o In a VMware Guest OS under VMware 5.x, maxView Storage Manager
+         and ARCCONF do not detect existing logical drive partitions. 
+         As a result, attempting to delete, clear, or erase the logical
+         drive may fail.
+
+       o On Series 6 controllers, maxView Storage Manager deletes   
+         partitioned JBODs without issuing a warning message. 
+         
+       o Series 6 controllers do not support the ARCCONF GETPERFORM command.
+
+  4.21 Simple Volume Support
+       
+       o In this release, you can create a maximum of 128 Simple 
+         Volumes in maxView Storage Manager, ARCCONF, or the BIOS.
+
+       o When a Simple Volume fails, the status remains unchanged  
+         after drive replacement. 
+
+         WORKAROUND: Manually delete the Simple Volume to remove it.
+         
+  4.22 Auto-Volume Support 
+
+       o Changing a controller into Auto-Volume mode (ARCCONF/BIOS) is not
+         supported if the configuration includes any logical device type  
+         other than Simple Volume, including a maxCache Device. The mode
+         switch from RAID mode to Auto-Volume mode is blocked if any other
+         type of logical volume exists (including maxCache). After
+         switching to Auto-Volume mode, you can create and delete Simple
+         Volumes only in maxView Storage Manager and ARCCONF.
+
+       o In Auto-Volume mode, only the first 128 RAW drives are converted 
+         to Simple Volumes; the rest of the RAW drives remain unchanged. 
+         If you uninitialize a Ready drive while the controller is in
+         Auto-Volume mode, the firmware converts the drive automatically
+         until the Simple Volume count reaches the maximum.
+            
+  4.23 Hot-Removing Disk Drives on Xenserver Guest OS
+
+       XenServer does not support "hot-removal" of disk drives from a 
+       partitioned logical drive. As a result, if you hot remove a disk  
+       from a logical drive, the Guest OS becomes inaccessible because   
+       the drive partition remains visible to the OS instead of being 
+       cleared.
+
+       WORKAROUND: Reboot the XenServer host, detach the failed 
+       partition, then restart the VM.
+
+  4.24 Updating Hard Disk Firmware on VMware Guest OS 
+
+       Updating the firmware for a SAS hard disk drive with ARCCONF/maxView 
+       can crash (PSOD) the VMware Guest OS. This issue is seen with SAS 
+       hard drives only; with SATA drives, the firmware update completes 
+       successfully.
+
+  4.25 Creating a Support Archive on a Guest OS
+  
+       To create a support archive on a VMware or Xenserver Guest OS,
+       use maxView Storage Manager only. Creating a support archive 
+       with ARCCONF is not supported in this release.
+  
+  4.26 Enclosure Status Reporting
+  
+       Enclosure status, in maxView Storage Manager, is event-driven.
+       As a result, enclosures can have a "Degraded" status even if
+       related resources (fan, temperature, power) are performing
+       normally (Optimal status). For instance, the Enclosure status
+       changes to "Degraded" if the system reports an "Enclosure device
+       not responding ..." event, even if other sensor values are normal. 
+
+  4.27 PHY Status on Enclosure Backplanes  
+
+       In the Controller Properties window, maxView Storage Manager shows
+       the Connector Info as "unknown" for all PHYs on an enclosure-based 
+       backplane (for instance, a backplane attached to connector 1).
+
+  4.28 Special Characters in Logical Device Names
+  
+       Special characters are permitted in logical device names
+       in maxView Storage Manager, the BIOS, and ARCCONF. However,
+       with Linux ARCCONF (create, setname), special characters  
+       must be "escaped" to ensure proper interpretation. For 
+       example:
+              
+       ARCCONF SETNAME 1 LOGICALDRIVE 1 arc_ldrive%\$12\& 
+
+  4.29 Speaker Status on SuperMicro SAS2X28 Enclosures
+
+       SuperMicro SAS2X28 enclosures do not propagate the speaker
+       status to maxView Storage Manager. As a result, maxView 
+       always displays the speaker status as Off.
+
+  4.30 Changing Read and Write Cache Settings for a Logical Drive
+
+       maxView Storage Manager does not allow you to change the 
+       read-cache and write-cache settings for a logical drive in  
+       one step. You must click OK after each change.
+
+  4.31 Online Help Issues 
+
+       When opening the maxView Storage Manager help from a remote
+       Linux system (eg, over a VPN), the help window may fail to 
+       open with a 'can't establish connection to server' message.
+         
+       WORKAROUND: replace 127.0.0.1:8443 in the URL with <system_ip_address>:8443
+                                           
+--------------------------------------------------------------------
+(c) 2015 PMC-Sierra, Inc. All Rights Reserved. 
+
+This software is protected under international copyright laws and 
+treaties. It may only be used in accordance with the terms 
+of its accompanying license agreement.
+
+The information in this document is proprietary and confidential to
+PMC-Sierra, Inc., and for its customers' internal use. In any event,
+no part of this document may be reproduced or redistributed in any
+form without the express written consent of PMC-Sierra, Inc.,  
+1380 Bordeaux Drive, Sunnyvale, CA 94089.
+
+P/N DOC-01768-05-A Rev A

amd64/2.01/License.txt

@@ -0,0 +1,292 @@
+International License Agreement for Non-Warranted Programs
+
+Part 1 - General Terms 
+
+PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE PROGRAM.
+Adaptec WILL LICENSE THE PROGRAM TO YOU ONLY IF YOU FIRST ACCEPT THE
+TERMS OF THIS AGREEMENT. BY USING THE PROGRAM YOU AGREE TO THESE
+TERMS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT,
+PROMPTLY RETURN THE UNUSED PROGRAM TO THE PARTY (EITHER Adaptec OR
+ITS RESELLER) FROM WHOM YOU ACQUIRED IT TO RECEIVE A REFUND OF
+THE AMOUNT YOU PAID. 
+
+The Program is owned by (Adaptec) or a supplier of Adaptec 
+and is copyrighted and licensed, not sold. 
+
+The term "Program" means the original program and all whole or
+partial copies of it. A Program consists of machine-readable
+instructions, its components, data, audio-visual content (such
+as images, text, recordings, or pictures), and related licensed
+materials. 
+
+This Agreement includes Part 1 - General Terms and Part 2 
+Country unique Terms and is the complete agreement regarding the
+use of this Program, and replaces any prior oral or written
+communications between you and Adaptec. The terms of Part 2 may
+replace or modify those of Part 1. 
+
+
+1. License 
+
+Use of the Program 
+
+Adaptec grants you a nonexclusive license to use the Program. 
+
+You may 1) use the Program to the extent of authorizations you
+have acquired and 2) make and install copies to support the
+level of use authorized, providing you reproduce the copyright
+notice and any other legends of ownership on each copy, or
+partial copy, of the Program. 
+
+If you acquire this Program as a program upgrade, your
+authorization to use the Program from which you upgraded is
+terminated. 
+
+You will ensure that anyone who uses the Program does so only in
+compliance with the terms of this Agreement. 
+
+You may not 1) use, copy, modify, or distribute the Program
+except as provided in this Agreement; 2) reverse assemble,
+reverse compile, or otherwise translate the Program except as
+specifically permitted by law without the possibility of
+contractual waiver; or 3) sublicense, rent, or lease the
+Program. 
+
+Transfer of Rights and Obligations 
+
+You may transfer all your license rights and obligations under a
+Proof of Entitlement for the Program to another party by
+transferring the Proof of Entitlement and a copy of this
+Agreement and all documentation. The transfer of your license
+rights and obligations terminates your authorization to use the
+Program under the Proof of Entitlement. 
+
+
+2. Proof of Entitlement 
+
+The Proof of Entitlement for this Program is evidence of your
+authorization to use this Program and of your eligibility for
+future upgrade program prices (if announced) and potential
+special or promotional opportunities. 
+
+
+3. Charges and Taxes 
+
+Adaptec defines use for the Program for charging purposes and
+specifies it in the Proof of Entitlement. Charges are based on
+extent of use authorized. If you wish to increase the extent of
+use, notify Adaptec or its reseller and pay any applicable charges.
+Adaptec does not give refunds or credits for charges already due or
+paid. 
+
+If any authority imposes a duty, tax, levy or fee, excluding
+those based on Adaptec's net income, upon the Program supplied by
+Adaptec under this agreement, then you agree to pay that amount 
+as Adaptec specifies or
+supply exemption documentation. 
+
+
+4. No Warranty 
+
+SUBJECT TO ANY STATUTORY WARRANTIES WHICH CAN NOT BE EXCLUDED,
+Adaptec MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
+INCLUDING WITHOUT LIMITATION, THE WARRANTY OF NON-INFRINGEMENT
+AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+PARTICULAR PURPOSE, REGARDING THE PROGRAM OR TECHNICAL SUPPORT,
+IF ANY. Adaptec MAKES NO WARRANTY REGARDING THE CAPABILITY OF THE
+PROGRAM TO CORRECTLY PROCESS, PROVIDE AND/OR RECEIVE DATE DATA
+WITHIN AND BETWEEN THE 20TH AND 21ST CENTURIES. 
+
+The exclusion also applies to any of Adaptec's subcontractors,
+suppliers, or program developers (collectively called
+"Suppliers"). 
+
+Manufacturers, suppliers, or publishers of non-Adaptec Programs may
+provide their own warranties. 
+
+
+5. Limitation of Liability 
+
+NEITHER Adaptec NOR ITS SUPPLIERS WILL BE LIABLE FOR ANY DIRECT OR
+INDIRECT
+
+DAMAGES, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
+SAVINGS, OR ANY INCIDENTAL, SPECIAL, OR OTHER ECONOMIC
+CONSEQUENTIAL DAMAGES, EVEN IF Adaptec IS INFORMED OF THEIR
+POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
+LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE
+EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU. 
+
+
+6. General 
+
+Nothing in this Agreement affects any statutory rights of
+consumers that cannot be waived or limited by contract. 
+
+Adaptec may terminate your license if you fail to comply with the
+terms of this Agreement. If Adaptec does so, you must immediately
+destroy the Program and all copies you made of it. 
+
+You agree to comply with applicable export laws and regulations. 
+
+Neither you nor Adaptec will bring a legal action under this
+Agreement more than two years after the cause of action arose
+unless otherwise provided by local law without the possibility
+of contractual waiver or limitation. 
+
+Neither you nor Adaptec is responsible for failure to fulfill any
+obligations due to causes beyond its control. 
+
+Adaptec does not provide program services or technical support,
+unless Adaptec specifies otherwise. 
+
+The laws of the country in which you acquire the Program govern
+this Agreement, except 1) in Australia, the laws of the State or
+Territory in which the transaction is performed govern this
+Agreement; 2) in Albania, Armenia, Belarus, Bosnia/Herzegovina,
+Bulgaria, Croatia, Czech Republic, Georgia, Hungary, Kazakhstan,
+Kirghizia, Former Yugoslav Republic of Macedonia
+(FYROM), Moldova, Poland, Romania, Russia, Slovak Republic,
+Slovenia, Ukraine, and Federal Republic of Yugoslavia, the laws
+of Austria govern this Agreement; 3) in the United Kingdom, all
+disputes relating to this Agreement will be governed by English
+Law and will be submitted to the exclusive jurisdiction of the
+English courts; 4) in Canada, the laws in the Province of
+Ontario govern this Agreement; and 5) in the United States and
+Puerto Rico, and People's Republic of China, the laws of the 
+State of New York govern this Agreement. 
+
+
+Part 2 - Country-unique Terms 
+
+
+AUSTRALIA: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Although Adaptec specifies that there are no warranties, you may
+have certain rights under the Trade Practices Act 1974 or other
+legislation and are only limited to the extent permitted by the
+applicable legislation. 
+
+Limitation of Liability (Section 3): 
+The following paragraph is added to this Section: 
+
+Where Adaptec is in breach of a condition or warranty implied by the
+Trade Practices Act 1974, Adaptec's liability is limited to the
+repair or replacement of the goods, or the supply of equivalent
+goods. Where that condition or warranty relates to right to
+sell, quiet possession or clear title, or the goods are of a
+kind ordinarily acquired for personal, domestic or household use
+or consumption, then none of the limitations in this paragraph
+apply. 
+
+
+GERMANY:
+
+No Warranty (Section 4):
+The following paragraphs are added to this Section:
+
+The minimum warranty period for Programs is six months.
+
+In case a Program is delivered without Specifications, we will
+only warrant that the Program information correctly describes
+the Program and that the Program can be used according to the
+Program information. You have to check the usability according
+to the Program information within the "money-back guaranty"
+period.
+
+Limitation of Liability (Section 5):
+The following paragraph is added to this Section:
+
+The limitations and exclusions specified in the Agreement will
+not apply to damages caused by Adaptec with fraud or gross
+negligence, and for express warranty. 
+
+
+INDIA: 
+
+General (Section 6): 
+The following replaces the fourth paragraph of this Section: 
+
+If no suit or other legal action is brought, within two years
+after the cause of action arose, in respect of any claim that
+either party may have against the other, the rights of the
+concerned party in respect of such claim will be forfeited and
+the other party will stand released from its obligations in
+respect of such claim. 
+
+
+IRELAND: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Except as expressly provided in these terms and conditions, all
+statutory conditions, including all warranties implied, but
+without prejudice to the generality of the foregoing, all
+warranties implied by the Sale of Goods Act 1893 or the Sale of
+Goods and Supply of Services Act 1980 are hereby excluded. 
+
+
+ITALY:
+
+Limitation of Liability (Section 5):
+This Section is replaced by the following:
+
+Unless otherwise provided by mandatory law, Adaptec is not liable
+for any damages which might arise. 
+
+
+NEW ZEALAND: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Although Adaptec specifies that there are no warranties, you may
+have certain rights under the Consumer Guarantees Act 1993 or
+other legislation which cannot be excluded or limited. The
+Consumer Guarantees Act 1993 will not apply in respect of any
+goods or services which Adaptec provides, if you require the goods
+and services for the purposes of a business as defined in that
+Act. 
+
+Limitation of Liability (Section 5): 
+The following paragraph is added to this Section: 
+
+Where Programs are not acquired for the purposes of a business
+as defined in the Consumer Guarantees Act 1993, the limitations
+in this Section are subject to the limitations in that Act. 
+
+
+PEOPLE'S REPUBLIC OF CHINA:
+
+Charges (Section 3):
+The following paragraph is added to the Section:
+
+All banking charges incurred in the People's Republic of China
+will be borne by you and those incurred outside the People's
+Republic of China will be borne by Adaptec. 
+
+
+UNITED KINGDOM: 
+
+Limitation of Liability (Section 5): 
+The following paragraph is added to this Section at the end of
+the first paragraph: 
+
+The limitation of liability will not apply to any breach of
+Adaptec's obligations implied by Section 12 of the Sales of Goods
+Act 1979 or Section 2 of the Supply of Goods and Services Act
+1982. 
+
+
+UNITED STATES AND CANADA:
+
+No Country-unique Terms apply.
+
+
+By continuing with the installation of the Program, you are 
+accepting the terms and conditions above.
+

amd64/2.01/README.TXT

@@ -0,0 +1,819 @@
+README.TXT: Adaptec maxView Storage Manager & 
+ARCCONF Command Line Interface Utility 
+as of March 22, 2016
+--------------------------------------------------------------------
+Please check the product website for the later versions of this 
+file to ensure you are reviewing the latest information. This 
+file contains important information about issues and errata 
+that were discovered after completion of the standard 
+product documentation.
+
+In the case of conflict between various parts of the documentation 
+set, this file contains the most current information.
+
+Table of Contents
+1. New Features of this Release
+2. Software Versions and Documentation
+	2.1. Utility Software
+	2.2. Documentation
+		4.2.2.1. Series 6, 7, 8 Controller Documentation
+		4.2.2.2. HBA 1000 Series Product Documentation
+		4.2.2.3. SmartIOC Product Documentation
+3. Installation Notes
+	3.1. Installation and Setup
+	3.2. Supported Operating Systems
+		3.2.1. Series 6, 7, 8 Controllers
+		3.2.2. Smart Family Controllers
+	3.3. General Setup Notes
+	3.4. Remote Access
+	3.5. Windows 8 Setup
+	3.6. SLES Setup
+	3.7. Ubuntu Setup
+	3.8. Bootable USB Image Security Warnings
+	3.9. RAW Device Setup (Series 6, 7, 8 Only)
+	3.10. maxView Plugin for VMware vSphere Web Client
+4. Known Limitations
+	4.1. Global Limitations
+		4.1.1. Dual-Controller Systems
+		4.1.2. Email Notifications
+		4.1.3. SGPIO Enclosures
+		4.1.4. Non-RAID Mode Controllers
+		4.1.5. Browser Issues
+		4.1.6. Remote System Access on Linux and Windows
+		4.1.7. RAID 10 Segment Order
+		4.1.8. RAID 10 Rebuild Order
+		4.1.9. Locate Logical Drive Blink LED
+		4.1.10. ARCCONF Backward Compatibility
+		4.1.11. Updating Hard Disk Firmware on VMware Guest OS
+		4.1.12. Hot Swap Issues on VMware CentOS Guest OS
+		4.1.13. Enclosure Status Reporting
+		4.1.14. PHY Status on Enclosure Backplanes
+		4.1.15. Special Characters in Logical Device Names
+		4.1.16. Speaker Status on SuperMicro SAS2X28 Enclosures
+		4.1.17. Online Help Issues
+		4.1.18. Broadcasting Alerts About Status and Activity
+	4.2. Limitations Specific to Series 6, 7, 8 Controllers
+		4.2.1. RAID-Level Migrations
+		4.2.2. maxCache Device Migration
+		4.2.3. ARCCONF maxCache Device Size Issue
+		4.2.4. Power Management Issues
+		4.2.5. Verify with Fix
+		4.2.6. ATA Secure Erase
+		4.2.7. Series 6 Controller Issues
+		4.2.8. Simple Volume Support
+		4.2.9. Auto-Volume Support
+		4.2.10. Hot-Removing Disk Drives on Xenserver Guest OS
+		4.2.11. Changing Read and Write Cache Settings for Logical Drive
+	4.3. Limitations Specific to Smart Family Controllers
+		4.3.1. SES Passthrough Commands to Expanders
+		4.3.2. Firmware Upgrade Issues
+
+
+1. New Features of this Release
+
+	o Added new features:
+		- New command to identify a device by blinking its LEDs.
+		- Segment and Group Information of a RAID 10 Logical 
+		  Device can now be displayed.
+		- A new UNINIT/TASK command to clear drive configuration 
+		  for physical devices containing RAID Information Sector 
+		  (RIS) that have been masked in order to protect the 
+		  configuration data.
+		- Ability to show SGPIO virtual SEP information to show 
+		  enclosure devices for SGPIO backplanes.
+		- For cases where a logical drive fails, the array status 
+		  is now reported.
+		- Ability to display physical drive mount point information.
+		- Ability to display logical drive mount point information.
+		- Verify Write support is provided. 
+		- Linux Hyper-V is supported for the maxView Storage Manager.
+	o For Smart family products, added support for Citrix XenServer.
+	o Bugfixes
+
+
+2. Software Versions and Documentation
+
+	2.1. Utility Software
+	
+		o Microsemi Adaptec maxView Storage Manager 
+		  Version 2.01.00  (22268)
+		o Microsemi Adaptec ARCCONF Command Line Interface 
+		  Utility Version 2.01.00  (22268)
+		
+	2.2. Documentation
+	
+		2.2.1. Series 6, 7, 8 Controller Documentation
+		
+			PDF Format (English/Japanese)
+			o maxView Storage Manager User's Guide
+			o Adaptec RAID Controller Command Line Utility 
+			  User's Guide
+			
+			HTML and Text Format
+			o maxView Storage Manager Online Help
+			o maxView Storage Manager README.TXT file
+			
+		2.2.2. HBA 1000 Series Product Documentation
+		
+			PDF:
+			o Adaptec maxView Storage Manager User's Guide for 
+			  Smart-Family Controllers
+			o Adaptec HBA 1000 Series Command Line Utility 
+			  User's Guide
+			
+			HTML and Text Format:
+			o maxView Storage Manager for Smart-Family Controllers 
+			  Online Help
+			o maxView Storage Manager README.TXT file
+			
+		2.2.3. SmartIOC Product Documentation
+		
+			PDF:
+			o Adaptec maxView Storage Manager User's Guide for 
+			  Smart-Family Controllers
+			o Adaptec SmartIOC 2000 Command Line Utility User's 
+			  Guide
+			
+			HTML and Text Format:
+			o maxView Storage Manager for Smart-Family Controllers 
+			  Online Help
+			o maxView Storage Manager README.TXT file
+
+
+3. Installation Notes
+
+	3.1. Installation and Setup
+	
+		Refer to your product documentation for the correct 
+		installation and setup details:
+		o Your product Installation and User's Guide contains 
+		  complete installation information for your product's 
+		  drivers.
+		o The maxView Storage Manager User's Guide for your 
+		  product contains installation information for the 
+		  maxView Storage Manager software.
+		o The Command Line Utility User's Guide for your product 
+		  contains complete installation for ARCCONF.
+			
+	3.2. Supported Operating Systems
+	
+		3.2.1. Series 6, 7, 8 Controllers
+		
+			Microsoft Windows
+			o Microsoft Windows Server 2012 (64-bit)
+			o Microsoft Windows Server 2012 R2 (64-bit)
+			o Microsoft Windows Server 2008 R2 SP1 (64-bit)
+			o Microsoft Windows SBS 2011 (Standard and Essential)
+			o Microsoft Windows 10 (32-bit and 64-bit)
+			o Microsoft Windows 8.1 (32-bit and 64-bit)
+			o Microsoft Windows 7 (32-bit and 64-bit)
+			o Microsoft WinPE 8.1 (32-bit and 64-bit)
+			
+			Linux
+			o Red Hat Enterprise Linux/CentOS 7.2, 7.1 (64-bit)
+			o Red Hat Enterprise Linux/CentOS 6.7, 6.6 (64-bit)
+			o Red Hat Enterprise Linux/CentOS 5.11, 5.10 (64-bit)
+			o SuSE Linux Enterprise Server 12 SP1 (64-bit)
+			o SuSE Linux Enterprise Server 12 (64-bit)
+			o SuSE Linux Enterprise Server 11 SP4 and SP3 (64-bit)
+			o Debian Linux 8.1 (64-bit)
+			o Ubuntu Linux 14.04.3, 14.04 (64-bit)
+			o Ubuntu Linux 12.04.5 (64-bit)
+			o Fedora Linux 22 (64-bit)
+			
+			FreeBSD
+			o FreeBSD 10.2 (64-bit)
+			o FreeBSD 9.3 (64-bit)
+			
+			Virtual OS Environments
+			o VMware ESXi 6.0 (64-bit)
+			o VMware ESXi 5.5 U2 (64-bit)
+			o Citrix XenServer 6.5.1 (64-bit)
+			o Citrix XenServer 6.2 (32-bit)
+			
+			Solaris
+			o Solaris 11 (32-bit)
+			o Solaris 10 U9 (32-bit)
+			
+			Notes
+			1.	The ARCCONF Command Line Utility is supported on 
+				only 64-bit versions of Microsoft Windows and Linux.
+			2.	Boot USB (offline or pre-boot) for the ARCCONF Command 
+				Line Utility and maxView Storage Manager is supported 
+				in Linux.
+				
+		3.2.2. Smart Family Controllers
+		
+			Microsoft Windows
+			o Microsoft Windows  Server 2012 (64-bit)
+			o Microsoft Windows  Server 2012 R2 (64-bit)
+			o Microsoft Windows  Server 2008 R2 SP1 (64-bit)
+			o Microsoft Windows  SBS 2011 (Standard and Essential)
+			o Microsoft Windows  10 (32-bit and 64-bit)
+			o Microsoft Windows  8.1 (32-bit and 64-bit)
+			o Microsoft Windows 7 (32-bit and 64-bit)
+			
+			Linux
+			o Red Hat Enterprise Linux/CentOS 7.2, 7.1 (64-bit)
+			o Red Hat Enterprise Linux/CentOS 6.7, 6.6 (64-bit)
+			o Red Hat Enterprise Linux/CentOS 5.11, 5.10 (64-bit)
+			o SuSE Linux Enterprise Server 12 SP1 (64-bit)
+			o SuSE Linux Enterprise Server 12 (64-bit)
+			o SuSE Linux Enterprise Server 11 SP4 and SP3 (64-bit)
+			o Ubuntu Linux 14.04.3, 14.04 (64-bit)
+			o Ubuntu Linux 12.04.5 (64-bit)
+			
+			Virtual OS Environments
+			o VMware ESXi 6.0, ESXi U1 (64-bit)
+			o VMware ESXi 5.5 U2, ESXi 5.5 U3 (64-bit)
+			o Citrix XenServer 6.5.1 (64-bit)
+			o Citrix XenServer 6.2 (32-bit)
+			
+			Notes
+			1.	The ARCCONF Command Line Utility is supported on 
+				only 64-bit versions of Microsoft Windows and Linux.
+			2.	Boot USB (offline or pre-boot) for the ARCCONF Command 
+				Line Utility and maxView Storage Manager is supported 
+				in Linux.
+				
+	3.3. General Setup Notes
+	
+		o maxView Storage Manager is not backwards-compatible with 
+		  Series 5 and older Adaptec controller models.
+		o maxView Storage Manager and legacy Adaptec Storage Manager 
+		  (ASM) cannot coexist on the same system.
+		o For Series 6, 7, 8 controllers:
+			-	maxView Storage Manager is not supported on FreeBSD. 
+				Use ARCCONF to create and manage arrays.
+				
+	3.4. Remote Access
+	
+		maxView Storage Manager requires the following range of 
+		ports to be open for remote access:
+		o 34570-34580 (TCP)
+		o 34570 (UDP)
+		o 34577-34580 (UDP)
+		See also 4.1.6 for OS-specific issues and workarounds.
+		
+	3.5. Windows 8 Setup
+	
+		To log in and use maxView Storage Manager on a Windows 8 
+		system, you must create a local user account; you cannot 
+		use your MS Live account. 
+		To create a local user account:
+		1.	Log into your MS Live account.
+		2.	Select Settings->Change PC Settings->Users->Switch to 
+			Local user.
+		3.	Provide account details.
+		4.	Start maxView Storage Manager and log in with your 
+			local user account credentials.
+			
+	3.6. SLES Setup
+	
+		o To avoid a problem with launching maxView Storage 
+		  Manager on SLES 11 x64 systems with DHCP enabled, 
+		  ensure that the /etc/hosts file maps the server 
+		  IP address to a valid host name; it is not sufficient 
+		  to map the IP address to 'localhost'.
+			
+	3.7. Ubuntu Setup
+	
+		o To avoid a maxView Login failure on Ubuntu systems, 
+		  you must ensure that the root user account is enabled. 
+		  (It is disabled, by default, on Ubuntu 14.04 
+		  and later because no password is set.)
+		  For example: sudo bash; sudo passwd root
+		o When upgrading maxView Storage Manager on an existing 
+		  Ubuntu Linux x64 installation, you must enable the 
+		  upgrade switch before installing the maxView .deb 
+		  package:
+				export maxView_Upgrade=true 
+				dpkg -i StorMan-*.deb
+				To uninstall maxView after the upgrade:
+				export maxView_Upgrade=false 
+				dpkg -r storman
+			
+	3.8. Bootable USB Image Security Warnings
+	
+		When running maxView Storage Manager from the bootable 
+		USB image, you may be prompted with one or more with 
+		security warnings before maxView launches. In 
+		each case, acknowledge the warning and continue.
+		
+	3.9. RAW Device Setup (Series 6, 7, 8 Only)
+	
+		On Adaptec Series 7 and Adaptec Series 8 controllers, 
+		a RAW Pass Through device is analogous to a JBOD, supported 
+		by Adaptec Series 6 controllers and older. Any drive without 
+		Adaptec RAID metadata is exposed to the OS as a RAW Pass 
+		Through device. To remove the Adaptec metadata and convert 
+		the drive to a RAW device, use the Uninitialize command in 
+		maxView Storage Manager; any existing data on the drive is 
+		destroyed. (You can also run uninit from the BIOS or 
+		ARCCONF.) For more information about working with RAW devices, 
+		see 'controller modes' in the CLI User's Guide, and BIOS 
+		'general settings' in the RAID Controller Installation and 
+		User's Guide.
+		
+	3.10. maxView Plugin for VMware vSphere Web Client
+	
+		The maxView Plugin for VMware vSphere Web Client is 
+		supported on VMware 5.5 and 6.0.
+
+4. Known Limitations
+
+	4.1. Global Limitations
+	
+		4.1.1. Dual-Controller Systems
+		
+			In dual-controller systems, the controller order in 
+			maxView Storage Manager and the BIOS differs. Example: 
+			with an Adaptec 72405 and 7805 installed, the BIOS reports 
+			the 72405 as controller 1 and the 7805 as controller 2; 
+			in the GUI, the controller order is reversed.
+			
+		4.1.2. Email Notifications
+		
+			o On Linux systems, we recommend adding the SMTP host 
+			  name and the system IP address, to the /etc/hosts file. 
+			  Doing so ensures that email notifications will succeed 
+			  if you specify the email server in maxView Storage 
+			  Manager by host name. Otherwise, email notifications 
+			  (including test messages) may fail if the DNS is unable 
+			  to resolve the host name.
+				
+			  WORKAROUND: Specify the email server in maxView Storage 
+			  Manager by IP address.
+				
+			o On CentOS 5.9 x64, email notifications may not be sent 
+			  for logical drive creations, degraded logical drives, 
+			  or logical drives that are rebuilding or fully rebuilt.
+				
+		4.1.3. SGPIO Enclosures
+		
+			In this release, maxView Storage Manager does not show 
+			connector information for SGPIO enclosures.
+			
+		4.1.4. Non-RAID Mode Controllers
+		
+			maxView Storage Manager can "see" RAID controllers 
+			operating in HBA mode, Auto-Volume mode, and Simple Volume 
+			mode (Adaptec Series 7, Adaptec Series 8, Smart Family 
+			controllers only). However, to change the controller mode 
+			on Adaptec Series 7/8 controllers, you must use ARCCONF 
+			or the BIOS. With Adaptec Smart-Family controllers, you 
+			can also change the controller mode with maxView Storage 
+			Manager.
+			
+		4.1.5. Browser Issues
+		
+			To run maxView Storage Manager on the supported browsers. 
+			Javascript must be enabled.
+			
+			o Due to a certificate bug in Firefox 31.x, maxView 
+			  login may fail on RHEL systems with a "Secure 
+			  Connection" error. (Firefox 31.1 is the default 
+			  browser on RHEL 6.6; on RHEL 7.1, it is 31.4.)
+			  WORKAROUND: Upgrade to Firefox 36.
+				
+			o With the default Security setting in Microsoft 
+			  Internet Explorer 10 and 11, you may be unable to 
+			  login to maxView Storage Manager or experience 
+			  certain GUI display issues in the maxView online 
+			  Help system.
+			  WORKAROUND: Change the default Security setting 
+			  from High (or Medium-High) to Medium. 
+			  Alternative: add the GUI IP address to the trusted 
+			  sites list.
+				
+			o With Google Chrome, the scrollbar resets itself to 
+			  the top after selecting a drive in the Logical Drive 
+			  wizard. To select another drive, you must 
+			  scroll back down to the drive location.
+				
+			o With Microsoft Internet Explorer 10, the controller 
+			  firmware update wizard does not show the f/w update 
+			  file name when the upload completes. To refresh 
+			  the display, click Next then Back.
+				
+			o We do not recommend using multiple browsers 
+			  simultaneously on the same maxView 
+			  instance. Doing so may cause display issues or freezes; 
+			  to restore maxView, refresh the display by pressing F5.
+				
+		4.1.6. Remote System Access on Linux and Windows
+		
+			To avoid remote system access failures from Linux 
+			and Windows clients running maxView Storage Manager, 
+			check and update one or all of the following system 
+			and network settings:
+			
+			Windows:
+			o Ensure that the DNS server information is properly 
+			  configured
+			
+			RHEL/Linux:
+			
+			o Set server.properties file permissions to at least 
+			  read-only at all levels
+				1.	Stop all maxView services.
+				2.	Set the Permissions of server.properties file to 
+					read and write or read-only at all levels 
+					(Owner, Group and Others). 
+				3.	Apply and close.
+				4.	Restart all services in the given order - cim, 
+					agent, tomcat
+				5.	Now try to remote login to this system from any 
+					other system
+				
+			o Check/update these network settings:
+				1.	Disable SELinux
+				2.	Disable firewall.
+				3.	Disable the ipv6 in the system, if ipconfig shows 
+					both ipv4 and ipv6 address.
+				4.	Remove the virtual bridge virbr0, if present
+				5.	Enter local ip address in 'localip' parameter in 
+					server.properties file
+					
+		4.1.7. RAID 10 Segment Order
+		
+			maxView Storage Manager and the Ctrl-A BIOS report the 
+			wrong segment order for RAID 10s, regardless of the order 
+			in which the drives are selected.
+			Example 1: Create RAID 10 with 2 SDDs and 2 HDDs in maxView 
+			Storage Manager:
+			
+				(1a) ARCCONF and maxView Storage Manager see the 
+					following RAID segment order: 
+							Device 2 (S1) 
+							Device 1 (H2) 
+							Device 3 (S2) 
+							Device 0 (H1) 
+				
+				(1b) the BIOS/CTRL-A sees the following RAID segment 
+					order: 
+							Device 2 (S1) 
+							Device 1 (H2) 
+							Device 0 (H1) 
+							Device 3 (S2) 
+				
+				(1c) the correct and expected RAID segment order is: 
+							Device 2 (S1) 
+							Device 0 (H1) 
+							Device 3 (S2) 
+							Device 1 (H2)
+							
+			Example 2: Create RAID 10 with 2 SDDs and 2 HDDs 
+			with ARCCONF:
+			
+				(2a) the BIOS/CTRL-A sees the following RAID segment 
+					order: 
+								  Device 0 (H1) 
+								  Device 2 (S1) 
+								  Device 1 (H2) 
+								  Device 3 (S2) 
+			   
+				(2b) ARCCONF and maxView Storage Manager see the 
+					correct RAID segment order: 
+								  Device 2 (S1) 
+								  Device 0 (H1) 
+								  Device 3 (S2) 
+								  Device 1 (H2)
+								  
+		4.1.8. RAID 10 Rebuild Order
+		
+			With a degraded RAID 10 logical drive, the drive is 
+			rebuilt one leg at a time, not in parallel.
+			
+		4.1.9. Locate Logical Drive Blink LED
+		
+			In maxView Storage Manager, Locate Logical Drive 
+			continues to blink the LED for a pulled physical drive 
+			in the array after the locate action is stopped. 
+			(For unpulled drives, the blinking stops.) This issue is 
+			not seen with ARCCONF.
+			
+		4.1.10. ARCCONF Backward Compatibility
+		
+			ARCCONF is backward compatible with older Adaptec 
+			controller models. As a result, the ARCCONF user's guide 
+			and online help show command options that are not 
+			supported by newer Adaptec controllers, like the 
+			Adaptec Series 7 and Adaptec Series 8 or later products.
+			
+			Example: With ARCCONF SETMAXCACHE, Adaptec Series 7 and 
+			Series 8 controllers do not support ADDTOPOOL or 
+			REMOVEFROMPOOL
+			
+		4.1.11. Updating Hard Disk Firmware on VMware Guest OS
+		
+			Updating the firmware for a SAS hard disk drive with 
+			ARCCONF/maxView can crash (PSOD) the VMware Guest OS. 
+			This issue is seen with SAS hard drives only; with 
+			SATA drives, the firmware update completes successfully.
+
+		4.1.12. Hot Swap Issues on VMware CentOS Guest OS
+		
+			Due to a limitation with the VMware CentOS Guest OS 
+			network configuration, maxView Storage Manager does not 
+			show newly added or removed hot swap drives. 
+			(ARCCONF sees the configuration change but maxView 
+			does not.)
+			
+			WORKAROUND: (1) reboot the system or restart maxView 
+			services; (2) adjust the network configuration; contact 
+			Adaptec Support for more information.
+			
+		4.1.13. Enclosure Status Reporting
+		
+			Enclosure status, in maxView Storage Manager, is 
+			event-driven. As a result, enclosures can have a 
+			"Degraded" status even if related resources (fan, 
+			temperature, power) are performing normally (Optimal 
+			status). For instance, the Enclosure status changes 
+			to "Degraded" if the system reports an "Enclosure 
+			device not responding ..." event, even if other sensor 
+			values are normal.
+			
+		4.1.14. PHY Status on Enclosure Backplanes
+		
+			In the Controller Properties window, maxView Storage 
+			Manager shows the Connector Info as "unknown" for all 
+			PHYs on an enclosure-based backplane (for instance, a 
+			backplane attached to connector 1).
+			
+		4.1.15. Special Characters in Logical Device Names
+		
+			Special characters are permitted in logical device 
+			names in maxView Storage Manager, the BIOS, and ARCCONF. 
+			However, with Linux ARCCONF (create, setname), special 
+			characters must be "escaped" to ensure proper 
+			interpretation. For example:
+			
+			ARCCONF SETNAME 1 LOGICALDRIVE 1 arc_ldrive%\$12\&
+			
+		4.1.16. Speaker Status on SuperMicro SAS2X28 Enclosures
+		
+			SuperMicro SAS2X28 enclosures do not propagate 
+			the speaker status to maxView Storage Manager. As 
+			a result, maxView always displays the speaker 
+			status as Off.
+			
+		4.1.17. Online Help Issues
+		
+			o When opening the maxView Storage Manager help 
+			  from a remote Linux system (eg, over a VPN), the 
+			  help window may fail to open with a 'can't establish 
+			  connection to server' message.
+			
+			  WORKAROUND: replace 127.0.0.1:8443 in the URL with 
+			  <system_ip_address>:8443
+				
+			o In IE11, topics in the help may display with a 'Topics 
+			  Not Found' message when their corresponding links are 
+			  clicked in the navigation pane of the help.
+				
+			  WORKAROUND: click on the "Add" browser link to add 
+			  certification to view the content.
+			
+		4.1.18. Broadcasting Alerts About Status and Activity
+		
+		This feature is not supported by the maxView Storage 
+		Manager or ARCCONF and has been removed from the product 
+		documentation.
+		
+	4.2. Limitations Specific to Series 6, 7, 8 Controllers
+	
+		4.2.1. RAID-Level Migrations
+		
+			o The following RAID-level migrations (RLM) are 
+			  supported in this release:
+				-	RAID 0 to RAID 5
+				-	RAID 0 to RAID 10
+				-	RAID 5 to RAID 6
+				-	RAID 6 to RAID 5
+				-	RAID 10 to RAID 5
+				-	RAID 5 to RAID 10
+				-	RAID 1 to RAID 5
+				-	SIMPLE VOLUME to RAID 1
+				-	RAID 1 to SIMPLE VOLUME
+				
+			o When migrating a Simple Volume to RAID 1, maxView 
+			  Storage Manager reports the logical drive state as 
+			  Impacted (rather than Reconfiguring); 
+			  this is normal.
+				
+			o We do not recommend performing a RAID-level 
+			  migration or Online Capacity Expansion (OCE) 
+			  on a logical drive with maxCache SSD caching 
+			  enabled.
+				
+			  NOTE: maxView Storage Manager grays out the 
+			  options for logical drives with maxCache enabled. 
+			  ARCCONF terminates the task.
+				
+			o Always allow a RAID-level migration to complete 
+			  before creating a support archive file. Otherwise, 
+			  the support archive will include incorrect 
+			  partition information. Once the migration is 
+			  complete, the partition information will be reported 
+			  correctly.
+				
+		4.2.2. maxCache Device Migration
+		
+			Only one maxCache Device is supported per controller. 
+			Moving the maxCache Device (all underlying SSDs) from 
+			one controller to another (assuming both controllers 
+			support maxCache) is supported only if (1) the new 
+			controller does not have a maxCache Device or any other 
+			maxCache Device with a conflicting device number and 
+			(2) only after a clean shutdown 
+			on the old controller.
+			
+		4.2.3. ARCCONF maxCache Device Size Issue
+		
+			ARCCONF supports >2TB maxCache Devices if you create 
+			the device with the 'max' parameter. However, the 
+			functional limit for the maxCache Device is 2TB, 
+			which is also the limit in maxView Storage Manager.
+			
+		4.2.4. Power Management Issues
+		
+			o Power management is not supported on FreeBSD.
+			
+			o Capturing support logs from maxView or ARCCONF 
+			  will spin up drives when power management is 
+			  active. This behavior is by design.
+				
+			o The Logical Drive Creation wizard no longer 
+			  includes the option to enable power management settings.
+				
+			  WORKAROUND: Enable power management for the 
+			  logical drive from the Set Properties window.
+				
+		4.2.5. Verify with Fix
+		
+			In maxView Storage Manager and ARCCONF, the Verify 
+			with Fix operation is NOT available when:
+			
+			1.	The logical drive has a non-redundant RAID level
+			2.	Other tasks are in progress on the logical drive
+			3.	The logical drive is in a non-optimal or impacted state
+			
+		4.2.6. ATA Secure Erase
+		
+			In ARCCONF, the ATA Secure Erase operation cannot 
+			be aborted. Once started, it continues to completion.
+			
+			NOTE: ATA Secure Erase is also available in the 
+			Ctrl-A BIOS and maxView Storage Manager.
+			
+		4.2.7. Series 6 Controller Issues
+		
+			The following issues are seen only with Adaptec 
+			Series 6 RAID controllers:
+			o In maxView Storage Manager, the Preserve Cache 
+			  option on the Set Properties window is not 
+			  supported on Series 6 RAID controllers. Attempting 
+			  to set this option for the Series 6 controller fails.
+				
+			o Renaming a RAID volume disables the write-cache 
+			  (if enabled). You cannot re-enable the write-cache 
+			  in maxView Storage Manager.
+				
+			  WORKAROUND: Use ARCCONF to enable the write-cache.
+				
+			o In a VMware Guest OS under VMware 5.x, maxView 
+			  Storage Manager and ARCCONF do not detect existing 
+			  logical drive partitions. As a result, 
+			  attempting to delete, clear, or erase the logical 
+			  drive may fail.
+				
+			o On Series 6 controllers, maxView Storage Manager 
+			  deletes partitioned JBODs without issuing a 
+			  warning message.
+				
+			o Series 6 controllers do not support the ARCCONF 
+			  GETPERFORM command.
+			
+		4.2.8. Simple Volume Support
+		
+			o In this release, you can create a maximum of 128 
+			  Simple Volumes in maxView Storage Manager, ARCCONF, 
+			  or the BIOS.
+				
+			o When a Simple Volume fails, the status remains 
+			  unchanged after drive replacement.
+				
+			  WORKAROUND: Manually delete the Simple Volume to 
+			  remove it.
+				
+		4.2.9. Auto-Volume Support
+		
+			o Changing a controller into Auto-Volume mode 
+			  (ARCCONF/BIOS) is not supported if the configuration 
+			  includes any logical device type other than Simple 
+			  Volume, including a maxCache Device. The mode switch 
+			  from RAID mode to Auto-Volume mode is blocked if any 
+			  other type of logical volume exists (including 
+			  maxCache). After switching to Auto-Volume mode, 
+			  you can create and delete Simple Volumes 
+			  only in maxView Storage Manager and ARCCONF.
+				
+			o In Auto-Volume mode, only the first 128 RAW drives 
+			  are converted to Simple Volumes; the rest of the 
+			  RAW drives remain unchanged. If you uninitialize 
+			  a Ready drive while the controller is in Auto-Volume 
+			  mode, the firmware converts the drive automatically 
+			  until the Simple Volume count reaches the maximum.
+				
+		4.2.10. Hot-Removing Disk Drives on Xenserver Guest OS
+		
+			XenServer does not support "hot-removal" of disk 
+			drives from a partitioned logical drive. As a result, 
+			if you hot remove a disk from a logical drive, 
+			the Guest OS becomes inaccessible because the drive 
+			partition remains visible to the OS instead of being cleared.
+			
+			WORKAROUND: Reboot the XenServer host, detach the 
+			failed partition, then restart the VM.
+			
+		4.2.11. Changing Read and Write Cache Settings for 
+			Logical Drive
+		
+			maxView Storage Manager does not allow you to change 
+			the read-cache and write-cache settings for a logical drive 
+			in one step. You must click OK after each change.
+			
+	4.3. Limitations Specific to Smart Family Controllers
+	
+		4.3.1. SES Passthrough Commands to Expanders
+		
+			SES passthrough commands to expanders fail.
+			
+		4.3.2 Firmware Upgrade Issues
+			
+			For systems using Adaptec HBA 1000 with an Adaptec 
+			SAS Expander 82885T card, where the ARCCONF utility 
+			is used to upgrade the expander firmware, ARCCONF 
+			may crash if 64-bit chunk sizes are used.  
+			
+			WORKAROUND: Use 32-bit chunk sizes to upgrade/downgrade 
+			the expander firmware.
+
+
+
+Copyright 2016 Microsemi Corporation. All rights reserved. 
+Microsemi and the Microsemi logo are trademarks of Microsemi 
+Corporation. All other trademarks and service marks are 
+the property of their respective owners.
+
+PMC-2153191, Issue 2
+
+Microsemi Corporation (Nasdaq: MSCC) offers a comprehensive 
+portfolio of semiconductor and system solutions for communications, 
+defense and security, aerospace, and industrial markets. 
+Products include high-performance and radiation-hardened 
+analog mixed-signal integrated circuits, FPGAs, SoCs, and 
+ASICs; power management products; timing and synchronization 
+devices and precise time solutions; voice processing devices; 
+RF solutions; discrete components; enterprise storage and 
+communications solutions; security technologies and scalable 
+anti-tamper products; Ethernet solutions; Power-over-Ethernet 
+ICs and midspans; custom design capabilities and services. 
+Microsemi is headquartered in Aliso Viejo, California and has 
+approximately 4,800 employees world-wide. 
+Learn more at www.microsemi.com.
+
+Microsemi makes no warranty, representation, or guarantee 
+regarding the information contained herein or the suitability 
+of its products and services for any particular purpose, 
+nor does Microsemi assume any liability whatsoever arising 
+out of the application or use of any product or circuit. 
+The products sold hereunder and any other products sold 
+by Microsemi have been subject to limited testing and should 
+not be used in conjunction with mission-critical equipment 
+or applications. Any performance specific ations are believed 
+to be reliable but are not verified, and Buyer must conduct 
+and complete all performance and other testing of the products, 
+alone and together with, or installed in, any end-products. 
+Buyer shall not rely on any data and performance specifications 
+or parameters provided by Microsemi. It is the Buyer's 
+responsibility to independently determine suitability of 
+any products and to test and verify the same. The information 
+provided by Microsemi hereunder is provided as is, where is 
+and with all faults, and the entire risk associated with such 
+information is entirely with the Buyer. Microsemi does not 
+grant, explicitly or implicitly, to any party any patent 
+rights, licenses, or any other IP rights, whether with regard 
+to such information itself or anything described by 
+such information. Information provided in this document is 
+proprietary to Microsemi, and Microsemi reserves the right 
+to make any changes to the information in this document or 
+to any products and services at any time without notice.
+
+The technology discussed in this document may be protected by 
+one or more patent grants.
+
+ 
+ 

amd64/2.02/License.txt

@@ -0,0 +1,292 @@
+International License Agreement for Non-Warranted Programs
+
+Part 1 - General Terms 
+
+PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE PROGRAM.
+Adaptec WILL LICENSE THE PROGRAM TO YOU ONLY IF YOU FIRST ACCEPT THE
+TERMS OF THIS AGREEMENT. BY USING THE PROGRAM YOU AGREE TO THESE
+TERMS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT,
+PROMPTLY RETURN THE UNUSED PROGRAM TO THE PARTY (EITHER Adaptec OR
+ITS RESELLER) FROM WHOM YOU ACQUIRED IT TO RECEIVE A REFUND OF
+THE AMOUNT YOU PAID. 
+
+The Program is owned by (Adaptec) or a supplier of Adaptec 
+and is copyrighted and licensed, not sold. 
+
+The term "Program" means the original program and all whole or
+partial copies of it. A Program consists of machine-readable
+instructions, its components, data, audio-visual content (such
+as images, text, recordings, or pictures), and related licensed
+materials. 
+
+This Agreement includes Part 1 - General Terms and Part 2 
+Country unique Terms and is the complete agreement regarding the
+use of this Program, and replaces any prior oral or written
+communications between you and Adaptec. The terms of Part 2 may
+replace or modify those of Part 1. 
+
+
+1. License 
+
+Use of the Program 
+
+Adaptec grants you a nonexclusive license to use the Program. 
+
+You may 1) use the Program to the extent of authorizations you
+have acquired and 2) make and install copies to support the
+level of use authorized, providing you reproduce the copyright
+notice and any other legends of ownership on each copy, or
+partial copy, of the Program. 
+
+If you acquire this Program as a program upgrade, your
+authorization to use the Program from which you upgraded is
+terminated. 
+
+You will ensure that anyone who uses the Program does so only in
+compliance with the terms of this Agreement. 
+
+You may not 1) use, copy, modify, or distribute the Program
+except as provided in this Agreement; 2) reverse assemble,
+reverse compile, or otherwise translate the Program except as
+specifically permitted by law without the possibility of
+contractual waiver; or 3) sublicense, rent, or lease the
+Program. 
+
+Transfer of Rights and Obligations 
+
+You may transfer all your license rights and obligations under a
+Proof of Entitlement for the Program to another party by
+transferring the Proof of Entitlement and a copy of this
+Agreement and all documentation. The transfer of your license
+rights and obligations terminates your authorization to use the
+Program under the Proof of Entitlement. 
+
+
+2. Proof of Entitlement 
+
+The Proof of Entitlement for this Program is evidence of your
+authorization to use this Program and of your eligibility for
+future upgrade program prices (if announced) and potential
+special or promotional opportunities. 
+
+
+3. Charges and Taxes 
+
+Adaptec defines use for the Program for charging purposes and
+specifies it in the Proof of Entitlement. Charges are based on
+extent of use authorized. If you wish to increase the extent of
+use, notify Adaptec or its reseller and pay any applicable charges.
+Adaptec does not give refunds or credits for charges already due or
+paid. 
+
+If any authority imposes a duty, tax, levy or fee, excluding
+those based on Adaptec's net income, upon the Program supplied by
+Adaptec under this agreement, then you agree to pay that amount 
+as Adaptec specifies or
+supply exemption documentation. 
+
+
+4. No Warranty 
+
+SUBJECT TO ANY STATUTORY WARRANTIES WHICH CAN NOT BE EXCLUDED,
+Adaptec MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
+INCLUDING WITHOUT LIMITATION, THE WARRANTY OF NON-INFRINGEMENT
+AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+PARTICULAR PURPOSE, REGARDING THE PROGRAM OR TECHNICAL SUPPORT,
+IF ANY. Adaptec MAKES NO WARRANTY REGARDING THE CAPABILITY OF THE
+PROGRAM TO CORRECTLY PROCESS, PROVIDE AND/OR RECEIVE DATE DATA
+WITHIN AND BETWEEN THE 20TH AND 21ST CENTURIES. 
+
+The exclusion also applies to any of Adaptec's subcontractors,
+suppliers, or program developers (collectively called
+"Suppliers"). 
+
+Manufacturers, suppliers, or publishers of non-Adaptec Programs may
+provide their own warranties. 
+
+
+5. Limitation of Liability 
+
+NEITHER Adaptec NOR ITS SUPPLIERS WILL BE LIABLE FOR ANY DIRECT OR
+INDIRECT
+
+DAMAGES, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
+SAVINGS, OR ANY INCIDENTAL, SPECIAL, OR OTHER ECONOMIC
+CONSEQUENTIAL DAMAGES, EVEN IF Adaptec IS INFORMED OF THEIR
+POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
+LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE
+EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU. 
+
+
+6. General 
+
+Nothing in this Agreement affects any statutory rights of
+consumers that cannot be waived or limited by contract. 
+
+Adaptec may terminate your license if you fail to comply with the
+terms of this Agreement. If Adaptec does so, you must immediately
+destroy the Program and all copies you made of it. 
+
+You agree to comply with applicable export laws and regulations. 
+
+Neither you nor Adaptec will bring a legal action under this
+Agreement more than two years after the cause of action arose
+unless otherwise provided by local law without the possibility
+of contractual waiver or limitation. 
+
+Neither you nor Adaptec is responsible for failure to fulfill any
+obligations due to causes beyond its control. 
+
+Adaptec does not provide program services or technical support,
+unless Adaptec specifies otherwise. 
+
+The laws of the country in which you acquire the Program govern
+this Agreement, except 1) in Australia, the laws of the State or
+Territory in which the transaction is performed govern this
+Agreement; 2) in Albania, Armenia, Belarus, Bosnia/Herzegovina,
+Bulgaria, Croatia, Czech Republic, Georgia, Hungary, Kazakhstan,
+Kirghizia, Former Yugoslav Republic of Macedonia
+(FYROM), Moldova, Poland, Romania, Russia, Slovak Republic,
+Slovenia, Ukraine, and Federal Republic of Yugoslavia, the laws
+of Austria govern this Agreement; 3) in the United Kingdom, all
+disputes relating to this Agreement will be governed by English
+Law and will be submitted to the exclusive jurisdiction of the
+English courts; 4) in Canada, the laws in the Province of
+Ontario govern this Agreement; and 5) in the United States and
+Puerto Rico, and People's Republic of China, the laws of the 
+State of New York govern this Agreement. 
+
+
+Part 2 - Country-unique Terms 
+
+
+AUSTRALIA: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Although Adaptec specifies that there are no warranties, you may
+have certain rights under the Trade Practices Act 1974 or other
+legislation and are only limited to the extent permitted by the
+applicable legislation. 
+
+Limitation of Liability (Section 3): 
+The following paragraph is added to this Section: 
+
+Where Adaptec is in breach of a condition or warranty implied by the
+Trade Practices Act 1974, Adaptec's liability is limited to the
+repair or replacement of the goods, or the supply of equivalent
+goods. Where that condition or warranty relates to right to
+sell, quiet possession or clear title, or the goods are of a
+kind ordinarily acquired for personal, domestic or household use
+or consumption, then none of the limitations in this paragraph
+apply. 
+
+
+GERMANY:
+
+No Warranty (Section 4):
+The following paragraphs are added to this Section:
+
+The minimum warranty period for Programs is six months.
+
+In case a Program is delivered without Specifications, we will
+only warrant that the Program information correctly describes
+the Program and that the Program can be used according to the
+Program information. You have to check the usability according
+to the Program information within the "money-back guaranty"
+period.
+
+Limitation of Liability (Section 5):
+The following paragraph is added to this Section:
+
+The limitations and exclusions specified in the Agreement will
+not apply to damages caused by Adaptec with fraud or gross
+negligence, and for express warranty. 
+
+
+INDIA: 
+
+General (Section 6): 
+The following replaces the fourth paragraph of this Section: 
+
+If no suit or other legal action is brought, within two years
+after the cause of action arose, in respect of any claim that
+either party may have against the other, the rights of the
+concerned party in respect of such claim will be forfeited and
+the other party will stand released from its obligations in
+respect of such claim. 
+
+
+IRELAND: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Except as expressly provided in these terms and conditions, all
+statutory conditions, including all warranties implied, but
+without prejudice to the generality of the foregoing, all
+warranties implied by the Sale of Goods Act 1893 or the Sale of
+Goods and Supply of Services Act 1980 are hereby excluded. 
+
+
+ITALY:
+
+Limitation of Liability (Section 5):
+This Section is replaced by the following:
+
+Unless otherwise provided by mandatory law, Adaptec is not liable
+for any damages which might arise. 
+
+
+NEW ZEALAND: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Although Adaptec specifies that there are no warranties, you may
+have certain rights under the Consumer Guarantees Act 1993 or
+other legislation which cannot be excluded or limited. The
+Consumer Guarantees Act 1993 will not apply in respect of any
+goods or services which Adaptec provides, if you require the goods
+and services for the purposes of a business as defined in that
+Act. 
+
+Limitation of Liability (Section 5): 
+The following paragraph is added to this Section: 
+
+Where Programs are not acquired for the purposes of a business
+as defined in the Consumer Guarantees Act 1993, the limitations
+in this Section are subject to the limitations in that Act. 
+
+
+PEOPLE'S REPUBLIC OF CHINA:
+
+Charges (Section 3):
+The following paragraph is added to the Section:
+
+All banking charges incurred in the People's Republic of China
+will be borne by you and those incurred outside the People's
+Republic of China will be borne by Adaptec. 
+
+
+UNITED KINGDOM: 
+
+Limitation of Liability (Section 5): 
+The following paragraph is added to this Section at the end of
+the first paragraph: 
+
+The limitation of liability will not apply to any breach of
+Adaptec's obligations implied by Section 12 of the Sales of Goods
+Act 1979 or Section 2 of the Supply of Goods and Services Act
+1982. 
+
+
+UNITED STATES AND CANADA:
+
+No Country-unique Terms apply.
+
+
+By continuing with the installation of the Program, you are 
+accepting the terms and conditions above.
+

amd64/2.02/README.TXT

@@ -0,0 +1,708 @@
+README: maxView Storage Manager & ARCCONF Command Line Utility
+
+Microsemi Adaptec maxView Storage Manager
+Microsemi Adaptec Command Line Interface Utility (ARCCONF)
+
+as of September 7, 2016
+--------------------------------------------------------------------
+Please check the product website for the newer versions of this file to
+ensure you are reviewing the latest information.
+
+This file contains important information about issues and errata that were
+discovered after completion of the standard product documentation.
+
+In the case of conflict between various parts of the documentation set, 
+this file contains the most current information.
+
+--------------------------------------------------------------------
+
+Table of Contents
+
+Chapter 1. New Features of this Release 	 
+
+Chapter 2. Software Versions and Documentation 	 
+2.1 Utility Software 	 
+2.2 Documentation 	 
+    2.2.1 Series 6, 7, 8 Product Documentation 	 
+    2.2.2 HBA 1000 Series Product Documentation 	 
+    2.2.3 SmartIOC Product Documentation 	 
+
+Chapter 3. Installation Notes 	 
+3.1 Installation and Setup 	 
+3.2 Supported Operating Systems 	 
+    3.2.1 Series 6, 7, 8 Controllers 	 
+    3.2.2 Smart Family Controllers 	 
+3.3 General Setup Notes 	 
+3.4 Remote Access 	 
+3.5 Windows 8 Setup 	 
+3.6 SLES Setup 	 
+3.7 Ubuntu Setup 	 
+3.8 Bootable USB Image Security Warnings 	 
+3.9 RAW Device Setup (Series 6, 7, 8 Only) 	 
+3.10 maxView Plugin for VMware vSphere Web Client 	 
+
+Chapter 4. Known Limitations 	 
+4.1 Global Limitations 	 
+     4.1.1 Dual-Controller Systems 	 
+     4.1.2 Email Notifications 	 
+     4.1.3 SGPIO Enclosures 	 
+     4.1.4 Non-RAID Mode Controllers 	 
+     4.1.5 Browser Issues 	 
+     4.1.6 Remote System Access on Linux and Windows 	 
+     4.1.7 RAID 10 Segment Order 	 
+     4.1.8 RAID 10 Rebuild Order 	 
+     4.1.9 Locate Logical Drive Blink LED 	 
+     4.1.10 ARCCONF Backward Compatibility 	 
+     4.1.11 Updating Hard Disk Firmware on VMware Guest OS 	 
+     4.1.12 Hot Swap Issues on VMware CentOS Guest OS 	 
+     4.1.13 Enclosure Status Reporting 	 
+     4.1.14 PHY Status on Enclosure Backplanes 	 
+     4.1.15 Special Characters in Logical Device Names 	 
+     4.1.16 Speaker Status on SuperMicro SAS2X28 Enclosures 	 
+     4.1.17 Online Help Issues 	 
+     4.1.18 Broadcasting Alerts About Status and Activity 	 
+     4.1.19 User-Specified Archive Path 	 
+     4.1.20 Clear Configuration Status After Re-Insertion 	 
+     4.1.21 Configuration Changes in Device Manager 	 
+4.2 Limitations for Series 6, 7, 8 Controllers 	 
+     4.2.1 RAID-Level Migrations 	 
+     4.2.2 maxCache Device Migration 	 
+     4.2.3 ARCCONF maxCache Device Size Issue 	 
+     4.2.4 Power Management Issues 	 
+     4.2.5 Verify/Verify with Fix 	 
+     4.2.6 ATA Secure Erase 	 
+     4.2.7 Series 6 Controller Issues 	 
+     4.2.8 Simple Volume Support 	 
+     4.2.9 Auto-Volume Support 	 
+     4.2.10 Hot-Removing Disk Drives on Xenserver Guest OS 	 
+     4.2.11 Viewing Logical Drive Details After Re-Insertion 	 
+4.3 Limitations for Smart Family Controllers 	 
+     4.3.1 SES Passthrough Commands to Expanders 	 
+     4.3.2 Firmware Upgrade Issues 	 
+     4.3.3 Mount Point Information with MPIO Support 	 
+     4.3.4 Locate Physical Disk LED Behavior 	 
+
+--------------------------------------------------------------------
+
+Chapter 1. New Features of this Release
+
+* Added new features:
+  * Support for SMR HA(1) and SMR DM drives for all RAID levels and hot spares
+  * Ability to attach support archive to email notifications
+  * Save Config/Restore Config ribbon actions moved from Controller group to
+    System group (Clear Config remains in Controller group.)
+  * Misc UI changes/enhancements:
+    * SMR drive identification in Enterprise view, Logical Device wizard,
+      Spare Management wizard, Dashboard (tabs)
+    * Display I2C address in Controller Properties tab (Smart controllers 
+      only)
+    * Display physical devices in Summary panel for Logical Device wizard
+    * Display enclosure information in Summary panel when multiple enclosures 
+      selected for Initialize/Uninitialize (Series 6/7/8)
+    * Display specific failure messages instead of generic "Operation failed"
+    * Display event message for Firmware Update complete
+    * Display new firmware image version in maxView (and ARCCONF) for 
+      Microsemi Adaptec(r) SAS Expander AEC-82885T
+    * New Enclosure node tabs: Resources, Slots
+    * Multi-language support in maxView: English, Chinese, German, Japanese, 
+      Spanish, Russian
+  * New/Enhanced ARCCONF commands:
+    * Series 6/7/8: UARTLOG CONSOLE
+    * Smart/HBA controllers: SETCONTROLLERPARAM <I2CAddress>, SAVECONFIG, 
+      PLAYCONFIG
+    * Add unused and reserved size of physical drive properties in 
+      GETCONFIG output
+  * Support for statically-linked ARCCONF on Linux x64 (allows ARCCONF to run 
+    without any OS library dependency)
+  * Support for PowerPC platforms running RHEL, SLES, and Ubuntu, and PowerKVM 
+    (Series 6/7/8)
+  * Support for Microsoft Hyper-V hypervisor, Hyper-V Windows & Linux 
+    Guest OSs
+* Bugfixes
+
+---------------
+ (1) SMR: Shingled Magnetic Recording. HA: Host Aware (backward compatible
+ with standard HDD). DM: Device Managed (backward compatible with standard 
+ HDD).
+
+--------------------------------------------------------------------
+
+Chapter 2. Software Versions and Documentation
+
+2.1. Utility Software
+
+* Microsemi Adaptec(r) maxView Storage Manager Version 2.02.00 (B22404)
+* Microsemi Adaptec(r) ARCCONF Command Line Interface Utility Version 2.02.00 (B22404)
+
+2.2. Documentation
+
+2.2.1 Series 6, 7, 8 Product Documentation
+
+PDF Format
+* maxView Storage Manager User's Guide for Microsemi Adaptec ARC-Family 
+  Controllers
+* Microsemi Adaptec RAID Controller Command Line Utility User's Guide
+
+HTML and Text Format
+* maxView Storage Manager Online Help
+* maxView Storage Manager/ARCCONF README.TXT file
+
+2.2.2 HBA 1000 Series Product Documentation
+
+PDF:
+* maxView Storage Manager User's Guide for Microsemi Smart-Family Controllers
+* Microsemi Adaptec HBA 1000 Series Command Line Utility User's Guide
+
+HTML and Text Format:
+* maxView Storage Manager for Smart-Family Controllers Online Help
+* maxView Storage Manager/ARCCONF README.TXT file
+
+2.2.3 SmartIOC Product Documentation
+
+PDF:
+* maxView Storage Manager User's Guide for Microsemi Smart-Family Controllers
+* Microsemi SmartIOC 2000 Command Line Utility User's Guide
+
+HTML and Text Format:
+* maxView Storage Manager for Microsemi Smart-Family Controllers Online Help
+* maxView Storage Manager/ARCCONF README.TXT file
+
+--------------------------------------------------------------------
+
+Chapter 3. Installation Notes
+
+3.1. Installation and Setup
+Refer to your product documentation for the installation and setup details:
+* Your product Installation and User's Guide contains complete installation 
+  information for your product's drivers.
+* The maxView Storage Manager User's Guide for your product contains 
+  installation information for the maxView Storage Manager software.
+* The Command Line Utility User's Guide for your product contains complete 
+  installation information for ARCCONF.
+
+3.2 Supported Operating Systems
+
+Notes:
+
+1. maxView Storage Manager and ARCCONF Command Line Utility are supported on 
+   64-bit operating systems only.
+2. The Boot USB (offline or pre-boot) for ARCCONF and maxView Storage Manager 
+   is supported on Linux.
+
+3.2.1 Series 6, 7, 8 Controllers
+
+Microsoft Windows
+* Microsoft(r) Windows(r) Server 2012 (64-bit)
+* Microsoft(r) Windows(r) Server 2012 R2 (64-bit)
+* Microsoft(r) Windows(r) Server 2008 R2 SP1 (64-bit)
+* Microsoft(r) Windows(r) SBS 2011 (Standard and Essential, 64-bit)
+* Microsoft(r) Windows(r) 10 (64-bit)
+* Microsoft(r) Windows(r) 8.1 (64-bit)
+* Microsoft(r) Windows(r) 7 (64-bit)
+* Microsoft(r) WinPE 5.x (64-bit)
+
+Linux
+* Red Hat(r) Enterprise Linux/CentOS 7.2, 7.1 (64-bit)
+* Red Hat(r) Enterprise Linux/CentOS 6.8, 6.7 (64-bit)
+* Red Hat(r) Enterprise Linux/CentOS 5.11, 5.10 (64-bit)
+* SuSE Linux Enterprise Server 12 SP1 (64-bit)
+* SuSE Linux Enterprise Server 12 (64-bit)
+* SuSE Linux Enterprise Server 11 SP4 and SP3 (64-bit)
+* Debian Linux 8.3, 8.1 (64-bit)
+* Ubuntu Linux 16.04, 14.04.4 (64-bit)
+* Fedora Linux 23 (64-bit)
+
+Linux on PowerPC
+* Red Hat(r) Enterprise Linux 7.2 (64-bit)
+* SuSE Linux Enterprise Server 12 SP1 (64-bit)
+* Ubuntu Linux 16.04, 14.04.4 (64-bit)
+* PowerKVM 3.1.0.1 (64-bit)
+
+FreeBSD
+* FreeBSD(r) 10.2 (64-bit)
+* FreeBSD(r) 9.3 (64-bit)
+
+Solaris
+* Solaris 11.2 (64-bit)
+* Solaris 10 U9 (64-bit)
+
+Virtual OS Environments
+* VMware vSphere 6.0 (64-bit)
+* VMware ESXi 6.0, ESXi 5.5 U3 and U2 (64-bit)
+* Citrix XenServer 6.5.1 (64-bit)
+* Microsoft Hyper-V (64-bit)
+
+3.2.2 Smart Family Controllers
+
+Microsoft Windows
+* Microsoft(r) Windows(r) Server 2012 (64-bit)
+* Microsoft(r) Windows(r) Server 2012 R2 (64-bit)
+* Microsoft(r) Windows(r) Server 2008 R2 SP1 (64-bit)
+* Microsoft(r) Windows(r) SBS 2011 (Standard and Essential, 64-bit)
+* Microsoft(r) Windows(r) 10 (64-bit)
+* Microsoft(r) Windows(r) 8.1 (64-bit)
+* Microsoft(r) Windows(r) 7 (64-bit)
+
+Linux
+* Red Hat(r) Enterprise Linux/CentOS 7.2, 7.1 (64-bit)
+* Red Hat(r) Enterprise Linux/CentOS 6.8, 6.7 (64-bit)
+* Red Hat(r) Enterprise Linux/CentOS 5.11, 5.10 (64-bit)
+* SuSE Linux Enterprise Server 12 SP1 (64-bit)
+* SuSE Linux Enterprise Server 12 (64-bit)
+* SuSE Linux Enterprise Server 11 SP4 and SP3 (64-bit)
+* Ubuntu Linux 16.04, 14.04.4 (64-bit)
+
+Virtual OS Environments
+* VMware vSphere 6.0 U1, 6.0 (64-bit)
+* VMware ESXi 6.0, ESXi 5.5 U3 and U2 (64-bit)
+* Citrix XenServer 6.5.1 (64-bit)
+* Microsoft Hyper-V (64-bit)
+
+
+3.3 General Setup Notes
+   * maxView Storage Manager is not backwards-compatible with Series 5 and 
+     older Adaptec controller models.
+   * maxView Storage Manager and legacy Adaptec Storage Manager (ASM) cannot 
+     coexist on the same system.
+   * For Series 6, 7, 8 controllers:
+     * maxView Storage Manager is not supported on FreeBSD. Use ARCCONF to   
+       create and manage arrays.
+
+3.4 Remote Access
+maxView Storage Manager requires the following range of ports to be open for 
+remote access:
+* 34570-34580 (TCP)
+* 34570 (UDP)
+* 34577-34580 (UDP)
+
+3.5 Windows 8 Setup
+To log in and use maxView Storage Manager on a Windows 8 system, you must 
+create a local user account; you cannot use your MS Live account. To create a 
+local user account:
+1. Log into your MS Live account.
+2. Select Settings->Change PC Settings->Users->Switch to Local user.
+3. Provide account details.
+4. Start maxView Storage Manager and log in with your local user account 
+   credentials.
+
+3.6 SLES Setup
+To avoid a problem with launching maxView Storage Manager on SLES 11 or SLES 
+12 x64 systems with DHCP enabled, ensure that the /etc/hosts file maps the 
+server IP address to a valid host name; it is not sufficient to map the IP 
+address to 'localhost'.
+
+3.7 Ubuntu Setup
+* To avoid a maxView Login failure on Ubuntu systems, you must ensure that the 
+  root user account is enabled. (It is disabled, by default, on Ubuntu 14.04 
+  and later because no password is set.)
+  For example: sudo bash; sudo passwd root
+* When upgrading maxView Storage Manager on an existing Ubuntu Linux x64 
+  installation, you must enable the upgrade switch before installing the 
+  maxView .deb package:
+  
+  export maxView_Upgrade=true
+  dpkg -i StorMan-*.deb
+
+  To uninstall maxView after the upgrade:
+  
+  export maxView_Upgrade=false
+  dpkg -r storman
+
+3.8 Bootable USB Image Security Warnings
+When running maxView Storage Manager from the bootable USB image, you may be 
+prompted with one or more with security warnings before maxView launches. In 
+each case, acknowledge the warning and continue.
+
+3.9 RAW Device Setup (Series 6, 7, 8 Only)
+On Adaptec Series 7 and Adaptec Series 8 controllers, a RAW Pass Through 
+device is analogous to a JBOD, supported by Adaptec Series 6 controllers and 
+older. Any drive without Adaptec RAID metadata is exposed to the OS as a RAW 
+Pass Through device. To remove the Adaptec metadata and convert the drive to a 
+RAW device, use the Uninitialize command in maxView Storage Manager; any 
+existing data on the drive is destroyed. (You can also run uninit from the 
+BIOS or ARCCONF.) For more information about working with RAW devices, see 
+'controller modes' in the CLI User's Guide, and BIOS 'general settings' in the 
+RAID Controller Installation and User's Guide.
+
+3.10 maxView Plugin for VMware vSphere Web Client
+The maxView Plugin for VMware vSphere Web Client is supported on VMware 5.5 
+and 6.0.
+
+--------------------------------------------------------------------
+
+Chapter 4. Known Limitations
+
+4.1 Global Limitations
+
+4.1.1 Dual-Controller Systems
+In dual-controller systems, the controller order in maxView Storage Manager 
+and the BIOS differs. Example: with an Adaptec 72405 and 7805 installed, the 
+BIOS reports the 72405 as controller 1 and the 7805 as controller 2; in the 
+GUI, the controller order is reversed.
+
+4.1.2 Email Notifications
+On Linux systems, we recommend adding the SMTP host name and the system IP 
+address, to the /etc/hosts file. Doing so ensures that email notifications 
+will succeed if you specify the email server in maxView Storage Manager by 
+host name. Otherwise, email notifications (including test messages) may fail 
+if the DNS is unable to resolve the host name.
+WORKAROUND: Specify the email server in maxView Storage Manager by IP address.
+
+4.1.3 SGPIO Enclosures
+In this release, maxView Storage Manager does not show connector information 
+for SGPIO enclosures.
+
+4.1.4 Non-RAID Mode Controllers
+maxView Storage Manager can "see" RAID controllers operating in HBA mode, 
+Auto-Volume mode, and Simple Volume mode (Adaptec Series 7, Adaptec Series 8, 
+Smart Family controllers only). However, to change the controller mode on 
+Adaptec Series 7/8 controllers, you must use ARCCONF or the BIOS. With Adaptec 
+Smart-Family controllers, you can also change the controller mode with maxView 
+Storage Manager.
+
+4.1.5 Browser Issues
+* To run maxView Storage Manager on the supported browsers, Javascript must be 
+  enabled.
+* With Ubuntu Linux, Firefox 46/47 has alignment problems in some parts of the 
+  maxView GUI.
+  WORKAROUND: Upgrade to Firefox 48.
+* Due to a certificate bug in Firefox 31.x, maxView login may fail on RHEL 
+  systems with a "Secure Connection" error. (Firefox 31.1 is the default 
+  browser on RHEL 6.6; on RHEL 7.1, it is 31.4.)
+  WORKAROUND: Upgrade to the latest Firefox version.
+* With the default Security setting in Microsoft Internet Explorer 10 and 11, 
+  you may be unable to login to maxView Storage Manager or experience certain 
+  GUI display issues in the maxView online Help system.
+  WORKAROUND: Change the default Security setting from High (or Medium-High) 
+  to Medium. Alternative: add the GUI IP address to the trusted sites list.
+* With Google Chrome, the scrollbar resets itself to the top after selecting a 
+  drive in the Logical Drive wizard. To select another drive, you must scroll 
+  back down to the drive location.
+* With Microsoft Internet Explorer 10, the controller firmware update wizard 
+  does not show the f/w update file name when the upload completes. To refresh 
+  the display, click Next then Back.
+* We do not recommend using multiple browsers simultaneously on the same 
+  maxView instance. Doing so may cause display issues or freezes; to restore 
+  maxView, refresh the display by pressing F5.
+
+4.1.6 Remote System Access on Linux and Windows
+To avoid remote system access failures from Linux and Windows clients running 
+maxView Storage Manager, check and update one or all of the following system 
+and network settings:
+
+Windows:
+* Ensure that the DNS server information is properly configured
+
+RHEL/Linux:
+Set server.properties file permissions to at least read-only at all levels
+1. Stop all maxView services.
+2. Set the Permissions of server.properties file to read and write or read-
+   only at all levels (Owner, Group and Others). Apply and close.
+3. Restart all services in the given order - cim, agent, tomcat
+4. Now try to remote login to this system from any other system
+
+4.1.7 RAID 10 Segment Order
+maxView Storage Manager and the Ctrl-A BIOS report the wrong segment order for 
+RAID 10s, regardless of the order in which the drives are selected.
+
+Example 1: Create RAID 10 with 2 SDDs and 2 HDDs in maxView Storage Manager:
+(1a) ARCCONF and maxView Storage Manager see the following RAID segment order:
+                Device 2 (S1)
+                Device 1 (H2)
+                Device 3 (S2)
+                Device 0 (H1)
+   
+(1b) the BIOS/CTRL-A sees the following RAID segment order:
+                Device 2 (S1)
+                Device 1 (H2)
+                Device 0 (H1)
+                Device 3 (S2)
+   
+(1c) the correct and expected RAID segment order is:
+                Device 2 (S1)
+                Device 0 (H1)
+                Device 3 (S2)
+                Device 1 (H2)
+
+Example 2: Create RAID 10 with 2 SDDs and 2 HDDs with ARCCONF:
+(2a) the BIOS/CTRL-A sees the following RAID segment order:
+                      Device 0 (H1)
+                      Device 2 (S1)
+                      Device 1 (H2)
+                      Device 3 (S2)
+  
+(2b) ARCCONF and maxView Storage Manager see the correct RAID segment order:
+                      Device 2 (S1)
+                      Device 0 (H1)
+                      Device 3 (S2)
+                      Device 1 (H2)
+
+4.1.8 RAID 10 Rebuild Order
+With a degraded RAID 10 logical drive, the drive is rebuilt one leg at a time, 
+not in parallel.
+
+4.1.9 Locate Logical Drive Blink LED
+In maxView Storage Manager, Locate Logical Drive continues to blink the LED 
+for a pulled physical drive in the array after the locate action is stopped. 
+(For unpulled drives, the blinking stops.) This issue is not seen with 
+ARCCONF.
+
+4.1.10 ARCCONF Backward Compatibility
+ARCCONF is backward compatible with older Adaptec controller models. As a 
+result, the ARCCONF user's guide and online help show command options that are 
+not supported by newer Adaptec controllers, like the Adaptec Series 7 and 
+Adaptec Series 8 or later products.
+Example: With ARCCONF SETMAXCACHE, Adaptec Series 7 and Series 8 controllers 
+do not support ADDTOPOOL or REMOVEFROMPOOL.
+
+4.1.11 Updating Hard Disk Firmware on VMware Guest OS
+Updating the firmware for a SAS hard disk drive with ARCCONF/maxView can crash 
+(PSOD) the VMware Guest OS. This issue is seen with SAS hard drives only; with 
+SATA drives, the firmware update completes successfully.
+
+4.1.12 Hot Swap Issues on VMware CentOS Guest OS
+Due to a limitation with the VMware CentOS Guest OS network configuration, 
+maxView Storage Manager does not show newly added or removed hot swap drives. 
+(ARCCONF sees the configuration change but maxView does not.)
+WORKAROUND: (1) reboot the system or restart maxView services; (2) adjust the 
+network configuration; contact Adaptec Support for more information.
+
+4.1.13 Enclosure Status Reporting
+Enclosure status, in maxView Storage Manager, is event-driven. As a result, 
+enclosures can have a "Degraded" status even if related resources (fan, 
+temperature, power) are performing normally (Optimal status). For instance, 
+the Enclosure status changes to "Degraded" if the system reports an "Enclosure 
+device not responding ..." event, even if other sensor values are normal.
+
+4.1.14 PHY Status on Enclosure Backplanes
+In the Controller Properties window, maxView Storage Manager shows the 
+Connector Info as "unknown" for all PHYs on an enclosure-based backplane (for 
+instance, a backplane attached to connector 1).
+
+4.1.15 Special Characters in Logical Device Names
+Special characters are permitted in logical device names in maxView Storage 
+Manager, the BIOS, and ARCCONF. However, with Linux ARCCONF (create, setname), 
+special characters must be "escaped" to ensure proper interpretation. For 
+example:  ARCCONF SETNAME 1 LOGICALDRIVE 1 arc_ldrive%\$12\&amp;
+
+4.1.16 Speaker Status on SuperMicro SAS2X28 Enclosures
+SuperMicro SAS2X28 enclosures do not propagate the speaker status to maxView 
+Storage Manager. As a result, maxView always displays the speaker status as 
+Off.
+
+4.1.17 Online Help Issues
+* Help from the Express Configuration wizard opens the Custom Configuration 
+  help panel.
+  WORKAROUND: Open the Express Configuration Help panel from the Help System 
+  TOC pane.
+* When opening the maxView Storage Manager help from a remote Linux system 
+  (eg, over a VPN), the help window may fail to open with a 'can't establish 
+  connection to server' message.
+  WORKAROUND: Replace 127.0.0.1:8443 in the URL with <system_ip_address>:8443
+* In IE11, topics in the help may display with a 'Topics Not Found' message 
+  when their corresponding links are clicked in the navigation pane of the 
+  help.
+  WORKAROUND: Click on the "Add" browser prompt to add certification to view 
+  the content.
+
+4.1.18 Broadcasting Alerts About Status and Activity
+This feature is not supported by the maxView Storage Manager or ARCCONF and 
+has been removed from the product documentation.
+
+4.1.19 User-Specified Archive Path
+While executing the savesupportarchive command where a user-specified path 
+exists, ARCCONF will instead place the logs under the /var/log/ directory.
+
+4.1.20 Clear Configuration Status After Re-Insertion
+After removing a RAID member and then clearing the controller configuration, 
+maxView Storage Manager recovers the configuration for all RAID volumes and 
+physical drives when the offline drive is re-inserted and the OS restarted. By 
+design, RAID members store metadata about all other virtual devices. This 
+allows the controller to recover the configuration from the re-inserted drive, 
+even though the configuration was previously cleared.
+
+4.1.21 Configuration Changes in Device Manager
+After disabling/enabling the Microsemi Adaptec controller in the Device 
+Manager, it can take up to 10 minutes for maxView Storage Manager to detect 
+the configuration change.
+WORKAROUND: Use the Refresh link in the maxView GUI to update the 
+configuration.
+
+4.2 Limitations for Series 6, 7, 8 Controllers
+
+4.2.1 RAID-Level Migrations
+* The following RAID-level migrations (RLM) are supported in this release:
+  * RAID 0 to RAID 5
+  * RAID 0 to RAID 10
+  * RAID 5 to RAID 6
+  * RAID 6 to RAID 5
+  * RAID 10 to RAID 5
+  * RAID 5 to RAID 10
+  * RAID 1 to RAID 5
+  * SIMPLE VOLUME to RAID 1
+  * RAID 1 to SIMPLE VOLUME
+* When migrating a Simple Volume to RAID 1, maxView Storage Manager reports 
+  the logical drive state as Impacted (rather than Reconfiguring); this is 
+  normal.
+* We do not recommend performing a RAID-level migration or Online Capacity 
+  Expansion (OCE) on a logical drive with maxCache SSD caching enabled.
+  NOTE: maxView Storage Manager grays out the options for logical drives with  
+  maxCache enabled. ARCCONF terminates the task.
+* Always allow a RAID-level migration to complete before creating a support 
+  archive file. Otherwise, the support archive will include incorrect 
+  partition information. Once the migration is complete, the partition 
+  information will be reported correctly.
+
+4.2.2 maxCache Device Migration
+Only one maxCache Device is supported per controller. Moving the maxCache 
+Device (all underlying SSDs) from one controller to another (assuming both 
+controllers support maxCache) is supported only if (1) the new controller does 
+not have a maxCache Device or any other maxCache Device with a conflicting 
+device number and (2) only after a clean shutdown on the old controller.
+
+4.2.3 ARCCONF maxCache Device Size Issue
+ARCCONF supports >2TB maxCache Devices if you create the device with the 'max' 
+parameter. However, the functional limit for the maxCache Device is 2TB, which 
+is also the limit in maxView Storage Manager.
+
+4.2.4 Power Management Issues
+* Power management is not supported on FreeBSD.
+* Capturing support logs from maxView or ARCCONF will spin up drives when 
+  power management is active. This behavior is by design.
+* The Logical Drive Creation wizard no longer includes the option to enable 
+  power management settings.
+  WORKAROUND: Enable power management for the logical drive from the Set 
+  Properties window.
+
+4.2.5 Verify/Verify with Fix
+* Incremental progress percentage information in SNMP is not updated for the 
+  Verify/Verify_Fix operations. Task progress shows 0% until complete, then 
+  100%.
+* In maxView Storage Manager and ARCCONF, the Verify_Fix operation is NOT 
+  available when:
+  1. The logical drive has a non-redundant RAID level.
+  2. Other tasks are in progress on the logical drive.
+  3. The logical drive is in a non-optimal or impacted state.
+
+4.2.6 ATA Secure Erase
+In ARCCONF, the ATA Secure Erase operation cannot be aborted. Once started, it 
+continues to completion.
+In maxView Storage Manager, the drive is locked during ATA Secure Erase. To 
+recover, use the ARCCONF ATAPASSWORD CLEAR <passwd> command; the default 
+password is 'pmc-sierra'.
+NOTE: ATA Secure Erase is also available in the Ctrl-A BIOS.
+
+4.2.7 Series 6 Controller Issues
+The following issues are seen only with Microsemi Adaptec Series 6 RAID 
+controllers:
+* In maxView Storage Manager, the Preserve Cache option on the Set Properties 
+  window is not supported on Series 6 RAID controllers. Attempting to set this 
+  option for the Series 6 controller fails.
+* Renaming a RAID volume disables the write-cache (if enabled). You cannot re-
+  enable the write-cache in maxView Storage Manager.
+  WORKAROUND: Use ARCCONF to enable the write-cache.
+* In a VMware Guest OS under VMware 5.x, maxView Storage Manager and ARCCONF 
+  do not detect existing logical drive partitions. As a result, attempting to 
+  delete, clear, or erase the logical drive may fail.
+* On Series 6 controllers, maxView Storage Manager deletes partitioned JBODs 
+  without issuing a warning message.
+* Series 6 controllers do not support the ARCCONF GETPERFORM command.
+
+4.2.8 Simple Volume Support
+* In this release, you can create a maximum of 128 Simple Volumes in maxView 
+  Storage Manager, ARCCONF, or the BIOS.
+* When a Simple Volume fails, the status remains unchanged after drive 
+  replacement.
+  WORKAROUND: Manually delete the Simple Volume to remove it.
+
+4.2.9 Auto-Volume Support
+* Changing a controller into Auto-Volume mode (ARCCONF/BIOS) is not supported 
+  if the configuration includes any logical device type other than Simple 
+  Volume, including a maxCache Device. The mode switch from RAID mode to Auto-
+  Volume mode is blocked if any other type of logical volume exists (including 
+  maxCache). After switching to Auto-Volume mode, you can create and delete 
+  Simple Volumes only in maxView Storage Manager and ARCCONF.
+* In Auto-Volume mode, only the first 128 RAW drives are converted to Simple 
+  Volumes; the rest of the RAW drives remain unchanged. If you uninitialize a 
+  Ready drive while the controller is in Auto-Volume mode, the firmware 
+  converts the drive automatically until the Simple Volume count reaches the 
+  maximum.
+
+4.2.10 Hot-Removing Disk Drives on Xenserver Guest OS
+XenServer does not support "hot-removal" of disk drives from a partitioned 
+logical drive. As a result, if you hot remove a disk from a logical drive, the 
+Guest OS becomes inaccessible because the drive partition remains visible to 
+the OS instead of being cleared.
+WORKAROUND: Reboot the XenServer host, detach the failed partition, then 
+restart the VM.
+
+4.2.11 Viewing Logical Drive Details After Re-Insertion
+If you remove/re-insert a RAID member when the controller's "Automatic 
+Failover" property is enabled and there is no hot spare configured/protecting 
+the logical device, you must click on the Refresh link in maxView Storage 
+Manager to view the proper data of the re-inserted drive and RAID volume.
+
+4.3. Limitations for Smart Family Controllers
+
+4.3.1 SES Passthrough Commands to Expanders
+SES passthrough commands to expanders fail.
+
+4.3.2 Firmware Upgrade Issues
+For systems using Adaptec HBA 1000 with an Adaptec SAS Expander 82885T card, 
+where the ARCCONF utility is used to upgrade the expander firmware, ARCCONF 
+may crash if 64-bit chunk sizes are used.
+WORKAROUND: Use 32-bit chunk sizes to upgrade/downgrade the expander firmware.
+
+4.3.3 Mount Point Information with MPIO Support
+When Multipath I/O (MPIO) is enabled in Windows, mount point information is 
+not available in maxView or ARCCONF.
+
+4.3.4 Locate Physical Disk LED Behavior
+Since the locate commands are executed at the physical device level, the LED 
+that is used to locate physical disks in an array when using ARCCONF/maxView 
+will continue to blink the physical device(s) even after deleting the array.
+
+--------------------------------------------------------------------
+
+Copyright (c) 2016 Microsemi Corporation. All rights reserved. Microsemi and 
+the Microsemi logo are trademarks of Microsemi Corporation. All other 
+trademarks and service marks are the property of their respective owners.
+
+Microsemi Corporation (Nasdaq: MSCC) offers a comprehensive portfolio of 
+semiconductor and system solutions for communications, defense and security, 
+aerospace, and industrial markets. Products include high-performance and 
+radiation-hardened analog mixed-signal integrated circuits, FPGAs, SoCs, and 
+ASICs; power management products; timing and synchronization devices and 
+precise time solutions; voice processing devices; RF solutions; discrete 
+components; enterprise storage and communications solutions; security 
+technologies and scalable anti-tamper products; Ethernet solutions; Power-
+over-Ethernet ICs and midspans; custom design capabilities and services. 
+Microsemi is headquartered in Aliso Viejo, California and has approximately 
+4,800 employees world-wide. Learn more at www.microsemi.com.
+
+PMC-2153191, Issue 3
+
+Microsemi makes no warranty, representation, or guarantee regarding the 
+information contained herein or the suitability of its products and services 
+for any particular purpose, nor does Microsemi assume any liability whatsoever 
+arising out of the application or use of any product or circuit. The products 
+sold hereunder and any other products sold by Microsemi have been subject to 
+limited testing and should not be used in conjunction with mission-critical 
+equipment or applications. Any performance specific ations are believed to be 
+reliable but are not verified, and Buyer must conduct and complete all 
+performance and other testing of the products, alone and together with, or 
+installed in, any end-products. Buyer shall not rely on any data and 
+performance specifications or parameters provided by Microsemi. It is the 
+Buyer's responsibility to independently determine suitability of any products 
+and to test and verify the same. The information provided by Microsemi 
+hereunder is provided "as is, where is" and with all faults, and the entire 
+risk associated with such information is entirely with the Buyer. Microsemi 
+does not grant, explicitly or implicitly, to any party any patent rights, 
+licenses, or any other IP rights, whether with regard to such information 
+itself or anything described by such information. Information provided in this 
+document is proprietary to Microsemi, and Microsemi reserves the right to make 
+any changes to the information in this document or to any products and 
+services at any time without notice.
+
+The technology discussed in this document may be protected by one or more 
+patent grants.

amd64/7.31/README.TXT

@@ -0,0 +1,678 @@
+--------------------------------------------------------------------
+README.TXT
+
+Adaptec Storage Manager (ASM)
+
+as of May 7, 2012
+--------------------------------------------------------------------
+Please review this file for important information about issues
+and erratas that were discovered after completion of the standard
+product documentation. In the case of conflict between various
+parts of the documentation set, this file contains the most
+current information.
+
+The following information is available in this file:
+
+   1. Software Versions and Documentation
+      1.1   Adaptec Storage Manager
+      1.2   Documentation
+   2. Installation and Setup Notes
+      2.1   Supported Operating Systems
+      2.2   Minimum System Requirements
+      2.3   General Setup Notes
+      2.4   Linux Setup Notes 
+      2.5   Debian Linux Setup Notes
+   3. General Cautions and Notes
+      3.1   General Cautions
+      3.2   General Notes
+   4. Operating System-Specific Issues and Notes
+      4.1   Windows - All
+      4.2   Windows 64-Bit
+      4.3   Linux
+      4.4   Debian and Ubuntu
+      4.5   FreeBSD
+      4.6   Fedora and FreeBSD
+      4.7   Linux and FreeBSD
+      4.8   VMware
+   5. RAID Level-Specific Notes
+      5.1   RAID 1 and RAID 5 Notes
+      5.2   RAID 10 Notes
+      5.3   RAID x0 Notes
+      5.4   RAID Volume Notes
+      5.5   JBOD Notes
+      5.6   Hybrid RAID Notes
+      5.7   RAID-Level Migration Notes
+   6. Power Management Issues and Notes
+   7. "Call Home" Issues and Notes
+   8. ARCCONF Issues and Notes   
+   9. Other Issues and Notes
+
+--------------------------------------------------------------------
+1. Software Versions and Documentation
+
+   1.1. Adaptec Storage Manager Version 7.3.1, ARCCONF Version 7.3.1
+
+   1.2. Documentation on this DVD
+
+        PDF format*:
+
+        -  Adaptec Storage Manager User's Guide
+        -  Adaptec RAID Controller Command Line Utility User's Guide
+        
+        *Requires Adobe Acrobat Reader 4.0 or later
+        
+        HTML and text format:
+        
+        -  Adaptec Storage Manager Online Help        
+        -  Adaptec Storage Manager README.TXT file
+        
+--------------------------------------------------------------------
+2. Installation and Setup Notes
+  
+   - The Adaptec Storage Manager User's Guide contains complete installation
+     instructions for the Adaptec Storage Manager software. The Adaptec
+     RAID Controllers Command Line Utility User's Guide contains 
+     complete installation instructions for ARCCONF, Remote ARCCONF,
+     and the Adaptec CIM Provider. The Adaptec RAID Controllers 
+     Installation and User's Guide contains complete installation
+     instructions for Adaptec RAID controllers and drivers.
+     
+   2.1 Supported Operating Systems
+             
+     - Microsoft Windows*:
+
+       o Windows Server 2008, 32-bit and 64-bit
+       o Windows Server 2008 R2, 64-bit
+       o Windows SBS 2011, 32-bit and 64-bit
+       o Windows Storage Server 2008 R2, 32-bit and 64-bit
+       o Windows Storage Server 2011, 32-bit and 64-bit
+       o Windows 7, 32-bit and 64-bit
+     
+     *Out-of-box and current service pack   
+
+     - Linux:
+
+       o Red Hat Enterprise Linux 5.7, 6.1, IA-32 and x64
+       o SuSE Linux Enterprise Server 10, 11, IA-32 and x64     
+       o Debian Linux 5.0.7, 6.0 IA-32 and x64       
+       o Ubuntu Linux 10.10, 11.10, IA-32 and x64       
+       o Fedora Linux 14, 15, 16 IA-32 and x64
+       o Cent OS 5.7, 6.2, IA-32 and x64
+       o VMware ESXi 5.0, VMware ESX 4.1 Classic (Agent only)
+
+     - Solaris:
+     
+       o Solaris 10, 
+       o Solaris 11 Express      
+             
+     - FreeBSD:
+      
+       o FreeBSD 7.4, 8.2
+           
+   2.2 Minimum System Requirements
+
+     o  Pentium Compatible 1.2 GHz processor, or equivalent
+     o  512 MB RAM
+     o  135 MB hard disk drive space
+     o  Greater than 256 color video mode   
+  
+   2.3 General Setup Notes 
+
+   - You can configure Adaptec Storage Manager settings on other
+     servers exactly as they are configured on one server. To
+     replicate the Adaptec Storage Manager Enterprise view tree   
+     and notification list, do the following:
+
+     1.  Install Adaptec Storage Manager on one server.
+
+     2.  Start Adaptec Storage Manager. Using the 'Add remote system' 
+         action, define the servers for your tree.
+
+     3.  Open the Notification Manager. Using the 'Add system' 
+         action, define the notification list.
+
+     4.  Exit Adaptec Storage Manager.
+
+     5.  Copy the following files onto a diskette from the directory
+         where the Adaptec Storage Manager is installed:
+
+         RaidMSys.ser --> to replicate the tree
+         RaidNLst.ser --> to replicate the notification list
+         RaidSMTP.ser --> to replicate the SMTP e-mail notification list
+         RaidJob.ser  --> to replicate the jobs in the Task Scheduler
+
+     6.  Install Adaptec Storage Manager on the other servers.
+
+     7.  Copy the files from the diskette into the directory where
+         Adaptec Storage Manager is installed on the other servers.
+
+   2.4 Linux Setup Notes
+   
+   - Because the RPM for Red Hat Enterprise Linux 5 is unsigned, the
+     installer reports that the package is "Unsigned, Malicious Software". 
+     Ignore the message and continue the installation.
+
+   - To run Adaptec Storage Manager under Red Hat Enterprise Linux for 
+     x64, the Standard installation with "Compatibility Arch Support"
+     is required. 
+
+   - To install Adaptec Storage Manager on Red Hat Enterprise Linux,
+     you must install two packages from the Red Hat installation CD:
+     
+     o  compat-libstdc++-7.3-2.96.122.i386.rpm
+     o  compat-libstdc++--devel-7.3-2.96.122.i386.rpm
+                   
+     NOTE:  The version string in the file name may be different 
+            from above. Be sure to check the version string on the 
+            Red Hat CD.
+     
+     For example, type:
+            
+     rpm --install /mnt/compat-libstdc++-7.3-2.96.122.i386.rpm
+            
+     where mnt is the mount point of the CD-ROM drive.            
+
+   - To install Adaptec Storage Manager on Red Hat Enterprise Linux 5,
+     you must install one of these packages from the Red Hat
+     installation CD:
+       
+     o  libXp-1.0.0-8.i386.rpm    (32-Bit)
+     o  libXp-1.0.0-8.x86.rpm     (64-Bit)
+
+   - To install Adaptec Storage Manager on SuSE Linux Enterprise  
+     Desktop 9, Service Pack 1, for 64-bit systems, you must install    
+     two packages from the SuSE Linux installation CD:
+     
+     - liblcms-devel-1.12-55.2.x86_64.rpm
+     - compat-32bit-9-200502081830.x86_64.rpm
+                   
+     NOTE:  The version string in the file name may be different 
+            from above. Be sure to check the version string on the 
+            installation CD.
+         
+   - To enable ASM's hard drive firmware update feature on RHEL 64-bit
+     systems, you must ensure that the "sg" module is loaded in the  
+     kernel. To load the module manually (if it is not loaded already),  
+     use the command "modprobe sg".                 
+   
+   2.5 Debian Linux Setup Notes
+
+   - You can use the ASM GUI on Debian Linux 5.x only if you install
+     the GNOME desktop. Due to a compatibility issue with X11, the
+     default KDE desktop is not supported in this release.
+          
+   - To ensure that the ASM Agent starts automatically when Debian
+     is rebooted, you must update the default start and stop values
+     in /etc/init.d/stor_agent, as follows:
+     
+     ·[Original]
+     # Default-Start:    2 3 5
+     # Default-Stop:     0 1 2 6
+     
+     ·[Modification]
+     # Default-Start:    2 3 4 5
+     # Default-Stop:     0 1 6
+     
+     To activate the changes, execute 'insserv stor_agent', as root.
+                
+--------------------------------------------------------------------
+3. Adaptec Storage Manager General Cautions and Notes
+
+   3.1 General Cautions
+   
+   - This release supports a maximum of 8 concurrent online capacity 
+     expansion (OCE) tasks in the RAID array migration wizard.         
+
+   - While building or clearing a logical drive, do not remove and 
+     re-insert any drive from that logical drive. Doing so may cause
+     unpredictable results.
+
+   - Do not move disks comprising a logical drive from one controller 
+     to another while the power is on. Doing so could cause the loss of
+     the logical drive configuration or data, or both. Instead, power 
+     off both affected controllers, move the drives, and then restart.
+
+   - When using Adaptec Storage Manager and the CLI concurrently, 
+     configuration changes may not appear in the Adaptec Storage 
+     Manager GUI until you refresh the display (by pressing F5).
+
+   3.2 General Notes
+
+   - Adaptec Storage Manager requires the following range of ports
+     to be open for remote access: 34570-34580 (TCP), 34570 (UDP),
+     34577-34580 (UDP).
+     
+   - Adaptec Storage Manager generates log files automatically to
+     assist in tracking system activity.  The log files are
+     created in the directory where Adaptec Storage Manager is
+     installed.  
+   
+     o RaidEvt.log  - Contains the information reported in 
+                      Adaptec Storage Manager event viewer for all
+                      local and remote systems.
+
+     o RaidEvtA.log - Contains the information reported in 
+                      Adaptec Storage Manager event viewer for the
+                      local system.
+                       
+     o RaidNot.log  - Contains the information reported in the
+                      Notification Manager event viewer.
+                                              
+     o RaidErr.log  - Contains Java messages generated by 
+                      Adaptec Storage Manager.
+                    
+     o RaidErrA.log - Contains Java messages generated by the
+                      Adaptec Storage Manager agent.
+                      
+     o RaidCall.log - Contains the information reported when 
+                      statistics logging is enabled in ASM.
+                      
+     Information written to these files is appended to the existing
+     files to maintain a history. However, when an error log file
+     reaches a size of 5 Mbytes, it is copied to a new file with 
+     the extension .1 and the original (that is, the .LOG file) is 
+     deleted and recreated. For other log files, a .1 file is created
+     when the .LOG file reaches a size of 1 Mbyte. If a .1 file already 
+     exists, the existing .1 file is destroyed.
+
+   - In the Event viewer, Adaptec Storage Manager reports both the 
+     initial build task for a logical drive and a subsequent Verify/Fix
+     as a "Build/Verify" task.
+   
+   - When displaying information about a physical device, the device, 
+     vendor and model information may be displayed incorrectly.
+
+   - After using a hot spare to successfully rebuild a redundant 
+     logical drive, Adaptec Storage Manager will continue to  
+     show the drive as a global hot spare. To remove the hot spare 
+     designation, delete it in Adaptec Storage Manager.
+          
+--------------------------------------------------------------------
+4. Operating System-Specific Issues and Notes
+
+   4.1 Windows - All
+             
+   - The Java Virtual Machine has a problem with the 256-color 
+     palette. (The Adaptec Storage Manager display may be distorted 
+     or hard to read.) Set the Display Properties Settings to a  
+     color mode with greater than 256 colors.      
+  
+   - When you shut down Windows, you might see the message 
+     "unexpected shutdown". Windows displays this message if the
+     Adaptec Storage Manager Agent fails to exit within 3 seconds. 
+     It has no effect on file I/O or other system operations and can
+     be ignored.        
+
+   4.2 Windows 64-Bit
+        
+   - Adaptec RAID controllers do not produce an audible alarm on the 
+     following 64-bit Windows operating systems:
+
+     o  Windows Server 2003 x64 Edition (all versions)
+                 
+   4.3 Linux
+
+   - When you delete a logical drive, the operating system can no longer 
+     see the last logical drive. WORKAROUND: To allow Linux to see the  
+     last logical drive, restart your system.
+
+   - The controller does not support attached CD drives during OS 
+     installation.    
+                                         
+   - On certain versions of Linux, you may see messages concerning font 
+     conversion errors. Font configuration under X-Windows is a known 
+     JVM problem. It does not affect the proper operation of the  
+     Adaptec Storage Manager software. To suppress these messages,  
+     add the following line to your .Xdefaults file:
+       
+     stringConversionWarnings: False
+     
+   4.4 Debian and Ubuntu
+
+   - To create logical drives on Debian and Ubuntu installations, you
+     must log in as root. It is not sufficient to start ASM with the
+     'sudo /usr/StorMan/StorMan.sh' command (when not logged in as 
+     root). WORKAROUND: To create logical drives on Ubuntu when not
+     logged in as root, install the package 'sudo dpkg -i storm_6.50-15645_amd64.deb'.  
+   
+   4.5 FreeBSD         
+   
+   - On FreeBSD systems, JBOD disks created with Adaptec Storage Manager
+     are not immediately available to the OS. You must reboot the  
+     system before you can use the JBOD.
+  
+   4.6 Fedora and FreeBSD
+ 
+   - Due to an issue with the Java JDialog Swing class, the 'Close' 
+     button may not appear on some Adaptec Storage Manager windows  
+     or dialog boxes under FreeBSD or Fedora Linux 15 or higher. 
+     WORKAROUND: Press ALT+F4 or right-click on the title bar, then 
+     close the dialog box from the pop-up menu. 
+
+   4.7 Linux and FreeBSD
+       
+   - If you cannot connect to a local or remote Adaptec Storage Manager  
+     installed on a Linux or FreeBSD system, verify that the TCP/IP hosts   
+     file is configured properly.
+          
+     1.  Open the /etc/hosts file.
+           
+         NOTE:  The following is an example:
+               
+                127.0.0.1 localhost.localdomain localhost matrix
+           
+     2.  If the hostname of the system is identified on the line
+         with 127.0.0.1, you must create a new host line.
+           
+     3.  Remove the hostname from the 127.0.0.1 line.
+           
+         NOTE:  The following is an example:
+               
+                127.0.0.1 localhost.localdomain localhost
+    
+     4.  On a new line, type the IP address of the system.
+           
+     5.  Using the Tab key, tab to the second column and enter the 
+         fully qualified hostname.
+               
+     6.  Using the Tab key, tab to the third column and enter the 
+         nickname for the system.
+               
+         NOTE:  The following is an example of a completed line:
+     
+                1.1.1.1 matrix.localdomain matrix
+                      
+                where 1.1.1.1 is the IP address of the server and
+                matrix is the hostname of the server.
+               
+     7.  Restart the server for the changes to take effect.   
+   
+   4.8 VMware
+           
+   - If you are unable to connect to VMware ESX Server from a 
+     remote ASM GUI, even though it appears in the Enterprise 
+     View as a remote system, most likely, some required ports
+     are open and others are not. (The VMware ESX firewall blocks 
+     most ports, by default.) Check to make sure that all ports 
+     34570 thru 34581 are opened on the ESX server. 
+
+   - After making array configuration changes in VMware, you must  
+     run the "esxcfg-rescan" tool manually at the VMware console
+     to notify the operating system of the new target characteristics
+     and/or availability. Alternatively, you can rescan from the 
+     Virtual Infrastructure Client: click on the host in the left 
+     panel, select the Configuration tab, choose "Storage Adapters", 
+     then, on the right side of the screen, click "Rescan".
+     
+   - With VMware ESX 4.1, the OS command 'esxcfg-scsidevs -a'  
+     incorrectly identifies the Adaptec ASR-5445 controller as 
+     "Adaptec ASR5800". (ASM itself identifies the controller 
+     correctly.) To verify the controller name at the OS level,  
+     use this command to check the /proc file system:
+     
+     # cat /proc/scsi/aacraid/<Node #>
+
+     where <Node #> is 1, 2, 3 etc.
+                                                                  
+--------------------------------------------------------------------
+5. RAID Level-Specific Notes
+
+   5.1 RAID 1 and RAID 5 Notes
+
+   - During a logical device migration from RAID 1 or RAID 5 to  
+     RAID 0, if the original logical drive had a spare drive
+     attached, the resulting RAID 0 retains the spare drive. 
+     Since RAID 0 is not redundant, you can remove the hot spare.
+
+   5.2 RAID 10 Notes
+
+   - If you force online a failed RAID 10, ASM erroneously shows two 
+     drives rebuilding (the two underlying member drives), not one.
+
+   - You cannot change the priority of a RAID 10 verify. Setting
+     the priority at the start of a verify has no effect. The
+     priority is still shown as high. Changing the priority of
+     a running verify on a RAID-10 changes the displayed priority
+     until a rescan is done, then the priority shows as high again.
+
+   - Performing a Verify or Verify/Fix on an RAID 10 displays the 
+     same message text in the event log: "Build/Verify started on 
+     second level logical drive of 'LogicalDrive_0.'" You may see the  
+     message three times for a Verify, but only once for a Verify/Fix.
+          
+   5.3 RAID x0 Notes
+
+   - To create a RAID x0 with an odd number of drives (15, 25, etc),
+     specify an odd number of second-level devices in the Advanced
+     settings for the array. For a 25 drive RAID 50, for instance,
+     the default is 24 drives.  
+     
+     NOTE: This differs from the BIOS utility, which creates RAID x0
+           arrays with an odd number of drives by default. 
+        
+   - After building or verifying a leg of a second-level logical drive,  
+     the status of the second-level logical drive is displayed as a  
+     "Quick Initialized" drive.
+     
+   5.4 RAID Volume Notes
+   
+   - In ASM, a failed RAID Volume comprised of two RAID 1 logical 
+     drives is erroneously reported as a failed RAID 10. A failed   
+     RAID Volume comprised of two RAID 5 logical drives is  
+     erroneously reported as a failed RAID 50.
+      
+   5.5 JBOD Notes
+     
+   - In this release, ASM deletes partitioned JBODs without issuing 
+     a warning message.
+   
+   - When migrating a JBOD to a Simple Volume, the disk must be quiescent
+     (no I/O load). Otherwise, the migration will fail with an I/O Read 
+     error. 
+
+   5.6 Hybrid RAID Notes
+
+   - ASM supports Hybrid RAID 1 and RAID 10 logical drives comprised
+     of hard disk drives and Solid State Drives (SSDs). For a Hybrid 
+     RAID 10, you must select an equal number of SSDs and HDDs in   
+     “every other drive” order, that is: SSD—HDD—SSD—HDD, and so on. 
+     Failure to select drives in this order creates a standard 
+     logical drive that does not take advantage of SSD performance. 
+     
+   5.7 RAID-Level Migration (RLM) Notes            
+  
+   - We strongly recommend that you use the default 256KB stripe 
+     size for all RAID-level migrations. Choosing a different stripe  
+     size may crash the system.
+   
+   - If a disk error occurs when migrating a 2TB RAID 0 to RAID 5
+     (eg, bad blocks), ASM displays a message that the RAID 5 drive
+     is reconfiguring even though the migration failed and no 
+     RAID-level migration task is running. To recreate the
+     logical drive, fix or replace the bad disk, delete the RAID 5
+     in ASM, then try again.
+  
+   - When migrating a RAID 5EE, be careful not to remove and re-insert
+     a drive in the array. If you do, the drive will not be included 
+     when the array is rebuilt. The migration will stop and the drive  
+     will be reported as Ready (not part of array).
+     
+     NOTE: We strongly recommend that you do not remove and re-insert  
+           any drive during a RAID-level migration. 
+
+   - When migrating a RAID 6 to a RAID 5, the migration will fail if 
+     the (physical) drive order on the target logical device differs    
+     from the source; for instance, migrating a four-drive RAID 6 to
+     a three-drive RAID 5.     
+     
+   - Migrating a RAID 5 with greater than 2TB capacity to RAID 6 or 
+     RAID 10 is not supported in this release. Doing so may crash
+     the system.
+     
+  -  When migrating from a RAID 0 to any redundant logical drive,  
+     like RAID 5 or 10, Adaptec Storage Manager shows the status as  
+     "Degraded Reconfiguring" for a moment, then the status changes  
+     to "Reconfiguring." The "Degraded" status does not appear in  
+     the event log.
+
+   - The following RAID-level migrations and online capacity 
+     expansions (OCE) are NOT supported:
+     
+     o RAID 50 to RAID 5 RLM
+     o RAID 60 to RAID 6 RLM
+     o RAID 50 to RAID 60 OCE
+
+   - During a RAID-level migration, ASM and the BIOS utility show
+     different RAID levels while the migration is in progress. ASM shows
+     the target RAID level; the BIOS utility shows the current RAID level.
+     
+   - If a disk error occurs during a RAID-level migration (eg, bad blocks),   
+     the exception is reported in the ASM event viewer (bottom pane)
+     and in the support archive file (Support.zip, Controller 1 logs.txt), 
+     but not in the main ASM Event Log file, RaidEvtA.log.   
+      
+   - Always allow a RAID-level migration to complete before gathering
+     support archive information in Support.zip. Otherwise, the Support.zip 
+     file will include incorrect partition information. Once the RLM is 
+     complete, the partition information will be reported correctly.     
+     
+--------------------------------------------------------------------
+6. Power Management Issues and Notes
+
+   - You must use a compatible combination of Adaptec Storage Manager  
+     and controller firmware and driver software to use the power  
+     management feature. All software components must support power
+     management. You can download the latest controller firmware 
+     and drivers from the Adaptec Web site at www.adaptec.com.
+ 
+   - Power management is not supported under FreeBSD.
+   
+   - Power management settings apply only to logical drives in the 
+     Optimal state. If you change the power settings on a Failed 
+     logical drive, then force the drive online, the previous 
+     settings are reinstated.
+     
+   - After setting power values for a logical drive in ARCCONF, the
+     settings are not updated in the Adaptec Storage Manager GUI.
+   
+--------------------------------------------------------------------
+7. "Call Home" Issues and Notes
+    
+   - The Call Home feature is not supported in this release. To gather  
+     statistics about your system for remote analysis, enable statistics   
+     logging in ASM, then create a Call Home Support Archive. For more   
+     information, see the user's guide.     
+     
+--------------------------------------------------------------------
+8. ARCCONF Issues and Notes
+
+   - With VMware ESX 4.1, you cannot delete a logical drive 
+     with ARCCONF. WORKAROUND: Connect to the VMware machine from a 
+     remote ASM GUI, then delete the logical drive.
+
+   - With Linux kernel versions 2.4 and 2.6, the ARCCONF 
+     DELETE <logical_drive> command may fail with a Kernel Oops 
+     error message. Even though the drives are removed from the 
+     Adaptec Storage Manager GUI, they may not really be deleted. 
+     Reboot the controller; then, issue the ARCCONF DELETE command
+     again. 
+     
+--------------------------------------------------------------------
+9. Other Issues and Notes
+                  
+   - Some solid state drives identify themselves as ROTATING media.
+     As a result, these SSDs:
+     
+     o Appear as SATA drives in the ASM Physical Devices View
+     o Cannot be used as Adaptec maxCache devices
+     o Cannot be used within a hybrid RAID array (comprised of 
+       SSDs and hard disks)
+
+   - The blink pattern on Adaptec Series 6/6Q/6E/6T controllers differs  
+     from Series 2 and Series 5 controllers:
+   
+     o When blinking drives in ASM, the red LED goes on and stays solid; 
+       on Series 2 and 5 controllers, the LED blinks on and off.
+     
+     o When failing drives in ASM (using the 'Set drive state to failed' 
+       action), the LED remains off; on Series 2 and 5 controllers, the 
+       LED goes on and remains solid.    
+
+   - Cache settings for RAID Volumes (Read cache, Write cache, maxCache)
+     have no effect. The cache settings for the underlying logical
+     devices take priority.
+
+   - On rare occasions, ASM will report invalid medium error counts on 
+     a SATA hard drive or SSD. To correct the problem, use ARCCONF to  
+     clear the device counts. The command is:
+
+     arcconf getlogs <Controller_ID> DEVICE clear
+      
+   - On rare occasions, ASM lists direct-attached hard drives and SSDs
+     as drives in a virtual SGPIO enclosure. Normally, the drives are  
+     listed in the Physical Devices View under ports CN0 and CN1.
+
+   - Hard Drive Firmware Update Wizard:
+          
+     o Firmware upgrade on Western Digital WD5002ABYS-01B1B0 hard drives 
+       is not supported for packet sizes below 2K (512/1024).       
+
+     o After flashing the firmware of a Seagate Barracuda ES ST3750640NS  
+       hard drive, you MUST cycle the power before ASM will show the new
+       image. You can pull out and re-insert the drive; power cycle the 
+       enclosure; or power cycle the system if the drive is attached directly.          
+     
+   - Secure Erase:
+   
+     o If you reboot the system while a Secure Erase operation is in  
+       progress, the affected drive may not be displayed in Adaptec 
+       Storage Manager or other Adaptec utilities, such as the ACU.
+   
+     o You can perform a Secure Erase on a Solid State Drive (SSD) to
+       remove the metadata. However, the drive will move to the Failed 
+       state when you reboot the system. To use the SSD, reboot to 
+       the BIOS, then initialize the SSD. After initialization, the SSD 
+       will return to the Ready state. (A SSD in the Failed state cannot
+       be initialized in ASM.)
+     
+   - The Repair option in the ASM Setup program may fail to fix a
+     corrupted installation, depending on which files are affected.
+     The repair operation completes successfully, but the software
+     remains unfixed. 
+
+   - Adaptec Storage Manager may fail to exit properly when you create 
+     64 logical devices in the wizard. The logical devices are still
+     created, however.      
+
+   - The "Clear logs on all controllers" action does not clear events
+     in the ASM Event Viewer (GUI). It clears device events, defunct 
+     drive events, and controller events in the controllers' log files.
+     To clear events in the lower pane of the GUI, select Clear   
+     configuration event viewer from the File menu.
+     
+   - Stripe Size Limits for Large Logical Drives:
+  
+     The stripe size limit for logical drives with more than 8 hard     
+     drives is 512KB; for logical drives with more than 16 hard 
+     drives it is 256KB.
+     
+   - Agent Crashes when Hot-Plugging an Enclosure:
+   
+     With one or more logical drives on an enclosure, removing
+     the enclosure cable from the controller side may crash 
+     the ASM Agent.
+     
+--------------------------------------------------------------------
+(c) 2012 PMC-Sierra, Inc. All Rights Reserved. 
+
+This software is protected under international copyright laws and 
+treaties. It may only be used in accordance with the terms 
+of its accompanying license agreement.
+
+The information in this document is proprietary and confidential to
+PMC-Sierra, Inc., and for its customers' internal use. In any event,
+no part of this document may be reproduced or redistributed in any
+form without the express written consent of PMC-Sierra, Inc.,  
+1380 Bordeaux Drive, Sunnyvale, CA 94089.
+
+P/N DOC-01700-02-A Rev A

amd64/centos5/libstdc++.so.6

@@ -0,0 +1 @@
+libstdc++.so.6.0.8

arcconf_2.03.0.orig.tar.gz.id

@@ -1 +0,0 @@
-6455985a1ce492a8d89b602f9e7663602b815a43

arcconf_2.03.1.orig.tar.gz.id

@@ -1 +0,0 @@
-b2c7e4e3926e1251a81ed1ffdfded410842377f7

arcconf_2.03.2.orig.tar.gz.id

@@ -1 +0,0 @@
-525eaf69e115059fb1210db1a2597eadc34f2413

arcconf_2.05.1.orig.tar.gz.id

@@ -1 +0,0 @@
-ba15fa23eac215b711d713a73fba9a0cc15391fa

arcconf_2.05.2.orig.tar.gz.id

@@ -1 +0,0 @@
-ba15fa23eac215b711d713a73fba9a0cc15391fa

arcconf_2.05.3.orig.tar.gz.id

@@ -1 +0,0 @@
-f4c596b9af3a8e2d71b67b9b275f12111daa2992

arcconf_2.05.4.orig.tar.gz.id

@@ -1 +0,0 @@
-423b71ae95e74b7812961a7eaba3d8cb41b46c5a

arcconf_2.06.1.orig.tar.gz.id

@@ -1 +0,0 @@
-ea2c84be2cbf46d1ff6774e4550fd6b12b873963

arcconf_3.00.1.orig.tar.gz.id

@@ -1 +0,0 @@
-ee3c07ca0ee088633c414d9d6ff4920cb999768a

arcconf_3.01.1.orig.tar.gz.id

@@ -1 +0,0 @@
-e6556d24736aaeda71c0d3f2c6117a13f3b7de10

arcconf_3.03.1.orig.tar.gz.id

@@ -1 +0,0 @@
-5cc091115dd8f93d9b103a7053e2ce3cb6215ca9

build_orig.sh

@@ -0,0 +1,102 @@
+#!/bin/bash
+# the directory of the script
+DIR=`cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd`
+echo "Working directory $DIR"
+
+# the temp directory used, within $DIR
+WORK_DIR=`mktemp -d -p "$DIR"`
+echo "Creating temp working directory $WORK_DIR"
+
+# deletes the temp directory
+function cleanup {
+  rm -rf "$WORK_DIR"
+  echo "Deleted temp working directory $WORK_DIR"
+}
+
+# register the cleanup function to be called on the EXIT signal
+trap cleanup EXIT
+
+# Download Files specified in files.diz
+while IFS=! read type app version outputfile url md5 realver
+do
+  echo "Downloading $app Version: $version"
+  #use -O for output file. define $outputfile yourself
+  wget -c --no-check-certificate --tries=1 -O $DIR/../$outputfile --timeout=5 "$url"
+  # use $(..) instead of backticks.
+  calculated_md5=$(md5sum "$DIR/../$outputfile" | cut -f 1 -d " ")
+  # compare md5
+  case "$calculated_md5" in
+    "$md5" )
+      echo "$DIR/../$outputfile md5 ok"
+    ;;
+    *)
+      echo "$DIR/../$outputfile md5 NOT ok"
+      exit 1
+    ;;
+  esac
+done < "$DIR/files.diz"
+
+# Extract to specified dir and set some variables
+while IFS=! read type app version outputfile url md5 realver
+do
+  mkdir -p $WORK_DIR/${type}/${realver}
+  pushd $WORK_DIR/${type}/${realver}
+  unzip $DIR/../$outputfile
+  tar -zxf $DIR/../$outputfile
+  rpm2cpio $DIR/../$outputfile | cpio -idmv
+  rpm2cpio manager/*.x86_64.rpm | cpio -idmv
+  rpm2cpio manager/*.i386.rpm | cpio -idmv
+  popd
+  mkdir -p $WORK_DIR/${app}-${version}/${type}/${realver}
+  pushd $WORK_DIR/${app}-${version}/${type}/${realver}
+  case "${type}" in
+    "amd64" )
+      mv $WORK_DIR/${type}/${realver}/linux_x64/cmdline/arcconf .
+      mv $WORK_DIR/${type}/${realver}/linux_x64/arcconf .
+      mv $WORK_DIR/${type}/${realver}/usr/lib64/lib* .
+      mv $WORK_DIR/${type}/${realver}/usr/StorMan/arcconf .
+      mv $WORK_DIR/${type}/${realver}/usr/StorMan/libstdc* .
+      chmod +x arcconf
+      dos2unix $WORK_DIR/${type}/${realver}/linux_x64/cmdline/*.{txt,TXT}
+      mv $WORK_DIR/${type}/${realver}/linux_x64/cmdline/*.{txt,TXT} .
+      dos2unix $WORK_DIR/${type}/${realver}/usr/StorMan/*.{txt,TXT}
+      mv $WORK_DIR/${type}/${realver}/usr/StorMan/*.{txt,TXT} .
+    ;;
+    "i386" )
+      mv $WORK_DIR/${type}/${realver}/linux/cmdline/arcconf .
+      mv $WORK_DIR/${type}/${realver}/usr/lib/lib* .
+      mv $WORK_DIR/${type}/${realver}/usr/StorMan/arcconf .
+      mv $WORK_DIR/${type}/${realver}/usr/StorMan/libstdc* .
+      chmod +x arcconf
+      dos2unix $WORK_DIR/${type}/${realver}/linux/cmdline/*.{txt,TXT}
+      mv $WORK_DIR/${type}/${realver}/linux/cmdline/*.{txt,TXT} .
+      dos2unix $WORK_DIR/${type}/${realver}/usr/StorMan/*.{txt,TXT}
+      mv $WORK_DIR/${type}/${realver}/usr/StorMan/*.{txt,TXT} .
+    ;;
+    *)
+      echo "Wrong arch"
+      exit 1
+    ;;
+  esac
+  echo "${app}_${version}.orig.tar.gz" > $WORK_DIR/filename.txt
+  echo "${app}-${version}" > $WORK_DIR/dirname.txt
+  echo "${version}" > $WORK_DIR/version.txt
+  popd
+done < "$DIR/files.diz"
+
+FILENAME=`cat $WORK_DIR/filename.txt`
+DIRNAME=`cat $WORK_DIR/dirname.txt`
+echo "Creating $DIR/../$FILENAME "
+
+pushd $WORK_DIR
+tar -czf $DIR/../$FILENAME $DIRNAME
+popd
+
+VER=`cat $WORK_DIR/version.txt`
+echo "Importing $DIR/../$FILENAME as $VER into git"
+#exit 1
+
+cleanup
+gbp import-orig --pristine-tar -u $VER $DIR/../$FILENAME
+
+exit 0

debian/README.source

@@ -0,0 +1,14 @@
+arcconf-2.02 (1:2.02.22404-1) unstable; urgency=low
+
+  Sources have been repacked from the following upstream archive:
+
+    373126b8d256aa76022906145a87d398  arcconf_v2_02_22404.zip
+
+  Upstream licence has been reformated using the following command:
+
+    cat /tmp/1 | sed 's!$!\n!' | \
+    sed "s|Bureau of Industry and Security's Lists to Check|http://www.bis.doc.gov/ComplianceAndEnforcement/ListsToCheck.htm|" | \
+    awk 'NR==1 || NF || prvNF {print} {prvNF=NF}' | sed 's!^$!.!' | \
+    vim - -c '%!fold -s -w76' -c '%s/^/ /'
+
+ -- Reto Kaiser (njam) <reto@cargomedia.ch>  Thu Mar 20 14:32:12 UTC 2014

debian/arcconf.wrapper32

@@ -0,0 +1,5 @@
+#!/bin/sh
+LD_LIBRARY_PATH=/usr/lib/arcconf:$LD_LIBRARY_PATH
+export LD_LIBRARY_PATH
+#exec /usr/bin/linux32 --uname-2.6 /usr/lib/arcconf/arcconf $@
+exec /usr/lib/arcconf/arcconf $@

debian/arcconf.wrapper64

@@ -0,0 +1,5 @@
+#!/bin/sh
+LD_LIBRARY_PATH=/usr/lib/arcconf:$LD_LIBRARY_PATH
+export LD_LIBRARY_PATH
+#exec /usr/bin/linux64 --uname-2.6 /usr/lib/arcconf/arcconf $@
+exec /usr/lib/arcconf/arcconf $@

debian/changelog

@@ -0,0 +1,26 @@
+arcconf (3.03.1-1) UNRELEASED; urgency=medium
+
+  * new integrated version
+  * add old 7.31 version of arcconf for compatiility
+  * add old version 4.30 for compatibility
+  * Bump to 2.06
+  * Bump to 3.00
+  * add missing 3.00 to package
+  * Bump to 3.01
+  * Bump to 3.02
+  * Bump to 3.03
+
+ -- Mario Fetka <mario.fetka@gmail.com>  Tue, 13 Aug 2019 15:05:02 +0200
+
+arcconf (2.05.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * new integrated version
+
+ -- Mario Fetka <mario.fetka@gmail.com>  Tue, 31 Oct 2017 17:14:13 +0100
+
+arcconf (2.02.22404-1) unstable; urgency=low
+
+  * Initial release.
+
+ -- Adam Cécile (Le_Vert) <gandalf@le-vert.net>  Thu, 20 Mar 2014 09:00:00 +0200

debian/compat

@@ -0,0 +1 @@
+7

debian/control

@@ -0,0 +1,46 @@
+Source: arcconf
+Section: admin
+Priority: optional
+Maintainer: Adam Cécile (Le_Vert) <gandalf@le-vert.net>
+Build-Depends: debhelper (>= 5), libc6-i386 | atop
+Standards-Version: 3.9.3
+
+Package: arcconf
+Architecture: amd64 i386
+Depends: ${misc:Depends}, ${shlibs:Depends}
+Provides: arcconf-1.05, arcconf-1.07, arcconf-1.08, arcconf-2.02
+Conflicts: arcconf-1.05, arcconf-1.07, arcconf-1.08, arcconf-2.02
+Replaces: arcconf-1.05, arcconf-1.07, arcconf-1.08, arcconf-2.02
+Description: Adaptec ARCCONF command line tool
+ Compatible Products:
+ .
+ Adaptec RAID 6405E
+ Adaptec RAID 6405T
+ Adaptec RAID 6445
+ Adaptec RAID 6805
+ Adaptec RAID 6805E
+ Adaptec RAID 6805Q
+ Adaptec RAID 6805T
+ Adaptec RAID 6805TQ
+ Adaptec RAID 7805
+ Adaptec RAID 7805Q
+ Adaptec RAID 71605
+ Adaptec RAID 71605E
+ Adaptec RAID 71605Q
+ Adaptec RAID 71685
+ Adaptec RAID 72405
+ Adaptec RAID 78165
+ Adaptec RAID 8405
+ Adaptec RAID 8405E
+ Adaptec RAID 8805
+ Adaptec RAID 8805E
+ Adaptec RAID 8885
+ Adaptec RAID 8885Q
+ Adaptec RAID 81605Z
+ Adaptec RAID 81605ZQ
+ PMC Adaptec HBA 1000-8e
+ PMC Adaptec HBA 1000-8i
+ PMC Adaptec HBA 1000-8i8e
+ PMC Adaptec HBA 1000-16e
+ PMC Adaptec HBA 1000-16i
+ Adaptec SAS Expander 82885T

debian/control.in

@@ -0,0 +1,46 @@
+Source: arcconf
+Section: admin
+Priority: optional
+Maintainer: Adam Cécile (Le_Vert) <gandalf@le-vert.net>
+Build-Depends: debhelper (>= 5), @BUILD_DEPENDS@
+Standards-Version: 3.9.3
+
+Package: arcconf
+Architecture: amd64 i386
+Depends: ${misc:Depends}, ${shlibs:Depends}
+Provides: arcconf-1.05, arcconf-1.07, arcconf-1.08, arcconf-2.02
+Conflicts: arcconf-1.05, arcconf-1.07, arcconf-1.08, arcconf-2.02
+Replaces: arcconf-1.05, arcconf-1.07, arcconf-1.08, arcconf-2.02
+Description: Adaptec ARCCONF command line tool
+ Compatible Products:
+ .
+ Adaptec RAID 6405E
+ Adaptec RAID 6405T
+ Adaptec RAID 6445
+ Adaptec RAID 6805
+ Adaptec RAID 6805E
+ Adaptec RAID 6805Q
+ Adaptec RAID 6805T
+ Adaptec RAID 6805TQ
+ Adaptec RAID 7805
+ Adaptec RAID 7805Q
+ Adaptec RAID 71605
+ Adaptec RAID 71605E
+ Adaptec RAID 71605Q
+ Adaptec RAID 71685
+ Adaptec RAID 72405
+ Adaptec RAID 78165
+ Adaptec RAID 8405
+ Adaptec RAID 8405E
+ Adaptec RAID 8805
+ Adaptec RAID 8805E
+ Adaptec RAID 8885
+ Adaptec RAID 8885Q
+ Adaptec RAID 81605Z
+ Adaptec RAID 81605ZQ
+ PMC Adaptec HBA 1000-8e
+ PMC Adaptec HBA 1000-8i
+ PMC Adaptec HBA 1000-8i8e
+ PMC Adaptec HBA 1000-16e
+ PMC Adaptec HBA 1000-16i
+ Adaptec SAS Expander 82885T

debian/copyright

@@ -0,0 +1,215 @@
+Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: arcconf
+Source: http://storage.microsemi.com/en-us/speed/raid/storage_manager/arcconf_v2_02_22404_zip.php
+
+Files: debian/*
+Copyright: Copyright (C) 2016 Adam Cecile (Le_Vert) <gandalf@le-vert.net>
+License: GPL-3.0+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+ .
+ This package is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ GNU General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <https://www.gnu.org/licenses/>.
+ .
+ On Debian systems, the complete text of the GNU General
+ Public License version 3 can be found in "/usr/share/common-licenses/GPL-3".
+
+Files: *
+Copyright: Copyright (C) 2003-2012 Adaptec by PMC
+License: Proprietary
+ Microsemi Corporation
+ Microsemi Adaptec Downloadable Files:
+ .
+ This License is granted by Microsemi Corporation, referred to in this 
+ License as "PMC-Sierra" or "ADAPTEC Inc" or "ADAPTEC" or "we" or "us." 
+ Microsemi reserves the right to record all activities and to use any 
+ information obtained in accordance with the privacy policy which you can 
+ access below. 
+ .
+ Directions to Obtain Your File:
+ .
+ CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS AS WELL AS THE EXPORT 
+ COMPLIANCE REQUIREMENTS SET OUT BELOW. YOU MUST ANSWER THE REQUIRED 
+ QUESTION TRUTHFULLY TO LET US KNOW WHETHER YOU HAVE READ AND UNDERSTOOD THE 
+ TERMS AND CONDITIONS AND EXPORT COMPLIANCE REQUIREMENTS AND WHETHER YOU 
+ AGREE TO COMPLY. YOU MUST CLICK A FURTHER BUTTON TO CONFIRM YOUR ANSWER AND 
+ IF YOU ANSWER IN THE AFFIRMATIVE, A BINDING LICENSE AGREEMENT ("LICENSE") 
+ WILL BE CONCLUDED BETWEEN US. YOU MAY THEN PROCEED TO DOWNLOAD THE SOFTWARE.
+ .
+ IF YOU DO NOT AGREE TO THESE TERMS, CONDITIONS, AND EXPORT COMPLIANCE 
+ REQUIREMENTS THEN DO NOT DOWNLOAD THE SOFTWARE. IF YOU WISH TO CANCEL THIS 
+ LICENSE AT ANY TIME YOU MAY DO SO BY DESTROYING ALL COPIES AND PARTIAL 
+ COPIES OF THE SOFTWARE WHICH YOU HAVE DOWNLOADED.
+ .
+ YOU ALSO AGREE THAT YOU HAVE ALL NECESSARY INFORMATION IN ORDER TO ENTER 
+ INTO THIS LICENSE WHETHER UNDER AN APPLICABLE EUROPEAN E-COMMERCE DIRECTIVE 
+ OR OTHERWISE. IF YOU DO NOT AGREE TO THESE TERMS, CONDITIONS, AND 
+ REQUIREMENTS, DO NOT DOWNLOAD ANY FILES.
+ .
+ Please retain a copy of the License for your files or you may contact 
+ ADAPTEC's Legal Department at the address listed below for a further copy. 
+ This license may be concluded in English or the language in which it is 
+ drafted by ADAPTEC and appears to you online, as applicable. If you are a 
+ consumer residing in Europe (a "European Consumer") then this License shall 
+ not affect your statutory rights under the local laws in Europe.
+ .
+ This License grants you a non-exclusive license to use the ADAPTEC Software 
+ and related documentation ("Software") on the following terms, conditions, 
+ and export compliance requirements: 
+ .
+ If you are NOT an individual consumer residing in Europe then the following 
+ terms, conditions and export compliance requirements apply and are a part 
+ of your license: ALL SECTIONS EXCEPT AS SPECIFIED HEREIN. 
+ .
+ If you are an individual consumer residing in Europe ("European Consumer") 
+ then the following terms, conditions and export compliance requirements 
+ apply and are made part of your License: 1, 2, 3, 4, applicable parts of 6, 
+ 7, 9 and the first paragraph of export compliance. IF YOU ARE A EUROPEAN 
+ CONSUMER THIS LICENSE SHALL NOT AFFECT YOUR RIGHTS UNDER THE STATUTORY LAWS 
+ OF EUROPE.
+ .
+ Your right to use the Software.You may use the Software in machine readable 
+ form (i.e. the form you download from us) within a single working location. 
+ You may copy the Software in the same form solely for back-up purposes or 
+ use within a single working location. You must reproduce ADAPTEC's 
+ copyright notice and proprietary legends. These requirements apply to 
+ European Consumers.
+ .
+ Restrictions. This Software contains trade secrets and in order to protect 
+ them you may not: (1) distribute copies of the Software in any manner, 
+ including, but not limited to, distribution through web site posting; (2) 
+ decompile, reverse engineer, disassemble, or otherwise reduce the Software 
+ to a human perceivable form; (3) MODIFY, ADAPT OR TRANSLATE THE SOFTWARE 
+ INTO ANY OTHER FORM; (4) RENT, LEASE, LOAN, RESELL FOR PROFIT, OR CREATE 
+ DERIVATIVE WORKS BASED UPON THE SOFTWARE OR ANY PART OF IT. These 
+ requirements apply to European Consumers.
+ .
+ Ownership. The Software is copyrighted by, proprietary to and a trade 
+ secret of ADAPTEC. ADAPTEC retains the title, ownership and intellectual 
+ property rights in and to the Software and all subsequent copies regardless 
+ of the form or media. The Software is protected by the copyright laws of 
+ the United States, the European Union, and international copyright 
+ treaties. This License is not a sale of the Software. These terms apply to 
+ European consumers.
+ .
+ Termination. This License is effective until terminated. This License will 
+ terminate automatically without notice if you fail to comply with any of 
+ the provisions. Upon termination you shall destroy all copies of the 
+ Software including any partial copies. This provision applies to European 
+ Consumers.
+ .
+ Disclaimer of Warranty. IF YOU ARE A EUROPEAN CONSUMER THEN THIS SECTION 5 
+ DOES NOT APPLY TO YOU AND DOES NOT FORM PART OF YOUR LICENSE WITH US. 
+ PROCEED TO SECTION 6.  THE SOFTWARE IS LICENSED TO YOU "AS IS." YOU ACCEPT 
+ ALL RISKS WHICH MAY ARISE FROM THE DOWNLOADING OF THE SOFTWARE, INCLUDING 
+ BUT NOT LIMITED TO ERRORS IN TRANSMISSION OR CORRUPTION OF EXISTING DATA OR 
+ SOFTWARE. ADAPTEC MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AND SPECIFICALLY 
+ DISCLAIMS ANY WARRANTY OF NON INFRINGEMENT OF THIRD PARTIES' RIGHTS, 
+ WARRANTIES OF SATISFACTORY QUALITY AND OF FITNESS FOR A PARTICULAR PURPOSE. 
+ Some states do not allow the exclusion of implied warranties or limitations 
+ of how long an implied warranty may last, so the above exclusion may not 
+ apply to you. You may also have other rights which vary from state to state.
+ .
+ Limitation of Liability.  FOR EUROPEAN CONSUMERS: WE WILL NOT BE LIABLE TO 
+ YOU WHERE YOU SUFFER LOSS WHICH WAS NOT FORESEEABLE TO YOU AND TO US WHEN 
+ YOU DOWNLOADED THE SOFTWARE (EVEN IF IT RESULTS FROM OUR FAILURE TO COMPLY 
+ WITH THIS LICENSE OR OUR NEGLIGENCE); WHERE YOU SUFFER ANY BUSINESS LOSS 
+ INCLUDING LOSS OF REVENUE, PROFITS OR ANTICIPATED SAVINGS (WHETHER THOSE 
+ LOSSES ARE THE DIRECT OR INDIRECT RESULT OF OUR DEFAULT); OR WHERE YOUR 
+ LOSS DOES NOT RESULT FROM OUR FAILURE TO COMPLY WITH THIS LICENSE OR OUR 
+ NEGLIGENCE. THE SOFTWARE HAS BEEN MADE AVAILABLE TO YOU FREE OF CHARGE. YOU 
+ MAY AT ANY TIME DOWNLOAD A FURTHER COPY OF THE SOFTWARE FREE OF CHARGE TO 
+ REPLACE YOUR ORIGINAL COPY OF THE SOFTWARE (CONSEQUENTLY, WE AND OUR 
+ SUPPLIERS WILL ONLY BE LIABLE TO YOU UP TO A MAXIMUM TOTAL LIMIT OF TWO 
+ THOUSAND DOLLARS U.S. OR ITS EURO EQUIVALENT AT THE TIME A CLAIM IS MADE). 
+ OUR MAXIMUM FINANCIAL RESPONSIBILITY TO YOU AND THAT OF OUR SUPPLIERS WILL 
+ NOT EXCEED THIS LIMIT EVEN IF THE ACTUAL LOSS YOU SUFFER IS MORE THAN THAT. 
+ HOWEVER, NOTHING IN THIS LICENSE SHALL RESTRICT ANY PARTY'S LIABILITY FOR 
+ FRAUD, DEATH OR PERSONAL INJURY ARISING FROM ITS NEGLIGENCE OR FOR FRAUD OR 
+ ANY FRAUDULENT MISREPRESENTATION.
+ .
+ ALL OTHERS DOWNLOADING THE SOFTWARE:  THE SOFTWARE IS PROVIDED FREE OF 
+ CHARGE TO YOU, THEREFORE UNDER NO CIRCUMSTANCES EXCEPT AS DESCRIBED HEREIN 
+ AND UNDER NO LEGAL THEORY, TORT (INCLUDING NEGLIGENCE), CONTRACT, OR 
+ OTHERWISE, SHALL ADAPTEC OR ITS SUPPLIERS OR RESELLERS BE LIABLE TO YOU OR 
+ ANY OTHER PERSON FOR ANY ECONOMIC LOSS (INCLUDING LOSS OF PROFIT) OR FOR 
+ ANY LOSS OF DATA, LOSS OF BUSINESS, LOSS OF GOODWILL, LOSS OF ANTICIPATED 
+ SAVINGS (IN EACH CASE WHETHER DIRECT OR INDIRECT) OR FOR ANY OTHER DIRECT 
+ OR INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER 
+ EVEN IF ADAPTEC SHALL HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 
+ HOWEVER, NOTHING IN THIS LICENSE SHALL RESTRICT ANY PARTY'S LIABILITY FOR 
+ FRAUD, DEATH OR PERSONAL INJURY ARISING FROM ITS NEGLIGENCE OR FOR FRAUD OR 
+ ANY FRAUDULENT MISREPRESENTATION.
+ .
+ Export. By downloading, you acknowledge that the laws and regulations of 
+ the United States and relevant countries within the European Union, 
+ restrict the export and re-export of the Software. Further, you agree that 
+ you will not export or re-export the Software or media in any form without 
+ the appropriate United States and foreign government approval. If you are a 
+ European Consumer you must not export Software outside the country in which 
+ you download it without our prior written permission. (See below for 
+ details on Export Compliance Requirements.)
+ .
+ U.S. Government Restricted Rights. IF YOU ARE A EUROPEAN CONSUMER THEN THIS 
+ CLAUSE WILL NOT APPLY TO YOU AND DOES NOT FORM PART OF YOUR LICENSE 
+ AGREEMENT WITH US. PLEASE PROCEED TO SECTION 9. If the Software is acquired 
+ under the terms of a United States GSA contract, use, reproduction or 
+ disclosure is subject to the restrictions set forth in the applicable ADP 
+ Schedule contract. If the Software is acquired under the terms of a DoD or 
+ civilian agency contract, use, duplication or disclosure by the Government 
+ is subject to the restrictions of this License in accordance with 48 C.F.R. 
+ 12.212 of the Federal Acquisition Regulations and its successors and 48 
+ C.F.R. 227.7202-1 of the DoD FAR Supplement and its successors. (See below 
+ for details on Export Compliance Requirements.)
+ .
+ General. California residents entered into and to be performed within 
+ California, except as governed by Federal law. Should any provision of this 
+ License be declared unenforceable in any jurisdiction, then such provision 
+ shall be deemed to be severable from this License and shall not affect the 
+ remainder hereof. All rights in the Software not specifically granted in 
+ this License are reserved by Adaptec.
+ .
+ EXPORT COMPLIANCE REQUIREMENTS
+ .
+ Export of any information from the Adaptec web site (including Confidential 
+ Information obtained through Adaptec Access) outside of the United States 
+ is subject to all U.S. export control laws. You will abide by such laws and 
+ also to the provision of the U.S. Export-Re-export Requirements and 
+ Enhanced Proliferation Control Initiative set forth here. You and your 
+ organization will not sell, license, or otherwise provide or ship Adaptec 
+ products or technical data (or the direct product thereof) for export or 
+ re-export to the embargoed or restricted* countries listed below:
+ .
+ Afghanistan (Taliban controlled area), Cuba, Iran, Iraq, North Korea*, 
+ Sudan, and Syria*
+ .
+ You agree not to transfer, export or re-export Adaptec products, technology 
+ or software to your customers or any intermediate entity in the chain of 
+ supply if our products will be used in the design, development, production, 
+ stockpiling or use of missiles, chemical or biological weapons or for 
+ nuclear end uses without obtaining prior authorization from the U.S. 
+ Government.
+ .
+ You also agree that unless you receive prior authorization from the U.S. 
+ Department of Commerce, you shall not transfer, export or re-export, 
+ directly or indirectly, any Adaptec technology or software (or the direct 
+ product of such technology or software or any part thereof, or any process 
+ or service which is the direct product of such technology or software) to 
+ any Sanctioned and/or Embargoed entity listed on:
+ .
+ http://www.bis.doc.gov/ComplianceAndEnforcement/ListsToCheck.htm
+ .
+ If you have any questions concerning this License, contact:
+ .
+ Microsemi Corporation
+ Legal Department
+ 1380 Bordeaux Drive
+ Sunnyvale, CA 94089
+ Phone: (408) 239-8000

debian/dirs

@@ -0,0 +1,2 @@
+usr/sbin
+usr/lib/arcconf

debian/docs

@@ -0,0 +1 @@
+amd64/2.02/README.TXT

debian/postinst

@@ -0,0 +1,62 @@
+#!/bin/sh
+
+set -e
+
+if [ -f "/usr/lib/arcconf/arcconf-3.03" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-3.03 303
+fi
+if [ -f "/usr/lib/arcconf/arcconf-3.02" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-3.02 302
+fi
+if [ -f "/usr/lib/arcconf/arcconf-3.01" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-3.01 301
+fi
+if [ -f "/usr/lib/arcconf/arcconf-3.00" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-3.00 300
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.06" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-2.06 206
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.05" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-2.05 205
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.04" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-2.04 204
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.03" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-2.03 203
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.02" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-2.02 202
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.01" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-2.01 201
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.00" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-2.00 200
+fi
+if [ -f "/usr/lib/arcconf/arcconf-1.08" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-1.08 108
+fi
+if [ -f "/usr/lib/arcconf/arcconf-1.07" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-1.07 107
+fi
+if [ -f "/usr/lib/arcconf/arcconf-1.06" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-1.06 106
+fi
+if [ -f "/usr/lib/arcconf/arcconf-1.05" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-1.05 105
+fi
+if [ -f "/usr/lib/arcconf/arcconf-1.04" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-1.04 104
+fi
+if [ -f "/usr/lib/arcconf/arcconf-7.31" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-7.31 100
+fi
+if [ -f "/usr/lib/arcconf/arcconf-4.30" ]; then
+    update-alternatives --install /usr/lib/arcconf/arcconf arcconf /usr/lib/arcconf/arcconf-4.30 90
+fi
+
+#DEBHELPER#
+
+exit 0

debian/prerm

@@ -0,0 +1,62 @@
+#! /bin/sh
+
+set -e
+
+if [ -f "/usr/lib/arcconf/arcconf-3.03" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-3.03
+fi
+if [ -f "/usr/lib/arcconf/arcconf-3.02" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-3.02
+fi
+if [ -f "/usr/lib/arcconf/arcconf-3.01" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-3.01
+fi
+if [ -f "/usr/lib/arcconf/arcconf-3.00" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-3.00
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.06" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-2.06
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.05" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-2.05
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.04" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-2.04
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.03" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-2.03
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.02" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-2.02
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.01" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-2.01
+fi
+if [ -f "/usr/lib/arcconf/arcconf-2.00" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-2.00
+fi
+if [ -f "/usr/lib/arcconf/arcconf-1.08" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-1.08
+fi
+if [ -f "/usr/lib/arcconf/arcconf-1.07" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-1.07
+fi
+if [ -f "/usr/lib/arcconf/arcconf-1.06" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-1.06
+fi
+if [ -f "/usr/lib/arcconf/arcconf-1.05" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-1.05
+fi
+if [ -f "/usr/lib/arcconf/arcconf-1.04" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-1.04
+fi
+if [ -f "/usr/lib/arcconf/arcconf-7.31" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-7.31
+fi
+if [ -f "/usr/lib/arcconf/arcconf-4.30" ]; then
+    update-alternatives --remove arcconf /usr/lib/arcconf/arcconf-4.30
+fi
+
+#DEBHELPER#
+
+exit 0

debian/rules

@@ -0,0 +1,138 @@
+#!/usr/bin/make -f
+
+# Uncomment this to turn on verbose mode.
+#export DH_VERBOSE=1
+
+
+clean:
+	dh_testdir
+	dh_testroot
+	dh_clean
+
+install:
+	dh_testdir
+	dh_testroot
+	dh_clean -k
+	dh_installdirs
+ifeq ($(DEB_BUILD_ARCH),amd64)
+	install -D -m 0755 debian/arcconf.wrapper64 \
+			   debian/arcconf/usr/sbin/arcconf
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/centos5/libstdc++.so.6.0.8
+	install -D -m 0755 amd64/centos5/libstdc++.so.6.0.8 \
+			   debian/arcconf/usr/lib/arcconf/libstdcv4.so.6.0.8
+	ln -s libstdcv4.so.6.0.8 debian/arcconf/usr/lib/arcconf/libstdcv4.so.6
+	install -D -m 0755 amd64/3.03/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-3.03
+	install -D -m 0755 amd64/3.02/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-3.02
+	install -D -m 0755 amd64/3.01/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-3.01
+	install -D -m 0755 amd64/3.00/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-3.00
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/2.06/arcconf
+	install -D -m 0755 amd64/2.06/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-2.06
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/2.05/arcconf
+	install -D -m 0755 amd64/2.05/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-2.05
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/2.04/arcconf
+	install -D -m 0755 amd64/2.04/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-2.04
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/2.03/arcconf
+	install -D -m 0755 amd64/2.03/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-2.03
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/2.02/arcconf
+	install -D -m 0755 amd64/2.02/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-2.02
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/2.01/arcconf
+	install -D -m 0755 amd64/2.01/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-2.01
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/2.00/arcconf
+	install -D -m 0755 amd64/2.00/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-2.00
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/1.08/arcconf
+	install -D -m 0755 amd64/1.08/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-1.08
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/1.07/arcconf
+	install -D -m 0755 amd64/1.07/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-1.07
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/1.06/arcconf
+	install -D -m 0755 amd64/1.06/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-1.06
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/1.05/arcconf
+	install -D -m 0755 amd64/1.05/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-1.05
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" amd64/1.04/arcconf
+	install -D -m 0755 amd64/1.04/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-1.04
+	sed -i "s/libstdc++.so.5/libstdcv3.so.5/g" amd64/7.31/libstdc++.so.5
+	install -D -m 0755 amd64/7.31/libstdc++.so.5 \
+			   debian/arcconf/usr/lib/arcconf/libstdcv3.so.5
+	sed -i "s/libstdc++.so.5/libstdcv3.so.5/g" amd64/7.31/arcconf
+	install -D -m 0755 amd64/7.31/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-7.31
+	install -D -m 0755 i386/4.30/libstdc++-libc6.2-2.so.3 \
+			   debian/arcconf/usr/lib/arcconf/libstdc++-libc6.2-2.so.3
+	install -D -m 0755 amd64/4.30/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-4.30
+endif
+ifeq ($(DEB_BUILD_ARCH),i386)
+	install -D -m 0755 debian/arcconf.wrapper32 \
+			   debian/arcconf/usr/sbin/arcconf
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" i386/centos5/libstdc++.so.6.0.8
+	install -D -m 0755 i386/centos5/libstdc++.so.6.0.8 \
+			   debian/arcconf/usr/lib/arcconf/libstdcv4.so.6.0.8
+	ln -s libstdcv4.so.6.0.8 debian/arcconf/usr/lib/arcconf/libstdcv4.so.6
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" i386/2.01/arcconf
+	install -D -m 0755 i386/2.01/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-2.01
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" i386/2.00/arcconf
+	install -D -m 0755 i386/2.00/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-2.00
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" i386/1.08/arcconf
+	install -D -m 0755 i386/1.08/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-1.08
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" i386/1.07/arcconf
+	install -D -m 0755 i386/1.07/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-1.07
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" i386/1.06/arcconf
+	install -D -m 0755 i386/1.06/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-1.06
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" i386/1.05/arcconf
+	install -D -m 0755 i386/1.05/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-1.05
+	sed -i "s/libstdc++.so.6/libstdcv4.so.6/g" i386/1.04/arcconf
+	install -D -m 0755 i386/1.04/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-1.04
+	sed -i "s/libstdc++.so.5/libstdcv3.so.5/g" i386/7.31/libstdc++.so.5
+	install -D -m 0755 i386/7.31/libstdc++.so.5 \
+			   debian/arcconf/usr/lib/arcconf/libstdcv3.so.5
+	sed -i "s/libstdc++.so.5/libstdcv3.so.5/g" i386/7.31/arcconf
+	install -D -m 0755 i386/7.31/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-7.31
+	install -D -m 0755 i386/4.30/libstdc++-libc6.2-2.so.3 \
+			   debian/arcconf/usr/lib/arcconf/libstdc++-libc6.2-2.so.3
+	install -D -m 0755 i386/4.30/arcconf \
+			   debian/arcconf/usr/lib/arcconf/arcconf-4.30
+endif
+	dh_install
+
+binary-indep: build install
+binary-arch: build install
+	dh_testdir
+	dh_testroot
+	dh_installchangelogs
+	dh_installdocs
+	dh_link
+	dh_compress
+	dh_fixperms
+	dh_makeshlibs
+	dh_strip
+	dh_installdeb
+	LD_LIBRARY_PATH=$$(pwd)/debian/arcconf/usr/lib/arcconf:$${LD_LIBRARY_PATH} dh_shlibdeps
+	dh_gencontrol
+	dh_md5sums
+	dh_builddeb
+
+binary: binary-arch binary-indep
+.PHONY: build clean binary-indep binary-arch binary install

files.diz

@@ -0,0 +1,29 @@
+amd64!arcconf!3.03.1!arcconf_v3_03_23668.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v3_03_23668.zip!b561a9db7b68695a10b489e63348a7ad!3.03
+amd64!arcconf!3.03.1!arcconf_v3_02_23600.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v3_02_23600.zip!63878768e5c80b787f1e83f28cd07c09!3.02
+amd64!arcconf!3.03.1!arcconf_v3_01_23531.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v3_01_23531.zip!8d8148719bda151c8fbbdb3426ea6e08!3.01
+amd64!arcconf!3.03.1!arcconf_v3_00_23488.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v3_00_23488.zip!df63edf89beba7b8e716db04994e5242!3.00
+amd64!arcconf!3.03.1!arcconf_v2_06_23167.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v2_06_23167.zip!f84e041ec412b1ccea4ab5e659a7709e!2.06
+amd64!arcconf!3.03.1!arcconf_v2_05_22932.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v2_05_22932.zip!51a03b5fe08b45f229b2c73127c5c6ae!2.05
+amd64!arcconf!3.03.1!arcconf_v2_04_22665.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v2_04_22665.zip!07153757100a62ece5551d8950297f00!2.04
+amd64!arcconf!3.03.1!arcconf_v2_03_22476.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v2_03_22476.zip!e98c9f2fb11d368adc0378ddd9daad40!2.03
+amd64!arcconf!3.03.1!arcconf_v2_02_22404.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v2_02_22404.zip!373126b8d256aa76022906145a87d398!2.02
+amd64!arcconf!3.03.1!arcconf_v2_01_22270.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v2_01_22270.zip!a51110590c3439245e5179a9e35bad86!2.01
+i386!arcconf!3.03.1!arcconf_v2_01_22270.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v2_01_22270.zip!a51110590c3439245e5179a9e35bad86!2.01
+amd64!arcconf!3.03.1!arcconf_v2_00_21811.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v2_00_21811.zip!946ed3423254d893120ceb89f7779685!2.00
+i386!arcconf!3.03.1!arcconf_v2_00_21811.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v2_00_21811.zip!946ed3423254d893120ceb89f7779685!2.00
+amd64!arcconf!3.03.1!arcconf_v1_8_21375.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v1_8_21375.zip!7a697a7c8b99b66312116d4249ab1922!1.08
+i386!arcconf!3.03.1!arcconf_v1_8_21375.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v1_8_21375.zip!7a697a7c8b99b66312116d4249ab1922!1.08
+amd64!arcconf!3.03.1!arcconf_v1_7_21229.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v1_7_21229.zip!8d8e1829172bb72f69081b2ac6d2e50b!1.07
+i386!arcconf!3.03.1!arcconf_v1_7_21229.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v1_7_21229.zip!8d8e1829172bb72f69081b2ac6d2e50b!1.07
+amd64!arcconf!3.03.1!arcconf_v1_6_21062.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v1_6_21062.zip!32aa39da4ecca41c4cb987791f5aa656!1.06
+i386!arcconf!3.03.1!arcconf_v1_6_21062.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v1_6_21062.zip!32aa39da4ecca41c4cb987791f5aa656!1.06
+amd64!arcconf!3.03.1!arcconf_v1_5_20942.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v1_5_20942.zip!de7e676bdd9c04db8125d04086d9efd6!1.05
+i386!arcconf!3.03.1!arcconf_v1_5_20942.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v1_5_20942.zip!de7e676bdd9c04db8125d04086d9efd6!1.05
+amd64!arcconf!3.03.1!arcconf_v1_4_20859.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v1_4_20859.zip!6c3d72fe83ff76e68a70fa59d92ae5f7!1.04
+i386!arcconf!3.03.1!arcconf_v1_4_20859.zip!http://download.adaptec.com/raid/storage_manager/arcconf_v1_4_20859.zip!6c3d72fe83ff76e68a70fa59d92ae5f7!1.04
+amd64!arcconf!3.03.1!asm_linux_x64_v7_31_18856.tgz!http://download.adaptec.com/raid/storage_manager/asm_linux_x64_v7_31_18856.tgz!f9f13c1f9223da6138abc2c8bdadd54a!7.31
+i386!arcconf!3.03.1!asm_linux_x86_v7_31_18856.tgz!http://download.adaptec.com/raid/storage_manager/asm_linux_x86_v7_31_18856.tgz!2bdfd5e999a86ac5bd8c7b43d858fdfd!7.31
+amd64!arcconf!3.03.1!libstdc++-4.1.2-55.el5.x86_64.rpm!http://vault.centos.org/5.11/os/x86_64/CentOS/libstdc++-4.1.2-55.el5.x86_64.rpm!ecbeb114ecf3a33848b7d4e1aefe65c2!centos5
+i386!arcconf!3.03.1!libstdc++-4.1.2-55.el5.i386.rpm!http://vault.centos.org/5.11/os/i386/CentOS/libstdc++-4.1.2-55.el5.i386.rpm!b615266b1ddae7f9a17601179f83c826!centos5
+amd64!arcconf!3.03.1!asm_linux_x64_v4.30-16038.rpm!http://download.adaptec.com/raid/aac/sm/asm_linux_x64_v4.30-16038.rpm!b7c7b25e2c7006b087997d8f0b8182cc!4.30
+i386!arcconf!3.03.1!asm_linux_v4.30-16038.rpm!http://download.adaptec.com/raid/aac/sm/asm_linux_v4.30-16038.rpm!9585c8b60873b5f92be97a4355d306b7!4.30

i386/1.08/License.txt

@@ -0,0 +1,292 @@
+International License Agreement for Non-Warranted Programs
+
+Part 1 - General Terms 
+
+PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE PROGRAM.
+Adaptec WILL LICENSE THE PROGRAM TO YOU ONLY IF YOU FIRST ACCEPT THE
+TERMS OF THIS AGREEMENT. BY USING THE PROGRAM YOU AGREE TO THESE
+TERMS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT,
+PROMPTLY RETURN THE UNUSED PROGRAM TO THE PARTY (EITHER Adaptec OR
+ITS RESELLER) FROM WHOM YOU ACQUIRED IT TO RECEIVE A REFUND OF
+THE AMOUNT YOU PAID. 
+
+The Program is owned by (Adaptec) or a supplier of Adaptec 
+and is copyrighted and licensed, not sold. 
+
+The term "Program" means the original program and all whole or
+partial copies of it. A Program consists of machine-readable
+instructions, its components, data, audio-visual content (such
+as images, text, recordings, or pictures), and related licensed
+materials. 
+
+This Agreement includes Part 1 - General Terms and Part 2 
+Country unique Terms and is the complete agreement regarding the
+use of this Program, and replaces any prior oral or written
+communications between you and Adaptec. The terms of Part 2 may
+replace or modify those of Part 1. 
+
+
+1. License 
+
+Use of the Program 
+
+Adaptec grants you a nonexclusive license to use the Program. 
+
+You may 1) use the Program to the extent of authorizations you
+have acquired and 2) make and install copies to support the
+level of use authorized, providing you reproduce the copyright
+notice and any other legends of ownership on each copy, or
+partial copy, of the Program. 
+
+If you acquire this Program as a program upgrade, your
+authorization to use the Program from which you upgraded is
+terminated. 
+
+You will ensure that anyone who uses the Program does so only in
+compliance with the terms of this Agreement. 
+
+You may not 1) use, copy, modify, or distribute the Program
+except as provided in this Agreement; 2) reverse assemble,
+reverse compile, or otherwise translate the Program except as
+specifically permitted by law without the possibility of
+contractual waiver; or 3) sublicense, rent, or lease the
+Program. 
+
+Transfer of Rights and Obligations 
+
+You may transfer all your license rights and obligations under a
+Proof of Entitlement for the Program to another party by
+transferring the Proof of Entitlement and a copy of this
+Agreement and all documentation. The transfer of your license
+rights and obligations terminates your authorization to use the
+Program under the Proof of Entitlement. 
+
+
+2. Proof of Entitlement 
+
+The Proof of Entitlement for this Program is evidence of your
+authorization to use this Program and of your eligibility for
+future upgrade program prices (if announced) and potential
+special or promotional opportunities. 
+
+
+3. Charges and Taxes 
+
+Adaptec defines use for the Program for charging purposes and
+specifies it in the Proof of Entitlement. Charges are based on
+extent of use authorized. If you wish to increase the extent of
+use, notify Adaptec or its reseller and pay any applicable charges.
+Adaptec does not give refunds or credits for charges already due or
+paid. 
+
+If any authority imposes a duty, tax, levy or fee, excluding
+those based on Adaptec's net income, upon the Program supplied by
+Adaptec under this agreement, then you agree to pay that amount 
+as Adaptec specifies or
+supply exemption documentation. 
+
+
+4. No Warranty 
+
+SUBJECT TO ANY STATUTORY WARRANTIES WHICH CAN NOT BE EXCLUDED,
+Adaptec MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
+INCLUDING WITHOUT LIMITATION, THE WARRANTY OF NON-INFRINGEMENT
+AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+PARTICULAR PURPOSE, REGARDING THE PROGRAM OR TECHNICAL SUPPORT,
+IF ANY. Adaptec MAKES NO WARRANTY REGARDING THE CAPABILITY OF THE
+PROGRAM TO CORRECTLY PROCESS, PROVIDE AND/OR RECEIVE DATE DATA
+WITHIN AND BETWEEN THE 20TH AND 21ST CENTURIES. 
+
+The exclusion also applies to any of Adaptec's subcontractors,
+suppliers, or program developers (collectively called
+"Suppliers"). 
+
+Manufacturers, suppliers, or publishers of non-Adaptec Programs may
+provide their own warranties. 
+
+
+5. Limitation of Liability 
+
+NEITHER Adaptec NOR ITS SUPPLIERS WILL BE LIABLE FOR ANY DIRECT OR
+INDIRECT
+
+DAMAGES, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
+SAVINGS, OR ANY INCIDENTAL, SPECIAL, OR OTHER ECONOMIC
+CONSEQUENTIAL DAMAGES, EVEN IF Adaptec IS INFORMED OF THEIR
+POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
+LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE
+EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU. 
+
+
+6. General 
+
+Nothing in this Agreement affects any statutory rights of
+consumers that cannot be waived or limited by contract. 
+
+Adaptec may terminate your license if you fail to comply with the
+terms of this Agreement. If Adaptec does so, you must immediately
+destroy the Program and all copies you made of it. 
+
+You agree to comply with applicable export laws and regulations. 
+
+Neither you nor Adaptec will bring a legal action under this
+Agreement more than two years after the cause of action arose
+unless otherwise provided by local law without the possibility
+of contractual waiver or limitation. 
+
+Neither you nor Adaptec is responsible for failure to fulfill any
+obligations due to causes beyond its control. 
+
+Adaptec does not provide program services or technical support,
+unless Adaptec specifies otherwise. 
+
+The laws of the country in which you acquire the Program govern
+this Agreement, except 1) in Australia, the laws of the State or
+Territory in which the transaction is performed govern this
+Agreement; 2) in Albania, Armenia, Belarus, Bosnia/Herzegovina,
+Bulgaria, Croatia, Czech Republic, Georgia, Hungary, Kazakhstan,
+Kirghizia, Former Yugoslav Republic of Macedonia
+(FYROM), Moldova, Poland, Romania, Russia, Slovak Republic,
+Slovenia, Ukraine, and Federal Republic of Yugoslavia, the laws
+of Austria govern this Agreement; 3) in the United Kingdom, all
+disputes relating to this Agreement will be governed by English
+Law and will be submitted to the exclusive jurisdiction of the
+English courts; 4) in Canada, the laws in the Province of
+Ontario govern this Agreement; and 5) in the United States and
+Puerto Rico, and People's Republic of China, the laws of the 
+State of New York govern this Agreement. 
+
+
+Part 2 - Country-unique Terms 
+
+
+AUSTRALIA: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Although Adaptec specifies that there are no warranties, you may
+have certain rights under the Trade Practices Act 1974 or other
+legislation and are only limited to the extent permitted by the
+applicable legislation. 
+
+Limitation of Liability (Section 3): 
+The following paragraph is added to this Section: 
+
+Where Adaptec is in breach of a condition or warranty implied by the
+Trade Practices Act 1974, Adaptec's liability is limited to the
+repair or replacement of the goods, or the supply of equivalent
+goods. Where that condition or warranty relates to right to
+sell, quiet possession or clear title, or the goods are of a
+kind ordinarily acquired for personal, domestic or household use
+or consumption, then none of the limitations in this paragraph
+apply. 
+
+
+GERMANY:
+
+No Warranty (Section 4):
+The following paragraphs are added to this Section:
+
+The minimum warranty period for Programs is six months.
+
+In case a Program is delivered without Specifications, we will
+only warrant that the Program information correctly describes
+the Program and that the Program can be used according to the
+Program information. You have to check the usability according
+to the Program information within the "money-back guaranty"
+period.
+
+Limitation of Liability (Section 5):
+The following paragraph is added to this Section:
+
+The limitations and exclusions specified in the Agreement will
+not apply to damages caused by Adaptec with fraud or gross
+negligence, and for express warranty. 
+
+
+INDIA: 
+
+General (Section 6): 
+The following replaces the fourth paragraph of this Section: 
+
+If no suit or other legal action is brought, within two years
+after the cause of action arose, in respect of any claim that
+either party may have against the other, the rights of the
+concerned party in respect of such claim will be forfeited and
+the other party will stand released from its obligations in
+respect of such claim. 
+
+
+IRELAND: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Except as expressly provided in these terms and conditions, all
+statutory conditions, including all warranties implied, but
+without prejudice to the generality of the foregoing, all
+warranties implied by the Sale of Goods Act 1893 or the Sale of
+Goods and Supply of Services Act 1980 are hereby excluded. 
+
+
+ITALY:
+
+Limitation of Liability (Section 5):
+This Section is replaced by the following:
+
+Unless otherwise provided by mandatory law, Adaptec is not liable
+for any damages which might arise. 
+
+
+NEW ZEALAND: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Although Adaptec specifies that there are no warranties, you may
+have certain rights under the Consumer Guarantees Act 1993 or
+other legislation which cannot be excluded or limited. The
+Consumer Guarantees Act 1993 will not apply in respect of any
+goods or services which Adaptec provides, if you require the goods
+and services for the purposes of a business as defined in that
+Act. 
+
+Limitation of Liability (Section 5): 
+The following paragraph is added to this Section: 
+
+Where Programs are not acquired for the purposes of a business
+as defined in the Consumer Guarantees Act 1993, the limitations
+in this Section are subject to the limitations in that Act. 
+
+
+PEOPLE'S REPUBLIC OF CHINA:
+
+Charges (Section 3):
+The following paragraph is added to the Section:
+
+All banking charges incurred in the People's Republic of China
+will be borne by you and those incurred outside the People's
+Republic of China will be borne by Adaptec. 
+
+
+UNITED KINGDOM: 
+
+Limitation of Liability (Section 5): 
+The following paragraph is added to this Section at the end of
+the first paragraph: 
+
+The limitation of liability will not apply to any breach of
+Adaptec's obligations implied by Section 12 of the Sales of Goods
+Act 1979 or Section 2 of the Supply of Goods and Services Act
+1982. 
+
+
+UNITED STATES AND CANADA:
+
+No Country-unique Terms apply.
+
+
+By continuing with the installation of the Program, you are 
+accepting the terms and conditions above.
+

i386/1.08/README.TXT

@@ -0,0 +1,693 @@
+README.TXT
+
+Adaptec maxView Storage Manager
+Adaptec Command Line Interface Utility (ARCCONF)
+
+as of May 19, 2015
+--------------------------------------------------------------------
+Please review this file for important information about issues
+and errata that were discovered after completion of the standard
+product documentation. In the case of conflict between various
+parts of the documentation set, this file contains the most
+current information.
+
+The following information is available in this file:
+
+   1. New Features in this Release
+   2. Software Versions and Documentation
+      2.1   Utility Software
+      2.2   Documentation
+   3. Installation and Setup
+      3.1   Installation Instructions
+      3.2   Supported Operating Systems
+      3.3   General Setup Notes
+      3.4   Remote Access
+      3.5   Windows 8 Setup
+      3.6   SLES Setup 
+      3.7   Ubuntu Setup
+      3.8   Bootable USB Image Security Warnings 
+      3.9   RAW Device Setup
+      3.10  maxView Plugin for VMware vSphere Web Client
+      3.11  Firmware Downgrade on Series 8 Board Revision "B1"
+      3.12  Uninstallation Issues
+   4. Known Limitations
+      4.1   Login Issues on Windows Domain Server
+      4.2   Hot Spare Issues
+      4.3   Dual-Controller Systems
+      4.4   Email Notifications
+      4.5   SGPIO Enclosures
+      4.6   Non-RAID Mode Controllers
+      4.7   RAID-Level Migrations
+      4.8   maxCache Device Migration
+      4.9   ARCCONF maxCache Device Size Issue 
+      4.10  Browser Issues
+      4.11  Remote System Issues
+      4.12  Power Management Issues
+      4.13  RAID 50/RAID 60, Max Drives
+      4.14  RAID 10 Segment Order
+      4.15  RAID 10 Rebuild Order       
+      4.16  Verify with Fix      
+      4.17  Locate Logical Drive Blink LED
+      4.18  ATA Secure Erase
+      4.19  ARCCONF Backward Compatibility
+      4.20  Adaptec Series 6 Controller Issues
+      4.21  Simple Volume Support
+      4.22  Auto-Volume Support 
+      4.23  Hot-Removing Disk Drives on Xenserver Guest OS
+      4.24  Updating Hard Disk Firmware on VMware Guest OS
+      4.25  Creating a Support Archive on a Guest OS
+      4.26  Enclosure Status Reporting
+      4.27  PHY Status on Enclosure Backplanes  
+      4.28  Special Characters in Logical Device Names   
+      4.29  Speaker Status on SuperMicro SAS2X28 Enclosures
+      4.30  Changing Read and Write Cache Settings for a Logical Drive
+      4.31  Online Help Issues 
+      
+--------------------------------------------------------------------
+1. New Features in this Release
+    
+   o Support for new operating systems
+   o Support for HDD/SSD temperature monitoring
+   o Improved SMART error logging for SAS and SATA devices  
+   o Basecode logs and Flash Backup Module hard error logs included in support archive
+   o Enhanced maxView SMTP mail client to comply with highly secured SMTP servers (Gmail, Yahoo, etc)
+   o Open Pegasus 2.13 (maxView CIM Server) upgrade 
+   o Re-design of maxView schedule dialog with advanced Primefaces calendar component
+   o Multi-level authentication and access privileges in maxView (Administrator/Standard user)
+   o Installer change: install GUI, Agent and CIM Server as separate components (saves 500MB RAM space, typical)
+   o Global Init/Uninit Physical Devices wizard
+   o Global Delete Logical Devices wizard
+   o Misc UI enhancements:
+      - Logical drive property tab shows initialization method
+      - Physical device temperature added to physical drive information
+      - Logical device long running task navigation from tree node to Tab to Task dialog
+   o ARCCONF changes:
+      - New commands: backupunit, driverupdate, setcustommode, setconnectormode
+      - Enhanced commands: identify command supports blink LED start/stop
+   o Bugfixes
+
+--------------------------------------------------------------------
+2. Software Versions and Documentation
+
+   2.1 Utility Software
+       
+       o Adaptec maxView Storage Manager Version 1.08    
+       o Adaptec ARCCONF Command Line Interface Utility Version 1.08
+
+   2.2 Documentation 
+  
+       PDF Format (English/Japanese):
+        
+       o maxView Storage Manager User's Guide               
+       o Adaptec RAID Controller Command Line Utility User's Guide
+
+       HTML and Text Format:
+
+       o maxView Storage Manager Online Help
+       o maxView Storage Manager README.TXT file
+        
+--------------------------------------------------------------------
+3. Installation and Setup
+
+   3.1 Installation Instructions
+
+       The Adaptec SAS RAID Controllers Installation and User's Guide
+       contains complete installation information for the controllers
+       and drivers. The Adaptec RAID Controllers Command Line Utility
+       User's Guide contains complete installation information for
+       ARCCONF. The maxView Storage Manager User's Guide contains  
+       complete installation information for the maxView Storage  
+       Manager software.        
+
+   3.2 Supported Operating Systems                           
+
+       Microsoft Windows: 
+  
+       o Windows Server 2012 R2, 64-bit
+       o Windows Server 2008, 32-bit and 64-bit
+       o Windows Server 2008 R2, 64-bit
+       o Windows SBS 2011, 64-bit 
+       o Windows 7, 32-bit and 64-bit
+       o Windows 8, Windows 8.1, 32-bit and 64-bit
+          
+       Linux:
+
+       o Red Hat Enterprise Linux 7.1, 64-bit
+       o Red Hat Enterprise Linux 6.6, 5.11, 32-bit and 64-bit
+       o SuSE Linux Enterprise Server 12, 64 bit 
+       o SuSE Linux Enterprise Server 11, 10*, 32-bit and 64-bit     
+       o Debian Linux 7.8, 32-bit and 64-bit  
+       o Ubuntu Linux 14.10, 14.04.1, 12.04.3, 32-bit and 64-bit
+       o Fedora Linux 21, 32-bit and 64-bit
+       o CentOS 7.1, 64 bit 
+       o CentOS 6.6, 5.11, 32-bit and 64-bit
+       
+       *See Section 3.6 for SLES 10 setup issues
+
+       Virtual OS Environments:
+        
+       o VMware ESXi 6.0, VMware ESXi 5.5
+       o Citrix XenServer 6.5 (32-bit GOS only)
+
+       Solaris:
+          
+       o Solaris 10 U11
+       o Solaris 11.2
+                           
+   3.3 General Setup Notes
+
+       o maxView Storage Manager supports Adaptec Series 8, Adaptec 
+         Series 7, and Adaptec Series 6 controllers. It is not backward
+         compatible with older Adaptec controller models. 
+
+       o maxView Storage Manager is not supported on FreeBSD. Use 
+         ARCCONF to create and manage arrays.
+   
+       o maxView Storage Manager and legacy Adaptec Storage Manager (ASM) 
+         cannot coexist on the same system.
+
+   3.4 Remote Access
+   
+       maxView Storage Manager requires the following range of ports
+       to be open for remote access: 
+       
+       o 34570-34580 (TCP)
+       o 34570 (UDP)
+       o 34577-34580 (UDP)
+       
+       See also Section 4.12 for OS-specific issues and workarounds.
+
+   3.5 Windows 8 Setup
+      
+       To log in and use maxView Storage Manager on a Windows 8 system,
+       you must create a local user account; you cannot use your
+       MS Live account. To create a local user account:
+          
+       1. Log into your MS Live account.       
+       2. Select Settings->Change PC Settings->Users->Switch to Local user.     
+       3. Provide account details.     
+       4. Start maxView Storage Manager and log in with your local user
+          account credentials.
+ 
+   3.6 SLES Setup       
+       
+       o Due to a JRE conflict, maxView Storage Manager is not 
+         supported on SLES 10 SP2/SP3 (x32, x64), and SLES 10 SP4 (x32).
+         
+         WORKAROUND: Install SLES 10 SP4 64-bit then replace the 64-bit 
+         JRE with a 32-bit JRE. Alternatively, use ARCCONF for storage
+         management on SLES 10 systems.
+       
+       o To avoid a problem with launching maxView Storage Manager on
+         SLES 11 x64 systems with DHCP enabled, ensure that the 
+         /etc/hosts file maps the server IP address to a valid host  
+         name; it is not sufficient to map the IP address to 'localhost'.
+
+   3.7 Ubuntu Setup 
+   
+       o To avoid a maxView Login failure on Ubuntu systems, you must
+         ensure that the root user account is enabled. (It is disabled,
+         by default, on Ubuntu 14.04 and later because no password is set.) 
+         
+         For example: sudo bash; sudo passwd root 
+
+       o When upgrading maxView Storage Manager on an existing Ubuntu  
+         Linux x64 installation, you must enable the upgrade switch 
+         before installing the maxView .deb package:
+
+         export maxView_Upgrade=true 
+         dpkg -i StorMan-*.deb 
+
+         To uninstall maxView after the upgrade:
+
+         export maxView_Upgrade=false 
+         dpkg -r storman        
+
+   3.8 Bootable USB Image Security Warnings
+   
+       When running maxView Storage Manager from the bootable USB 
+       image, you may be prompted with one or more with security 
+       warnings before maxView launches. In each case, acknowledge 
+       the warning and continue.
+       
+   3.9 RAW Device Setup
+    
+       On Adaptec Series 7 and Adaptec Series 8 controllers, a RAW 
+       Pass Through device is analogous to a JBOD, supported by Adaptec  
+       Series 6 controllers and older. Any drive without Adaptec RAID 
+       metadata is exposed to the OS as a RAW Pass Through device. To 
+       remove the Adaptec metadata and convert the drive to a RAW device, 
+       use the Uninitialize command in maxView Storage Manager; any 
+       existing data on the drive is destroyed. (You can also run 
+       uninit from the BIOS or ARCCONF.) For more information about 
+       working with RAW devices, see 'controller modes' in the CLI 
+       User's Guide, and BIOS 'general settings' in the RAID Controller
+       Installation and User's Guide.
+       
+  3.10 maxView Plugin for VMware vSphere Web Client
+
+       The maxView Plugin for VMware vSphere Web Client is supported
+       on VMware 5.5 only.
+
+  3.11 Firmware Downgrade on Series 8 Board Revision "B1"
+
+       Firmware downgrade from maxView Storage Manager, ARCCONF or the
+       BIOS is not supported on Adaptec Series 8 RAID controllers with 
+       Board Revision "B1" (the newest board revision). Older firmware  
+       versions do not support Board Revision "B1".
+
+  3.12 Uninstallation Issues
+       
+       o When uninstalling maxView Storage Manager on Fedora Linux, 
+         the OS displays a series of warning messages about missing
+         files. These messages can be ignored; the uninstallation 
+         completes successfully.
+
+         WORKAROUND: To avoid the warnings, uninstall maxView with
+         './StorMan-1.06-21032.i386.bin --remove' rather than
+         'rpm -e StorMan'.
+
+       o When using the 'Modify' option to uninstall maxView Storage
+         Manager on Windows, the 'Adaptec' folder is not removed from
+         the file system.         
+                               
+--------------------------------------------------------------------
+4. Known Limitations   
+
+   4.1 Login Issues on Windows Domain Server
+   
+       If the maxView login account doesn't have local administrative 
+       rights, login will fail with an error message: 'Invalid Username
+       or Password'. On domain servers running later versions of Microsoft
+       Windows Server, where no local administrator exists or can be 
+       created, maxView login is not possible. Use ARCCONF to create 
+       and manage arrays.
+       
+   4.2 Hot Spare Issues
+         
+       o After using a global hot spare to rebuild a redundant logical
+         drive, maxView Storage Manager displays an erroneous event 
+         message: "Deleted dedicated hot spare drive for logical device". 
+         In fact, the message should read "Logical device X is no longer
+         protected by hot spare drive Y".
+         	 
+       o maxView Storage Manager allows you to un-assign a global hot
+	 spare drive while copyback is in progess. This procedure is 
+	 not recommended. 
+	 
+   4.3 Dual-Controller Systems
+       
+       In dual-controller systems, the controller order in maxView
+       Storage Manager and the BIOS differs. Example: with an
+       Adaptec 72405 and 7805 installed, the BIOS reports 
+       the 72405 as controller 1 and the 7805 as controller 2; 
+       in the GUI, the controller order is reversed.
+          
+   4.4 Email Notifications
+   
+       o On Linux systems, we recommend adding the SMTP host name
+         to the /etc/hosts file. Doing so ensures that email 
+         notifications will succeed if you specify the email 
+         server in maxView Storage Manager by host name. Otherwise, 
+         email notifications (including test messages) may fail if
+         the DNS is unable to resolve the host hame. 
+         
+         WORKAROUND: specify the email server in maxView Storage
+         Manager by IP address.
+
+       o On CentOS 5.9 x64, email notifications may not be sent for 
+         logical drive creations, degraded logical drives, or logical 
+         drives that are rebuilding or fully rebuilt.
+                   
+   4.5 SGPIO Enclosures
+       
+       In this release, maxView Storage Manager does not show connector
+       information for SGPIO enclosures.
+         
+   4.6 Non-RAID Mode Controllers
+       
+       maxView Storage Manager can "see" RAID controllers operating
+       in HBA mode, Auto-Volume mode, and Simple Volume mode (Adaptec
+       Series 7 and Adaptec Series 8 controllers only). However, to 
+       change the controller mode, you must use ARCCONF or the BIOS.       
+       
+   4.7 RAID-Level Migrations
+    
+       o The following RAID-level migrations (RLM) are supported in
+         this release:
+       
+         RAID 0 to RAID 5
+         RAID 0 to RAID 10
+         RAID 5 to RAID 6
+         RAID 6 to RAID 5
+         RAID 10 to RAID 5
+         RAID 5 to RAID 10
+         RAID 1 to RAID 5
+         SIMPLE VOLUME to RAID 1
+         RAID 1 to SIMPLE VOLUME
+         
+       o When migrating a Simple Volume to RAID 1, maxView Storage
+         Manager reports the logical drive state as Impacted (rather
+         than Reconfiguring); this is normal.
+
+       o We do not recommend performing a RAID-level migration or 
+         Online Capacity Expansion (OCE) on a logical drive with 
+         maxCache SSD caching enabled.
+         
+         NOTE: maxView Storage Manager grays out the options for logical
+         drives with maxCache enabled. ARCCONF terminates the task.
+       
+       o Always allow a RAID-level migration to complete before creating
+         a support archive file. Otherwise, the support archive will 
+         include incorrect partition information. Once the migration is
+         complete, the partition information will be reported correctly.
+
+   4.8 maxCache Device Migration
+   
+       Only one maxCache Device is supported per controller. Moving
+       the maxCache Device (all underlying SSDs) from one
+       controller to another (assuming both controllers support 
+       maxCache) is supported only if (1) the new controller does not 
+       have a maxCache Device or any other maxCache Device with a 
+       conflicting device number and (2) only after a clean shutdown
+       on the old controller.
+
+   4.9 ARCCONF maxCache Device Size Issue 
+
+       ARCCONF supports >2TB maxCache Devices if you create the
+       device with the 'max' parameter. However, the functional
+       limit for the maxCache Device is 2TB, which is also the 
+       limit in maxView Storage Manager.                 
+       
+  4.10 Browser Issues
+          
+       o To run maxView Storage Manager on the supported browsers,
+         Javascript must be enabled. 
+
+       o Due to a certificate bug in Firefox 31.x, maxView login
+         may fail on RHEL systems with a "Secure Connection" error. 
+         (Firefox 31.1 is the default browser on RHEL 6.6; on 
+         RHEL 7.1, it is 31.4.)
+         
+         WORKAROUND: Upgrade to Firefox 36.
+
+       o With the default Security setting in Microsoft Internet 
+         Explorer 10 and 11, you may be unable to login to maxView   
+         Storage Manager or experience certain GUI display issues 
+         in the maxView online Help system.
+       
+         WORKAROUND: Change the default Security setting from High 
+         (or Medium-High) to Medium. Alternative: add the GUI IP 
+         address to the trusted sites list.
+
+       o With Google Chrome, the scrollbar resets itself to the top
+         after selecting a drive in the Logical Drive wizard. To 
+         select another drive, you must scroll back down to the 
+         drive location.
+
+       o With Microsoft Internet Explorer 10, the controller 
+         firmware update wizard does not show the f/w update   
+         file name when the upload completes. To refresh the
+         display, click Next then Back.
+
+       o We do not recommend using multiple browsers simultaneously
+         on the same maxView instance. Doing so may cause display
+         issues or freezes; to restore maxView, refresh the
+         display by pressing F5.
+           
+  4.11 Remote System Access on Linux and Windows
+       
+       To avoid remote system access failures from Linux and Windows 
+       clients running maxView Storage Manager, check and update one 
+       or all of the following system and network settings:
+       
+       Windows:
+       
+       o Ensure that the DNS server information is properly configured
+       
+       RHEL/Linux:
+       
+       o Set server.properties file permissions to at least read-only at all levels
+
+         1. Stop all maxView services. 
+         2. Set the Permissions of server.properties file to read and write or read-only 
+            at all levels (Owner, Group and Others). Apply and close. 
+         3. Restart all services in the given order - cim, agent, tomcat 
+         4. Now try to remote login to this system from any other system 
+       
+       o Check/update these network settings:
+       
+         1. Disable SELinux 
+         2. Disable firewall.
+         3. Disable the ipv6 in the system, if ipconfig shows both ipv4 and ipv6 address. 
+         4. Remove the virtual bridge virbr0, if present
+         5. Enter local ip address in 'localip' parameter in server.properties file 
+                   
+  4.12 Power Management Issues
+   
+       o Power management is not supported on FreeBSD.
+       
+       o Capturing support logs from maxView or ARCCONF will spin up
+         drives when power management is active. This behavior is by design.
+
+       o For logical drives comprised of SSDs only, the Power Tab in
+         maxView Storage Manager is disabled. 
+
+       o The Logical Drive Creation wizard does not save the power
+         management settings after the logical drive is created. 
+         It is always disabled. 
+         
+         WORKAROUND: Enable power management for the logical drive
+         from the Set Properties window.
+  
+  4.13 RAID 50/RAID 60, Max Drives
+   
+       The maximum number of drives in a RAID 50 or RAID 60 differ
+       between maxView Storage Manager, ARCCONF, and the BIOS:
+       
+       o BIOS and ARCCONF: 128 drives max
+          
+         RAID 50 - From 2-16 legs with 3-32 drives/leg
+         RAID 60 - From 2-16 legs with 4-16 drives/leg
+    
+       o maxView Storage Manager:  
+       
+         Assumes 2 legs for RAID 50/RAID 60 (non-selectable)
+         RAID 50 2-32 drives/leg (64 total) 
+         RAID 60 2-16 drives/leg (32 total)
+
+  4.14 RAID 10 Segment Order
+  
+       maxView Storage Manager and the Ctrl-A BIOS report the wrong
+       segment order for RAID 10s, regardless of the order in which
+       the drives are selected. 
+           
+       Example 1:  Create RAID 10 with 2 SDDs and 2 HDDs in maxView Storage Manager:
+           
+       (1a) ARCCONF and maxView Storage Manager see the following RAID segment order:
+                Device 2 (S1)
+                Device 1 (H2)
+                Device 3 (S2)
+                Device 0 (H1)
+   
+       (1b) the BIOS/CTRL-A sees the following RAID segment order:
+                Device 2 (S1)
+                Device 1 (H2)
+                Device 0 (H1)
+                Device 3 (S2)
+   
+       (1c) the correct and expected RAID segment order is:
+                Device 2 (S1)
+                Device 0 (H1)
+                Device 3 (S2)
+                Device 1 (H2)
+                
+       Example 2:  Create RAID 10 with 2 SDDs and 2 HDDs with ARCCONF:
+  
+       (2a) the BIOS/CTRL-A sees the following RAID segment order:
+                      Device 0 (H1)
+                      Device 2 (S1)
+                      Device 1 (H2)
+                      Device 3 (S2)
+  
+       (2b) ARCCONF and maxView Storage Manager see the correct RAID segment order:
+                      Device 2 (S1)
+                      Device 0 (H1)
+                      Device 3 (S2)
+                      Device 1 (H2)
+  
+  4.15 RAID 10 Rebuild Order 
+   
+       With a degraded RAID 10 logical drive, the drive is rebuilt
+       one leg at a time, not in parallel.  
+         
+  4.16 Verify with Fix
+  
+       In maxView Storage Manager and ARCCONF, the Verify with Fix
+       operation is NOT available when: 
+       
+       1. The logical drive has a non-redundant RAID level
+       2. Other tasks are in progress on the logical drive
+       3. The logical drive is in a non-optimal or impacted state
+       
+  4.17 Locate Logical Drive Blink LED
+  
+       In maxView Storage Manager, Locate Logical Drive continues to
+       blink the LED for a pulled physical drive in the array after 
+       the locate action is stopped. (For unpulled drives, the blinking
+       stops.) This issue is not seen with ARCCONF.
+                    
+  4.18 ATA Secure Erase
+  
+       In ARCCONF, the ATA Secure Erase operation cannot be aborted.
+       Once started, it continues to completion. 
+       
+       NOTE: ATA Secure Erase is also available in the Ctrl-A BIOS. 
+       and maxView Storage Manager.
+
+  4.19 ARCCONF Backward Compatibility
+
+       ARCCONF is backward compatible with older Adaptec controller
+       models. As a result, the ARCCONF user's guide and online help
+       show command options that are not supported by newer Adaptec
+       controllers, like the Adaptec Series 7 and Adaptec Series 8. 
+       
+       Example: 
+              
+       o With ARCCONF SETMAXCACHE, Adaptec Series 7 and Series 8 
+         controllers do not support ADDTOPOOL or REMOVEFROMPOOL                                     
+  
+  4.20 Adaptec Series 6 Controller Issues
+        
+       The following issues are seen only with Adaptec Series 6 RAID
+       controllers:
+                                       
+       o In maxView Storage Manager, the Preserve Cache option on the  
+         Set Properties window is not supported on Series 6 RAID
+         controllers. Attempting to set this option for the Series 6 
+         controller fails.
+
+       o Renaming a RAID volume disables the write-cache (if enabled).
+         You cannot re-enable the write-cache in maxView Storage Manager.
+          
+         WORKAROUND: Use ARCCONF to enable the write-cache.
+        
+       o In a VMware Guest OS under VMware 5.x, maxView Storage Manager
+         and ARCCONF do not detect existing logical drive partitions. 
+         As a result, attempting to delete, clear, or erase the logical
+         drive may fail.
+
+       o On Series 6 controllers, maxView Storage Manager deletes   
+         partitioned JBODs without issuing a warning message. 
+         
+       o Series 6 controllers do not support the ARCCONF GETPERFORM command.
+
+  4.21 Simple Volume Support
+       
+       o In this release, you can create a maximum of 128 Simple 
+         Volumes in maxView Storage Manager, ARCCONF, or the BIOS.
+
+       o When a Simple Volume fails, the status remains unchanged  
+         after drive replacement. 
+
+         WORKAROUND: Manually delete the Simple Volume to remove it.
+         
+  4.22 Auto-Volume Support 
+
+       o Changing a controller into Auto-Volume mode (ARCCONF/BIOS) is not
+         supported if the configuration includes any logical device type  
+         other than Simple Volume, including a maxCache Device. The mode
+         switch from RAID mode to Auto-Volume mode is blocked if any other
+         type of logical volume exists (including maxCache). After
+         switching to Auto-Volume mode, you can create and delete Simple
+         Volumes only in maxView Storage Manager and ARCCONF.
+
+       o In Auto-Volume mode, only the first 128 RAW drives are converted 
+         to Simple Volumes; the rest of the RAW drives remain unchanged. 
+         If you uninitialize a Ready drive while the controller is in
+         Auto-Volume mode, the firmware converts the drive automatically
+         until the Simple Volume count reaches the maximum.
+            
+  4.23 Hot-Removing Disk Drives on Xenserver Guest OS
+
+       XenServer does not support "hot-removal" of disk drives from a 
+       partitioned logical drive. As a result, if you hot remove a disk  
+       from a logical drive, the Guest OS becomes inaccessible because   
+       the drive partition remains visible to the OS instead of being 
+       cleared.
+
+       WORKAROUND: Reboot the XenServer host, detach the failed 
+       partition, then restart the VM.
+
+  4.24 Updating Hard Disk Firmware on VMware Guest OS 
+
+       Updating the firmware for a SAS hard disk drive with ARCCONF/maxView 
+       can crash (PSOD) the VMware Guest OS. This issue is seen with SAS 
+       hard drives only; with SATA drives, the firmware update completes 
+       successfully.
+
+  4.25 Creating a Support Archive on a Guest OS
+  
+       To create a support archive on a VMware or Xenserver Guest OS,
+       use maxView Storage Manager only. Creating a support archive 
+       with ARCCONF is not supported in this release.
+  
+  4.26 Enclosure Status Reporting
+  
+       Enclosure status, in maxView Storage Manager, is event-driven.
+       As a result, enclosures can have a "Degraded" status even if
+       related resources (fan, temperature, power) are performing
+       normally (Optimal status). For instance, the Enclosure status
+       changes to "Degraded" if the system reports an "Enclosure device
+       not responding ..." event, even if other sensor values are normal. 
+
+  4.27 PHY Status on Enclosure Backplanes  
+
+       In the Controller Properties window, maxView Storage Manager shows
+       the Connector Info as "unknown" for all PHYs on an enclosure-based 
+       backplane (for instance, a backplane attached to connector 1).
+
+  4.28 Special Characters in Logical Device Names
+  
+       Special characters are permitted in logical device names
+       in maxView Storage Manager, the BIOS, and ARCCONF. However,
+       with Linux ARCCONF (create, setname), special characters  
+       must be "escaped" to ensure proper interpretation. For 
+       example:
+              
+       ARCCONF SETNAME 1 LOGICALDRIVE 1 arc_ldrive%\$12\& 
+
+  4.29 Speaker Status on SuperMicro SAS2X28 Enclosures
+
+       SuperMicro SAS2X28 enclosures do not propagate the speaker
+       status to maxView Storage Manager. As a result, maxView 
+       always displays the speaker status as Off.
+
+  4.30 Changing Read and Write Cache Settings for a Logical Drive
+
+       maxView Storage Manager does not allow you to change the 
+       read-cache and write-cache settings for a logical drive in  
+       one step. You must click OK after each change.
+
+  4.31 Online Help Issues 
+
+       When opening the maxView Storage Manager help from a remote
+       Linux system (eg, over a VPN), the help window may fail to 
+       open with a 'can't establish connection to server' message.
+         
+       WORKAROUND: replace 127.0.0.1:8443 in the URL with <system_ip_address>:8443
+                                           
+--------------------------------------------------------------------
+(c) 2015 PMC-Sierra, Inc. All Rights Reserved. 
+
+This software is protected under international copyright laws and 
+treaties. It may only be used in accordance with the terms 
+of its accompanying license agreement.
+
+The information in this document is proprietary and confidential to
+PMC-Sierra, Inc., and for its customers' internal use. In any event,
+no part of this document may be reproduced or redistributed in any
+form without the express written consent of PMC-Sierra, Inc.,  
+1380 Bordeaux Drive, Sunnyvale, CA 94089.
+
+P/N DOC-01768-05-A Rev A

i386/2.01/License.txt

@@ -0,0 +1,292 @@
+International License Agreement for Non-Warranted Programs
+
+Part 1 - General Terms 
+
+PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE PROGRAM.
+Adaptec WILL LICENSE THE PROGRAM TO YOU ONLY IF YOU FIRST ACCEPT THE
+TERMS OF THIS AGREEMENT. BY USING THE PROGRAM YOU AGREE TO THESE
+TERMS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT,
+PROMPTLY RETURN THE UNUSED PROGRAM TO THE PARTY (EITHER Adaptec OR
+ITS RESELLER) FROM WHOM YOU ACQUIRED IT TO RECEIVE A REFUND OF
+THE AMOUNT YOU PAID. 
+
+The Program is owned by (Adaptec) or a supplier of Adaptec 
+and is copyrighted and licensed, not sold. 
+
+The term "Program" means the original program and all whole or
+partial copies of it. A Program consists of machine-readable
+instructions, its components, data, audio-visual content (such
+as images, text, recordings, or pictures), and related licensed
+materials. 
+
+This Agreement includes Part 1 - General Terms and Part 2 
+Country unique Terms and is the complete agreement regarding the
+use of this Program, and replaces any prior oral or written
+communications between you and Adaptec. The terms of Part 2 may
+replace or modify those of Part 1. 
+
+
+1. License 
+
+Use of the Program 
+
+Adaptec grants you a nonexclusive license to use the Program. 
+
+You may 1) use the Program to the extent of authorizations you
+have acquired and 2) make and install copies to support the
+level of use authorized, providing you reproduce the copyright
+notice and any other legends of ownership on each copy, or
+partial copy, of the Program. 
+
+If you acquire this Program as a program upgrade, your
+authorization to use the Program from which you upgraded is
+terminated. 
+
+You will ensure that anyone who uses the Program does so only in
+compliance with the terms of this Agreement. 
+
+You may not 1) use, copy, modify, or distribute the Program
+except as provided in this Agreement; 2) reverse assemble,
+reverse compile, or otherwise translate the Program except as
+specifically permitted by law without the possibility of
+contractual waiver; or 3) sublicense, rent, or lease the
+Program. 
+
+Transfer of Rights and Obligations 
+
+You may transfer all your license rights and obligations under a
+Proof of Entitlement for the Program to another party by
+transferring the Proof of Entitlement and a copy of this
+Agreement and all documentation. The transfer of your license
+rights and obligations terminates your authorization to use the
+Program under the Proof of Entitlement. 
+
+
+2. Proof of Entitlement 
+
+The Proof of Entitlement for this Program is evidence of your
+authorization to use this Program and of your eligibility for
+future upgrade program prices (if announced) and potential
+special or promotional opportunities. 
+
+
+3. Charges and Taxes 
+
+Adaptec defines use for the Program for charging purposes and
+specifies it in the Proof of Entitlement. Charges are based on
+extent of use authorized. If you wish to increase the extent of
+use, notify Adaptec or its reseller and pay any applicable charges.
+Adaptec does not give refunds or credits for charges already due or
+paid. 
+
+If any authority imposes a duty, tax, levy or fee, excluding
+those based on Adaptec's net income, upon the Program supplied by
+Adaptec under this agreement, then you agree to pay that amount 
+as Adaptec specifies or
+supply exemption documentation. 
+
+
+4. No Warranty 
+
+SUBJECT TO ANY STATUTORY WARRANTIES WHICH CAN NOT BE EXCLUDED,
+Adaptec MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
+INCLUDING WITHOUT LIMITATION, THE WARRANTY OF NON-INFRINGEMENT
+AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+PARTICULAR PURPOSE, REGARDING THE PROGRAM OR TECHNICAL SUPPORT,
+IF ANY. Adaptec MAKES NO WARRANTY REGARDING THE CAPABILITY OF THE
+PROGRAM TO CORRECTLY PROCESS, PROVIDE AND/OR RECEIVE DATE DATA
+WITHIN AND BETWEEN THE 20TH AND 21ST CENTURIES. 
+
+The exclusion also applies to any of Adaptec's subcontractors,
+suppliers, or program developers (collectively called
+"Suppliers"). 
+
+Manufacturers, suppliers, or publishers of non-Adaptec Programs may
+provide their own warranties. 
+
+
+5. Limitation of Liability 
+
+NEITHER Adaptec NOR ITS SUPPLIERS WILL BE LIABLE FOR ANY DIRECT OR
+INDIRECT
+
+DAMAGES, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
+SAVINGS, OR ANY INCIDENTAL, SPECIAL, OR OTHER ECONOMIC
+CONSEQUENTIAL DAMAGES, EVEN IF Adaptec IS INFORMED OF THEIR
+POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
+LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE
+EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU. 
+
+
+6. General 
+
+Nothing in this Agreement affects any statutory rights of
+consumers that cannot be waived or limited by contract. 
+
+Adaptec may terminate your license if you fail to comply with the
+terms of this Agreement. If Adaptec does so, you must immediately
+destroy the Program and all copies you made of it. 
+
+You agree to comply with applicable export laws and regulations. 
+
+Neither you nor Adaptec will bring a legal action under this
+Agreement more than two years after the cause of action arose
+unless otherwise provided by local law without the possibility
+of contractual waiver or limitation. 
+
+Neither you nor Adaptec is responsible for failure to fulfill any
+obligations due to causes beyond its control. 
+
+Adaptec does not provide program services or technical support,
+unless Adaptec specifies otherwise. 
+
+The laws of the country in which you acquire the Program govern
+this Agreement, except 1) in Australia, the laws of the State or
+Territory in which the transaction is performed govern this
+Agreement; 2) in Albania, Armenia, Belarus, Bosnia/Herzegovina,
+Bulgaria, Croatia, Czech Republic, Georgia, Hungary, Kazakhstan,
+Kirghizia, Former Yugoslav Republic of Macedonia
+(FYROM), Moldova, Poland, Romania, Russia, Slovak Republic,
+Slovenia, Ukraine, and Federal Republic of Yugoslavia, the laws
+of Austria govern this Agreement; 3) in the United Kingdom, all
+disputes relating to this Agreement will be governed by English
+Law and will be submitted to the exclusive jurisdiction of the
+English courts; 4) in Canada, the laws in the Province of
+Ontario govern this Agreement; and 5) in the United States and
+Puerto Rico, and People's Republic of China, the laws of the 
+State of New York govern this Agreement. 
+
+
+Part 2 - Country-unique Terms 
+
+
+AUSTRALIA: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Although Adaptec specifies that there are no warranties, you may
+have certain rights under the Trade Practices Act 1974 or other
+legislation and are only limited to the extent permitted by the
+applicable legislation. 
+
+Limitation of Liability (Section 3): 
+The following paragraph is added to this Section: 
+
+Where Adaptec is in breach of a condition or warranty implied by the
+Trade Practices Act 1974, Adaptec's liability is limited to the
+repair or replacement of the goods, or the supply of equivalent
+goods. Where that condition or warranty relates to right to
+sell, quiet possession or clear title, or the goods are of a
+kind ordinarily acquired for personal, domestic or household use
+or consumption, then none of the limitations in this paragraph
+apply. 
+
+
+GERMANY:
+
+No Warranty (Section 4):
+The following paragraphs are added to this Section:
+
+The minimum warranty period for Programs is six months.
+
+In case a Program is delivered without Specifications, we will
+only warrant that the Program information correctly describes
+the Program and that the Program can be used according to the
+Program information. You have to check the usability according
+to the Program information within the "money-back guaranty"
+period.
+
+Limitation of Liability (Section 5):
+The following paragraph is added to this Section:
+
+The limitations and exclusions specified in the Agreement will
+not apply to damages caused by Adaptec with fraud or gross
+negligence, and for express warranty. 
+
+
+INDIA: 
+
+General (Section 6): 
+The following replaces the fourth paragraph of this Section: 
+
+If no suit or other legal action is brought, within two years
+after the cause of action arose, in respect of any claim that
+either party may have against the other, the rights of the
+concerned party in respect of such claim will be forfeited and
+the other party will stand released from its obligations in
+respect of such claim. 
+
+
+IRELAND: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Except as expressly provided in these terms and conditions, all
+statutory conditions, including all warranties implied, but
+without prejudice to the generality of the foregoing, all
+warranties implied by the Sale of Goods Act 1893 or the Sale of
+Goods and Supply of Services Act 1980 are hereby excluded. 
+
+
+ITALY:
+
+Limitation of Liability (Section 5):
+This Section is replaced by the following:
+
+Unless otherwise provided by mandatory law, Adaptec is not liable
+for any damages which might arise. 
+
+
+NEW ZEALAND: 
+
+No Warranty (Section 4): 
+The following paragraph is added to this Section: 
+
+Although Adaptec specifies that there are no warranties, you may
+have certain rights under the Consumer Guarantees Act 1993 or
+other legislation which cannot be excluded or limited. The
+Consumer Guarantees Act 1993 will not apply in respect of any
+goods or services which Adaptec provides, if you require the goods
+and services for the purposes of a business as defined in that
+Act. 
+
+Limitation of Liability (Section 5): 
+The following paragraph is added to this Section: 
+
+Where Programs are not acquired for the purposes of a business
+as defined in the Consumer Guarantees Act 1993, the limitations
+in this Section are subject to the limitations in that Act. 
+
+
+PEOPLE'S REPUBLIC OF CHINA:
+
+Charges (Section 3):
+The following paragraph is added to the Section:
+
+All banking charges incurred in the People's Republic of China
+will be borne by you and those incurred outside the People's
+Republic of China will be borne by Adaptec. 
+
+
+UNITED KINGDOM: 
+
+Limitation of Liability (Section 5): 
+The following paragraph is added to this Section at the end of
+the first paragraph: 
+
+The limitation of liability will not apply to any breach of
+Adaptec's obligations implied by Section 12 of the Sales of Goods
+Act 1979 or Section 2 of the Supply of Goods and Services Act
+1982. 
+
+
+UNITED STATES AND CANADA:
+
+No Country-unique Terms apply.
+
+
+By continuing with the installation of the Program, you are 
+accepting the terms and conditions above.
+

i386/2.01/README.TXT

@@ -0,0 +1,819 @@
+README.TXT: Adaptec maxView Storage Manager & 
+ARCCONF Command Line Interface Utility 
+as of March 22, 2016
+--------------------------------------------------------------------
+Please check the product website for the later versions of this 
+file to ensure you are reviewing the latest information. This 
+file contains important information about issues and errata 
+that were discovered after completion of the standard 
+product documentation.
+
+In the case of conflict between various parts of the documentation 
+set, this file contains the most current information.
+
+Table of Contents
+1. New Features of this Release
+2. Software Versions and Documentation
+	2.1. Utility Software
+	2.2. Documentation
+		4.2.2.1. Series 6, 7, 8 Controller Documentation
+		4.2.2.2. HBA 1000 Series Product Documentation
+		4.2.2.3. SmartIOC Product Documentation
+3. Installation Notes
+	3.1. Installation and Setup
+	3.2. Supported Operating Systems
+		3.2.1. Series 6, 7, 8 Controllers
+		3.2.2. Smart Family Controllers
+	3.3. General Setup Notes
+	3.4. Remote Access
+	3.5. Windows 8 Setup
+	3.6. SLES Setup
+	3.7. Ubuntu Setup
+	3.8. Bootable USB Image Security Warnings
+	3.9. RAW Device Setup (Series 6, 7, 8 Only)
+	3.10. maxView Plugin for VMware vSphere Web Client
+4. Known Limitations
+	4.1. Global Limitations
+		4.1.1. Dual-Controller Systems
+		4.1.2. Email Notifications
+		4.1.3. SGPIO Enclosures
+		4.1.4. Non-RAID Mode Controllers
+		4.1.5. Browser Issues
+		4.1.6. Remote System Access on Linux and Windows
+		4.1.7. RAID 10 Segment Order
+		4.1.8. RAID 10 Rebuild Order
+		4.1.9. Locate Logical Drive Blink LED
+		4.1.10. ARCCONF Backward Compatibility
+		4.1.11. Updating Hard Disk Firmware on VMware Guest OS
+		4.1.12. Hot Swap Issues on VMware CentOS Guest OS
+		4.1.13. Enclosure Status Reporting
+		4.1.14. PHY Status on Enclosure Backplanes
+		4.1.15. Special Characters in Logical Device Names
+		4.1.16. Speaker Status on SuperMicro SAS2X28 Enclosures
+		4.1.17. Online Help Issues
+		4.1.18. Broadcasting Alerts About Status and Activity
+	4.2. Limitations Specific to Series 6, 7, 8 Controllers
+		4.2.1. RAID-Level Migrations
+		4.2.2. maxCache Device Migration
+		4.2.3. ARCCONF maxCache Device Size Issue
+		4.2.4. Power Management Issues
+		4.2.5. Verify with Fix
+		4.2.6. ATA Secure Erase
+		4.2.7. Series 6 Controller Issues
+		4.2.8. Simple Volume Support
+		4.2.9. Auto-Volume Support
+		4.2.10. Hot-Removing Disk Drives on Xenserver Guest OS
+		4.2.11. Changing Read and Write Cache Settings for Logical Drive
+	4.3. Limitations Specific to Smart Family Controllers
+		4.3.1. SES Passthrough Commands to Expanders
+		4.3.2. Firmware Upgrade Issues
+
+
+1. New Features of this Release
+
+	o Added new features:
+		- New command to identify a device by blinking its LEDs.
+		- Segment and Group Information of a RAID 10 Logical 
+		  Device can now be displayed.
+		- A new UNINIT/TASK command to clear drive configuration 
+		  for physical devices containing RAID Information Sector 
+		  (RIS) that have been masked in order to protect the 
+		  configuration data.
+		- Ability to show SGPIO virtual SEP information to show 
+		  enclosure devices for SGPIO backplanes.
+		- For cases where a logical drive fails, the array status 
+		  is now reported.
+		- Ability to display physical drive mount point information.
+		- Ability to display logical drive mount point information.
+		- Verify Write support is provided. 
+		- Linux Hyper-V is supported for the maxView Storage Manager.
+	o For Smart family products, added support for Citrix XenServer.
+	o Bugfixes
+
+
+2. Software Versions and Documentation
+
+	2.1. Utility Software
+	
+		o Microsemi Adaptec maxView Storage Manager 
+		  Version 2.01.00  (22268)
+		o Microsemi Adaptec ARCCONF Command Line Interface 
+		  Utility Version 2.01.00  (22268)
+		
+	2.2. Documentation
+	
+		2.2.1. Series 6, 7, 8 Controller Documentation
+		
+			PDF Format (English/Japanese)
+			o maxView Storage Manager User's Guide
+			o Adaptec RAID Controller Command Line Utility 
+			  User's Guide
+			
+			HTML and Text Format
+			o maxView Storage Manager Online Help
+			o maxView Storage Manager README.TXT file
+			
+		2.2.2. HBA 1000 Series Product Documentation
+		
+			PDF:
+			o Adaptec maxView Storage Manager User's Guide for 
+			  Smart-Family Controllers
+			o Adaptec HBA 1000 Series Command Line Utility 
+			  User's Guide
+			
+			HTML and Text Format:
+			o maxView Storage Manager for Smart-Family Controllers 
+			  Online Help
+			o maxView Storage Manager README.TXT file
+			
+		2.2.3. SmartIOC Product Documentation
+		
+			PDF:
+			o Adaptec maxView Storage Manager User's Guide for 
+			  Smart-Family Controllers
+			o Adaptec SmartIOC 2000 Command Line Utility User's 
+			  Guide
+			
+			HTML and Text Format:
+			o maxView Storage Manager for Smart-Family Controllers 
+			  Online Help
+			o maxView Storage Manager README.TXT file
+
+
+3. Installation Notes
+
+	3.1. Installation and Setup
+	
+		Refer to your product documentation for the correct 
+		installation and setup details:
+		o Your product Installation and User's Guide contains 
+		  complete installation information for your product's 
+		  drivers.
+		o The maxView Storage Manager User's Guide for your 
+		  product contains installation information for the 
+		  maxView Storage Manager software.
+		o The Command Line Utility User's Guide for your product 
+		  contains complete installation for ARCCONF.
+			
+	3.2. Supported Operating Systems
+	
+		3.2.1. Series 6, 7, 8 Controllers
+		
+			Microsoft Windows
+			o Microsoft Windows Server 2012 (64-bit)
+			o Microsoft Windows Server 2012 R2 (64-bit)
+			o Microsoft Windows Server 2008 R2 SP1 (64-bit)
+			o Microsoft Windows SBS 2011 (Standard and Essential)
+			o Microsoft Windows 10 (32-bit and 64-bit)
+			o Microsoft Windows 8.1 (32-bit and 64-bit)
+			o Microsoft Windows 7 (32-bit and 64-bit)
+			o Microsoft WinPE 8.1 (32-bit and 64-bit)
+			
+			Linux
+			o Red Hat Enterprise Linux/CentOS 7.2, 7.1 (64-bit)
+			o Red Hat Enterprise Linux/CentOS 6.7, 6.6 (64-bit)
+			o Red Hat Enterprise Linux/CentOS 5.11, 5.10 (64-bit)
+			o SuSE Linux Enterprise Server 12 SP1 (64-bit)
+			o SuSE Linux Enterprise Server 12 (64-bit)
+			o SuSE Linux Enterprise Server 11 SP4 and SP3 (64-bit)
+			o Debian Linux 8.1 (64-bit)
+			o Ubuntu Linux 14.04.3, 14.04 (64-bit)
+			o Ubuntu Linux 12.04.5 (64-bit)
+			o Fedora Linux 22 (64-bit)
+			
+			FreeBSD
+			o FreeBSD 10.2 (64-bit)
+			o FreeBSD 9.3 (64-bit)
+			
+			Virtual OS Environments
+			o VMware ESXi 6.0 (64-bit)
+			o VMware ESXi 5.5 U2 (64-bit)
+			o Citrix XenServer 6.5.1 (64-bit)
+			o Citrix XenServer 6.2 (32-bit)
+			
+			Solaris
+			o Solaris 11 (32-bit)
+			o Solaris 10 U9 (32-bit)
+			
+			Notes
+			1.	The ARCCONF Command Line Utility is supported on 
+				only 64-bit versions of Microsoft Windows and Linux.
+			2.	Boot USB (offline or pre-boot) for the ARCCONF Command 
+				Line Utility and maxView Storage Manager is supported 
+				in Linux.
+				
+		3.2.2. Smart Family Controllers
+		
+			Microsoft Windows
+			o Microsoft Windows  Server 2012 (64-bit)
+			o Microsoft Windows  Server 2012 R2 (64-bit)
+			o Microsoft Windows  Server 2008 R2 SP1 (64-bit)
+			o Microsoft Windows  SBS 2011 (Standard and Essential)
+			o Microsoft Windows  10 (32-bit and 64-bit)
+			o Microsoft Windows  8.1 (32-bit and 64-bit)
+			o Microsoft Windows 7 (32-bit and 64-bit)
+			
+			Linux
+			o Red Hat Enterprise Linux/CentOS 7.2, 7.1 (64-bit)
+			o Red Hat Enterprise Linux/CentOS 6.7, 6.6 (64-bit)
+			o Red Hat Enterprise Linux/CentOS 5.11, 5.10 (64-bit)
+			o SuSE Linux Enterprise Server 12 SP1 (64-bit)
+			o SuSE Linux Enterprise Server 12 (64-bit)
+			o SuSE Linux Enterprise Server 11 SP4 and SP3 (64-bit)
+			o Ubuntu Linux 14.04.3, 14.04 (64-bit)
+			o Ubuntu Linux 12.04.5 (64-bit)
+			
+			Virtual OS Environments
+			o VMware ESXi 6.0, ESXi U1 (64-bit)
+			o VMware ESXi 5.5 U2, ESXi 5.5 U3 (64-bit)
+			o Citrix XenServer 6.5.1 (64-bit)
+			o Citrix XenServer 6.2 (32-bit)
+			
+			Notes
+			1.	The ARCCONF Command Line Utility is supported on 
+				only 64-bit versions of Microsoft Windows and Linux.
+			2.	Boot USB (offline or pre-boot) for the ARCCONF Command 
+				Line Utility and maxView Storage Manager is supported 
+				in Linux.
+				
+	3.3. General Setup Notes
+	
+		o maxView Storage Manager is not backwards-compatible with 
+		  Series 5 and older Adaptec controller models.
+		o maxView Storage Manager and legacy Adaptec Storage Manager 
+		  (ASM) cannot coexist on the same system.
+		o For Series 6, 7, 8 controllers:
+			-	maxView Storage Manager is not supported on FreeBSD. 
+				Use ARCCONF to create and manage arrays.
+				
+	3.4. Remote Access
+	
+		maxView Storage Manager requires the following range of 
+		ports to be open for remote access:
+		o 34570-34580 (TCP)
+		o 34570 (UDP)
+		o 34577-34580 (UDP)
+		See also 4.1.6 for OS-specific issues and workarounds.
+		
+	3.5. Windows 8 Setup
+	
+		To log in and use maxView Storage Manager on a Windows 8 
+		system, you must create a local user account; you cannot 
+		use your MS Live account. 
+		To create a local user account:
+		1.	Log into your MS Live account.
+		2.	Select Settings->Change PC Settings->Users->Switch to 
+			Local user.
+		3.	Provide account details.
+		4.	Start maxView Storage Manager and log in with your 
+			local user account credentials.
+			
+	3.6. SLES Setup
+	
+		o To avoid a problem with launching maxView Storage 
+		  Manager on SLES 11 x64 systems with DHCP enabled, 
+		  ensure that the /etc/hosts file maps the server 
+		  IP address to a valid host name; it is not sufficient 
+		  to map the IP address to 'localhost'.
+			
+	3.7. Ubuntu Setup
+	
+		o To avoid a maxView Login failure on Ubuntu systems, 
+		  you must ensure that the root user account is enabled. 
+		  (It is disabled, by default, on Ubuntu 14.04 
+		  and later because no password is set.)
+		  For example: sudo bash; sudo passwd root
+		o When upgrading maxView Storage Manager on an existing 
+		  Ubuntu Linux x64 installation, you must enable the 
+		  upgrade switch before installing the maxView .deb 
+		  package:
+				export maxView_Upgrade=true 
+				dpkg -i StorMan-*.deb
+				To uninstall maxView after the upgrade:
+				export maxView_Upgrade=false 
+				dpkg -r storman
+			
+	3.8. Bootable USB Image Security Warnings
+	
+		When running maxView Storage Manager from the bootable 
+		USB image, you may be prompted with one or more with 
+		security warnings before maxView launches. In 
+		each case, acknowledge the warning and continue.
+		
+	3.9. RAW Device Setup (Series 6, 7, 8 Only)
+	
+		On Adaptec Series 7 and Adaptec Series 8 controllers, 
+		a RAW Pass Through device is analogous to a JBOD, supported 
+		by Adaptec Series 6 controllers and older. Any drive without 
+		Adaptec RAID metadata is exposed to the OS as a RAW Pass 
+		Through device. To remove the Adaptec metadata and convert 
+		the drive to a RAW device, use the Uninitialize command in 
+		maxView Storage Manager; any existing data on the drive is 
+		destroyed. (You can also run uninit from the BIOS or 
+		ARCCONF.) For more information about working with RAW devices, 
+		see 'controller modes' in the CLI User's Guide, and BIOS 
+		'general settings' in the RAID Controller Installation and 
+		User's Guide.
+		
+	3.10. maxView Plugin for VMware vSphere Web Client
+	
+		The maxView Plugin for VMware vSphere Web Client is 
+		supported on VMware 5.5 and 6.0.
+
+4. Known Limitations
+
+	4.1. Global Limitations
+	
+		4.1.1. Dual-Controller Systems
+		
+			In dual-controller systems, the controller order in 
+			maxView Storage Manager and the BIOS differs. Example: 
+			with an Adaptec 72405 and 7805 installed, the BIOS reports 
+			the 72405 as controller 1 and the 7805 as controller 2; 
+			in the GUI, the controller order is reversed.
+			
+		4.1.2. Email Notifications
+		
+			o On Linux systems, we recommend adding the SMTP host 
+			  name and the system IP address, to the /etc/hosts file. 
+			  Doing so ensures that email notifications will succeed 
+			  if you specify the email server in maxView Storage 
+			  Manager by host name. Otherwise, email notifications 
+			  (including test messages) may fail if the DNS is unable 
+			  to resolve the host name.
+				
+			  WORKAROUND: Specify the email server in maxView Storage 
+			  Manager by IP address.
+				
+			o On CentOS 5.9 x64, email notifications may not be sent 
+			  for logical drive creations, degraded logical drives, 
+			  or logical drives that are rebuilding or fully rebuilt.
+				
+		4.1.3. SGPIO Enclosures
+		
+			In this release, maxView Storage Manager does not show 
+			connector information for SGPIO enclosures.
+			
+		4.1.4. Non-RAID Mode Controllers
+		
+			maxView Storage Manager can "see" RAID controllers 
+			operating in HBA mode, Auto-Volume mode, and Simple Volume 
+			mode (Adaptec Series 7, Adaptec Series 8, Smart Family 
+			controllers only). However, to change the controller mode 
+			on Adaptec Series 7/8 controllers, you must use ARCCONF 
+			or the BIOS. With Adaptec Smart-Family controllers, you 
+			can also change the controller mode with maxView Storage 
+			Manager.
+			
+		4.1.5. Browser Issues
+		
+			To run maxView Storage Manager on the supported browsers. 
+			Javascript must be enabled.
+			
+			o Due to a certificate bug in Firefox 31.x, maxView 
+			  login may fail on RHEL systems with a "Secure 
+			  Connection" error. (Firefox 31.1 is the default 
+			  browser on RHEL 6.6; on RHEL 7.1, it is 31.4.)
+			  WORKAROUND: Upgrade to Firefox 36.
+				
+			o With the default Security setting in Microsoft 
+			  Internet Explorer 10 and 11, you may be unable to 
+			  login to maxView Storage Manager or experience 
+			  certain GUI display issues in the maxView online 
+			  Help system.
+			  WORKAROUND: Change the default Security setting 
+			  from High (or Medium-High) to Medium. 
+			  Alternative: add the GUI IP address to the trusted 
+			  sites list.
+				
+			o With Google Chrome, the scrollbar resets itself to 
+			  the top after selecting a drive in the Logical Drive 
+			  wizard. To select another drive, you must 
+			  scroll back down to the drive location.
+				
+			o With Microsoft Internet Explorer 10, the controller 
+			  firmware update wizard does not show the f/w update 
+			  file name when the upload completes. To refresh 
+			  the display, click Next then Back.
+				
+			o We do not recommend using multiple browsers 
+			  simultaneously on the same maxView 
+			  instance. Doing so may cause display issues or freezes; 
+			  to restore maxView, refresh the display by pressing F5.
+				
+		4.1.6. Remote System Access on Linux and Windows
+		
+			To avoid remote system access failures from Linux 
+			and Windows clients running maxView Storage Manager, 
+			check and update one or all of the following system 
+			and network settings:
+			
+			Windows:
+			o Ensure that the DNS server information is properly 
+			  configured
+			
+			RHEL/Linux:
+			
+			o Set server.properties file permissions to at least 
+			  read-only at all levels
+				1.	Stop all maxView services.
+				2.	Set the Permissions of server.properties file to 
+					read and write or read-only at all levels 
+					(Owner, Group and Others). 
+				3.	Apply and close.
+				4.	Restart all services in the given order - cim, 
+					agent, tomcat
+				5.	Now try to remote login to this system from any 
+					other system
+				
+			o Check/update these network settings:
+				1.	Disable SELinux
+				2.	Disable firewall.
+				3.	Disable the ipv6 in the system, if ipconfig shows 
+					both ipv4 and ipv6 address.
+				4.	Remove the virtual bridge virbr0, if present
+				5.	Enter local ip address in 'localip' parameter in 
+					server.properties file
+					
+		4.1.7. RAID 10 Segment Order
+		
+			maxView Storage Manager and the Ctrl-A BIOS report the 
+			wrong segment order for RAID 10s, regardless of the order 
+			in which the drives are selected.
+			Example 1: Create RAID 10 with 2 SDDs and 2 HDDs in maxView 
+			Storage Manager:
+			
+				(1a) ARCCONF and maxView Storage Manager see the 
+					following RAID segment order: 
+							Device 2 (S1) 
+							Device 1 (H2) 
+							Device 3 (S2) 
+							Device 0 (H1) 
+				
+				(1b) the BIOS/CTRL-A sees the following RAID segment 
+					order: 
+							Device 2 (S1) 
+							Device 1 (H2) 
+							Device 0 (H1) 
+							Device 3 (S2) 
+				
+				(1c) the correct and expected RAID segment order is: 
+							Device 2 (S1) 
+							Device 0 (H1) 
+							Device 3 (S2) 
+							Device 1 (H2)
+							
+			Example 2: Create RAID 10 with 2 SDDs and 2 HDDs 
+			with ARCCONF:
+			
+				(2a) the BIOS/CTRL-A sees the following RAID segment 
+					order: 
+								  Device 0 (H1) 
+								  Device 2 (S1) 
+								  Device 1 (H2) 
+								  Device 3 (S2) 
+			   
+				(2b) ARCCONF and maxView Storage Manager see the 
+					correct RAID segment order: 
+								  Device 2 (S1) 
+								  Device 0 (H1) 
+								  Device 3 (S2) 
+								  Device 1 (H2)
+								  
+		4.1.8. RAID 10 Rebuild Order
+		
+			With a degraded RAID 10 logical drive, the drive is 
+			rebuilt one leg at a time, not in parallel.
+			
+		4.1.9. Locate Logical Drive Blink LED
+		
+			In maxView Storage Manager, Locate Logical Drive 
+			continues to blink the LED for a pulled physical drive 
+			in the array after the locate action is stopped. 
+			(For unpulled drives, the blinking stops.) This issue is 
+			not seen with ARCCONF.
+			
+		4.1.10. ARCCONF Backward Compatibility
+		
+			ARCCONF is backward compatible with older Adaptec 
+			controller models. As a result, the ARCCONF user's guide 
+			and online help show command options that are not 
+			supported by newer Adaptec controllers, like the 
+			Adaptec Series 7 and Adaptec Series 8 or later products.
+			
+			Example: With ARCCONF SETMAXCACHE, Adaptec Series 7 and 
+			Series 8 controllers do not support ADDTOPOOL or 
+			REMOVEFROMPOOL
+			
+		4.1.11. Updating Hard Disk Firmware on VMware Guest OS
+		
+			Updating the firmware for a SAS hard disk drive with 
+			ARCCONF/maxView can crash (PSOD) the VMware Guest OS. 
+			This issue is seen with SAS hard drives only; with 
+			SATA drives, the firmware update completes successfully.
+
+		4.1.12. Hot Swap Issues on VMware CentOS Guest OS
+		
+			Due to a limitation with the VMware CentOS Guest OS 
+			network configuration, maxView Storage Manager does not 
+			show newly added or removed hot swap drives. 
+			(ARCCONF sees the configuration change but maxView 
+			does not.)
+			
+			WORKAROUND: (1) reboot the system or restart maxView 
+			services; (2) adjust the network configuration; contact 
+			Adaptec Support for more information.
+			
+		4.1.13. Enclosure Status Reporting
+		
+			Enclosure status, in maxView Storage Manager, is 
+			event-driven. As a result, enclosures can have a 
+			"Degraded" status even if related resources (fan, 
+			temperature, power) are performing normally (Optimal 
+			status). For instance, the Enclosure status changes 
+			to "Degraded" if the system reports an "Enclosure 
+			device not responding ..." event, even if other sensor 
+			values are normal.
+			
+		4.1.14. PHY Status on Enclosure Backplanes
+		
+			In the Controller Properties window, maxView Storage 
+			Manager shows the Connector Info as "unknown" for all 
+			PHYs on an enclosure-based backplane (for instance, a 
+			backplane attached to connector 1).
+			
+		4.1.15. Special Characters in Logical Device Names
+		
+			Special characters are permitted in logical device 
+			names in maxView Storage Manager, the BIOS, and ARCCONF. 
+			However, with Linux ARCCONF (create, setname), special 
+			characters must be "escaped" to ensure proper 
+			interpretation. For example:
+			
+			ARCCONF SETNAME 1 LOGICALDRIVE 1 arc_ldrive%\$12\&
+			
+		4.1.16. Speaker Status on SuperMicro SAS2X28 Enclosures
+		
+			SuperMicro SAS2X28 enclosures do not propagate 
+			the speaker status to maxView Storage Manager. As 
+			a result, maxView always displays the speaker 
+			status as Off.
+			
+		4.1.17. Online Help Issues
+		
+			o When opening the maxView Storage Manager help 
+			  from a remote Linux system (eg, over a VPN), the 
+			  help window may fail to open with a 'can't establish 
+			  connection to server' message.
+			
+			  WORKAROUND: replace 127.0.0.1:8443 in the URL with 
+			  <system_ip_address>:8443
+				
+			o In IE11, topics in the help may display with a 'Topics 
+			  Not Found' message when their corresponding links are 
+			  clicked in the navigation pane of the help.
+				
+			  WORKAROUND: click on the "Add" browser link to add 
+			  certification to view the content.
+			
+		4.1.18. Broadcasting Alerts About Status and Activity
+		
+		This feature is not supported by the maxView Storage 
+		Manager or ARCCONF and has been removed from the product 
+		documentation.
+		
+	4.2. Limitations Specific to Series 6, 7, 8 Controllers
+	
+		4.2.1. RAID-Level Migrations
+		
+			o The following RAID-level migrations (RLM) are 
+			  supported in this release:
+				-	RAID 0 to RAID 5
+				-	RAID 0 to RAID 10
+				-	RAID 5 to RAID 6
+				-	RAID 6 to RAID 5
+				-	RAID 10 to RAID 5
+				-	RAID 5 to RAID 10
+				-	RAID 1 to RAID 5
+				-	SIMPLE VOLUME to RAID 1
+				-	RAID 1 to SIMPLE VOLUME
+				
+			o When migrating a Simple Volume to RAID 1, maxView 
+			  Storage Manager reports the logical drive state as 
+			  Impacted (rather than Reconfiguring); 
+			  this is normal.
+				
+			o We do not recommend performing a RAID-level 
+			  migration or Online Capacity Expansion (OCE) 
+			  on a logical drive with maxCache SSD caching 
+			  enabled.
+				
+			  NOTE: maxView Storage Manager grays out the 
+			  options for logical drives with maxCache enabled. 
+			  ARCCONF terminates the task.
+				
+			o Always allow a RAID-level migration to complete 
+			  before creating a support archive file. Otherwise, 
+			  the support archive will include incorrect 
+			  partition information. Once the migration is 
+			  complete, the partition information will be reported 
+			  correctly.
+				
+		4.2.2. maxCache Device Migration
+		
+			Only one maxCache Device is supported per controller. 
+			Moving the maxCache Device (all underlying SSDs) from 
+			one controller to another (assuming both controllers 
+			support maxCache) is supported only if (1) the new 
+			controller does not have a maxCache Device or any other 
+			maxCache Device with a conflicting device number and 
+			(2) only after a clean shutdown 
+			on the old controller.
+			
+		4.2.3. ARCCONF maxCache Device Size Issue
+		
+			ARCCONF supports >2TB maxCache Devices if you create 
+			the device with the 'max' parameter. However, the 
+			functional limit for the maxCache Device is 2TB, 
+			which is also the limit in maxView Storage Manager.
+			
+		4.2.4. Power Management Issues
+		
+			o Power management is not supported on FreeBSD.
+			
+			o Capturing support logs from maxView or ARCCONF 
+			  will spin up drives when power management is 
+			  active. This behavior is by design.
+				
+			o The Logical Drive Creation wizard no longer 
+			  includes the option to enable power management settings.
+				
+			  WORKAROUND: Enable power management for the 
+			  logical drive from the Set Properties window.
+				
+		4.2.5. Verify with Fix
+		
+			In maxView Storage Manager and ARCCONF, the Verify 
+			with Fix operation is NOT available when:
+			
+			1.	The logical drive has a non-redundant RAID level
+			2.	Other tasks are in progress on the logical drive
+			3.	The logical drive is in a non-optimal or impacted state
+			
+		4.2.6. ATA Secure Erase
+		
+			In ARCCONF, the ATA Secure Erase operation cannot 
+			be aborted. Once started, it continues to completion.
+			
+			NOTE: ATA Secure Erase is also available in the 
+			Ctrl-A BIOS and maxView Storage Manager.
+			
+		4.2.7. Series 6 Controller Issues
+		
+			The following issues are seen only with Adaptec 
+			Series 6 RAID controllers:
+			o In maxView Storage Manager, the Preserve Cache 
+			  option on the Set Properties window is not 
+			  supported on Series 6 RAID controllers. Attempting 
+			  to set this option for the Series 6 controller fails.
+				
+			o Renaming a RAID volume disables the write-cache 
+			  (if enabled). You cannot re-enable the write-cache 
+			  in maxView Storage Manager.
+				
+			  WORKAROUND: Use ARCCONF to enable the write-cache.
+				
+			o In a VMware Guest OS under VMware 5.x, maxView 
+			  Storage Manager and ARCCONF do not detect existing 
+			  logical drive partitions. As a result, 
+			  attempting to delete, clear, or erase the logical 
+			  drive may fail.
+				
+			o On Series 6 controllers, maxView Storage Manager 
+			  deletes partitioned JBODs without issuing a 
+			  warning message.
+				
+			o Series 6 controllers do not support the ARCCONF 
+			  GETPERFORM command.
+			
+		4.2.8. Simple Volume Support
+		
+			o In this release, you can create a maximum of 128 
+			  Simple Volumes in maxView Storage Manager, ARCCONF, 
+			  or the BIOS.
+				
+			o When a Simple Volume fails, the status remains 
+			  unchanged after drive replacement.
+				
+			  WORKAROUND: Manually delete the Simple Volume to 
+			  remove it.
+				
+		4.2.9. Auto-Volume Support
+		
+			o Changing a controller into Auto-Volume mode 
+			  (ARCCONF/BIOS) is not supported if the configuration 
+			  includes any logical device type other than Simple 
+			  Volume, including a maxCache Device. The mode switch 
+			  from RAID mode to Auto-Volume mode is blocked if any 
+			  other type of logical volume exists (including 
+			  maxCache). After switching to Auto-Volume mode, 
+			  you can create and delete Simple Volumes 
+			  only in maxView Storage Manager and ARCCONF.
+				
+			o In Auto-Volume mode, only the first 128 RAW drives 
+			  are converted to Simple Volumes; the rest of the 
+			  RAW drives remain unchanged. If you uninitialize 
+			  a Ready drive while the controller is in Auto-Volume 
+			  mode, the firmware converts the drive automatically 
+			  until the Simple Volume count reaches the maximum.
+				
+		4.2.10. Hot-Removing Disk Drives on Xenserver Guest OS
+		
+			XenServer does not support "hot-removal" of disk 
+			drives from a partitioned logical drive. As a result, 
+			if you hot remove a disk from a logical drive, 
+			the Guest OS becomes inaccessible because the drive 
+			partition remains visible to the OS instead of being cleared.
+			
+			WORKAROUND: Reboot the XenServer host, detach the 
+			failed partition, then restart the VM.
+			
+		4.2.11. Changing Read and Write Cache Settings for 
+			Logical Drive
+		
+			maxView Storage Manager does not allow you to change 
+			the read-cache and write-cache settings for a logical drive 
+			in one step. You must click OK after each change.
+			
+	4.3. Limitations Specific to Smart Family Controllers
+	
+		4.3.1. SES Passthrough Commands to Expanders
+		
+			SES passthrough commands to expanders fail.
+			
+		4.3.2 Firmware Upgrade Issues
+			
+			For systems using Adaptec HBA 1000 with an Adaptec 
+			SAS Expander 82885T card, where the ARCCONF utility 
+			is used to upgrade the expander firmware, ARCCONF 
+			may crash if 64-bit chunk sizes are used.  
+			
+			WORKAROUND: Use 32-bit chunk sizes to upgrade/downgrade 
+			the expander firmware.
+
+
+
+Copyright 2016 Microsemi Corporation. All rights reserved. 
+Microsemi and the Microsemi logo are trademarks of Microsemi 
+Corporation. All other trademarks and service marks are 
+the property of their respective owners.
+
+PMC-2153191, Issue 2
+
+Microsemi Corporation (Nasdaq: MSCC) offers a comprehensive 
+portfolio of semiconductor and system solutions for communications, 
+defense and security, aerospace, and industrial markets. 
+Products include high-performance and radiation-hardened 
+analog mixed-signal integrated circuits, FPGAs, SoCs, and 
+ASICs; power management products; timing and synchronization 
+devices and precise time solutions; voice processing devices; 
+RF solutions; discrete components; enterprise storage and 
+communications solutions; security technologies and scalable 
+anti-tamper products; Ethernet solutions; Power-over-Ethernet 
+ICs and midspans; custom design capabilities and services. 
+Microsemi is headquartered in Aliso Viejo, California and has 
+approximately 4,800 employees world-wide. 
+Learn more at www.microsemi.com.
+
+Microsemi makes no warranty, representation, or guarantee 
+regarding the information contained herein or the suitability 
+of its products and services for any particular purpose, 
+nor does Microsemi assume any liability whatsoever arising 
+out of the application or use of any product or circuit. 
+The products sold hereunder and any other products sold 
+by Microsemi have been subject to limited testing and should 
+not be used in conjunction with mission-critical equipment 
+or applications. Any performance specific ations are believed 
+to be reliable but are not verified, and Buyer must conduct 
+and complete all performance and other testing of the products, 
+alone and together with, or installed in, any end-products. 
+Buyer shall not rely on any data and performance specifications 
+or parameters provided by Microsemi. It is the Buyer's 
+responsibility to independently determine suitability of 
+any products and to test and verify the same. The information 
+provided by Microsemi hereunder is provided as is, where is 
+and with all faults, and the entire risk associated with such 
+information is entirely with the Buyer. Microsemi does not 
+grant, explicitly or implicitly, to any party any patent 
+rights, licenses, or any other IP rights, whether with regard 
+to such information itself or anything described by 
+such information. Information provided in this document is 
+proprietary to Microsemi, and Microsemi reserves the right 
+to make any changes to the information in this document or 
+to any products and services at any time without notice.
+
+The technology discussed in this document may be protected by 
+one or more patent grants.
+
+ 
+ 

i386/7.31/README.TXT

@@ -0,0 +1,678 @@
+--------------------------------------------------------------------
+README.TXT
+
+Adaptec Storage Manager (ASM)
+
+as of May 7, 2012
+--------------------------------------------------------------------
+Please review this file for important information about issues
+and erratas that were discovered after completion of the standard
+product documentation. In the case of conflict between various
+parts of the documentation set, this file contains the most
+current information.
+
+The following information is available in this file:
+
+   1. Software Versions and Documentation
+      1.1   Adaptec Storage Manager
+      1.2   Documentation
+   2. Installation and Setup Notes
+      2.1   Supported Operating Systems
+      2.2   Minimum System Requirements
+      2.3   General Setup Notes
+      2.4   Linux Setup Notes 
+      2.5   Debian Linux Setup Notes
+   3. General Cautions and Notes
+      3.1   General Cautions
+      3.2   General Notes
+   4. Operating System-Specific Issues and Notes
+      4.1   Windows - All
+      4.2   Windows 64-Bit
+      4.3   Linux
+      4.4   Debian and Ubuntu
+      4.5   FreeBSD
+      4.6   Fedora and FreeBSD
+      4.7   Linux and FreeBSD
+      4.8   VMware
+   5. RAID Level-Specific Notes
+      5.1   RAID 1 and RAID 5 Notes
+      5.2   RAID 10 Notes
+      5.3   RAID x0 Notes
+      5.4   RAID Volume Notes
+      5.5   JBOD Notes
+      5.6   Hybrid RAID Notes
+      5.7   RAID-Level Migration Notes
+   6. Power Management Issues and Notes
+   7. "Call Home" Issues and Notes
+   8. ARCCONF Issues and Notes   
+   9. Other Issues and Notes
+
+--------------------------------------------------------------------
+1. Software Versions and Documentation
+
+   1.1. Adaptec Storage Manager Version 7.3.1, ARCCONF Version 7.3.1
+
+   1.2. Documentation on this DVD
+
+        PDF format*:
+
+        -  Adaptec Storage Manager User's Guide
+        -  Adaptec RAID Controller Command Line Utility User's Guide
+        
+        *Requires Adobe Acrobat Reader 4.0 or later
+        
+        HTML and text format:
+        
+        -  Adaptec Storage Manager Online Help        
+        -  Adaptec Storage Manager README.TXT file
+        
+--------------------------------------------------------------------
+2. Installation and Setup Notes
+  
+   - The Adaptec Storage Manager User's Guide contains complete installation
+     instructions for the Adaptec Storage Manager software. The Adaptec
+     RAID Controllers Command Line Utility User's Guide contains 
+     complete installation instructions for ARCCONF, Remote ARCCONF,
+     and the Adaptec CIM Provider. The Adaptec RAID Controllers 
+     Installation and User's Guide contains complete installation
+     instructions for Adaptec RAID controllers and drivers.
+     
+   2.1 Supported Operating Systems
+             
+     - Microsoft Windows*:
+
+       o Windows Server 2008, 32-bit and 64-bit
+       o Windows Server 2008 R2, 64-bit
+       o Windows SBS 2011, 32-bit and 64-bit
+       o Windows Storage Server 2008 R2, 32-bit and 64-bit
+       o Windows Storage Server 2011, 32-bit and 64-bit
+       o Windows 7, 32-bit and 64-bit
+     
+     *Out-of-box and current service pack   
+
+     - Linux:
+
+       o Red Hat Enterprise Linux 5.7, 6.1, IA-32 and x64
+       o SuSE Linux Enterprise Server 10, 11, IA-32 and x64     
+       o Debian Linux 5.0.7, 6.0 IA-32 and x64       
+       o Ubuntu Linux 10.10, 11.10, IA-32 and x64       
+       o Fedora Linux 14, 15, 16 IA-32 and x64
+       o Cent OS 5.7, 6.2, IA-32 and x64
+       o VMware ESXi 5.0, VMware ESX 4.1 Classic (Agent only)
+
+     - Solaris:
+     
+       o Solaris 10, 
+       o Solaris 11 Express      
+             
+     - FreeBSD:
+      
+       o FreeBSD 7.4, 8.2
+           
+   2.2 Minimum System Requirements
+
+     o  Pentium Compatible 1.2 GHz processor, or equivalent
+     o  512 MB RAM
+     o  135 MB hard disk drive space
+     o  Greater than 256 color video mode   
+  
+   2.3 General Setup Notes 
+
+   - You can configure Adaptec Storage Manager settings on other
+     servers exactly as they are configured on one server. To
+     replicate the Adaptec Storage Manager Enterprise view tree   
+     and notification list, do the following:
+
+     1.  Install Adaptec Storage Manager on one server.
+
+     2.  Start Adaptec Storage Manager. Using the 'Add remote system' 
+         action, define the servers for your tree.
+
+     3.  Open the Notification Manager. Using the 'Add system' 
+         action, define the notification list.
+
+     4.  Exit Adaptec Storage Manager.
+
+     5.  Copy the following files onto a diskette from the directory
+         where the Adaptec Storage Manager is installed:
+
+         RaidMSys.ser --> to replicate the tree
+         RaidNLst.ser --> to replicate the notification list
+         RaidSMTP.ser --> to replicate the SMTP e-mail notification list
+         RaidJob.ser  --> to replicate the jobs in the Task Scheduler
+
+     6.  Install Adaptec Storage Manager on the other servers.
+
+     7.  Copy the files from the diskette into the directory where
+         Adaptec Storage Manager is installed on the other servers.
+
+   2.4 Linux Setup Notes
+   
+   - Because the RPM for Red Hat Enterprise Linux 5 is unsigned, the
+     installer reports that the package is "Unsigned, Malicious Software". 
+     Ignore the message and continue the installation.
+
+   - To run Adaptec Storage Manager under Red Hat Enterprise Linux for 
+     x64, the Standard installation with "Compatibility Arch Support"
+     is required. 
+
+   - To install Adaptec Storage Manager on Red Hat Enterprise Linux,
+     you must install two packages from the Red Hat installation CD:
+     
+     o  compat-libstdc++-7.3-2.96.122.i386.rpm
+     o  compat-libstdc++--devel-7.3-2.96.122.i386.rpm
+                   
+     NOTE:  The version string in the file name may be different 
+            from above. Be sure to check the version string on the 
+            Red Hat CD.
+     
+     For example, type:
+            
+     rpm --install /mnt/compat-libstdc++-7.3-2.96.122.i386.rpm
+            
+     where mnt is the mount point of the CD-ROM drive.            
+
+   - To install Adaptec Storage Manager on Red Hat Enterprise Linux 5,
+     you must install one of these packages from the Red Hat
+     installation CD:
+       
+     o  libXp-1.0.0-8.i386.rpm    (32-Bit)
+     o  libXp-1.0.0-8.x86.rpm     (64-Bit)
+
+   - To install Adaptec Storage Manager on SuSE Linux Enterprise  
+     Desktop 9, Service Pack 1, for 64-bit systems, you must install    
+     two packages from the SuSE Linux installation CD:
+     
+     - liblcms-devel-1.12-55.2.x86_64.rpm
+     - compat-32bit-9-200502081830.x86_64.rpm
+                   
+     NOTE:  The version string in the file name may be different 
+            from above. Be sure to check the version string on the 
+            installation CD.
+         
+   - To enable ASM's hard drive firmware update feature on RHEL 64-bit
+     systems, you must ensure that the "sg" module is loaded in the  
+     kernel. To load the module manually (if it is not loaded already),  
+     use the command "modprobe sg".                 
+   
+   2.5 Debian Linux Setup Notes
+
+   - You can use the ASM GUI on Debian Linux 5.x only if you install
+     the GNOME desktop. Due to a compatibility issue with X11, the
+     default KDE desktop is not supported in this release.
+          
+   - To ensure that the ASM Agent starts automatically when Debian
+     is rebooted, you must update the default start and stop values
+     in /etc/init.d/stor_agent, as follows:
+     
+     ·[Original]
+     # Default-Start:    2 3 5
+     # Default-Stop:     0 1 2 6
+     
+     ·[Modification]
+     # Default-Start:    2 3 4 5
+     # Default-Stop:     0 1 6
+     
+     To activate the changes, execute 'insserv stor_agent', as root.
+                
+--------------------------------------------------------------------
+3. Adaptec Storage Manager General Cautions and Notes
+
+   3.1 General Cautions
+   
+   - This release supports a maximum of 8 concurrent online capacity 
+     expansion (OCE) tasks in the RAID array migration wizard.         
+
+   - While building or clearing a logical drive, do not remove and 
+     re-insert any drive from that logical drive. Doing so may cause
+     unpredictable results.
+
+   - Do not move disks comprising a logical drive from one controller 
+     to another while the power is on. Doing so could cause the loss of
+     the logical drive configuration or data, or both. Instead, power 
+     off both affected controllers, move the drives, and then restart.
+
+   - When using Adaptec Storage Manager and the CLI concurrently, 
+     configuration changes may not appear in the Adaptec Storage 
+     Manager GUI until you refresh the display (by pressing F5).
+
+   3.2 General Notes
+
+   - Adaptec Storage Manager requires the following range of ports
+     to be open for remote access: 34570-34580 (TCP), 34570 (UDP),
+     34577-34580 (UDP).
+     
+   - Adaptec Storage Manager generates log files automatically to
+     assist in tracking system activity.  The log files are
+     created in the directory where Adaptec Storage Manager is
+     installed.  
+   
+     o RaidEvt.log  - Contains the information reported in 
+                      Adaptec Storage Manager event viewer for all
+                      local and remote systems.
+
+     o RaidEvtA.log - Contains the information reported in 
+                      Adaptec Storage Manager event viewer for the
+                      local system.
+                       
+     o RaidNot.log  - Contains the information reported in the
+                      Notification Manager event viewer.
+                                              
+     o RaidErr.log  - Contains Java messages generated by 
+                      Adaptec Storage Manager.
+                    
+     o RaidErrA.log - Contains Java messages generated by the
+                      Adaptec Storage Manager agent.
+                      
+     o RaidCall.log - Contains the information reported when 
+                      statistics logging is enabled in ASM.
+                      
+     Information written to these files is appended to the existing
+     files to maintain a history. However, when an error log file
+     reaches a size of 5 Mbytes, it is copied to a new file with 
+     the extension .1 and the original (that is, the .LOG file) is 
+     deleted and recreated. For other log files, a .1 file is created
+     when the .LOG file reaches a size of 1 Mbyte. If a .1 file already 
+     exists, the existing .1 file is destroyed.
+
+   - In the Event viewer, Adaptec Storage Manager reports both the 
+     initial build task for a logical drive and a subsequent Verify/Fix
+     as a "Build/Verify" task.
+   
+   - When displaying information about a physical device, the device, 
+     vendor and model information may be displayed incorrectly.
+
+   - After using a hot spare to successfully rebuild a redundant 
+     logical drive, Adaptec Storage Manager will continue to  
+     show the drive as a global hot spare. To remove the hot spare 
+     designation, delete it in Adaptec Storage Manager.
+          
+--------------------------------------------------------------------
+4. Operating System-Specific Issues and Notes
+
+   4.1 Windows - All
+             
+   - The Java Virtual Machine has a problem with the 256-color 
+     palette. (The Adaptec Storage Manager display may be distorted 
+     or hard to read.) Set the Display Properties Settings to a  
+     color mode with greater than 256 colors.      
+  
+   - When you shut down Windows, you might see the message 
+     "unexpected shutdown". Windows displays this message if the
+     Adaptec Storage Manager Agent fails to exit within 3 seconds. 
+     It has no effect on file I/O or other system operations and can
+     be ignored.        
+
+   4.2 Windows 64-Bit
+        
+   - Adaptec RAID controllers do not produce an audible alarm on the 
+     following 64-bit Windows operating systems:
+
+     o  Windows Server 2003 x64 Edition (all versions)
+                 
+   4.3 Linux
+
+   - When you delete a logical drive, the operating system can no longer 
+     see the last logical drive. WORKAROUND: To allow Linux to see the  
+     last logical drive, restart your system.
+
+   - The controller does not support attached CD drives during OS 
+     installation.    
+                                         
+   - On certain versions of Linux, you may see messages concerning font 
+     conversion errors. Font configuration under X-Windows is a known 
+     JVM problem. It does not affect the proper operation of the  
+     Adaptec Storage Manager software. To suppress these messages,  
+     add the following line to your .Xdefaults file:
+       
+     stringConversionWarnings: False
+     
+   4.4 Debian and Ubuntu
+
+   - To create logical drives on Debian and Ubuntu installations, you
+     must log in as root. It is not sufficient to start ASM with the
+     'sudo /usr/StorMan/StorMan.sh' command (when not logged in as 
+     root). WORKAROUND: To create logical drives on Ubuntu when not
+     logged in as root, install the package 'sudo dpkg -i storm_6.50-15645_amd64.deb'.  
+   
+   4.5 FreeBSD         
+   
+   - On FreeBSD systems, JBOD disks created with Adaptec Storage Manager
+     are not immediately available to the OS. You must reboot the  
+     system before you can use the JBOD.
+  
+   4.6 Fedora and FreeBSD
+ 
+   - Due to an issue with the Java JDialog Swing class, the 'Close' 
+     button may not appear on some Adaptec Storage Manager windows  
+     or dialog boxes under FreeBSD or Fedora Linux 15 or higher. 
+     WORKAROUND: Press ALT+F4 or right-click on the title bar, then 
+     close the dialog box from the pop-up menu. 
+
+   4.7 Linux and FreeBSD
+       
+   - If you cannot connect to a local or remote Adaptec Storage Manager  
+     installed on a Linux or FreeBSD system, verify that the TCP/IP hosts   
+     file is configured properly.
+          
+     1.  Open the /etc/hosts file.
+           
+         NOTE:  The following is an example:
+               
+                127.0.0.1 localhost.localdomain localhost matrix
+           
+     2.  If the hostname of the system is identified on the line
+         with 127.0.0.1, you must create a new host line.
+           
+     3.  Remove the hostname from the 127.0.0.1 line.
+           
+         NOTE:  The following is an example:
+               
+                127.0.0.1 localhost.localdomain localhost
+    
+     4.  On a new line, type the IP address of the system.
+           
+     5.  Using the Tab key, tab to the second column and enter the 
+         fully qualified hostname.
+               
+     6.  Using the Tab key, tab to the third column and enter the 
+         nickname for the system.
+               
+         NOTE:  The following is an example of a completed line:
+     
+                1.1.1.1 matrix.localdomain matrix
+                      
+                where 1.1.1.1 is the IP address of the server and
+                matrix is the hostname of the server.
+               
+     7.  Restart the server for the changes to take effect.   
+   
+   4.8 VMware
+           
+   - If you are unable to connect to VMware ESX Server from a 
+     remote ASM GUI, even though it appears in the Enterprise 
+     View as a remote system, most likely, some required ports
+     are open and others are not. (The VMware ESX firewall blocks 
+     most ports, by default.) Check to make sure that all ports 
+     34570 thru 34581 are opened on the ESX server. 
+
+   - After making array configuration changes in VMware, you must  
+     run the "esxcfg-rescan" tool manually at the VMware console
+     to notify the operating system of the new target characteristics
+     and/or availability. Alternatively, you can rescan from the 
+     Virtual Infrastructure Client: click on the host in the left 
+     panel, select the Configuration tab, choose "Storage Adapters", 
+     then, on the right side of the screen, click "Rescan".
+     
+   - With VMware ESX 4.1, the OS command 'esxcfg-scsidevs -a'  
+     incorrectly identifies the Adaptec ASR-5445 controller as 
+     "Adaptec ASR5800". (ASM itself identifies the controller 
+     correctly.) To verify the controller name at the OS level,  
+     use this command to check the /proc file system:
+     
+     # cat /proc/scsi/aacraid/<Node #>
+
+     where <Node #> is 1, 2, 3 etc.
+                                                                  
+--------------------------------------------------------------------
+5. RAID Level-Specific Notes
+
+   5.1 RAID 1 and RAID 5 Notes
+
+   - During a logical device migration from RAID 1 or RAID 5 to  
+     RAID 0, if the original logical drive had a spare drive
+     attached, the resulting RAID 0 retains the spare drive. 
+     Since RAID 0 is not redundant, you can remove the hot spare.
+
+   5.2 RAID 10 Notes
+
+   - If you force online a failed RAID 10, ASM erroneously shows two 
+     drives rebuilding (the two underlying member drives), not one.
+
+   - You cannot change the priority of a RAID 10 verify. Setting
+     the priority at the start of a verify has no effect. The
+     priority is still shown as high. Changing the priority of
+     a running verify on a RAID-10 changes the displayed priority
+     until a rescan is done, then the priority shows as high again.
+
+   - Performing a Verify or Verify/Fix on an RAID 10 displays the 
+     same message text in the event log: "Build/Verify started on 
+     second level logical drive of 'LogicalDrive_0.'" You may see the  
+     message three times for a Verify, but only once for a Verify/Fix.
+          
+   5.3 RAID x0 Notes
+
+   - To create a RAID x0 with an odd number of drives (15, 25, etc),
+     specify an odd number of second-level devices in the Advanced
+     settings for the array. For a 25 drive RAID 50, for instance,
+     the default is 24 drives.  
+     
+     NOTE: This differs from the BIOS utility, which creates RAID x0
+           arrays with an odd number of drives by default. 
+        
+   - After building or verifying a leg of a second-level logical drive,  
+     the status of the second-level logical drive is displayed as a  
+     "Quick Initialized" drive.
+     
+   5.4 RAID Volume Notes
+   
+   - In ASM, a failed RAID Volume comprised of two RAID 1 logical 
+     drives is erroneously reported as a failed RAID 10. A failed   
+     RAID Volume comprised of two RAID 5 logical drives is  
+     erroneously reported as a failed RAID 50.
+      
+   5.5 JBOD Notes
+     
+   - In this release, ASM deletes partitioned JBODs without issuing 
+     a warning message.
+   
+   - When migrating a JBOD to a Simple Volume, the disk must be quiescent
+     (no I/O load). Otherwise, the migration will fail with an I/O Read 
+     error. 
+
+   5.6 Hybrid RAID Notes
+
+   - ASM supports Hybrid RAID 1 and RAID 10 logical drives comprised
+     of hard disk drives and Solid State Drives (SSDs). For a Hybrid 
+     RAID 10, you must select an equal number of SSDs and HDDs in   
+     “every other drive” order, that is: SSD—HDD—SSD—HDD, and so on. 
+     Failure to select drives in this order creates a standard 
+     logical drive that does not take advantage of SSD performance. 
+     
+   5.7 RAID-Level Migration (RLM) Notes            
+  
+   - We strongly recommend that you use the default 256KB stripe 
+     size for all RAID-level migrations. Choosing a different stripe  
+     size may crash the system.
+   
+   - If a disk error occurs when migrating a 2TB RAID 0 to RAID 5
+     (eg, bad blocks), ASM displays a message that the RAID 5 drive
+     is reconfiguring even though the migration failed and no 
+     RAID-level migration task is running. To recreate the
+     logical drive, fix or replace the bad disk, delete the RAID 5
+     in ASM, then try again.
+  
+   - When migrating a RAID 5EE, be careful not to remove and re-insert
+     a drive in the array. If you do, the drive will not be included 
+     when the array is rebuilt. The migration will stop and the drive  
+     will be reported as Ready (not part of array).
+     
+     NOTE: We strongly recommend that you do not remove and re-insert  
+           any drive during a RAID-level migration. 
+
+   - When migrating a RAID 6 to a RAID 5, the migration will fail if 
+     the (physical) drive order on the target logical device differs    
+     from the source; for instance, migrating a four-drive RAID 6 to
+     a three-drive RAID 5.     
+     
+   - Migrating a RAID 5 with greater than 2TB capacity to RAID 6 or 
+     RAID 10 is not supported in this release. Doing so may crash
+     the system.
+     
+  -  When migrating from a RAID 0 to any redundant logical drive,  
+     like RAID 5 or 10, Adaptec Storage Manager shows the status as  
+     "Degraded Reconfiguring" for a moment, then the status changes  
+     to "Reconfiguring." The "Degraded" status does not appear in  
+     the event log.
+
+   - The following RAID-level migrations and online capacity 
+     expansions (OCE) are NOT supported:
+     
+     o RAID 50 to RAID 5 RLM
+     o RAID 60 to RAID 6 RLM
+     o RAID 50 to RAID 60 OCE
+
+   - During a RAID-level migration, ASM and the BIOS utility show
+     different RAID levels while the migration is in progress. ASM shows
+     the target RAID level; the BIOS utility shows the current RAID level.
+     
+   - If a disk error occurs during a RAID-level migration (eg, bad blocks),   
+     the exception is reported in the ASM event viewer (bottom pane)
+     and in the support archive file (Support.zip, Controller 1 logs.txt), 
+     but not in the main ASM Event Log file, RaidEvtA.log.   
+      
+   - Always allow a RAID-level migration to complete before gathering
+     support archive information in Support.zip. Otherwise, the Support.zip 
+     file will include incorrect partition information. Once the RLM is 
+     complete, the partition information will be reported correctly.     
+     
+--------------------------------------------------------------------
+6. Power Management Issues and Notes
+
+   - You must use a compatible combination of Adaptec Storage Manager  
+     and controller firmware and driver software to use the power  
+     management feature. All software components must support power
+     management. You can download the latest controller firmware 
+     and drivers from the Adaptec Web site at www.adaptec.com.
+ 
+   - Power management is not supported under FreeBSD.
+   
+   - Power management settings apply only to logical drives in the 
+     Optimal state. If you change the power settings on a Failed 
+     logical drive, then force the drive online, the previous 
+     settings are reinstated.
+     
+   - After setting power values for a logical drive in ARCCONF, the
+     settings are not updated in the Adaptec Storage Manager GUI.
+   
+--------------------------------------------------------------------
+7. "Call Home" Issues and Notes
+    
+   - The Call Home feature is not supported in this release. To gather  
+     statistics about your system for remote analysis, enable statistics   
+     logging in ASM, then create a Call Home Support Archive. For more   
+     information, see the user's guide.     
+     
+--------------------------------------------------------------------
+8. ARCCONF Issues and Notes
+
+   - With VMware ESX 4.1, you cannot delete a logical drive 
+     with ARCCONF. WORKAROUND: Connect to the VMware machine from a 
+     remote ASM GUI, then delete the logical drive.
+
+   - With Linux kernel versions 2.4 and 2.6, the ARCCONF 
+     DELETE <logical_drive> command may fail with a Kernel Oops 
+     error message. Even though the drives are removed from the 
+     Adaptec Storage Manager GUI, they may not really be deleted. 
+     Reboot the controller; then, issue the ARCCONF DELETE command
+     again. 
+     
+--------------------------------------------------------------------
+9. Other Issues and Notes
+                  
+   - Some solid state drives identify themselves as ROTATING media.
+     As a result, these SSDs:
+     
+     o Appear as SATA drives in the ASM Physical Devices View
+     o Cannot be used as Adaptec maxCache devices
+     o Cannot be used within a hybrid RAID array (comprised of 
+       SSDs and hard disks)
+
+   - The blink pattern on Adaptec Series 6/6Q/6E/6T controllers differs  
+     from Series 2 and Series 5 controllers:
+   
+     o When blinking drives in ASM, the red LED goes on and stays solid; 
+       on Series 2 and 5 controllers, the LED blinks on and off.
+     
+     o When failing drives in ASM (using the 'Set drive state to failed' 
+       action), the LED remains off; on Series 2 and 5 controllers, the 
+       LED goes on and remains solid.    
+
+   - Cache settings for RAID Volumes (Read cache, Write cache, maxCache)
+     have no effect. The cache settings for the underlying logical
+     devices take priority.
+
+   - On rare occasions, ASM will report invalid medium error counts on 
+     a SATA hard drive or SSD. To correct the problem, use ARCCONF to  
+     clear the device counts. The command is:
+
+     arcconf getlogs <Controller_ID> DEVICE clear
+      
+   - On rare occasions, ASM lists direct-attached hard drives and SSDs
+     as drives in a virtual SGPIO enclosure. Normally, the drives are  
+     listed in the Physical Devices View under ports CN0 and CN1.
+
+   - Hard Drive Firmware Update Wizard:
+          
+     o Firmware upgrade on Western Digital WD5002ABYS-01B1B0 hard drives 
+       is not supported for packet sizes below 2K (512/1024).       
+
+     o After flashing the firmware of a Seagate Barracuda ES ST3750640NS  
+       hard drive, you MUST cycle the power before ASM will show the new
+       image. You can pull out and re-insert the drive; power cycle the 
+       enclosure; or power cycle the system if the drive is attached directly.          
+     
+   - Secure Erase:
+   
+     o If you reboot the system while a Secure Erase operation is in  
+       progress, the affected drive may not be displayed in Adaptec 
+       Storage Manager or other Adaptec utilities, such as the ACU.
+   
+     o You can perform a Secure Erase on a Solid State Drive (SSD) to
+       remove the metadata. However, the drive will move to the Failed 
+       state when you reboot the system. To use the SSD, reboot to 
+       the BIOS, then initialize the SSD. After initialization, the SSD 
+       will return to the Ready state. (A SSD in the Failed state cannot
+       be initialized in ASM.)
+     
+   - The Repair option in the ASM Setup program may fail to fix a
+     corrupted installation, depending on which files are affected.
+     The repair operation completes successfully, but the software
+     remains unfixed. 
+
+   - Adaptec Storage Manager may fail to exit properly when you create 
+     64 logical devices in the wizard. The logical devices are still
+     created, however.      
+
+   - The "Clear logs on all controllers" action does not clear events
+     in the ASM Event Viewer (GUI). It clears device events, defunct 
+     drive events, and controller events in the controllers' log files.
+     To clear events in the lower pane of the GUI, select Clear   
+     configuration event viewer from the File menu.
+     
+   - Stripe Size Limits for Large Logical Drives:
+  
+     The stripe size limit for logical drives with more than 8 hard     
+     drives is 512KB; for logical drives with more than 16 hard 
+     drives it is 256KB.
+     
+   - Agent Crashes when Hot-Plugging an Enclosure:
+   
+     With one or more logical drives on an enclosure, removing
+     the enclosure cable from the controller side may crash 
+     the ASM Agent.
+     
+--------------------------------------------------------------------
+(c) 2012 PMC-Sierra, Inc. All Rights Reserved. 
+
+This software is protected under international copyright laws and 
+treaties. It may only be used in accordance with the terms 
+of its accompanying license agreement.
+
+The information in this document is proprietary and confidential to
+PMC-Sierra, Inc., and for its customers' internal use. In any event,
+no part of this document may be reproduced or redistributed in any
+form without the express written consent of PMC-Sierra, Inc.,  
+1380 Bordeaux Drive, Sunnyvale, CA 94089.
+
+P/N DOC-01700-02-A Rev A

i386/centos5/libstdc++.so.6

@@ -0,0 +1 @@
+libstdc++.so.6.0.8