danioj

Members
  • Posts

    1530
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by danioj

  1. Link to post earlier in the thread: http://lime-technology.com/forum/index.php?topic=36749.msg363800#msg363800 ~ 52 Hours (Using Brian's FASTER preclear script).
  2. I am not convinced that this is a downsize at all. I am refreshing my Main Server with an R5 and (based on my other thread which you have been active in) I am going to use Seagate 8TB drives too. I can fit 14 (13 Data + 1 Parity) 3.5 " drives in my R5 plus 1 x 2.5" SSD for Cache and 1 x 2.5" SSD for Apps/VM. I don't want to use an expansion card until I really NEED to so I have bought a Supermicro X10SL7-F board which has 14 Sata ports on it as well as everything anyone else would want from a server board IMHO. See my build thread here for more info and considerations: http://lime-technology.com/forum/index.php?topic=37567.0 Any input you have positive or negative I will appreciate.
  3. 3.5 Pre Clears (I had a power cut in the middle of the first run) and a LONG S.M.A.R.T test at the end - which incidentally is now my default pre deployment drive checking regime. On top of that of course a Parity Sync and then a Parity Check when I configured the Array before any data was copied to the Array. All Good.
  4. I know I am beginning to sound like a one string banjo when it comes to addressing issues and future development of Unraid but I feel I must keep plucking .... Since I have started using v6bx - one of the things I am most disappointed about is that the webGui does not yet provide the full S.M.A.R.T report meaning I have to drop to the command line when I want to get this data as documented in the Wiki (http://lime-technology.com/wiki/index.php?title=Troubleshooting#Obtaining_a_SMART_report). Once again I repeat - LT's position is that they only want and expect the ADVANCED user to drop to the command line (which has been used as an argument for not implementing other features) HOWEVER obtaining a FULL S.M.A.R.T report is essential when dealing with a failing / failed drive which EVERY user of Unraid will experience. Why didn't the implementation of this feature go ALL the way and present the FULL report for download from the GUI? EDIT: changed post for clarity. Post is about the need to obtain AND download a FULL report. When asking for assistance from the community it is almost the first thing that is requested. I do believe even a senior member (not sure which from memory now) has this in their sig to prompt users to do it when there is an issue. Point is - if EVERY user is expected to do it then it should be doable from the GUI.
  5. I haven't done any tests on power consumption - BUT - I am happy to do them if someone shows me how they would like the test to be run and how they want the data to be presented! As for reliability of Seagate (and please ALL remember this is my opinion based on my observations ONLY over the years in an Enterprise and Personal environment) - I don't really subscribe to the whole "Seagate drives always fail and are generally less reliable". Generally my observations have led me to conclude that in the main those who have had drives fail (Seagate or otherwise) inside the warranty of the drive tend to be those who don't adequately "work out" their drives before deploying them OR operate them outside the manufacturers operating conditions (e.g. temperature)! Even I didn't work out my past drives like I've given these bad boys a work out (This is down to me learning some best practices off of the likes of Gaz and Brian). I know that doesn't say anything to their future reliability (albeit these newly learned methods for ensuring a drive passes the infant mortality period have been applied) BUT then again they come with a 3 year warranty. On top of Unraid's fault tollerance I have a COMPLETE backup of my data. ALL Drives WILL Fail, it's just a matter of time - if they do Ill replace them - if they are in Warranty Ill RMA if not I've had my moneys worth! My Data is safe so I am good. I'm quite happy.
  6. I have now posted. 80% in at the time of this post and I am experiencing the same results as I did with the write to the Array of larger files (~40MB/s ) Sorry - have been interstate working! See the thread for the actual data I posted: http://lime-technology.com/forum/index.php?topic=36749.400
  7. My largest file is a 40,275,436 KB (40GB) file which was transferred in the last test I did (and which I monitored) and it transferred in FULL at ~40MB/s.
  8. Update: 80% into the copy: 3.05TB down of ~4TB. (19,000 files of 22,526) so far. Still speeding along at ~40MB/s. In addition - I monitored the copy in the test of the ~4GB files and have done so in this test too. INTERESTING results! Where I saw periodic drops in speed as it reached 100% of 4TB of the larger files I am now seeing INCREASES in speed as it is reaching 4TB of the smaller files up to ~59MB/s. I am certain these speed fluctuations are not material as they do not impact the mean speed of the copy. But I find them interesting all the same. For those who need more evidence: P.S. I am 20% progress (to completion) away from concluding that these drives are FINE for my use in an UNRAUD environment. I have thousands of files all on average between 400MB and 15GB and between two copies of 4TB of sets of both I have experienced NO difference in write or read speed between these Seagate 8TB drives and my existing WD Red 3TB drives. P.P.S. The above also means I am 20% progress (to completion) away from using these drives in the refresh of my Main Server over my planned 6TB WD drives.
  9. Update: 60% into the copy: 2.3TB down of ~4TB. (13,251 files of 22,526) so far. Still speeding along at ~40MB/s.
  10. Hi Guys, back home in Rainy Melbourne Anyway, just started the copy of the "smaller files" going. Another ~4TB made up of 22,526 Files. Started at 0% as always 40MB/s. Will provide periodic updates. Update: 41% into the copy: 1.5TB down of ~4TB. (10,422 files of 22,526) so far. Still speeding along at ~40MB/s.
  11. Hi Guys, back home in Rainy Melbourne Anyway, just started the copy of the "smaller files" going. Another ~4TB made up of 22,526 Files. Started at 0% as always 40MB/s. Will provide periodic updates.
  12. I've had to go away on Business since the 15th in ASP, NT. I didn't set it running because I wouldn't be able to observe. I fly back into MEL on Thursday night AEST and will run it then. Standby.
  13. Just me abreviating Gary. Didn't want to write garycase.
  14. Some further supportive data from an Aussie forum I'm a member of but not active in. http://forums.overclockers.com.au/showpost.php?p=16643176&postcount=139
  15. I agree with your sentiments Once you're past the mortality period. I know other senior hats like Gaz like the Reds better. Rated for longer / better warrenty etc for what you're paying extra they think it's worth it. And I agree - at thier price point (In the US I assume). Here in AUS (at the moment) the price difference is much wider. I run 3TB Reds now (bought when the AUS $ was stronger) and have to say they have been perfect. But for my new Rig I have to consider the Greens (at least when selecting a 6 TB drive) because they are so much cheaper than thier Red counterpart. Couple that with the fact that there is very little "material" difference in the drives AND in my scenario I could "self insure" with an extra Green disk cheaper than what I could buying the required Reds AND I could run WDIDLE3 to set the Greens head parking delay to match the Reds. Decision made for me, but as I note in the thread below " ...it comes down here to what I want to pay for and if the extra $$ is worth the warranty ..." http://lime-technology.com/forum/index.php?topic=39025.0
  16. Yep. I can't say "I agree with Gaz .." Because (while I do), well really, he helped me form the opinion. However, the above setup was selected as a backup server for me. (Which as you can see from above is complete). To be updated, but see my Project thread which shows a build of my replacement Main Server (not yet finished) which is an E12xx build for doing similar to what you mention. http://lime-technology.com/forum/index.php?topic=37567.0
  17. Yep disk 1 was the warmest and what you mention is correct. Fan speeds (the Stock ones) were being reported in the BMI interface running at 1000 RPM. Sorry fellas - there was allot off text. I admit difficult to spot. In summary yes - I setup and run the test on the rig with all filters attached. In short - skirt aside (to manage the airflow) and the subsequent addition of the NF-12's (which as me and Gaz mention was probably an addition that wasn't really required for the sake of an extra 2C) I didn't fiddle with the default configuration of any component.
  18. Last Update for this test: Copy is Complete (It's now doing the testing of the files which I guess you don't need to see). To me "on average" speed was maintained throughout at ~38MB/s. I did sit in front of it for a couple of periods (maybe 20 minutes each time) just to add some observations. I DID notice that every now and then the speed would dip. In my first observation (at around 50%) it dipped in the copying of a file to about 18MB/s but only for a second and went back up to 38-39MB/s. It did this a couple of times. Similarly I just sat in front of it at the end and I observed that the speed dipped this time observed to as low as 2MB/s but again only for a second and then went back to 38-39MB/s. Again it only did this a couple of times in 20 minutes. I have to go to work but Ill let you all draw whatever conclusions you want (and Ill read later). I'll set the copy of the smaller files going tonight and report.
  19. I hope so! Well, after this run I have another share to backup which is of similar size but the files are between 5 and 10 times smaller. Ill post those too if you'd like to see that data.
  20. I found out what it was. Loose cable. All fixed.
  21. Re-Check the thread. https://lime-technology.com/forum/index.php?topic=31967.msg365908#msg365908 I have just completed my C2550D4I build for my backup server: ASRock C2550D4I Mini ITX Motherboard Kingston 4GB (1x4GB), PC-12800 (1600MHz) ECC Unbuffered DDR3L, ValueRAM, CL11, 1.35V, Single Stick Silverstone ST45SF-G 450W SFX Form Factor Power Supply - ST45SF-G 3 x Seagate 8TB Archive HDD, SATA III, 5900RPM, 128MB (in top 3 bays) I am currently filling the 2 8TB data drives (3 in there because 1 is Parity) I have put in it and am having no issues at all. Board came with latest firmware on everything. BMI interface is awesome and the board is a great partner to the DS380 case which with a little air flow management (which I refer to in the thread) is a great case.
  22. Hi Guys, To close off my part of this testing story, the other day I completed a Parity Sync with the new Noctua Fans installed as well as the custom skirt. Here are the results. Disk 1: Start Temperature: 26C, Finish Temperature: 34C, Peak Temperature**: 34C Disk 2: Start Temperature: 27C, Finish Temperature: 31C, Peak Temperature**: 33C Disk 3: Start Temperature: 25C, Finish Temperature: 30C, Peak Temperature**: 32C Motherboard Temperature: 37C CPU Temperature: 36C ** Note that for the peak temperature for this run I checked the temperature exactly half way through (so it might not be the true peak) - best I could do without watching it for hours and hours. To add to the conclusion I stated above - air flow is still the key here. The stock fans did a great job and as I mentioned I was happy and the temperatures were excellent. The Noctua NF-F12's have shaved ~2 degrees off what I recorded before with the stock fans which is always nice. However in my opinion I don't feel ~2 degrees is worth AUD $30 each I paid for them - AUD $90 for 2 degrees, if I hadn't already bought them before I had done the earlier test I wouldn't have done so again!
  23. Further Update: Copy is still going Strong!! Now at 58 percent (2.7 TB) and maintaining 38 - 40MB/s No noticeable slowdown at all so far!
  24. Spot on. I think it will hold too, but time will tell. As for temps, those are with the new Noctuas I installed. I managed to shave another 2-3C off each drive in the DS380. I'll post an update in the DS380 thread.