Barrow1990

Hi All, Ive got a DS218+ currently being used as an NVR and want to transfer that to a penology as theres no real data that will be at risk I then want to repurpose the DS218+ to be a photo storage to utilise the synology moments. I only have 3 cameras connected with a purchased license. How would I go about getting it all working on an Xpenology. Or would I be better purchasing another device to ensure smooth transition

Just done this and seems that its not working. Probs just missing something. Here's the output of ls -la /lib/firmware/bnx2/ drwx------ 2 root root 4096 Apr 10 16:57 . drwxr-xr-x 5 root root 4096 Apr 10 16:24 .. -rw------- 1 root root 92824 Apr 10 16:21 bnx2-mips-06-6.2.3.fw -rw------- 1 root root 103904 Apr 10 16:25 bnx2-mips-09-6.2.1b.fw -rw------- 1 root root 5696 Apr 10 16:55 bnx2-rv2p-06-6.0.15.fw -rw------- 1 root root 6104 Apr 10 16:56 bnx2-rv2p-09-6.0.17.fw -rw------- 1 root root 6616 Apr 10 16:57 bnx2-rv2p-09ax-6.0.17.fw and dmesg | grep bnx [ 5.671628] bnx2: QLogic bnx2 Gigabit Ethernet Driver v2.2.6 (January 29, 2014) [ 5.672351] bnx2 0000:02:00.0 eth0: Broadcom NetXtreme II BCM5716 1000Base-T (C0) PCI Express found at mem c0000000, IRQ 16, node addr d4:ae:52:bf:32:84 [ 5.673068] bnx2 0000:02:00.1 eth1: Broadcom NetXtreme II BCM5716 1000Base-T (C0) PCI Express found at mem c2000000, IRQ 17, node addr d4:ae:52:bf:32:85 [ 68.374936] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.36 ($DateTime: 2016/06/16 03:53:41 $) [ 73.729898] bnx2 0000:02:00.0: Direct firmware load for bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2 [ 73.739906] bnx2 0000:02:00.0: Falling back to user helper [ 73.851143] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" [ 73.963230] bnx2 0000:02:00.1: Direct firmware load for bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2 [ 73.972749] bnx2 0000:02:00.1: Falling back to user helper [ 73.979967] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw"

Just got round to installing. Managed to get the server running with APLR with an intel pci card but unfortunately im unable to get the drivers loaded for the Broadcom NetXtreme II BCM5716 Gigabit Nics. Looking through the forums it seems the bnx2/bnx2-mips-09-6.2.1b.fw drivers are broken. If I do the following ssh'd in: dmesg | grep bnx I get the following output: [ 5.058781] bnx2: QLogic bnx2 Gigabit Ethernet Driver v2.2.6 (January 29, 2014) [ 5.059509] bnx2 0000:02:00.0 eth0: Broadcom NetXtreme II BCM5716 1000Base-T (C0) PCI Express found at mem c0000000, IRQ 16, node addr d4:ae:52:bf:32:84 [ 5.060220] bnx2 0000:02:00.1 eth1: Broadcom NetXtreme II BCM5716 1000Base-T (C0) PCI Express found at mem c2000000, IRQ 17, node addr d4:ae:52:bf:32:85 [ 26.645194] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.36 ($DateTime: 2016/06/16 03:53:41 $) [ 30.934069] bnx2 0000:02:00.0: Direct firmware load for bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2 [ 30.943569] bnx2 0000:02:00.0: Falling back to user helper [ 30.980277] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" [ 31.126879] bnx2 0000:02:00.1: Direct firmware load for bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2 [ 31.136387] bnx2 0000:02:00.1: Falling back to user helper [ 31.143637] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" Don't know if anyone can point me in the right direction for getting the correct drivers that work

@vicrod74 Curious on this 1 I have a R210 ii that i thought maybe i could utilise for a Xpenology. How much luck have you got with it?

utcome of the update: SUCCESSFUL - DSM version prior update: 6.1.7-15284 - Loader version and model: Jun's Mod V1.02b - DS3615xs - Using custom extra.lzma: No - Installation type: Baremetal - Gigabyte GA-H61MA-D2V Rev 2.0, i3-2120, 6GB Ram - Additional comments: Reboot Required

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 1 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (Intel DQ670W) - Additional comments: N/A

Question for you guys. What would be the purpose of have such a powerfull PC for XPEnology? I understand for example in the case of Freenas which is RAM hungry and ECC is very highly recommended if not mendatory, but in the case of XPEnology, why would we need more cores or a faster CPU? Why would we need more RAM? Would ECC be better or not? Most people with that hardware go the virtualisation route. So possibly utilise virtualbox or run dsm in esxi/hyper-v

The file sze posted? I get invalid file format

How do i install this or Create the spk file?

Does anyone know how to compile a spk VMware Tools? Sent from my iPhone using Tapatalk Pro

Hi I seem to have a problem where DSM is unaccessible by GUI and the Dockers that are should be running are not available. This is running the v1.02a Bootloader on ESXi 6.0 I can ssh and telnet into the Nas but not visiable through Synology Assistant I read to run sudo cat /var/log/nginx/error.log which has multiple lines of the following. 2017/04/04 14:31:06 [crit] 9487#9487: *21 connect() to unix:/run/synoscgi.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.0.149, server: _, request: "POST /webman/login.cgi HTTP/1.1", upstream: "scgi://unix:/run/synoscgi.sock:", host: "192.168.0.210:5001" Also tried sudo synoservice --start DSM Ive also tried restarting nginx Using a port scanner and see both 5000 & 5001 available. On the serial port of the vm (serial.out) i get the following: [ 494.437583] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff880078a213c0, ffff88007b7c3e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 494.440310] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a213c0, ffffffffa0bef440) failed, ret=-104 [ 494.466552] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff88007d3641c0, ffff880077423e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 494.469878] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff88007d3641c0, ffffffffa0bef250) failed, ret=-104 [ 494.617507] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff880078a83bc0, ffff88007b527e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 494.620294] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a83bc0, ffffffffa0bef620) failed, ret=-104 [ 498.202643] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff880078a213c0, ffff88007b7c3e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 498.205411] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a213c0, ffffffffa0bef440) failed, ret=-104 [ 498.208177] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff88007d3641c0, ffff880077423e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 498.210801] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff88007d3641c0, ffffffffa0bef250) failed, ret=-104 [ 498.433474] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff880078a83bc0, ffff88007b527e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 498.436180] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a83bc0, ffffffffa0bef620) failed, ret=-104 [ 501.920509] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff880078a213c0, ffff88007b7c3e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 501.923177] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a213c0, ffffffffa0bef440) failed, ret=-104 [ 501.942865] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff88007d3641c0, ffff880077423e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 501.945481] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff88007d3641c0, ffffffffa0bef250) failed, ret=-104 [ 501.984353] iSCSI:target_core_rodsp_server.c:721:rodsp_remote_client_login_init errcode(1) [ 501.985716] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a213c0, ffffffffa0bef440) failed, ret=-22 [ 502.004551] iSCSI:target_core_rodsp_server.c:721:rodsp_remote_client_login_init errcode(1) [ 502.005931] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff88007d3641c0, ffffffffa0bef250) failed, ret=-22 [ 502.229572] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff880078a83bc0, ffff88007b527e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 502.232164] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a83bc0, ffffffffa0bef620) failed, ret=-104 [ 502.292824] iSCSI:target_core_rodsp_server.c:721:rodsp_remote_client_login_init errcode(1) [ 502.294213] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a83bc0, ffffffffa0bef620) failed, ret=-22

Hi Ive got this working on ESXi and fully updated (DSM 6.1-15047 Update 2) in which is there a OpenVM tools for this? It was a clean install.

A good majority of the SynoCommunity packages won't work unless you install them on 5.2, and upgrade to 6.0. The reason is that SynoCommunity packages create specific users and groups, a feature that was removed in 6.0 - not entirely removed, but modified in a way that these packages need serious retouching to get them to work again. Further info on the issue here Docker is quite simple to get working. Most of the packages you seem to be using are already available in the LinuxServer.io packages, ready to deploy. Think of each Docker container as an app running in its own chroot. If you need some help, I can give some pointers in private (since this thread is about the loader, not Docker or packages). And the latter part is pure bullshit. Synology implemented Docker for a single reason - it's an industry-leading technology of containerizing stuff. I wouldn't be surprised if they replaced their apps with containers in the future. Will message you when ive had a look more into it then Cheers

The SynoCommunity packages do not work on 6.x, it is not an issue with the DS3617xs. What software do you need? Most probably you'll be able to run the same via Docker (which should be the preferred method any way). Syno Community works fine on dsm 6.x with the DS3615xs. The packages i use are sabnzbd, couch potato, sonarr and the respected dependencies. I tried using docker n couldnt get it to work. Also i read somewhere that the docker wont be working for the near future on DX3617xs. But could try it on Sent from my iPhone using Tapatalk Pro

Hi, Booted a vm on ESXi 6.0 and updated to the latest (DSM 6.1-15047 Update 2). Managed to create a disk (Virtual Only). Was only planning on using it for a downloading client with the SynoCommunity Packages but the packaged arent compiled yet for the new DS3617xs But looks good other than the packages issue. Will shut it down for now untill the packages are available. Also ive not put any MAC addresses in the file and still works fine

I have 2 running as well. Seems to work fine. Sent from my iPhone using Tapatalk Pro

1 of the main reasons for me is to utilise the hardware its on. You dont need loads of power to run a synology. So i can have synology in a vm with pass-through so i can just put it on bare metal and in theory it should just boot fine. But can also run other stuff on the same host Sent from my iPhone using Tapatalk Pro

Update: Decided to have the following set-up: ESXi 6.0 Intel DQ67OW Motherboard 2 x 8GB Corsair Vengeance & 1 x 2GB Kingston (Had Lying about) Dual Port Intel Pro 1000 PCI-E Currently got a SAS3041E-HP and a generic 2 port Sata I have 2x500GB, 2x1TB (SHR on Motherboard sata - Pass-Through) 2x2TB (Raid1 on SAS3041E-HP - Pass-Through) Datastore on generic sata card. My question now is do i put all the hard drives with the same set up in the same vm or separate the 2 disk groups? If i go in same vm i will purchase a better sas card to cope with all he disk drives Sent from my iPhone using Tapatalk Pro

Any update on this. The SPAM is getting worst. Sent from my iPhone using Tapatalk

Ive just got round to having another look. Ive managed to put the raid 1 back in the DS212j and did this https://www.synology.com/en-uk/knowledg ... ogy_NAS#t3. Then put it in my ESXi Server and passthrough to vm and it boots up and finds it. Unsure how to replicate that with the bootloader

I had same issue with ESXi 6 and same DSM. Ended up losing the configuration. Thought mine was due to the fact i took 2 hard drives in raid 1 out of a current set up (4 DIsk SHR1 + 2 Disk RAID 1) and putting that in a vm with the other still powered on (Shut down to remove hard drives). Found 1 of them showed in Synology Assistant as normal and the other was like above. Then i tried to connect to the 1 like above and nothing happened. THen all of a sudden lost everything. SO ended up putting the raid 1 in a DS212j (Which is my backup) and then starting from scratch on the SHR1 on bare metal. Still haven't got round to trying the VM again.

Please could someone recommend me a Sata/SAS Controller. Im looking at putting it in an ESXi as a pass through to Xpenology so what is compatiable? I currently have 4 Sata drives at the moment. But will more than likely add more in the future. Been looking at the following: https://www.ebay.co.uk/itm/272566321934 https://www.ebay.co.uk/itm/122404882531 https://www.ebay.co.uk/itm/371898076806 https://www.ebay.co.uk/itm/162067160068

I have the same problem but with a different card. Think its driver related on the esxi bootloader. Try boot as baremetal on your vm. If it detects it then its just a driver issue. I got around it by doing it this way. Sent from my iPhone using Tapatalk

Im just testing by transferring part of it to a vm. It completely wiped my set up and had to put my backup into a ds212j and reinstall my production 1. All be performance isnt as good now. Think it lost configuration on both. All the more reason to have a back up Sent from my iPhone using Tapatalk

Look that I have no issue seeing them in esxi, or any other vm baring when i load juns esxi vm loader. Even works fine on the baremetal in a vm Sent from my iPhone using Tapatalk