Dot Hill Systems RAIDCore User Manual

Download

Page 1

P/N 83-00004638-12

Revision A

December 2009

RAIDCore User Manual

Page 2

The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, changes in the product design can be made without reservation and without notification to its users.

Page 3

RAIDCore User Manual 1

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Chapter 1 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Safety Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Chapter 2 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

RAIDCore Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Who Should Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

System Requirements for Using RAIDCore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Supported Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Features of RAIDCore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

RAIDCore Licensing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Major Features of RAIDCore Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Features Set: by RAIDCore License Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Chapter 3 Arrays, Disks, and RAID Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Understanding Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

RAID Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Array States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Creating Arrays: Future Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Expanding Disk Capacity Online: Using OCE (supported only by RAIDCore VST) . . . . . . . . . . . . . . . . . .26

Migrating RAID Levels Online: Using ORLM (supported only by RAIDCore VST) . . . . . . . . . . . . . . . . . .26

Array Tasks: Starting and Stopping Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Understanding Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Disks States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

RAID Minimum Disk Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Rescanning Disks for Changes in State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Sparing Options: Disks and Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Distributed Sparing (supported only by RAIDCore VST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Dedicated Sparing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Global Sparing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

RAID Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Number and Organization of Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Caching Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Application Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

RAID Reliability Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Data Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Flexibility and Expansion Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Multiple RAID Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Operating System Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Chapter 4 Installing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Before You Begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

System Setup Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . .33

Copy Drivers to Removable Storage Media: Windows Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . .34

Use the storage medium and its copied files to install the drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Copy Drivers to Removable Storage Media: Linux Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Install Drivers and Applications: Windows Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Install Drivers on a System at the Same Time That the Windows Operating System is Installed . . . . . . .36

Page 4

RAIDCore User Manual 2

Install Drivers, Configuration Devices, and the Management Suite: Windows . . . . . . . . . . . . . . . . . . . . . .37

Install Drivers and Applications: Linux Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Install Drivers on a System at the Same Time That the Linux Operating System Is Installed . . . . . . . . . .41

Install Drivers at the Same Time That Red Hat Linux is Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Install Drivers at the Same Time That SUSE Linux is Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Install Drivers, Configuration Devices, and the Management Suite: Linux . . . . . . . . . . . . . . . . . . . . . . . . .49

Booting from a Legacy Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Supplemental Linux Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Manually Install RAIDCore Drivers on an Existing Installation of Linux . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Install the RAIDCore software driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Manually install the RAIDCore driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Chapter 5 BIOS Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

When to Use the RAIDCore BIOS Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Access the RAIDCore BIOS Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Understanding the Color Code in the BIOS Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Initialize Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Initialize Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Create Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Create An Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Select An Array Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Resume the Boot Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Delete Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Delete an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Swap Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Swap Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

View Disk Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

View Array Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Rescan All Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Change the Controller Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Select a Boot Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Change the Staggered Spinup Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Continue Booting from the BIOS Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Chapter 6 RAIDConsole Graphical User Interface (GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Start the RAIDConsole GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Start RAIDConsole under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Start RAIDConsole under Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Password Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Things to Know About Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Set Password Protection from the First Time Run Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Disable Password Protection from the First Time Run Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Enable Password Protection from the Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Disable Password Protection from the Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. .65

Change a Password from the Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Help and About Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Reviewing the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

The Array Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

The Array View Section of the Array Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Elements of the Array View Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Array View Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

The Disk List Section of the Array Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Elements of the Disk List Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

The Array List Section of the Array Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Elements of the Array List Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

The Event View Section of the Array Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Elements of the Event View Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Page 5

RAIDCore User Manual 3

The I/O Status Bar of the Array Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Elements of the I/O Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Working with Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Initialize Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

To initialize disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Rescan Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Change Cache Properties for Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Change disk caching properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Change Disk View Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Operations Available at the Physical View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Legacy Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Working with Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Create and Format Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Create an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Select an array and cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Select options and configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Partition an array for use with Windows Server 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Format the array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Name Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

To name an array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Transform Arrays (supported only by RAIDCore VST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Transform an array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Copy Arrays (supported only by RAIDCore VST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Copy an array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Use the Un-Link and Un-Hide Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Access Additional Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Prepare to Physically Remove an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Delete Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Delete an array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Recreate a deleted array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Recover Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Recover an array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Change Cache Settings for Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

Change cache settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

Change the Priority Level of a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

To change a task priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Interrupt or Cancel a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Interrupt or cancel a task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Check for Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Manually start a Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Manually stop a Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Schedule a Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Schedule a Consistency Check for later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Delete a scheduled Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Scan an Array in the Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Enable or disable a Background Array Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Split Mirrored Arrays (supported only by RAIDCore VST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Split a mirror using default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Before you start... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Use default settings to split a RAID 1 or RAID 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Split a mirror using the advanced split option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Add or Remove Distributed Spares (supported only by RAIDCore VST) . . . . . . . . . . . . . . . . . . . . . . . . . .92

Add a distributed spare while creating an array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Add a distributed spare while transforming an array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Page 6

RAIDCore User Manual 4

Remove a distributed spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Add or Remove Dedicated Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Add a dedicated spare while creating an array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Add a dedicated spare after an array has been created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Remove a dedicated spare assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Remove All Dedicated Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Remove all dedicated spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Add or Remove Global Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Add a global spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Remove a global spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Working with Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

View or Change the License Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

View license level using RAIDConsole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Change Password Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Change View Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Set small icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Use Expand On Click . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Change how the array tree expands when an array is clicked in the Array View . . . . . . . . . . . . . . . . .96

Edit exit columns in the Disk List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Edit the Physical View of the Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

View Log Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Set Event Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Set or change event notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Set Up Remote Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Add a Remote System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Read SMART Information from Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Read SMART information from disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Turn on Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Recover an array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Stop and restart the RAIDCore Event Service program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Stop and Restart the RAIDCore Event Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Stop the RAIDCore Event Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Start the RAIDCore Event Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Chapter 7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

System Startup Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Warning Messages: POST Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Array-Related Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Disk-Related Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Appendix A Software License: EULA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Software License: End-User License Agreement (EULA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

1. Limited License to Authorized Distributors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

2. Limited License to End Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

3. Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

4. Proprietary Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

5. Source Code Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

6. Term and Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

7. No Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

8. Limitation of Liability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

9. Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

10. Export Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

11. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

Appendix B bcadm Command Line Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

What is bcadm? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

To Use bcadm with a Linux OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

To Use bcadm with a Windows OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

Manage Arrays and Disks: bcadm --manage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Understand Query Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Page 7

RAIDCore User Manual 5

bcadm Controller List Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

bcadm Disk List Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121

bcadm Array List Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122

View Help from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

To view a list of the major modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

To view help for a specific mode and its options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

To view the bcadm man page on a Linux system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

Create New Arrays: bcadm --create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

Delete Arrays: bcadm --delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

Transform Arrays: bcadm --transform (supported only by RAIDCore VST) . . . . . . . . . . . . . . . . . . . . . . . . .124

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

Copy Arrays: bcadm --create-copy (supported only by RAIDCore VST) . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

Legacy Disks: bcadm --create-copy (supported only by RAIDCore VST) . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Split Mirrored Arrays: bcadm --split (supported only by RAIDCore VST) . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Follow or Monitor Arrays and Disks: bcadm --follow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

View or Change License Levels: bcadm --license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Before you begin... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Page 8

RAIDCore User Manual 6

Page 9

RAIDCore User Manual 7

Figures

1 Dot Hill® window, showing Install Windows Management Suite selected . . . . . . . . . . . . . . . . . . . . . . . . . 40

2 License Agreement window, showing I accept the terms of the License Agreement selected.. . . . . . . . . 40

3 Four-Drive RAID 5 Array at the Main Menu (typical window). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4 Example of a RAID 5 Swapped for a RAID 10 (typical window) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

5 Controller Options Section of the RAIDCore(tm) Array Configuration Window (typical) . . . . . . . . . . . . . . 61

6 First Time Run Dialog Box (typical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

7 RAIDConsole Dot Hill Window (typical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

8 Array Status Window: Accessing Array Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

9 RAIDConsole Properties Window (typical). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

10 Sections of the Array Status Window (typical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

11 Icons of the Array View Section of the Array Status Window (typical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

12 Array View, Array Status Window: Select an Array to be Copied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

13 Array View: Un-Link Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

14 RAIDConsole - Event Service Window: Rescan Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

15 RAIDConsole Window: Task -> Pause and Task -> Remove Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

16 License Window, showing the license level and the space for entering an Activation ID . . . . . . . . . . . . . 94

17 An example of an Entitlement Certificate, which contains the Activation ID . . . . . . . . . . . . . . . . . . . . . . . 95

18 Select Display Columns Window: Edit Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

19 Notification Setup Window: Notification Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

20 Options Drop-Down Menu of the SMART Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

21 SMART Information Window: Summary Error Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Page 10

8 Figures

Page 11

RAIDCore User Manual 9

Tables

1 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 System Requirements for RAIDCore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 Features of RAIDCore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4 Feature Set for RAIDCore: by RAIDCore License Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5 RAID Levels and Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

6 RAID Levels - General Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

7 Array States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

8 Failure States by RAID Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

9 Array Expansion Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

10 Types of Tasks per Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

11 Disk States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

12 Minimum Disk Configurations per RAID Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

13 Sparing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

14 System Setup Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

15 Driver Files for Windows Operating Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

16 Windows Operating System: Install Drivers, Configuration Devices, and Management Suite. . . . . . . . . . 37

17 Components of the Management Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

18 Installing the Red Hat Linux Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

19 SUSE Linux 10.3: Installing the SUSE Linux Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

20 SUSE Linux 11: Installing the SUSE Linux Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

21 Linux Operating System: Install Drivers, Configuration Devices, and Management Suite. . . . . . . . . . . . . 49

22 Components Installed with the Management Suite (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

23 Reasons for Using the RAIDCore BIOS Configuration Utility (Option ROM) . . . . . . . . . . . . . . . . . . . . . . . 53

24 BIOS Color Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

25 Selecting An Array Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

26 Choices for Selecting a Boot Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

27 Elements at the Array View Section of the Array Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

28 Disk List Section of the Array Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

29 Array List Section of the Array Status Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

30 Event View Elements, Array Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

31 I/O Status Bar Elements, Array Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

32 Restrictions and Conditions When Transforming a Legacy Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

33 Issues and Recommendations for Creating and Formatting Arrays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

34 Issues and Recommendations for Transforming Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

35 Issues and Recommendations for Copying Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

36 Options for Unlinking Copied Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

37 Issues and Recommendations for Deleting Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

38 Cache Array Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

39 Consistency Check Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

40 Splitting a Mirror by RAID Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

41 Event Notification Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

42 Event Log Priority Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

43 System Does Not Boot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

44 The BIOS Configuration Utility Does Not Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

45 Warning Messages: POST Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

46 Troubleshooting: Cannot Create an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

47 Troubleshooting: An Array is in an Offline State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

48 Troubleshooting: An Array is in a Critical State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

49 Troubleshooting: Cannot Assign a Dedicated Hot Spare to an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

50 Troubleshooting: Cannot Create a Global Hot Spare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

51 Troubleshooting: Cannot Create an Array Larger Than 2 TB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

52 Troubleshooting: Recreating a Deleted Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

53 Troubleshooting: The Disk Fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

54 Troubleshooting: A Dedicated Hot Spare Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

55 Troubleshooting: The Wrong Disk was Removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Page 12

RAIDCore User Manual 10

56 Troubleshooting: Cannot Initialize a Disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

57 Modes for the bcadm Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

58 bcadm Controller List Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

59 bcadm Disk List Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

60 bcadm Array List Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

61 Restrictions and Conditions When Transforming a Legacy Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Page 13

RAIDCore User Manual 11

Preface

This user guide:

• Provides information about arrays, disks, and RAID levels (RAID types).

• Describes how to improve storage system performance or reliability by understanding array and disk tasks and options.

Intended audience

This user guide is intended for use by system administrators and technicians who are experienced with the following:

• Direct Attached Storage (DAS), Storage Area Network (SAN), or Network Attached Storage (NAS) operators

• Network administration

• Network installation

• Storage system installation and configuration

Prerequisites

Prerequisites for installing and configuring this product include familiarity with:

• Servers and computer networks

• RAID and input/output signal technology (such as SCSI, SAS, or SATA)

• Fibre Channel and Ethernet protocols

Document conventions and symbols

Table 1 Document Conventions

Convention Element

Navy blue text: Figure 1

Cross-reference links and e-mail addresses

Navy blue, underlined text (

http://www.example.com)

Web site addresses

Bold font

•Key names

• Text typed into a GUI element, such as into a box

• GUI elements that are clicked or selected, such as menu and list items, buttons, and check boxes

Italics font

Text emphasis

Monospace font

• File and directory names

• System output

•Code

• Text typed at the command-line

Monospace, italic font

• Code variables

• Command-line variables

Monospace, bold font

Emphasis of file and directory names, system output, code, and text typed at the command line

Page 14

12 Preface

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT: Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

Customer Support

For customer support, contact your system or motherboard supplier.

Page 15

RAIDCore User Manual 13

1 Chapter 1 Safety Precautions

General

This section includes general safety precautions and specific RAIDCore cautions. Read and keep this user manual for future reference.

Safety Definitions

CAUTION: A Caution denotes the possibility of minor to severe damage to equipment and/or loss of data.

Safety Precautions

CAUTION: Before installing RAIDCore read all instructions and cautionary markings on the equipment and all

appropriate sections of this user manual.

CAUTION: Before installing RAIDCore in an existing system, back up all critical data. Failure to follow this

accepted system management practice could result in loss of data.

CAUTION: All components (drivers and applications) must be installed when upgrading to the latest version

of RAIDCore. This means that an older version driver will not work with the latest version of the RAIDCore application and vice versa.

CAUTION: If a disk has a RAID array on it, it cannot be initialized. To initialize the disk anyway, delete the

array. Make sure this is what is desired. Deleted data on a disk cannot be retrieved.

CAUTION: Do not upgrade the system if there are any tasks (such as a Transform or a Restore) running on

any of the arrays.

CAUTION: Deleting an array permanently destroys all data that is on the array. This action cannot be

undone.

CAUTION: Booting an operating system from a RAIDCore bootable array is supported. Dot Hill Systems

Corp. does not support booting from a RAIDCore array without having a RAIDCore BIOS (option ROM).

CAUTION: Leaving Write Back caching enabled might increase the likelihood of data being corrupted,

if the system experiences a power interruption or unexpected shutdown.

CAUTION: When a task is cancelled, data that is in the part of the task that did not finish will be lost on the

destination array.

Page 16

14 Chapter 1 Safety Precautions

Page 17

RAIDCore User Manual 15

2 Chapter 2 Getting Started

RAIDCore Technology

RAIDCore consists of (a) storage management and (b) RAID controller and port virtualization. RAIDCore runs on existing systems by using a motherboard’s built-in SATA ports or enhanced chipsets that have SAS disk or expansion capability.

RAIDCore provides a common interface to arrays, regardless of the type of controller.

Who Should Use This Manual

Only trained, experienced, and authorized personnel should install RAIDCore and use its features and capabilities.

All unit operators must be familiar with system hardware, data storage, RAID technology, input/output signal technology (such as SCSI, SAS, or SATA), and Direct Attached Storage (DAS) Storage, Network Attached Storage (NAS), and/or Storage Area Network (SAN) concepts and technology.

The intended user audience of this user manual are system administrators and experienced users.

System Requirements for Using RAIDCore

Make sure the systems that use RAIDCore meet the requirements indicated in the following table.

Supported Controllers

The following controllers are supported by the latest version of RAIDCore:

• AMD SB0700, SP5100

Supported Operating Systems

The following operating systems are supported by the current release of RAIDCore:

• Microsoft Windows

Server 2003 SP2: Enterprise Edition, Standard Edition: 32-bit and 64-bit.

• Microsoft Windows

Server 2008: Enterprise Edition, Standard Edition: 32-bit and 64-bit.

• Microsoft Windows

Server 2008 R2: Enterprise Edition, Standard Edition: 64-bit.

•Red Hat

Enterprise Linux® 5.3 and 5.4: 32-bit and 64-bit

•SUSE

Linux Enterprise Server 10.3 and 11: 32-bit and 64-bit

NOTE: Microsoft Windows

Server 2003 without SP2 is not supported by RAIDCore.

Table 2 System Requirements for RAIDCore

Component Requirements

Memory (RAM) Minimum: 512 MB.

Recommended: 2 GB.

Hard disk At least one SATA or SAS Expansion disk (the number of disks depends on the

number, type, and capacity of the arrays to be created).

Page 18

16 Chapter 2 Getting Started

Features of RAIDCore

The features of RAIDCore described in this user manual apply to all license levels and supported operating systems. See Supported Operating Systems on page 15.

The following table describes these features. Also see Table 4 on page 21 for a summary of features that are available with each license level of RAIDCore: RAIDCore Basic, RAIDCore Plus, and RAIDCore VST.

Table 3 Features of RAIDCore

RAIDCore Feature Description

Arrays (general information) RAIDCore allows:

• Creating arrays of different RAID levels using the same disks.

NOTE: RAID 5 is supported by RAIDCore Plus and

RAIDCore VST. RAID 1n, 10n, and 50 are supported by RAIDCore VST.

• Creating different RAID level arrays on the same disk, to adapt each array to the I/O that it processes.

• Creating an array from a mix of different-type disks. For example, a RAID 10 array can be created from a group of disks that contain two SATA II HDDs, a SAS HDD, and a SATA SSD.

• Migrating an existing array to another RAID level, if the type of array being used is not the optimal type for the application. This function depends on the array capacity and redundancy level.

A array refers to data storage created by RAIDCore from one or more disks. Although an array can be created from several disks, it is seen by the operating system as a single disk.

Array copying The Copy option is used to create a new array that contains an exact

copy of the data on a source array. It combines the Create Array and Copy Array functions into a single command.

NOTE: This feature is available only with RAIDCore

VST. See Copy Arrays (supported only by RAIDCore VST) on page 80.

Array hiding An array can be hidden from the operating system so that neither

the software nor users can see or access it. This is a key element in creating secure data backups.

Array recovery If an array is accidentally deleted, it can be recovered by creating a

new array with the same properties as the deleted array. This can occur only if disk Write Access operations are not in-progress.

Page 19

RAIDCore User Manual 17

Background array initialization (BGI)

The background initialization of a redundant array creates the parity data that allows the array to maintain its redundant data and survive a disk failure.

Because background initialization helps RAIDCore identify and correct problems that might occur with the redundant data at a later time, background initialization is similar to check consistency.

Background initialization allows a redundant array to be used immediately. Data is not lost if a disk goes offline prior to completion of the BGI process.

Cache support for arrays Various array-caching options are supported: No Cache, Read

Cache, Write Back Cache, Read + Write Back Cache.

Cache support for disks Various disk-caching options are supported: No Cache, Disk Read

Ahead, Disk Write Back, Disk Read Ahead + Write Back.

Consistency Check A Consistency Check is a background operation that verifies and

corrects the mirror or parity data for fault-tolerant disks. It is recommended that a Consistency Check be run periodically on the disks.

By default, a Consistency Check automatically corrects mirror or parity inconsistencies.

A Consistency Check can be scheduled or started manually by the system user.

Controller spanning A unique feature of RAIDCore that allows very wide arrays to be

created from disks connected to different controllers.

NOTE: This feature is available only with RAIDCore

VST.

See Supported Controllers on page 15.

Disk roaming With disk roaming, SAS/SATA cables can be disconnected from

their disks and shuffled without confusing RAIDCore.

NOTE: Disconnect the SAS/SATA cables from the disks

only when the system is offline.

Disk roaming also allows:

• Disks to be moved to different slots in the backplane. RAIDCore detects which disks belong to which arrays, regardless of where the disks are moved in the backplane.

• Disk(s) to be moved between systems.

Table 3 Features of RAIDCore (continued)

RAIDCore Feature Description

Page 20

18 Chapter 2 Getting Started

Fault tolerance The following fault tolerance features are available with

RAIDCore, in order to prevent data loss in case of a failed disk.

• Disk failure detection (automatic).

• Array rebuild using hot spares (automatic, if the hot spare is configured for this functionality).

• Parity generation and checking (RAID 5 only).

• Hot-swap manual replacement of a disk without rebooting the system (available only for systems with a backplane that supports hot-swapping).

For example if a disk fails in RAID 10, the array remains functional and data is read from the surviving mirrored disk(s). Up to two disk failures can be sustained, depending on how the mirrored pairs fail.

Mirror rebuilding A broken mirror can be rebuilt after a new disk is inserted and the

disk is designated as a spare. The system does not have to be rebooted.

Mirror splitting A mirrored array can be split, so that the volumes can be used

independently.

NOTE: This feature is available only with RAIDCore

VST. See Split Mirrored Arrays (supported only by

RAIDCore VST) on page 90.

Multiple RAID levels per disk Support for multiple array levels per disk allows the administrator

to create arrays of different RAID levels using the same disks.

Native Command Queuing (NCQ) Native Command Queuing is a command protocol of disks that are

supported by RAIDCore. NCQ enables individual disks to internally optimize the order in which Read and Write commands are executed. RAIDCore permits a queue depth of up to 32 read/write commands per disk.

Online Capacity Expansion (OCE) OCE is a process that allows the user to add storage capacity to an

existing array, without taking the system offline. OCE enables the user to increase the total storage capacity of an array by integrating unused storage into the array.

Data can be accessed while the disks are added and while data on the array is being redistributed.

NOTE: This feature is available only with RAIDCore

VST. See Expanding Disk Capacity Online: Using OCE

(supported only by RAIDCore VST) on page 26.

Table 3 Features of RAIDCore (continued)

RAIDCore Feature Description

Page 21

RAIDCore User Manual 19

Online RAID Level Migration (ORLM)

With online RAID level migration, users can easily move an array from one RAID level to another. While the migration is taking place, data is accessible and protected to the lowest protection of either the source RAID level or the destination RAID level.

NOTE: This feature is available only with RAIDCore

VST. See Migrating RAID Levels Online: Using ORLM

(supported only by RAIDCore VST) on page 26.

RAID Level Support Supports RAID levels 0, 1, 1n, 5, 10, 10n, 50, and Volume.

NOTE: RAID 5 is supported by RAIDCore Plus and

RAIDCore VST. RAID 1n, 10n, and 50 are supported by RAIDCore VST.

Self-Monitoring Analysis and Reporting Technology (SMART)

The SMART feature monitors disks and attempts to detect and report potential or impending failures. Its purpose is to be proactive: to allow the user to replace a disk before it degrades or fails.

This feature helps monitor disk performance and reliability, and protects the data on the disk. When problems are detected on a disk, the user can replace or repair the disk without losing any data.

SMART-compliant disks have attributes for which data (attributes) can be monitored, in order to identify changes in values and determine whether the values are within threshold limits. Many mechanical and electrical failures display some degradation in performance before a failure occurs.

Software RAID spanning A feature of the operating system, software RAID spanning allows

the creation of arrays larger than 2 TB. Because Windows has a limit of 2TB of space per array, see Tab le 5 1 on page 112 to create volumes larger than 2TB.

Table 3 Features of RAIDCore (continued)

RAIDCore Feature Description

Page 22

20 Chapter 2 Getting Started

RAIDCore Licensing Overview

RAIDCore ships with a 30-day trial license that can be activated only once on any given system and expires 30 days after the activation. The trial license is included with the RAIDCore installation and does not need an Internet connection to be activated.

Major Features of RAIDCore Licensing

• Programmatic Internet-based online activation: This is done via connection to the Dot Hill Systems Corp. License server at install time or later (requires an Activation ID).

NOTE: Activation can only be done once for a given client system and Activation ID. Any subsequent

activation request involves Dot Hill Systems Corp. technical support. Minor license issues due to hardware changes can be handled via repair (see below). Activation can also be completed after the installation through the GUI or command line tools.

• License event notifications: Uses standard RAIDCore event mechanisms (bc_service.log, bc_popup, GUI, e-mail if configured), consistent with other RAIDCore events.

• License validation check: A license validation check is done to ensure a valid license. A successful license check results in a heartbeat message to the RAIDCore driver.

NOTE: RAIDCore Event Service <bc_service.exe> must be running during the license validation check.

• RAIDCore heartbeat verification checks every hour to make sure that the services are running. If the heartbeat message is missing, the driver generates a warning event after an hour, and reduces performance after another hour. Performance is restored immediately if a valid license check message is received.

• License validation check will cause a significant reduction in RAIDCore performance after a grace period, if the check fails or shows an expired license. The grace period varies depending on circumstances.

• RAIDCore event notification will send a periodic reminder during the grace period (once a day) and more frequent notification after the grace period has elapsed (twice a day).

• RAIDCore license view and repair operations are provided for validated licenses via the GUI or command line tools. A repair might be required when the client machine hardware changes. A license check will detect the need to repair and alert the user.

Page 23

RAIDCore User Manual 21

Features Set: by RAIDCore License Level

Table 4 Feature Set f o r RAIDCore: by RAIDCore License Level

License Levels

Features Sub-Features RAIDCore

Basic

RAIDCore Plus

RAIDCore VST

Legacy/boot drive support Yes Yes Yes

O-ROM (BIOS) support

Create array Yes Yes Yes

Delete array Yes Yes Yes

Boot/INT13 control Yes Yes Yes

RAID levels supported

Volume Yes Yes Yes

0 Yes Yes Yes

1 Yes Yes Yes

10 Yes Yes Yes

5NoYesYes

1n No No Yes

10n No No Yes

50 No No Yes

Array creation

No initialization Yes Yes Yes

Foreground initialization

Yes Yes Yes

Background initialization

Yes Yes Yes

Array copying No No Yes

Array deletion Yes Yes Yes

Mirror splitting No No Yes

Gl ob al Yes Yes Yes

Sparing Dedicated Yes Yes Yes

Distributed No No Yes

Consistency check

Background Yes Yes Yes

Scheduled Yes Yes Yes

Online capacity expansion (OCE)

No No Yes

Online RAID level migration (ORLM) No No Yes

Drive/disk roaming

Same-system support Yes Yes Yes

Between-systems support

Yes Yes Yes

Spanning across multiple controllers No No Yes

RAIDConsole (management GUI) Yes Yes Yes

bcadm (management CLUI) Yes Yes Yes

Page 24

22 Chapter 2 Getting Started

a. At the BIOS Configuration Utility (also referred to as the option-ROM or O-ROM) arrays can be created or deleted, and Critical or Offline

arrays are indicated. INT13 support can be turned off completely at the BIOS Configuration Utility.

b. See Chapter 3 Arrays, Disks, and RAID Levels for detailed information about understanding arrays, RAID levels, and performance and

reliability considerations.

c. The unique ability of RAIDCore to provide online expansion to RAID levels across multiple disks becomes extremely valuable when

expanding storage is a requirement. d. Disk roaming allows arrays to be moved from port to port, either within the same system or between systems. e. Multiple RAID levels (array types) per disk allows the administrator to create different RAID levels on the same disks. For example: The

administrator wants data redundancy for the user data, and creates a RAID 5 set using part of the disks’ data. At the same time the

administrator wants performance for the swap spaces, and creates a RAID 0 array using the rest of the disks’ capacities (space). This

feature is useful in collecting unused capacity from disks with different capacities. f. This feature increases data integrity for redundant array types, by logging areas of an array that have been written to. In the event of a system

crash, the logged area’s consistency is checked and/or corrected. Without this feature, data corruption might occur. g. Arrays can be instantly created and used by skipping the background consistency check. For certain types of redundant arrays this is a

viable option and has no data integrity drawbacks. A consistency check can always be done at a later time. If an initialization is skipped

when using RAID 5 or RAID 50, the array will not be redundant until a consistency check is performed. h. Disks can be added to the system and to an array while the system is operating.

Online license activation Yes Yes Yes

Drive interfaces supported

S ATA Yes Ye s Yes

SAS Yes Yes Yes

SATA C D/ D VD Yes Ye s Ye s

ATAPI Yes Yes Yes

Dissimilar disk support within the same array

Yes Yes Yes

Cache support

No Cache Yes Yes Yes

Read Cache Yes Yes Yes

Write Back Cache Yes Yes Yes

Read with Write Back Cache

Yes Yes Yes

Create Array and Delete Array functions without rebooting

Yes Yes Yes

Restore (rebuild) priority Yes Yes Yes

Multiple RAID levels per disk

Yes Yes Yes

Touched region logging

Yes Yes Yes

E-mail event notification Yes Yes Yes

System event log integration Yes Yes Yes

Instant create support

Yes Yes Yes

Hot-swap support

Yes Yes Yes

Ta ble 4 Feature Set for RAID Core: by RAIDCore License Level (continued)

License Levels

Features Sub-Features RAIDCore

Basic

RAIDCore Plus

RAIDCore VST

Page 25

RAIDCore User Manual 23

3 Chapter 3 Arrays, Disks, and RAID Levels

Understanding Arrays

Arrays are several disks that are grouped together to improve either the performance or reliability of a storage system. Because some RAID levels enhance performance while others improve reliability, it is important to consider the user’s needs when planning an array configuration.

RAIDCore supports various RAID levels. See the following table.

NOTE: It is highly recommended that this user manual be reviewed in its entirety before configuring arrays.

Some of the advanced features of RAIDCore (such as sparing options) must be understood by the user before creating arrays.

RAID Levels

RAIDCore supports the RAID levels indicated in the following table.

Table 5 RAID Levels and Selection Criteria

Number of Disks RAID Level

1 to 4 Volume, RAID 0, RAID 1, RAID 1n, RAID 5

4 and up RAID 10, RAID 10n, RAID 50

Table 6 RAID Levels - General Characteristics

RAID Level Main Characteristic Use/Usefulness

Volume (JBOD) RAIDCore treats one or more

disks or the unused space on a disk as a single array.

1. Concatenation provides the ability to link-together storage from one or several disks, regardless of the size of the space on those disks.

2. Concatenation is useful in scavenging space on disks unused by other disks in the array.

3. Concatenation does not provide performance benefits or data redundancy.

4. When a disk in a concatenated or spanned array fails, data is lost in the array. Because there is no redundancy, data can be restored only from a backup.

RAID 0 (striping) Provides the highest performance

but no data redundancy. Data in the array is striped (distributed) across several disks.

RAID 0 arrays are useful for holding information, such as the operating system paging file, where performance is extremely important but redundancy is not.

RAID 1 (mirroring) Mirrors data on a partition of one

disk to another.

Useful when there are only two disks available and data integrity is more important than storage capacity.

Page 26

24 Chapter 3 Arrays, Disks, and RAID Levels

RAID 1n (n-way mirroring) Mirrors the data stored in one disk

to several disks.

1. This RAID level provides superior data redundancy because there are three or more copies of the data.

2. Useful for creating exact copies of an array for backup purposes.

3. Expensive, in both performance and the amount of disk space necessary to create the array type.

RAID 10 (striped RAID 1 sets) Combines mirrors and stripe sets.

RAID 10 allows multiple disk failures, up to 1 failure in each mirror that has been striped.

1. Offers better performance than a simple mirror because of the extra disks.

2. Requires twice the disk space of RAID 0 to offer redundancy.

RAID 10n Stripes multiple n-way mirror sets.

Allows multiple disk failures per mirror set, up to n-1 failures in each mirror set that has been striped (where n = the number of disks in each mirror set)

1. This RAID level is useful in creating exact copies of an array's data using the Split command.

2. Offers better random read performance than a RAID 10 array, but uses more disk space.

RAID 5 (stripe with parity) Stripes data, as well as parity,

across all disks in the array.

Parity information is interspersed across the disk array.

In the event of a failure, RAIDCore can restore the lost data of the failed disk from the other surviving disks.

1. Offers exceptional read performance, as well as redundancy.

2. Write performance is not an issue due to the tendency of operating systems to perform many more reads than writes.

3. Requires only one extra disk to offer redundancy.

4. For most systems with three or more disks this is the correct choice for a RAID level.

RAID 50 (striped RAID 5 sets) Intersperses parity information

across each RAID 5 set in the array.

1. Offers good read performance, as well as redundancy. A 6-disk array provides two striped, 3-disk RAID 5 sets.

2. Useful in very large arrays (arrays with 10 or more disks).

3. Can handle multiple disk failures.

Table 6 RAID Levels - General Characteristics (continued)

RAID Level Main Characteristic Use/Usefulness

Page 27

RAIDCore User Manual 25

Array States

Within the management applications, an array is a logical device that can exist in one of three states: Normal, Critical, or Offline.

• In RAIDConsole, these states display in the Array List section in a column named State.

• Within the bcadm Command Line tool, these states also display in a column named State.

The array states are defined in the following table.

Whether an array is marked as Critical or Offline depends upon what RAID level it is and how many disks within the array have failed. Note the changes in state in the following table.

For example, RAID 50 is a stripe of RAID 5 sets. If a RAID 50 set contains three RAID 5 sets, each RAID 5 set can have up to one disk failure. The RAID 50 array state shows as Critical. If a third disk fails, the state of the RAID 50 array changes to Offline. Or, if two disks fail on one of the RAID 5 sets, the state of the RAID 50 array changes to Offline.

More than one array can be created using the same set of disks. If a disk is disconnected that belongs to more than one array, only the arrays that try to access the disk and receive I/O errors report the failure. For example: there are two arrays, both of which are RAID 5 sets, and both use disk 4. If a system being used by array 1 receives an I/O error when trying to communicate with disk 4, the state of array 1 changes to Critical. However, the state of array 2 using disk 4 does not change to Critical until an I/O error is reported. If systems using array 1 are not communicating with failed disk 4, the state of array 1 still displays as Normal.

If a rescan of all channels is performed after disconnecting a disk, the state of every array using the missing disk changes from Normal to either the Critical or Offline, depending on the RAID level.

See Rescanning Disks for Changes in State on page 29 for a discussion of when to rescan disks and the outcomes when doing so.

Table 7 Array States

State Description

Normal The Normal state is displayed when everything is functioning correctly.

Critical The Critical state is displayed when the array is no longer redundant (fault tolerant)

because of one or more disk failures. Arrays can still be read and written to, but the data is no longer protected should another disk fail.

Offline The Offline state is displayed when arrays cannot be read or written to because of one or

more disk failures.

Table 8 Failure States by RAID Level

RAID Level This Failure State... Is Displayed Whenever...

RAID 1, RAID 5 Critical A single disk fails.

RAID 1n, RAID 10,

RAID 10n, or RAID 50 (RAID levels with multiple redundancies)

Critical A single disk fails in any one of those sets.

Volume and RAID 0 Offline A single disk fails.

RAID 1 and RAID 5 (redundant arrays)

Offline Two or more disks fail.

RAID 1n, RAID 10, RAID 10n (RAID levels with multiple redundancies)

Offline All disks in a set fail.

RAID 50 (RAID levels with multiple redundancies)

Offline Two or more disks fail.

Page 28

26 Chapter 3 Arrays, Disks, and RAID Levels

Creating Arrays: Future Expansion

When creating arrays, consider whether disk capacity will need to expand in the future. If the file system must be expanded, perform the tasks indicated in the following table.

Expanding Disk Capacity Online: Using OCE (supported only by RAIDCore VST)

Online Capacity Expansion (OCE) allows:

• Adding disks to an array at any time.

• Accessing the array data while it is being redistributed.

To increase the size and organization of an array, transform the array. For more information on transforming arrays, see Transform Arrays (supported only by RAIDCore VST) on page 78.

Migrating RAID Levels Online: Using ORLM (supported only by RAIDCore VST)

Online RAID Level Migration (ORLM) allows an array to move from one RAID level to almost any other RAID level. This task includes migrating the array from a non-redundant RAID level to a redundant RAID level.

Prior to starting a RAID level migration/transformation, make sure that the disks selected for the destination array have sufficient capacity. RAID level migration/transformation can occur only when the destination array has the same or larger capacity as the source array.

While the migration/transformation is taking place, data is accessible and protected to the lowest protection of either the source RAID level or the destination RAID level.

The Transform task can also be used to expand the capacity of an array, by using OCE. It can also be used as part of the system backup and recovery strategy through the use of the RAID 1, RAID 10, RAID 1n, and RAID 10n RAID levels.

To perform this process, see Transform Arrays (supported only by RAIDCore VST) on page 78.

Table 9 Array Expansion Considerations

For This Operating System Do This... And Consider This...

Microsoft Windows

Format the arrays with NTFS. Microsoft Corporation provides a utility (Diskpart.exe) that can dynamically extend an NTFS file system onto any unused adjacent space.

Note also that using a single partition per array makes expansion much easier.

1. The Diskpart.exe utility version depends on which version of the Windows operating system is running.

2. The Diskpart.exe utility can be found on the CD for some versions of Windows operating systems, or on the Microsoft Corporation website

(http://www.microsoft.com

) for other versions. Use the correct version for the operating system.

Linux Use an expandable file system. Because RAIDCore software is limited

to eight arrays, if a large number of logical volumes are needed, use a logical volume manager (LVM).

Page 29

RAIDCore User Manual 27

Array Tasks: Starting and Stopping Tasks

Tasks are started when one of the following actions are performed:

• Create a redundant array.

• Transform an array.

• Copy an array.

• Restore an array.

• Check for consistency on redundant arrays.

• Verify that data was not corrupted after a system crash (Check_Bitmap; performed automatically).

Full task control can be used on Create, Copy, Consistency Check and Bitmap Check tasks. On a Transform or Restore task for dedicated and global spares, task control can only pause/resume, but it cannot remove the task. To remove these types of tasks, pause and then delete them.

NOTE: If a task is paused and then deleted, the array will be deleted. Deleting a task is the same as deleting

an array. Data loss will occur. Backup all data prior to deleting a task that involves a Transform or a Restore.

The tasks indicated in the following table can be displayed for each array.

Table 10 Types of Tasks per Array

Task When Displaye d

Transform While an array is being transformed.

Create While an array is being created.

Copy While an array is being copied.

In a --verbose query, the array numbers of the source and destination array are given (for example, Copy 2>5).

Consistency Check While verifying that the parity (RAID 5) or mirror disk consistency is correct. For

redundant type arrays only.

Restore While an array is being restored.

Check_Bitmap While verifying that the parity on a RAID 5 set, or the mirror halves on a RAID 1 or

RAID 10 set, are consistent. This action is performed automatically to ensure that data is not corrupted whenever a system crashes.

Not_Active When no other tasks are being performed.

Page 30

28 Chapter 3 Arrays, Disks, and RAID Levels

Understanding Disks

Disks States

Within the management applications, a disk can be part of one or more arrays and can exist in one of three states: Online, Offline, or SMART Error.

• In RAIDConsole, these states are displayed in the Disk List section in a column named State. See

Table 2 8 on page 70 for additional information.

• Within the bcadm program, these states are also displayed in a column named State. See Tab l e 59 on page 121 and Tab le 60 on page 122 for additional information.

The disk states are defined in the following table.

If a disk fails it is displayed in the Disk List as Online until a rescan is performed. (If host I/O is going to a failed disk and the disk is used in a single array, the disk appears as Online in the Disk List but is highlighted in red; the disk appears as Failed in Array View. If host I/O is going to a failed disk and the disk is used in multiple arrays, the disk may appear in the Disk List as Offline and as Failed for each array in Array View; after a rescan the Disk List state may change to Online). After the rescan is performed the following can occur:

• A disconnected disk no longer appears in the Disk List (although it appears as Missing in the Array View, for the array(s) that uses the disk).

• A disk that is disconnected, but for which a rescan is not performed, appears in the Disk List as Online. However, if a Background Array Scan or Consistency Check is performed, the disk state changes to Offline and it is highlighted in the Disk List in red.

• A disk that experiences a catastrophic failure appears in the Disk List as Offline and is highlighted in red.

• A disk that has a SMART error appears in the Disk List as SMART Error. (A disk with a SMART error can be used to create an array, but the array must be created in the BIOS Configuration Utility, not in RAIDConsole).

• A disk that experiences a software-related failure appears in the Disk List as Online and is highlighted in red. New arrays can be created with the disk.

Arrays that exist on a failed or disconnected disk might not be designated as Failed or Missing until the system attempts to communicate with the failed or disconnected disk.

RAID Minimum Disk Configurations

The following table lists the minimum disk configurations for each RAID level.

Table 11 Disk States

Disk State When Displayed

Online Whenever the disk is connected, functioning correctly, and RAIDCore can communicate

with it.

Offline Whenever the disk fails and RAIDCore detects an error condition on the disk.

SMART Error Whenever the disk reports a SMART error(s) to RAIDCore.

Table 12 Minimum Disk Configurations per RAID Level

RAID Level Minimum Number of Disks

JBOD (Volume) 1

RAID 0 2

RAID 1 2

RAID 1n 3

RAID 10 4

RAID 10n 6

RAID 5 3

RAID 50 6

Page 31

RAIDCore User Manual 29

Rescanning Disks for Changes in State

The information displayed in the Disk List section is the state of the disks when they were last scanned. If a rescan has not been performed, the information being displayed is the state of the disks at boot time.

Every time a disk is connected or disconnected while online, a message asks if the user wants to perform a

rescan (of all SATA channels). If Rescan is selected, the information in both the Array List and the Disk List

is updated. This view might show arrays as being in a Critical or Offline state, if all disks have not been installed or removed.

Although it is highly recommended that the system be shut down before adding or removing disks, disks can be added or removed while the system is online (“hot-swapping”), if the system supports the hot-swapping function.

Because of this function, RAIDConsole does not automatically perform a rescan when it detects that a disk has been added or removed. For example, to hot-swap a RAID 5 set with six disks into a new system, do not perform a rescan until all six disks have been connected.

Arrays associated with the disks that are not yet connected change state to either Critical or Offline. In the example above, if the state of the RAID 5 set changes to Offline, data is lost.

This feature can also result in the state of a disk being reported differently in the Array View and the Disk List. A disk within an array can have a state of Failed in the Array View field, while at the same time it can show a state of Online in the Disk List.

Sparing Options: Disks and Arrays

RAIDCore supports multiple sparing options. Spares are restored in the order indicated in the following table.

NOTE: An array is marked Critical or Offline if a disk reports a Failed state to an I/O, or if the SAS/SATA

cable or power cable is disconnected.

NOTE: One or more spares can be assigned to a redundant RAID level.

NOTE: Spare assignments do not apply to non-redundant RAID levels. To protect data, transform the array

to a redundant RAID level. Spares can then be assigned. (Be aware that the Transform task is supported only by RAIDCore VST.)

Table 13 Sparing Options

Option Description

Dedicated A spare disk assigned to a specific, redundant array.

Distributed A sparing option that consists of reserved space on each disk in an array.

Global A spare disk that is shared by multiple arrays.

Page 32

30 Chapter 3 Arrays, Disks, and RAID Levels

Distributed Sparing (supported only by RAIDCore VST)

RAIDCore’s proprietary distributed sparing feature reserves space on each disk in an array. This space is used when the data from a failed disk is being regenerated during a Restore task.

Whereas other methods of sparing (such as dedicated spares) provide the same level of protection, distributed sparing provides better performance. All disks are active in an array and are not sitting idle, as is the case with dedicated spares.

Another advantage of distributed spares is that because all disks are active, a disk cannot fail and go unnoticed, as is the case with dedicated or global spares.

With distributed sparing, each array has its own dedicated fail-over spaces. This averts the potential problem of having insufficient space to start a fail-over on the single disk that has been assigned as a spare.

A distributed spare is assigned at the time an array is created or transformed. Distributed spares are valid only for:

• RAID 5 (four or more disks)

• RAID 50 (four or more disks per RAID 5 set)

• RAID 10 and RAID 10n (six or more disks).

This spare type is the most protective, because space is allocated when the array is created. Like a dedicated spare, this spare type is assigned to a specific array.

If an array was created without a distributed spare, the array must be transformed to add a distributed spare. A distributed spare can be assigned only when an array is being created or transformed.

• If there is insufficient unused space on the disks in an array, a distributed spare cannot be added without adding an additional disk and transforming it to an array (with distributed sparing enabled).

• The distributed spare option uses the equivalent storage of one of the disks in the array.

For example: the total capacity of six disks is being used in a RAID 5 array, and distributed sparing has been enabled.

• The capacity of the array is the same as a four-disk RAID 0.

• The capacity of one disk is lost to the RAID 5 parity data.

• The capacity of another disk is lost to the distributed sparing option.

For additional information, see Add or Remove Distributed Spares (supported only by RAIDCore VST) on page 92.

Dedicated Sparing

A dedicated spare is a disk that is assigned as an alternate disk for a specific array. Should a disk fail in that array, the alternate disk is used to replace the failed disk and the array is rebuilt.

A dedicated spare can be assigned to any redundant array type, and up to four spares can be assigned to an array.

NOTE: Assigning a dedicated spare does not reserve space on the disk. Therefore, an automatic restore is not

guaranteed if a disk fails. If a disk fails, make room on the disk for the fail-over to complete, or assign a different disk with enough room. If a dedicated spare is assigned and a disk fails, the restore process starts automatically, if there is enough space available on the dedicated spare.

NOTE: A dedicated spare cannot be assigned while a task is running on the array.

NOTE: When a dedicated spare is assigned while an array is being created or transformed, the first disk

selected to create the array is assigned by default as the dedicated spare.

Page 33

RAIDCore User Manual 31

NOTE: When a dedicated spare is added after the array has been created, select which disk to use as the

spare.

For additional information, see Add or Remove Dedicated Spares on page 92.

Global Sparing

A global spare is a disk that is assigned as an alternate disk for multiple arrays, instead of associating it with only one array.

Many arrays can be restored using the global spare disk, as long as it is not already part of the array and it has enough space available. Unlike a dedicated spare, this type of spare can be assigned at anytime, even while tasks are running on arrays.

Assigning a disk for use as a global spare does not reserve space on that disk. An automatic restore is not guaranteed if a disk fails.

If there is not enough disk space on the global spare, make room for the fail-over to complete, or assign a different disk with enough capacity as the spare. If there is enough space available on the global spare and a disk failure occurs, the restore process starts automatically.

For additional information, see Add or Remove Global Spares on page 93.

RAID Performance Considerations

With RAID technology, performance is based on the following considerations:

• The number and organization of disks in an array.

• Caching attributes used for the array.

• Application workload.

Number and Organization of Disks

RAID functions increase performance by putting more disks to work and by buffering data for the host.

Many disks can transfer data at greater than 50 MB per second. RAIDCore can aggregate this bandwidth in an almost linear fashion, as more of the same disks are included in an array.

Caching Attributes

RAIDCore can also be configured to provide read and Write Back caching, if desired. Write Back caching has a large effect on most workloads, but should be used with caution.

Application Workload

When configuring an array, workload is probably the most important performance variable. Most applications do many more reads than writes, so the best performance will be obtained with array types like RAID 0, RAID 5, or RAID 10.

Page 34

32 Chapter 3 Arrays, Disks, and RAID Levels

RAID Reliability Considerations

RAID reliability is enhanced through data redundancy and backup.

Data Redundancy

RAID 1, RAID 1n, RAID 5, RAID 50, RAID 10, or RAID 10n are necessary for redundancy. With redundancy, both capacity and performance are sacrificed for reliability. With RAIDCore, extremely high performance is obtained even with redundant-type arrays.

Backup

NOTE: The Transform and Mirror Splitting tasks are supported only by RAIDCore VST.

RAIDCore’s ability to transform arrays and split mirrors can be used as part of a backup strategy.

For example, create a RAID 1 or RAID 10 array, yet periodically transform them into RAID 1n and RAID 10n arrays. The RAID 1n and RAID 10n arrays can be split into the original array and a backup array.

As part of a “hot fallback” strategy, the backup array can be kept online and hidden from the operating system or remain visible, or it can be removed from the system and stored as a backup device.

When a boot array is split, the original and the copy are identical and contain the same labels. It is recommended that you keep the split copy hidden during boot time, to avoid boot-time issues with duplicate labels.

Flexibility and Expansion Considerations

Before configuring an array, consider the following points to enhance the flexibility of the RAID system.

Multiple RAID Levels

With RAIDCore, different RAID levels can be created on the same disk, to adapt each array to the I/O that it processes. Also, more than one array can be created per disk.

Depending on the array capacity and redundancy level, an existing array can be transformed to another RAID level, if the level of the array being used is not the optimal RAID level for the application. Also, different arrays with different characteristics can be built for different applications.

Operating System Considerations

An important array planning consideration is whether to extend the RAID benefits to the system disk and operating system, as well as to the data disks.

For example, if the operating system is installed on a RAID 1 array (mirror), split the array into two volumes. Hide one of the resulting volumes. The operating system can be recovered easily if the system disk fails.

Alternatively, improve operating system performance by installing the operating system on a RAID 10 array. Split the array and hide one of the RAID 1 arrays.

To install the operating system on an array and boot from that array, see Create Arrays on page 55.

Page 35

RAIDCore User Manual 33

4 Chapter 4 Installing Software

Before You Begin...

This chapter is designed to get RAIDCore up and running by using default settings. For most users these are the optimal settings.

CAUTION: All components (drivers and applications) must be installed when installing or upgrading

RAIDCore. This means that a previous version driver will not work with the current version of RAIDCore application, and vice versa.

NOTE: To modify a default setting, see the applicable features in Chapter 5 BIOS Configuration Utility, and

either Chapter 6 RAIDConsole Graphical User Interface (GUI) or Appendix B bcadm Command Line Tool.

System Setup Process

A generic system setup process is described in the following table.

Table 14 System Setup Process

Process Action

1. Startup the system.

2. Access the BIOS setup window for the system.

Set the SATA mode per the type of chipset. For supported AMD chipsets, set

the SATA mode as RAID (for use with RAIDCore).

3. Enable the applicable chipset.

Refer to the BIOS configuration procedure in the motherboard’s instruction manual.

4. Initialize the disks. See Initialize Disks on page 54.

5. Create arrays using the RAIDCore BIOS Configuration Utility.

See Create Arrays on page 55.

6. Copy the drivers to removable storage media.

See Copy Drivers to Removable Storage Media: Windows Operating

Systems on page 34.

Copy Drivers to Removable Storage Media: Linux Operating Systems on

page 35.

7. Install the drivers on the system.

See Install Drivers on a System at the Same Time That the Windows

Operating System is Installed on page 36.

Install Drivers on a System at the Same Time That the Linux Operating System Is Installed on page 41.

8. Install the Management Suite on the system.

See Install Drivers, Configuration Devices, and the Management Suite:

Windows on page 37.

Install Drivers, Configuration Devices, and the Management Suite: Linux on

page 49.

Page 36

34 Chapter 4 Installing Software

Copy Drivers to Removable Storage Media: Windows Operating Systems

When installing the operating system to a RAIDCore bootable array, copy the drivers for RAIDCore to removable storage media (CD-ROM, DVD, flash drive, floppy disk, etc).

Use a system that is running a Windows operating system and has a a CD-ROM or DVD drive, floppy drive, or an I/O port for removable storage media, such as a flash drive.

1. Insert the storage medium into the applicable drive, or connect a flash drive to a USB or similar port.

• Windows Server 2003

: Insert a floppy disk into the disk drive.

• Windows Server 2008 or Windows Server 2008 R2

: Insert a blank CD-ROM or DVD into the applicable

drive, or connect a flash drive to a USB or similar port.

2. Insert the RAIDCore Media CD-ROM into a second CD-ROM or DVD drive.

3. Copy the files from the applicable folder on the RAIDCore Media CD-ROM, as indicated in the following

table.

NOTE: If the drivers are being installed on a system that has an existing operating system, skip step 4 and

proceed to Install Drivers, Configuration Devices, and the Management Suite: Windows on page 37.

Use the storage medium and its copied files to install the drivers. See Install Drivers on a System at the Same Time That the

Windows Operating System is Installed on page 36.

Table 15 Driver Files for Windows Operating Systems

Operating System Files to Copy to a Floppy Disk or Storage Media

Windows Server 2003 SP2

For 32-bit Windows Server 2003 systems: copy all of the files in the windows\driver\bcraid\i386\W2k3 folder to the floppy disk.

For 64-bit Windows Server 2003 systems: copy all of the files in the windows\driver\bcraid\x86_64\W2k3 folder to the floppy disk.

Windows Server 2008 SP2, Windows Server 2008 R2

For 32-bit Windows Server 2008 systems: copy all of the files in the windows\driver\bcraid\i386\W2k8 folder to the storage media.

For 64-bit Windows Server 2008 or 2008 R2 systems: copy all of the files in the windows\driver\bcraid\x86_64\W2k8 folder to the storage media.

Page 37

RAIDCore User Manual 35

Copy Drivers to Removable Storage Media: Linux Operating Systems

To install a bootable array, copy the drivers on the RAIDCore Media CD-ROM to removable USB storage media.

• A SATA DVD drive cannot be used to load the drivers.

• A USB DVD drive can be used to install the operating system and drivers.

Removable storage media are needed only if a bootable array is installed. If the installation is not to a bootable array, follow the procedure Install Drivers, Configuration Devices, and the Management Suite: Linux on page 49.

1. Connect a flash drive to a USB port.

2. Insert the RAIDCore Media CD-ROM into the system’s CD-ROM or DVD drive.

3. Mount the RAIDCore Media CD-ROM at a convenient location. (The RAIDCore Media CD-ROM is in

ISO 9660 format).

Example: mount /dev/cdrom /mnt/cdrom

4. To find the kernel version, processor type, and architecture, at the command prompt, type: uname -a Example output: Linux <system>.<domain> 2.4.21-4.ELsmp #1 SMP <date & time>

i686 GNU/Linux

5. From the <cd mount point>/linux/<vendor>/<version>/driver folder, select the

distribution version of Linux.

6. Copy the .iso image file (which match the distribution of Linux) to the desktop.

• For Red Hat Linux

• Copy the .iso file from the desktop to the USB flash drive.

• For SUSE Linux

• Mount the .iso image file. For example: <mount -o loop “the name of the iso file”/media>

• Navigate to /media and copy the .iso folder/files from /media to the USB flash drive.

NOTE: If the system/server used to copy the .iso image to the USB flash drive uses a Windows operating

system, perform “a” or “b” below: a. Use an application (such as WinImage) to extract the .iso image directly onto the USB flash drive. or b. Use an application (such as Nero Express Essentials) to burn the .iso image onto a CD-ROM. Then, copy the burned .iso image from the CD-ROM onto a USB flash drive.

Use the USB removable storage medium to install the drivers during the driver installation process. See Install

Drivers on a System at the Same Time That the Linux Operating System Is Installed on page 41, or Install Drivers, Configuration Devices, and the Management Suite: Linux on page 49.

Page 38

36 Chapter 4 Installing Software

Install Drivers and Applications: Windows Operating Systems

There are two situations under which RAIDCore can be installed:

• At the same time that the Windows operating system is installed. See Install Drivers on a System at the Same

Time That the Windows Operating System is Installed below.

• After the Windows operating system has been installed. See Install Drivers, Configuration Devices, and the

Management Suite: Windows on page 37.

Install Drivers on a System at the Same Time That the Windows Operating System is Installed

CAUTION: All components (drivers and applications) must be installed when installing or upgrading

RAIDCore. This means that a previous version driver will not work with the current version of RAIDCore applications and vice versa.

Follow these functions, if the operating system is being loaded onto a RAIDCore bootable array:

• Modify the boot priority list in the motherboard BIOS. See the motherboard manual for information.

• Make sure that the RAIDCore bootable array is included in the boot priority list.

• At the BIOS Configuration Utility, make sure that INT13 support is ON for RAIDCore. See Change the

Controller Options on page 60.

• At the BIOS Configuration Utility, make sure that the boot array is the first array listed in the Arrays list. Use the Swap Two Arrays task to place the boot array first. See Swap Arrays on page 58.

Install the drivers

1. Follow Microsoft procedures to install the applicable Windows operating system.

NOTE: At step 2 for Windows Server 2003, press F6 immediately.

2. At the Windows Setup window, perform the following:

• Windows Server 2003

: Press F6 to install the driver.

• Windows Server 2008 or Windows Server 2008 R2

: Click Load Driver to install the driver.

3. When prompted, insert the storage medium into the applicable drive or USB or similar port:

• Windows Server 2003

: Press S, then press Enter.

• Windows Server 2008 or Windows Server 2008 R2

:Press Load Driver, then press Enter.

4. Windows should report that it found the drivers. Press Enter to select and load the drivers.

5. Press Enter to continue. Follow the on-screen instructions to complete the installation of the applicable

Windows operating system.

6. After the operating system is installed, see Install Drivers, Configuration Devices, and the Management Suite:

Windows on page 37.

7. Remove the storage medium from the applicable drive or USB or similar port.

Page 39

RAIDCore User Manual 37

Install Drivers, Configuration Devices, and the Management Suite: Windows

Installing or upgrading RAIDCore involves the installation of RAIDCore drivers, RAIDCore configuration devices, and the Management Suite.

NOTE: The windows shown in this section are typical. Path names and text can vary, depending on

user-designated selections and other parameters.

Table 16 Windows Operating System: Install Drivers, Configuration Devices, and Management Suite

Element Action

1. RAIDCore Media CD-ROM Insert the RAIDCore Media CD-ROM in the system’s CD-ROM or DVD

drive.

NOTE: If AutoPlay is disabled, or if the Dot Hill

window is

not visible, select Start -> Computer. Click on Computer. Right-click on the CD-ROM/DVD drive icon. Select Open

AutoPlay....The AutoPlay window appears. Select

RunAutoPlay.exe. The Dot Hill

window now appears.

NOTE: When the Management Suite is installed from the

RAIDCore Media CD-ROM, several components are installed. See

Table 17 on page 39.

2. Dot Hill® window Select Install Windows Management Suite. See Figure 1 on page 40.

3. InstallAnywhere window Wait while it prepares for the installation. (Other windows appear

momentarily during the preparation process).

4. Introduction window a. Read the text carefully.

b. To proceed with the installation click Next.

NOTE: A Previous Version found dialog box appears whenever

RAIDCore is upgraded. Read the text carefully about uninstalling a

previous version of RAIDCore. Click No to uninstall the previous version. Click Yes to continue installing the Management Suite.

5. License Agreement window a. Select I accept the terms of the License Agreement. See

Figure 2 on page 40.

b. Click Next.

6. What would you like to

install? window

a. Click Management Suite with Drivers. b. Click Next.

7. Important - Please Be

Advised window

a. Read the advisory message. b. To continue installing the RAIDCore driver, click OK.

8. Choose Install Folder

window

a. Accept the default settings. b. Click Next.

9. Choose Shortcuts window a. Choose the desired shortcuts for the Management Suite.

b. Click Next.

Page 40

38 Chapter 4 Installing Software

10. Pre-Installation Summary

window

a. Review the selections. b. If they are OK, click Install.

NOTE: The Installing the RAIDCore(tm) Management Suite

window appears, showing the progress of the installation.

11. Software Installation window

[Windows Server 2003 only]

a. This window might appear. It warns that the software has not passed

Windows Logo testing.

b. Ignore the warning. Click Continue Anyway.

12. Hardware Installation

window [Windows Server 2003 only]

a. This window might appear. It warns that the software for the

controller has not passed Windows Logo testing.

b. Ignore the warning. Click Continue Anyway.

13. Hardware Installation

window [Windows Server 2003 only]

a. This window might appear again for each additional controller. b. Click Contin ue Anyway again.

14. Windows Security - Would

you like to install this device software? window [Windows Server 2008 or Windows Server 2008 R2 only]

a. This window might appear for the Dot Hill Systems Corp. system

devices. Read the text carefully.

b. Click Install.

15. Windows Security - Would

you like to install this device software? [Windows Server 2008 or Windows Server 2008 R2 only]

a. This window might appear for the Dot Hill Systems Corp. storage

controllers. Read the text carefully.

b. Click Install.

16. Activation Needed window a. This window appears only if a trial license is installed on the system. b. Decide whether to accept or skip full license activation.

• To accept activation click Next. The Enter Activation window

appears. Continue with step 17.

• To skip activation, check the Skip Activation check box. Click

Next. Continue with step 20.

17. Enter Activation ID window Perform one of the following:

• For a licensed

version of RAIDCore: Enter an Activation ID

number. Click Next.

•For a trial

version of RAIDCore: Check I do not have an

Activation ID. Click Next.

18. Activation was successful

window

a. Appears only for a licensed

version of RAIDCore.

b. Click Next and continue with step 20.

Element Action

Page 41

RAIDCore User Manual 39

Table 17 Components of the Management Suite

19. Trial license successfully

activated window

a. Appears only for a trial

version of RAIDCore.

b. Click Next.

NOTE: The Trial license successfully activated window appears

only when a license is activated for the first time, or when a license has expired and a new license is activated.

NOTE: A Trial license activation was unsuccessful window

appears if the Activation Specification Record (ASR) for the system has already been activated. Read the text carefully at the window

and decide whether to return to the previous window or click Next. When Next is selected the installation process advances to the

Install Complete window. See step 20.

20. Install Complete window Click Done to restart the system.

21. RAIDCore Media CD-ROM Remove the RAIDCore Media CD-ROM from the CD-ROM or DVD

drive.

Component Description For More Information...

RAIDConsole A management application that has a graphical

user interface (GUI) and an array maintenance service application.

See Chapter 6 RAIDConsole

Graphical User Interface (GUI).

bcadm A command-line alternative for managing the

controller, disks, and arrays.

See Appendix B bcadm Command

Line Tool.

Element Action

Page 42

40 Chapter 4 Installing Software

Figure 1 Dot Hill® window, showing Install Windows Management Suite selected

Figure 2 License Agreement window, showing I accept the terms of the License Agreement

selected.

Page 43

RAIDCore User Manual 41

Install Drivers and Applications: Linux Operating Systems

There are two situations under which RAIDCore can be installed:

• At the same time that the Linux operating system is installed. See Install Drivers on a System at the Same Time That the Linux Operating System is Installed below.

• After the Linux operating system has been installed. See Install Drivers, Configuration Devices, and the

Management Suite: Linux on page 49.

Install Drivers on a System at the Same T ime That the Linux Operating System Is Installed

NOTE: The Linux operating system modules must include the gcc+ compiler and the pthreads library, so that

the bcadm program can be installed properly.

The Linux operating system and the RAIDCore software drivers can be installed at the same time. There are separate procedures in this section for:

• Red Hat Linux

• SUSE Linux

Follow these important functions:

• If the installation is to a bootable array, the boot priority list must be modified in the motherboard BIOS. See the motherboard manual for more information.

• Make sure that the RAIDCore bootable array is included in the boot priority list.

• Disable other IDE devices.

• Make sure that INT13 support is enabled on the controller. See Change the Controller Options in Chapter 5.

• The boot array must be the first array listed in the Arrays list of the RAIDCore(tm) Array Configuration window. Use the Swap Two Arrays feature to place the boot array first. For details, see Swap Arrays on page 58.

• A USB flash drive must be used to install the drivers for Red Hat Linux 5.3 and 5.4 and SUSE Linux 10.3 and 11.

NOTE: A USB DVD drive can be used to install the operating system and drivers.

Page 44

42 Chapter 4 Installing Software

Install Drivers at the Same Time That Red Hat Linux is Installed

NOTE: Prior to starting this procedure, copy the RAIDCore drivers on the RAIDCore Media CD-ROM to

removable storage media. See Copy Drivers to Removable Storage Media: Linux Operating Systems on page 35.

NOTE: When installing Red Hat Linux using the RAIDCore Media CD-ROM, use the Linux dd installation mode instead of the Linux expert mode.

NOTE: Not all of the windows indicated in the table below might appear during an installation.

Table 18 Installing the Red Hat Linux Drivers

Element Action

1. Power-on the system Make sure the system is loaded with the Linux operating system.

2. Red Hat OS CD-ROM or

DVD

Insert the Red Hat operating system CD-ROM or DVD into the system’s CD or DVD drive.

3. Enter BIOS utility (O-ROM) At the system’s Power-On Self-Test (POST) screen, click Ctrl + R.

4. Create a bootable array. a. Use the Create Array command in the Main Menu. b. Make sure the bootable array is listed first in the Array section of the

BIOS Configuration Utility.

5. Boot the system. Scroll to Continue to Boot and click Enter

6. Insert a USB drive (which

contains the drivers and the rc-ks.cfg file)

At Red Hat Enterprise Linux 5 window, type:

linux noprobe=ata ks=hd:sdb1:rc-ks.cfg dd

NOTE: The script of the rc-ks.cfg file automatically installs

the operating system to the first array listed in the RAIDCore BIOS Configuration Utility.

NOTE: rc-ks.cfg is a Red Hat Kickstart file that is required to

correctly install the Dot Hill System RAID driver. More information about Kickstart files can be found at:

https://fedoraproject.org/wiki/Anaconda/Kickstart

7. Driver Disk window a. Tab to Yes. b. Click Enter.

8. Driver Disk Source window a. Select /dev/sda1. b. Tab to OK. c. Click Enter.

9. Select Driver Disk Image

window

a. Select the applicable driver. b. Tab to OK. c. Click Enter.

Page 45

RAIDCore User Manual 43

10. More Driver Disks? window a. Tab to No. b. Click Enter.

NOTE: If the Arrays section of the BIOS Configuration Utility

contains more than one array, increase sdb to sdx. For example, if there are two virtual disks, increase sdb to sdx.

NOTE: If an Error Downloading Kickstart File window appears, modify the kickstart parameter. Tab to OK. Click Enter.

11. Choose a Language window a. Choose the default language (English). b. Tab to OK. c. Click Enter.

12. Keyboard Type window a. Choose the default keyboard type (US). b. Tab to OK. c. Click Enter.

13. Installation Method window a. Choose the default installation method (Local CDROM). b. Tab to OK. c. Click Enter.

14. Installation Number window a. Choose one of the following:

• Enter Installation Number:

• Skip entering Installation Number

b. Click OK.

15. Skip dialog box Click Skip.

16. Warning dialog box If the text is OK, click Yes.

NOTE: If No is selected, the bootable array created in step 3 will

not be used.

17. Red Hat Enterprise Linux 5

window

Choose Remove all partitions on selected drivers and create default layout from the pull-down menu.

18. RAIDCore array check box a. Check the check box next to the RAIDCore array that was created in

the BIOS Configuration Utility.

b. Un-check the check-box(es) next to other arrays. c. Click Next.

19. Warning dialog box Click Yes.

20. Region window a. Mouse-over the world map, or use the pull-down menu, and choose

the applicable time zone.

b. Click Next.

21. Root account window a. Enter the applicable root password. b. Re-enter the root password. c. Click Next.

Element Action

Page 46

44 Chapter 4 Installing Software

22. Desktop Environments and

GNOME Desktop Environment window

a. Highlight the desktop environments one at a time. b. Leave the default package settings as-is. c. Check-mark the following packages:

• Development

• Development Libraries

• Development Tools

• Legacy Software Development

• Base System

• System Tools

NOTE: System Tools is a recommended selection, but is not

required.

23. USB flash drive When the installation is finished remove the USB flash drive and Red Hat

operating system CD or DVD from the system.

24. Reboot the system a. At the system’s POST screen, use Ctrl + R to access the BIOS

Configuration Utility.

b. Make sure that the bootable array is the first array listed in the Array

section of the BIOS Configuration Utility.

c. Select Continue to Boot.

25. Install the Management Suite

and drivers

See Install Drivers, Configuration Devices, and the Management Suite:

Linux on page 49.

Element Action

Page 47

RAIDCore User Manual 45

Install Drivers at the Same Time That SUSE Linux is Installed

NOTE: Prior to starting this procedure, copy the RAIDCore drivers on the RAIDCore Media CD-ROM to

removable storage media. See Copy Drivers to Removable Storage Media: Linux Operating Systems on page 35

NOTE: The SUSE driver CD-ROM .iso image contains all Linux variations for a particular release (smp,

bigsmp, etc.). Therefore, only one .iso file exists.

SUSE Linux 10.3 Procedure

Table 19 SUSE Linux 10.3: Installing the SUSE Linux Drivers

Element Action

1. Power-on the system Make sure the system is loaded with the Linux operating system.

2. SUSE Linux OS CD or DVD Insert the SUSE Linux operating system CD-ROM or DVD into the

system’s CD or DVD drive.

3. Enter BIOS utility (O-ROM) At the POST screen, click Ctrl + R.

4. Create a bootable array. a. Use the Create Array command in the Main Menu. b. Make sure bootable array is listed first in the Array section. c. Scroll to Continue to Boot and click Enter.

5. Insert the USB flash drive

(which contains the drivers).

a. At the SUSE Linux Enterprise Server window, scroll down to

Installation.

b. At Boot Options type:

brokenmodules=ahci oem-modules=1

NOTE: Type the command line within 3 to 5 seconds of the

window appearing.

c. Click Enter.

NOTE: It might be necessary to press F3, to change the Video

Mode to VESA, if no video appears on the monitor.

6. Language window Make sure English (US) is highlighted. (As desired, choose a different

language). Click Next.

7. License Agreement window a. Read the text. b. Click the Yes, I Agree to the License Agreement radio button. c. Click Next.

8. Installation Mode window a. Make sure that New Installation (default) is selected. b. Click Next.

9. Clock and Time Zone

window

a. Select the desired Region and Time Zone. b. Un-check the Hardware Clock Set to UTC check-box (if local

time is desired).

c. Click Next.

10. Installation Settings window a. Click the Overview tab. b. Click the Software category.

Page 48

46 Chapter 4 Installing Software

11. Software Selection a. At the Software Selection and System Tasks window: Select the

Development category.

b. Check the C/C++ Compiler and Tools check-box. c. Click the Details... button. d. At the Filter: pull-down menu, choose Search. e. At Search, enter libstdC++. Click Search. f. At the check-boxes that appear on the right-hand section of the

window, check the check-box that corresponds to the 32-bit standard

C++ shared library. Click Accept.

12. Agfa fonts At the agfa-fonts window: click Accept.

13. Automatic changes At the Automatic Changes window: click Continue.

14. Installation Settings window At the Installation Settings window:

a. Click the Overview tab. b. Click the Partitioning category.

15. Suggested Partitioning

window

a. Read the text. b. Choose Accept Proposal (default). c. Click Next.

16. Installation Settings window a. Click the Expert tab. b. Click the Booting category.

17. Boot Loader Settings

window

a. Click the Boot Loader Installation tab. b. Change the setting from Boot from Boot

Partition to Boot from Master Boot Record.

c. Click Finish.

18. Installation Settings window a. Click Accept

19. Confirm Installation window Click Install.

20. Perform Installation process Wait while the Perform Installation process runs.

21. Finish the installation Finish the installation process by entering a root password and completing

the site-specific information as it appears on-screen.

22. USB flash drive and OS disk When the installation is finished remove the USB flash drive and the SUSE

Linux operating system CD or DVD from the system.

23. Reboot the system a. At the system’s POST screen, use Ctrl + R to access the BIOS

Configuration Utility.

b. Make sure that the bootable array is the first array listed in the Array

section of the BIOS Configuration Utility.

c. Select Continue to Boot.

24. Install the Management

Suite.

Proceed to the Management Suite installation procedure. See Install

Drivers, Configuration Devices, and the Management Suite: Linux on

page 49.

Element Action

Page 49

RAIDCore User Manual 47

SUSE Linux 11 Procedure

Table 20 SUSE Linux 11: Installing the SUSE Linux Drivers

Element Action

1. Power-on the system Make sure the system is loaded with the Linux operating system.

2. SUSE Linux OS CD or DVD Insert the SUSE Linux operating system CD-ROM or DVD into the

system’s CD or DVD drive.

3. Enter BIOS utility (O-ROM) At the POST screen, click Ctrl + R.

4. Create a bootable array. a. Use the Create Array command in the Main Menu. b. Make sure bootable array is listed first in the Array section. c. Scroll to Continue to Boot and click Enter.

5. Insert the USB flash drive

(which contains the drivers).

a. At the SUSE Linux Enterprise Server window, scroll down to

Installation.

b. At Boot Options type:

brokenmodules=ahci oem-modules=1

NOTE: Type the command line within 3 to 5 seconds of the

window appearing.

c. Click Enter.

NOTE: It might be necessary to press F3, to change the Video

Mode to VESA, if no video appears on the monitor.

6. Welcome window a. Check the I Agree to the License Terms box. b. Make sure that the Language and Keyboard Layout categories

are at English (US). (As desired, choose a different language).

c. Click Next.

7. Media Check window a. Make sure that the CD or DVD Drive setting is correct. b. Click Next.

8. Installation Mode window a. Make sure that New Installation (default) is selected. b. Click Next.

9. Clock and Time Zone

window

a. Select the desired Region and Time Zone. b. Un-check the Hardware Clock Set to UTC check-box (if local

time is desired).

c. Click Next.

10. Server Base Scenario

window

a. Make sure that Physical Machine (default) is selected. (As

desired, choose other settings at the window).

b. Click Next.

11. Installation Settings window a. Click the Overview tab. b. Click the Software category. c. At the Development category, check the C/C++ Compiler and

Tools check-box.

d. Click the Details... button.

Page 50

48 Chapter 4 Installing Software

12. Software details a. At the Filter: pull-down menu, choose Search. b. At Search, enter libstdC++. Click Search. c. At the check-boxes that appear on the right-hand section of the

window, make sure the check-boxes that correspond to the 32-bit

standard C++ shared libraries are checked. Click Accept.

13. Agfa fonts At the YaST2 agfa-fonts window: click Accept.

14. Changed packages At the Changed Packages window: click Continue.

15. Installation Settings window At the Installation Settings window: a. Click the Overview tab.

b. Click the Partitioning category.

16. Preparing Hard Disk: Step 1

window

a. Select the RAIDCore array that was created in step 4. b. Click Next.

17. Preparing Hard Disk -- Step

2 window

a. Review the text. b. Click Next.

18. Installation Settings window a. Click the Expert tab. b. Click the Booting category. c. Click the Boot Loader Installation tab. d. Change the setting from Boot from Boot Partition to Boot

from Master Boot Record. Click OK.

e. At the main menu of the Installation Settings window. Verify that

they are correct.

f. If the settings are OK, click Install.

19. Confirm installation At the YaST2 Confirm Installation window: a. Review the text.

b. Click Install.

20. Perform Installation process Wait while the Perform Installation process runs.

21. Finish the installation Finish the process by entering a root password and completing the

site-specific information as it appears on-screen.

22. USB flash drive and OS disk When the installation is finished remove the USB flash drive and the SUSE

Linux operating system CD or DVD from the system.

23. Reboot the system a. At the system’s POST screen, use Ctrl + R to access the BIOS

Configuration Utility.

b. Make sure that the bootable array is the first array listed in the Array

section of the BIOS Configuration Utility.

c. Select Continue to Boot.

24. Install the Management

Suite.

Proceed to the Management Suite installation procedure. See Install

Drivers, Configuration Devices, and the Management Suite: Linux on

page 49.

Element Action

Page 51

RAIDCore User Manual 49

Install Drivers, Configuration Devices, and the Management Suite: Linux

NOTE: See Supplemental Linux Information on page 52, for the manual driver installation procedure, in

case you do not want to use the graphical installer.

NOTE: The operating system should automount the RAIDCore Media CD-ROM, but it might need to be

mounted manually.

Table 21 Linux Operating System: Install Drivers, Configuration Devices, and Management Suite

Element Action

1. RAIDCore Media CD-ROM Insert the RAIDCore Media CD-ROM in the system’s DVD-ROM drive.

2. CD-ROM drive window Locate the Linux directory (folder) and double-click it.

3. Apps directory (folder) Double-check the folder when it appears.

4. Setup.bin icon a. Drag the Setup.bin icon from the Apps directory (folder) to the

system’s desktop.

b. Wait while Linux copies the Setup.bin file.

5. Setup.bin file a. Verify that the Setup.bin file is executable by right-clicking on

the Setup.bin icon that is on the desktop.

b. From the pop-up menu, select the Properties category. c. Click the Permissions tab.

6. Permissions tab a. Make sure that the Execute or Executable box(es) is/are

check-marked.

b. Click Close.

7. Setup.bin icon Perform one of the following procedures, depending on the Linux software:

Red Hat Linux

a. Double-click the Setup.bin icon that is on the desktop. b. At Do you want to run “Setup.bin” or display its

contents?, click Run.

c. Wait while Linux runs the Management Suite installer.

SUSE Linux

a. Right-click anywhere on the desktop. b. Select Terminal (or similar) at the popup menu, to open a Terminal

window.

c. At the Terminal window type: <./set.bin>. Click Enter. d. Wait while Linux runs the Management Suite installer.

NOTE: If the message, Do you want to run ‘Setup.bin’ or

display its contents? (or a similar message) appears click Run (or

similar).

NOTE: When the Management Suite is installed from the

RAIDCore Media CD-ROM, several components are installed. See

Table 22 on page 51.

Page 52

50 Chapter 4 Installing Software

8. Introduction window Click Next.

NOTE: A Previous version found window might appear. It warns

that previous versions of the software must be removed before

installing the new software. To continue, click Yes.

9. License Agreement window a. Select I accept the terms of the License Agreement. b. Click Next.

10. What would you like to

install? window

a. Select Management Suite with Drivers. b. Click Next.

11. Important - Please Be

Advised window

a. Read its text carefully. b. To continue installation, click OK.

12. Choose Install Folder

window

a. Accept the default settings. b. Click Next.

13. Choose Shortcuts window Click Next.

14. Pre-Installation Summary

window

a. Review the selections. b. If they are OK, click Install.

NOTE: Wait until the functions at the Install RAIDCore(tm)

Management Suite window are completed.

15. Enter Activation ID window Perform one of the following:

• For a licensed

version of the RAIDCore software: enter an

Activation ID number. Click Next.

•For a trial

version of the RAIDCore software: check I do not have

an Activation ID. Click Next.

16. Activation was successful

window

a. Appears only for a licensed

version of the RAIDCore software.

b. Click Next.

17. Trial license successfully

activated window

a. Appears only for a trial

version of the RAIDCore software.

b. Click Next.

18. Reboot required window Click OK.

19. Install Complete window Click Done.

20. Remove the CD-ROM Remove the RAIDCore Media CD-ROM from the system’s CD or DVD

drive.

21. Reboot the system. Make sure that RAIDConsole functions correctly after the system reboots.

Element Action

Page 53

RAIDCore User Manual 51

Table 22 Components Installed with the Management Suite (Linux)

Component Description For More Information...

bcadm A command-line alternative for managing the

controller, disks, and arrays

See Appendix B bcadm Command

Line Tool.

RAIDConsole A management application that has a graphical

user interface (GUI) and an array maintenance service application.

See Chapter 6 RAIDConsole

Graphical User Interface (GUI).

Page 54

52 Chapter 4 Installing Software

Booting from a Legacy Disk

Legacy disks include new, uninitialized disks; disks that contain non-RAIDCore data; or disks that contain an operating system and that are connected to a motherboard that has a RAIDCore controller.

A legacy disk appears, in the BIOS Configuration Utility and in RAIDConsole, as a legacy array. When the legacy disk is initialized using RAIDCore, RAIDCore configuration data is written to the disk. The legacy array then becomes an online disk that can be used in a RAIDCore array.

1. Shut down the system.

2. Connect the legacy disks to the ports on the motherboard.

3. Boot the system.

4. Install the RAIDCore drivers for the particular operating system. For Windows operating systems see Install

Drivers and Applications: Windows Operating Systems on page 36. For Linux operating systems: see Install Drivers and Applications: Linux Operating Systems on page 41.

NOTE: It is not necessary to initialize disks or create arrays when installing the controller drivers.

5. Boot the system.

NOTE: The legacy array should now exist in the RAIDCore BIOS, and the system should be booting from

the legacy disk.

Supplemental Linux Information

Manually Install RAIDCore Drivers on an Existing Installation of Linux

If Linux has already been installed on the system, you need only to install the drivers for the RAIDCore software.

Install the RAIDCore software driver

1. Boot-up Linux.

2. Insert the RAIDCore Media CD-ROM in the CD-ROM drive.

3. Follow the procedures at Install Drivers and Applications: Linux Operating Systems on page 41.

NOTE: If a problem occurs, manually install the drivers by following the manual installation procedure

below.

Manually install the RAIDCore driver

In a terminal window install the driver:

cd /opt/raidcore/driver_sdk ./install

NOTE: The install script requires that the kernel-development packages be installed. The kernel source and

headers are required to build the matching RAIDCore drivers.

After the drivers for the RAIDCore software are installed, install the bcadm program to manage the RAID controllers, arrays, and disks.

Page 55

RAIDCore User Manual 53

5 Chapter 5 BIOS Configuration Utility

When to Use the RAIDCore BIOS Configuration Utility

The RAIDCore BIOS Configuration Utility is also known as the option ROM (O-ROM) or the RAIDCore(tm) /VST Array Configuration. Use the utility to accomplish the actions indicated in the following table.

Access the RAIDCore BIOS Configuration Utility

When booting the system, press Ctrl + R when the BIOS banner displays. There is a maximum of three (3)

seconds to use this key combination to enter the BIOS Configuration Utility.

Understanding the Color Code in the BIOS Configuration Utility

Color codes indicate the type or status of information at the BIOS Configuration Utility. See the table below.

Table 23 Reasons for Using the RAIDCore BIOS Configuration Utility (Option ROM)

Action Description Find More Information At...

Create a boot array If the system is not booting off the

array, this utility does not need to be used to create an array, although it can. A non-bootable array can be created in the RAIDConsole management application.

Table 51 on page 112.

Create New Arrays: bcadm --create on page 123.

Initialize a new disk To initialize a new disk drive for

data storage.

Initialize Disks on page 54.

Create or delete arrays Create arrays at different RAID

levels (depending on the license level for the system).

Create Arrays on page 55.

Delete Arrays on page 58.

Swap arrays Change the array order, especially

for the bootable array.

Swap Arrays on page 58.

View disk and array details View information about each disk or

array.

View Disk Details on page 59.

View Array Details on page 60.

Change controller options Change INT13 boot support, turn off

Critical arrays or warning for Offline arrays while booting, or change the number of disks that can spun-up when the system is powered-on.

Change the Controller Options on page 60.

Table 24 BIOS Color Codes

Action Description

White text Indicates an available option or informational text.

Black text, yellow highlighting

Indicates an option or device for which action might be taken.

Yellow text Indicates information about the yellow-highlighted option.

Green text Indicates an item that has been selected.

Light blue text Indicates that the item cannot be selected.

Magenta text Indicates items that are related to spares or boot options.

Red text Indicates a failed virtual or physical disk or a warning. For example, informational

text might be red if an option is not available.

Page 56

54 Chapter 5 BIOS Configuration Utility

Initialize Disks

New disks must be initialized before they can be used.

Initialization writes RAIDCore configuration information (metadata) to the disk. The RAIDCore BIOS Configuration Utility can be used to create and manage arrays, so that the operating system and device drivers can be installed on a RAIDCore bootable array. The system is booted from this array.

Before you begin...

• To boot from a RAIDCore array and continue to use the hard disks connected to the controller, refer to the motherboard manual for the specific BIOS Configuration Utility settings. This will establish the proper boot order.

• To boot from another controller within the system, disable INT13 installation in the BIOS Configuration Utility. See Change the Controller Options on page 60.

Initialize Disks

CAUTION: If a disk is part of a RAIDCore array, the disk cannot be selected for initialization. To initialize

this disk anyway, delete the array. Be sure this is what is desired, because the data on the disk will be deleted.

1. Power-up the system to start booting.

2. When prompted, press the Ctrl + R keys to access the RAIDCore BIOS Configuration Utility. The

RAIDCore(tm) Array Configuration window is displayed.

NOTE: If the BIOS is not displayed, contact Support at Dot Hill Systems Corp.

3. Use the arrow keys to select Initialize Disk(s) from the Main Menu.

4. Press Enter.

5. Use the arrow keys to highlight a disk, and then press the Insert key to select the disk or choose all

selectable disks by pressing the A key.

NOTE: Multiple disks can be selected; there is no need to initialize one disk at a time.

6. Press Enter to initialize the selected disks.

7. Press the C key to confirm the initialization or press Esc to cancel the initialization.

Initialization takes 10–15 seconds per disk. A status indicator shows which disk is being initialized. When the initialization is complete, the status indicator turns off. A complete rescan of all channels is done automatically.

Page 57

RAIDCore User Manual 55

Create Arrays

Arrays can be created after the disks are initialized. See RAID Levels on page 23, for deciding what type of RAID levels to use for the array.

NOTE: If the system is booted from a RAIDCore bootable array, the first array in the Arrays list must be the

bootable array. The system boots only from the first array in the list.

TIP: See also Create and Format Arrays on page 76, and Create New Arrays: bcadm --create on page 123.

Before you begin...

• In some circumstances, more than eight arrays are possible. They might appear to function properly, but are not supported by Dot Hill Systems Corp. For redundant arrays, the creation process is not finished until after the operating system and RAIDCore drivers have been installed and the system has been booted into the operating system context. However, the arrays are immediately available to use for either a boot or data array.

• Array numbers are valid only for a given boot, and might be different in the BIOS and drivers. If a permanent label is required, use the labeling feature.

• At any point in the this procedure, return to a prior window by pressing Esc.

• If the created array will be the RAIDCore bootable array, it must be the first array listed in the Arrays section of the BIOS Configuration Utility. As necessary, use the Swap Two Arrays feature to swap arrays and place the boot array in the first position.

Create An Array

1. From the Main Menu of the RAIDCore(tm) Array Configuration window, use the arrow keys to select

Create Array. Press Enter.

2. Select the disks on which to create the array by doing the following: c. Highlight the disk, by using the arrow keys. d. For each disk, press Insert to select the disk. The disks can be inserted in any order. e. After selecting the disks to be included in the array, press Enter.

3. In the User Input section, use the arrow keys to select an array type. Press En ter. (Only array types that can

be created with the selected disks are available).

4. If spares are applicable: a. In the User Input section, use the arrow keys to highlight a spare type. b. If applicable, in the Disks section, highlight the disk(s) to use as a spare. Press the Insert key to select

them.

5. Press Enter to add the spare disk(s).

6. Continue with the procedure Select An Array Size on page 56.

Page 58

56 Chapter 5 BIOS Configuration Utility

Select An Array Size

NOTE: Use the Page Up and Page Down keys to increase or decrease the array size in large increments.

Use the up arrow or down arrow keys to increase or decrease the array size in small increments.

To select an array size, perform one of the following, as shown in the table below.

Table 25 Selecting An Array Size

To Create This Array Size... Do This... Then This...

≤ 2.199 TB Use the Page Up or Page Down keys to select a

size

use the up arrow or down arrow keys to select a size.

Press Enter.

> 2.199 TB 1. Press the Page Up or the up arrow key to

increase the array size.

2. When an array size of 2.1 TB is reached, a message states that a size greater than the maximum is being attempted, and whether the size of the array should

be limited. Press Esc to create an array larger than

2 TB.

3. Press Page Up or the up arrow until either the

desired size or the maximum available size is reached.

4. Press Enter.

5. Select a caching level using the arrow keys. Press

Enter.

6. Press C to confirm the > 2 TB array size.

7. Continue with the procedure, Resume the Boot

Process on page 57.

NOTE: The array is marked Ready for use.

The text at the top of the RAIDCore(tm) Array Configuration window returns to a description of the menu items.

Page 59

RAIDCore User Manual 57

Resume the Boot Process

When the user is finished creating arrays, resume the boot process.

1. From the Main Menu, highlight Cont inue to Bo ot.

2. Press Enter. (A reboot is not required).

Figure 3 Four-Drive RAID 5 Array at the Main Menu (typical window)

In the example in the figure shown above, a four-drive RAID 5 array has been configured. If the user is installing the operating system to a bootable array, modify the boot priority list in the motherboard BIOS. See the motherboard’s user documentation for more information. Ensure that the RAIDCore bootable array is included in the boot priority list.

Also make sure that INT13 support is enabled on the RAID controller, as described in Change the Controller

Options on page 60.

NOTE: A RAIDCore bootable array must be the first array listed in the Arrays list. If necessary, use the

Swap Two Arrays feature to place the bootable array in the first position.

Page 60

58 Chapter 5 BIOS Configuration Utility

Delete Arrays

CAUTION: Deleting an array permanently destroys all data that was on the array. This action cannot be

undone.

Delete an Array

1. Highlight Delete Arrays from the Main Menu. Press Enter.

2. Do one of the following:

• Highlight each array to delete. Press Insert to select it.

•Type A to select all arrays for deletion.

3. Press Enter.

4. Press C to continue.

TIP: Also see Delete Arrays on page 85.

Swap Arrays

Use the Swap Two Arrays option to arrange arrays in a different order.

Before you begin...

• If more than one array is created, install the operating system to any of them. However, a small amount of boot information is always written to a disk(s) in the first array (Array 1) of the array list, regardless on which array the operating system is installed. If anything happens to a disk in Array 1, the system might not be able to boot. It is recommended that the user install the operating system on an array at a redundant RAID level—such as RAID 1 or RAID 5—and swap the array into the first position, if it is not already Array 1.

• The swap array feature is only available from the BIOS Configuration Utility.

Swap Arrays

1. Highlight Swap Two Arrays in the Main Menu. Press Enter.

2. Use the arrow keys to highlight an array. Press Insert to select the array.

3. Use the arrow keys to highlight another array. Press Insert to select the array.

4. Press Enter to swap the arrays.

Page 61

RAIDCore User Manual 59

Figure 4 Example of a RAID 5 Swapped for a RAID 10 (typical window)

In the example in the figure shown above, the RAID 10 array was the first array created. However, to boot from the RAID 5 bootable array (which contains the installed operating system and drivers), the arrays were swapped so that the RAID 5 bootable array is the first array listed.

View Disk Details

This option allows the user to view details about the disk. Nothing can be changed from this menu option; it is for informational purposes only.

1. From the Main Menu, select View Disk Details.

2. Use the arrow keys to choose a disk.

3. Information about the disk is displayed in the Information field across the top:

• Disk Number

• Controller Number

• Channel Number

• Disk Type (SATA/SAS/SSD)

•Disk Size

• New/Legacy/Empty/InArray

• Free space

• Disk Model Number

Page 62

60 Chapter 5 BIOS Configuration Utility

View Array D eta i ls

This option allows the details of the array to be viewed. Nothing can be changed from this menu option; it is for informational purposes only.

1. From the Main Menu, select View Disk Details.

2. Use the arrow keys to choose an array.

3. The full details of the array are displayed in both the Information field across the top:

• Array Number

•Type

•Size

• State

NOTE: The disks list shows the disks in the array, as selected (green).

Rescan All Channels

This option allows the user to rescan all channels to detect new or removed disks and arrays.

• To perform a rescan, select Rescan All Channels from the Main Menu. (The activity indicator in the

Information field spins while the disks are being polled).

• The Rescan All Channels option rescans all the channels, searching for new or removed disks, and rereads the configuration information from each disk.

NOTE: Sometimes when a disk is offline, it can be brought online through a rescan. Rescan also stops, and

then automatically resumes, all tasks.

Change the Controller Options

Selecting Controller Options allows the user to configure whether RAIDCore arrays might be bootable, as

well as other aspects of the boot process.

The default is to configure an array. An operating system can boot from RAIDCore. If an error occurs, an error message is displayed.

However, the user might be booting from the motherboard IDE or another SCSI device in the system. If this is the case, do not enable INT13 (without INT13, DOS cannot see the array).

NOTE: If Boot Mode is configured to enable INT13 and never display an error message, the user will not

know during the boot process if an array is degraded or if other problems have occurred.

One symptom of having too much memory used by the BIOS Configuration Utility is a blank window, with the message “Couldn't initialize memory” appearing in the top left hand corner. No additional information is given.

This menu also sets whether the boot process will pause when an error occurs. When the Pause feature is enabled and an array goes critical or offline, or there is a RAIDCore configuration error, the boot process stops.

Press Enter to continue booting.

View the error message on the window. If the Pause feature is disabled, the error message is displayed briefly, but the system continues to boot.

Page 63

RAIDCore User Manual 61

Select a Boot Option

1. From the Main Menu, select Controller Options.

NOTE: The controller options are displayed in the Controller Options section of the RAIDCore(tm) Array

Configuration window, as shown in the figure below.

Figure 5 Controller Options Section of the RAIDCore(tm) Array Configuration Window (typical)

2. Use the up or down arrow keys to select a boot option. See the choices in Table 2 6 on page 62.

NOTE: By default, all options are turned on. It is recommended that options remain enabled.

Page 64

62 Chapter 5 BIOS Configuration Utility

Change the Staggered Spinup Count

Depending on a system’s power supply load-rating, the end-user might want to limit the number of disks that are spun-up together when a system is powered on.

For example, if a system has six disks and the staggered spinup count is set to “2,” RAIDCore sends a command to spin-up disks 1 and 2 together, then disks 3 and 4, and finally disks 5 and 6.

1. At the RAIDCore BIOS Configuration Utility scroll down to Controller Options. Press Enter.

2. Scroll to Set Staggered Spinup Count. Press Enter. (The number within the brackets changes color).

3. Use the keyboard up arrow or down arrow to change the number within the brackets (minimum = 1;

maximum = 8). Press Enter to save the setting.

4. Press Esc to return to the Main Menu.

Continue Booting from the BIOS Configuration Utility

After arrays have been created, continue booting the system from the point where the RAIDCore BIOS Configuration Utility was entered.

To resume the boot process, select Continue to Boot in the Main Menu. Press Enter. (A system reboot is not

required).

Table 26 Choices for Selecting a Boot Array

To Accomplish This... Do This... Notes

Not boot the system from an array

1. Highlight Toggle INT13 Boot Support, using the

arrow keys.

2. Press Enter to change the setting to Disabled.

It is recommended that INT13 be disabled only if the system will be booted from another device. Leave the rest of the options enabled.

Turn off critical arrays while booting

1. Highlight Toggle Pause if Critical.

2. Press Enter to change the setting to Disabled.

Turn off warnings due to offline arrays when booting

1. Highlight Toggle Pause if Offline.

2. Press Enter to change the setting to Disabled.

Page 65

RAIDCore User Manual 63

6 Chapter 6 RAIDConsole Graphical User

Interface (GUI)

Start the RAIDConsole GUI

Start RAIDConsole under Windows

Access RAIDConsole by using one of three methods:

•Click Start, then click the RAIDConsole icon:

• Select Start -> Programs [All Programs] -> RAIDCore -> RAIDCore Management Suite ->

RAIDConsole

• Click the RAIDConsole icon on the system desktop (if applicable).

Start RAIDConsole under Linux

1. Open a command prompt and type /usr/bin/bc_winraid.

NOTE: For most Linux systems, step 1 starts RAIDConsole and also starts the bc_service application that

logs events in the system, as well as starts the bcapiservice application that enables remote management.

NOTE: If these applications do not autostart, start them manually. The user can stop the applications and keep them from autostarting next time by changing to the /etc/init.d/ directory from a console window. Type the following:- For bc_service: bcserviced start | stop- For bcapiservice: bcapid start |

stop.

2. If you want a pop-up message to appear on the desktop when an event is detected by bc_service and

reported to the log, run the bcpopup application. Open a command prompt and type /usr/bin/bcpopup.

3. Open the Security Level Configuration window by clicking Desktop at the menu bar.

4. Click System Settings.

5. Click Security Level.

6. At the Security Level Configuration window, select the SELinux tab.

7. Disable SELinux by un-clicking the first option. Or, change the policy from Enforcing to Permissive by

clicking the second option.

When RAIDConsole starts, the First Time Run window opens and inquires whether password protection is needed. See Password Protection below for information and instructions.

Password Protection

It is strongly recommended that the RAIDConsole management application be protected by a password. Misuse of the application by unauthorized and/or untrained personnel could result in destroyed data.

Page 66

64 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Password protection for the application can be enabled or disabled the first time it is started, using the First Time Run dialog box. If the user chooses not to protect the application with a password at this time, the user can do it later from the Options menu.

Figure 6 First Time Run Dialog Box (typical)

Page 67

RAIDCore User Manual 65

Things to Know About Passwords

• If the password is forgotten, the user will not be able to run the application. Create a password that will be remembered.

• The password must be at least six characters long.

• The password is case-sensitive.

• Four chances are given to enter the password correctly. If the password is typed incorrectly, the application will close after the fourth try. To try again, reopen the application.

• The application does not keep track of passwords that have been used previously.

• To change an existing password, see Change Password Settings on page 96.

Set Password Protection from the First Time Run Dialog Box

1. Type a password in the Password box.

2. Confirm the password by typing it again in the Confirm box.

3. Click Continue. The Array Status window opens.

Disable Password Protection from the First Time Run Dialog Box

1. Select Disable Passw ord Pro tection.

2. Click Continue. The Array Status window displays.

NOTE: If Disable Password Protection is selected, the next time RAIDConsole is started, a small dialog

box appears, without spaces for entering choices for Password and Confirm.

Enable Password Protection from the Options Menu

1. At the Options menu, select Password.

2. Check Enable Password Protectio n.

3. Enter a password.

4. Confirm the password by typing it again.

5. Click OK.

Disable Password Protection from the Options Menu

1. On the Options drop-down menu, select Password.

2. Check Disable Password Protection.

3. Type a password.

4. Click OK.

Change a Password from the Options Menu

1. On the Options drop-down menu, select Password.

2. Check Change Password.

3. Type the current password.

4. Type a new password.

5. Confirm the password by typing it again.

Page 68

66 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Help and About Windows

To view the software version and build number information for the GUI itself, access the Help drop-drop menu

and select About. The RAIDConsole Dot Hill window appears. See the figure below.

Figure 7 RAIDConsole Dot Hill Window (typical)

To view detailed software release and component version information at the RAIDConsole, perform the following.

1. Access RAIDConsole, using one of the three methods indicated at Start the RAIDConsole GUI on

page 63.

Page 69

RAIDCore User Manual 67

2. At the Array Status window, select the controller group icon and right-click. Select Properties.

See the following figure.

Figure 8 Array Status Window: Accessing Array Properties

3. The RAIDConsole Properties window appears, with information about component versions, license level,

and firmware. See the figure below.

Figure 9 RAIDConsole Properties Window (typical)

Page 70

68 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Version information for the following is displayed:

• The RAIDCore driver (bcraid.sys)

• The configuration driver (bccfg.sys)

• The array maintenance service (bc_service.exe)

• The remote management service (bcapiservice)

• The pop-up message utility (bcpopup)

• The dynamic link library (bc_vbdll.dll). To copy the version or license information, click Copy to Clipboard. Paste the information into a text editor,

such as Notepad. This method captures the serial numbers of the disk drives in the system, which are listed by the disk controller channel.

Reviewing the GUI

The Array Status Window

Figure 10 Sections of the Array Status Window (typical)

NOTE: Certain languages do not display correctly in the Array View section. (English, other languages that

use the Roman alphabet, and numerous other languages do display properly).

NOTE: To refresh the array and disk information displayed in the Array Status window, click View and then click Refresh. This command rereads configuration information from the driver, but does not poll the disks.

1 Array View section 2 Disk List section 3 Array List section 4 Event View section 5 I/O Status bar

Page 71

RAIDCore User Manual 69

The Array View Section of the Array Status Window

Elements of the Array View Section

The Array View section on the left side of the Array Status window presents a graphical view of array properties during and after the creation of the array. See the following table for the Array View elements.

Array View Icons

The icons in the Array View section indicate the RAID level of the array(s) (RAID 0, RAID 1, etc.), and the disks in the array(s).

An example of the Array View icons is shown in the following figure.

Figure 11 Icons of the Array View Section of the Ar ray Status Window (typical)

Table 27 Elements at the Array View Section of the Array Status Window

Element Description

Controller Group The RAIDCore controller for the arrays displayed below it.

Array The array number assigned to created or creating arrays.

Array name The name assigned to an array.

Task Percent Complete and ETA

The progress of a current array task, such as a Create or a Transform, is shown as percent complete and with the estimated time left to completion (hours:minutes:seconds).

Task type The nature of a current task, such as a Create or Transform.

Source array The original array to be transformed.

Destination array The array to which the source array is being transformed.

Page 72

70 Chapter 6 RAIDConsole Graphical User Interface (GUI)

The Disk List Section of the Array Status Window

Elements of the Disk List Section

The Disk List section on the Array Status window provides information about all disks assigned or available to arrays, as indicated in the following table.

NOTE: Ctrl Chan is a default element and is always displayed at the Disk List. All other elements can be

displayed or hidden by using Options -> View -> Edit Columns.

NOTE: If a disk is missing from the Disk List, the most likely causes are:

• A loose cable. Make sure that all disk cables are connected, then perform a rescan.

• A disk that is not fully seated in its bay. Make sure that the disk is inserted completely in its bay, then perform a rescan.

For more information, see Rescan Disks on page 73.

Table 28 Disk List Section of the Array Status Window

Element Description

Ctrl Chan Disk controller and channel number.

State State of the disk (Online, Offline, SMART Error).

WB Cache Enabled or Disabled.

Read Ahead Enabled or Disabled.

Type Disk type (Disk, Legacy, New, ATAPI).

Port Type The negotiated speed, not the speed of the port type.

In Use Indicates that the disk is In-Use or Free.

Capacity Disk capacity:

1 MB = 1,000,000 bytes

1 GB = 1,000,000,000 bytes

NOTE: Because the ATA storage industry has standardized the meanings

of MB as 1,000,000 bytes and GB as 1,000,000,000 bytes, RAIDCore reports the same units.

Free Space Total amount of space unused on the disk.

Largest Free Largest contiguous unused space on the disk.

GS Indicates if the disk is assigned as a global spare.

Model Number Disk manufacturer’s model number.

Serial Number Disk manufacturer’s serial number.

Firmware Revision Disk manufacturer’s firmware version.

Page 73

RAIDCore User Manual 71

The Array List Section of the Array Status Window

Elements of the Array List Section

The Array List section of the Array Status window provides the information about the arrays, as indicated in the following table.

Table 29 Array List Section of the Array Status Window

Element Description

Device The array number.

O.S. Name Drive number assigned by the operating system to the array.

•“Drive n” appears for an array that is Online and not hidden from the operating

system.

• “Hidden” appears if the array is hidden from the operating system.

• “None” appears if the array is Offline.

Partition Drive letter that was assigned to this array during the partition process. (A blank

space appears if the array has not been partitioned).

NOTE: If a dynamic volume is created on an array, RAIDConsole cannot

retrieve the volume’s drive letter.

Array Name User-created name for the array.

Type RAID level (RAID type) or Legacy.

Total Capacity Total capacity: 1MB = 1,000,000 bytes, 1GB = 1,000,000,000 bytes.

State State of the array (Normal, Critical, Offline).

Task Task type, if in progress (Transform, Copy, Check, Check_Bitmap, Not_Active,

Create, Restore).

Task State The state of the task (Started, Paused, Completed); the progress of the task is

given in the Array View section.

Pri Task priority if a task is in progress.

Scan Background Array Scan enabled? (Yes/No).

Cache Current cache setting (NC = No Cache, R = Read Cache, WB = Write Back

Cache, RW = Read/Write Cache)

Dst Spare Indicates whether the distributed spare option is being used.

Ded Spare Indicates the number of dedicated spares assigned to the array.

Page 74

72 Chapter 6 RAIDConsole Graphical User Interface (GUI)

The Event View Section of the Array Status Window

Elements of the Event View Section

The Event View section of the Array Status window is an optional-view section. It can be displayed or hidden by selecting View -> Event View.

The information in the Event View is linked to the View Log, which displays user-initiated tasks or actions, and system-generated notifications and events. The View Log can be accesses by selecting View -> Log.

The Event View provides the information indicated in the following table.

The I/O Status Bar of the Array Status Window

Elements of the I/O Status Bar

The I/O Status bar in the Array Status window provides the information indicated in the following table.

NOTE: The I/O status indicators indicate approximate numbers, especially when a system is experiencing a

high volume of I/O traffic.

Table 30 Event View Elements, Array Status Window

Element Description

Date The date on which the event occurred.

Time The time at which the event occurred.

System The system on which the event occurred.

CG The controller group to which the event applies.

Event The RAIDCore Asynchronous Event Notification (AEN) number of the event.

Priority The notification priority of the event: Low, Informational, Warning, Critical, or Fatal.

Text A brief description of the event.

Table 31 I/O Status Bar Elements, Array Status Window

Element Description

Host xx.x MB/S Host traffic in megabytes per second.

Disk xx.x MB/S Disk traffic in megabytes per second.

Host xxx IO/S Host I/Os per second.

Disk xxxx IO/S Disk I/Os per second.

H Queue Number of Host I/O requests currently in progress.

D Queue Number of Disk I/O requests currently in progress.

Dirty Number of dirty cache buffers if Write caching has been enabled (“dirty cache”

indicates the number of buffers not actually written out to the disks). This is informational only and not an error condition.

Host: xxx.xx MB/GB/TB Total amount of data transferred to or from the host since the last system boot.

Disk: xxx.xx MB/GB/TB Total amount of data transferred to or from the disks since the last system boot.

Page 75

RAIDCore User Manual 73

Working with Disks

Initialize Disks

When a disk is initialized, RAIDCore configuration information (metadata) is written to the disks. If a disk is new and has not been used before, it must be initialized before it can be used in RAIDCore arrays. After a disk is initialized, it shows as Disk in the Disk List.

CAUTION: Do not initialize a disk that is part of an array.

Initializing a disk in a non-redundant array deletes the array and its data; the array no longer appears in Array View. (This is especially true for a non-redundant bootable array. Initializing a disk in a non-redundant bootable array causes the array to Fail and deletes the operating system and drivers). Initializing a disk in a redundant array causes the array to become Critical. Initializing two or more disks in a redundant array deletes the array and its data; the array no longer appears in Array View.

CAUTION: All new disks, and disks that contain existing data (including a disk that contains an operating

system), appear as legacy arrays in the Array View and Array List until they are initialized.

To initialize disks

1. From the Disk drop-down menu, select Initialize. The Initialize Disk window is displayed.

2. Select the disk(s) to be initialized, by clicking on the box next to the disk(s).

3. Click Initialize Selected.

TIP: See also Initialize Disks on page 54.

Rescan Disks

The Rescan Disks option:

• Rescans the SATA channels that search for new or removed disks.

• Rereads the configuration information from each disk.

Sometimes when a disk is offline, it can be brought online through a rescan. Rescan also stops and then automatically resumes all tasks.

To rescan disks, select Rescan at the Disk drop-down menu.

TIP: See also Rescan All Channels on page 60.

Change Cache Properties for Disks

The Read Ahead and Write Back Cache properties can be changed if the disks support this option. The default settings are:

• Read Ahead is enabled.

• Write Back Cache is enabled.

CAUTION: Leaving Write Back Cache enabled might increase the likelihood of data being corrupted if the

system experiences a power interruption or unexpected shutdown.

NOTE: The disk cache settings cannot be changed if tasks are active on the arrays. The option is enabled

when the tasks are finished.

Page 76

74 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Change disk caching properties

1. From the Disk drop-down menu, select Properties. The Properties window appears.

2. Select the disks.

3. Under Disk Properties, click Enable or Disable for the WB Cache and Read Ahead settings.

4. Click Exit.

Change Disk View Settings

At the View drop-down menu click either Disk List View or Physical View.

The Disk List View is a view of the disks in a list format (as described in The Disk List Section of the Array

Status Window on page 70). It is the default view. In this view, this user can:

• Right-click on a disk in the Ctrl Chan column to add or remove a dedicated or global spare.

• View information, such as disk capacity and the amount of free space (which do not display in the physical view).

The Physical View is a graphical representation of the disks and their status. A default picture is provided, but any JPEG (*.jpg) image can be inserted and edited to match the configuration of the disks in the system.

Operations Available at the Physical View

The following operations can be performed at the Physical View.

Create a Dedicated Spare

Right-click on a disk-identifying box to assign it as a dedicated spare or to assign it as a global spare.

View the Disk Status

View the disk status as conveyed by the font and background color of the disk-identifying boxes.

Edit the Physical View

Use Edit Physical View on the Options menu to:

• Add a *.jpg file (see the procedure below).

• Show or hide a disk in the view.

• Change the positions of the disk-identifying boxes, in order to match the configuration of the actual disks in the enclosure(s).

To add a different JPEG image, perform the following:

1. At the Physical View, click .jpg Image.

2. At the JPG IMage window, click the ... button.

3. Browse to the folder that contains the desired JPEG image.

4. Select the JPEG and click OK.

5. At the JPG Image window, click OK.

6. At the Physical View, click Commit. The physical view image is replaced.

Page 77

RAIDCore User Manual 75

Legacy Disks

A disk that was previously attached to a non-RAIDCore SATA controller can be used with a RAIDCore array.

RAIDCore recognizes disks with valid DOS partition tables as legacy disks. With the Copy command, data can be moved from a legacy disk onto a RAIDCore array. The legacy disk can be reused within a RAIDCore array.

There are a few restrictions and some different behaviors when transforming a legacy disk, as compared to a standard RAIDCore array:

Table 32 Restrictions and Conditions When Transforming a Legacy Disk

Action Result

Transform a legacy disk

Transforming cannot be undone. Copying a legacy disk moves the data to a new array. The array on the legacy disk is gone. The legacy disk is initialized automatically and displays in the RAIDConsole Disk List as Disk. (It is no longer displayed as legacy)

Copy a legacy disk When copying a legacy disk, the legacy disk cannot be used in the destination array and

cannot be hidden.

Legacy disk space If all the space on the legacy disk has been used, the disks in the destination array must

have more capacity than the legacy disk or the data cannot be moved.

(This occurs because configuration information written to RAIDCore arrays takes up some space on each disk).

Page 78

76 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Working with Arrays

Create and Format Arrays

RAIDCore allows the partitioning and creation of as many as eight arrays across installed disks. Portions of disks can be used to create arrays, at the same time that other arrays use different portions of the same disks.

Before you begin...

Review the issues and recommendations indicated in the following table.

Create an Array

Select an array and cache

1. From the Array drop-down menu, or by selecting an existing array and right-clicking, select Create.

2. In the Disk List select the disks to include in the array by checking the box next to the desired disks.

NOTE: Click the All button to select all disks, or click the Unused button to select those disks that have yet

to be used in an array.

3. Select an array type from the Type list.

4. Enter the capacity in the Capacity field.

NOTE: The maximum available capacity changes with the disks selected, the RAID level, and the sparing

option that is chosen.

TIP: For creating volumes larger than 2 TB, see Table 51 on page 112.

5. Select a cache option for the array. The default is Read + Write Back Cache.

TIP: Also see Create New Arrays: bcadm --create on page 123.

Table 33 Issues and Recommendations for Creating and Formatting Arrays

Issues Recommendations

Access to arrays The creation of arrays, even redundant arrays, allows users immediate access to the

arrays, unless the Zero Create option is used during the create.

Array numbers Array numbers are valid only for a given boot, and can be different in the BIOS and

drivers. If a permanent label is required, use the labeling feature described in Name

Arrays on page 78.

Array size The array size of the new array is limited to 2.199 TB on some versions of Windows

and Linux. Refer to the operating system documentation for details on maximum array sizes.

Number of arrays In some circumstances, more than eight arrays are possible. They might appear to

function properly, but are not supported by Dot Hill Systems Corp.

System reboot If the system reboots, the creation process continues where it left off.

Page 79

RAIDCore User Manual 77

Select options and configurations

1. Select whether to configure dedicated spares by clicking the appropriate option.

2. Select whether to enable background array scanning by clicking Backgrou nd Arra y Scan .

TIP: See Scan an Array in the Background on page 90 for details.

3. Choose whether to skip initialization by clicking Skip Initialization.

CAUTION: Creating a RAID 5 array with this Skip Initialization selected, and a cache option of No Cache,

can, in some situations, result in data corruption.

NOTE: Arrays can be created instantly by skipping the background consistency check usually performed

when initializing the array. For certain types of redundant arrays this is a viable option and has no data integrity drawbacks. A Consistency Check can be performed at a later time (see Schedule a Consistency Check on page 89). For RAID 5 sets, if the initialization is skipped, the arrays are not redundant until a Consistency Check is performed.

4. If the configuration information for an array is lost and the user wants to leave data that was on the disks

untouched when writing new configuration information, check Leave Existing Data Intact.

5. Choose whether to use the Zero Create option, which writes the created array with zeros. If the Zero Create

option is used, the array is not immediately available (that is, the array being created is hidden from the operating system during the Create process).

6. Name the array, if desired.

7. Click Create to create the array.

Partition an array for use with Windows Server 2003

Use the standard operating system format procedure to format an array. If the user is unfamiliar with this procedure, use the following procedure for Microsoft Windows

Server 2003:

1. From the desktop, right-click My Computer.

2. Select Manage .

3. Click Disk Management.

4. Follow the instructions provided by the Write Signature and Upgrade Disk Wizard to write a signature on

the drive. When the wizard is closed, the Computer Management window reappears.

The O.S. Name is the same name found in the Array Status window. This is the array that needs to be formatted before it can be used.

Format the array

1. Right click in the white section surrounding the new partition and select Create Volume.

2. Follow the instructions provided by the Create Volume Wizard to format the disk.

TIP: Future expansion is easiest if the array is formatted with NTFS.

Page 80

78 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Name Arrays

Naming an array can be a useful practice to perform backups. It allows an array in the BIOS Configuration Utility to be easily identified.

To name an array

1. In the Array View section of the Array Status window, click on the array to select it.

2. Right-click on the array and select Name. The Array Name dialog box appears.

3. Type the desired name in the Array Name dialog box. Click OK.

NOTE: The specified name appears in the Array List and in the BIOS Configuration Utility.

NOTE: The following characters are not allowed in the array name:

TIP: Names can be up to 30 characters long. However, the BIOS Configuration Utility displays only 17 of

those characters.

Transform Arrays (supported only by RAIDCore VST)

With the Transform task, an array can be transformed from one RAID level to almost any other RAID level. The array can be expanded dynamically, even under I/O load.

Before you begin...

Review the issues and recommendations indicated in the following table.

(

)

“

”

Table 34 Issues and Recommendations for Transforming Arrays

Issues Recommendations

Array size An array cannot be transformed to a smaller-sized array. New arrays must be

either the same capacity or larger.

Array size limits The array size of the transformed array is limited to 2.199 TB on some

versions of Windows and Linux. Refer to the operating system documentation for details on maximum array sizes.

Disk failure during a Transform

If a disk fails while the Transform task is in progress, no data is lost as long as the source and destination RAID levels are redundant. If a spare has been assigned to the destination array, a fail-over task will start as soon as the Transform completes, provided the spare is available after the Transform.

Multiple arrays If there are multiple arrays, it might not be possible to transform some of the

arrays to a larger size. If, in the future, an array needs to be expanded in size, it is best to configure the available space as a single array.

Page 81

RAIDCore User Manual 79

Transform an array

1. In the Array View section of the Array Status window, select the array to be transformed.

2. Right-click the array to access the Array menu. Select Transform.

NOTE: If the system window is not wide enough, only the Destination View is displayed.

3. Select the RAID level to be transformed.

4. Select all the disks that is desired for the array (including disks that might already be in the array) by

clicking on the box next to the drive in the Disk List section.

5. Do one of the following:

• To expand the array, enter the size of the new array.

• Accept the default size.

NOTE: If a Transform is not possible, the Commit option is not enabled. A common reason preventing a

Transform is insufficient available space.

6. Click Commit.

NOTE: If the system is not licensed for RAIDCore VST, a License Issue message appears when the user clicks Commit.

NOTE: Unless the transformation is instantaneous, the Array Status window updates to show the source and

destination arrays, along with the progress of the transformation.

Task control commands When using task control commands, a Transform task can only be

paused/resumed but not removed. To end a Transform task, pause and delete it.

NOTE: If a task is paused and then deleted, the array will be

deleted. Deleting a task is the same as deleting an array. Data loss will occur when the task is deleted. Please ensure that data is backed up prior to deleting a task involving a Transform or a Restore.

System reboot during a Transform

If the system reboots during a Transform, the Transform continues where it left off.

Table 34 Issues and Recommendations for Transforming Arrays (continued)

Page 82

80 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Copy Arrays (supported only by RAIDCore VST)

The Copy task on the Array drop-down menu is used to create a new array that contains an exact copy of the data on a source array. It combines the Create Array and Copy Array tasks into a single command.

The new array does not have to be the same RAID level as the source array. The copy is linked to the source array upon completion. As long as the two arrays remain linked, changes to the source are also made on the copy.

The two arrays can be automatically or “manually” un-linked. The Copy task is useful for creating a “snapshot” of a source array at a moment in time.

Before you begin...

Review the issues and recommendations indicated in the following table.

Copy an array

1. In the Array View section of the Array Status window, select the array to be copied.

2. From the Array menu, select Copy. See the following figure.

Figure 12 Array View, Array Status Window: Select an Array to be Copied

Table 35 Issues and Recommendations for Copying Arrays

Issues Recommendations

Array destination The destination array is hidden at the completion of the copy. After the arrays

are unlinked, the RAIDConsole Un-Hide command can be used to unhide it.

Array size An array cannot be copied to a smaller-sized array. New arrays must be either

the same capacity or larger.

Array size limits The array size of the copied array is limited to 2.199 TB on some versions of

Windows and Linux. Refer to the operating system documentation for details on maximum array sizes.

Drive failure during copying

If a drive fails while the Copy task is in progress, data is not lost.

System reboot during a Copy task

If the system reboots during a Copy task, the copying continues where it left off.

Page 83

RAIDCore User Manual 81

3. Select the RAID level of the copy.

NOTE: If a RAID level is selected for the destination array for which the system is not licensed, a

License Issue message displays.

4. Select all the disks that the user wants in the destination array (including disks that might already be in the

array) by clicking the check box next to the drives in the Ctrl Chan section of the Disk List section.

5. Do one of the following:

• To expand the array, type the size of the new array.

• Accept the default size

NOTE: If a Copy is not possible, the Commit option is not enabled. A common reason preventing a Copy

task is insufficient available disk space.

6. Select a cache option for the array. The default is Read + Write Back Cache.

7. Select whether to configure spares. See Sparing Options: Disks and Arrays on page 29 to determine what

kind of spare or spares to assign.

8. Select whether to enable background array scanning by clicking the Background Array Scan option. See

Scan an Array in the Background on page 90 for details.

9. If the user wants the source and the copy array to be unlinked when the Copy task has completed, click the

Unlink on copy finished option.

NOTE: If the Unlink on copy finished option is not selected, the two arrays will be unlinked when the

system is rebooted. This has the benefit of capturing any changes to the source array at the last moment before the system shuts down, after any cleanup operations have occurred. The copy array remains hidden after the unlink. To access the data on the copy array, the array must be unhidden.

NOTE: If the system is not rebooted, the two arrays remain linked until they are manually unlinked using the

Un-Link command. See Use the Un-Link and Un-Hide Commands on page 83 for information on how to use this feature.

10. Name the Copy array, if desired.

11. Unless the Copy is instantaneous, the Array Status window updates to show the source and destination

arrays, along with the progress of the Copy.

Progress of the copied array

The progress of the Copy task remains at 100% until the arrays are unlinked. The task might appear to be hung-up, but it is not. While the task reads 100%, the arrays are still linked. Copying might occur as the source array changes.

After the copying is complete, the destination array comes back linked to the source array and hidden. There are three options for unlinking the copied arrays. See Table 36 on page 82.

Page 84

82 Chapter 6 RAIDConsole Graphical User Interface (GUI)

CAUTION: If the arrays are unlinked, data that the user expects to be written to both arrays might not be

written.

If the user needs to interrupt or stop the Copy task, use the task control feature described in Interrupt or cancel

a task on page 87.

Table 36 Options for Unlinking Copied Arrays

If This Action Occurred...

Do This... Then This...

Unlink on copy finished was selected

Unhide the destination array by using the Un-Hide command. This allows the data to be accessed.

NOTE: The destination

array is automatically unlinked when the copy is complete.

Unlink on copy finished was not

selected

Reboot and the two arrays will be unlinked.

Unhide the destination array using the Un-Hide command, in order to access the data.

NOTE: When this

method is used, all active data is flushed to the copy before the unlink. This ensures that all the data is captured from the file system or from applications are that currently running.

Unlink on copy finished was not

selected and the system was not rebooted

Manually unlink the source and destination arrays by using the Un-Link command.

Unhide the destination array using the Un-Hide command, in order to access the data.

Page 85

RAIDCore User Manual 83

Use the Un-Link and Un-Hide Commands

To manually unlink the source and destination array, use the Un-Link command.

After the destination array has been unlinked, it must be unhidden by using the Un-Hide command. The Un-Hide command is not available until the destination array has been unlinked.

To manually unlink the source and the destination array, and unhide the destination array, perform the following:

1. Select the source or the destination array in the Array view and right-click.

2. From the pop-up menu, select the Un-Link command. (The source and destination are now unlinked). See

the figure below.

Figure 13 Array View: Un-Link Command

3. Select the destination array in the Array View and right-click it.

4. From the pop-up menu, select the Un-Hide command.

CAUTION: The destination array must be unhidden in all cases to access the data, regardless of which method

is used to unlink the two arrays.

Page 86

84 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Access Additional Space

When an array has been transformed to a larger size, use the operating system tools to access the additional space.

There are several possible methods for expanding the existing file system on an array that has been transformed to a large size.

Microsoft provides a command prompt utility called Diskpart.exe

that can expand any NTFS file system without requiring a reboot. The Diskpart.exe utility version to use depends on which version of Windows is being run.

The Diskpart.exe utility can be found on the CD that comes with some versions of Windows, or at the Microsoft website (http://www.microsoft.com

) for others. Use the correct version for the operating system.

For arrays formatted with FAT32, use a third-party application, such as PartitionMagic® from PowerQuest Corporation.

Prepare to Physically Remove an Array

To prepare an array for physical removal:

1. In the Array View section, click the array to be removed.

2. From the Array drop-down menu, select Prepare to Remove. The array and all associated disks

disappear from the Array Status window.

3. Remove the first disk from the system. Do not click Rescan when the message in the following figure

appears:

Figure 14 RAIDConsole - Event Service Window: Rescan Button

4. Click Cancel. Remove the remaining disks in the array.

5. When all disks in the array have been removed from the system, click Rescan.

Page 87

RAIDCore User Manual 85

Delete Arrays

CAUTION: When an array is deleted the data on the array is lost.

Before you begin...

Review the issues and recommendations indicated in the following table.

Delete an array

1. In the Array Status window, click on the array to be deleted.

2. From the Array drop-down menu or by right-clicking on the array, select Delete.

TIP: Also see Delete Arrays on page 58.

Recreate a deleted array

If an array is deleted, it might be possible to recreate the array. See Table 52 in Chapter 7, Troubleshooting.

Recover Arrays

The Recover Array option attempts to force a failed array back into a functioning state. This option is provided as a last resort to recover whatever data might be present after an array has failed and its data cannot be recreated by RAIDCore.

Recover an array

1. From the Options drop-down menu, select Advanced Options.

2. Select the failed array to recover.

3. From the Array drop-down menu, select Recover.

4. Read the message at the Warning window. To proceed, click Continue.

NOTE: The status of the array might remain as failed (Offline) after this option is used.

Table 37 Issues and Recommendations for Deleting Arrays

Issue Recommendation

Drive letters or partitions Remove drive letters or partitions from the array by using the Change Drive

Letter and Paths... or Delete Volume... functions at Manage -> Disk Management -> Computer Management.

Operating system impact on arrays

If the array is not being used by the operating system, the array can be deleted at any time, even while tasks are running on the array.

If the array is being used by the operating system, the array cannot be deleted. Therefore, a bootable array cannot be deleted in RAIDConsole. A bootable array can only be deleted in the BIOS Configuration Utility.

Page 88

86 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Change Cache Settings for Arrays

There are four array caching options from which to choose.

NOTE: Cache options cannot be changed while a task is active on that array. They can be changed at any

other time, including while I/O is running.

Change cache settings

1. In the Array View section of the Array Status window, click on the array whose caching options are to be

changed.

2. From the Array drop-down menu or by right-clicking on the array, select Modify Cache Settings.

3. Choose either No Cache, Read Cache, Write Back Cache, or Read + Write Back Cache.

4. The new cache setting displays in the Array List Cache information.

Table 38 Cache Array Options

Option Description

No Cache When the No Cache option is selected for an array, I/O requests are translated

and passed to the disks without keeping a cached copy of the data available for future requests.

Read Cache When selected, the Read Cache option caches reads, if appropriate, and

performs sequential Read Ahead, when necessary.

Write Back Cache When the Write Back Cache setting is selected, writes are cached. This setting

is intended for advanced users who understand the implications of Write Back caching.

Read + Write Back Cache (default setting)

Both Read and Write Back Cache options can be selected.

Page 89

RAIDCore User Manual 87

Change the Priority Level of a Task

The task priority feature allows the user to speed up or slow down tasks being performed on arrays.

To decrease the amount of time it takes for a task to complete, set the task priority higher (10 is the highest).

NOTE: A task priority can only be changed after a task is running on the array.

NOTE: Tasks include operations such as a Transform, Copy, or Consistency Check.

To change a task priority

1. Click the array.

2. From the Array drop-down menu, select Task -> Priority.

3. Change the task priority by clicking the slider and moving it one way or the other.

Interrupt or Cancel a Task

The Task Control commands allow the user to pause, resume, or cancel (remove) tasks being performed on arrays.

Full task control can be used on Create, Copy, Consistency Check, and Bitmap_Check tasks. On Restores with dedicated or global spares the task can be removed, but the array will return to the Critical state.

NOTE: Task control can only be used when a task is running on the array.

Interrupt or cancel a task

1. Select the array upon which a task is being performed and right-click. If the task is a Copy, select either the

source array or the destination array.

2. From the menu, select Task -> Pause to interrupt the task, or Task -> Remove to cancel the task. See the

following figure.

Figure 15 RAIDConsole Window: Task -> Pause and Task -> Remove Options

3. If Task -> Pause is selected, right-click on the highlighted paused array. Locate a Task -> Resume

option to use to continue the task.

CAUTION: When a Copy task is cancelled, data that is in the part of the task that did not finish copying will

be lost on the destination array.

Page 90

88 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Check for Consistency

For redundant-type arrays only, the Consistency Check task is available from the Array drop-down menu. When this task is selected it starts the process of verifying that the parity (RAID 5) or mirror drive consistency is correct. If inconsistent areas are found, they are corrected during this process.

Having consistent arrays is very important. If an array is inconsistent and a drive fails, data is lost. RAIDCore is designed to maintain consistent arrays, but it is good practice to frequently run consistency checks. See

Schedule a Consistency Check on page 89.

When a redundant array is created using the Create task, and the Skip Initialize option is not checked (the default setting), a Consistency Check is performed automatically. Although a Consistency Check that runs

during a Create task can be removed (by highlighting the array and selecting Task -> Remove), the array that

is created will not be redundant. Unless a Consistency Check runs from end-to-end, an array is not protected.

After a Consistency Check has been started, adjust the priority of the Consistency Check task relative to user I/O activity. Use the Task Priority option (see Change the Priority Level of a Task on page 87).

A Consistency Check task can be scheduled with the Schedule Consistency Check task (see Schedule a

Consistency Check on page 89).

Before you begin...

• A Consistency Check task can be started at any time on a redundant-type array, as long as another task is

not running on the array.

• If the array state is Critical, the Consistency Check fails.

• A Consistency Check task can be started while under I/O load.

• To estimate how long the Consistency Check will take, look at the percentage of the task that is completed

and the estimate of the remaining time (hours: minutes: seconds). These details are displayed next to the array in the Array View section of the Array Status window.

Manually start a Consistency Check

1. Click the array on which to run the Consistency Check task.

2. From the Array drop-down menu or by selecting an array and right-clicking, select Check Consistency.

3. Click Start.

Manually stop a Consistency Check

1. Click the array on which to stop the Check Consistency task.

2. From the Array drop-down menu or by selecting an array and right-clicking, select Check Consistency.

3. Click Stop.

Page 91

RAIDCore User Manual 89

Schedule a Consistency Check

A Consistency Check task can be scheduled for later in the day or week. A Consistency Check task can be scheduled to run each week or each month.

NOTE: Schedule only one Consistency Check event on an array. This means that if a monthly check has been

scheduled and a weekly check is desired, delete the monthly event and schedule the new event.

The following scheduling options are available for a Consistency Check.

Schedule a Consistency Check for later

1. Click the array on which to run the Consistency Check.

2. On the Array drop-down menu or by selecting an array and right-clicking, select Check Consistency.

3. Click Schedule.

4. At the Check Consistency dialog box, select the frequency, day, and time.

5. Click Confirm.

Delete a scheduled Consistency Check

1. Click the array on which to delete the Consistency Check.

2. From the Array drop-down menu or by selecting an array and right-clicking, select Check Consistency.

3. Click Schedule.

4. At the Consistency Check dialog box, click Cancel.

Table 39 Consistency Check Options

Option Description

One Time Only Schedule the Consistency Check for the current day (“Today”) or up to seven

days in the future.

Weekly Events can be scheduled weekly. After it is selected, a Consistency Check runs

on the specified array at the same time each week.

Monthly Events can be scheduled to run once per month to run on the specified array at

a specified time.

Page 92

90 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Scan an Array in the Background

A Background Array Scan task performs a continuous background read operation of an array, accessing at least one copy of every block of the array from beginning to end.

A Background Array Scan is manually started by the user and runs continuously until the user stops it.

Although a Background Array Scan can run while an array is engaged in other tasks, it is recommended that the Background Array Scan run while the array is idle (that is, when there is no input to, or output from, the array).

Enable or disable a Background Array Scan

1. Click the array on which to run the background scan.

2. From the Array drop-down menu or by right-clicking the array, select Scan Array.

3. Select Start.

4. If a Background Array Scan is already enabled, and the user wishes to disable it, select Array ->

Background Array Scan -> Stop, or right-click the array and select Background Array Scan -> Stop.

NOTE: The Scan Array task can also be enabled for an array when it is created or copied.

Split Mirrored Arrays (supported only by RAIDCore VST)

A mirrored array can be split into separate arrays using either of the following procedures:

• The default settings (see below, Split a mirror using default settings)

• The advanced settings, which allows the user to specify which disks to keep as part of the original array (see

Split a mirror using the advanced split option on page 91).

Split a mirror using default settings

Mirrors can be split into separate arrays. See the following table of the RAID levels and the results from splitting an array.

Table 40 Splitting a Mirror by RAID Level

RAID Level Results from Splitting the Array

RAID 1 A RAID 1 array, when split, turns into two Volumes.

RAID 10 A RAID 10 array, when split, turns into two RAID 0 arrays.

RAID 1n A RAID 1n, when split using default settings, produces a Volume.

• The remainder of a RAID 1n, where “n” is 3, becomes a simple RAID 1.

• The remainder of a RAID 1n, where “n” is greater than 3, becomes a RAID 1n.

RAID 10n A RAID 10n, when split using fault settings, produces a RAID 0.

The remainder of a RAID 10n can become a RAID 10 or RAID 10n, depending on the value of “n”.

When an array is split, a portion of the array is split off. The remainder is hidden from the operating system.

Page 93

RAIDCore User Manual 91

Before you start...

• If there are failed disks in the array, only the non-failed disks will be included in the resulting Volume, RAID 0, RAID 1, or RAID 10. This will result in fewer arrays than expected. For example, a critical RAID 1 becomes a single volume. A critical RAID 1n (where n = 3) becomes a Volume and a critical RAID 1. Splitting the critical RAID 1 again will result in an additional Volume.

• Splitting a mirrored array cannot be undone. To remirror, the array needs to be transformed back to a mirror. For information about transforming arrays, see Transform Arrays (supported only by RAIDCore VST) on page 78.

Use default settings to split a RAID 1 or RAID 10

1. Click the array to be split.

2. From the Array menu or by right-clicking the array, select Mirror.

3. Click Split.

4. Click Default.

NOTE: By default, the split-off array is hidden.

Split a mirror using the advanced split option

For mirrors of RAID level RAID 1n or RAID 10n, various split combinations are possible using the Advanced Split option.

With the Advanced Split option, select the disks to keep as part of the original array. Disks not selected are split to the second array. For example, a four-disk RAID 1n can be split into two RAID 1 arrays.

NOTE: Select an equal number of disks from each mirror or the split cannot be performed.

1. Click on the array to be split to select it.

2. From the Array menu or by right-clicking the array, select Mirror.

3. Click Split.

4. Click Advanced.

5. Click to select the disks to keep as part of the original array.

6. Click Commit to perform the split.

Page 94

92 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Add or Remove Distributed Spares (supported only by RAIDCore VST)

Add a distributed spare while creating an array

1. From the Array menu or by right-clicking the array, select Create.

2. Configure the array.

3. In the Distributed Spare field, click Enabled.

Add a distributed spare while transforming an array

1. From the Array menu or by right-clicking the array, select Transform.

2. Configure the new array.

3. In the Distributed Spare field, click Enabled.

Remove a distributed spare

1. From the Array menu or by right-clicking the array, select Transform.

2. Configure the new array.

3. In the Distributed Spare field, click Disabled.

TIP: For additional information see Sparing Options: Disks and Arrays on page 29.

Add or Remove Dedicated Spares

If a dedicated spare is added, make sure there is adequate space on the dedicated spare. Pre-allocation of disk space is not available.

Add a dedicated spare while creating an array

1. From the Array drop-down menu or by right-clicking the array, select Create.

2. Select the disks for the array.

NOTE: The first disk selected becomes the dedicated spare.

3. Select the array type, capacity, and cache options.

4. Check the Dedicated Spare box.

5. Click Create.

6. At the Array View field, expand the array. Notice that the array being created includes the dedicated spare.

Add a dedicated spare after an array has been created

1. In the Array View section of the Array Status window, select the array to which to assign a dedicated spare.

2. In the Disk List section, right-click on the disk that will be the dedicated spare.

3. At the Options dialog box, select Assig n as De dicated Spare.

4. Click OK.

Remove a dedicated spare assignment

1. In the Array View section of the Array Status window, click the array from which to remove a dedicated

spare.

2. In the Disk List section, right-click on the disk that will be removed as the dedicated spare.

3. At the Options dialog box, select Remove as Dedicated Spare.

4. Click OK.

TIP: For additional information see Sparing Options: Disks and Arrays on page 29.

Page 95

RAIDCore User Manual 93

Remove All Dedicated Spares

Removing all dedicated spares from the RAIDConsole application is useful when removing a failed, missing, or removed disk that cannot be selected from the disk list.

Remove all dedicated spares

1. In the Array View section of the Array Status window, select the array from which to remove all dedicated

spares.

2. From the Array menu, select Remove Spares.

3. Click OK.

TIP: For additional information see Sparing Options: Disks and Arrays on page 29.

Add or Remove Global Spares

If a global spare is being added, make sure there is adequate space on the global spare.

Add a global spare

1. In the Disk List section, right-click the disk that will be the global spare.

2. At the Options dialog box, select Assign as Global Spare.

3. Click OK.

Remove a global spare

1. In the Disk List section, right-click the disk that will be removed as the global spare.

2. At the Options dialog box, select Remove as Global Spare.

3. Click OK.

Page 96

94 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Working with Options

View or Change the License Level

License information can be viewed, or license keys/Activation IDs, can be changed, by using RAIDConsole or bcadm.

When a license level is changed, the driver performs a rescan of all disks to get the license information.

CAUTION: License keys/Activation IDs, and upgrade license keys/Activation IDs, are unique for each

system and cannot be used to upgrade alternate systems.

NOTE: The unauthorized creation of an upgrade license key/Activation ID for this product invalidates the

product warranty and might be considered theft.

NOTE: RAIDCore is shipped with a 30-day trial license. After the trial period expires, RAIDCore runs with

extremely degraded performance.

NOTE: Features that are not licensed (for example, when a license expires) will be disabled. Certain features

will not be available, and array types that are not licensed will go offline. This situation can be remedied by purchasing a license.

View license level using RAIDConsole

1. Access the License window, using one of the following methods:

• From the Options drop-down menu, select License.

• Right-click on the Controller Group. Choose Properties and click the License button. See Figure 16.

Figure 16 License Window, showing the license level and the space for entering an Activation ID

Page 97

RAIDCore User Manual 95

2. To activate the license key/Activation ID paste or enter the Activation ID (obtained from the Entitlement

Certificate) into the New License Key/Activation ID box. See Figure 16 on page 94 and an example of an Entitlement Certificate below.

Figure 17 An example of an Entitlement Certificate, which contains the Activation ID

3. Click Apply.

NOTE: The issued license key/Activation ID only works with the system for which the original license

key/Activation ID was issued. A license key/Activation ID and upgrade license key/Activation ID are unique for the system and cannot be used to upgrade other systems.

NOTE: To inquire about RAIDCore licensing and license keys, visit the Dot Hills Systems Web site at

http://www.dothill.com/products/data-protection-software/raidcore.htm

and

click the Contact Us segment of the window.

Page 98

96 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Change Password Settings

A password can be enabled, disabled, or changed at the Options drop-down menu. See Password Protection on page 63.

Change View Settings

On the Options drop-down menu, the View command allows the user to:

• Change the size of the icons used in the graphical user interface

• Select how the array tree expands within the Array View.

Set small icons

This setting switches between displaying large and small icons in the Array View section. Use small icons when

there are large numbers of drives or if the window resolution of the system is low.

NOTE: The View task is unavailable while editing the Physical View of the disks.

1. From the Options drop-down menu, select View.

2. Click Small Icons to check (enable) or clear (disable) the feature.

Use Expand On Click

When Expand On Click is enabled, clicking an array in the Array View section expands the selected array hierarchy and contracts all others.

Change how the array tree expands when an array is clicked in the Array View

1. From the Options drop-down menu, select View.

2. Check Expand On Click to check (enable) or clear (disable) the feature.

Page 99

RAIDCore User Manual 97

Edit exit columns in the Disk List

Individual columns in the Disk List can be displayed or hidden using the Edit Columns feature.

1. From the Options drop-down menu, select View.

2. Click Edit Columns. See the following figure.

Figure 18 Select Display Columns Window: Edit Columns

3. To show or hide a column, highlight its name and use the >> or << buttons to move it into or out of the

Show These Fields: list.

Page 100

98 Chapter 6 RAIDConsole Graphical User Interface (GUI)

Edit the Physical View of the Disks

Most SCSI RAID enclosures have lights on the box to indicate disk activity status. Most SATA and SATA II enclosures do not have this feature.

However, the RAIDConsole management application provides a feature to configure a physical view of the system that also graphically indicates disk status.

A default picture is provided with the application for use, as an example of what a physical view of a system might look like. The disk-identifying boxes show a controller number followed by a disk number.

Edit the physical view

1. On the Options drop-down menu, select Edit Physical View. (The disks in the system appear in the default

Physical View).

2. To add an image, click the .jpg image button. Type the location of the file that contains the JPEG. Click OK.

NOTE: Resize the JPEG image to fit the rectangular space of the Edit Physical View screen. The default

image is 551 x 187 pixels.

3. If needed, drag & drop disk boxes from the list at the top onto or from the image. For example, choose to

position a disk in place of an empty bay in the enclosure, or remove disk boxes that are not controlled by RAIDCore.

NOTE: Any disks from the top not used within the image are hidden when the Physical View is saved.

4. Click Commit to save the changes.

View Log Window

The View Log window displays all of the messages generated by RAIDCore. All messages are logged, not just the ones enabled in Notification.

All messages received from the RAIDCore driver are sent to a message log file. If desired, change the name of this file in the Notification window.

By default, notification events in Windows-based systems are saved to %Program Files%\RAIDCore\bc_service.log.

Notification events in Linux-based systems are saved to /var/log/bc_service.log. From the View menu, select Log to view the event log.

Dot Hill Systems RAIDCore User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual