![]() Which links to a firmware for this drive provided by Dell. values on it's drives, causing them to be misinterpreted by third party tools (ie HP System Health Monitor). We got the machine last fall, and have periodically experienced exactly the same thing mentioned by the original poster - vmware virtual machines would suddenly stop responding (although the machine itself would still be accessible, probably because I was running vmware off an SD card).Īfter I found this thread, I did a little digging on the Seagate drive and found this:īasically, Seagate puts it's own proprietary information into the S.M.A.R.T. The G7, however, has been a different story. I have 3 hp dl380 servers - a G5, a G6, and a G7, each with 8 of the Seagate ST9500420AS drives mentioned, and all running vmware ESXi 4.1. All three have always reported an overheated condition on POST, although due to the different iLO versions (version 1 for the G5, version 2 for the G6, and version 3 on the new G7), the two older machines have always coped with the issue, albeit with the fans running at excessive levels as noted on this thread. LSI Logic full feature set and HP has two features. I have an LSI Logic SCSI controller and an identical HP SCSI controller. The problem is most like the communication with the backplane in the non-HP enclosure. Hard drives, controllers, and cards use only HP. I have one server running Axiom HP memory. You don't get Seagate drives, you use HP drives. However, if you want a server to function properly and be supported, you use HP parts. ![]() I ended up removing the enclosures and upgrading to SAS RAID. Something in the backplane did not like the firmware on the controller. ![]() I never was able to get it working properly again. ![]() ![]() LSI Logic checked the controller and replaced it. One day, all the drives started to fail in cascade. I had Supermicro SCSI SCA enclosures at home. The enclosure backplane does a lot more than just setting IDs. The firmware on the drives and controller backplane could be causing the misreading. The issue could be the enclosure backplane from non-HP components is not communicating with the server properly. HPE Blog, Austria, Germany & Switzerland. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |