Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 11/09/2018 in all areas

  1. When setting up an XPEnology system, you must first select a DSM platform and version. XPEnology supports a few specific DSM platforms that enable certain hardware and software features. All support a minimum of 4 CPU cores, 64GB of RAM, 10Gbe network cards and 12-disk arrays. When you choose a platform and the desired DSM software version, you must download the correct corresponding loader. That may not be the "newest" loader available. The last 6.x version (6.2.4-25556) is functional only with the TCRP loader. TCRP is very different than the Jun loader. If you want to learn more, or if you are interested in deploying the latest 7.x versions, see the 7.x Loaders and Platforms thread. Be advised that installing 6.2.4 with TCRP is basically the same procedure as installing 7.x. Each of these combinations can be run "baremetal" as a stand-alone operating system OR as a virtual machine within a hypervisor (VMWare ESXi is most popular and best documented, but other hypervisors can be used if desired). Review the table and decision tree below to help you navigate the options. 6.x Loaders and Platforms as of 16-May-2022 Options Ranked DSM Platform DSM Version Loader Boot Methods*** Hardware Transcode Support NVMe Cache Support RAIDF1 Support Oldest CPU Supported Max CPU Threads Notes 1,3a DS918+ 6.2.0 to 6.2.3-25426 Jun 1.04b UEFI, BIOS/CSM Yes Yes No Haswell ** 8 6.2.0, 6.2.3 ok, 6.2.1/6.2.2 not recommended for new installs* 2,3b DS3617xs 6.2.0 to 6.2.3-25426 Jun 1.03b BIOS/CSM only No No Yes any x86-64 16 6.2.0, 6.2.3 ok, 6.2.1/6.2.2 not recommended for new installs* DS3615xs 6.2.0 to 6.2.3-25426 Jun 1.03b BIOS/CSM only No No Yes any x86-64 8 6.2.0, 6.2.3 ok, 6.2.1/6.2.2 not recommended for new installs* DS918+ 6.2.4-25556 TCRP 0.4.6 UEFI, BIOS/CSM Yes Yes No Haswell ** 8 recommend 7.x instead DS3615xs 6.2.4-25556 TCRP 0.4.6 UEFI, BIOS/CSM No No Yes any x86-64 8 recommend 7.x instead DS916+ 6.0.3 to 6.1.7 Jun 1.02b UEFI, BIOS/CSM Yes No No Haswell ** 8 obsolete, use DS918+ instead DS3617xs 6.0.3 to 6.1.6 Jun 1.02b UEFI, BIOS/CSM No No Yes any x86-64 16 6.1.7 may kernel panic on ESXi 4 DS3615xs 6.0.3 to 6.1.7 Jun 1.02b UEFI, BIOS/CSM No No Yes any x86-64 8 best compatibility on 6.1.x * 6.2.1 and 6.2.2 have a unique kernel signature causing issues with most kernel driver modules, including those included in the loader. Hardware compatibility is limited. ** FMA3 instruction support required. All Haswell Core processors or later support it. Only a select few Pentium, and no Celeron CPUs do. ** Piledriver is believed to be the minimum AMD CPU architecture to support the DS916+ and DS918+ DSM platforms. *** If you need an MBR version of the boot loader because your system does not support a modern boot methodology, follow this procedure. CURRENT LOADER/PLATFORM RECOMMENDATIONS/SAMPLE DECISION POINTS: 1. DEFAULT install DS918+ 6.2.3 - also if hardware transcoding or NVMe cache support is desired, or if your system only support UEFI boot Prerequisite: Intel Haswell (aka 4th generation) or newer CPU architecture (or AMD equivalent) Configuration: baremetal loader 1.04b, DSM platform DS918+ version 6.2.3 Compatibility troubleshooting options: extra.lzma or ESXi 2. ALTERNATE install DS3617xs 6.2.3 - if RAIDF1, 16-thread or best SAS support is desired, or your CPU is too old for DS918+ Prerequisite: USB key boot mode must be set to BIOS/CSM/Legacy Boot Configuration: baremetal loader 1.03b, DSM platform DS3617xs version 6.2.3 Compatibility troubleshooting options: extra.lzma, DS3615xs platform, or ESXi 3. ESXi (or other hypervisor) virtual machine install - generally, if hardware is unsupported by DSM but works with a hypervisor Prerequisites: ESXi hardware compatibility, free or full ESXi 6.x or 7.x license Use case examples: virtualize unsupported NIC, virtualize SAS/NVMe disks and present as SATA, run other ESXi VM's instead of Synology VMM Option 3a: 1.04b loader, DSM platform DS918+ version 6.2.3 Option 3b: 1.03b loader, DSM platform DS3617xs version 6.2.3 (VM must be set to BIOS Firmware) Preferred configurations: passthrough SATA controller and disks, and/or configure RDM/RAW disks 4. FALLBACK install DS3615xs 6.1.7 - if you can't get anything else to work Prerequisite: none Configuration: baremetal loader 1.02b, DSM platform DS3615xs version 6.1.7 SPECIAL NOTE for Intel 8th generation+ (Coffee Lake, Comet Lake, Ice Lake, etc.) motherboards with embedded Intel network controllers: Each time Intel releases a new chipset, it updates the PCI id for the embedded NIC. This means there is a driver update required to support it, which may or may not be available with an extra.lzma update. Alternatively, disable the onboard NIC and install a compatible PCIe NIC such as the Intel CT gigabit card.
    1 point
  2. List of mirror links to DSM 5.x and DSM 6.x boot loaders. Please drop a comment if you see a broken link or some erroneous information. All other posts will be deleted. Before downloading a loader I suggest you read this topic (for DSM 6.x) or this topic (for DSM 7.x) to know which loader to download. DSM 7.x - Read Flyride topic Tinycore-redpill (TCRP) Releases | Download is straight from Github. Link to code: https://github.com/pocopico/tinycore-redpill OR (the choice is yours) Automated RedPill Loader (ARPL) Releases | Download is straight from Github. Link to code: https://github.com/fbelavenuto/arpl --------
    1 point
  3. Video tutorial on how to get XPEnology to run on an HP Microserver Gen8 via ESXi 6.7, and install DSM 6.2 on SSD drive on ODD port, and pass drivebays to VM with RDM (Raw Data Mapping) MANY Thanx go to the great tutorial already posted here by @luchuma [ Tutorial: Install/DSM 6.2 on ESXi 6.7 ] I just always prefer to watch a video
    1 point
  4. I just wanted to add a brief comment about my build, to let others know that this combination of hardware works. CPU: i5-8400 MB: Asrock H370M-ITX/ac Memory: 8 GB G.Skill Aegis 2666 mhz Disk: 2x 6TB Ironwolf + 2x 2TB Samsung/WD. USB drive: Kingston SE9 8GB Loader: Jun's 1.03b DS3617xs with DSM 6.2.1.23824 update 1. It's running bare metal. Everything in the BIOS is default, except that I changed the boot order to legacy USB (not UEFI). In the DSM, I only have one NIC available, but I haven't tried getting the other one working. I have tried using all 6 SATA slots, and they all work. No issues at all. I have tried migrating from another NAS as well, and that worked. Let me know, if you have any questions.
    1 point
  5. Last time I did an upgrade, I created a new USB with new Jun's loader then I believe I had to go through some upgrade procedure. Is that still the way? I can't seem to find any topic on this specifically. thanks!
    1 point
  6. добыча) взял по случаю ещё и сетевой адаптер для mac и сяоми ми бокс. впереди выходные, наиграюсь...
    1 point
  7. Очень умный совет, аплодисменты. Экранированный вариант кабеля SFTP дает возможность использовать его в более обширных сферах применения благодаря защите от помех. Основным условием для использования такой витой пары является применение соответствующего оборудования. Во время прокладки этого вида кабеля на обоих концах придется использовать оснащение, где есть специальное заземление для экрана. Если нет такого оснащения, помех на этом кабеле окажется еще больше. Он будет работать как своеобразная антенна, которая принимает помехи. Поэтому такой формат кабеля в основном используется для прокладки внутри конкретного здания между серверами. В остальных случаях более удачным вариантом будет применение UTP или FTP кабеля
    1 point
  8. вот тут [синофорум] народ что-то похожее делал через mdadm. полистай, может появятся какие-то мысли/решения. ещё можешь, для профилактики, вытащить его, и прогнать под виндой на Hard Disk Sentinel Pro тест поверхности "disk repair".
    1 point
  9. Hi, Thank's for your answer. Yes I had make this modifications. I just found a good solution: I reinstalled DSM without restoring my configuration, while keeping my data. In fact my system was very unstable, many other bugs. The best solution was to reinstall DSM.
    1 point
  10. под виндой - спокойно читается через UFS Explorer Pro Recovery. а на хрени автоматически - никак не работает. связано это с DSM'овской raid-структурой, которая на всех syno-дисках прописывается. для подключения понадобится немного "потанцевать с бубном". проблема описана в этом топике на сино-форуме. взял с полки винт со старой системой (уже ненужный) и попробовал: TempStation> cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md2 : active raid1 sda3[0] sdb3[1] 971940544 blocks super 1.2 [2/2] [UU] md3 : active raid5 sdc3[0] sde3[2] sdd3[1] 5850889088 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU] md1 : active raid1 sda2[0] sdb2[1] sdc2[2] sdd2[3] sde2[4] 2097088 blocks [5/5] [UUUUU] md0 : active raid1 sda1[0] sdb1[1] sdc1[2] sdd1[4] sde1[3] 2490176 blocks [5/5] [UUUUU] unused devices: <none> TempStation> mdadm -A -R /dev/md9 /dev/sdq3 mdadm: /dev/md9 has been started with 1 drive (out of 2). TempStation> pwd /root TempStation> mkdir my_usb TempStation> mount /dev/md9 /root/my_usb TempStation> cd /root/my_usb/ TempStation> ls @S2S @SYNO.Core.UserS.core @database @synoscgi_______.core @SYNO.Core.DSMNo.core @SYNO.Entry.Requ.core @ffmpeg.core @tmp @SYNO.Core.Deskt.core @SYNO.FileStatio.core @ssrotated.core aquota.group @SYNO.Core.Packa.core @SYNO.Finder.Fil.core @surveillance aquota.user @SYNO.Core.Polli.core @SYNO.Surveillan.core @synocodectool.core synoquota.db @SYNO.Core.Syste.core @appstore @synoelasticd.core чтоб увидеть файло через веб/ftp - монтировать в какую-нить открытую шару. после завершения работы с диском не забыть отмонтировать, чтоб "хвостов" не случилось. TempStation> umount /root/my_usb/ TempStation> mdadm --stop /dev/md9 mdadm: stopped /dev/md9 примечание: запускал на DSM 5.2
    1 point
  11. Back to the Asrock boards: J3455B-ITX: works J3455-M: works J3455-ITX: i915 driver fails which explains why /dev/dri is missing: ===== trigger device plug event ===== [ 219.079271] BUG: unable to handle kernel NULL pointer dereference at (null) [ 219.087187] IP: [< (null)>] (null) [ 219.092288] PGD 1783da067 PUD 1783db067 PMD 0 [ 219.096825] Oops: 0010 [#1] PREEMPT SMP [ 219.100846] 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) 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 imwz(OE) [last unloaded: apollolake_synobios] [ 219.193595] CPU: 3 PID: 6837 Comm: insmod Tainted: P OE 4.4.59+ #23824 [ 219.201196] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J3455-ITX, BIOS P1.80 05/21/2018 [ 219.210792] task: ffff880178b0e240 ti: ffff880072450000 task.ti: ffff880072450000 [ 219.218296] RIP: 0010:[<0000000000000000>] [< (null)>] (null) [ 219.225833] RSP: 0018:ffff880072453950 EFLAGS: 00010202 [ 219.231162] RAX: 0000000000000246 RBX: ffff8800727341c0 RCX: 0000000000000010 [ 219.238322] RDX: 0000000000000002 RSI: 0000000000000002 RDI: ffff8800727341c0 [ 219.245482] RBP: ffff880072453970 R08: 0000000000000000 R09: 0000000000000000 [ 219.252641] R10: 0000000000bc5624 R11: 0000000000000001 R12: ffff880072453990 [ 219.259803] R13: 0000000000000002 R14: 0000000000000002 R15: ffff880072734ba0 [ 219.266962] FS: 00007fb83f4f3700(0000) GS:ffff88017fd80000(0000) knlGS:0000000000000000 [ 219.275077] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 219.280847] CR2: 0000000000000000 CR3: 0000000174ffd000 CR4: 00000000003406f0 [ 219.288006] Stack: [ 219.290031] ffffffff8140c409 ffff8800727341c0 ffff880072734000 ffff8800727341c0 [ 219.297556] ffff8800724539b8 ffffffffa059da68 ffff8800724539e7 0000000000000000 [ 219.305082] 0000000100000040 ffff88007245398c ffff001000010040 ffff8800724539d0 [ 219.312605] Call Trace: [ 219.315076] [<ffffffff8140c409>] ? i2c_transfer+0x79/0x90 [ 219.320594] [<ffffffffa059da68>] drm_dp_dual_mode_read+0x58/0x80 [drm_kms_helper] [ 219.328194] [<ffffffffa059dcb2>] drm_dp_dual_mode_detect+0x32/0x150 [drm_kms_helper] [ 219.336121] [<ffffffffa0683adc>] lspcon_init+0x6c/0x1a0 [i915] [ 219.342121] [<ffffffffa066b480>] intel_ddi_init+0x2d0/0x4f0 [i915] [ 219.348474] [<ffffffffa0649537>] intel_modeset_init+0x15e7/0x1a70 [i915] [ 219.355342] [<ffffffffa0683507>] ? intel_setup_gmbus+0x2e7/0x310 [i915] [ 219.362118] [<ffffffffa05beccf>] i915_driver_load+0xa0f/0xe00 [i915] [ 219.368637] [<ffffffffa05c9797>] i915_pci_probe+0x27/0x40 [i915] [ 219.374761] [<ffffffff812fc85c>] pci_device_probe+0x8c/0x100 [ 219.380537] [<ffffffff813842d1>] driver_probe_device+0x1f1/0x310 [ 219.386654] [<ffffffff81384472>] __driver_attach+0x82/0x90 [ 219.392254] [<ffffffff813843f0>] ? driver_probe_device+0x310/0x310 [ 219.398544] [<ffffffff81382361>] bus_for_each_dev+0x61/0xa0 [ 219.404226] [<ffffffff81383d69>] driver_attach+0x19/0x20 [ 219.409643] [<ffffffff81383993>] bus_add_driver+0x1b3/0x230 [ 219.415324] [<ffffffffa06fa000>] ? 0xffffffffa06fa000 [ 219.420483] [<ffffffff81384c7b>] driver_register+0x5b/0xe0 [ 219.426079] [<ffffffff812fb337>] __pci_register_driver+0x47/0x50 [ 219.432243] [<ffffffffa06fa03e>] i915_init+0x3e/0x45 [i915] [ 219.437926] [<ffffffff810003b6>] do_one_initcall+0x86/0x1b0 [ 219.443608] [<ffffffff810dfdd8>] do_init_module+0x56/0x1be [ 219.449204] [<ffffffff810b61ad>] load_module+0x1ded/0x2070 [ 219.454798] [<ffffffff810b3510>] ? __symbol_put+0x50/0x50 [ 219.460307] [<ffffffff810b65b9>] SYSC_finit_module+0x79/0x80 [ 219.466082] [<ffffffff810b65d9>] SyS_finit_module+0x9/0x10 [ 219.471679] [<ffffffff81567444>] entry_SYSCALL_64_fastpath+0x18/0x8c [ 219.478146] Code: Bad RIP value. [ 219.481540] RIP [< (null)>] (null) [ 219.486723] RSP <ffff880072453950> [ 219.490238] CR2: 0000000000000000 [ 219.493572] ---[ end trace 21ef5019a03d0eeb ]--- [ 219.498323] ------------[ cut here ]------------ I've tried: all official versions of the J3455-ITX BIOS including the newly released 1.80 flashing the J3455B-ITX and J3455-M BIOSs to the board using an external flashing device the J3455B-ITX BIOS booted but for whatever reason said it was a J3355B-ITX and wouldn't get past post saying the CPU didn't match the BIOS. the J3455-M BIOS also booted but the model string was incorrect all combinations of BIOS settings installing 6.2 using 3615 bootloader, then upgrading to 6.2.1 and the 918+ bootloader changing the GPU priority to PCIe and sticking in a PCIe video card All of the above failed It looks like the original release of the 918+ boot loader works on this board so maybe something to do with the newer i915 driver @jun put in?
    1 point
  12. I'm currently working on a new UI with a max. resolution of 850x700px.
    1 point
  13. It looks like compatibility is pretty wide. Synology are using many different chipsets for USB 3.0 The NEC/Renesas seems to be the most popular. I was able to get a Dell ECS U3N2-D Card for $7 used locally, and it works fine
    1 point
  14. Ну, все я спать...какая прелесть на ночь. За 9 лет там от кондеров только названия остались. Меняйте БП и не ипите мозг.
    1 point
  15. Патч-корда тогда S/FTP надо брать, чтобы наверняка ))
    0 points
×
×
  • Create New...