Barrow1990

Members
  • Content count

    30
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Barrow1990

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Barrow1990

    DSM 6.1.7-15284 Update 2

    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
  2. Barrow1990

    DSM 6.1.4-15217 Update 3

    - 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
  3. Barrow1990

    DSM 6.1.x Loader

    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
  4. Barrow1990

    Open-vm-tools v9.4.6 for XPEnology

    The file sze posted? I get invalid file format
  5. Barrow1990

    Open-vm-tools v9.4.6 for XPEnology

    How do i install this or Create the spk file?
  6. Barrow1990

    DS3617xs VMware Tools

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

    Jun's Alpha Loader for DSM 6.1

    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
  8. Barrow1990

    Jun's Alpha Loader for DSM 6.1

    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.
  9. Barrow1990

    DSM 6.1.x Loader

    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
  10. Barrow1990

    DSM 6.1.x Loader

    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
  11. Barrow1990

    DSM 6.1.x Loader

    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
  12. I have 2 running as well. Seems to work fine. Sent from my iPhone using Tapatalk Pro
  13. Barrow1990

    ESXI vs Hyper V & Best Config

    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
  14. Barrow1990

    ESXI vs Hyper V & Best Config

    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
  15. Barrow1990

    Can we change the forum rules?

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