Return to MAIN-Index  Return to SUB-Index    IBM-AUSTRIA - PC-HW-Support    30 Aug 1999

More Than One DDD Drive, One DHS, No RBL



More Than One DDD Drive, One DHS, No RBL


Note: The following procedure for multiple DDD drives assumes that the operating system is installed on one of the DDD drives.

In this scenario, the operating system is no longer functional.
Therefore, you must boot to the ServeRAID DOS Configuration Diskette to recover the logical drive.
It is extremely important to confirm that either the ServeRAID Administration Utility or Netfinity Manager 5.0 has been running prior to the drives being marked defunct.
If so, the utility or Netfinity Manager has logged the sequence of DDD events to a log file, either on a diskette or on a local or network drive.
With this file, you can view the log file on another machine to determine the 'inconsistent' drive.
When you know which drive is 'inconsistent', you can attempt to recover data.

Note: Once you lose more than one drive in a set of RAID-5 or RAID-1 logical drives, loss of data is definitely a possibility.
The steps below guide you through a recovery. However, a recovery may not be possible in every case.
  1.  View the ServeRAID log on another machine and write down the order in which the drives went defunct.
  2.  Boot to the ServeRAID DOS Configuration Diskette and choose View Configuration.
     Make sure that the Channel Record Table contains the correct information for the status  of all drives, not just those listed in the RAID log.

  3.  Using the ServeRAID Configuration Utility program, choose Set Device State and choose a DDD drive that is not listed in  the ServeRAID log.
     Set that drive to an ONL state. Repeat this step until the only DDD drives remaining are those indicated in the ServeRAID log file.

    Important: The drives marked DDD that are not listed in the ServeRAID log are the  last ones to go defunct.
     You must recover those drives first so that the information from them can be used to rebuild the original drive that failed   - that is, the 'inconsistent' drive. If you do not replace the 'inconsistent' drive last, the system uses it to rebuild the last drive that went defunct, and  data can be corrupted as a result. Therefore, it is extremely important to  perform the above step 3 carefully!

  4.  Choose Set Device State and then choose the last drive to go defunct according to the log file.
     Set that device to the ONL state. Repeat until there is only one DDD drive remaining.

  5.  Choose Set Device State and choose the DHS drive. Change its state from DHS to HSP.
  6.  Choose Rebuild and highlight the DDD drive.

Back to  Jump to TOP-of-PAGE
More INFORMATION / HELP is available at the  IBM-HelpCenter

Please see the LEGAL  -  Trademark notice.
Feel free - send a Email-NOTE  for any BUG on this page found - Thank you.