Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
1,359 Views

Rapid Storage Technology RAID 5 Initialization stopped at 69%

Using version 12.5.0.1066 of RST running Windows Server 2012 Standard on a ASUS P6X58-E WS motherboard, which has an Intel ICH10R controller which supports Intel Matrix Storage Technology. I installed 6 identical new Seagate 2 tb drives (ST2000DM001). 5 disks are assigned to a RAID 5 array (using all of the storage), and the 6th drive is a hot spare. The RAID 5 volume is shown to be 7452 gb.

The RAID 5 initialization was moving along a an acceptable pace, but stalled at 69% (2 days ago). I've found no messages indicating any problems. Does anyone have any insights. Where should I look for error messages?

- Michael Faklis mailto:Michael_Faklis@EvolSwSys.net Michael_Faklis@EvolSwSys.net 415-772-1921.

0 Kudos
5 Replies
Highlighted
Valued Contributor III
9 Views

Could you please post the report generated by Intel(R) Rapid Storage Technology?

For information on how to get this report you can refer to this article:

http://www.intel.com/support/chipsets/imsm/sb/CS-023487.htm Intel(R) Rapid Storage Technology (Intel(R) RST) | System reports

0 Kudos
Highlighted
Beginner
9 Views

Forgive me for the delay, but I had to repeat the procedure (as I understand it) to make sure I had a repeatable problem description. The requested report is below:

I have 6 identical new disks (Seagate 2 tb ST2000DM001), initialized with CMD > DISKPART > CLEAN. I defined a RAID5 array using the 1st 5 disks, while intending to use the 6th disk as a hot spare after the initialization completes. After defining the RAID5 array, the RST screen tells me to define a partition and format it. I rebooted and then using the Windows Disk Management control panel, I defined a single simple volume using all available space (7451 gb), and formatted it as ReFS.

The RST status panel showed progress for 2 days and then stalled at 69%. The Computer Management panel showed progress during that period and stalled at 16% formatted.

I questioned (to myself) why I was being asked to partition and format the array so quickly, by RST showed the array was initialized almost immediately by the time I was asked to define and format my partitions.

System Report

System Information

OS name: Microsoft Windows Server 2012 Standard

OS version: 6.2.9200 9200

System name: ESSWS2012HV

System manufacturer: System manufacturer

System model: System Product Name

Processor: GenuineIntel Intel64 Family 6 Model 26 Stepping 5 2.673 GHz

BIOS: American Megatrends Inc., 0301

Intel® Rapid Storage Technology enterprise Information

User interface version: 12.5.0.1066

Language: English (United States)

RAID option ROM version: 8.0.0.1038

Driver version: 12.5.0.1066

ISDI version: 12.5.0.1066

Storage System Information

RAID Configuration

Array Name: SATA_Array_0000

Size: 9,538,644 MB

Available space: 19 MB

Number of volumes: 1

Volume member: ESSWSHVR5

Number of array disks: 5

Array disk: Z1E36GQD

Array disk: S240LT98

Array disk: Z1E36HXP

Array disk: Z2F02X4S

Array disk: W1E0D8ES

Disk data cache: Enabled

Volume name: ESSWSHVR5

Status: Initializing 69% complete

Type: RAID 5

Size: 7,630,899 MB

System volume: No

Data stripe size: 128 KB

Write-back cache: Off

Initialized: Yes

Parity errors: 0

Blocks with media errors: 0

Physical sector size: 4096 Bytes

Logical sector size: 512 Bytes

Hardware Information

Controller name: Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller

Type: SATA

Mode: RAID

Number of SATA ports: 6

Number of volumes: 1

Volume: ESSWSHVR5

Number of spares: 0

Number of available disks: 1

Rebuild on Hot Plug: Disabled

Manufacturer: 32902

Model number: 10274

Product revision: 0

Direct attached disk: Z1E36GQD

Direct attached disk: S240LT98

Direct attached disk: Z1E36HXP

Direct attached disk: Z2F02X4S

Direct attached disk: W1E0D8ES

Direct attached disk: S2F07SF5

Disk on Controller 0, Port 0

Status: Normal

Type: SATA disk

Location type: Internal

Usage: Array disk

Size: 1,863 GB

System disk: No

Disk data cache: Enabled

Command queuing: NCQ

SATA transfer rate: 3 Gb/s

Model: ST2000DM001-1CH164

Serial number: Z1E36GQD

SCSI device ID: 0

Firmware: CC26

Physical sector size: 4096 Bytes

Logical sector size: 512 Bytes

Disk on Controller 0, Port 1

Status: Normal

Type: SATA disk

Location type: Internal

Usage: Array disk

Size: 1,863 GB

System disk: No

Disk data cache: Enabled

Command queuing: NCQ

SATA transfer rate: 3 Gb/s

Model: ST2000DM001-9YN164

Serial number: S240LT98

SCSI device ID: 1

Firmware: CC4H

Physical sector size: 4096 Bytes

Logical sector size: 512 Bytes

Disk on Controller 0, Port 2

Status: Normal

Type: SATA disk

Location type: Internal

Usage: Array disk

Size: 1,863 GB

System disk: No

Disk data cache: Enabled

Command queuing: NCQ

SATA transfer rate: 3 Gb/s

Model: ST2000DM001-1CH164

Serial number: Z1E36HXP

SCSI device ID: 2

Firmware: CC26

Physical sector size: 4096 Bytes

Logical sector size: 512 Bytes

Disk on Controller 0, Port 3

Status: Normal

Type: SATA disk

Location type: Internal

Usage: Array disk

Size: 1,863 GB

System disk: No

Disk data cache: Enabled

Command queuing: NCQ

SATA transfer rate: 3 Gb/s

Model: ST2000DM001-9YN164

Serial number: Z2F02X4S

SCSI device ID: 3

Firmware: CC9C

Physical sector size: 4096 Bytes

Logical sector size: 512 Bytes

Disk on Controller 0, Port 4

Status: Normal

Type: SATA disk

Location type: Internal

Usage: Array disk

Size: 1,863 GB

System disk: No

Disk data cache: Enabled

Command queuing: NCQ

SATA transfer rate: 3 Gb/s

Model: ST2000DM001-9YN164

Serial number: W1E0D8ES

SCSI device ID: 4

Firmware: CC4C

Physical sector size: 4096 Bytes

Logical sector size: 512 Bytes

Disk on Controller 0, Port 5

Status: Normal

Type: SATA disk

Location type: Internal

Usage: Available

Size: 1,863 GB

System disk: No

Disk data cache: Enabled

Command queuing: NCQ

SATA transfer rate: 3 Gb/s

Model: ST2000DM001-9YN164

Serial number: S2F07SF5

SCSI device ID: 5

Firmware: CC4C

Physical sector size: 4096 Bytes

Logical sector size: 512 Bytes

0 Kudos
Highlighted
Valued Contributor III
9 Views

From what I see in the report your system is using an really old version of the Option ROM. You should check with Asus* for updated BIOS that should install an updated version of the Option ROM.

There is a method that you may follow to try to update this on your own, however this is not supported nor validated from our side. You may try it under your own convenience only if Asus* may not provide you an updated version. For more information you can use this as a reference:

0 Kudos
Highlighted
Beginner
9 Views

Problem Solved!

1st: I had to remove Intel's Matrix Support Technology. I had the most recent release, but little did I know upon the next release, Intel renamed the program to Rapid Storage Technology. I installed the latest release of RST.

2nd: When you define your raid array using RST, I gives you a message that you must define and format partition(s) before populating the array. Following that directive, I used the MS Disk Manager to define the partition and format it. Moments later RST initializes the array while the partition is being formatted. Hence, the array initialization is running concurrently with the partition format. Those action proceed without error for a couple days and finally stalls out with the array initialization at 69% and the partition format stalls at the same time at about 16%.

The correct procedure is to ignore what RST tells you to do after defining the array. First define the array with RST. Second leave you computer alone and it will begin the array initialization on it's own. Wait for that to finish. It took a couple days for me. You can monitor the status of RST and find something to do until the array initialization reaches 100% and finishes. Third, you can partition the array and format the partitions. When the format(s) are completed, the array is ready to use. Oh, a reboot is required between steps.

Remember that even if you define your array to as Raid 5 or 10, you still need to backup everything. Don't forget to test system recovery, because an untested backup/recovery strategy is usually worthless.

0 Kudos
Highlighted
Valued Contributor III
9 Views

Thank you, we appreciate your feedback on this, it is really valuable for any similar issues.

0 Kudos