It's not so much the actual read/write is it is the fact that every drive in the array spins up for every read/write - so there's more wear and tear on the drive mechanics rather than the disk platter's surface.-40hz
Okay, now we're getting somewhere (i think).
If you saved a file to a single drive, only it would spin up and be written to (along with the housekeeping of finding sufficient free clusters. On a three element RAID-5, three drives would be spun up to accomplish the same thing, plus need to write additional information (i.e. parity) above and beyond that contained in the actual file itself. That's three times the disk activity plus "parity tax" plus three times the heat generated over a single drive save operation.-40hz
Hm... three times the disk activity regarding spinning up three drives, ok. But three times the i/o I ain't buying (I'm thinking closer to 1.5). The scenario also assumes the drives weren't already spun up for some reason (do SCSI drives ever spin down?).
Energy consumption/heat issues I can see (kinda) but it makes me wonder how much extra is another HDD actually gonna cost in a year (filed under why I hate accountants

) $5?
So when you add in the MTBF for each of the three drives, you have a higher probability of a drive failing all other factors being equal.-40hz
Granted statistics isn't my thing ... But if the MTBF for a given drive is 3,000 hours, then for 3 drives it should still be 3,000 hrs. Or is this just the Murphy's Law More moving parts... argument? <-I'll buy that - as it appeals to my cynical side (hehe)).
And most arrays have more than three drives since that's the least cost effective RAID-5 configuration since you always sacrifice one drive to parity even if that drive doesn't exclusively hold the parity data.-40hz
Funny, I would consider 3 or a multiple thereof to be the best choice for RAID5. As regardless of how many drives you have you're going to sacrifice 33% of the total storage for parity info. Goes back to the less moving parts is better argument. Use a smaller number of larger drives. *Shrug* Having 3 drives just makes the 33% parity "overhead" more obvious, not higher.
Most times, the drives chosen for arrays are built to a higher quality standard than those normally deployed in PCs - so that may even up the failure occurrence rate up between server and non-server drives despite a higher utilization rate.-40hz
I understand where you're going here, but I can't help but think that the design of a Server/Enterprise class drive would sort of have to be predicated on the fact that it would not be getting very much sleep (e.g. spinning down) ... Know what I mean?