Popular Content

Showing content with the highest reputation since 08/24/2020 in all areas

  1. 4 points
    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
  2. 3 points
    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
  3. 3 points
    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
  4. 2 points
    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
  5. 2 points
    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/)
  6. 2 points
    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.
  7. 2 points
    Ok, I gave it a try and set up a Hyper-V VM with 1x500GB SSD VHDX and 2x direct connected 1TB HDDs. The process is pretty straightforward. Download the Hyper-V VM, unpack and import it, adjust the hardware settings (I gave it 1x CPU and 4GB RAM) and fire it up. The rest is done as known via browser as usual (managing admin account, set up system settings, entering the license key, etc.). Qnap‘s browser gui is not as „clean“ as Synology’s DSM but good to handle. Some features like creating RAID and volumes seem to be more difficult but you’ll have more options (thick or thin volumes, warning level, over-provisioning, etc.). Although the VM has only one CPU and 4GB RAM dedicated it runs pretty smooth. SMB and rsync transfers are fast as expected. Next step will be installing some (free) apps.
  8. 2 points
    https://mega.nz/file/adVDmaLS#2SN_FA-kkOb_yP0lfQJ84DFywMBW15I3Wk3i3ZTfEew Paid the 2$ so you don't have to do it. Thanks for your work armazohairge
  9. 2 points
    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
  10. 2 points
  11. 1 point
    two is fine i use a two port 10G card and with the onboard its three, was no problem with 3615 so far but since i migrated to a new hardware using 918+ i "loose" one of the ports with a bigger update (ok, for now it was just one case and after 7.0 seems to start this year the 6.2 line might never get a bigger update after 6.2.3 this spring)
  12. 1 point
    Нельзя. Только если реализовать это через dsvideo то можно.
  13. 1 point
    Regarding your question, I also posted on the below thread. The NIC 211AT should be compatible, I had an H370M board that had that NIC and it worked but maybe their are other factors that it does not work for you. Also according to Flyride on that post he said that it does not matter if your VID/PID are correct or not. It has nothing to do with your NIC. Those VID/PID should be correct during the installation of the DSM.
  14. 1 point
    Собрал я себе домашний DIY NAS на SSD и GA-SBCAP3350. Давно хотел сделать полностью бесшумный, без активного охлаждения, экономичный и компактный NAS. И в принципе это удалось сделать. Подвернулась плата GA-SBCAP3350 с пассивным охлаждением (массивная пластина на днище), 2 SATA, 2 Ethernet, с питанием 9-36В, как раз под накопившиеся БП из под ноута. Вот описание платы: https://www.gigabyte.ru/products/page/mb/ga-sbcap3350rev_10#kf На борту 2х ядерный N3350. Существуют похожие платы на N3450, N4200 и др. Поставил 2 SSD Samsung Evo 860 и все это запихнул в корпус от старого eth коммутатора. Оба SSD питаются от разъема SATA_PWR1 на плате. В данный момент работает на: - Версия и модель загрузчика: JUN'S LOADER v1.03b - DS3615xs - Версия DSM: DSM 6.2.3-25426 - Дополнительные модули extra.lzma: NO Поставлено все с 0. По нагреву: БП от ноута 80Вт, немного теплый. Температура процессора в простое 43-45, в нагрузке 50+. Температура SSD в простое 43-45 в нагрузке 50+. Точнее проведу замеры и дополню информацию. В перспективе возможно использую более просторный корпус с оребрением для лучшего охлаждения SSD дисков
  15. 1 point
    Проверьте корректность правки значений VID и PID. Возможно придётся флешку поменять Для начала попробуйте восстановить родную версию, потом обновляйтесь. И устанавливайте вручную, предварительно скачав файл из архива Синолоджи.
  16. 1 point
    La solution OPenMptcpRouter reste intéressante si tu parviens à l'installer en VMM sur le Syno, ce serait le plus simple et le moins cher puisque tu n'aurais à priori pas grand chose à modifier dans ton réseau pour faire fonctionner cette solution. Fais un tuto si tu y parviens Mais effectivement, quoi qu'il en soit, pour NATter de la connexion 4G, à part peut-être la Box 4G Bouygues Telecom, il faut passer par un VPS extérieur pour récupérer une IP publique exploitable. Concernant ta question sur la télé, je ne suis pas certain d'avoir compris, tu voulais parler du multiposte TV de la Freebox, permettant d'accéder aux chaînes TV via la playlist m3u de la Freebox? Je ne sais pas si cela répond à ta question, mais j'ai omis de préciser que dans mon installation, la connexion ADSL est prioritaire sur la 4G; cela se règle au niveau du routeur sous Freshtomato en attribuant un "poids" ("Load Balance Weight" dans l'interface du routeur) à chacune des connexions: l'ADSL a le poids maximum de 256 et la 4G est à 1. Du coup, si je ne force pas un équipement à passer par la ligne 4G grâce au menu "Multiwan routing" de Freshtomato, tout équipement connecté au routeur utilisera par défaut la ligne ADSL. Et concernant l'ip de la TV, oui c'est possible de lui attribuer une IP fixe dans le sous réseau de la Freebox, c'est ce que je fais pour le Freeplayer puisque le DHCP de ma Freebox est désactivé. En gros pour schématiser même si j'ai depuis passé la Freebox en bridge et que ça change quelques trucs, ça donne ça (les IPS sont différentes dans mes captures d'écran, c'est juste pour l'exemple): Freebox (IP :, sans DHCP) \ > Routeur R7000 sous Freshtomato (IP: avec DHCP) --> machines du réseau local en IP:192.168.3.xxx Modem 4G (IP:, sans DHCP) / Mon modem 4G est un Netgear Nighthawk MR1100 que je ne recommande pas car il faut le bidouiller au niveau des antennes (4x4 mimo). Un bon vieux Huawei B715S ou équivalent fait très bien l'affaire. EDIT: j'ajoute deux captures de Freshtomato pour illustrer un peu mieux mon propos, dans le premier tu verras la page de configuration des modems ADSL (Wan) et 4G (Wan2). Dans le second, le Multiwan routing, où il suffit d'entrer seulement les périphériques Wan2 (4G) puisque Wan (adsl) est prioritaire et ne nécessite donc pas d'être forcé (j'en avais quand même entré un ou deux, just because).
  17. 1 point
    У меня ниже var, на втором уровне владелец у всех каталогов root, ниже не смотрел досконально, но встретились несколько файлов (не каталогов) у которых группа была не root. Еще как вариант, смотрите права в каталоге-шаблоне /var.defaults и делайте соответствующие в /var, может быть так будет правильней. По поводу вебинтерфейса DSM - выходит у разных моделей сино отличаются вебморды, я честно говоря не знал, т.к. немного имел дело только с хренологией 918 и 3615. По вопросу переустановки с восстановлением настроек - не имею пока должного опыта, если решитесь, напишите лучше в соответствующую ветку форума, думаю обязательно помогут, просто в ветку некстклоуда могут опытные товарищи не заглядывать.
  18. 1 point
    Проверьте, включена ли галка ssh в панель управления / терминал и снмп, sftp работает поверх ssh... Так же поройтесь в районе безопасность / учетная запись на предмет блокировки айпишников, пропишите вашу локальную подсеть в список разрешенных. Брандмауэр точно выключен?
  19. 1 point
    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
  20. 1 point
    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.
  21. 1 point
    Сетевое окружение включено ? В панели управления, где Обновление, есть пункт Сброс, но походу там всё сбрасывает. Можно удалить личные данные посредством удаления папки etc.defaults Удалить раздел /etc.defaults Перегрузиться Установить заново DSM Восстановить конфигурацию из *.dss (лучше сохранить резерв и в случае чего, не помешает) Установить по новой необходимые приложения
  22. 1 point
    Только это значение прописывал, остальные по дефолту. Если источник контента имеет статичный ip. то одного хватит. Если же динамика, то группу ip надо прописывать. Или каждый раз новый. Серийником не заморачивался, он мне не особо нужен, без него всё что мне надо работает
  23. 1 point
    Вот полностью согласен с предыдущим оратором....... Понятно когда с Синолоджи переход, но вот обратно...... Как то мне в руки попал халявный Синолоджи на шесть дисков, думал перейду на легальный аппарат. Поставил я его рядом со своим НР54 и вижу, проигрывает Синолоджи и по внешнему виду и по ....... Да по всем параметрам он проиграл. Но это чисто на мой, субъективный взгляд. Продал Синолоджи и не жалею.
  24. 1 point
    Petit retour (peut être que ça intéressera des personnes sur le forum) Ancien NAS : loader 1.02b 3615xs, 6.1.7, cm Asus p5gdc, core 2 duo Nouveau NAS : loader 1.03b 3615xs, 6.2.3-25426 (je n'ai pas tenté l'update 2 encore), cm Gigabyte h270m , 16 go ram Tout est reconnu sans insérer de drivers supplémentaires Insertion des nouveau disques sur le nouveau, j'ai tenté de respecter l'ordre (sans savoir vraiment si ça allait changer quelque chose). Syno assistant ne voit pas le nas, alors que findsynology si . Il me propose de migrer le nas, que je fais en mettant le.pat correspondant au 6.2.3. Redémarrage, puis maj des paquets et tout fonctionne nickel J'ai refaire les VM dans VMM car elles n'ont jamais réussi à redémarrer. Merci à @nicoueron pour la migration réussie
  25. 1 point
    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
  26. 1 point
    Hi, and again thanks to IG-88 for the amazing work ... As regularly registered tester for the DSM7.0 preview, I got link to download/test the pre-release on an official Synology 920+ ... it works fine (not a real revolution on GUI, certainly more on the core features especially on rebuild optimisations etc., but not tested obviously). By chance the overall Synology versions are available for the registered preview testers (I will not share, please don't ask), and I tried the 3617XS on an Xpenology baremetal under DSM 6.2.3-25426 Update 2. The update is well accepted, and installation worked fine (btw June Loader 1.03b is still compatible ), with final automated reboots etc. but then it block exactly as for the install from 6.2.2 to 6.2.3 = the new DSM7.0 install reset the additional drivers and a new extra.lzma aligned with DSM7.0 is needed to restore NICs support (and I assume the other requested drivers). Hope our driver extension master will be kind to provide in the future with new release compatible of DSM7.0
  27. 1 point
    Sorry I don't have one anymore. My cable provider switched to encrypted channels two years ago which made T230 is useless.
  28. 1 point
    Yes. It might. Look at this post where you can find a tool to find the VID and PID and other useful software.
  29. 1 point
    Then definitely the I211AT should work without any issue. Did you try on both ports?
  30. 1 point
    El tema energético es importante sí. Pero que tengas una fuente de 550W no significa que el consumo real sea ese 24 horas al día. Yo en casa tengo hasta 3 servidores 24 horas y no suponen más de 10€ de consumo al mes. Realmente la mayor parte del tiempo los equipos no hacen gran cosa. Puedes poner algún medidos de consumo en el enchufe donde lo tienes para que compruebes realmente cuanto gasta tu xpenology. Saludos
  31. 1 point
    Купил на авито ASMedia asm1062+1093x2, 6 портов SATA, у человека на freeNAS-e не взлетел, воткнул в свой сервер с двумя дисками, диски определились, проинициализировал, посмотрим как работать будет. Продавец сказал что заказывал в Китае, выглядит как на этой картинке. только надписи над радиатором нет. Похожее что-то тут: https://aliexpress.ru/item/32929475100.html Запустил на железе из подписи, без бубнов и прочего, extra.lzma не менял, все штатно, с загрузчика. При первом запуске с контроллером кроме подключенных дисков определился диск на 100 мегабайт, с именем типа asm1093 config, точно не запомнил, после перезагрузки не появлялся больше.
  32. 1 point
    Вообще не удалить, а отформатировать.... Но сам никогда этим способом не лечил. На форуме описан этот вариант. По мне так проще ROOT сделать и снести раздел.
  33. 1 point
    yes -the patch has nothing to do with plex, its for synology's videostation and its licensing -the pre requirement for hardware transcoding is to have a proper hardware (cpu) and to use loader 1.04b with 918+ installation (minimum 4th gen intel cpu) if you dont have something in /dev/dri then there is no hardware transcoding, plex and videostation both need this device and its driver to work 3615/17 dont have such drivers, only 918+ comes with it and your hardware is not capable of running 918+ because your cpu is to old (3rd gen intel)
  34. 1 point
    Many are using earlier variants of that board (myself included). I don't see anything in the specifications that suggest it will work any differently.
  35. 1 point
    If you have a dynamic IP, you will need to setup a DDNS to access your NAS from outside your local network. So to start thing off you will need to open an account with a DDNS service provider. There are plenty out there, some paid, some free. The two below are the ones that I use personally. They are free. If you find others then you should also be able to use those. Some of these providers might already be part of the list included by Synology in which case you can skip the 'Customize' button and simply use the 'Add' button and select your service provider from there. The configuration example I am giving below will be based on duckdns.org because it's the easiest I have seen out there but unfortunately it is not included in the DDNS service providers list included by Synology so you will need to use the 'Customize' button first. - http://www.duckdns.org - http://www.nsupdate.info Once you have chosen your domain with duckdns.org you will need to configure DSM accordingly. So here is how to: In Control Panel go to External Access (1), then click on Customize (2). A new window should open. You need to fill in as per the image. To save you some time you can copy paste from the code tag provided below the image: http://www.duckdns.org/update?domains=__HOSTNAME__&token=__PASSWORD__&ip=__MYIP__ When you are done click Save. The window should close. Now click on Add (3), see first image. A new window should open. Select *DuckDns from the service provider list and fill in your duckdns domain, username and token: Click on Test Connection to verify that it's working. If it is working you should see the word Normal in green next to Status. You can then click Ok. If it is not working then it means you screwed up somewhere. Recheck query URL, domain, username and token. All that is left to do is to configure port forwarding on your router. This is called at times "port forwarding" or "port mapping". You need to check with your router's user guide as sometimes the wording differs from one brand to the other. The port(s) you will be forwarding to your box also need to be opened on DSM's firewall else DSM will refuse access to the port/service requested. If your ISP implements double NAT you might have to do some additional configuration to your router to allow the ports to be forwarded correctly. Check with your ISP first and also check this site or this site on how to overcome double NAT. Google is your friend. Note of caution here: If you want to make things very safe you would only port forward VPN ports. This means that you can only access your box via VPN which in turn then gives you full access to the box (and to your local network if configured accordingly) once a VPN connection is established. You could also port forward the GUI ports (usually 5000/5001 or the ones you would have customised). This would give you full GUI access to DSM from outside of your network but this can be unsafe specially if you don't have a strong password and proper firewall and safety mechanisms configured in DSM. You could also just forward the port(s)/service(s) that you need. It really all depends what you are using your box for but in most cases the VPN solution is the safest although not the most convenient. NEVER EVER port forward port 22 unless you know exactly what you are doing. To test that your box is accessible from the outside world while being at home you could use your smart phone in data mode (not in wifi) at the following address: http://[yourdomain].duckdns.org:[port number] or https://[yourdomain].duckdns.org:[port number] - Do no put www
  36. 1 point
    На "ТЫ" я обращаюсь только к очень близко знакомым, друзьям и родным. Ваши привычки возможно стоит пересмотреть. В таком случае все предельно просто. Загрузчик и два диска. Усложнять смысла нет. Маленького размера флешка это все что нужно. Когда есть только загрузчик и он срабатывает, система находится в сети (если драйвер для сетевой карты подходит) и сообщает, что диски для установки самой ОС не обнаружены. Если Вы настаиваете на установке загрузчика на SSD, то этот диск будет потерян для всего остального, включая установку самой ОС, и остаток его использовать не получится. Живет она там! и причем на всех дисках создает копии для отказаустойчивости. У Synology совершенно другой подход к вопросу установки ОС. Обсуждать его здесь и сожалеть, что он отличается от Вашего представления о том, как должна устанавливаться и работать операционная система бессмыслено. Этот проект - всего лишь попытка установить Synology DSM на сторонее железо. При том часто вполне успешная. Примерно как Hackintosh для МАК ОС.
  37. 1 point
    Yep, they have a monthly and yearly subscription model. Each VM with QuTSCloud needs a valid license. Licenses with monthly subscription can‘t be upgraded, for example from 1 to 2 cores. That’s only possible with yearly subscriptions. Bare metal isn’t possible with QuTSCloud.
  38. 1 point
    Дополняю отзыв по своему решению. Пришли все железки, собрал себе NAS на 12 дисков, 8 отсеков заполнил. Выполнил замер скорости передачи данных SSD диска через программу CrystalDIskMark, SSD подключен к контроллеру JMB585 через расширитель pci-e. Результат на фото. Результатом БОЛЕЕ чем доволен. P.S. Фоткал экран, т.к. загружался с livecd)) Всем удачи!
  39. 1 point
    there something in the tutorial section but beside editing jun.patch and synoinfo_override.conf you need to repack the extra/extra2 https://xpenology.com/forum/topic/14358-tutorial-modifying-104b-loader-to-default-to-24-drives/ imho its incomplete that way but when it works for some people ... one things that i would do more/different for my extra/extra2 usbportcfg needs to be changed too when going to 24 instead of 16 and thats something that needs to be added to jun's patch instead of just change something that is already there the original value looks like this usbportcfg="0x30000" the four zeros are equivalent to 16 so it goes well with jun's patch but when going to 24 the usb ports need to be shifted to above 24 to prevent overlapping with the internal ports so to be correct for 24 internal disks it should be this usbportcfg="0x3000000" or maybe make it 8 usb ports (just two as synologys original is a little low for normal systems) usbportcfg="0xff000000"
  40. 1 point
    - 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
  41. 1 point
    - 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 :
  42. 1 point
  43. 1 point
    Update: завелась без видеокарты с этим биос-модом: ZX-DU99D4_V1.11_for_x99zv102-Vasiliy-Temnikov взят отсюда был: https://xeon-e5450.ru/socket-2011-3/x99z-v102 PS. Добавил SSD - затестил Virtual Machine Manager - все летает, все нравится, ура!
  44. 1 point
    This script has evolved from a fairly simple "push" of the descriptive text into the Synology libraries overriding the default DSM text for the native CPU. Now the patch script is trying to use hardware information exposed in Linux (/proc/cpuinfo) to update not only the CPU description but the number of cores and hyperthreads. However, this is a flawed approach, because DSM has a thread limit for actual hardware. DS916+/DS918+/DS3615xs support a maximum of 8 threads of any type. This can be 8 physical cores, or 4 cores and 4 hyperthreads. But /proc/cpuinfo will not enumerate more than 8, regardless of how many cores and threads the CPU has. If you have an 6- or 8- core system, you will get the best performance by DISABLING hyperthreading with these DSM images so that all your actual cores are in play. DS3617xs supports up to 16 threads of any type. This can be 16 physical cores, or 8 cores and 8 hyperthreads. The same limitations apply, if you had a dual X5660 Xeon system, each CPU with 6 cores and 6 HT's, you would be best served by disabling hyperthreading so all your cores were functional. And just to confirm, the script itself addresses a purely cosmetic problem. It does not enable the use of CPU hardware. DSM uses the available cores and threads subject to the limitations above, regardless of what Control Panel says.
  45. 1 point
    Gigabyte Z390 Gaming X Howdy, reporting back. Implemented new build 1.04b ds918+ - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: yes IG-88 extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.11 - Installation type: BAREMETAL - Gigabyte Z390 Gaming X - CPU: Intel i3-9100 - NIC: Intel I219-V - Additional comments: Video hardware transcoding success - Plex, and Videostation with Updated Videostation workaround. (Updated Videostation workaround IG-88 post) /dev/dri - new driver has /dev/dri/Card0 - 0.10 had /dev/dri/0 interface - same hardware. CPU Frequency governor insmod ./cpufreq_ondemand.ko - FAILS with insmod ./cpufreq_ondemand.ko insmod: ERROR: could not insert module ./cpufreq_ondemand.ko: Unknown symbol in module /var/log/messages output. 2020-05-20T09:16:37+10:00 XXXXX kernel: [687147.086168] cpufreq_ondemand: Unknown symbol gov_queue_work (err 0) 2020-05-20T09:16:37+10:00 XXXXX kernel: [687147.086187] cpufreq_ondemand: Unknown symbol cpufreq_governor_dbs (err 0) 2020-05-20T09:16:37+10:00 XXXXX kernel: [687147.086204] cpufreq_ondemand: Unknown symbol dbs_check_cpu (err 0) Ironwolf Health Management is also running ok in 0.11 (it did not in 0.10) Thanks for your efforts. DeadS
  46. 1 point
    CPU is "Prestonia" which is Netburst architecture. Unlikely to work as the Linux kernel compile requires Nehalem or later. That chip is more than 15 years old!
  47. 1 point
    Synology DSM 6.1 (xpenology) Lets Encrypt ACMEv1 to ACMEv2 If you get messages like: synoscgi_SYNO.Core.Certificate.LetsEncrypt_1_create[5038]: certificate.cpp:957 syno-letsencrypt failed. 200 [new-req, unexpect httpcode] synoscgi_SYNO.Core.Certificate.LetsEncrypt_1_create[5038]: certificate.cpp:1359 Failed to create Let'sEncrypt certificate. [200][new-req, unexpect httpcode] Then you need to upgrade your DSM up to version 6.2 or replace execution (syno-letsencrypt) file and some changes in configuarion file: 1. Download file syno-letsencrypt (this file from DSM v6.2) link https://drive.google.com/drive/folders/1-LgjOAU3dBtNk2WKZ1KJY88Lklf12RPp?usp=sharing 2. If not enabled SSH, please enable in settings 3. Copy downloaded file syno-letsencrypt in any folder on you NAS 4. Connect to NAS with SSH (Putty) using admin account 5. Make backup of original syno-letsencrypt (sudo cp /usr/syno/sbin/syno-letsencrypt usr/syno/sbin/syno-letsencrypt.bck) 6. Copy downloaded syno-letsencrypt file to directory /usr/syno/sbin/ (ex.: sudo cp /volume1/sharedFolder/syno-letsencrypt /usr/syno/sbin/) 7. Change attributes (sudo chmod 755 /usr/syno/sbin/syno-letsencrypt) to execute new file 8. Now change default address for syno-letsencrypt, using ssh (sudo vi /usr/syno/etc.defaults/letsencrypt/letsencrypt.default) 9. Fine string "server": "https://acme-v01.api.letsencrypt.org/directory", press i and change 01 to 02 10. Press escape, enter :wq and reboot your NAS.
  48. 1 point
    Alors Bonne nouvelle !!! Je viens de faire cette mise a jour et tout fonctionne. J'ai encore quelques tests a faire mais tout semble fonctionner Pour ceux qui ont un doute : Lancez la mise a jour lorsque ça redémarre éteignez tout enlevez la clef et placez l'extra 0.5 remettre la clef et redémarrez et normalement tout fonctionne pour ma part j'ai du faire un hard reset de plus c'est tout
  49. 1 point
    You are ignoring the fact that Synology compiles DSM for each piece of hardware. We have support for the DS918 build via 1.04b and DS3615 via 1.03b. The only requirement for Haswell is the DS918 DSM image as it is compiled with FMA3 instructions. As long as you stay on loader 1.03b and DS3615 DSM you should be able to run 6.2.1 fine. However, on this loader and 6.2.1, very few network drivers are able to boot - e1000e is the one most are successful with. I think you have a 82576 NIC (you said 82676) which is supported by the igb driver. You can try it but if the network won't come up, you may need to disable in BIOS and add a e1000e NIC such as an 82571, 82574 or 82579 and it should work.
  50. 1 point
    Перед тем как что-то менять в своей работающей системе, настоятельно рекомендуется сделать резервные копии своих особо ценных данных, чтобы потом не жалеть об их безвозвратной потере. Все, что вы творите - это ваш страх и риск, никто не побуждает вас это делать. Самый простой и надежный способ безопасно попробовать - выключить хрень, отключить все диски и загрузочную флешку от действующей системы, взять чистый диск и другую флешку и попробовать установить новую версию загрузчика и системы, если прокатило, то делать уже на действующей системе. 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. Просьба к админам прибить тему в шапке и дать мне доступ на редактирование первого поста этой темы, буду добавлять по мере поступления вопросов, ибо задолбали оленеводы, которые задают вопросы по установке, во всех подряд темах.