Jump to content
XPEnology Community

boOmLa

Member
  • Posts

    34
  • Joined

  • Last visited

Posts posted by boOmLa

  1. You could run a little benchmark with dd via console. For example:

     

    sudo dd if=/dev/zero of=//testfile bs=1G count=1 oflag=dsync

     

    To remove the testfile aftwards, type:

     

    sudo rm //testfile

     

    Thanks jensmander - Wow - Now this is fast:

     

    2utg2vp.png

     

    What is wrong then when copying from folder to floder on the same SSD volume from the synology GUI ?

     

    9krq6p.png

  2. Hm, could be more but as I mentioned copying files (even on RAID0) from and to the same drive is always slower. Another thing: are these SSDs connected to a real SATA 3.0 (6Gbps) port? Connecting them to older SATA 2.0 ports will cut the bandwith to 50%.

     

    Synology DS916+ have 4 Sata 3 --> 24d3sjl.png

     

    This pic is taken from the specification site (Synology)

     

    Best regards

     

    boOmLa

  3. How do you copy files from one folder to another directly on the NAS? With the FileStation (browser) or do you use your Windows PC (Explorer, TotalCommander, ...) for this? If you copy files with your Windows PC (for example: copying from \\NAS\Share1 to \\NAS\Share2) then everything will be transmitted through your PC. This will lock down speeds to the highest possible throughput of your PC (it reads the data NAS -> PC and retransfers it PC -> NAS) while it will "cut" the bandwith (synchronous transfer, pull and push).

     

    Yeah that is true - I do it thoght through browser (NAS GUI), there should'nt be any speed lim. Don't you allso think it's slow for a RAID 0 to transfer from floder A to Floder B on the same volume with about 150MB/s - considering 1 of those disks runs over 500MB/s read/write ?

     

    Best regards

     

    boOmLa

  4. To copy a file or folder means to duplicate it when you work on the same drive. This is always slower than moving a file or copy it from one disk to another.

     

    Hay jensmander - sounds reasonable enough - thoug shoul'nt it be on fire when running Raid0 ? I mean 1 Samsung 850 SSD alone is cabable of Read: Up to 550MB/s and Write: Up to 520MB/s - and i'am not even near with RAID0 ?? I really Hope I have'nt messed up configuring the disks -

     

    s5y5bm.png

     

     

     

    Best regards

    boOmLa

  5. Hi Hostilian.. I have disabled windows defender with same result- Wifi :smile:

     

    2nu3e3p.png

     

    It drops to 150 MB/s - here it is actually on the Synology GUI - copying a file from one folder to another on the same Raid0 Volume - the Nas is on Cable - in this scenario it dows'nt matter couse everything is happening within the NAS :smile:

     

    Best regard

    boOmLa

  6. Hi Hostilian, thanx for your reply :smile:

     

    So you would mean that these speeds are Ok over wifi ?

    Yes I mean copy / Paste - files over 4Gb

    I have a Samsung 850 SSD 500GB in my lenovo - I have tried the same from synology DS916+ with same speed...

     

    I have another quation - but it's somthing else :smile:

    In my Synology DS916+ I have 2 samsung SSD 850 running Raid0 - when I'am copying files (allso over 4GB) from 1 folder to another on the same Volume i get speeds that start about 280 MBps and the drops to about 150Mbps ... Is that allso normal speed on a Raid0 array ?

     

    Thanx in advanced

     

    boOmLa

  7. Hi all.

    Having a Xpenology running om my baremetal (lenovo M83 tiny) - (Synology DS1916+), and Synology router ac2600. Transfer speed over wifi over LAN to my macbook pro 2016 model (core i7 and 16 Gb ram) is about 30-35 Mbps, have been reading and seeing some videos on youtube transfering much faster some over 100 Mbps ..

     

    Tried allso with other computers (windows 10 ) in the house with the same result - over LAN.. all RJ45 cabels are cat. 6 ...

     

    Can someone clear this up for me ... Thanx in advanced...

     

    Best ragards

     

    boOmLa

  8. Okay, now I'm having the same issue. System set up properly, USB PID and VID matches, serial and MAC matches, aaaand it doesn't work. Nothing on the network. Nothing found by Synology's tool or find.synology.com. Interesting.

     

    Loader is v1.01, with the same USB drive I've been using for months.

     

    try rebooting ur router - had this issue the other day with my Synology DS916+II - after a router reboot I could find it with find.synology.com with no prob.

  9. Wrote a few days ago (pg 225) about running 3617x version of 1.02a and the drive issues.

    Moving over to 3615 and 6.1 (DSM_DS3615xs_15047.pat) worked great.

     

    That said... 5.2 was quite a bit faster on file transfers, and I added a SSD to the mix just to see if it made any difference on 6.1 (knowing for large file transfers it wouldnt).

     

    on 5.2 I was able to consistently max out the 10GB line at 850-950+ MB/sec.

    on 6.1 I get spikes up to about 500, but it nosedives down to 100-150, then perks up to about 200, but not much better

     

    So i'm a bit bummed there because i like 6.x series as my real Syno runs it (yep supported the company as well).

     

    For reference I'm using a LSI9211-8 on a Supermicro X10SDV-4C-TLN2F-O Xeon D-1521 board.

     

    My question is this... Does anyone think that with the new 6.1 drop, that any of the new compiles will make any tangible difference?

     

    Also, anyone know if M.2 SSD might be supported? would be amazing for cache at the 10GB speeds since single SSD is going to max out at 500.

    wow 850-950mbs ? What SSD are you using - i had an Samsung 850 SSD in mine 5.2 and maxed out at 245Mbs - now running Synology DS916+II with 2 Samsung 850 SSD running Raid 0 and peeking at 310 when start transf, a 8GB file from a folder to another and gets down to 145Mbs ..

     

    I would love to hear more about your config - I'am running the Raid0 on btrfs as volume 1 - Had hoped to get much more speed with 2 ssd raid0, but still around 150-145Mbs

  10. Hi all, I have a spare macmini (2012) I'am not using for anything - maybe it's a dumb quas :smile: but have some tried juns loader on a mac - and will it work at all on a mac.

     

    Would be cool to use it as a nas insted of not using it at all :smile:

     

    Thanx in advanced.

    At least there's a post from 2015 which indicates that it used to work with 5.1.

    viewtopic.php?f=7&t=5026&start=60#p29661

     

    So why don't you just go ahead and give it a try?

     

    Edit: Besides, a 2012 Mac Mini would (depending on its hardware configuration) still be worth a few hundred bucks, so you could still sell it and buy some hardware that is much better suited for an Xpenology system, including hard drives.

     

    Thanx for ur fast reply Gex :smile: i will try when i'am get home - yeah ur right about that, maybe i will :smile:

  11. Hi all, I have a spare macmini (2012) I'am not using for anything - maybe it's a dumb quas :smile: but have some tried juns loader on a mac - and will it work at all on a mac.

     

    Would be cool to use it as a nas insted of not using it at all :smile:

     

    Thanx in advanced.

  12. Hey!

    I found out that after doing an Factory Reset, the Error would be gone. Haven't seen it since then. :smile: But it seems like my favorite Apps aren't updated to 6.1 yet :sad: Need an Usenet Downloader, something like SABnbzD or NZBget. Anyone an idea if there's a similar software?

     

    Sounds good for a new fresh install, but otherwize wouldnt it erase alle your data on the drive ? seems like it from what i Read :-|

  13. Anyone knows if it's save to use 6.1 even if there's always this error about crashed drives? I'm about to do a fresh install on my NAS at the moment. But if there will be an updated release in the next days, then i'll wait. If not i'd rather stay on 6.02 a little longer and wait for a "safer" release...

     

    Yes everything works just fine even though after every reboot u'll see this message ...

  14. I tried with force install and it worked, but now, every time my machine boots, this error comes up...

     

    jtdUCAS.jpg

     

    Any ideas?

     

    Same error over here too after each reboot. As a matter of fact, found that on the 6.0.2 the SSD (500GB) 200 of used space after upgrading to 6.1 it shows that 254GB used space - seems like 54Gb puff gone :ugeek:

    Is that the case on your Nas too ?

  15. I've tried migrating to the new alpha, but got this error instead:

     

    "We've detected errors on the hard drives (6), and the SATA ports have also been disabled.

    Please shut down your DS3615xs to replace or remove the hard drives and try again."

     

    I'm using the same SATA configuration as 6.0.2 loader (SataPortMap=4), and I also tried SataPortMap=1, SataPortMap=5 and SataPortMap=6.

     

    No luck.

     

    I´ll try again later today using the forced mode.

     

    Faced the same issue - tried forced mode and seems everything went well :smile:

  16. Just migrated one of my "test" bare metal boxes from jun's v1.01 loader running 6.02-8451 Update 9 to jun's v1.02-Alpha loader running 6.1-15047. Migration to DSM 6.1-15047 completed without error. Testing of packages begins.

     

    Thanks jun.

     

    Hi, is there a step by step to the migration u did, i would like to migrate. I use to clean install running now jun's 1.01 loader dsm 6.02-8451 Update 9.

     

    thanx in advanced ..

     

    I believe there have been others who have written tutorials on migration. Polanskiman has written an excellent migration guide taking you from 5.2 to 6.0. The general idea is the same going from 6.0 to 6.1. http://xpenology.com/forum/viewtopic.php?f=2&t=22100 Please read his turorial. It is an excellent guide.

     

    This is just a quick summary of what I did to perform the migration.

     

    1. I created a new boot thumb drive using jun's v1.02-Alpha loader. I won't go into detail but this means you need to update the vid, pid, s/n, mac, etc. in the grub.cfg file.

    2. I powered down the "test" bare metal box that was running jun's v1.01 loader and DSM 6.02-8451 Update 9.

    3. I powered up the "test" bare metal box with the thumb drive I created in step 1.

    4. After powering up, you can use either Synology Assistant or "find.synology.com" to find your system. If your system is not found then jun's v1.02-Alpha loader doesn't contain a driver for your network card. Go back to your original thumb drive containing jun's v1.01 loader, boot from it and you should be back to DSM 6.02-8451.

    5. If your system is found and you are connected via a web browser, you will be presented with a screen which will step you through the migration of updating the DSM that is installed on your hard drives.

    6. After following the instructions, DSM 6.1 will be downloaded from Synology and your system will reboot.

    7. When it comes up, you should be on DSM 6.1-15047

     

    Caveat, YMMV, my "test" box has an intel cpu and legacy bios, jun's v1.02 - Alpha Loader had the driver for my network card.

     

    Important: Backup your data before trying.

     

    Tahnx alot for your fast reply and clearing things up for me - looking into it now :smile:

  17. Just migrated one of my "test" bare metal boxes from jun's v1.01 loader running 6.02-8451 Update 9 to jun's v1.02-Alpha loader running 6.1-15047. Migration to DSM 6.1-15047 completed without error. Testing of packages begins.

     

    Thanks jun.

     

    Hi, is there a step by step to the migration u did, i would like to migrate. I use to clean install running now jun's 1.01 loader dsm 6.02-8451 Update 9.

     

    thanx in advanced ..

  18. update to 7 fails too.

    also tried update 6 first, exactly the same results.

     

    so, remains update 5 version. waiting for new progress...

     

    BTW: AMD cpu, N54L, ...

     

    Have you tried the upgrade fromthe control panel on the disk station ? Just did the 7'th update and everything went fine and straight forward...

×
×
  • Create New...