Home » 3Ware Manuals » Network Cards » 3Ware 9550SXU-16ML » Manual Viewer

3Ware 9550SXU-16ML User Guide - Page 191

Rebuilding Units, the failed drives are only half of each mirrored pair.

UPC - 693494971606

Add to My Manuals
Save this manual to your list of manuals

Page 191 highlights

Rebuilding Units Rebuilding Units If a hot spare is specified and a redundant unit degrades, an event notification is generated and the hot spare dynamically replaces the failed drive in the redundant unit without user intervention. The rebuild process will automatically be launched as a background process at the next scheduled time. If scheduling is turned off, the rebuild process will start almost immediately (within a few minutes). If 3DM is running and E-mail notification is enabled, an event notification will be sent to specified users when the rebuild process starts and when it completes. For 9550SX controllers, if Auto-Rebuild is enabled, the firmware will attempt to rebuild a degraded unit with an available drive or a failed drive. If desired, you can manually replace the drive, rescan the controller, and start the rebuild process. Manual rebuilds can be started from either 3BM or 3DM, although the rebuild itself only happens when the operating system is running. If multiple drives are faulted in a RAID 10 configuration, the drives are rebuilt simultaneously. In a 4-drive RAID 10 configuration, up to two drives can be rebuilt. In a 6-drive configuration, up to three drives can be rebuilt. In an 8-drive configuration, up to four drives can be rebuilt. In a 12-drive configuration, up to six drives can be rebuilt. Note: If both drives in a RAID 10 mirror set are faulted, the data is not recoverable. Up to half of the drives in a RAID 10 unit can become defective and still have the user data retained, as long as the failed drives are only half of each mirrored pair. A RAID 50 unit can also sustain multiple drive failures, as long there is only one failed drive in each RAID 5 set. When a RAID 5 is running in Degraded mode, the missing data is reconstructed from all non-degraded drives. Note: If a rebuild fails, check the Alarms page for the reason. If there was an ECC error on the source disk, you can force the rebuild to continue by checking the Overwrite ECC Error policy on the Controller Settings page in 3DM and then running Rebuild again. This will cause uncorrectable blocks to be rewritten, but the data may be incorrect. It is recommended that you execute a file system check when the rebuild completes. www.3ware.com 181

Section	Page
Title Page	1
Table of Contents	3
How this Guide is Organized	7
Conventions	9
Introducing the 3ware® 9000 Series Controller	11
Product Features	11
What’s New with the 3ware 9550SX Controllers	12
System Requirements	12
Understanding RAID Concepts and Levels	14
Available RAID Configurations	15
RAID 0	15
RAID 1	16
RAID 5	16
RAID 10	17
RAID 50	17
Single Disk	18
JBOD	18
Hot Spare	18
Determining What RAID Level to Use	18
Support for Over 2 Terabytes	20
3ware Tools for Configuration and Management	20
3BM (3ware BIOS Manager)	21
3DM 2 (3ware Disk Manager)	21
3ware CLI (Command Line Interface)	21
Monitoring, Maintenance, and Troubleshooting Features	22
Getting Started with Your 3ware RAID Controller	25
Physically Install the Controller and Drives	25
Configure the RAID Unit and Drives	25
Install the Driver and Make the Operating System Aware of the New Drives	26
Set Up Management and Maintenance Features	26
First-Time RAID Configuration Using 3BM	29
Basic Steps for Creating a Unit	29
Specifying a Hot Spare	35
Leaving Individual Drives as JBODs	36
Checking the Motherboard Boot Sequence	36
What Next?	37
Driver Installation	39
Driver Installation Under Windows	40
Materials Required	40
Creating a 3ware Driver Diskette	41
Installing the 3ware Driver and Windows on a New Unit	41
Installing the Driver on a System that Boots from a Different Device	42
Making Units Managed by a 3ware Controller Available to Windows	47
Driver Installation Under Linux	48
Obtaining 3ware Linux Drivers	49
Be Sure to Use the Correct Drivers	49
Determining the Current Version of your 3ware Driver	50
Driver Installation Under Red Hat Linux or Fedora Core 4	50
Materials required	50
Creating a Red Hat Linux Driver Diskette	50
Installing the 3ware Driver and Red Hat Linux on a New Unit	51
Installing the 3ware Driver on a Red Hat Linux System that Boots From a Different Device	52
Driver Installation Under SuSE Linux	55
Materials required	55
Creating a SuSE Linux Driver Diskette	55
Installing the 3ware Driver and SuSE Linux with YaST2 on a New Unit	55
Installing the 3ware Driver on a SuSE Linux System that Boots from a Different Device	56
Compiling a 3ware Driver for Linux	57
Driver Installation Under FreeBSD	58
Obtaining 3ware FreeBSD Drivers	58
Materials Required	58
Installing the Driver under FreeBSD	59
Installing the Driver while Installing FreeBSD on the 3ware RAID Controller	59
Installing the 3ware Driver on a FreeBSD System that Boots from a Different Device	62
3ware BIOS Manager 2 (3BM 2)	65
Starting 3BM 2	65
Exiting the 3BM Configuration Utility	67
Working in the 3BM Screens	68
Adjusting BIOS Loading Settings	71
Power-On Self Test (POST) Display Options	71
BIOS Loading Options	71
Displaying Controller Information	73
Getting Help While Using 3BM	73
3ware Disk Manager (3DM 2)	75
Browser Requirements for 3DM	76
Setting up Mozilla	76
Installing 3DM	77
Installing 3DM on a Microsoft Windows system	77
Uninstalling 3DM under Microsoft Windows	80
Installing 3DM for Linux or FreeBSD	80
Uninstalling 3DM under Linux or FreeBSD	82
Starting 3DM and Logging In	83
Starting 3DM under Linux	83
Starting 3DM under Microsoft Windows	83
Viewing 3DM Remotely via a Standard Web Browser	84
Logging In	84
Working with the 3DM Screens	85
3DM Menus	86
Viewing Information About Different Controllers in 3DM	87
Refreshing the Screen	87
3DM Screens and What They're Used For	87
Setting Up 3DM Preferences	89
Setting and Changing 3DM Passwords	89
Managing E-mail Event Notification	90
Enabling and Disabling Remote Access	91
Setting the Incoming Port #	92
Setting the Frequency of Page Refreshes	92
3DM 2 Reference	93
Controller Summary Page	93
Controller Details Page	95
Unit Information Page	96
Unit Details Page	97
Drive Information Page	99
Drive Details Window	100
Extra Drive Information	101
SMART Data	101
Controller Settings Page	102
Background Task Rate	102
Unit Policies	103
Unit Names	104
Other Controller Settings	105
Scheduling Page	106
About Task Schedules	107
About Self-tests	107
Maintenance Page	108
Rescan Controller	109
Unit Maintenance	110
Available Drives (to Create Units)	114
Alarms Page	117
Battery Backup Page	118
3DM 2 Settings Page	121
E-mail Notification	121
Password	122
Page Refresh	122
Remote Access	122
HTTP Settings	123
Configuring Your Controller	125
Viewing Information About Individual Controllers	125
Viewing and Setting Controller Policies	127
Viewing Controller Policies	128
Exporting JBOD Disks	129
Enabling and Setting Up Staggered Spinup	130
Disabling Write Cache on Unit Degrade	131
Multi LUN Support and Auto-Carving	131
Setting the Auto-Rebuild Policy	133
Configuring Units	135
Creating a New Unit	135
Drives to be included in the unit	136
Type of configuration	136
Name of the unit (optional)	136
Stripe size, if appropriate for the RAID level	137
Unit policies	137
Creating a Unit through 3DM	137
Creating a Unit through 3BM	140
Ordering Units in 3BM	143
Partitioning and Formatting Units	143
Creating a Hot Spare	145
Specifying a Hot Spare through 3DM	145
Specifying a Hot Spare through 3BM	146
Enabling and Disabling the Unit Write Cache	147
Enabling and Disabling the Unit Write Cache through 3DM	148
Enabling or Disabling the Write Cache through 3BM	148
Setting the StorSave Profile for a Unit	149
Setting the StorSave Profile through 3DM	151
Setting the StorSave Profile through 3BM	151
Enabling or Disabling Queuing for a Unit	151
Setting Other Unit Policies through 3DM	153
Changing An Existing Configuration	154
RAID Level Migration (RLM) Overview	154
Changing RAID Level	155
Expanding Unit Capacity	156
Informing the Operating System of Changed Configuration	157
Naming a Unit	159
Naming a Unit Through 3DM	159
Naming a Unit Through 3BM	159
Deleting a Unit	160
Deleting a Unit through 3DM	160
Deleting a Unit through 3BM	162
Removing a Unit	164
Removing a Unit Through 3DM	164
Removing a Unit Through 3BM	165
Moving a Unit from One Controller to Another	166
Unlocking Drives Configured on a 9500S Controller	167
Moving Units from an 8000 Controller to a 9000 Controller	167
Moving Legacy JBOD Units to a 9000 Controller	168
Moving Units from a 9500S to a 9550SX Controller	169
Adding a Drive through 3DM	170
Removing a Drive	171
Rescanning the Controller	173
Maintaining Units	175
Checking Unit and Drive Status through 3DM	175
Reviewing Alarms and Errors	177
Viewing Alarms	177
Downloading an Error Log	178
Viewing SMART Data About a Drive	178
About Background Tasks	179
About Initialization	179
Foreground Versus Background Initialization	179
Initialization of Different RAID Types	180
Initialization of RAID 0 Units	180
Initialization of RAID 5 and RAID 50 Units	180
Initialization of RAID 1 and RAID 10 Units	180
Auto Initialization After Power Failure	181
About Rebuilds	182
About Verification	182
About Verifies of Non-Redundant Units	183
About Verifies of Redundant Units	183
How Errors Are Handled	183
About Migration	184
Moving a Unit to Another Controller During Migration	184
About Self-tests	185
Setting Background Task Rate	185
Scheduling Background Tasks	186
Prioritization of Background Tasks	186
Scheduled Task Duration	187
Viewing Current Task Schedules	187
Turning On or Off Use of a Task Schedule	188
Removing a Task Schedule	189
Adding a New Task Schedule Slot	189
Selecting Self-tests to be Performed	190
Rebuilding Units	191
Rebuilding a Unit Through 3DM	192
Rebuilding Units through 3BM	193
Cancelling a Rebuild and Restarting It with a Different Drive	195
Verifying Units	196
Verifying a Unit through 3DM	197
Verifying a Unit through 3BM	197
Locating a Drive by Blinking Its LED	198
Maintaining Your Controller	199
Determining the Current Version of Your 3ware Driver	199
Updating the Driver and Firmware	200
Updating the 3ware Driver and Firmware Under Windows	201
Using the Update Utility With Multiple Controllers	205
Updating the 3ware Driver Under Windows XP	206
Updating the 3ware Driver Under Red Hat	213
Updating the 3ware Driver Under SuSE	214
Updating the 3ware Driver Under FreeBSD	215
Updating the Firmware Under Linux and FreeBSD	216
Viewing Battery Information	217
Testing Battery Capacity	218
Troubleshooting	221
Before Contacting Customer Support	221
Problems and Solutions	222
Software Installation	222
Problems in 3DM	223
AEN Messages	224
AEN Error Message Summary	224
AEN Error Message Details	227
001h Controller reset occurred	227
002h Degraded unit	227
003h Controller error occurred	227
004h Rebuild failed	227
005h Rebuild completed	228
006h Incomplete unit detected	228
007h Initialize completed	228
008h Unclean shutdown detected	228
009h Drive timeout detected	228
00Ah Drive error detected	229
00Bh Rebuild started	229
00Ch Initialize started	229
00Dh Unit deleted	229
00Eh Initialize failed	229
00Fh SMART threshold exceeded	229
019h Drive removed	230
01Ah Drive inserted	230
01Eh Unit inoperable	230
01Fh Unit Operational	230
020h Prepare for shutdown (power-off)	230
021h Downgrade UDMA mode	230
022h Upgrade UDMA mode	231
023h Sector repair completed	231
024h Sbuf memory test failed	231
025h Cache flush failed; some data lost	231
026h Drive ECC error reported	232
027h DCB checksum error detected	232
028h DCB version unsupported	232
029h Verify started	232
02Ah Verify failed	233
02Bh Verify completed	233
02Ch Source drive ECC error overwritten	233
02Dh Source drive error occurred	233
02Eh Replacement drive capacity too small	233
02Fh Verify not started; unit never initialized	233
030h Drive not supported	234
032h Spare capacity too small for some units	234
033h Migration started	234
034h Migration failed	234
035h Migration completed	234
036h Verify fixed data/parity mismatch	234
037h SO-DIMM not compatible	234
038h SO-DIMM not detected	234
039h Buffer ECC error corrected	235
03Ah Drive power on reset detected	235
03Bh Rebuild paused	235
03Ch Initialize paused	235
03Dh Verify paused	235
03Eh Migration paused	235
03Fh Flash file system error detected	235
040h Flash file system repaired	235
041h Unit number assignments lost	236
042h Primary DCB read error occurred	236
043h Backup DCB read error detected	236
044h Battery voltage is normal	236
045h Battery voltage is low	236
046h Battery voltage is high	236
047h Battery voltage is too low	237
048h Battery voltage is too high	237
049h Battery temperature is normal	237
04Ah Battery temperature is low	237
04Bh Battery temperature is high	237
04Ch Battery temperature is too low	237
04Dh Battery temperature is too high	238
04Eh Battery capacity test started	238
04Fh Cache synchronization skipped	238
050h Battery capacity test completed	238
051h Battery health check started	238
052h Battery health check completed	238
053h Battery capacity test is overdue	239
055h Battery charging started	239
056h Battery charging completed	239
057h Battery charging fault	239
058h Battery capacity is below warning level	239
059h Battery capacity is below error level	239
05Ah Battery is present	239
05Bh Battery is not present	239
05Ch Battery is weak	239
05Dh Battery health check failed	240
05Eh Cache synchronization completed	240
05Fh Cache synchronization failed; some data lost	240
Glossary	241
Compliance and Conformity Statements	247
Federal Communications Commission Radio Frequency Interference Statement	247
Microsoft Windows Hardware Quality Lab (WHQL)	248
European Community Conformity Statement	248
Warranty, Technical Support, and Service	249
Limited Warranty	249
Exclusions	250
State Law Provisions	250
Warranty Service and RMA Process	250
AMCC Technical Support and Services	251
Sales and ordering information	251
Feedback on this manual	251

Match case Limit results 1 per page

Rebuilding Units

www.3ware.com

181

Rebuilding Units

If a hot spare is specified and a redundant unit degrades, an event notification

is generated and the hot spare dynamically replaces the failed drive in the

redundant unit without user intervention. The rebuild process will

automatically be launched as a background process at the next scheduled

time. If scheduling is turned off, the rebuild process will start almost

immediately (within a few minutes). If 3DM is running and E-mail

notification is enabled, an event notification will be sent to specified users

when the rebuild process starts and when it completes.

For 9550SX controllers, if Auto-Rebuild is enabled, the firmware will attempt

to rebuild a degraded unit with an available drive or a failed drive.

If desired, you can manually replace the drive, rescan the controller, and start

the rebuild process.

Manual rebuilds can be started from either 3BM or 3DM, although the rebuild

itself only happens when the operating system is running.

If multiple drives are faulted in a RAID 10 configuration, the drives are

rebuilt simultaneously. In a 4-drive RAID 10 configuration, up to two drives

can be rebuilt. In a 6-drive configuration, up to three drives can be rebuilt. In

an 8-drive configuration, up to four drives can be rebuilt. In a 12-drive

configuration, up to six drives can be rebuilt.

Note

: If both drives in a RAID 10 mirror set are faulted, the data is

not recoverable. Up to half of the drives in a RAID 10 unit can

become defective and still have the user data retained, as long as

the failed drives are only half of each mirrored pair.

A RAID 50 unit can also sustain multiple drive failures, as long there is only

one failed drive in each RAID 5 set.

When a RAID 5 is running in Degraded mode, the missing data is

reconstructed from all non-degraded drives.

Note:

If a rebuild fails, check the Alarms page for the reason. If

there was an ECC error on the source disk, you can force the

rebuild to continue by checking the Overwrite ECC Error policy on

the Controller Settings page in 3DM and then running Rebuild

again. This will cause uncorrectable blocks to be rewritten, but the

data may be incorrect. It is recommended that you execute a file

system check when the rebuild completes.