Hostilian

Easy... Buy a Synology box.. As far as getting DS3617 to work on that machine, I'm having the same problems.. No joy (so far) on my Optiplex 9010 with DS3617.. DS3615 works fine. By the way, 1.04b is for DS918+ only, AFAIK..

If your storage is already fault tolerant, and it's being backed up, then you could probably just go with a single 'disk' under DSM.. How big are your VMDKs? If the available storage is always wayyyyy bigger than your DSM disk sizes, you could simply create a new disk in VSphere, create a new 'disk' under DSM and move the Share/Data to the new one.. Not sure about expanding disks but rebuilding arrays in DSM seems to take a long damn time.. Apologies for the mini-thread hijack - but it's kind of on topic.. Can someone please explain to me why you'd install DSM in ESXi? It sounds like a recovery nightmare. Not to mention poorer performance over bare metal. Aside from the obvious pro's of virtualisation (having more than one server on the one box) and hardware compatibility; why do it?

You might be able to squeeze an SSD in there too! Assuming there's a SATA port for the CDRom... Can install all the Syno Apps on that drive - more responsive - with a storage partition for important stuff.. I'd give the DS918+ a quick try.. If you don't get an IP address to connect to, give up and try DS3615.. I don't think DS3517 will work at present (I have a similar Optiplex and it just won't work with 6.2.2 on new loaders - with custom extra.lzma.. Though this might change with newer versions!!)..

DS3615xs and 1.03b.. Or possibly the DS918+ loader.. Depends on how many HDD's you want..

Thanks.. Aye, been digging around in there - and had a go at adding drivers for 1.03b for a box I have (e1000e) but it didn't work.. Awaiting your custom.lzma! Have ordered a desktop adapter.. Thanks!

Morning all Wondered if anyone could recommend a GBit PCIE x1 NIC (3.0) that works with DSM 6.2.2+ please? Must be PCIe x1!! DS3617 preferred! Preferably 2 ports, but one will do fine..

Even if it drops to 150, it's still much higher than he's getting - and 'just about above' the limits of most non-SSD drives.. On my 1GB network - despite having LACP etc - files transfer at 111MB/sec; which is maxed-out GB.. Have you tried copying from another computer? Also try using a crossover cable PC<>NAS to rule out problems with the switch (set static IP's obviously).. Try different network cables.. Is it 1000Mb full duplex on all NICs/Interfaces? BIOS updated etc.. Any clanking noises from the drive? 2.5 or 3.5"? Try add-in network card, rather than the integrated one.. How about running a Linux boot USB disk - rather than synology - and trying the file copy to/from the Windows 10 PC.. What about performance when copying files ON the NAS? ie, copy a file to the same volume.. Also to another volume etc. Using the file manager interface.

Good stuff.. Aye, I have a DS918+ too; but it's not suitable for use on my main NAS boxes - so waiting for DS3617/5 extra.lzma then!

Don't suppose you have an updated 1.03b extra.lzma for DS3617 yet please? (that I could test)

Good job! Looking for Intel 82579LM drivers for 1.03b loader - DS3617.. (Might be e1000e) Any plans to add these in - or might anyone have a set of drivers please?

Serial/MAC combination needs to be legit - ie. as on an actual Syno box - or else it's not gonna work.. Have a look in the Synology packages forum for other similar posts.. Bear it in mind - make sure you use Hyperbackup to back up your license (so you can restore it to the box). If your synology dies and you need to rebuild it, your SS licenses will be 'stuck' if you don't..

1000Mb/1Gb. I'm still getting over 100MB/s transfer rates (that's Megabytes)..

Aye, had already tried it.. I think it still tries to go 'online' (at some point) and simply doesn't work.. I might need to go down the dodgy route - or just give them my legit Syno box serial and claim ignorance. But it wasn't registered on that one, so who knows..

OK. Suggestions requred please.. I have a legit SS license that got corrupted on my server when I tried to migrate to a new disk.. Done it before but this time SS reinstalled itself, rather than repair itself, and the license is buggered. Doesn't let me install it again on the same box as there's an issue with the serial.. Tried a different serial - but it says my license is already allocated to another server (yes, my old server's serial).. So.. I'm stuck.. PM me if required, thanks!

Worked fine for my J3455-ITX - though I made my own Extra.lzma.. Powerdown and reboots are fixed too, good job! Should say that I needed to leave it for an awfully long time before getting a ping (and a couple of reboots).. But all was good eventually.. Attached my custom.lzma extra.lzma

- Outcome of the update: SUCCESSFUL - DSM version prior to update: DSM 6.2.1-23824 Update 6 - Loader version and model: Jun v1.04b - DS918+ - Using custom extra.lzma: YES (stripped out drivers) - Installation type: BAREMETAL - J3455-ITX with Intel dual port NIC and spare USB pendrive and a single old hard drive (for testing purposes). - Additional comments: Installed 6.2.1, then update 6. Then upgraded to 6.2.2 (only took 1 reboot but about 4-5 minutes to log on), then updated to update 3.. Update from 6.2.2 to 6.2.2 u3 actually needed 3 reboots!!! I left it about 5-6 minutes after each reboot. OK so it works then! - Doing the same again with my actual nas drives next.. Edit: Completed successfully on my real NAS drives (same server). Now at 6.2.2 update 3. It took a very long time and a few reboots.. My advice, just leave it - for up to 20 mins before rebooting.

Just use the 1.03b loader.. Maybe the image you're using isn't bootable - or it's screwed up in some way. No matter what, you SHOULD get the menu.. https://mega.nz/#!OV4gVKyZ!dCgfXx1bgAOyvbFwFiov3s7RSNoFuqnAcNmSllLoUiw (for DS3615xs) - v1.03b

In linux? Just right click grub.cfg and select open with or edit.. Think I used Linux Mint or Ubuntu.. Handy to have a VM sitting around for various tasks..

- Outcome of the update: SUCCESSFUL - DSM version prior to update: DSM 6.2.2 - Loader version and model: Jun v1.03b - DS3615 - Using custom extra.lzma: No - Installation type: BAREMETAL - Asus H87-i Plus with extra Intel dual port NIC (All three NICs working fine).. - Additional comments: No issues.. Expected it to work as was already on 6.2.2..

Ok so it can boot but do you get the Menu when you boot to the synology drive? If not, theres possibly an issue with how you're editing the IMG file.. Easiest (for me) is to just Rufus the vanilla image to USB then plug it into a linux VM (or machine), mount the partition and edit the grub.cfg directly..

Does it not boot at all to USB or just not boot to a working Syno? Whatever the case, I'd suggest using 1.03b.. Works fine on my DS3615xs.. Also, can you select the boot type? I think I need to use Legacy - rather than UEFI - boot to USB..

It's a basic disk at present - and I thought that if you mirrored the drive, it would be the same size of volume/stroage pool as the existing disk - so I'd be stuck in the same place I am now.. (Although I wouldn't have the original disk I took the clone of, just part of a broken mirror).. Anyway, going to remove a mech disk, add in the SSD, create new SP/Vol and just transfer stuff over to it.. A bit fiddly, TBH...

OK. Cloned the 250GB SSD to a 500GB SSD using the default options in Clonezilla. Worked fine. Able to plug it back into the Syno and boot without an issue. The disk size has been updated to 500GB in DSM. HOWEVER.. The Storage pool and volumes have not increased in size.. They're still sitting around 228GB.. Next Question.. How to I increase the size of the Storage Pool (and then Volume, I guess) to fill this 500GB drive?

As long as the drive's recognised after I put it back in, then yeah, possibility.. Was thinking I could maybe.. -Take out one of the mech disks.. -Add the new SSD in as a RAID1 drive with the current SSD (the one I will be replacing). Let data mirror complete.. - Shutdown then remove the old drive. Switch the new SSD onto the old SSDs SATA port.. - Boot up, should show as degraded.. Break the Mirror by removing any RAID on the disks.. - Shutdown, put original mech disk back in and boot up.. Only thing I'd need to do would be to extend the size of the volume on the new, bigger, SSD.. Doable?

All single disks - no RAID at all on this box.. I don't need fault tolerance on any particular volume as it's only for security cameras..