![]() In my case it wasn't anything wrong with the drives or the controller per-se but just a miscommunication between the (2) that caused some of the drives to change state unexpectedly and confuse the controller. I would try updating to the latest firmware for your controller card and see if the errors go away. In my case it also resulted in the controller reporting immature failure of the drives when they were in reality perfectly fine. It was fixed in a later firmware update for the controller which in effect disabled all power management functionality of the controller and caused the controller to not attempt to send in-active drives to sleep. Apparently it was a bug with the firmware of the I believe Seagate drives I had on the controller and the controller itself. In my case when I saw a similar error what was happening is the system was unexpectedly awakening the hot spare drive from sleep, sending it to sleep waking it up and this continuously happened all the time. This is likely a power management firmware bug that I have seen with some drives on these controllers.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |