Leaderboard

edit 14.05.2020: 6.2.3 is back online as v25426, for newer coffeelake cpu's with problems using hardware transcoding (dev/dri present after boot) there is a new videostation that fixes the problem https://xpenology.com/forum/topic/28321-driver-extension-jun-104b-for-dsm623-for-918/?do=findComment&comment=144918 edit2 02.06.2020: as @richv31 pointed out here https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/?do=findComment&comment=148564 there seems to be a serious problem with 918+ and scsi/scs drivers, at least with mpt2sas/mpt3sas, not just with 6.2.2/6.2.3 it also happens with jun's original loader 1.04b and dsm 6.2.0 (23824), breaking raid sets after not properly waking up from hdd hibernation means potential data loss i had a two disk raid1 set on a lsi 9211-8i and after disks spinning down only one came up and i saw some really worrying messages on the serial console, i was not able to log in to the system, not on the web gui, even not on the serial console, the whole system was in lock down and only switching off seemed to work as of the problems with not getting s.m.a.r.t. values i used juns old original raid_class.ko, scsi_transport_sas.ko, scsi_transport_spi.ko to get the old state back (replacing my newly made ones from more recent synology kernel source 24922 ) in 0.11/0.12 - these version inherit the problem that seems to be present since the beginning with loader 1.04b anyone using mpt2sas/mpt3sas and disk hibernation on 918+ should disable it for now to not risk any data loss the new 0.13 for 918+ will have the raid_class.ko, scsi_transport_sas.ko, scsi_transport_spi.ko from kernel source 24922, that version did work on testing on my system without breaking anything and without such alarming errors on wakeup of disks, there will be no smart data but at least it seems safer then disks not waking up properly for "proper" lsi sas controller support i'd suggest using 3615 or 3617 as it is "native" in these units and should work better, maybe there are kernel options missing in the 918+ kernel and that cant be fixed, if anyone finds out more just add a comment (i might not have the time to dig into this) the other alternative is to use sata/ahci instead of scsi/sas with 918+, that works without problems on my system using 918+ (12 disks), JMB585 based controller seem to be the best choice atm as they support pcie 3.0 and can have up to 2000 MByte/s for its 5 sata ports (the older marvell and asm chips use only pcie 2.0 limiting the data rate to 500 MB/s or 1000 MB/s, even 8 port controller with two of the older chips use a pcie bridge chip with just two lanes making them terrible choice for a high port count - might be ok with just one or two 1GBit nic's but will at least limit the rebuild speed and ssd's should be kept away from these controllers and place in internal sata ports) for Instructions about installing or updating please read "Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+" if i have time i will write more in this place the new package is not well tested i just did some tests with hardware i have at hand (ahci, e1000e, r8168, igb, bnx2x, mpt2sas/mpt3sas) and tested update from 6.2.2 to 6.2.3 basically synology reverted the kernel config change made in 6.2.2 back to what was before so old drivers from original 1.04b loader (and older driver i made before 6.2.2) should work again - but as synology also introduced there own new i915 driver with 6.2.3 there will be a conflict when jun's i915 driver is loaded with 6.2.3 there are two positive new things, synology released a nearly recent kernel source code (24922) and 6.2.3 has a new i915 driver supporting as much gpu hardware as jun's backported i915 driver in loader 1.04b - so there is no need for jun's i915 driver anymore and in theory we should have good support for apollo lake, gemini lake and other newer hardware but it seems not all new UHD630 is supported as there is dev id "3E98" unsupported (i5-9400, i5-9600k, i7-9700t, i7-9700), ark.intel.com and wikichip.og are usually good sources to check the id https://ark.intel.com/content/www/us/en/ark/products/134898/intel-core-i5-9400-processor-9m-cache-up-to-4-10-ghz.html https://en.wikichip.org/wiki/intel/core_i5/i5-9400 there is also a good document from intel listing all coffeelake's https://01.org/sites/default/files/documentation/intel-gfx-prm-osrc-cfl-vol01-configurations.pdf coffeelake cup's without driver support (no hardware transcoding), SKU numbers should be listed when buying and can be checked on the box i9 SKU S82 i7 SKU S82 i5 SKU S6f2 a new 10th gen i5-10500 / i3-10300 have device id's "9BC8" and there are no "9xxx" numbers in the driver we use so don't expect any newer gen10 cpu to work with hardware transcoding even when it "only" has UHD630 igpu edit: i made a modded i195 driver were the pci device id of the 9th gen UHD 630 iGPU (3E92) is replaces with the device id's of the newer/different UHD 630 iGPU's that are unsupported 8086:3E92 => iGPU UHD 630, Low End Desktop 9 Series (original driver) -> 8086:3E98 => iGPU UHD 630, High End Desktop 9 Series (i5-9400, i5-9600k, i7-9700t, i7-9700) 8086:9BC8 => iGPU UHD 630, Low End Desktop i5-10500, i5-10600T and lower 8086:9BC5 => iGPU UHD 630, High End Desktop i510600K and higher the zip file contains 3 versions in every one is 3E92 replaced with the one we want to get working, as its just a crude binary patch i choose 3E92 as it seemed the most similar device, was tested for 3E98 iGPU and seemed to work, for the 10th there is at least one positive feedback with plex its intended to be used with the extra/extra2 from this thread as this removes jun's old i915 driver (not just one file) that will prevent synologys new driver to work properly the patched i915.ko file is supposed to be copied to /usr/lib/modules/ and replaces the original file from synology http://s000.tinyupload.com/?file_id=00724045082403681927 - 2nd try same as above but for the new driver in 6.2.3 Update2 http://s000.tinyupload.com/?file_id=60054869936813513844 a little warning, in worst case the system might crash or freeze when transcoding and and such undefined states and hard resets can result i data loss (cache) or damaged raids (depending on the load of the system at this time) so until its more tested it should not be used on system with "important" data and a recent backup - ok i know its a little over cautious but i dont like the thought someone looses data because of this nice to have feature (software mdadm raids can be repaired in most cases if the worst happens) -> positive feedback for a i5-9400, i5-9600K, i9-9900T (8086:3E98) to fully working -> one user positive feedback for a i5-10600T (88086:9BC8) to fully working with plex -> one user negative feedback for a i5-10500 (88086:9BC8) to get /dev/dri devices but no transcoding with emby i completely removed jun's i915 drivers from the extra/extra2 and changed/added the i915 firmware needed, also i took care of the "old" i915 drivers on the installed system in /usr/lib/modules/update/, they are now deleted on boot so if you come from 6.2.2 and used extra/extra2 std or recovery or you did already used juns original 1.04b extra/extra2, it should work as soon as you boot up (when drivers in "update" are not present then the default drivers from synology will be used and with the added i915 in place it will work on most intel gpu's up to coffee lake) the driver versions are the same as in the 6.2.2 extra/extra2 but are newly compiled, as every driver from 6.2.2 is renewed all the old drivers are overwritten and there should be no crashing drivers on boot (which can prevent proper shutdown or reboot) we now have one universal i915 driver (and not jun's and synologys) its back to one package for all cpu/gpu, if needed there will be a recovery version too i only did test a new created loader from 1.04b image file with zImage and rd.gz from "DSM_DS918+_25426.pat" and the new extra.extra2, it will also work with the 6.2.0 kernel that is by default in the 1.04b image if there are problems getting hardware transcoding to work it might help to disable vt-x/vt-d in bios (reported on a J5005 Gemini Lake), but there are other possible reasons because of the licensing thats needed for this to work, but at least it will not hurt as as lon as you dint intent to use the vmm package if you accidentally updated 6.2.2 to 6.2.3 and now have problems like no network after boot, no proper shutdown/reboot or missing /dev/dri (hardware transcoding) then you just copy the new extra/extra2 to your already updated usb drive (the update to 6.2.3 already installed the new kernel on it) with latest updates of win10 there is no drive letter anymore, its possible to still do it with the tools already used for creating the usb drive, read the usb to a imgae file with "Win32DiskImager 1.0" (activate "read only allocated partitions"), mount that image with osfmount (like in the tutorial section), overwrite old /extra/extra2.lzma and write the image back to usb with Win32DiskImager extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13.3 scsi/sas disks will have no s.m.a.r.t. infos (see edit2 above), newer atlantic.ko driver 2.3.4, r8125 added to rc.modules, used latest source for realtek drivers r8101/r8125/r8152/r8168/r8169, bna.ko firmware corrected http://s000.tinyupload.com/?file_id=66035132371971554733 https://gofile.io/d/jy9Q99 for special purpose and tests, extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.12.1 - this version shows s.m.a.r.t. info and serial of disks for lsi scsi/sas but might corrupt the raid when disk hibernation is active (see warning above) http://s000.tinyupload.com/?file_id=00074364916273522754 https://gofile.io/d/h5VBSM extra.lzma for loader 1.03b ds3615 DSM 6.2.3 v0.11_test, same added drivers as for 6.2.2 like newer intel drivers, 10G nics, ... http://s000.tinyupload.com/?file_id=04147311964729253115 https://gofile.io/d/h0Fxvk extra.lzma for loader 1.03b ds3617 DSM 6.2.3 v0.11.2_test, same added drivers as for 6.2.2 like newer intel drivers, 10G nics, ... (0.11.2 because i forgot bnx2/bnx2x firmware and mpt2/mp3 driver problem when updating from 6.2.2 in 0.11) http://s000.tinyupload.com/?file_id=00282289527307524672 https://gofile.io/d/IvGoV3

after testing the loaders 1.03b for 3615 and 1.04b for 918+ with 7.0 preview i'd say that's not the case, the loaders do not work anymore with the kernel of dsm 7.0 jun used a "pre" kernel (bzImage on 1st partition of the loader) that is started by grub and that loads the the synology kernel and i guess that's the point where it fails, the synology kernel is not loaded properly and it fails to start, resulting in dsm not booting (drivers like extra.lzma come later into play) i guess it needs to be the same kernel version to step from a running "pre" kernel into loading a new kernel and as synology changed the base kernel version in all three dsm versions, we have loaders for, it will not work with any of them 3615 3.10.105 -> 3.10.108 3617 3.10.105 -> 4.4.180+ 918+ 4.4.59+ -> 4.4.180+ all loaders throw a va not found Failed to process header on the serial console when booting with the new 7.0 kernel and stop after this (as @OllieD already wrote some days ago https://xpenology.com/forum/topic/33940-dsm-7-preview/?do=findComment&comment=164967) case closed i'd say

NOTE: This problem is consistently manifested when running as a virtual machine, but many have encountered problems with Synoboot devices on baremetal installs of 6.2.3 and under certain conditions, other 6.2.x versions. The fix can be implemented safely on baremetal installs. You can verify if you have the issue by launching SSH and issuing the following command: $ ls /dev/synoboot* /dev/synoboot /dev/synoboot1 /dev/synoboot2 If these files are not present, your Synoboot devices are not being configured correctly, and you should install the fix script. If /dev/synoboot3 exists that is okay. TL;DR: When running DSM 6.2.3 as a virtual machine (and sometimes on baremetal), Jun's 1.03b and 1.04b bootloaders fail to build /dev/synoboot DSM 6.2.3 displays SATA devices (i.e. bootloader on 1.04b) that are mapped beyond the MaxDisks limit when previous versions did not DSM 6.2.3 update rewrites the synoinfo.cfg disk port bitmasks which may break some high-disk count arrays, and cause odd behavior with the bootloader device Background: Setting the PID/VID for a baremetal install allows Jun's loader to pretend that the USB key is a genuine Synology flash loader. On an ESXi install, there is no USB key - instead, the loader runs a script to find its own boot device, and then remakes it as /dev/synoboot. This was very reliable on 6.1.x and Jun's loader 1.02b. But moving to DSM 6.2.x and loaders 1.03b and 1.04b, there are circumstances when /dev/synoboot is created and the original boot device is not suppressed. The result is that sometimes the loader device is visible in Storage Manager. Someone found that if the controller was mapped beyond the maximum number of disk devices (MaxDisks), any errant /dev/sd boot device was suppressed. Adjusting DiskIdxMap became an alternative way to "hide" the loader device on ESXi and Jun's latest loaders use this technique. Now, DSM 6.2.3: The upgrade changes at least two fundamental DSM behaviors: SATA devices that are mapped beyond the MaxDisks limit no longer are suppressed, including the loader (appearing as /dev/sdm if DiskIdxMap is set to 0C) The disk port configuration bitmasks are rewritten in synoinfo.conf: internalportcfg, usbportcfg and esataportcfg and on 1.04b, do not match up with the default MaxDisks=16 anymore (or if you have modified MaxDisks). NOTE: If you have more than 12 disks, it will probably break your array and you will need to restore the values of those parameters Also, when running as a virtual machine (and sometimes on baremetal), DSM 6.2.3 breaks Jun's loader synoboot script such that /dev/synoboot is not created at all. Negative impacts: The loader device might be accidentally configured in Storage Manager, which will crash the system The loader partitions may inadvertently be mapped as USB or eSata folders in File Station and become corrupted Absence of /dev/synoboot devices may cause future upgrades to fail, when the upgrade wants to modify rd.gz in the loader (often, ERROR 21 or "file corrupt") Unpacking Jun's synoboot script reveals that it harvests the device nodes, deletes the devices altogether, and remakes them as /dev/synoboot. It tries to identify the boot device by looking for a partition smaller than the smallest array partition allowed. It's an ambiguous strategy to identify the device, and something new in 6.2.3 is causing it to fail during early boot system state. There are a few technical configuration options can can cause the script to select the correct device, but they are difficult and dependent upon loader version, DSM platform, and BIOS/EFI boot. However, if Jun's script is re-run after the system is fully started, everything is as it should be. So extracting the script from the loader, and adding it to post-boot actions appears to be a solution to this problem: Download the attached FixSynoboot.sh script (if you cannot see it attached to this post, be sure you are logged in) Copy the file to /usr/local/etc/rc.d chmod 0755 /usr/local/etc/rc.d/FixSynoboot.sh Thus, Jun's own code will re-run after the initial boot after whatever system initialization parameters that break the first run of the script no longer apply. This solution works with either 1.03b or 1.04b and is simple to install. This should be considered required for a virtual system running 6.2.3, and it won't hurt anything if installed or ported to another environment. FixSynoboot.sh

https://www.anandtech.com/show/16102/intel-launches-10nm-atom-embedded-cpus-elkhart-lake-now-available https://ark.intel.com/content/www/us/en/ark/products/207909/intel-celeron-processor-j6413-1-5m-cache-up-to-3-00-ghz.html https://ark.intel.com/content/www/us/en/ark/products/207903/intel-pentium-processor-j6425-1-5m-cache-up-to-3-00-ghz.html eight PCIe 3.0 lanes sound good 2 x sata is a little low but vendors could add more 2.5GbE sounds nice but the driver is only in newer kernels and not as single driver source available, so i don't expect it to work for us same goes for the gen 11 gpu, might not work with the "old" i915 we use, no ehl aka elkhart-lake firmware is used in this driver the "In-Band ECC" sounds interesting, having ECC with normal ram's by using some of the ram for ecc (might cost performance but might be a great feature for nas) lets see if synology makes a new ds921+ out of this and just to confuse everyone there is also jasper lake with similar features? https://www.fanlesstech.com/2020/09/exclusive-jasper-lake-lineup.html

Nos liens sont ici : Nativement ton Gen8 n'est pas géré pour la dernière version, ll faudrait : soit investir dans un NIC Intel sur PCI-E soit que tu utilises en plus le fichier FixSynoboot.sh (de nombreuses personnes y sont parvenues , ex https://xpenology.com/forum/topic/31751-dsm-623-25426-update-2/?do=findComment&comment=156973). tu peux suivre ce tuto : https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available/)

I seriously recommend the i3-8100 and the i3-8350 on the used market. They go for very little, "used" is not a scary word when it comes to a CPU. They are super easy to cool, there are tons of inexpensive systemboards you can get for litttle as well. The idle power usage is the same among nearly every model in a given series, so the power costs will be the same as the pentiums you mention. They have exceptional hardware transcoding with no driver fuss if you want to use that (it's amazing if you use it). And they have 4 honest to goodness fast intel cores for muscle when you want to do anthing locally. They also do not rely on turbo mode. Turbo mode may/may not function in xpenology, only base clocks and power saving modes. "Turbo boost is managed by intel_pstate scaling driver, which is not available with the 918+ kernel" The high base clock on the i3 models means they really kick ass compared to the lower end models and frankly some of the higher end models. I ran xpenology servers with i3-8100, i3-8350K, i5-8600k, i5-9600k, and even i9-9900k. The j5040 is not anywhere near as powerful as the others below as it is a pentium "silver" based on the atom core, not the skylake core. Also although it is 4 core, ignoring turbo mode it is only a 2.0GHz CPU consider these CPUs (What you will see without turbo) pentium 6400t 2 cores w HT 4MB cache 2.3/3.4GHz pentium 6400 2cores w HT 4MB cache 4.0GHz i3-8100t 4 cores 6MB cache 2.4/3.1GHz (bios set) i3-8100 4 cores 6MB cache 3.6GHz i3-8300t 4 cores 8MB cache 2.5/3.2GHz (bios set) i3-8300 4 cores 8MB cache 3.7GHz i3-8350K 4 cores 8MB cache 4.0GHz i5-8400t 6 cores 9MB cache 1.2/1.7GHz i5-8400 6 cores 9MB cache 2.8GHz i5-8500t 6 cores 9MB cache 2.1GHz i5-8500 6 cores 9MB cache 3.0GHz i5-8600t 6 cores 9MB cache 2.3GHz i5-8600 6 cores 9MB cache 3.1GHz i5-8600k 6 cores 9MB cache 3.6GHz Then consider that both single thread and multithread are important. In my mind the 8100 is a rock star because you can get them so cheap, say 40$ more that the 6400 used at times. The 8350K is also a standout becasue of the comparitive excellent single core and multi-core performance. The 8600K is the next model I like because the mulithreaded performance is enough over the i3-8350K to finally more than make up for the drop in single core performance. Don't make the mistake of thinking the low end models will save you appreciable money in power, they will not. Neither will the low power models. They don't burn less power to speak of. When you are looking at a nas from a power cost perspective, the most important thing to look at is the idle power usage. Once you add in the power saving script to shedule power savings, every single one of these CPU run at the same 800 MHz, have the same power gate tech, support the same power saving modes etc etc. They idle at the same power usage (or close enough that it doesnt matter) then you look at the relatively rare (for a nas) power burn when the CPU is busy. This is where the lower freq of the T models will burn less power over time. The important thing to remember is that in a NAS your CPU work is fixed, and your T models, being slower, spend a greater amount of time in the high burn mode. The regular CPUs are already back in idle mode while the low power CPU's are still in their high burn mode. So, while its not exactly the same, even when you need to do work, the over all power used is pretty darn closer than you would think when looking at TDP numbers. So, why chose the low power models? Because they are easier to cool. Use can use them in all sorts of places where the heat generated by a high power CPU would overheat or damage near by caps etc. In my opinion, T models are never worth looking at unless you can't use even a small heatsync and fan with at least some airflow. If Turbo mode works ( and the fact I see CPU rates at 36,000,001 means it might) things change a bit.

Daily, there are questions regarding how to select a DSM platform, version and loader, usually after something has been tried that isn't working. This table and decision point example should help navigate the options and current state of the loaders. While situations rapidly change, it should be correct as of the listed date. 6.x Loaders and Platforms as of 11-Aug-2020 Loader DSM Platform DSM Version Kernel Boot Method /dev/dri supported NVMe cache supported RAIDF1 supported Minimum CPU Architecture Max CPU Threads Notes 1.04b DS918+ 6.2 to 6.2.3 4.4.x EFI or Legacy BIOS Yes Yes No Haswell * 8 6.2.0 and 6.2.3 ok, 6.2.1 and 6.2.2 are not recommended for new installs ** 1.03b DS3617xs 6.2 to 6.2.3 3.10.x Legacy BIOS only No No Yes any x86-64 16 6.2.0 and 6.2.3 ok, 6.2.1 and 6.2.2 are not recommended for new installs ** 1.03b DS3615xs 6.2 to 6.2.3 3.10.x Legacy BIOS only No No Yes any x86-64 8 6.2.0 and 6.2.3 ok, 6.2.1 and 6.2.2 are not recommended for new installs ** 1.02b DS916+ 6.0.3 to 6.1.7 3.10.x EFI or Legacy BIOS or MBR (Genesys) Yes No No any x86-64 8 1.02b DS3617xs 6.0.3 to 6.1.6 3.10.x EFI or Legacy BIOS or MBR (Genesys) No No Yes any x86-64 16 6.1.7 fails with kernel panic on ESXi 1.02b DS3615xs 6.0.3 to 6.1.7 3.10.x EFI or Legacy BIOS or MBR (Genesys) No No Yes any x86-64 8 best compatibility on 6.1.x 1.01 DS916+ or DS3615xs or DS3617xs 6.0 to 6.0.2 3.10.x EFI or Legacy BIOS or MBR (Genesys) No No any x86-64 obsolete * AMD Piledriver is suspected to be the minimum chip architecture to support the DS918+ DSM platform, but this is unverified. ** 6.2.1 and 6.2.2 have a unique kernel signature that causes problems with most kernel driver modules, including those included with Jun's loader 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: Haswell (or equivalent) or newer CPU Configuration: baremetal loader 1.04b, platform DS918+ version 6.2.3 Compatibility troubleshooting options: extra.lzma or ESXi 2. ALTERNATE install DS3617xs 6.2.3 - if RAIDF1 or 16-thread support is desired, or your CPU is too old for DS918+ Prerequisite: boot mode (for USB key) set to Legacy Boot/CSM in BIOS Configuration: baremetal loader 1.03b, platform DS3617xs version 6.2.3 Compatibility troubleshooting options: extra.lzma, DS3615xs platform, or ESXi 3. ESXi (or other virtualization platform) virtual machine install - if hardware is unsupported by DSM but works with ESXi Use case examples: virtualize unsupported NIC, virtualize SAS disk or NVMe SSD and access in DSM as SATA, or do not want to use Synology VMM for VMs Prerequisite: ESXi hardware compatibility Configuration: loader/platform/version from options #1 or #2 Preferred disk configurations: passthrough SATA controller (and all connected disks), and/or individual RDM/RAW disks attach to the DSM VM 4. FALLBACK install DS3615xs 6.1.7 - if you can't get anything else to work Prerequisite: none Configuration: baremetal loader 1.02b, platform DS3615xs version 6.1.7

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.03b - DS3615XS - Using custom extra.lzma: NO - Installation type: 2 x BAREMETAL - Dell Optiplex 790 - Additional comments: Reboot required - Outco me of the update: SUCCESSFUL - D SM version prior update: DSM 6.2.3-25426 - Lo ader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BARAMETAL - HP Microserver Gen8 - Additional comment : reboot required | Intel NIC | WOL works | PhpVirtualBox works - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.03b - DS3615XS - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen7 N54L - HP Microserver Gen7 N40L - Additional comments: reboot required | Intel NIC | WOL works | PhpVirtualBox works

not that much if you have a cable on the "receiving" side you can use a usb2serial adapter if the newer system (using putty) does not have a com port you can at least see the difference between not starting because of uefi boot and a driver problem (you would even be able to login into the system without network that way) the settings can be seen in the grub.cfg in the loader (8n1, 115200) testing with loader 1.02b can help to see if its working at all as this one does not depend on csm/legacy mode for just testing to boot you dont need to change anything in the loader (like grub.cfg) the vid/pid of the usb only gets impotant when installing a dsm file to the system, just booting up and check if can be found in network works with the default settings of the loader, if its prooven to boot and found in network you can start changing the vid/pid an maybe use the real mac of the nic (thats only important when using wol, otherwise ts just nice to always see the same mac in network)

На китае нужно кинуть onvif, rtsp, и http тогда все заработает

afair there where people with Asus XG-C100C https://xpenology.com/forum/topic/31751-dsm-623-25426-update-2/?do=findComment&comment=156123 https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/?do=findComment&comment=151119 and also on 1.02b with dsm 6.1 https://xpenology.com/forum/topic/9508-driver-extension-jun-102bdsm61x-for-3615xs-3617xs-916/?do=findComment&comment=81686 as asus is still offering driver 2.0.15 on its website it might be possible to assume that there is no newer hardware for at least two years that would need a newer driver

ax88179_178a.ko ASIX AX88179/178A based USB 3.0/2.0 Gigabit Ethernet Devices Vid : 0B95 Pid : 178A ASIX Electronics Corp. Vid : 0B95 Pid : 1790 AX88179 Gigabit Ethernet Vid : 0DF6 Pid : 0072 AX88179 Gigabit Ethernet [Sitecom] cdc-acm.ko USB Abstract Control Model driver for USB modems and ISDN adapters Vid : 03EB Pid : 0030 Atmel Corp. Vid : 0421 Pid : 0001 E61i (PC Suite mode) Vid : 0421 Pid : 0007 Nokia Mobile Phones Vid : 0421 Pid : 000E Nokia Mobile Phones Vid : 0421 Pid : 002F 6120 Phone (PC-Suite mode) Vid : 0421 Pid : 003A Nokia Mobile Phones Vid : 0421 Pid : 0042 E51 (PC Suite mode) Vid : 0421 Pid : 0070 N95 (PC Suite mode) Vid : 0421 Pid : 0071 Nokia Mobile Phones Vid : 0421 Pid : 007B Nokia Mobile Phones Vid : 0421 Pid : 0088 Nokia Mobile Phones Vid : 0421 Pid : 008F Nokia Mobile Phones Vid : 0421 Pid : 0094 Nokia Mobile Phones Vid : 0421 Pid : 0099 Nokia Mobile Phones Vid : 0421 Pid : 00A0 Nokia Mobile Phones Vid : 0421 Pid : 00AB E71 (PC Suite mode) Vid : 0421 Pid : 00B0 Nokia Mobile Phones Vid : 0421 Pid : 00E9 Nokia Mobile Phones Vid : 0421 Pid : 00E9 Nokia Mobile Phones Nokia Mobile Phones Vid : 0421 Pid : 00FC Nokia Mobile Phones Vid : 0421 Pid : 0108 Nokia Mobile Phones Vid : 0421 Pid : 010E E75 (PC Suite mode) Vid : 0421 Pid : 0128 Nokia Mobile Phones Vid : 0421 Pid : 0134 Nokia Mobile Phones Vid : 0421 Pid : 0154 5800 XpressMusic (PC Suite mode) Vid : 0421 Pid : 0178 Nokia Mobile Phones Vid : 0421 Pid : 01D0 Nokia Mobile Phones Vid : 0421 Pid : 01D4 Nokia Mobile Phones Vid : 0421 Pid : 01F5 Nokia Mobile Phones Vid : 0421 Pid : 0223 Nokia Mobile Phones Vid : 0421 Pid : 026C N97 (PC Suite) Vid : 0421 Pid : 0275 Nokia Mobile Phones Vid : 0421 Pid : 02D9 Nokia Mobile Phones Vid : 0421 Pid : 02E3 5230 (PC-Suite mode) Vid : 0421 Pid : 0302 Nokia Mobile Phones Vid : 0421 Pid : 0335 Nokia Mobile Phones Vid : 0421 Pid : 03CD C7-00 (Nokia Suite mode) Vid : 0421 Pid : 0418 E70 (PC Suite mode) Vid : 0421 Pid : 0419 E60 (PC Suite mode) Vid : 0421 Pid : 0420 Nokia Mobile Phones Vid : 0421 Pid : 0425 Nokia Mobile Phones Vid : 0421 Pid : 042D Nokia Mobile Phones Vid : 0421 Pid : 042F Nokia Mobile Phones Vid : 0421 Pid : 0445 Nokia Mobile Phones Vid : 0421 Pid : 044D E61 (PC Suite mode) Vid : 0421 Pid : 046E 6110 Navigator Vid : 0421 Pid : 0475 Nokia Mobile Phones Vid : 0421 Pid : 0481 Nokia Mobile Phones Vid : 0421 Pid : 0486 Nokia Mobile Phones Vid : 0421 Pid : 048E Nokia Mobile Phones Vid : 0421 Pid : 04B2 Nokia Mobile Phones Vid : 0421 Pid : 04C9 Nokia Mobile Phones Vid : 0421 Pid : 04CE E90 Communicator (PC Suite mode) Vid : 0421 Pid : 04D8 Nokia Mobile Phones Vid : 0421 Pid : 04DF Nokia Mobile Phones Vid : 0421 Pid : 04E6 Nokia Mobile Phones Vid : 0421 Pid : 04F0 Nokia N95 (PC Suite mode) Vid : 0421 Pid : 0508 E65 (PC Suite mode) Vid : 0482 Pid : 0203 AH-K3001V Vid : 04D8 Pid : 000B PIC18F2550 (32K Flashable 10 Channel, 10 Bit A/D USB Microcontroller) Vid : 04E7 Pid : 6651 Elo TouchSystems Vid : 04E8 Pid : 685D GT-I9100 Phone [Galaxy S II] (Download mode) Vid : 0572 Pid : 1321 Conexant Systems (Rockwell), Inc. Vid : 0572 Pid : 1324 Conexant Systems (Rockwell), Inc. Vid : 0572 Pid : 1328 TrendNet TFM-561 modem Vid : 0572 Pid : 1329 Conexant Systems (Rockwell), Inc. Vid : 0572 Pid : 1340 Conexant Systems (Rockwell), Inc. Vid : 058B Pid : 0041 Flash Loader utility Vid : 05F9 Pid : 4002 PSC Scanning, Inc. Vid : 0694 Pid : FF00 Lego Group Vid : 079B Pid : 000F Sagem Vid : 0803 Pid : 3095 V.92 56K Mini External Modem Model 3095 Vid : 0870 Pid : 0001 Ricochet GS Vid : 0ACE Pid : 1602 ZyXEL Omni FaxModem 56K Vid : 0ACE Pid : 1608 ZyXEL Omni FaxModem 56K UNO Vid : 0ACE Pid : 1611 ZyXEL Omni FaxModem 56K Plus Vid : 0E8D Pid : 0003 MT6227 phone Vid : 0E8D Pid : 3329 Qstarz BT-Q1000XT Vid : 1576 Pid : 03B1 ??? Vid : 17EF Pid : 7000 Lenovo Vid : 1BBB Pid : 0003 Alcatel one touch 4030D modem connection Vid : 2184 Pid : 001C GW Instek Vid : 22B8 Pid : 2D91 Motorola PCS Vid : 22B8 Pid : 2D92 Motorola PCS Vid : 22B8 Pid : 2D93 Motorola PCS Vid : 22B8 Pid : 2D95 Motorola PCS Vid : 22B8 Pid : 2D96 Motorola PCS Vid : 22B8 Pid : 2D97 Motorola PCS Vid : 22B8 Pid : 2D99 Motorola PCS Vid : 22B8 Pid : 2D9A Motorola PCS Vid : 22B8 Pid : 6425 Motorola PCS Vid : 22B8 Pid : 7000 Motorola PCS ehci-hcd.ko USB 2.0 'Enhanced' Host Controller (EHCI) Driver uhci-hcd.ko USB Universal Host Controller Interface driver usbcore.ko usb-common usbhid.ko USB HID core driver usbnet.ko USB network driver framework usb-storage.ko USB Mass Storage driver for Linux Vid : 03F3 Pid : 0001 Adaptec, Inc. Vid : 0409 Pid : 0040 Floppy Vid : 04DA Pid : 2372 Lumix Camera (Storage mode) Vid : 04DA Pid : 2373 Panasonic (Matsushita) Vid : 04E8 Pid : 5122 Samsung Electronics Co., Ltd Vid : 04E8 Pid : 5136 Samsung Electronics Co., Ltd Vid : 0525 Pid : A4A5 Pocketbook Pro 903 / Mobius 2 Action Cam / xDuoo X3 Vid : 054C Pid : 0032 MemoryStick MSC-U01 Reader Vid : 054C Pid : 0058 Clie PEG-N7x0C PalmOS PDA Mass Storage Vid : 054C Pid : 0069 Memorystick MSC-U03 Reader Vid : 054C Pid : 006D Clie PEG-T425 PDA Mass Storage Vid : 054C Pid : 0099 Clie NR70 PDA Mass Storage Vid : 054C Pid : 016A Clie PEG-TJ35 PDA Mass Storage Vid : 057B Pid : 0022 Y-E Data, Inc. Vid : 05AC Pid : 1202 iPod 2G Vid : 05AC Pid : 1203 iPod 4.Gen Grayscale 40G Vid : 05AC Pid : 1204 iPod [Photo] Vid : 05AC Pid : 1205 iPod Mini 1.Gen/2.Gen Vid : 05AC Pid : 120A iPod Nano Vid : 05C6 Pid : 1000 Mass Storage Device Vid : 05E3 Pid : 0701 USB 2.0 IDE Adapter Vid : 05E3 Pid : 0702 USB 2.0 IDE Adapter [GL811E] Vid : 0636 Pid : 0003 Vivicam 35Xx Vid : 07AB Pid : FCCD Freecom Technologies Vid : 07C4 Pid : A400 CompactFlash & Microdrive Reader Vid : 07C4 Pid : A4A5 Datafab Systems, Inc. Vid : 090A Pid : 1200 MP3 player Vid : 090C Pid : 1132 5-in-1 Card Reader Vid : 0AF0 Pid : 6971 Globetrotter HSDPA Modem Vid : 0BC2 Pid : 2300 Expansion Portable Vid : 0D49 Pid : 7310 OneTouch 4 Vid : 0DD8 Pid : 1060 USB-CF-Card Vid : 0DD8 Pid : D202 Netac Technology Co., Ltd Vid : 1058 Pid : 0704 My Passport Essential (WDME) Vid : 1058 Pid : 070A My Passport Essential (WDBAAA), My Passport for Mac (WDBAAB), My Passport Essential SE (WDBABM), My Passport SE for Mac (WDBABW) Vid : 1199 Pid : 0FFF Sierra Wireless, Inc. Vid : 1822 Pid : 0001 Twinhan Vid : 19D2 Pid : 1225 ZTE WCDMA Technologies MSM Vid : 2735 Pid : 100B MPIO HS200

That is a good start. Unfortunately I cannot help with the 10gb NIC... Keep looking around the forum.

oui tu peux assurer de cette manière

За редким исключением, обновление и миграция, проходит просто и безболезненно. Не забывайте резервировать свою конфигурацию. Править, точнее, необходим новый загрузчик. Если у вас 1.02, то необходим 1.03 https://mega.nz/folder/yQpw0YTI#DQqIzUCG2RbBtQ6YieScWg/folder/7AoyySoS Как я уже писал выше, это скрытые Системные папки. Для их видимости, необходимо получить, так называемый ROOT доступ. Без этого доступа, сложно показать местоположение этой папки. Ну а так...... "Два пальца левее Алголя...." ))) Сделайте эти рекомендации и вы её сами увидите https://www.synology.com/ru-ru/knowledgebase/DSM/tutorial/General_Setup/How_to_login_to_DSM_with_root_permission_via_SSH_Telnet

Thank you fryride for time you spent. I'm done and happy Now i know how to change disks in NAS, move packages and something new about how DSM works

Thanks. You have a number of options. If you have backed everything up from volume 2 (after salvaging what you can from volume 1) then you can do a fresh install on your new drives. I have a question about the version of DSM you have chosen (later). Then you can restore data, install packages and start configuring. If you haven't, then you could put your new drives into the NAS, with volume 2 and then boot. You could then create a new RAID group on the two disks and copy your files over. You can then remove volume2 and boot your new machine, You can then do an upgrade. (Note in case you are unaware, the system gets copied to all disks and so can boot from any available disks.). If you do go for the upgrade then you need to delete the hidden directory ./xpenoboot which will be there from when you were on version 5.2 before you run the upgrade. My next question is: Why have you chosen to go with 6.2.2 rather than 6.2.3? At the moment, 6.2.3 is the recommended version (see below) and it seems to be supported on HP Gen 8 The only negative is that disk hibernation may not work on this release. For the releases in between 6.1.7 and 6.2.3, Synology changed the driver support. And then they put it back the way it was for for 6.2.3. To get 6.2.2 to work, you are going to have to either buy and install an intel based network card or mess around with loading a driver set into the image on your USB stick. and So I would strongly recommend going to 6.2.3 or if disk hibernation is an issue, then I would go for 6.1.7 Finally (phew!) If you must use the same USB stick, then you can use the same VID/PID. That bit worries me. I would just like to keep a known working configuration around for a bit.

Mellanox cards work great, I use Connect X-3's on my systems, directly attached with DACs.

the build number of that dsm beta version it 40850, a lot of changes compared to the 25426 of dsm 6.2 (if there is no new start at a higher number like 40000 like when starting to use new base kernel) 918+ -> 4.4.180+ 3615 -> 3.10.108 (i guess 3617 will be 3.10.108 too) edit: and i was wrong with 3617, its 4.4.180+ i guess @satdream's "both" might be 918+ and 3617? its a little surprise to see that 3617 got a really "new" kernel, so all three versions use a new base kernel and old extra drivers will not work for that reason as there is no new kernel source from synology we could start with a vanilla kernel from kernel.org, i guess at least the network drivers should work that way because synologys patches in there custom kernel are usually not in that area

Открутите плату контроллера с жёсткого диска и канцелярской резинкой красно-синей почистите контакты (без фанатизма) которые идут к головкам, они скорее всего окислились. Это частая проблема дисков WD. Далее заново прогоните викторией низкоуровневое форматирование. Я использую Hard Disk Sentinel. У меня стабильно раз в полгода отваливается один из трёх жёстких, все WD. Как только появляется ошибка ввода-вывода, сразу выключаю сервер и чищу контакты. Проблема сразу исчезает даже без форматирования и SMART по нестабильным секторам чистый становится. Если процедуру оперативно не сделать, то из нестабильных секторов они переходят в неисправные или перераспределённые из резерва. Дома у меня влажность 50-60%, почему они окисляются я хз. Но по поиску проблемы в интернете я не один, нас много. По такому принципу я восстановил дисков 10 на работе, которые хотели выкинуть, почистил и все проблемы ушли. 3 сентября была очередная проблема

In general - Synology Write Cache:

hi guys .... i just managed to install xpentology in hdd, no usb required to boot system 6.2. 1)Just start up boot from usb... 2)make nesessary login setups etc... 3) use usb to image tool (google it) to backup usb stick to *.img 4) connect your hdd you intent to use as boot with adapter as usb to the system you mad the *.img file 5) use balena etcher (google it) to write *.img to hdd 6) disconnect hdd and connect it as boot disk to xpentology system. 7) xpentology runs just fine from the new hdd!!!

Ese problema siempre lo vas a tener salvo que compres (yo lo hice), un paquete del mismo proveedor. En algún almacén online de la "amazonia", venden por ejemplo paquetes de 10 memorias USB de 256MB o 512MB, y todas tienen el mismo PIV/VID. Sino tendrías que estar editar el archivo grub.cfg antes de restaurar el usb. En mi caso guardo las imágenes de los USB con la aplicación Win32DiskImager, que permite tanto hacer copias de las memorias como restaurar imagenes en ellas. Es super cómodo y si el USB fallase solo tengo que restaurar la imagen en otro USB. Espero te sirva, saludos

Pues gracias Yonvu, el cráneo de IG-88 me dio consejos, y compre uns Gigabyte b365M H3, 8gb ram, un i3 8100, viene con 6 puertos satas, y así hice mi primer NAS, estoy muy contenta, ya está funcionando con 5 HDD mecánicos y un .M2 donde tengo las VMMs. Ciertamente, gasto demasiada electricidad para este equipo con fuente de 550w, 24hs x 7 días, con el tiempo puede ser un problema. Estoy pensando en alternativas, poner un panel solar solo para el NAS, por el momento he programado el encendido y apagado y de noche lo tengo 8hs. apagado, y a la mañana se enciende solo, es decir , por ahora está el DSM6.2 encendido 16hs diarias, y veremos PODO como se comporta.

Вообще не удалить, а отформатировать.... Но сам никогда этим способом не лечил. На форуме описан этот вариант. По мне так проще ROOT сделать и снести раздел.

Так Хрень не даст. Массив разрушит. Лучше на выброс Баловался как то с Викой, тоже трёшки гонял, так максимум три дня дала Хрень. Потом ошибки и сбой. Лучше не испытывать судьбу

Так вот своими странностями она и предупреждала. Хрень очень критична к битых хардам. Что Винда пропустит, синолоджи отринет.

увидела ли синолоджи все диски? я тут с 16 боролся как мог и то постоянные траблы если при перезапуске USB диск будет подключен, то он садиться на порт SATA вместо пары последних внутренних дисков как я понял нужно править загрузчик и в него прописывать патчинг файлов на лету в процессе загрузки. это инструкция временная - гораздо удобнее завести с сертификатом и ключом WinSCP рутом. Последовательность такая: 1) Взял puttygen, сгенерировал и экспортировал приватный (nas.ppk) и публичный (nas.pub) ключи (SSH2-RSA 2048, без пассфразы). 2) Залогинился WinSCP админом, запихнул публичный ключ в /tmp/nas.pub 3) после в putty логинимся под админом и вводим sudo -i + пароль админа, далее скопировал ключ на место: mkdir /root/.ssh ssh-keygen -i -f /tmp/nas.pub >> /root/.ssh/authorized_keys 4) в WinSCP указал nas.ppk (SSH->Auth->Private key for authorisation). Все. Теперь логинсь в NAS по ключу.

Think of the hypervisor (ESXi) as a "wrapper" around DSM. Install ESXi on server, then configure a virtual machine (VM) inside, on which to install DSM. You will need an ESXi boot device (generally a USB key, which is confusing because a baremetal XPEnology loader also uses a USB key). You will also need an ESXi scratch disk that is separate from the disk(s) you intend to use for DSM. Once you have installed ESXi and have a scratch volume configured, you can install the DSM VM. XPEnology loader does not need a USB key when running under VMWare, it can just use a disk image. That's why there is a menu option in the loader, so it knows which you are doing. It takes some trial and error to learn how to best configure DSM under a hypervisor; it offers you much more control over your hardware/software configuration. FMI: https://www.vmware.com/topics/glossary/content/hypervisor#:~:text=How does a hypervisor work,the physical and virtual resources.

Сегодня пробовал открыть SurveillanceStation-x86_64-8.2.7-6222_patch_40 на андроиде SS клиент, пробовал в течении нескольких часов но они не работали (картинка есть но сверху картинки крутится круг, вроде как грузится), сразу же включил на компютере SS клиент - все работает, посмотрел на Андроид а там все загрузилось и стало показывать. Таим бомба или что это?

Дополняю отзыв по своему решению. Пришли все железки, собрал себе NAS на 12 дисков, 8 отсеков заполнил. Выполнил замер скорости передачи данных SSD диска через программу CrystalDIskMark, SSD подключен к контроллеру JMB585 через расширитель pci-e. Результат на фото. Результатом БОЛЕЕ чем доволен. P.S. Фоткал экран, т.к. загружался с livecd)) Всем удачи!

Sorry if this is hijacking the thread but anyone that wants to move their existing VM setup to this updated setup, here's how I did mine on Workstation 15. Open and import Armazohairge's appliance. - you might want to change the processor and memory allocations of this imported VM Power it up, find it using Synology Assistant and configure just the initial setup. Shut down the VM, through the Synology shutdown process. Add your old Virtual drives to this new VM BUT make sure all of those drives are on SATA1 and not SATA0. Jun's bootloader is on SATA0. Launch the VM Go into Storage Manager and repair the System Partition that is prompted. Update the basic packages that are prompted. That's it.

i checked too and it did not work, so i made a new upload and replaced the link

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: Jun's Loader v1.03b DS3617xs - Using custom extra.lzma: No - Installation type: ESXi 6.7 I also had the "File is corrupt issue." Fixed it after installing FixBoot.sh :

Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.03b - ds918+ - Using custom extra.lzma: NO - Installation type :CONFIGURATION ASUS H170M PLUS/INTEL CORE3 4130/16Gb DDR4/6x 8To (st8000vn0022)+SSD SATA CACHE 500 Samsung 860 EVO SHR (btrfs) + beyimie sata carte pcie 4 ports (marvell 88se9215) UPS eaton ellipse eco 650 external HDD 1 To BOOT USB Lexar 64GB P20 JumpDrive USB 3.0 LOADER JUN'S LOADER v1.04b DS918+ DSM 6.2.3-25426 POSTE CONFIG xpenology.com/forum/topic/18529-config-ok-asus-h170m-plus - Additional comments: 1. Update with DSM GUI to DSM 6.2.3-25426 Update 2 : All is work.

918+ image worked with an HPE version of the x520 for me.

Intel x520 and the other Variants works with Stock. Gesendet von meinem Mi A3 mit Tapatalk

Hello i want to post my successful CLEAN installation of DSM 6.2.2-24922 Update 6 on the F2-220. The things i have used: -Jun's Loader v1.03b DS3615xs (LINK) -Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs (LINK) -Bios settings set to "Legacy" -VGA cable to select USB Stick from Boot options Steps: -First edit the GRUB file with VID,PID,MAC etc -Second, mount the second partition and replace the extra.lzma file from Driver extension mod -Third, extract the zImage and the rd.gz from the DSM_DS3615xs_24922.pat file and place them on the second partition again Edit: I have tested the DSM 6.2.3-25426 Version and booted up nicely I have followed the same steps but i have used the following: -Same loader -Driver extension jun 1.03b/1.04b for DSM6.2.3 (LINK) -The zImage and the rd.gz from the DSM_DS3615xs_25426.pat file

30 or best offer. He accepted 25 dollar offer plus free shipping. Just bought today will try to update this is where I got mine he's got 7 more but there's like 7 other guys selling sale cards from server pulls ae rj45 some sfp+ some low, some high profile. https://www.ebay.com/itm/133363872120 I confirmed with Guru IG-88 that he has one working with 6.2.2 and it its working with the 6.2.2 driver pack so the 57810 should work too the driver is bnx2x.ko though I can't vouch for the eBay vendor you can return it within 30 days. Since I am still somewhat of a novice I made sure to check with others who knew about this so maybe do some checking before you pull the trigger on buying one if you don't know what you're doing.

Связался с гуру этого форума IG-88, получил очень много информации. Отвечаю на свои вопросы выше: контроллер Marvell 88SE9215 + JMicron JMB5xx с множителем. Marvel 9215 + Marvell 9705 с множителем т.е. максимально DSM будет видеть 4 порта SATA. Да и вообще обширный поиск всех площадок показал - Не существует контроллеров на 8 SATA под pci-e 1x без множителя. В моём случае есть решение, заказать такой переходник, https://www.aliexpress.com/item/33016011943.html?spm=a2g0s.8937460.0.0.6e482e0ekrSfyt И взять 2 контроллера на 5 SATA на чипсете JMB585 с pci-e 3.0 4x https://www.amazon.co.uk/SNOWINSPRING-SATA3-0-Expansion-Computer-Chassis-black/dp/B089K4ZX7Q/ref=sr_1_1?dchild=1&keywords=JMB585&qid=1592129852&s=electronics&sr=1-1 Ограничения в моей текущей конфигурации будут следующие: У меня pci-e 2.0 x1, общая скорость обмена данными составит 500 MB/s. Для моих домашних нужд этого будет достаточно. Плюс в том, что если когда-нибудь я перейду на pci-e 3.0, то у меня будет прирост производительности. Вариант от IG-88 мне тоже понравился. Он предложил использовать схему без лишнего контроллера в цепочке, а только гибкий шлейф с pci-e x1 на pci-e x16. Схема уже проверена и рабочая. https://www.amazon.co.uk/non-brand-Ribbon-Extension-Cable-Adapter/dp/B07WK36H3B/ И взять один 8 портовый контроллер на чипсетах ASM1806 chip & 4 chips ASM1061. DSM видит все 8 дисков, проверено. https://www.amazon.co.uk/dp/B07KW38G9N?linkCode=gs2&tag=comonboo-21 По сути можно брать любой проверенный на форуме контроллер в данной схеме. Надеюсь кому-то это будет полезным. Удачи вам.

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2-23922 Update 5 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: YES - Installation type: BAREMETAL - ASUS ROG STRIX Z390 I GAMING, Intel - Core i3-8100 3.6 GHz Quad-Core Processor - Additional comments: Ran Recommended Commands: rm -rf /usr/lib/modules/update/* rm -rf /usr/lib/firmware/i915/* from ssh terminal to remove drivers and restarted before using newly copied Test LZMA 0.11. Updated Directly with DSM_DS918+_25426.pat file, took about 7-10 minutes from restart back to Main Page. All Settings Seem to be intact including Docker. AMAZON USB 3.0 GIGABIT ETHERNET NIC Working (0B95 1790), . I-219-V Internal NIC (WORKING GREAT with Test LZMA v0.11 previously did not work). I am a happy camper. I also recommend having a ubuntu iso flashed to a flash drive on hand for quick troubleshooting and getting a better view of your devices ID's & grub editing/mounting. Cheers and Thank You again to all members who assisted!

Hi IG-88, Is there a way that we can include these files in DSM6.2.3 for 918+ ? I have a Nvidia on a shelf and maybe I will do a better job than G5400 cpu.

For those Linux newbs who need exact instructions on installing the script, follow this here. Please be VERY careful with syntax especially when working as root. If you have not turned on ssh in Control Panel remote access, do it Download putty or other ssh terminal emulator for ssh access Connect to your nas with putty and use your admin credentials. It will give you a command line "$" which means non-privileged In File Station, upload FixSynoboot.sh to a shared folder. If the folder name is "folder" and it's on Volume 1, the path in command line is /volume1/folder From command line, enter "ls /volume1/folder/FixSynoboot.sh" and the filename will be returned if uploaded correctly. Case always matters in Linux. $ ls /volume1/folder/FixSynoboot.sh FixSynoboot.sh Enter "sudo -i" which will elevate your admin to root. Use the admin password again. Now everything you do is destructive, so be careful. The prompt will change to "#" to tell you that you have done this. $ sudo -i Password: # Copy the file from your upload location to the target location. # cp /volume1/folder/FixSynoboot.sh /usr/local/etc/rc.d Make the script executable. # chmod 0755 /usr/local/etc/rc.d/FixSynoboot.sh Now verify the install. The important part is the first -rwx which indicates FixSynoboot.sh can be executed. # ls -la /usr/local/etc/rc.d/FixSynoboot.sh -rwxr-xr-x 1 root root 2184 May 18 17:54 FixSynoboot.sh Ensure the file configuration is correct, reboot the nas and FixSynoboot will be enabled.

Краткая инструкция по получению значений vid и pid Необходимое условие правильной работоспособности DSM , это запись реальных значений vid и pid в ваш образ загрузчика перед записью на флешку. Редактирование файла grub.cfg , строки set vid=Ваш vid и set pid=Ваш pid Один из симптомов неправильной записи vid и pid, это отсутствие DSM в сети. Получить vid и pid не сложно. Либо воспользоваться способом описанным в "Центре поддержки Synology" или посредством одной из программ. http://flashboot.ru/files/vidpid/ https://www.antspec.com/usbflashinfo/ https://www.usbdev.ru/files/usbflashinfo/ https://www.synology.com/ru-ru/knowledgebase/DSM/tutorial/Compatibility_Peripherals/How_do_I_check_the_PID_VID_of_my_USB_device

Let me introduce my build First of all Thank you guys for your help & advises. So I got my first NAS two years ago. (WD My cloud ex2 ultra) and couple months ago I got WD PR4100... Initially I choose WD just because I had no experience and I got a deal. I wasn't happy with that. I had many problems with almost everything. Customer support is terrible... Very poor OS and etc. Finally I decide to go to Synology and good for me I found this great website and project. Thanks! Parts list: 1. ASRock Motherboard Motherboards Z370M-ITX/AC ($95.90 + $8.87 Tax = $104.77) 2. Intel i7 8600k (I had 8700k but gave it to my friend on NY) = $259.89 3. EVGA 450 BT, 80+ Bronze 450W = $24.99 + $2.31 = $27.30 4. Patriot Viper Elite Series DDR4 8GB PC4-21300 2666 MHz Memory Module = $53.99 + $4.99 = $58.98 5. Lian-li q25b = $40 (Craiglist) = $490.94 1.03b + DSM 6.2 + DS3617XS. Especially want to mention MB. Happy with that. 6SATA + Mini ITX form-factor. Exactly what I want for my case. WIFI + 2 LAN ports. Good price also. I didn't include HDDs because it's all up to you. But I have 2x2TB Hitachi & 2xWD4TB Red NAS. Now I am testing the system Hitachi's HDD. Also I want copy/paste my post from my first thread about issues. I wasn't able to find NAS after first boot. I did 4 things and problem is gone. 1. Turn off Audio Controller 2. Change priority to onboard graphics. 3. Turnoff bluetooth controller. 4. Turn off wireless adapter. Please, see pictures. I will glad to know your feedback. P.S. English is second language. Post can (for sure) have linguistic/grammar mistakes.

Результат: Успешно - Версия и модель загрузчика: JUN'S LOADER v1.04b - DS918+ - Версия DSM: DSM 6.2.1-23824 Update 4 - Аппаратное решение: Gigabyte GA-J3455N-D3H (версия биоса F3) + 1x4Gb DDR3L - lzma не редактировался - установлено RAID SHR и разделы BTRFS (разница в скоростях с EXT4 +/- одинаковая, тестировал) - транскодинг есть (хардварный появляется сразу, а софтварный появится после установки и запуска видео станции) / новичкам замечу, кто не знает что это такое - даже не вникайте, на практике это не малонужная услуга - гигабитные порты работают на 100%, wi-fi 5 ГГц работают на скорости до 75 Мб/с при больших файлах, однако видно что малостабильно при обычном использовании, возможно проблема драйверов (возможно поправят в новом загрузчике); так или иначе, скоростей с головой хватает работать большими офисами или огромной семьей одновременно смотреть разное кино с NAS из разных комнат:) - проблемы при подключении к портам USB NAS (скорость туда-обратно 5-30 Мб/с) (настройки в BIOS ситуацию не меняют); с проблемой не знаю как бороться, ожидаю обновления загрузчика; опять таки перенести инфу можно и по WIFI, а в повседневной жизни вам USB этот и не нужен будет - есть quikconnect (в инструкции указано про серийники устройств. поясняю, что серийники могут остаться либо те что есть по умолчанию в файле, всё запустится, но не будет малонужных примочек; либо необходимо прописать серийник сетевой карты И самого устройства с реально выпущенной машины), опять таки, малополезная функция, так как легко можно настроить альтернативные сервисы - не запускался образ с флэшкой Transcend JF V60 (ошибка отсутствия 13 файлов), запустилась на SiliconPower и SunDisk. Флэш карты можно восстановить с помощью recovery tools с сайтов производителей флэшек. Ни в коем случае не прерывайте процесс установки (первые 10 минут после начала установки), иначе можно загнуть разделы флэш карты, как я и сделал. После перезагрузки можно выключить. Ещё замечу, что разницы от типа флэшек я не заметил в скорости работы или ещё в чем-то. - отключено с-state (отключить обязательно) в bios и все настройки экономии питания процессора для повышения скорости работы портов - запуск в режиме только legacy никак не меняет ситуацию, можете не тратить время - тем кто присматривается к материнке, советую также присмотреться к ASrock, если найдете по отзывам стабильные платы. Собирать новые системы на базе Pentium или Core себя никак не оправдает, только если вы не владелец киноресурса. Оперативной памяти в 2-4Gb за глаза. Обычная нагрузка не превышает 1Gb. Больше есть смысл только для виртуализации. Также не забывайте что процессор j3455 поддерживает максимум 8Gb (16 нет смысла ставить).

Перед тем как что-то менять в своей работающей системе, настоятельно рекомендуется сделать резервные копии своих особо ценных данных, чтобы потом не жалеть об их безвозвратной потере. Все, что вы творите - это ваш страх и риск, никто не побуждает вас это делать. Самый простой и надежный способ безопасно попробовать - выключить хрень, отключить все диски и загрузочную флешку от действующей системы, взять чистый диск и другую флешку и попробовать установить новую версию загрузчика и системы, если прокатило, то делать уже на действующей системе. 1. Как установить (подготовительные работы описаны для компа с Windows): а) скачать образ загрузчика 1.04b (исходная тема тут), создать каталог в корне диска без символов на кириллице, например, c:/918/ и поместить туда образ загрузчика б) определить VID/PID флешки или картридера в который она вставлена (Панель управления - Диспетчер устройств - Контроллеры USB - Ваша флешка/ридер - Свойства - Сведения - ИД оборудования, нужно для того, чтобы система DSM опознала этот диск и не пыталась устанавливать себя на него, если неправильно определите и пропишите эти параметры, то система будет вылетать по ошибке 13 при установке в) скачать, установить и запустить программу OSFmount, смонтировать Partition 0 (15 Mb) из файла загрузчика, перед монтированием убрать галку Read-only drive г) скачать, установить и запустить программу Akelpad, открыть файл grub/grub.cfg на ранее смонтированном диске, правим, сохраняем: set vid=0xA234 #VID флешки/ридера set pid=0xB678 #PID флешки/ридера set sn=1780PDN123456 #sn set mac1=001132123456 #mac первой сетевой карты set mac1=001132123457 #mac второй сетевой карты, второй и последующий отличаются от первого на +1 в последнем разряде в шестнадцатеричной системе ... set netif_num=2 #количество сетевых карт ... set sata_args='SataPortMap=6' #контроллер sata, значения: 6 - 1 контроллер на 6 портов; 22 - 2 контроллера по 2 порта; 42 - 2 контроллера, первый на 4 порта, второй на 2 и т.п. Где брать sn и mac - ваша головная боль, гугл в помощь, система установится и будет работать с теми, которые изначально прописаны в загрузчике, но с ограничением функционирования некоторых сервисов и модулей, таких как: QC, пуш уведомления, активация кодеков для транскодинга, установка лицензий syno... Но для большинства и без них будет достаточно. На форуме писали, что прокатывало с sn и mac от других реальных моделей syno, но так не пробовал, поэтому утверждать не буду, кто хочет - дерзайте. д) размонтировать диск в OSFmount е) скачать, установить и запустить программу Rufus и записать ранее подготовленный образ на флешку з) вставить флешку в машину, на которой планируете запустить хрень, подключить диски, включить питание ж) отключить брандмауэр в антивирусе, в браузере набрать http://find.synology.com или установить Synology Assistant с сайта syno и найти вновь установленную хрень в вашей сети и) установить DSM установить хрень следуя инструкциям программы установки и приступить к настройке (как это делать здесь не описываю, ибо все ответы есть в базе знаний syno) Для ленивых есть утилита, где собраны основные проги для Windows x64 2. Если хрень не обнаружилась в сети, то скорее всего в загрузчике нет драйверов для ваших сетевых карт и/или для sata контроллеров. a) запустить программу OSFmount, смонтировать Partition 1 (30 Mb) из файла загрузчика, перед монтированием убрать галку Read-only drive б) скачать extra.lzma из этой темы и перезаписать в смонтированном диске в) размонтировать диск и перезаписать образ с добавленными драйверами на флешку г) попробовать запустить и найти хрень в сети, если не получилось, то увы и ах, либо просить, чтобы добавили дрова для ваших устройств в этой теме или самому их добавлять - теория тут 3. Транскодинг (нужны sn и mac от реальной железки) С наибольшей степени вероятности запустиnся на процессорах Intel начиная с 4го поколения (Haswell), но есть нюансы с моделями материнских плат и биосами. Проверяем следующим образом: hardware (hw) транскодинг - в корне системы должен быть каталог /dev/dri с тремя подкаталогами внутри, если его нет, но нет и hw транскодинга, чтобы проверить - ищем каталог в терминале/ssh командой cd /dev/dri. software (sw) транскодинг - должны подняться соответствующие кодеки, проверить можно командой в терминале/ssh cat /usr/syno/etc/codec/activation.conf Если результат такой, то он есть: {"success":true,"activated_codec":["hevc_dec","h264_dec","h264_enc","mpeg4part2_dec","ac3_dec","vc1_dec","vc1_enc","aac_dec","aac_enc","mpeg4part2_enc"],"token":"абракадабра"} Если ничего похожего нет, то нет и транскодинга. P.S. Просьба к админам прибить тему в шапке и дать мне доступ на редактирование первого поста этой темы, буду добавлять по мере поступления вопросов, ибо задолбали оленеводы, которые задают вопросы по установке, во всех подряд темах.

All good advice. However, if you manually troubleshoot your volumes, a standard RAID1/RAID5 array is easier to work with than SHR (which is multiple RAID arrays joined via LVM). So if you don't need that extra 500GB of storage, I'd leave those two off and just add to your array when you get additional, larger drives. Also, consider skipping the cache. It is less effective than you might think. And much of the value is duplicated with the large amount of RAM you have which will write cache. There are many, many instances of corrupted volumes due to SSD cache. At a minimum, do some testing with and without cache for a workload you are likely to do. I think you'll find that it isn't meaningful enough to warrant its use.

4 - How many drives can I use? Community members have tried systems with up to 24 drives that are stable. There is a physical limit of 26 drives due to limitations in drive addressing in Linux