Leaderboard

thats pretty slow, any hardware thats not older then 10 years should be able to use the full bandwidth in xpenology, thats "just" ~110MB/s and most disks sould be able to deliver that when writing large files don't bother about reDDevil, he opened lots of threads about his problem, got help and found out that a mtu of 2000 instead of the 1500 default solved his problem but the reason is unknown and he might going to find out what the cause is that makes a wrong mtu size working better

Gentlemen. Just installed one more xpenology instance and succefully activate ABB but failed to activate ABO and ABG so i dug in my records and get this instructions. This is absolutely the same as OP but i want to point your attention to a few moments: LOGIN FIRST - use uncommented link from my example USE SERIAL NUMBER WITHOUT THE QUOTES Here is mine own manual i created for myself it works for me without any issues. I tried it right now on two more fresh XPENOLOGY installs with ABB ABO ABG latest versions

The script works like a charm, even with today's update to DSM 6.2.3-25426! Thank you a thousand times, @flyride

I would not want to disturb you but... dd without direct option shows only cache speed - no more. In some configurations, you can get a linear speed without a cache higher than with a cache. In some you will receive hundreds of megabytes per second, with linear performance in units of megabytes. With the direct option (iflag = direct for reading, oflag = direct for writing), dd checks only the linear velocity. Which is absolutely not equal to the maximum speed (if we are talking about a raid on many disks, then a raid in several threads can give more speed than in one), not a real performance. link1 link2 So for correct measurement, we need to do a drop cache before testing.