
//Edit : cpa pret d'arriver : 12h et 22% pour 400Go. Je m'en vais voir combien coute du SAS sur Ebay.
Et pour couronner le tout je pensais acheter un lot de 2x450Go SAS pour avoir proche du To en stockage sauf que ...[root@ML350-G6:/vmfs/volumes] ls
00771275-fcf9a6ce-1446-efd640e6b259 58653bf8-f5186e77-e39c-b4b52f675dba
[#0000FF]2to[/#0000FF] 58a6b6f7-47594ec8-32dd-b4b52f675dba
32c5c27d-50282089-27bd-941f2978ff8c 58a6b74e-d3311d63-a2f0-b4b52f675dba
58653bf2-e53f19b8-ed1b-b4b52f675dba [#0000FF]80go[/#0000FF]
58653bf8-0fe04671-fd00-b4b52f675dba [#0000FF]datastore1[/#0000FF]
[root@ML350-G6:~] time dd if=/dev/zero of=/vmfs/volumes/[#0000FF]80go[/#0000FF]/test.tmp bs=1024 count=1000000
1000000+0 records in
1000000+0 records out
[#FF0E00]real 11m 56.28s[/#FF0E00]
user 0m 4.61s
sys 0m 0.00s
[root@ML350-G6:~] time dd if=/dev/zero of=/vmfs/volumes/[#0E00F0]datastore1[/#0E00F0]/test.tmp bs=1024 count=1000000
1000000+0 records in
1000000+0 records out
[#1CFF00]real 0m 6.50s[/#1CFF00]
user 0m 4.46s
sys 0m 0.00s
[root@ML350-G6:~]
https://community.spiceworks.com/topic/ ... ive-accessI see what you are saying. With Smart Array controllers you cannot do JBOD, so this is a way to get around that roadblock.
Je me demande pourquoi le Sata est si lent, de mémoire je n'ai pas vu de paramètres spécifiques au contrôleur dans le BIOS ...[root@ML350-G6:~] time dd if=/dev/zero of=/vmfs/volumes/[#0000FF]2to[/#0000FF]/test.tmp bs=1024 count=100000
100000+0 records in
100000+0 records out
[#FF0000]real 1m 36.57s[/#FF0000]
user 0m 0.47s
sys 0m 0.00s
[root@ML350-G6:~]
That's all more or less true (despite being almost impossible to read), however, none of it requires special firmware on hard drives or limiting the system's drive controller to only working with 'branded drives'. The functionality that allows for IPMI (ILO) management of drives is almost exclusively built on standard SMART drive error reporting and statistics. That is all the drive has to support to provide the failure notification stuff. No reason to need specially branded drives.the issue as far as hp has responded is that the hp hard drives are preloaded with firmware to interact directly with the hp controllers and servers. this has not been put on the drives to disuade you from using non hp drives. this is a feature that hp offers with there servers. which they believe justifies the cost. the controller and hard drive will interact with ILO (integrated lights out) which has features built in for server management. for example ILO will send you warnings if a drive is going to fail. if the controller looks for that functionality on the drive and does not find it you have a percent chance that the drive will pull through that and work. also if the drive does work there is a chance that the drive will be worn down faster than it should. I have seen several reports of this. I don't work for hp. but i work with them building servers for large solutions. I see people trying to use the non hp drives all day long. find some sleds from old hard drives on ebay and save some money. it's doable. in fact I think you can even find some way to get the firmware on the 3r party hard drives. but any way you look at it the manufacturer won't support these options. hp servers are more expensive than whitebox servers because of the many features they build into there servers/controllers/hard drives to ease your workload on your IT environments. such as ILO remote management. their servers will even send you a text message if your hard drives are going to fail. lol. But all in all when you try to use there hardware outside of hps intended use there will always be problems.
The reason HP and others do it is purely to increase profit by:
A - Making you pay more for branded drives
B - Saving money on support costs by turning away support cases where drives are not branded
C - Saving money on support costs by limiting compatibility testing to only their preferred drives
car mes SAS sont en 2.5 bien sûrpour connecter mes HDD Sata sur le sas je ne peux pas, ce sont des 3.5"