Error message

  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Deprecated function: implode(): Passing glue string after array is deprecated. Swap the parameters in drupal_get_feeds() (line 394 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).

7

3ware 9500s manual

LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF

File Name:3ware 9500s manual.pdf
Size: 4114 KB
Type: PDF, ePub, eBook

Category: Book
Uploaded: 26 May 2019, 23:25 PM
Rating: 4.6/5 from 608 votes.

Status: AVAILABLE

Last checked: 4 Minutes ago!

In order to read or download 3ware 9500s manual ebook, you need to create a FREE account.

Download Now!

eBook includes PDF, ePub and Kindle version

✔ Register a free 1 month Trial Account.

✔ Download as many books as you like (Personal use)

✔ Cancel the membership at any time if not satisfied.

✔ Join Over 80000 Happy Readers

3ware 9500s manualTrademarks 3ware, Escalade, and 3DM are all registered trademarks of AMCC. The 3ware logo, 3BM, StorSwitch, TwinStor, and R5 Fusion are all trademarks of AMCC. All other trademarks herein are property of their respective owners. For more complete information about managing and using arrays connected to the 3ware RAID controller, see 3ware 9000 Series Serial ATA RAID Controller User Guide. Features of the 3ware 9000 series controllers include: Advanced RAID features for greater data protection and management. PCI slot that meets the Plug and Play and PC99 specifications. For all 3ware 9000 series models, install the card in a 64- Note: bit, 66MHz PCI or PCI-X slot for best performance. Drives may be of any capacity or physical form factor. If the drives are not already installed in the computer, install them. Connect the interface cables to the drives. Close up the case. Power on the system. www.3ware.com. Save your changes and exit. Specify a hot spare (optional). Install the 3ware driver and make the units available to the operating system. For details see one of the following: “Driver Installation Under Windows” on page 53 “Driver Installation Under Linux”. It contains the following topics: “Before You Begin” things you should consider before starting installation, and tools and equipment you will need. “Safety Factors” personal safety and to protect your equipment and data. Be sure to read this section. The amount of clearance you need will depend on the number of drives you will be connecting to the controller. Safety Factors Be sure to follow the guidelines presented on the next few pages to insure your own safety, and that of your equipment. Handle the 3ware RAID controller by its edges or by the black rail and metal bracket at its two ends. Do not touch any pin, contact, lead or component on the 3ware RAID controller. The earlier models use Pchip v1.4 and are not BBU-compatible. The more recent models use Pchip v1.5 and are BBU-compatible.http://dopuskvsro.ru/UserFiles/bosch-ice-maker-manual.xml

    Tags:
  • 3ware 9500s-4lp manual, 3ware 9500s manual, 3ware 9500s manual download, 3ware 9500s manual pdf, 3ware 9500s manuals, 3ware 9500s manual free.

Check with your chassis documentation before connecting. Table 1: LED Indicator Pin Positions Controller Header 9500S-4LP 9500S-8 (Pchip v1.4) 9500S-8 (Pchip v1.5) Find the PCI slot you want to use for the serial 3ware RAID controller. For a discussion of which slot to use, see “Selecting the Slot in Which to Install the Controller”. Check that the 3ware RAID controller’s metal bracket covers the hole in the case and secure the bracket with the screw that was used to secure the filler bracket in step 5. These controllers can be installed in an enclosure with a backplane. The. If you are using a standard enclosure, connect each of the individual SATA connectors to a drive. 3ware 9000 Series Serial ATA RAID Controller Installation Guide. Remove the metal filler bracket for the slot. Save this screw; it will be used to secure the 3ware RAID Controller after you have seated it in the slot. Configure your RAID Arrays Turn to “Configuring Units” on page 27 for information about configuring the RAID arrays. 3ware 9000 Series Serial ATA RAID Controller Installation Guide. Contact Technical Support to obtain the utility. Install the 9000 controller and attach the drives to the 9000 board, as described earlier in this section. 3ware 9000 Series Serial ATA RAID Controller Installation Guide. Additional information about 3BM is available in 3ware 9000 Series Serial ATA RAID Controller User Guide.) Press the F8 or Esc key to save and exit. When you work with 3ware software, “unit” is the term used to refer to an array of disks that is configured and managed through the 3ware software. The stripe size is configurable in 3ware BIOS Manager (3BM). Requires a minimum of two drives. When drives are configured in a striped disk array, large files are distributed across the multiple disks using RAID 0 techniques. Like disks in other RAID configurations, single disks contain 3ware Disk Control Block (DCB) information and are seen by the OS as available units.http://xn----7sbab1bcaqplb0ccyi9d.xn--p1ai/UserFiles/bosch-induction-hob-user-manual.xml Used to store data locally on the drive before it is. For more information, see “Enabling Auto-Carving for Units Larger Than 2 TB” on page 47, and in 3ware 9000 Series Serial ATA RAID Controller User Guide, see “Multi LUN Support and Auto-Carving.”. It includes the following sections: Starting the 3BM configuration utility Exiting the 3BM configuration utility Working in the 3BM configuration screens. Otherwise, press any key to continue. www.3ware.com Working with the 3ware BIOS Manager (3BM) For more information, see the 3ware 9000 Series Serial ATA RAID Controller User Guide. 3ware 9000 Series Serial ATA RAID Controller Installation Guide If you make changes on the Policy screen,. Before you can use these drives, they must be deleted. For more information, see the discussion of Deleting Units in 3ware 9000 Series Serial ATA RAID Controller User Guide. Basic Steps for Creating a Unit. The Create Disk Array screen appears (see Figure 11 and Figure 12 for examples). Make sure that the proper drives are listed. www.3ware.com Specifying the Unit Configuration. Create Disk Array Display, RAID 0 Example Figure 12. Create Disk Array Display, RAID 5 Example 3ware 9000 Series Serial ATA RAID Controller Installation Guide. For more information about write cache, see page 31. Press Tab to move to the field Stripe Size and select the desired stripe size (16KB, 64KB, or 256KB). www.3ware.com Specifying the Unit Configuration. To confirm unit configuration Press Tab to select the OK button and press Enter to confirm creation of the unit. You’ll see the words “Hot Spare” appear next to the drive in the Available Drives list. Figure 16. Hot Spare Indicated 3ware 9000 Series Serial ATA RAID Controller Installation Guide. On the Policy screen, tab to 2TB Auto-Carving, and change the setting to “Enabled.” www.3ware.com Specifying the Unit Configuration. For these configurations, initialization begins automatically after you create them in the 3BM utility.http://www.drupalitalia.org/node/67893 Zeroes are written to all unit members. www.3ware.com. The steps below describe how to do this through the BIOS (3BM). For information about using 3DM 2, see 3ware 9000 Series Serial ATA RAID Controller User Guide. After installing the 3ware 9000 controller in your system, go into the BIOS for your computer system to check and change the boot order. This is necessary because most systems automatically change the boot order when they detect a newly installed controller and device. Will the unit you have created be your system's boot device. If so, you will install the driver for the controller as you install the operating system. A drive or unit managed by the 3ware RAID controller may be configured to be your system’s boot device. Or, you can use another device as your boot device, such as a disk attached to the motherboard. If you are installing Windows, you must create a 3ware driver diskette. If Windows is already installed on another device, you may install the 3ware driver from either the 3ware software CD-ROM or from a diskette. Insert the 3ware driver diskette and press Enter. This wizard guides you through installing the 3ware drivers (see Figure 17). Note that you will see screens for the installation of two drivers during this process. This wizard guides you in installing the 3ware drivers (see Figure 21). Note that you will see screens for the installation of two drivers during this process. When the Welcome to the Found New Hardware Wizard screen appears again (Figure 23), click Next and follow the prompts on the screen to install the second driver. www.3ware.com. Remove the driver diskette or CD, reboot the system, and log in as the system administrator. You may also want to install 3ware’s browser-based Disk Management tool, 3DM 2, or the 3ware Command Line Interface (CLI). With 3DM 2 and CLI, you can maintain your RAID units while running Windows.https://climatechange-news.com/images/3ware-9500s-user-manual.pdf For more information, see the 3ware 9000 Series Serial ATA RAID Controller User Guide and the 3ware Escalade 9000 Series Serial ATA RAID Controller CLI Guide. A drive or unit managed by the 3ware RAID controller may be configured to be your system’s boot device. Or, you can use another device as your boot device, such as a disk attached to the motherboard. For more information, see “Compiling a 3ware Driver for Red Hat Linux” on page 77 and “Compiling a 3ware Driver for SuSE Linux” on page 83. We have tested some older systems where an IDE. Select the appropriate set of steps below, based on whether:. Mount the CD which contains the 3ware driver: To mount the CD, type: and press Enter. Copy the driver:. To install the 3ware driver and load the driver manually instead of using a RAM disk Log in as root and open a console window. If Linux is already installed on another device, you may install the 3ware driver from the 3ware software CD-ROM. Install the Kernel source under Create a symbolic link. A drive or unit managed by the 3ware RAID controller may be configured to be your system’s boot device. Or, you can use another device as your boot device, such as a disk attached to the motherboard. The 3ware software CD-ROM that came with the 3ware RAID controller includes compiled and tested drivers for FreeBSD 4.8 and 4.9. To see if a more recent driver is available, please see the 3ware web site. Immediately after the OS starts booting from the CD,. The 3ware driver, twa.ko, should be automatically loaded at reboot time. To make the driver part of the kernel Boot with the FreeBSD CD-ROM or diskette.If you do not insert it immediately, the loader may fail to recognize the floppy drive.To make the driver part of the kernel. If drives are attached and you do not want to install the 3ware BIOS, press Alt-b to bypass the BIOS installation when you start the system. This is useful when booting temporarily from another device, if the operating system is already installed on the 3ware unit. For the half-height board, the bracket sits on the bottom of the board, with screws inserted from the top. 3ware 9000 Series Serial ATA RAID Controller Installation Guide. Figures 10 and 11 show the BBU fully installed on 3ware controllers. You can check the status of the battery, and run a battery test to determine if the battery needs to be replaced. BBU installed on controllers 3ware 9000 Series Serial ATA RAID Controller Installation Guide. For details, see instructions in 3ware 9000 Series Serial ATA RAID Controller User Guide. There is a risk of explosion if the battery is Caution: replaced by an incorrect type. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. www.3ware.com. European Community Conformity. Exclusions This warranty does not cover any damage to this product which results from accident, abuse, misuse, natural or personal disaster, or any unauthorized disassembly, repair or modification. You will be issued a return material authorization (RMA) number. AMCC also offers toll-free (800) 945-7273 and (408) 523-1145 direct phone support during normal business hours. Table 1: Sections in this CLI Guide Chapter 1. Introduction to 3ware Command Line Interface 2. Multiple 3ware RAID controllers can be managed using the CLI via a command line or script. Note: RAID controllers. For a summary of what you can do using the CLI, see “Common Tasks Mapped to CLI Commands”. If you are using 3DM, as opposed to 3DM2, AMCC does not recommend installing both 3DM and CLI on the same system. Conflicts may occur. For example, if both are installed, alarms will be captured only by 3DM. You should use either CLI or 3DM to manage your 3ware RAID controllers. To do so, simply enter the command and the arguments. Single commands can be useful when you want to perform a task such as redirecting the output of the command to a file. This could be useful, for example, if you want to email the output to AMCC Technical Support.AMCC's 3ware controllers support RAID 0, 1, 5, 6, 10, 50, JBOD and Single Disk. The information below provides a more in-depth explanation of the different RAID levels. RAID 1 is also known as a mirrored array. Mirroring is done on pairs of drives. Mirrored disk arrays write the same data to two different drives using RAID 1 algorithms (see Figure ?). When drives are configured as a striped mirrored array, the disks are configured using both RAID 0 and RAID 1 techniques, thus the name RAID 10 (see Figure ?). RAID 50 requires a minimum of six drives. JBOD configuration is no longer supported in the 3ware 9000 series. AMCC recommends that you use Single Disk as a replacement for JBOD, to take advantage of advanced features such as caching, OCE, and RLM. Determining What RAID Level to Use Your choice of which type of RAID unit (array) to create will depend on your needs. This is because the capacity of each drive is limited to the capacity of the smallest drive in the unit. Throughout this chapter the examples reflect the interactive method of executing 3ware CLI. Common Tasks Mapped to CLI Commands The table below lists many of the tasks people use to manage their RAID controllers and units, and lists the primary CLI command associated with those tasks. For example, the command show alarms by default lists alarms with the most recent alarm first. If you include the attribute reverse, as in the command show alarms reverse, alarms are listed in reverse order. For example, you can use enclosure object commands to see information about an enclosure and its elements (slots, fan, and temperature sensor elements). Help Commands. all commands and attributes. For details, see “Help Commands” on page 91. Shell Object Commands Shell object commands are either applicable to all the controllers in the system (such as show, rescan, flush, commit), or redirect the focused object. The reverse attribute displays the most recent message last.For example, you use controller object commands to see alarms specific to a controller, to create schedules for when background tasks are run, and to set policies for the controller.Additional attributes about controllers, units, ports and disks can be obtained by querying for them explicitly. For details, see the other show subcommands.If you use a 32-bit operating system, it is recommended that you keep the policy on unless you know that your operating system supports disks that are larger than 2 TB. This command shows the Auto-Rebuild policy. If the policy is enabled, the firmware will select drives to use for rebuilding a degraded unit using the following priority order.For more about the meaning of Not Optimal, see “Shell Object Commands” on page 23.By default the host operating system will be informed of the new block device, write cache will be enabled, and a storsave policy of protect will be set. The following table illustrates the supported and applicable stripes on unit types and controller models. Stripe size units are in K (kilobytes). If no stripe size is specified, 64K is used by default, if applicable. If you need to change the stripe size after the unit is created, you can do so my migrating the unit. For 16 disks, the disks can be grouped into groups of 4 or 8 drives.It commits all changes if a faster shutdown method is needed when running certain database applications. Linux and FreeBSD file systems do not require this command since they have their own ways of notifying the controller to do clean up for shut down. Do you want to continue.If you include it, the compatibility checks are bypassed. Note that some characters might not be printable or rendered correctly (human readable). It is recommended to save the output from this command to a file, where it can be communicated to technical support or further studied with Linux utilities such as od(1). In this case, the controller will not use the defined schedule timeslots. If the rebuild command is entered manually, rebuilding will start within 10 to 15 minutes. It will begin automatically if a rebuild is needed and a proper spare drive is set If the rebuild schedule is enabled while a rebuild process is underway, the rebuild will pause until a scheduled time slot. Verify is one of the supported background tasks. Rebuild and selftest are other background tasks for which there are separate schedules. A JBOD is an unconfigured disk attached to your 3ware RAID controller. AMCC recommends that you use Single Disk as a replacement for JBOD, to take advantage of features such as RAID level migration. The value must be a positive integer between 0 to 60 seconds. By default, autorebuild is on. If the policy is on the firmware will select drives to use for rebuilding a degraded unit using the following priority order. If a port is empty (no drive is inserted), this feature is disabled for that port and its port number is shown. If the Auto-Carving policy was on at the time the unit was created and the unit is over the carve size, multiple volumes were created and are displayed at the end of the summary information. One or many attributes can be requested. Specifying an invalid attribute will terminate the loop.This command reports the name (if any) of the specified unit. This command reports the storsave policy on the unit.This command shows the current setting of the ignoreECC policy for the specified unit.After deleting a unit, ports (or disks) associated with the unit will be part of the free pool of managed disks. The system does not check to ensure uniqueness of names, so be careful to assign different names to each unit. All data flushing from controller cache will be flushed to media. One or more ports can be specified. Multiple ports can be specified using a colon (:) or a dash (-) as port index separators. For 15 disks, the disks can be grouped into groups of 3 or 5 drives. For 16 disks, the disks can be grouped into groups of 4 or 8 drives.Migration Process In all cases of migration, the background migration process must be completed before the newly sized unit is available for use. In this example, the report indicates that completion.You use port object commands for such tasks as seeing the status, model, or serial number of the drive. This command displays the NCQ (Native Command Queueing) information for the drive attached to the specified port, including whether NCQ is supported by the drive, and whether it is enabled at the drive. For queuing to be used, it must be enabled for the unit and supported by the drive. This object is only available on 9000 series controllers on which a BBU is actually installed. Specifying an invalid attribute will terminate the loop.The HIGH and LOW are in warning range.During the test, the BBU is not capable of backup operation and the write cache of all units attached to that controller is disabled. Possible statuses are OK and Unknown. If a slot has been inserted with a drive and no fault has been detected, the status is OK. If the slot is empty the status would indicate NO-DEVICE. If a fan is on and no fault has been detected, the status would indicate OK.All rights reserved.See the section “Shell Object Commands” on page 23 for more information. This publication may be co pied or reproduced for reference purposes only. T o do so, simply enter the command and the arguments. RAID 1 is also known as a mirrored array. Enclosure object commands provide information and perform ac tions related to a par ticular en clo s ure. The default is to display the most re cent message first. This command shows the Au to-Rebuild policy. The following table illustrates the supported an d applicable stripes on unit types and controller models. Stripe size units are in K (kiloby tes). For 16 disk s, the disks can be grouped into groups of 4 or 8 drives. Do you want to continue. In this case, the controller will not use the define d schedule timeslots. By default, exportjbod is off. If the JBOD export policy is off, CLI will not be able to create JBODs. One or many attributes can be requested. This command reports the storsave policy on the unit. One or more ports can be specified. For 15 disks, the disks can be grouped into grou ps of 3 or 5 drives. One or many attributes can be sp ecified. The test may take up to 24 hours to complete. The slot name is followed by its status. The fan name is followed by its status. All other purposes require the express written consent of AMCC, 215 Mof fett Park Drive, Sunnyvale, CA 94089. The 3ware logo, 3BM, S torSwitch, and R5 Fusion are all trademarks of AMCC. PowerPC and the PowerPC logo are tradema r ks of Internationa l Business Machines Corporation. All other trademarks herein are property of their respective owners. Disc laimer While every attempt is made to make this document as accurate as possible, AMCC assumes no responsibility for errors or omissions in this document, nor does AMCC make any commitment to update the information contained herein. There are often multiple ways to acc omplish the same configuration and maintenance tasks for your 3ware cont roller. T able 1: Sections in this CL I Guide Chapter Description 1. Introduction to 3 ware Command Line Interface Installation, features, concepts 2. CLI Syntax Reference Describes individual commands using the primary syntax Multiple 3ware RAID controllers can be managed using the CLI via a command line or script. It provides co ntroller, logical unit, drive, enclosure, and BBU (Battery Backup Unit) management. It can be used in both interactive and batch mode, providing higher level AP I (application programming interface) functionalities. Note: Some CLI commands are supported only for particular models of 3ware RAID controllers. Wherever possible, comman ds are labeled to indicate when they are supported for only a subset of cont rollers. Within the 90 00 series, some commands apply to only to models 9550SX, 9590SE, and 9650SE an d not to 9500S, and are so labeled. A few commands apply only to models 950 0S, and are labeled as such. Import ant! For all of the functions of the 3ware CLI to work properly, you must h ave the proper CLI, firmware, and driver versions installed.For a summary of what you can do using the CLI, see “Common T asks Mapped to CLI Commands” on pag e 19. For specific versions of Linux and FreeB SD that are supported for the 3ware CLI, see the Release Notes. T er minolog y This document uses th e following terminology: Logical Unit s. Usually shortened to “units.” These are block devices presented to the operating system. A logical unit can be a one-tier, two-tier, or three-tier arrangement. JBOD, Spare, an d Single logical units are examples of one-tier units. RAID 1 and RAID 5 are examples of two-tier units and as such will have sub-units. RAID 10 and RAID 50 are examples of three-tier units and as such will have sub-sub-units. Port. A controller has one or many ports (typically 4, 8, 12, 16). Each port can be attached to a single disk drive. On a controller such as th e 9590SE-4ME, with a multilane serial port connector, one connector supp orts four ports. For additional information about 3ware controller concepts and terminology, see the user guide that came with you r 3ware RAID controller or the user guide portions of the 3ware HTML Book shelf. Wa r ni n g! If you are using 3DM, as opposed to 3DM2, AMCC does not recommend installing both 3DM and CLI on the same system. Conf licts may occur. For example, if both are inst alled, alarm s will be cap tured only by 3DM. Y ou should u se either CLI or 3DM to manage your 3ware RAID controllers. This is not an issue for 3DM2. Be sure to copy the corre ct version for the version of th e operating system you are using. The CLI prompt is displayed in a DOS console window. Online manual pages are also availabl e in nroff and html formats. Be sure to copy the correct version for the version of th e operating system you are using. T o do so, simply enter the command and the arguments. Single commands can be useful when you want to perform a task such as redirecting the output of the command to a file. It also allows you to use the command line history to eliminate some typing.The file is a text file containing a list of CLI command s which you have entered in advance. Each command must be on a s eparate line. This exampl e sets up a 12-port controller with two units: one with the firs t 2 drives mirrored, and another with the remaining drives in a RAID 5 array. It then prints the configurations for verification.In the storage industry, the term “array” is used to describe two or more disk drives that appear to the operating system as a single unit. When working with a 3w are RAID controller, “unit” is the term used to refer to an array of disks that is configured and managed through the 3ware software. If one drive fails, the data is preserved on the paired drive. Mirroring provides data pro tection through redundan cy. Parity works in combination with striping on RAID 5, RAID 6, and RAID 50. Parity informa tion is written to each of the striped drives, in rotation. This is useful when you need to exchange a defective drive in a redundant array. The di sks may be attached to different ports than they were originally attach ed to, without harm to the data. For definitions of other terms used throughout the documentation, see the “Glossary”. A vailable RAID Configur a tions RAID is a method of combining several hard drives into one unit. It of fers fault tolerance and higher throughp ut levels than a single hard drive or group of independent hard dr ives. RAID levels 0, 1, 10 and 5 are the m ost popular. AMCC's 3ware controllers support RAID 0, 1, 5, 6, 10, 50, JBOD and Single Disk. The information below provides a more in-depth ex plan ation of the different RAID levels. For how to configure RAID un its, see “Configuring a New Unit” on page 96. RAID 0 RAID 0 provides improved performance, but no fault t olerance. Since the data is striped across more than one di sk, RAID 0 disk arrays achie ve high transfer rates because they can read an d write data on more tha n one drive simultaneously. The stripe size is conf igurable during un it creation. RAID 0 requires a minimum o f two drives. When drives are configured in a striped disk array (see Figure ?), large files are distributed across the multiple disks using RAID 0 techniques. Striped disk arrays give excepti ona l performance, particularly for data intensive applications such as vide o editing, computer-ai ded design and geographical info rmation systems. RAID 0 arrays are not fault tolerant. The loss of any driv e resu lts in the loss of all the data in that array, and can even cause a system hang, depending on your operating system. RAID 0 arra ys are not recommended for high availability systems unless additional precautions are taken to prevent system hangs and data loss. Figure 1. RAID 0 Configuration Example RAID 1 is also known as a mirrored array. Mirrored disk arrays write the sam e data to two dif ferent drives using RAID 1 algorithms (see Figure ?). This gives your system fault tolerance by preserving the data on one drive if th e other drive fails. W ith T winS tor technology, read performance is twice the speed of a single drive during sequential read operatio n. The adaptive alg orithms in T winStor tech nology boost performance by distinguishing betw een random and sequential read requests. For the sequential requests generated when accessi ng large files, both drives are used, with the heads simultaneous ly reading alternating sec tions of the file. For the smaller random transactions, the data is read from a single optimal drive head. Figure 2. RAID 1 Configuration Example RAID 5 RAID 5 provides performance, fault tole rance, high capacity, and storage efficiency. It requires a minimum of three drives and combines striping data with parity (exclusive OR) to rest ore data in case of a drive failure. Performance and ef ficiency increas e as the number of drives in a unit increases. Parity information is distributed across all of the drives in a unit rather than being concentrated on a single disk (s ee Figure ?). This avoids throughput loss due to contention for the parity drive. RAID 5 is able to tolerate 1 drive failure in the unit. This also means that a RAID 6 unit may be in two dif ferent states at the same time. For example, one sub-unit can be degraded, while another may be rebuilding, or o ne sub-unit may be initializing, while another is verifying. RAID 6 requires a minimum of five drives. Performance and storage efficiency also increase as the number of drives increase. When drives are configured as a striped mirrored array, the disks are configured using both RAID 0 and RAID 1 techni ques, thus the name RAID 10 (see Figure ?). A mi nimum of four drives are required to use this technique. The first two drives are mirro red as a fault tolerant array using RAID 1. The third and fourth drives are mirrored as a second fault tolerant array using RAID 1. The two mirrored arrays are then grouped as a striped RAID 0 array using a two tier structure. Higher data transfer rates are achieved by leveraging T winStor and striping the arrays.