Changes between Version 7 and Version 8 of megaSAS_RAID_card_events

Timestamp:

Dec 8, 2011, 9:35:43 PM (15 years ago)

Author:

cindy

Comment:

--

megaSAS_RAID_card_events

@@ -8 +8 @@
 Nov 2011
  * ipp064 drive 3 failed Show FAILED and was replaced. Still showed FAILED. This was not normal.  I (Cindy)took the drive offline and put it back online. This is what I have to do for some of my 3ware arrays ( not the ipp 3ware arrays ).  This is what can be done to rebuild a drive that is already part of the array - but not a new drive.  It caused corruption in the data. 
- * ipp058 drive 20 failed, showed FAILED and was replaced.  Still showed FAILED.  Under direction from LSI - who admitted this was not normal - I was able to start rebuild on the new drive.  It rebuilt.  We get this message every 24 hours. LSI stated that marking the drive as an Emergency Spare is normal for this driver, it is a good thing - this warning should not be generated. This is the warning he is asking the engineers about.
-  * Controller ID: 0 Reminder: Potential non-optimal configuration due, PD commissioned as Emergency spare: --:--:20
+ * ipp058 drive 20 failed, showed FAILED and was replaced.  Still showed FAILED.  Under direction from LSI - who admitted this was not normal - I was able to start rebuild on the new drive.  It rebuilt.  We get a message every 24 hours. '''Controller ID: 0 Reminder: Potential non-optimal configuration due, PD commissioned as Emergency spare: --:--:20'''  LSI stated that marking the drive as an Emergency Spare is normal for this driver, it is a good thing - this warning should not be generated. This is the warning he is asking the engineers about.
  * LSI sends new driver, Gavin installs it on 1pp064 and ipp058.
  * ipp056 drive fails. Gavin installs the driver and reboots the machine.  We replace the drive and it automatically rebuilds. It also generated the warning.