tjambro

Members
  • Posts

    7
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

tjambro's Achievements

Noob

Noob (1/14)

0

Reputation

  1. That’s how it should be, the sequential read speed slows down as the disk moves from the outer to the inner tracks, I have mostly WD green drives, parity check starts at ~150MB/s and ends at ~80MB/s, average speed in the end is a little over 100MB/s. That makes sense Johnnie, thanks. Reminds me of my laserdisc days with CAV and CLV.
  2. This was the jump I experienced using 8 for nr_requests. I was able to ultimately increase it from 110MB/s to 125-130MB/s by tweaking the md_num_stripes and md_sync_window values from the Disk Settings page. For reference, the default values are: md_num_stripes = 1280 md_sync_window = 384 With my 14 drive array (including parity disk), I used these values: md_num_stripes = 3840 md_sync_window = 1728 You're mileage may vary, but I encourage you to at least experiment with the md_sync_window value to see what you can top out at. I ran the tunables script with just under 105MB/s. With it's settings implemented and the nr 8 settings, I just completed a parity check with an average of 90.6MB/s. It actually started out higher and decreased over time which was surprising to me. Still much better than my last parity check which was around 50 or 55MB/s. Went from 19+ hours to 12:15. I'll take it!
  3. Works here also! I went from starting out about 45MB/s to over 110MB/s. For the novice out there, please note that you do need a space after the "8" and ">" If you don't add the space, you will not get an error message but the command apparently doesn't work. Don't ask me how I know this.
  4. My last parity check took 19:35 hours for an average of 56.7 MB/s. I average about 30 MB/s until the 2.0 TB drives drop out.
  5. Just discovered Dynamix: lime-technology.com/forum/index.php?topic=30939.0....WOW!! It works great on both my servers. I'm quite pleased!
  6. SimpleFeatures is absolutely wonderful and it works great on (1) of my (2) unRaid servers. My newest server worked great but the older one has the exact problem seen in bnevets27's photo...no individual disk usage bars. This holds true for me with FF, Chrome and IE under Win7 and FF under Linux Mint 16. Tried on 2 computers. System Stats works fine. Since the problem server was quite old, I formatted the flash drive and did a clean unRaid install, verified it was working correctly and then re-installed SF hoping to fix the issue but it looks exactly the same. Since there was no response to bnevets27's post, I was hoping to see if anyone has any ideas? Thanks!