5 Replies Latest reply on Oct 29, 2013 11:18 AM by kevin_intel

    Rapid Storage Raid-1 Rebuild, Questions

    obas

      Hi,

       

      I'm working building an image for our OEM workstation using an Intel Rapid
      Storage RAID-1 solution. I started with using Clonezilla (a disk copy software)
      to create an instance of our configured machine and restored the image into a
      RAID-1 configuration. Clonezilla doesn't support Rapid Storage so when the
      system rebooted to windows, the raid was in a faulted state. I
      got the system to rebuild the RAID-1 with my cloned image and everything is
      good.

       

      But the background initialization is anything but 'rapid'; I'm estimating
      8.5 hours to Migrate a 2TB RAID-1.

       

      Firstly does this sound normal speed?

       

      Secondly is there a method utility to do the initialization in the
      foreground and get the disks to sync faster in a dedicated manor?

       

      Finally could someone recommend better image cloning software which
      recognizes Rapid Storage and would leave the raid in working order after the
      reimaging?

       

      Our workstation product software records data at about a 1meg/s; There’s concern
      about delivery of a product to the consumer while Migration is still running.

       

       

      System Report

       

      System Information
      OS name:  Microsoft Windows 7 Professional
      OS version:  6.1.7601 Service Pack 1 7601

      Processor:  GenuineIntel Intel64 Family 6 Model 58 Stepping 9 3.601  GHz
      BIOS: K51 v01.61

      Intel® Rapid Storage Technology enterprise Information
      Kit installed:  11.5.4.1001
      User interface version:  11.5.4.1001
      Language:  English (United States)
      RAID option ROM version:  11.5.0.1582
      Driver version:  11.5.4.1001
      ISDI version:  11.5.4.1001

       

      Storage System Information
      RAID Configuration

      Array Name:  SATA_Array_0000
      Size:  3,815,457 MB
      Available space:  7 MB
      Number of volumes:  1
      Volume member:  RAIDVOL
      Number of array disks:  2
      Array disk:  Z1E5A3M6
      Array disk:  Z1E5AD35
      Disk data cache:  Enabled

      Volume name:  RAIDVOL
      Status:  Migrating data 87% complete
      Type:  RAID 1
      Size:  1,907,724 MB
      System volume:  Yes 
      Data stripe size:  64 KB
      Write-back cache:  Enabled
      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:  3
      Number of volumes:  1
      Volume:  RAIDVOL
      Number of spares:  0
      Number of available disks:  0
      Rebuild on Hot Plug:  Disabled

      Manufacturer:  32902
      Model number:  10274
      Product revision:  4
      Direct attached disk:  Z1E5A3M6
      Direct attached disk:  Z1E5AD35

       

       

      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: 6 Gb/s
      Model:  ST2000DM001-1CH164                     
      Serial number:  Z1E5A3M6
      SCSI device ID:  0
      Firmware:  HP34   
      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: 6 Gb/s
      Model:  ST2000DM001-1CH164                     
      Serial number:  Z1E5AD35
      SCSI device ID:  1
      Firmware:  HP34   
      Physical sector size:  4096 Bytes
      Logical sector size:  512 Bytes

       

       

      ATAPI device on Controller 0, Port 2
      Location type:  Internal
      SATA transfer rate: 1.5 Gb/s
      Model:  hp       BD-RE  BH40L                  
      Serial number:  327CF000456
      Firmware:  B726  

        • 1. Re: Rapid Storage Raid-1 Rebuild, Questions
          kevin_intel

          Hi obas,

           

          The initialization process of the raid that is taking is completely normal. This depends on the HDD capacity and information. I honestly have seen cases where it takes up to 2 days to complete this task so, 8 hours seems normal.

           

          To complete this process, from our side the only way to do it is using the IRST and I am afraid that we do not handle any other software or 3rd party software to clone a raid image.

          1 of 1 people found this helpful
          • 2. Re: Rapid Storage Raid-1 Rebuild, Questions
            obas

            Hi Kevin,

                

            Thanks for the information on confirming the Migration time.

             

            As for the cloning software, my thoughts are if the RAID has been pre
            synced from our hardware manufacture. Then my image could be applied using
            clone software which recognizes the RAID configuration. Then the total
            bench setup time might be reduced, as the image would be written through
            the RAID controller.  Have you heard of this being achievable?

             

            Another question, Does the IRST write to a log file or the windows event viewer? I don’t
            believe the tray icon will meet our requirements, for warning and failure
            status notifications.   Our product runs full screen, our application
            will need a means of detecting a failure so then it could communicate to the
            user some action to follow. Our system does not have network access for email
            notifications.

             

             

            thanks,

            • 3. Re: Rapid Storage Raid-1 Rebuild, Questions
              kevin_intel

              obas,

              Honestly we do not handle information about software with these capabilities. My best recommendation on this is to contact RAID card manufacturers and confirm if their 3rd party software can do such task.

               

              In regards the other question, IRST does have an event log but it cannot be accessed unless the IRST is uninstalled and then the reports will be visible under the Windows Event Log.

              • 4. Re: Rapid Storage Raid-1 Rebuild, Questions
                obas

                  Kevin,

                 

                Thanks again for your input; I agree with your assessment that we
                should contact other RAID manufacturers. But focusing right now on our
                current IRST implementation, I had to chuckle with the fact that IRST has to be
                uninstalled for the event information to be written to windows.
                Please clarify that the uninstalling IRST means the software application
                which manages the RAID and reports status in the windows tray. 

                    

                I'll double check this scenario today; that the event is actually written to
                the windows log. I have a prototype machine without the windows IRST
                software installed which should have those events listed.

                 

                That would mean an additional step but important one, to uninstall the IRST
                after RAID configuration for our application to monitor for a raid fault.
                Will the raid migration process continue after uninstall of IRST or should it
                go to 100% prior to?

                 

                thanks again for your continued support

                • 5. Re: Rapid Storage Raid-1 Rebuild, Questions
                  kevin_intel

                  Hi obas,

                  My best recommendation is to complete the current migration processes before doing any other step.