peter_sm Posted December 5, 2011 Share Posted December 5, 2011 Hi all! I have a controllercard that is some year old now (VScom Seriel ATA-150 PCI Controller) (Silicon Image SiI 3112 SATARaid Controller Driver) I planned to use it only for my cache drive. then I can free up one slot for a new data drive ;-) after that I can't put in more disc in my BOX ;-) Anyone knows if this can be used on unraid? Swedish link: http://www.ciao.se/Produktinformation/TITAN_SATA_200__71306 //Peter Quote Link to comment
S80_UK Posted December 5, 2011 Share Posted December 5, 2011 Hi Peter, I think it very likely that it can be used. I (and others) have used SIL3114 (the four port version) without issues. Cheers, Les. Quote Link to comment
Johnm Posted December 5, 2011 Share Posted December 5, 2011 I would check your cache drive speed before and after the change. It might make more sense to put the last data drive on this controller and have the cache on the motherboard? if there is a speed hit. i rather have my parity take an extra hour then a cache drive speed hit. then again, it might perform just fine the way you suggested.. just food for thought. Quote Link to comment
peter_sm Posted December 5, 2011 Author Share Posted December 5, 2011 Thanks, I going to try this later this week, I let you know ;.) Quote Link to comment
peter_sm Posted December 5, 2011 Author Share Posted December 5, 2011 One more thing ;-) do I need to change some settings in the bios of the card ? //Peter Quote Link to comment
WeeboTech Posted December 5, 2011 Share Posted December 5, 2011 I would install it and check the read/write speeds locally within the machine using the dd writeread10gb script. Then I would do a network test. If the speed change is small I would use the PCI card for the cache drive rather then adding time to a full parity operation. In my mind, a full parity operation needs to complete as fast as possible since that is when a drive is in jeopardy of some form of failure. If you loose a drive, you want to rebuild it as fast as possible. If you have some issue where you need to rebuild parity, you want that as fast as possible. If I can only move data to a cache drive at 60MB/s or so, then being on a SATA-150 controller may not really be an issue. Quote Link to comment
S80_UK Posted December 5, 2011 Share Posted December 5, 2011 One more thing ;-) do I need to change some settings in the bios of the card ? //Peter If it has any, make sure that no local RAID features are enabled. Probably they won't be if you only have a single drove connected to it. Quote Link to comment
peter_sm Posted December 5, 2011 Author Share Posted December 5, 2011 I would install it and check the read/write speeds locally within the machine using the dd writeread10gb script. Can this script be used safely on my array? so it not destroy ant data ? and can i test all my disk with this script? I saw how this scripts works, doing some test on all my disk right now. Quote Link to comment
peter_sm Posted December 5, 2011 Author Share Posted December 5, 2011 Have tested my Disk1 (with parity), is the result normal ? so I can compare this date with my old card later..... root@Tower:/boot# writeread10gb.sh /mnt/disk1/test.dd writing 10240000000 bytes to: /mnt/disk1/test.dd 1+0 records in 1+0 records out 1024 bytes (1.0 kB) copied, 11.2927 s, 0.1 kB/s 405+0 records in 405+0 records out 414720 bytes (415 kB) copied, 16.5497 s, 25.1 kB/s 96644+0 records in 96644+0 records out 98963456 bytes (99 MB) copied, 20.2832 s, 4.9 MB/s 222396+0 records in 222396+0 records out 227733504 bytes (228 MB) copied, 25.3209 s, 9.0 MB/s 369209+0 records in 369209+0 records out 378070016 bytes (378 MB) copied, 30.387 s, 12.4 MB/s 518895+0 records in 518895+0 records out 531348480 bytes (531 MB) copied, 35.5608 s, 14.9 MB/s 692794+0 records in 692794+0 records out 709421056 bytes (709 MB) copied, 40.5316 s, 17.5 MB/s 854657+0 records in 854657+0 records out 875168768 bytes (875 MB) copied, 45.6858 s, 19.2 MB/s 993358+0 records in 993358+0 records out 1017198592 bytes (1.0 GB) copied, 50.6884 s, 20.1 MB/s 1150540+0 records in 1150540+0 records out 1178152960 bytes (1.2 GB) copied, 55.7097 s, 21.1 MB/s 1317410+0 records in 1317410+0 records out 1349027840 bytes (1.3 GB) copied, 60.8122 s, 22.2 MB/s 1476810+0 records in 1476810+0 records out 1512253440 bytes (1.5 GB) copied, 65.9259 s, 22.9 MB/s 1639138+0 records in 1639138+0 records out 1678477312 bytes (1.7 GB) copied, 70.9085 s, 23.7 MB/s 1819879+0 records in 1819879+0 records out 1863556096 bytes (1.9 GB) copied, 75.9407 s, 24.5 MB/s 1975042+0 records in 1975042+0 records out 2022443008 bytes (2.0 GB) copied, 81.0523 s, 25.0 MB/s 2218812+0 records in 2218812+0 records out 2272063488 bytes (2.3 GB) copied, 86.1849 s, 26.4 MB/s 2357904+0 records in 2357904+0 records out 2414493696 bytes (2.4 GB) copied, 91.1585 s, 26.5 MB/s 2486928+0 records in 2486928+0 records out 2546614272 bytes (2.5 GB) copied, 96.3011 s, 26.4 MB/s 2638815+0 records in 2638815+0 records out 2702146560 bytes (2.7 GB) copied, 101.224 s, 26.7 MB/s 2809569+0 records in 2809569+0 records out 2876998656 bytes (2.9 GB) copied, 106.345 s, 27.1 MB/s 2974231+0 records in 2974231+0 records out 3045612544 bytes (3.0 GB) copied, 111.37 s, 27.3 MB/s 3110577+0 records in 3110577+0 records out 3185230848 bytes (3.2 GB) copied, 116.44 s, 27.4 MB/s 3251193+0 records in 3251193+0 records out 3329221632 bytes (3.3 GB) copied, 121.534 s, 27.4 MB/s 3411449+0 records in 3411449+0 records out 3493323776 bytes (3.5 GB) copied, 126.696 s, 27.6 MB/s 3596241+0 records in 3596241+0 records out 3682550784 bytes (3.7 GB) copied, 131.669 s, 28.0 MB/s 3839073+0 records in 3839073+0 records out 3931210752 bytes (3.9 GB) copied, 136.642 s, 28.8 MB/s 3988833+0 records in 3988833+0 records out 4084564992 bytes (4.1 GB) copied, 141.934 s, 28.8 MB/s 4128857+0 records in 4128857+0 records out 4227949568 bytes (4.2 GB) copied, 146.826 s, 28.8 MB/s 4249818+0 records in 4249818+0 records out 4351813632 bytes (4.4 GB) copied, 151.839 s, 28.7 MB/s 4387873+0 records in 4387873+0 records out 4493181952 bytes (4.5 GB) copied, 156.931 s, 28.6 MB/s 4545589+0 records in 4545589+0 records out 4654683136 bytes (4.7 GB) copied, 162.004 s, 28.7 MB/s 4801605+0 records in 4801605+0 records out 4916843520 bytes (4.9 GB) copied, 167.155 s, 29.4 MB/s 4976161+0 records in 4976161+0 records out 5095588864 bytes (5.1 GB) copied, 172.118 s, 29.6 MB/s 5148778+0 records in 5148778+0 records out 5272348672 bytes (5.3 GB) copied, 177.192 s, 29.8 MB/s 5280509+0 records in 5280509+0 records out 5407241216 bytes (5.4 GB) copied, 182.233 s, 29.7 MB/s 5399634+0 records in 5399634+0 records out 5529225216 bytes (5.5 GB) copied, 187.387 s, 29.5 MB/s 5542615+0 records in 5542615+0 records out 5675637760 bytes (5.7 GB) copied, 192.339 s, 29.5 MB/s 5702751+0 records in 5702751+0 records out 5839617024 bytes (5.8 GB) copied, 197.392 s, 29.6 MB/s 5870310+0 records in 5870310+0 records out 6011197440 bytes (6.0 GB) copied, 202.443 s, 29.7 MB/s 6036316+0 records in 6036316+0 records out 6181187584 bytes (6.2 GB) copied, 207.502 s, 29.8 MB/s 6171474+0 records in 6171474+0 records out 6319589376 bytes (6.3 GB) copied, 212.618 s, 29.7 MB/s 6334172+0 records in 6334172+0 records out 6486192128 bytes (6.5 GB) copied, 217.62 s, 29.8 MB/s 6478401+0 records in 6478401+0 records out 6633882624 bytes (6.6 GB) copied, 222.7 s, 29.8 MB/s 6624994+0 records in 6624994+0 records out 6783993856 bytes (6.8 GB) copied, 227.807 s, 29.8 MB/s 6798865+0 records in 6798865+0 records out 6962037760 bytes (7.0 GB) copied, 233.015 s, 29.9 MB/s 6974653+0 records in 6974653+0 records out 7142044672 bytes (7.1 GB) copied, 238.291 s, 30.0 MB/s 7150786+0 records in 7150786+0 records out 7322404864 bytes (7.3 GB) copied, 243.074 s, 30.1 MB/s 7322571+0 records in 7322571+0 records out 7498312704 bytes (7.5 GB) copied, 247.977 s, 30.2 MB/s 7486584+0 records in 7486584+0 records out 7666262016 bytes (7.7 GB) copied, 253.068 s, 30.3 MB/s 7644462+0 records in 7644462+0 records out 7827929088 bytes (7.8 GB) copied, 258.067 s, 30.3 MB/s 7804507+0 records in 7804507+0 records out 7991815168 bytes (8.0 GB) copied, 263.354 s, 30.3 MB/s 7986902+0 records in 7986902+0 records out 8178587648 bytes (8.2 GB) copied, 268.198 s, 30.5 MB/s 8142841+0 records in 8142841+0 records out 8338269184 bytes (8.3 GB) copied, 273.249 s, 30.5 MB/s 8329807+0 records in 8329807+0 records out 8529722368 bytes (8.5 GB) copied, 278.281 s, 30.7 MB/s 8480454+0 records in 8480454+0 records out 8683984896 bytes (8.7 GB) copied, 283.347 s, 30.6 MB/s 8629688+0 records in 8629688+0 records out 8836800512 bytes (8.8 GB) copied, 288.417 s, 30.6 MB/s 8777753+0 records in 8777753+0 records out 8988419072 bytes (9.0 GB) copied, 293.66 s, 30.6 MB/s ^[[15~8937713+0 records in 8937713+0 records out 9152218112 bytes (9.2 GB) copied, 298.642 s, 30.6 MB/s 9106729+0 records in 9106729+0 records out 9325290496 bytes (9.3 GB) copied, 303.685 s, 30.7 MB/s 9285459+0 records in 9285459+0 records out 9508310016 bytes (9.5 GB) copied, 308.606 s, 30.8 MB/s 9428730+0 records in 9428730+0 records out 9655019520 bytes (9.7 GB) copied, 313.708 s, 30.8 MB/s 9603377+0 records in 9603377+0 records out 9833858048 bytes (9.8 GB) copied, 318.692 s, 30.9 MB/s 9740935+0 records in 9740935+0 records out 9974717440 bytes (10 GB) copied, 323.776 s, 30.8 MB/s 9893205+0 records in 9893205+0 records out 10130641920 bytes (10 GB) copied, 328.84 s, 30.8 MB/s ^[[15~9941209+0 records in 9941209+0 records out 10179798016 bytes (10 GB) copied, 334.903 s, 30.4 MB/s 9949841+0 records in 9949841+0 records out 10188637184 bytes (10 GB) copied, 339.352 s, 30.0 MB/s 9972497+0 records in 9972497+0 records out 10211836928 bytes (10 GB) copied, 344.562 s, 29.6 MB/s 9976717+0 records in 9976717+0 records out 10216158208 bytes (10 GB) copied, 349.777 s, 29.2 MB/s 9977601+0 records in 9977601+0 records out 10217063424 bytes (10 GB) copied, 354.782 s, 28.8 MB/s 10000000+0 records in 10000000+0 records out 10240000000 bytes (10 GB) copied, 358.69 s, 28.5 MB/s write complete, syncing reading from: /mnt/disk1/test.dd 10000000+0 records in 10000000+0 records out 10240000000 bytes (10 GB) copied, 99.215 s, 103 MB/s removing: /mnt/disk1/test.dd removed `/mnt/disk1/test.dd' And this is to may cache disk root@Tower:/boot# writeread10gb.sh /mnt/cache/test.dd writing 10240000000 bytes to: /mnt/cache/test.dd 324705+0 records in 324705+0 records out 332497920 bytes (332 MB) copied, 5.02506 s, 66.2 MB/s 531707+0 records in 531707+0 records out 544467968 bytes (544 MB) copied, 10.1158 s, 53.8 MB/s 900869+0 records in 900869+0 records out 922489856 bytes (922 MB) copied, 15.107 s, 61.1 MB/s 1173813+0 records in 1173813+0 records out 1201984512 bytes (1.2 GB) copied, 20.1343 s, 59.7 MB/s 1480845+0 records in 1480845+0 records out 1516385280 bytes (1.5 GB) copied, 25.1842 s, 60.2 MB/s 1764390+0 records in 1764390+0 records out 1806735360 bytes (1.8 GB) copied, 30.2154 s, 59.8 MB/s 1978177+0 records in 1978177+0 records out 2025653248 bytes (2.0 GB) copied, 35.2471 s, 57.5 MB/s 2253842+0 records in 2253842+0 records out 2307934208 bytes (2.3 GB) copied, 40.4596 s, 57.0 MB/s 2584082+0 records in 2584082+0 records out 2646099968 bytes (2.6 GB) copied, 45.3731 s, 58.3 MB/s 2895610+0 records in 2895610+0 records out 2965104640 bytes (3.0 GB) copied, 50.3655 s, 58.9 MB/s 3159386+0 records in 3159386+0 records out 3235211264 bytes (3.2 GB) copied, 55.392 s, 58.4 MB/s 3404402+0 records in 3404402+0 records out 3486107648 bytes (3.5 GB) copied, 60.4505 s, 57.7 MB/s 3583710+0 records in 3583710+0 records out 3669719040 bytes (3.7 GB) copied, 65.4902 s, 56.0 MB/s 3866923+0 records in 3866923+0 records out 3959729152 bytes (4.0 GB) copied, 70.6281 s, 56.1 MB/s 4204259+0 records in 4204259+0 records out 4305161216 bytes (4.3 GB) copied, 76.5738 s, 56.2 MB/s 4502025+0 records in 4502025+0 records out 4610073600 bytes (4.6 GB) copied, 80.6254 s, 57.2 MB/s 4776547+0 records in 4776547+0 records out 4891184128 bytes (4.9 GB) copied, 85.6531 s, 57.1 MB/s 5059779+0 records in 5059779+0 records out 5181213696 bytes (5.2 GB) copied, 90.6956 s, 57.1 MB/s 5349308+0 records in 5349308+0 records out 5477691392 bytes (5.5 GB) copied, 95.7081 s, 57.2 MB/s 5569109+0 records in 5569109+0 records out 5702767616 bytes (5.7 GB) copied, 100.729 s, 56.6 MB/s 5905748+0 records in 5905748+0 records out 6047485952 bytes (6.0 GB) copied, 105.794 s, 57.2 MB/s 6269533+0 records in 6269533+0 records out 6420001792 bytes (6.4 GB) copied, 110.847 s, 57.9 MB/s 6541237+0 records in 6541237+0 records out 6698226688 bytes (6.7 GB) copied, 115.838 s, 57.8 MB/s 6812077+0 records in 6812077+0 records out 6975566848 bytes (7.0 GB) copied, 120.881 s, 57.7 MB/s 7053275+0 records in 7053275+0 records out 7222553600 bytes (7.2 GB) copied, 125.899 s, 57.4 MB/s 7384510+0 records in 7384509+0 records out 7561737216 bytes (7.6 GB) copied, 130.958 s, 57.7 MB/s 7672573+0 records in 7672573+0 records out 7856714752 bytes (7.9 GB) copied, 136.008 s, 57.8 MB/s 7880252+0 records in 7880252+0 records out 8069378048 bytes (8.1 GB) copied, 141.104 s, 57.2 MB/s 8268313+0 records in 8268313+0 records out 8466752512 bytes (8.5 GB) copied, 146.077 s, 58.0 MB/s 8491034+0 records in 8491034+0 records out 8694818816 bytes (8.7 GB) copied, 151.104 s, 57.5 MB/s 8731813+0 records in 8731813+0 records out 8941376512 bytes (8.9 GB) copied, 156.17 s, 57.3 MB/s 9038387+0 records in 9038387+0 records out 9255308288 bytes (9.3 GB) copied, 162.028 s, 57.1 MB/s 9297971+0 records in 9297971+0 records out 9521122304 bytes (9.5 GB) copied, 166.626 s, 57.1 MB/s 9599541+0 records in 9599541+0 records out 9829929984 bytes (9.8 GB) copied, 171.486 s, 57.3 MB/s 9902149+0 records in 9902149+0 records out 10139800576 bytes (10 GB) copied, 176.348 s, 57.5 MB/s 10000000+0 records in 10000000+0 records out 10240000000 bytes (10 GB) copied, 179.244 s, 57.1 MB/s write complete, syncing reading from: /mnt/cache/test.dd 10000000+0 records in 10000000+0 records out 10240000000 bytes (10 GB) copied, 132.131 s, 77.5 MB/s removing: /mnt/cache/test.dd removed `/mnt/cache/test.dd' root@Tower:/boot# Quote Link to comment
WeeboTech Posted December 5, 2011 Share Posted December 5, 2011 The start of the disk1 test is a bit slow. Were the disks spun down or are there tons of files on that disk? The end result is pretty normal depending on model numbers of the disks. Quote Link to comment
peter_sm Posted December 10, 2011 Author Share Posted December 10, 2011 I have now installed the "old" sata-150 card, moved my cache drive to this. all looks OK, same speed as before! see log below. FYI: I'm going to test all my drives now, and see what they perform. root@Tower:/boot# writeread10gb.sh /mnt/cache/test.dd writing 10240000000 bytes to: /mnt/cache/test.dd 299593+0 records in 299593+0 records out 306783232 bytes (307 MB) copied, 5.43943 s, 56.4 MB/s 558665+0 records in 558665+0 records out 572072960 bytes (572 MB) copied, 10.4087 s, 55.0 MB/s 836587+0 records in 836587+0 records out 856665088 bytes (857 MB) copied, 15.6887 s, 54.6 MB/s 1119719+0 records in 1119719+0 records out 1146592256 bytes (1.1 GB) copied, 20.1901 s, 56.8 MB/s 1392469+0 records in 1392469+0 records out 1425888256 bytes (1.4 GB) copied, 25.23 s, 56.5 MB/s 1685583+0 records in 1685582+0 records out 1726035968 bytes (1.7 GB) copied, 30.2637 s, 57.0 MB/s 1902606+0 records in 1902606+0 records out 1948268544 bytes (1.9 GB) copied, 35.3291 s, 55.1 MB/s 2156873+0 records in 2156873+0 records out 2208637952 bytes (2.2 GB) copied, 40.3697 s, 54.7 MB/s 2504672+0 records in 2504672+0 records out 2564784128 bytes (2.6 GB) copied, 45.4342 s, 56.5 MB/s 2723012+0 records in 2723012+0 records out 2788364288 bytes (2.8 GB) copied, 51.5143 s, 54.1 MB/s 3019067+0 records in 3019067+0 records out 3091524608 bytes (3.1 GB) copied, 55.5317 s, 55.7 MB/s 3241242+0 records in 3241242+0 records out 3319031808 bytes (3.3 GB) copied, 60.5598 s, 54.8 MB/s 3525616+0 records in 3525616+0 records out 3610230784 bytes (3.6 GB) copied, 65.6516 s, 55.0 MB/s 3795241+0 records in 3795241+0 records out 3886326784 bytes (3.9 GB) copied, 70.6816 s, 55.0 MB/s 4060185+0 records in 4060185+0 records out 4157629440 bytes (4.2 GB) copied, 76.5047 s, 54.3 MB/s 4269451+0 records in 4269451+0 records out 4371917824 bytes (4.4 GB) copied, 80.7489 s, 54.1 MB/s 4586425+0 records in 4586425+0 records out 4696499200 bytes (4.7 GB) copied, 85.8997 s, 54.7 MB/s 4845497+0 records in 4845497+0 records out 4961788928 bytes (5.0 GB) copied, 91.1265 s, 54.4 MB/s 5108617+0 records in 5108617+0 records out 5231223808 bytes (5.2 GB) copied, 97.003 s, 53.9 MB/s 5359571+0 records in 5359571+0 records out 5488200704 bytes (5.5 GB) copied, 100.939 s, 54.4 MB/s 5630809+0 records in 5630809+0 records out 5765948416 bytes (5.8 GB) copied, 106.729 s, 54.0 MB/s 5906886+0 records in 5906886+0 records out 6048651264 bytes (6.0 GB) copied, 111.06 s, 54.5 MB/s 6185163+0 records in 6185163+0 records out 6333606912 bytes (6.3 GB) copied, 117.173 s, 54.1 MB/s 6460583+0 records in 6460583+0 records out 6615636992 bytes (6.6 GB) copied, 121.158 s, 54.6 MB/s 6698146+0 records in 6698146+0 records out 6858901504 bytes (6.9 GB) copied, 126.21 s, 54.3 MB/s 7007693+0 records in 7007693+0 records out 7175877632 bytes (7.2 GB) copied, 131.249 s, 54.7 MB/s 7277905+0 records in 7277905+0 records out 7452574720 bytes (7.5 GB) copied, 136.289 s, 54.7 MB/s 7542674+0 records in 7542674+0 records out 7723698176 bytes (7.7 GB) copied, 142.177 s, 54.3 MB/s 7836741+0 records in 7836741+0 records out 8024822784 bytes (8.0 GB) copied, 146.411 s, 54.8 MB/s 8116281+0 records in 8116281+0 records out 8311071744 bytes (8.3 GB) copied, 152.294 s, 54.6 MB/s 8379401+0 records in 8379401+0 records out 8580506624 bytes (8.6 GB) copied, 157.082 s, 54.6 MB/s 8642521+0 records in 8642521+0 records out 8849941504 bytes (8.8 GB) copied, 162.495 s, 54.5 MB/s 8908765+0 records in 8908765+0 records out 9122575360 bytes (9.1 GB) copied, 166.62 s, 54.8 MB/s 9164713+0 records in 9164713+0 records out 9384666112 bytes (9.4 GB) copied, 172.034 s, 54.6 MB/s 9446406+0 records in 9446406+0 records out 9673119744 bytes (9.7 GB) copied, 177.737 s, 54.4 MB/s 9759253+0 records in 9759253+0 records out 9993475072 bytes (10 GB) copied, 181.961 s, 54.9 MB/s 9997762+0 records in 9997762+0 records out 10237708288 bytes (10 GB) copied, 186.789 s, 54.8 MB/s 10000000+0 records in 10000000+0 records out 10240000000 bytes (10 GB) copied, 186.801 s, 54.8 MB/s write complete, syncing reading from: /mnt/cache/test.dd 10000000+0 records in 10000000+0 records out 10240000000 bytes (10 GB) copied, 157.611 s, 65.0 MB/s removing: /mnt/cache/test.dd removed `/mnt/cache/test.dd' Quote Link to comment
peter_sm Posted December 10, 2011 Author Share Posted December 10, 2011 Result of all my drives, looks OK, what I think except disk7 dISK1:WDC_WD15EADS-00R6B0: 10240000000 bytes (10 GB) copied, 99.2064 s, 103 MB/s Disk2:WDC_WD15EADS-00P8B0: 10240000000 bytes (10 GB) copied, 103.945 s, 98.5 MB/s Disk3:WDC_WD10EADS-00L5B1: 10240000000 bytes (10 GB) copied, 115.908 s, 88.3 MB/s Disk4:WDC_WD15EADS-00S2B0: 10240000000 bytes (10 GB) copied, 94.1725 s, 109 MB/s Disk5:SAMSUNG_HD103UJ: 10240000000 bytes (10 GB) copied, 87.7448 s, 117 MB/s Disk6:WDC_WD6400AARS-00Y5B1: 10240000000 bytes (10 GB) copied, 86.1624 s, 119 MB/s Disk7:WDC_WD10EACS-00ZJB0: 10240000000 bytes (10 GB) copied, 133.822 s, 76.5 MB/s Disk8:WDC_WD15EARS-00Z5B1: 10240000000 bytes (10 GB) copied, 105.994 s, 96.6 MB/s cache:ST3500630AS :10240000000 bytes (10 GB) copied, 157.611 s, 65.0 MB/s Quote Link to comment
WeeboTech Posted December 10, 2011 Share Posted December 10, 2011 Disk 7 is a WD EACS only 16MB of cache, those drives are not very speedy. I think they were one of the first 1TB drives to come out. Later on they came out with the EADS which had 32MB of cache. It made a difference. I have a bunch of EACS, I use them for the large DVD rips and they perform find. Oh, when I had my bittorrent client on them they performed like an old dog. and sheesh when partiy was on them it made the whole server slow. Once I moved parity to a 7200 RPM disk, the system got faster and then when I moved to a 32MB cache 7200 rpm bittorrent client I did not even notice I was torrenting. Point is sometimes the model of drive you use for parity can really slow down your system. Chances are if you had a more modern 1tb or 2tb drive as your cache drive you would see it approach 90-120MB/s (but I doubt it would get above 120MB/s). Does your PCI Slot support PCI 2.3 66Mhz? If so, you could use a Promise TX4 in it and realize a 266Mhz bus. Still a drive rarely gets above 120MB/s but you would have bandwidth for another drive or 2. Quote Link to comment
peter_sm Posted December 10, 2011 Author Share Posted December 10, 2011 Hi, My MB -> http://www.gigabyte.com/products/product-page.aspx?pid=3062#ov I have this drive as parity ST31500341AS_9VS4Q71V Quote Link to comment
WeeboTech Posted December 10, 2011 Share Posted December 10, 2011 Can't really tell from the board specs. According to the in the manual, it says 33mhz If you have lspci you can do an lspci -v to see what capabilities may be there. For example, on another machine I noticed this one day. I realized something was different about this board and setup during my benchmarks. I.E. 2 drives doing the DD test ran at full speed with no intervention between them. 01:01.0 Mass storage controller: Promise Technology, Inc. PDC40718 (SATA 300 TX4) (rev 02) Subsystem: Promise Technology, Inc. PDC40718 (SATA 300 TX4) Flags: bus master, 66MHz, medium devsel, latency 72, IRQ 201 I/O ports at df00 I/O ports at dc00 Memory at fdcff000 (32-bit, non-prefetchable) Memory at fdcc0000 (32-bit, non-prefetchable) [virtual] Expansion ROM at fdd20000 [disabled] Capabilities: [60] Power Management version 2 on my other system that has PCI-X I saw this output root@atlas ~ #lspci -v | egrep -i mhz Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 79 Flags: bus master, stepping, 66MHz, medium devsel, latency 32, IRQ 24 Flags: bus master, fast Back2Back, 66MHz, medium devsel, latency 32, IRQ 48 Flags: bus master, fast Back2Back, 66MHz, medium devsel, latency 32, IRQ 52 it's a top performer too. It uses the Supermicro AOC-SATA cards. In the end your cache drive is the only drive on the PCI bus and your speed is appropriate for the configuration. Not sure how it would perform if data is being written to the drives on the motherboard simultaneously. That would be an interesting test. a writeread10gb test to an internal motherboard port while simultaneously doing the test to the cache drive. then a writeread10gb test to a sata port on the PCIe slot while simultaneously doing the test to the cache drive. Quote Link to comment
peter_sm Posted December 10, 2011 Author Share Posted December 10, 2011 Here is a output of lspci -v root@Tower:~# lspci -v 00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge Subsystem: Giga-byte Technology Unknown device 5000 Flags: bus master, 66MHz, medium devsel, latency 32 00:01.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx) (prog-if 00 [Normal decode]) Flags: bus master, 66MHz, medium devsel, latency 99 Bus: primary=00, secondary=01, subordinate=01, sec-latency=68 I/O behind bridge: 0000e000-0000efff Memory behind bridge: fdc00000-fddfffff Prefetchable memory behind bridge: 00000000d8000000-00000000dfffffff Capabilities: [44] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [b0] Subsystem: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx) 00:02.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Graphics Port 0) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 0000d000-0000dfff Memory behind bridge: fd900000-fdbfffff Prefetchable memory behind bridge: 00000000fd600000-00000000fd6fffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot-), MSI 00 Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Capabilities: [b0] Subsystem: Giga-byte Technology Unknown device 5000 Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] #1002 Kernel driver in use: pcieport 00:06.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 2) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 0000c000-0000cfff Memory behind bridge: fdf00000-fdffffff Prefetchable memory behind bridge: 00000000fde00000-00000000fdefffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot-), MSI 00 Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Capabilities: [b0] Subsystem: Giga-byte Technology Unknown device 5000 Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] #1002 Kernel driver in use: pcieport 00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] (prog-if 01 [AHCI 1.0]) Subsystem: Giga-byte Technology Unknown device b002 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 22 I/O ports at ff00 [size=8] I/O ports at fe00 [size=4] I/O ports at fd00 [size=8] I/O ports at fc00 [size=4] I/O ports at fb00 [size=16] Memory at fe02f000 (32-bit, non-prefetchable) [size=1K] Capabilities: [60] Power Management version 2 Capabilities: [70] SATA HBA <?> Kernel driver in use: ahci Kernel modules: ahci 00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller (prog-if 10 [OHCI]) Subsystem: Giga-byte Technology Unknown device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16 Memory at fe02e000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller (prog-if 10 [OHCI]) Subsystem: Giga-byte Technology Unknown device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16 Memory at fe02d000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller (prog-if 20 [EHCI]) Subsystem: Giga-byte Technology Unknown device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17 Memory at fe02c000 (32-bit, non-prefetchable) [size=256] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci_hcd 00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller (prog-if 10 [OHCI]) Subsystem: Giga-byte Technology Unknown device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18 Memory at fe02b000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller (prog-if 10 [OHCI]) Subsystem: Giga-byte Technology Unknown device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18 Memory at fe02a000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller (prog-if 20 [EHCI]) Subsystem: Giga-byte Technology Unknown device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 19 Memory at fe029000 (32-bit, non-prefetchable) [size=256] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci_hcd 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a) Subsystem: Giga-byte Technology Unknown device 4385 Flags: 66MHz, medium devsel Capabilities: [b0] HyperTransport: MSI Mapping Enable- Fixed+ 00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller (prog-if 8a [Master SecP PriP]) Subsystem: Giga-byte Technology Unknown device 5002 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16 I/O ports at 01f0 [size=8] I/O ports at 03f4 [size=1] I/O ports at 0170 [size=8] I/O ports at 0374 [size=1] I/O ports at fa00 [size=16] Capabilities: [70] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Kernel driver in use: ATIIXP_IDE Kernel modules: atiixp 00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller Subsystem: Giga-byte Technology Unknown device 5001 Flags: bus master, 66MHz, medium devsel, latency 0 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (prog-if 01 [subtractive decode]) Flags: bus master, VGA palette snoop, 66MHz, medium devsel, latency 64 Bus: primary=00, secondary=04, subordinate=04, sec-latency=64 I/O behind bridge: 0000b000-0000bfff Memory behind bridge: fd800000-fd8fffff Prefetchable memory behind bridge: fd700000-fd7fffff 00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller (prog-if 10 [OHCI]) Subsystem: Giga-byte Technology Unknown device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18 Memory at fe028000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] HyperTransport Configuration Flags: fast devsel Capabilities: [80] HyperTransport: Host or Secondary Interface 00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Address Map Flags: fast devsel 00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] DRAM Controller Flags: fast devsel 00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Miscellaneous Control Flags: fast devsel Capabilities: [f0] Secure device <?> 00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Link Control Flags: fast devsel 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon 2100 (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Unknown device d000 Flags: bus master, fast devsel, latency 32, IRQ 11 Memory at d8000000 (64-bit, prefetchable) [size=128M] Memory at fdde0000 (64-bit, non-prefetchable) [size=64K] I/O ports at ee00 [size=256] Memory at fdc00000 (32-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 2 Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- 01:05.2 Audio device: ATI Technologies Inc Radeon X1200 Series Audio Controller Subsystem: Giga-byte Technology Unknown device 7919 Flags: bus master, fast devsel, latency 32, IRQ 7 Memory at fddfc000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- 02:00.0 RAID bus controller: Adaptec Serial ATA II RAID 1430SA (rev 02) Subsystem: Adaptec Serial ATA II RAID 1430SA Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at fd900000 (64-bit, non-prefetchable) [size=1M] I/O ports at de00 [size=256] Memory at fda00000 (64-bit, non-prefetchable) [size=1M] Capabilities: [40] Power Management version 2 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting <?> Kernel driver in use: sata_mv Kernel modules: sata_mv 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard Flags: bus master, fast devsel, latency 0, IRQ 40 I/O ports at ce00 [size=256] Memory at fdeff000 (64-bit, prefetchable) [size=4K] Memory at fdee0000 (64-bit, prefetchable) [size=64K] [virtual] Expansion ROM at fde00000 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Mask- TabSize=2 Capabilities: [d0] Vital Product Data <?> Capabilities: [100] Advanced Error Reporting <?> Capabilities: [140] Virtual Channel <?> Capabilities: [160] Device Serial Number 78-56-34-12-78-56-34-12 Kernel driver in use: r8169 Kernel modules: r8169 04:06.0 RAID bus controller: Silicon Image, Inc. SiI 3112 [sATALink/SATARaid] Serial ATA Controller (rev 02) Subsystem: Silicon Image, Inc. SiI 3112 SATARaid Controller Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 20 I/O ports at bf00 [size=8] I/O ports at be00 [size=4] I/O ports at bd00 [size=8] I/O ports at bc00 [size=4] I/O ports at bb00 [size=16] Memory at fd8ff000 (32-bit, non-prefetchable) [size=512] [virtual] Expansion ROM at fd700000 [disabled] [size=512K] Capabilities: [60] Power Management version 2 Kernel driver in use: sata_sil Kernel modules: sata_sil root@Tower:~# Quote Link to comment
WeeboTech Posted December 10, 2011 Share Posted December 10, 2011 Looks like you are in good hands. 4:06.0 RAID bus controller: Silicon Image, Inc. SiI 3112 [sATALink/SATARaid] Serial ATA Controller (rev 02) Subsystem: Silicon Image, Inc. SiI 3112 SATARaid Controller Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 20 http://www.siliconimage.com/products/product.aspx?pid=63 You'll be able to support another drive on there at full speed. Keep in mind the two drives used simultaneously may interact slightly, but your bus speed seems to be at 66mhz, so you can probably get up to 120-135 MB/s out of a modern large drive on the outer tracks. Quote Link to comment
peter_sm Posted December 10, 2011 Author Share Posted December 10, 2011 Did the test of 2 drives ;-) cache: 10240000000 bytes (10 GB) copied, 249.897 s, 41.0 MB/s DISK2: (sdh) 10240000000 bytes (10 GB) copied, 356.91 s, 28.7 MB/s //Peter Quote Link to comment
WeeboTech Posted December 10, 2011 Share Posted December 10, 2011 Hmm, looks like they are sharing bandwidth in the chipset. The block diagram showed that. Is sdh on the motherboard port or the 1430sa? Quote Link to comment
peter_sm Posted December 10, 2011 Author Share Posted December 10, 2011 Hi, I'm not sure right now whar port this is, can I see this in the log file? However I did a new test with disk8 together with cache drive Disk 8 (sdb)10240000000 bytes (10 GB) copied, 338.036 s, 30.3 MB/s EDIT With these 2 test I'm downloading using SABnzb !! Can that affect what you like too see ?? ;-) //Peter Quote Link to comment
WeeboTech Posted December 10, 2011 Share Posted December 10, 2011 Yes, if you have other activity on the array it will affect any form of benchmarking. I'm sure it's possible to tell what drive is on what controller when looking at /dev/disk/by-path, but I do not know how to translate that possibly matching output of lspci -v to ls -l /dev/disk/by-path | grep -v part It's all good, you don't need to stop anything or do any other testing. It was just something that peaked my interest. Quote Link to comment
peter_sm Posted December 10, 2011 Author Share Posted December 10, 2011 I know now that the disk 4 is on my SATA II card & disk8 on MB Going to test this again after ZAB is done Quote Link to comment
Johnm Posted December 10, 2011 Share Posted December 10, 2011 that performed better then I thought it would.. Quote Link to comment
peter_sm Posted December 10, 2011 Author Share Posted December 10, 2011 possibly matching output of lspci -v to ls -l /dev/disk/by-path | grep -v part root@Tower:/boot# ls -l /dev/disk/by-path | grep -v part total 0 lrwxrwxrwx 1 root root 9 2011-12-10 10:25 pci-0000:00:11.0-scsi-0:0:0:0 -> ../../sdb lrwxrwxrwx 1 root root 9 2011-12-10 10:25 pci-0000:00:11.0-scsi-2:0:0:0 -> ../../sdc lrwxrwxrwx 1 root root 9 2011-12-10 10:25 pci-0000:00:11.0-scsi-6:0:0:0 -> ../../sdd lrwxrwxrwx 1 root root 9 2011-12-10 10:25 pci-0000:00:11.0-scsi-7:0:0:0 -> ../../sde lrwxrwxrwx 1 root root 9 2011-12-10 10:25 pci-0000:00:11.0-scsi-8:0:0:0 -> ../../sdf lrwxrwxrwx 1 root root 9 2011-12-10 10:25 pci-0000:00:12.2-usb-0:4:1.0-scsi-0:0:0:0 -> ../../sda lrwxrwxrwx 1 root root 9 2011-12-10 10:25 pci-0000:02:00.0-scsi-0:0:0:0 -> ../../sdg lrwxrwxrwx 1 root root 9 2011-12-10 10:25 pci-0000:02:00.0-scsi-2:0:0:0 -> ../../sdh lrwxrwxrwx 1 root root 9 2011-12-10 10:25 pci-0000:02:00.0-scsi-3:0:0:0 -> ../../sdi lrwxrwxrwx 1 root root 9 2011-12-10 10:25 pci-0000:02:00.0-scsi-8:0:0:0 -> ../../sdj lrwxrwxrwx 1 root root 9 2011-12-10 10:25 pci-0000:04:06.0-scsi-0:0:0:0 -> ../../sdk Quote Link to comment
WeeboTech Posted December 10, 2011 Share Posted December 10, 2011 Sometimes people under rate the potentials / over rate theoretical values. a perfect example is how power supply wattage and ratings has reached such high values. Here our CPU's become more energy efficient, yet Video cards eat up power, and we have consumer hobbyist power supplies in the 1,000 watt range. A PCI card on a 66MHZ bus is almost the speed of a PCIe x1. PCIe X1 is usually rated at 500MB/s but that's a full duplex rating. So it's really 250MB/s in one direction. PCI 2.3 66Mhz bus is rated at 266Mhz with 266MB/s theoretical maximim, Although protocol overhead and handshaking come into play. That's what slows it down compared to PCIe. So for unRAID purposes, a one directional read or write allows it to be quite useful. This was a good explanation. http://www.naplestech.com/shopcart/bus_speeds.asp The promise TX4 is also a good choice for a PCI 2.3 66Mhz bus as it has a small fifo which assists in caching some of the data. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.