Hostilian

Should do.. It's the CPU that has it embedded and the mobo has a DVI port (and maybe HDMI too)... Not 100% sure it'll work but it looks like it has Intel NICs, so that's a good start.. I'd make sure you have enough PCIE slots to do you; as the mini-atx only have one.. WD-Red for me; every day of the week and three times on Sundays... Cheers

Doesn't the mobo have a built in graphics card? Why purchase another? More expense - and more power utilization.. If I build another, it won't be mini ATX.. Too limited for expansion.. You can either add NICs OR storage, but not both.. Bit of a nightmare if you're using it as an iSCSI endpoint for ESXi.. Micro-ATX maybe but not mini.. I picked up a Dell 9010 optiplex tower for £70 on Ebay a few weeks back (i3 CPU). It works perfectly with DSM 6.1.3 so I'm transferring all my VMWare (and work) stuff to it and leaving my Media on my old box. Job done! .

Ordered this one https://www.amazon.co.uk/dp/B00AZ9T41M?tag=opr-mkt-opr-uk-21&ascsubtag=1ba00-01000-ubp00-def00-other-nomod-uk000-pcomp-feature-scomp-wm-4&th=1 Arrived yesterday, put it into my NAS today.. It just worked. No need to change anything! Thanks again!

How many drives do you have connected as I think that one has a bottleneck of 250MB/sec.. Think there is a PCIe 2.0 one (on same page) for a few quid extra.. So will have a look at that! Thanks for the tip!

Can't see an edit button so should say that it's a Bare Metal install - not in ESXi..

Hi all I am looking at expanding a test 'server' I have and adding a Sata3 controller card. I was wondering if anyone could recommend any please? Needs to be PCIe 2.0 or above and I guess x4 would be preferable.. I guess it depends on the number of ports - I'd need 2 minimum (no more than 4).. The main reason I'm asking if for compatibility with DSM6.1.3.. Yes, they need to work without issues - and preferably no extra drivers required.. Oh, they also need to be cheap - and I would be running normal disks. Not SSDs (for now, anyway).. Anyone tried the Syba or CSL controller cards on Amazon for under £20? Cheers, #H

OK.. Did an update on my test machine 6.1 to 6.1.3. (DS3615xs Intel) Steps.. All done on my workstation, before upgrading my test server to the new 6.1.3 version. -Copy off my grup.cfg as a backup from the USB key I was using (as a backup) the rest of the USB drive contents weren't important. -Use 'Rufus' to copy the new 1.02b loader image to the USB key, overwriting the old loader. -Copied relevant data from my backup grub.cfg to the new grub.cfg on the USB key (which was obviously overwritten when copying the image). (I replaced, vid, pid, mac address etc to suit my test server's previously known working config.) Done on test server. -inserted USB drive and booted. Done on workstation (via browser). -Waited until server was discoverable (I use Netscan) it took a while. It did not default to my previously configured static IP address, at this stage.. -Went to 'new' server IP address and had the option to 'Recover' the box. Took about 5-10 mins and after a reboot the server was back to the previously configured Static IP.. -Connected to the servers static IP address. -Updated to 6.1.3 via the update option on the console. -Reboot Job done.. Currently seeing how stable it is before upgrading my main NAS.. Cheers, H

Intel Pro/1000 PCI-e Gigabit Dual Port LAN Card Should be able to get one for less than 20 quid.. Works great..

Update to 6.1.1 from 6.1 u2 worked fine. My real Synology 216J = OK (as you'd expect) Test server with loader 1.0.2 ds3615 = OK I'll update my Main NAS (loader 1.0.2 ds3615) in a day or two, assuming no issues with the two above.. No, I won't be 'upgrading' to the DS3617 version as my DS3615 installs are working fine - and I value my data, thanks! Plus, for me, there is absolutely no benefit in doing so..

I'll probably go for a consumer rather than server option tbh.. The second one's only PCIE 2.0 x1 - which means it shares 500MB/sec between the four ports (not great, especially for SSDs).. I'm looking PCIE 2.0 x4 minimum (2GB/sec)..

Hey, aye thought so.. Thanks. Even with concurrent access, it would still be better than a physical disk - so should provide some benefit. The problem isn't with buying extra disks - it's SATA interfaces.. I have 6 SATA ports on a Mini-ITX board (all used), which has only one PCIE interface (used by dual port Intel NIC), so the only option might be to get a board with additional PCIE interfaces.. Oh well.. Can anyone recommend a working (with Synology) PCIE SATA3 card please? Preferably PCIE x4 but it depends on the number of ports..

Hi there I'm currently using a 256GB SSD as an SSD Cache on DSM6.1. Turns out I can only use the disk as a cache for ONE volume. Seems like an awful waste. Is there any way to tweak things so I can use a single disk as a cache for two volumes? Even better would be to use the remainder as an additional volume. Possible?

Why is there even a version (here) for DS3617xs anyway?? It's a virtual disk station, on different hardware, so why bother? It's not an actual DS3617 and the OS is the same - DS 6.1. Do you gain anything other than grief trying to make it work - over using the tried and tested DS3615xs?? #H

Virtualbox doesn't work under 6.0.2; you need 6.1 for that.. Which means the newest loader and newest DSM.. #H

There's nothing wrong with 126.6MB/s The (sudo dd) test file created doesn't actually copy anything from one disk to the other. It (from what I understand about it) creates a new file.. So it's not reading anything.. Have you tested this on a different computer (new install on another computer you might have lying around)? It could be an issue with your machine (dodgy drivers).. It looks to be a space-saver PC of some sort? When you're testing anything, please don't use Wifi.. In fact, switch it off and use a cable - until you get to the bottom of the problem.. #H

Of course they can hack back but using Quickconnect with a fake Synology is especially bloody stupid.. Most people use their NAS with the loaders and it happily sits and works without ever contacting the Internet (and definitely not Synology and using their services).. When you use Quickconnect, you are effectively TELLING SYNOLOGY that there are boxes out there with dodgy serial numbers and mac addresses. They'll run a little Quickconnect report that will tell them exactly which boxes are legit or not.. With such a report, they are going to want to do something about it. This is only the start of their fightback.. If you're daft enough to try to use Quickconnect, you could very well kill off this project - maybe even this website.. Nice work...

No way in hell I would EVER expose my NAS onto the Internet in that way.. I would check whether your router supports use of a VPN and use it to access your network..... #H

Yup.. Sounds like the same issue with large files.. I'd check to see if there is a hotfix for your OS and would definitely temporarily disable Windows Defender, if you use it.. Sorry, does it drop to 150Mbps or MBps? Once again, you'll need to say whether its wifi or cabled - as copying 'might' actually copy via your desktop (unless you use the synology GUI to copy it in file manager).. I'd say the same thing here for Windows Defender.. #H

No worries.. #H

Just upgraded my main NAS to 6.1.. Went fine. All configuration settings were retained (that I've checked so far). LACP, SSD Cache, 2x Raid 1 volumes etc all look fine.. The IP address was reset to DHCP on first boot (as found in my testing) but after the package installed and the NAS rebooted, this time, the IP Address went back to what was statically configured. Saved me a step! Updated to update2 without a problem.. Just throwing another SSD in there (that I just found) and I'll get virtualbox installed! edit.. Virtualbox installed with no issues.. Installing a server OS into Virtualbox just now! #H

No. It is correct. I was giving MY methodology. Feel free to give yours.. 1.. It didn't for me, twice - and it was a static IP address on the box previously.. 2.. Do you think I don't know that? I 'chose' to use a new, spare, one (as I wanted the previous flash drive as a backup. It is in Alpha, after all).. 3.. It's an identical model of flash drive so the PID/VID are the same.. 4.. I wanted to install it manually - and I will continue do so so, so I know the file that that gets installed is the one I tested.. #H

Wifi or cabled? If wifi, then those speeds aren't bad.. If cabled, is your WIFI card disabled on your macbook? By 'transfer' do you mean copy and paste or rSync? Are they very large files (4GB +)? Windows 10 sometimes slows right down for large files - especially if you have Windows Defender enabled.. What sort of disks do you have in the Lenovo? Have you tried a baremetal install on another desktop PC? Just incase there's an issue with the Lenovo?

I've done it already, twice, on a test machine I have.. Bare metal DS3615xs.. I used a second, new, USB drive with the new loader on it.. Steps are.. - Shut down existing 6.0.2 NAS. - Insert new USB drive flashed with new 1.02a loader. Settings should be edited as per your original loader for 6.0.x (Pid/vid/Serial number/MAC addresses/Sataportmap etc). I had to move Sataportmap command to the upper line, so it was used.. - Boot to new USB drive on your NAS. Select defaults (or just leave it). - Scan network for new IP address (it doesnt stay the same) and open in browser (I don't use the find synology method). - It will ask you if you want to Migrate or Clean install - choose to Migrate.. - Use (previously downloaded) pat file for 6.1 to update the box (200meg or so).. - Box will update and reboot.. Logon again, set static IP address etc.. - Update to latest patch 2.. - Reboot. - Done!

That line could refer to the fix for the volume issue - not sure of the exact ins and outs though. I'm increasingly willing to risk an upgrade on my main NAS.. I'll keep one eye on the Synology forums though - to see what issues are present.. Cheers #H

FYI.. I have just checked and the 'phantom' volume crash errors are reported on the Official Synology forums - on Synology hardware - for the original 6.1 release. So it looks to be an issue with the release - and not Jun's loader.. Which has now been fixed.. #H