[Phoenix32]

Originally Posted by schnappi

That's what I said on 08-27-2009 08:33 AM .. But some are full of oneself.

And some are just mindless zombies who just make assumptions based on one observation or worse yet, nothing at all.

Me? I don't care if someone takes my advice or not. I do however care when some clown puts out crap information as fact in a place where people come for help and can be mislead easily. And THAT is what your information is. CRAP! With no basis in anything other than you couldn't do it and neither could one other guy.

Instead of puting this bad information out as fact, how about puting it out with questions to figure out what might be wrong with you or your methods.

Since you are determined to put this bogus information out, then prepare to defend it. So let's get right to it. I have some simple question I would LOVE for you to explain to us with your powerful insight, observations, and skills. I beg you to teach me here the error or my ways.

#1 How do explain away the FACT that I myself (and others) have installed those very same model drives in those very same model Snap Servers with no problems? Was it just lucky magic, or what? I am dieing to hear your answer to this one.

#2 Theorizing the following; a) WD would not put out a drive that did not follow proper interface standards. b) The Snap Server in question follows proper interface standards. c) The Snap Server does not have some type of BIOS hard setting for a specific drive model combination. Then why would this combination not work? If you are so sure here this doesn't work, please tells us why? I await eagerly for this insight you have.

-Notes on the theories of #2: There are minor things that can slip past a manufacturer of their drives, or Host Bus Adapters, BIOS programing etc or even shortcuts they might make that can cause problems, but these are usually obscure and rare combos, not mainstream. If the BIOS is hard set to a particular drive combination, you would not be able to do the upgrades we do without some reprograming. We pretty much know this is not the case of a Snap 4200.


As an example of proper good information that is similar to this case, let's look at a Snap 4000.

You cannot use some model Seagate drives (and a few others) in some model Snap 4000. Makes no sense on the surface, but there is a simple explaination.

- There are 4 different models of the Snap 4000, 2 of which use cables that require the use of Cable Select rather than Master/Slave.

- The Snap 4000 does not support ATA133.

- Some model Seagate drives (and a few other drives out there) that when put in CS mode, will switch to AT133 and not switch down to a lower speed to meet the HBA speed. Or least not in the timing required for that HBA.

End result, the Snap 4000 models that have the CS requirement but cannot do ATA133 will puke with drives like some of the Seagates and others that do the ATA133 thing in CS mode. As a note, this can be fixed by changing the cables so that you can use the Master/Slave mode.

See? In this example, it makes sence, can be proven and is a known quanity. Now lets go back to your BS theory.

The Snap 4200 does not have the ATA133/CS problem, and in fact pretty much uses any drive in a Standard configuration. So why would it not work with any mainstream drives in a standard configuration? Makes no sence at all. If either the Snap 4200 or those Model WD drives had problems with standard single/master configurations, I am pretty sure it would be a big deal and it would be pretty common knowledge about that unit or drive. The Snap having problems with MANY drives, or the Drive Model having MANY problems in many servrs or computers. IT MAKES NO SENSE!

Then, you have to come back and wonder why others have not had this problem and it worked fine (like me).


Now is no time to just sit back and expect me or anyone else to just accept this theory of yours as some magic fact. Please, I am dieing to hear your explaination as to why this happens and what the problem is. Please enlighten us all. I eagerly await your response. I am always open to learning some new bit of information.