Jump to content
XPEnology Community

Hostilian

Member
 View Profile  See their activity

  • Posts

    318

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Posts posted by Hostilian

    DSM 6.2 Loader

    in Loaders

    Posted

    13 hours ago, Tattoofreak said:

    Hey guys

     

    I have just installed 1.04b / DS918 / DSM 6.21 on ESXi 6.7.

    Everything seems to be running fine except VMM.

    When I try to set up a vDSM virtual machine I can create it but when I want to start it there is an error message coming up which says I do not have enough RAM to start the VM. 

    I dedicated 4GB of RAM and after the error message I tried to play around with this value without success.

    I ended up by trying to delete the whole vDSM virtual machine but that wasn't even possible anymore. It just gives me an error message that it is not possible to delete the VM but it does not say why.

    Can someone confirm this issue?

    Thank you in advance.

    I had to uninstall the Virtual Machine Manager application - and reinstall - after upping the RAM on one of my test servers..

    Then it worked fine..

    XPenology in a dedicated server

    in DSM 6.x

    Posted

    On 10/17/2018 at 9:32 PM, sylvone said:

    second : is there any way to force Synology assistant to look for a NAS on a specific network to reach my VM through Internet ?

    third : if not, how can I proceed to connect to Xpenology and proceed to the DSM installation ?

     

    Don't bother with Synology Assistant, use a network scanner and put the IP Range (given out by DHCP in the remote site) into it.. Then look for the MAC Addresses you assigned..

    I use NetScan.exe. This used to be free and you can still find the free version (6.2.1 is the latest free version) by doing a Google search..

     

    Very bad network performance on ESXi 6.0

    in DSM 6.x

    Posted · Edited by Hostilian

    It's disk performance in that your disks ARE the bottleneck - in your example..

    You did read that the OP was using one disk per volume, yeah?

     

    I think we can agree that the issues could lie in multiple areas; the disks, the hardware (RAID controller - there are known issues with a particular IBM adapter, for example), the network configuration (not just internally in ESXi - for all of the previous posts) AND/OR the ESXi patch level..

    Very bad network performance on ESXi 6.0

    in DSM 6.x

    Posted

    20 hours ago, MooseMan123 said:

    I just got my virtual NAS setup in ESXi 6.7 with 2 cores of an E3-1270 V2, 2GB of RAM and gave it an E1000E NIC and a vmxnet3 in active/failover (For compatibility, in case one stops working with an update)

     

    I have 3 x 4TB 3.5" disks and a super old 1TB Samsung drive all in SHR and I get around 400MB/s read, 330MB/s write. So this is either fixed, or your guys setup has something wrong. I thought I would post, as this thread could put people off! 

    400MB/s read on 1x E1000E NIC**? That's DISK performance (or at least internal ESXi transfer speeds) - and this thread is primarily about NETWORK performance!!

    The OP also had separate volumes on single disks, where you have a RAID volume across 3 disks - which is obviously quicker..  Not comparing like with like!

    VMWare did fix an AHCI bug since the original post - so that, at least, resolves one issue..

     

     

     

    3615 v 3617

    in DSM 6.x

    Posted

    That's a low power CPU.. Perfect for a NAS..  :)

    I have the 4785T (just got recently)..

     

    All CPUs are 'identified' as i3 4130's on these boxes.. It's hard coded but doesn't affect the speed of your chip..

    I've looked into trying to change it to match what I actually have but can't find where to do it..

     

    As far as upgrade from 3615 to 3617.. Probably not much - but I'm going to do it anyway soon.. Will let you know how I get on.

    CPU upgrade will depend on whether you transcode or not.. If you don't transcode, don't bother upgrading...

    FYI.. What that CPU will limit you in is using the DS918+ image.. It's not supported (doesn't work - you won't get an IP address)..

    DSM 6.2 Loader

    in Loaders

    Posted

    45 minutes ago, Jamzor said:

     

    Hi!

    Thanks so much for answering. Im right now in the process of doing this so I just sat by the laptop for 20mins waiting for your answer :) Thanks!

     

    It is enough for me to just unplug my 3 drives I have right now in a RAID-5 config, and it will be untouched by any errors that might occur right..?

    And if everything goes successfull I can just ******* down the NAS and plug them in again and it is ready to go with my old volume working?

    If unsuccessful I can just put the old USB back with the loader etc that Im running right now and plug the disks back and its back to this state at the moment..?

     

    Edit: also my CPU is 7th gen kaby lake if Im not mistaken. Its a intel g4560 . So not ivy Bridge. So it should be compatible with the DS918+, just the ethernet controller that I need to hope for right?

     

    No worries.. Yes, if you UNPLUG all your current drives and use a different hard drive AND USB flash drive, your existing configuration will be untouched..

     

    You will be able to reconnect them and plug in your current flash drive and it will go back to the way it was..

    Just remember to change back any BIOS changes you make (if any)..

     

    Yep, sounds like Ethernet will be the only concern..

    • Thanks 1

    DSM 6.2 Loader

    in Loaders

    Posted

    19 minutes ago, Jamzor said:

     

    So what exactly determines if hardware support is good for ds918?

    is it just CPU and NIC card on the motherboard? I have a intel g4560 and MSI B250I-Pro which has the

    Realtek RTL8111H Gigabit LAN controller

     

    I guess it will fail because not an intel ethernet controller? 

    The drivers in the loader, I guess..

    There are some realtec drives included in 1.04b..
    Disconnect your hard disks, put a temporary hard disk in and give it a test, using a different USB drive..

     

    CPU support is definitely a concern though.. It simply refused to work on my Ivy Bridge i7 when using ESXi..

    I changed the CPU to a Haswell (i7 4785T) and it worked first time (on a new Motherboard, obviously).. 4th Gen is minimum CPU requirement..

    • Like 1

    DSM 6.2 Loader

    in Loaders

    Posted

    1 hour ago, knopserl said:

    I run my DSM with VMware and changed from DS3615 to DS3617 using DM 6.2 and Jun's BL 1.03b. I observe, that newest version are released first for the DSM918+.

    I have tested DSM918+ on VMware 14 with Jun's BL 1.04b and it works with DM 6.2.1, but for "productive" usage, I'm still on DS3617 with DS6.2 and BL 1.03b.

    No my question to the experts of this forum: Is it recommeneded to switch from DS3615/17 to DS918+ as it's based on newer HW (I use a N4200 Apollo lake CPU in my VMware machine)? 

    Do you see June focus more on the DS918+ rather than the older DS3615/17?  

    I think it's a no-brainer to move to DS3617 - if you're on 3615 and your hardware supports it..

    However, moving to DS918 is up for discussion..  It has got a newer kernel version (4.4.x) rather than the 3615's 3.10.x..

    Transcoding? I don't transcode. I'm not sure what the point is other than to make your CPU work it's ass off - I just stream in whatever the native format is..

     

    Benchmarking your synology

    in Tutorials and Guides

    Posted

    Since there have been some reports of a few complaints about performance on the new 1.04b - 6.2.1 loader - I thought I'd look into a simple benchmark for Synology..

    There are other threads using movie conversions (and another one that uses dd for file transfer benchmark) but I wanted something quick and easy for a CPU test - with no installation..

     

    Turns out you can use DD to do both..

    Connect to the Synology using SSH, and run the following..

     

    CPU..

    dd if=/dev/zero bs=1M count=1024 | md5sum

    (it basically gives it a CPU intensive task to do - good enough for a rough guide)

     

    Question I have, if anyone's familiar, which disk does the dev/zero reside on? Is it in RAM or is it any and all of the disks in my machine as the system partition is synched to each disk?

    If it happens to use a HDD, rather than a SSD, what difference does that make and can we specify a different location (if disk is a bottleneck for this test)?

     

    DISK.. (I needed to use Sudo for this)

    sudo dd bs=1M count=256 if=/dev/zero of=/volumeX/share/testx conv=fdatasync

     

    Where volumeX/share is the volume and share you want to copy the file to.. It's case sensitive..

     

    Be careful!  :)

     

     

     

    Not sure if it tests using all cores (the second VM tested had 4 CPUs as opposed to 2)

    Now, the 1st of these machines is under load (web cams) but it gives a rough idea!  :)

     

    For two bare metal machines I have..

    1.. J3455-ITX on DSM 6.2.1 DS918+ . 12GB.

    CPU = 217MB/s average  (its under load, slightly)

    Disk = 146MB/s to HDD, 347MB/s to SSD.

     

    2.. i3 4130 on Asus H87i-plus DSM 6.2U2 DS3617. 8GB

    CPU = 663 MB/s

    Disks later

     

    2 Syno 'test' VMs running on ESXi..

    3. ESXi with i7 3770s on ASus P8z77v-pro DSM 6.21 DS3617. 16GB

    Both had CPU = 630MB/s

    Disks later but a quick test showed me I had an issue with one of my drives..

    ESXi and Etherchannel / LACP - Vcenter

    in DSM 6.x

    Posted

    OK.. Some info for those that want to set up Etherchannel or Trunking between ESXi and an HP (or cisco) switch..

    Not strictly Synology related - but I'm looking to host at least 2 syno boxes in ESXi, possibly 3, so need the throughput!

     

    It's all very well just adding a few uplinks to the vSwitch but you simply don't get the desired throughput until you set this up (tested by copying files to 2 separate vSyno servers from two separate computers).. Without link aggregation you get approximately  113/2 MB/s per computer.. WITH link aggregation/etherchannel, you get 110 each..

    Oh and (in DSM) 'Adaptive Load Balancing' as a Bond Method is next to useless (apart from redundancy)..

     

    HP Switch<>ESXi

    Set up a TRUNK (using the GUI) with the switchports you're using. Just go into the configuration of each port and change it from 'access' to 'trunk', there isn't a separate section for Trunking..

    Don't use LACP as it won't work with Standalone ESXi.

     

    OR

     

    cisco Switch<>ESXi

    Set up an etherchannel port group containing the switchports you want..

     

    AND

     

    ESXi config..

    vSwitch - Route based on IP hash for the NIC teaming, with notify switches set to Yes..

    VMNetwork - take settings from vSwitch..

     

    Hope this helps,

     

    #H

    DSM 6.2.1-23824 Update 1

    in DSM Updates Reporting

    Posted

    - Outcome of the installation/update: SUCCESSFUL

    - DSM version prior update: DSM 6.2 U1 (on DS3617)

    - Loader version and model: JUN'S LOADER v1.04b - DS918+

    - Using custom extra.lzma: NO

    - Installation type: Upgrade from another DSM model, using a new loader - because I'm crazy...  J3455-ITX with 12GB RAM. 2x SSD and 1xHDD..

    - Additional comments: Took a long time, compared to others and it was basically a fresh install (it didn't really work as an upgrade)..

    I had my config backed up and Surveillance station camera config (and others) backed up, so it was relatively straight-forward to restore..

    Data was never at risk (not that there was anything that was irreplacable)..

    Top tip.. If you have LACP set up on a network BOND, plug the cables into a non-LACP enabled port until the 'upgrade' is finished (change them as needed) OR break the Bond and change your switch config before the upgrade..

    DSM 6.2 Loader

    in Loaders

    Posted

    17 hours ago, waazdakka said:

    @Polanskiman I assume it's stupid to think about moving from DS3615 to DS918 to get the last loader ? (Or have to make a fresh install ;) )

    Not only that but you get a much more recent Kernel.. 4.x as opposed to 3.x..

    Annoying as it's not going to work on my Ivy Bridge ESXi.. It needs Haswell or later..

     

    I'd test the upgrade using another hard drive and different flash drive first though..  (Disconnect all your currrent HDDs and don't use your current USB stick..)

     

     

    DSM 6.2 Loader

    in Loaders

    Posted · Edited by Hostilian

    Anyone got 1.04b working in ESXi yet?

    Not seeing the network..

    Tried BIOS and UEFI.. e1000 NIC..

    Actually, do I need a certain CPU? 4th gen+ is it?

    Works fine in Vmware Workstation though - same image..

    DSM 6.2 Loader

    in Loaders

    Posted

    6 hours ago, T-REX-XP said:

    Hello @jun,  thanks for the update. But HW transcoding still not working on j3455 CPU. Please see my dmesg.

      log (Reveal hidden contents)

    [  190.503161] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
    [  190.503720] [drm] Finished loading DMC firmware i915/bxt_dmc_ver1_07.bin (v1.7)
    [  190.505257] BUG: unable to handle kernel NULL pointer dereference at           (null)
    [  190.513070] IP: [<          (null)>]           (null)
    [  190.518110] PGD 37631067 PUD 37630067 PMD 0
    [  190.522414] Oops: 0010 [#1] PREEMPT SMP
    [  190.526376] Modules linked in: i915(E+) drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) cfbfillrect(E) cfbcopyarea(E) cfbimgblt(E) drm(E) fb(E) fbdev intel_agp(E) intel_gtt(E) agpgart(E) video backlight button synoacl_vfs(PO) hfsplus md4 hmac r8168(OE) ixgbe(E) igb(E) i2c_algo_bit e1000e(E) vxlan ip6_udp_tunnel udp_tunnel fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq processor cpufreq_stats dm_snapshot dm_bufio crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram sg etxhci_hcd rtc_cmos(E) mdio(E) mpt3sas(E) raid_class(E) scsi_transport_sas(E) megaraid_sas(E) megaraid(E)
    [  190.598682]  mptctl(E) mptspi(E) mptscsih(E) mptbase(E) scsi_transport_spi(E) megaraid_mbox(E) megaraid_mm(E) vmw_pvscsi(E) BusLogic(E) usb_storage xhci_pci xhci_hcd usbcore usb_common pppfxm(OE) [last unloaded: apollolake_synobios]
    [  190.618236] CPU: 1 PID: 6613 Comm: insmod Tainted: P           OE   4.4.59+ #23824
    [  190.625742] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J3455-ITX, BIOS P1.60 01/16/2018
    [  190.635227] task: ffff8800692b2180 ti: ffff880173d44000 task.ti: ffff880173d44000
    [  190.642643] RIP: 0010:[<0000000000000000>]  [<          (null)>]           (null)
    [  190.650087] RSP: 0018:ffff880173d47950  EFLAGS: 00010202
    [  190.655355] RAX: 0000000000000246 RBX: ffff880179cd31c0 RCX: 0000000000000010
    [  190.662428] RDX: 0000000000000002 RSI: 0000000000000002 RDI: ffff880179cd31c0
    [  190.669502] RBP: ffff880173d47970 R08: 0000000000000000 R09: 0000000000000000
    [  190.676572] R10: 0000000000000001 R11: 0000000000000001 R12: ffff880173d47990
    [  190.683646] R13: 0000000000000002 R14: 0000000000000002 R15: ffff880179cd3ba0
    [  190.690719] FS:  00007ff18eeb6700(0000) GS:ffff88017fc80000(0000) knlGS:0000000000000000
    [  190.698741] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [  190.704435] CR2: 0000000000000000 CR3: 0000000177855000 CR4: 00000000003406f0
    [  190.711512] Stack:
    [  190.713514]  ffffffff8140c419 ffff880179cd31c0 ffff880179cd3000 ffff880179cd31c0
    [  190.720938]  ffff880173d479b8 ffffffffa059da68 ffff880173d479e7 0000000000000000
    [  190.728375]  0000000100000040 ffff880173d4798c ffff001000010040 ffff880173d479d0
    [  190.735810] Call Trace:
    [  190.738249]  [<ffffffff8140c419>] ? i2c_transfer+0x79/0x90
    [  190.743701]  [<ffffffffa059da68>] drm_dp_dual_mode_read+0x58/0x80 [drm_kms_helper]
    [  190.751206]  [<ffffffffa059dcb2>] drm_dp_dual_mode_detect+0x32/0x150 [drm_kms_helper]
    [  190.759026]  [<ffffffffa0683adc>] lspcon_init+0x6c/0x1a0 [i915]
    [  190.764940]  [<ffffffffa066b480>] intel_ddi_init+0x2d0/0x4f0 [i915]
    [  190.771197]  [<ffffffffa0649537>] intel_modeset_init+0x15e7/0x1a70 [i915]
    [  190.777969]  [<ffffffffa0683507>] ? intel_setup_gmbus+0x2e7/0x310 [i915]
    [  190.784645]  [<ffffffffa05beccf>] i915_driver_load+0xa0f/0xe00 [i915]
    [  190.791067]  [<ffffffffa05c9797>] i915_pci_probe+0x27/0x40 [i915]
    [  190.797107]  [<ffffffff812fc85c>] pci_device_probe+0x8c/0x100
    [  190.802813]  [<ffffffff813842d1>] driver_probe_device+0x1f1/0x310
    [  190.808856]  [<ffffffff81384472>] __driver_attach+0x82/0x90
    [  190.814383]  [<ffffffff813843f0>] ? driver_probe_device+0x310/0x310
    [  190.820593]  [<ffffffff81382361>] bus_for_each_dev+0x61/0xa0
    [  190.826204]  [<ffffffff81383d69>] driver_attach+0x19/0x20
    [  190.831561]  [<ffffffff81383993>] bus_add_driver+0x1b3/0x230
    [  190.837183]  [<ffffffffa06fa000>] ? 0xffffffffa06fa000
    [  190.842278]  [<ffffffff81384c7b>] driver_register+0x5b/0xe0
    [  190.847804]  [<ffffffff812fb337>] __pci_register_driver+0x47/0x50
    [  190.853895]  [<ffffffffa06fa03e>] i915_init+0x3e/0x45 [i915]
    [  190.859516]  [<ffffffff810003b6>] do_one_initcall+0x86/0x1b0
    [  190.865139]  [<ffffffff810dfdd8>] do_init_module+0x56/0x1be
    [  190.870672]  [<ffffffff810b61ad>] load_module+0x1ded/0x2070
    [  190.876196]  [<ffffffff810b3510>] ? __symbol_put+0x50/0x50
    [  190.881635]  [<ffffffff810b65b9>] SYSC_finit_module+0x79/0x80
    [  190.887337]  [<ffffffff810b65d9>] SyS_finit_module+0x9/0x10
    [  190.892862]  [<ffffffff81567444>] entry_SYSCALL_64_fastpath+0x18/0x8c
    [  190.899247] Code:  Bad RIP value.
    [  190.902592] RIP  [<          (null)>]           (null)
    [  190.907720]  RSP <ffff880173d47950>
    [  190.911186] CR2: 0000000000000000
    [  190.914479] ---[ end trace 4d4c0a00a6c31297 ]---
    [  191.022715] ------------[ cut here ]------------
    [  191.027300] WARNING: CPU: 1 PID: 6613 at kernel/softirq.c:150 __local_bh_enable_ip+0x65/0x90()
    [  191.035832] Modules linked in: i915(E+) drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) cfbfillrect(E) cfbcopyarea(E) cfbimgblt(E) drm(E) fb(E) fbdev intel_agp(E) intel_gtt(E) agpgart(E) video backlight button synoacl_vfs(PO) hfsplus md4 hmac r8168(OE) ixgbe(E) igb(E) i2c_algo_bit e1000e(E) vxlan ip6_udp_tunnel udp_tunnel fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq processor cpufreq_stats dm_snapshot dm_bufio crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram sg etxhci_hcd rtc_cmos(E) mdio(E) mpt3sas(E) raid_class(E) scsi_transport_sas(E) megaraid_sas(E) megaraid(E)
    [  191.108115]  mptctl(E) mptspi(E) mptscsih(E) mptbase(E) scsi_transport_spi(E) megaraid_mbox(E) megaraid_mm(E) vmw_pvscsi(E) BusLogic(E) usb_storage xhci_pci xhci_hcd usbcore usb_common pppfxm(OE) [last unloaded: apollolake_synobios]
    [  191.127643] CPU: 1 PID: 6613 Comm: insmod Tainted: P      D    OE   4.4.59+ #23824
    [  191.135142] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J3455-ITX, BIOS P1.60 01/16/2018
    [  191.144623]  0000000000000000 ffff880173d47658 ffffffff812b673d 0000000000000000
    [  191.152054]  ffffffff81720af4 ffff880173d47690 ffffffff8104794d 0000000000000201
    [  191.159488]  ffff8800692b2180 ffff8800692b27f8 ffff8800692b2180 ffff880036ec84e8

    Instalation: fresh, baremetal

    MB: Asrock j3455 itx 

    BIOS: 1.6

    Loader: 1.04

    Model: ds 918

    Extra lzma: NO 

     

    Hi.. Where did you get the updated BIOS for your board please?
    Latest on the Asrock website is 1.40 - and I cant seem to access any FTP site where there might be updates...

×
×
  • Create New...