On 2009-12-03 16:12, [email protected] wrote: > Thank you very much for your reply. I thought these were errors relating > to the SCSI Inquiry not being read but the drive came with a Dell Server > we have, and it was working fine prior: > > Vendor ID : DELL > Product ID : MAX3073RC > Revision : D206 > > Though you mention something that is worrying, that the slot failed. Could > I make this drive a hot swappable or clear, which I did successfully, if > the slot had failed?
I haven't had a slot fail so I don't know. But it's certainly a possibility that could explain both the previous disk failing and the current one acting weird. That's all I'm saying. Have you used MegaCli to dump the controller event log? > Is there any way to test a failed slot through these tools? I checked > consistency (when the drive was replaced) and all was okay it seems. If > the slot failed, it seems to me that the drive may not even be recognized. I suggest putting the drive in a different box to see if it behaves better. That would be some evidence either way about the slot. I'm confused tho. Earlier you wrote: > We're running a RAID 5 and two days ago, a drive went down. We replaced it > and it went into Foreign mode to which I cleared it: > > sudo omconfig storage controller action=clearforeignconfig controller=0 > > That worked fine. However, I cannot seem to get this new hard drive to > attach itself to the RAID array, no matter what I try: How is it that you were unable to add the drive to the array but were able to perform a consistency check? > The drive is a Dell drive (well Fujitsu) - I find it odd it would bug > out... Drives bug out all the time. Please don't top post. _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
