View Single Post
Unread 08-19-2006, 03:38 PM   #10
Phoenix32
Thermophile
 
Phoenix32's Avatar
 
Join Date: May 2006
Location: Yakima, WA
Posts: 1,282
Default Re: Snap 4100 orphaned drive question

Quote:
Originally Posted by Reason_Man

I even replaced the ribbon cables some extras I had lying around but the same thing happens.
Well, I guess after this comment I need to throw in my 2 cents worth, Dave can correct me if I am out to lunch here.

Changed cables?

Many SNAP servers (with multiple drives), but not all, use cable select cables not standard IDE cable. While this may not be a problem in your case, and most certainly is not the orignal problem, changing the cables in the middle of this "MAY HAVE" created another problem in the process. Meaning, the new drive might have corrected your problem but changing the cables kept it from doing so. In fact this may be why your error messages changed and no longer showing a fatal disk error.

Hey, just my 2 cents worth. I do not have a 4100, but my 4000 does in fact use cable select cables and changing them to standard IDE cables would be a problem. But as I said, Dave can correct me if I am wrong here and I will just shut up.



Side Note: Different RAID controllers are more or less sensitive to the drives sizes in any type RAID that uses stripping, some will work, some will not, and the ones that will vary in how far they will go. I cannot speak for the controllers built into the SNAP servers. HOWEVER, I can tell you that from my experience, most RAID controllers in RAID 5 arrays using HOT SPARE will usualy NOT pick up a non identical drive to be used in a failed array. When non identical drives can be used, you usualy have to do it manualy as a general rule. Just a thought.

Last edited by Phoenix32; 08-19-2006 at 03:57 PM.
Phoenix32 is offline   Reply With Quote