Jump to content
XPEnology Community

flyride

Moderator
 View Profile  See their activity

  • Posts

    2,438

  • Joined

  • Last visited

  • Days Won

    127

 Content Type 

Posts posted by flyride

    DSM 6.2 Loader

    in Loaders

    Posted

    20 hours ago, Gigaset said:

    1. BACK-UP YOUR DATA BEFORE ANY UPDATE - Polanskiman has told you a hundred times to do it, JUST DO IT

    2. Go for a Clean Install when moving from 6.1 to 6.2 - I am convinced that it was the Migration option that f*k*d up my system, and not anything to do with the v1.03b loader. The fact that all my network cards are now visible on the DSM and my router without me having to use the extra.lzma is evidence of this.

    3. It has made me think about whether I should move to FreeNAS or to Windows Server 2016 or unRAID or something else - but that is a discussion for another time.

    Good luck.

     

    Thanks for relaying your experience.

    But your comment #3 - let's all not forget that 1.03b development and 6.2 support is still seriously in beta.  If you want stability and lack of problems, stay on 6.1 for now.

    DSM 6.2 Loader

    in Loaders

    Posted

    8 hours ago, filippo333 said:

     

    Agreed, it's worth pointing out that the DS3615xs is based off the regular consumer i3 architecture whereas the DS3617xs is Xeon based. Obviously if you're not using a Xeon of that generation then it's recommended not to use that specific config.

     

    I disagree with this generalization - Xeon does not offer any capabilities that desktop processors do not have. ECC RAM and improved security are Xeon's two main benefits, both which are irrelevant to DSM.  So I would not worry about using DS3617xs with a non-Xeon processor as long as it supported the needed instruction set, which is a function of processor generation, not server vs. desktop.  The final answer for your CPU should be discernible by reviewing the hardware capabilities as described in the Intel Ark pages.

     

    How to summarize all this?  Basically, the DS916/3615/3617 DSM code base, AS COMPILED BY SYNOLOGY, seems to require a Sandy Bridge or later CPU.

    DSM on DS918 appears to use instructions that appeared in Haswell and later, which includes Broadwell, Skylake, Kaby Lake, Coffee Lake, Apollo Lake, Gemini Lake.  The community is still compiling information about exactly which CPU's are supported, so don't assume this list is definitive.

     

    Also note that the embedded Linux kernel for DSM DS916/3615/3617 is v3.10 (even on DSM 6.2) and the DS918 uses v4.4.  This may also turn out to be a threshold for CPU selection.

     

    For hardware transcoding, QuickSync processor extension is required both for Synology native support (via Video Station) or third party (i.e. Plex).  QuickSync capability increases with each processor generation, so even if your processor has QuickSync support, it may not meet the specific requirements of the software you are trying to run.  Also, not every modern processor has QuickSync silicon (no Atoms have it, most desktop processors do, some Xeons do).

     

    In addition to the above, DSM must support QuickSync with kernel drivers, and the required components are only available with DSM on the DS916 and DS918 platforms today.

    • Like 3

    DSM 6.2 Loader

    in Loaders

    Posted · Edited by flyride

    16 hours ago, sarge said:

    I'm new to both XPenology and DSM.  Just got Dell R720XD with dual 6 core CPU's (total of 12 cores, 24 threads) and I'm using Jun's 6.2 bootloader.  Everything seems to be working fine, but I just noticed that in Info Center it is only reporting 4 cores.  I'm assuming this is because the 3617 image is limited to 4 cores?  Install is bare metal.
    Update: Just installed Virtual Machine Manager and it says the host has 6 cores and 16 thread (???) and 32 available vCPU's.  That's not confusing at all.

    So now I'm kind of thinking that Info Center isn't actually looking at what is in the machine, but reporting a static string for what a 3617 should have?

    Any thoughts?

    Info Center reports what it expects on the intended hardware for the image and is not correlated to the actual CPU in the system.  That said I don't think you can use more than 8 cores in DSM, if you have HT and more than 4 cores, disable hyperthreading.

    Progress of 6.2 loader

    in Developer Discussion Room

    Posted

    4 hours ago, kpas said:

    i just installed 3617 with 1.03b loaders

    i found the kernel version is 3.10.105

    but 918p is 4.4

     

    Yes, that is the way Synology is supporting the older CPU's; they are not upgrading the kernel, at least in 6.2.  So if you want a newer kernel, 918 will be the way to go.

    DSM 6.2 Loader

    in Loaders

    Posted

    3 hours ago, typer77 said:

    I am a bit confused. In this upgrade on ESXi, I am using the ISO file as CDROM loader converted from the img file in the v1.03b folder. How about synoboot.vmdk? Where can I find .vmdk file for this upgrade? Thanks in advance!

    Load a vmdk file in a text editor and you will have your answer.

    DSM 6.1.7-15284 Update 2

    in DSM Updates Reporting

    Posted

    - Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 6.1.7-15284U1

    - Loader version and model: Jun's loader v1.02b - DS3615xs

    -  Using custom extra.lzma: NO

    - Installation type: VM - ESXi 6.5.0 U1-7388607

    - Additional comments: REBOOT REQUIRED / No issues with physical RDM and controller pass-through.

    DSM 6.1.7-15284 Update 2

    in DSM Updates Reporting

    Posted

    - Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 6.1.7-15284 Update 1

    - Loader version and model: Jun's Loader v1.02b - DS916

    - Using custom extra.lzma: NO

    - Installation type: BAREMETAL - ASRock J4105-ITX

    - Additional comments: NO REBOOT REQUIRED

    Original DSM (.pat file) from Synology usable?

    in The Noob Lounge

    Posted

    Unless you manually modify them yourself, you will not be using anything other than original PAT files from Synology.

     

    You should read the FAQ and best practices regarding updates.  In short, nobody knows for sure whether an update is going to break XPEnology.  Most folks either wait for someone to report success on a software/hardware platform similar to theirs before applying an update, or have a test system that they don't mind crashing to try it out on prior to committing the production system.

    Extend VM disk for XPEnology

    in Answered Questions

    Posted

    If you are not using DSM to provide storage redundancy, why are you using it in the first place vs. a Linux fileshare or Docker host?

     

    You could theoretically use vSAN to achieve redundancy in the VMWare space (again DSM seems useless at that point).

     

    Like IG-88 says, you can provision on two datastores and the JBOD them together in DSM, but there is no redundancy.

     

    If you have a 1.5TB volume on a 3TB datastore, and you want a 2TB volume on a 3TB datastore, it's not difficult to add space to your VMDK, then use mdadm and btrfs/ext tools to expand the disk from command line.

     

    Another option is to create 2TB VMDK on the 2nd 3TB datastore, convert the volume to a RAID1, expand the 1.5TB VMDK to 2TB, repair which will automatically expand the volume, then drop the member on the 2nd datastore.  You will then have a "critical" RAID1 which is the same as a Basic volume, you then can get rid of the error message with mdadm --grow -n 1 --force /dev/mdX

     

    Two problem with esxi 6.7 - dsm 6.1

    in DSM 6.x

    Posted · Edited by flyride

    I had a similar problem, only way I could get things to work when ANY NIC had jumbo frames was to use E1000.  I pass through my 10GBe card to DSM finally, and that works but I don't have other VM's that need high bandwidth.

     

    A few ESXi questions

    in DSM 6.x

    Posted

    As you found out, for some reason 6.1.7 and ESXi don't work on DS3617 image.  6.1.5 works with DS3617.  DS3615 works with all 6.1.x

     

    I have not used LSI controller before but most LSI components seem to be supported, either natively on DS3617 or via extra.lzma.

     

    You do have the choice to present storage to DSM via 1) virtual drive on datastore, 2) rdm or 3) passthrough controller and drives

     

    A few ESXi questions

    in DSM 6.x

    Posted

    Make the boot disk a SATA drive (add SATA controller, delete IDE controller).

    The boot drive should be the only drive on that SATA controller.

    Make sure you are using the ESXi boot option on the loader.

     

    Then your boot disk should be hidden.

     

    DSM 6.1.7-15284 Update 1

    in DSM Updates Reporting

    Posted

    - Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 6.1.7-15284

    - Loader version and model: Jun's loader v1.02b - DS3615xs

    -  Using custom extra.lzma: NO

    - Installation type: VM - ESXi 6.5.0 U1-7388607

    - Additional comments: REBOOT REQUIRED / No issues with test VM upgrade or production VM with physical RDM and controller pass-through.

    Progress of 6.2 loader

    in Developer Discussion Room

    Posted

    58 minutes ago, IG-88 said:

     

    there is already a skylake in my list (i5-6500) so i guess it will work, if hardware transcoding can be used is a different matter

     

    It works on my Kaby Lake processor, and Skylake/Kaby Lake are basically identical.  I don't have QuickSync model however, so can't address transcoding questions.

×
×
  • Create New...