Leaderboard

This is the first (experiential?) test version of the driver extension for loader 1.04b and 918+ DSM 6.2.2 edit 1/2020: atm i'd not recommend using the 918+ 0.6_test anymore, there will be a package with newer drivers shortly and it also will take the different cpu/igpu types into account (in some cases jun's new i915 driver can prevent systems from booting, seen on J1xxx and N42xx) additional information and packages for 1.03b and 3615/3617 are in the lower half under a separate topic Tested as fresh install with 1.04b loader with DSM 6.2.2, there are extra.lzma and extra2.lzma in the zip file - you need both - the "extra2" file is used when booting the 1st time and under normal working conditions the extra.lzma is used (i guess also normal updates - jun left no notes about that so i had to find out and guess). Hardware in my test system used additional driver: r8168, igb, e1000e, bnx2x, tn40xx, mpt2sas The rest of the drivers just load without any comment on my system, i've seen drivers crashing only when real hardware is present so be warned extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.2 v0.6_test http://s000.tinyupload.com/?file_id=29784352988385987676 !!! still network limit in 1.04b loader for 918+ !!! atm 918+ has a limit of 2 nic's (as the original hardware) If there are more than 2 nic's present and you can't find your system in network then you will have to try after boot witch nic is "active" (not necessarily the onboard) or remove additional nic's and look for this after installation You can change the synoinfo.conf after install to support more then 2 nic's (with 3615/17 it was 8 and keep in mind when doing a major update it will be reset to 2 and you will have manually change this again, same as when you change for more disk as there are in jun's default setting) - more info's are already in the old thread about 918+ DSM 6.2.(0) I might change that later so it will be set the same way as more disks are set by jun's patch - syno's max disk default for this hardware was 4 disks but jun's pach changes it on boot to 16!!! (so if you have 6+8 sata ports then you should not have problems when updating like you used to have with 3615/17) I will extend here to what is in the old thread for 6.2 had but atm i'm more willing to add 3615/17 support Basically what is on the old page is valid, so no sata_*, pata_* drivers Here are the drivers in the test version listed as kernel modules: The old thread as reference !!! especially read "Other things good to know about DS918+ image and loader 1.03a2:" its still valid for 1.04b loader !!! This section is about drivers for ds3615xs and ds3617xs image/dsm version 6.2.2 (v24922) Both use the same kernel (3.10.105) but have different kernel options so don't swap or mix, some drivers might work on the other system some don't at all (kernel oops) Its a test version and it has limits in case of storage support, read careful and only use it when you know how to recover/downgrade your system !!! do not use this to update when you have a different storage controller then AHCI, LSI MPT SAS 6Gb/s Host Adapters SAS2004/SAS2008/SAS2108/SAS2116/SAS2208/SAS2308/SSS6200 (mpt2sas) or LSI MPT SAS 12Gb/s Host Adapters SAS3004/SAS3008/SAS3108 (mpt3sas - only in 3617), instead you can try a fresh "test" install with a different usb flash drive and a empty single disk on the controller in question to confirm if its working (most likely it will not, reason below) !!! The reason why 1.03b loader from usb does not work when updating from 6.2.0 to 6.2.2 is that the kernel from 6.2.2 has different options set witch make the drivers from before that change useless (its not a protection or anything), the dsm updating process extracts the new files for the update to HDD, writes the new kernel to the usb flash drive and then reboots - resulting (on USB) in a new kernel and a extra.lzma (jun's original from loader 1.03b for dsm 6.2.0) that contains now incompatible drivers, the only drivers working reliable in that state are the drivers that come with dsm from synology Beside the different kernel option there is another thing, nearly none of the new compiled scsi und sas drivers worked They only load as long as no drive is connected to the controller. ATM I assume there was some changes in the kernel source about counting/indexing the drives for scsi/sas, as we only have the 2.5 years old dsm 6 beta kernel source there is hardly a way to compensate People with 12GBit SAS controllers from LSI/Avago are in luck, the 6.2.2 of 3617 comes with a much newer driver mpt3sas then 6.2.0 and 6.2.1 (13.00 -> 21.00), confirmed install with a SAS3008 based controller (ds3617 loader) Driver not in this release: ata_piix, mptspi (aka lsi scsi), mptsas (aka lsi sas) - these are drivers for extremely old hardware and mainly important for vmware users, also the vmw_pvscsi is confirmed not to work, bad for vmware/esxi too Only alternative as scsi diver is the buslogic, the "normal" choice for vmware/ESXi would be SATA/AHCI I removed all drivers confirmed to not work from rc.modules so they will not be loaded but the *.ko files are still in the extra.lzma and will be copied to /usr/modules/update/ so if some people want to test they can load the driver manually after booting These drivers will be loaded and are not tested yet (likely to fail when a disk is connected) megaraid, megaraid_sas, sx8, aacraid, aic94xx, 3w-9xxx, 3w-sas, 3w-xxxx, mvumi, mvsas, arcmsr, isci, hpsa, hptio (for some explanation of what hardware this means look into to old thread for loader 1.02b) virtio driver: i added virtio drivers, they will not load automatically (for now), the drivers can be tested and when confirmed working we will try if there are any problems when they are loaded by default along with the other drivers they should be in /usr/modules/update/ after install To get a working loader for 6.2.2 it needs the new kernel (zImage and rd.gz) and a (new) extra.lzma containing new drivers (*.ko files) zImage and rd.gz will be copied to usb when updating DSM or can be manually extracted from the 6.2.2 DSM *.pat file and copied to usb manually and that's the point where to split up between cases/way's case 1: update from 6.2.0 to 6.2.2 case 2: fresh install with 6.2.2 or "migration" (aka upgrade) from 6.0/6.1 Case 1: update from 6.2.0 to 6.2.2 Basically you semi brick your system on purpose by installing 6.2.2 and when booting fails you just copy the new extra.lzma to your usb flash drive by plugging it to a windows system (witch can only mount the 2nd partition that contains the extra.lzma) or you mount the 2nd partition of the usb on a linux system Restart and then it will finish the update process and when internet is available it will (without asking) install the latest update (at the moment update4) and reboot, so check your webinterface of DSM to see whats going or if in doubt wait 15-20 minutes check if the hdd led's are active and check the webinterface or with synology assistant, if there is no activity for that long then power off and start the system, it should work now Case 2: fresh install with 6.2.2 or "migration" (aka upgrade) from 6.0/6.1 Pretty much the normal way as described in the tutorial for installing 6.x (juns loader, osfmount, Win32DiskImager) but in addition to copy the extra.lzma to the 2nd partition of the usb flash drive you need to copy the new kernel of dsm 6.2.2 too so that kernel (booted from usb) and extra.lzma "match" You can extract the 2 files (zImage and rd.gz) from the DSM *.pat file you download from synology https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3615xs_24922.pat or https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3617xs_24922.pat These are basically zip files so you can extract the two files in question with 7zip (or other programs) You replace the files on the 2nd partition with the new ones and that's it, install as in the tutorial In case of a "migration" the dsm installer will detect your former dsm installation and offer you to upgrade (migrate) the installation, usually you will loose plugins, but keep user/shares and network settings DS3615: extra.lzma for loader 1.03b_mod ds3615 DSM 6.2.2 v0.5_test http://s000.tinyupload.com/?file_id=87576629927396429210 DS3617: extra.lzma for loader 1.03b_mod ds3617 DSM 6.2.2 v0.5_test http://s000.tinyupload.com/?file_id=80273327432412263889

Hi guys, today i have found the new loader for DS1019+on the Chainise forum. Does Anybody have access to it?? Please use the following links: Gebi1-> http://www.gebi1.cn/thread-294293-1-1.html http://www.gebi1.cn/thread-294290-1-1.html Thanks in advice.

15 - What is RAIDF1 and why would I want to use it? RAIDF1 a modification of RAID5, implemented with a customization of MDRAID (the disk array manager used by DSM). It is specifically tuned to minimize the likelihood of SSDs wearing out at the same time. SSDs have a finite lifespan based on the number of times they are written. This information is usually presented as a "wear indicator" or "life remaining" number from 100 (new) counting down to 0 (end of service life). Most operating systems, including DSM, monitor SSD health using SMART and will alert when devices near the end of their service lives, and prior to failure. An array of brand new SSDs are consumed evenly because of how RAID5 intentionally distributes workloads evenly to the array members. Eventually, the SSDs all wear out together, which can result in multiple, simultaneous drive failures and subsequent data loss. How does RAIDF1 work? RAIDF1 attempts to avoid this by biasing writes to a specific drive in the array. To understand this, consider how the DSM btrfs and ext4 filesystems store data. By default, DSM filesystems save data in 4K blocks. Even a 1-byte file uses 4K as a minimum amount of space. Modern HDDs/SSDs also store data in 4K sectors. When a byte must be changed, all the other bytes within the sector are read, then rewritten at the same time. This read/write requirement is called write amplification and it affects the performance of all parts of the storage ecosystem, from HDDs and SSDs to filesystems to RAID arrays. MDRAID also works with blocks, but they are called chunks to differentiate them from filesystem blocks. The default chunk size for DSM RAID5/6/10 is 64K. A stripe is the logical grouping of adjacent chunks spanning the array members horizontally. Using the example of a RAID5 with three drives, two of the chunks in the stripe contain data and the third chunk is parity. When DSM performs data scrubbing, it reads all three chunks, then validates all the data and parity in each stripe for mathematical consistency (and corrects if necessary). Each stripe rotates the position of the parity block successively through the array members. In the three-drive example, stripe 1's parity chunk is on drive 1, stripe 2's parity chunk is on drive 2, stripe 3's parity chunk is on drive 3, stripe 4's parity chunk is back on drive 1, and so on... This results in an even distribution of data and parity across all array members. Note that many files (filesystem blocks) may be stored in one chunk. The highest density case is 16 files of 4K or smaller in a single chunk. Consider that when one of those files change, only two of the three chunks in the stripe must be rewritten: first, the chunk containing the block containing the file, and then the parity chunk (since the parity calculation must be updated). RAIDF1 subtly modifies the RAID5 implementation by picking one of the array members (let's call it the F1-drive), and sequencing two consecutive stripes in the stripe parity rotation for it. This is NOT additional parity (each stripe still only has one parity chunk), so there is no loss of space or read/write performance. The table below compares parity distribution (how much of the total parity is stored on specific array members) between RAID5 and RAIDF1: Array configuration Drive #1 parity Drive #2 parity Drive #3 parity Drive #4 parity Drive #5 parity 3-drive RAID5 33.33% 33.33% 33.33% 4-drive RAID5 25% 25% 25% 25% 3-drive RAIDF1 25% 25% 50% (F1-drive) 4-drive RAIDF1 20% 20% 20% 40% (F1-drive) 5-drive RAIDF1 16.66% 16.66% 16.66% 16.66% 33.33% (F1-drive) With RAIDF1, anytime a full stripe is written, I/O is evenly distributed among the drives, just like RAID5. When a small file or file fragment (one that does not span a stripe) is written, on average the F1-drive will be used about twice as often as the other drives. Thus, the F1-drive will experience accelerated wear and will reach its life limit first. Then it can be replaced with minimal risk of one of the remaining members failing at the same time. Upon replacement, DSM selects the SSD that is closest to being worn out and designates it as the new F1-drive. The array sync then rewrites the array to achieve the desired RAIDF1 parity distribution. Note that the total number of write events are not increased with RAIDF1. "Total cost of ownership" does not change, as the extra writes to the F1-drive are avoided with the other array members, so they last longer. Caveats and other notable issues As a RAID5 variant, RAIDF1 creates arrays based on the smallest member device. For best results, all the drives should all be the same size and type (a larger drive can be used but extra space will be ignored). RAIDF1 can theoretically be “defeated” by installing dissimilar drives, with one drive having significantly higher capacity and/or a high DWPD (drive writes per day) rating. If this drive was then selected as the F1-drive, it may have enough write capacity to outlast the other array members, which could then fail together. Always using identical SSDs for the array will avoid this freak occurrence. SHR (Synology Hybrid RAID) allows drives of different sizes to be used in a redundant array while maximizing space available. This is done by creating a series of arrays, including a small one compatible with the smallest drive, and a large one using the available space common to the largest drives, and possibly some in between depending upon the makeup and complexity of the SHR. The arrays are then concatenated into a single logical volume (using LVM) available for use within DSM. For redundancy, the large SHR drives must be members of all the arrays. The small SHR drives contain only one array and not much of the overall data, and are accessed much less frequently than the larger drives. For RAIDF1’s algorithm to produce expected results, array write patterns must be simple and predictable. In summary, RAIDF1 and SHR array behaviors are not compatible with each other, which is reflected in the Synology DiskStation product lines. The Synology models that support RAIDF1 are the same as those that do not officially support SHR. This includes the XPEnology-enabled DS3615xs+ and DS3617xs+ platforms. Note that SHR can be enabled on these platforms by modifying /etc.defaults/synoinfo.conf, with no impact to RAIDF1 functionality. The MDRAID modifications that enable RAIDF1 are compiled into the DSM kernel. The consumer-oriented DSM platforms do not contain those changes, including the XPEnology-enabled DS916+ and DS918+ platforms. Creation and maintenance of a RAIDF1 is not possible on those systems. However, just like SHR, an established RAIDF1 array is completely functional and behaves like any other RAID5 array when migrated to a platform that does not support it. Brilliant! TRIM helps minimize the impact of write amplification on SSDs. Because the F1-drive is written to more frequently, it will be affected by write amplification more severely than the other array members, and performance of both the drive and the array will degrade over time unless TRIM support is enabled. Finally, there is no RAID6-based, SSD-optimized choice yet. Perhaps RAIDF2 will be an option in DSM 7.0. References If you want to install RAIDF1 on XPEnology, you will find a simple tutorial here https://en.wikipedia.org/wiki/Standard_RAID_levels https://global.download.synology.com/download/Document/Software/WhitePaper/Firmware/DSM/All/enu/Synology_RAID_F1_WP.pdf http://wiki.linuxquestions.org/wiki/Block_devices_and_block_sizes https://raid.wiki.kernel.org/index.php/RAID_setup#Chunk_sizes https://raid.wiki.kernel.org/index.php/A_guide_to_mdadm https://www.synology.com/en-sg/knowledgebase/DSM/tutorial/Storage/Which_Synology_NAS_models_support_RAID_F1 https://www.synology.com/en-us/knowledgebase/DSM/tutorial/Storage/Which_models_have_limited_support_for_Synology_Hybrid_RAID_SHR https://en.wikipedia.org/wiki/Trim_(computing)

Попробовал на тесте с "0", да работает, так и транкодирование тоже работает ))

the download link works and there are 2 img files you can inspect by opening it with 7z edit: i took the freedom and incorporated your russian article in english too

This is nice work, and thank you for your contribution. For those who aren't familiar with patching binary files, here's a script to enable nvme support per this research. It must be run as sudo and you should reboot afterward. Note that an update to DSM might overwrite this file such that it has to be patched again (and/or can't be patched due to string changes, although this is unlikely). Your volume might appear as corrupt or not mountable until the patch is reapplied. To be very safe, you may want to remove the cache drive from the volume prior to each update. #!/bin/ash # patchnvme for DSM 6.2.x # TARGFILE="/usr/lib/libsynonvme.so.1" PCISTR="\x00\x30\x30\x30\x30\x3A\x30\x30\x3A\x31\x33\x2E\x31\x00" PHYSDEVSTR="\x00\x50\x48\x59\x53\x44\x45\x56\x50\x41\x54\x48\x00\x00\x00\x00\x00\x00" PCINEW="\x00\x6E\x76\x6D\x65\x00\x00\x00\x00\x00\x00\x00\x00\x00" PHYSDEVNEW="\x00\x50\x48\x59\x53\x44\x45\x56\x44\x52\x49\x56\x45\x52\x00\x00\x00\x00" # [ -f $TARGFILE.bak ] || cp $TARGFILE $TARGFILE.bak if [ $? == 1 ]; then echo "patchnvme: can't create backup (sudo?)" exit fi COUNT=`grep -obUaP "$PCISTR" $TARGFILE | wc -l` if [ $COUNT == 0 ]; then echo "patchnvme: can't find PCI reference (already patched?)" exit fi if [ $COUNT -gt 1 ]; then echo "patchnvme: multiple PCI reference! abort" exit fi COUNT=`grep -obUaP "$PHYSDEVSTR" $TARGFILE | wc -l` if [ $COUNT == 0 ]; then echo "patchnvme: can't find PHYSDEV reference (already patched?)" exit fi if [ $COUNT -gt 1 ]; then echo "patchnvme: multiple PHYSDEV reference! abort" exit fi sed "s/$PCISTR/$PCINEW/g" $TARGFILE >$TARGFILE.tmp if [ $? == 1 ]; then echo "patchnvme: patch could not be applied (sudo?)" exit fi sed "s/$PHYSDEVSTR/$PHYSDEVNEW/g" $TARGFILE.tmp >$TARGFILE if [ $? == 1 ]; then echo "patchnvme: patch could not be applied (sudo?)" exit fi echo "patchnvme: success" rm $TARGFILE.tmp 2>/dev/null

Hi! I made a little tool which can help you to get your XPEnology up & running without installing any software. It contains (as portable versions): - Nirsoft's USB device view (helps to identify the VID & PID of your USB boot media) - V2.76 - XPEnology Serial Generator for DS3615XS, DS3617XS and DS916+ (a converted version of the HTML site) - Win32 DiskImager (to write your modified synoboot.img to your USB boot media) - V1.0 (only available in V1.4.1) - OSFMount x64 (to mount the synoboot.img and modifiy it) - V1.5 - Notepad++ (best editor for changing values inside grub.cfg) - V7.5.3 - Synology Assistant (useful tool from Synology to find your XPEnology and install DSM) - V6.2-23733 - TFTP/DHCP portable (a small TFTP, DHCP and Syslog server by Ph. Jounin) - V4.6.2 - MiniTool Partition Wizard 10 (helps assigning already formatted/written USB devices to modify existing grub.cfg) - V10.3 - SoftPerfect Network Scanner - V6.2.1 - USB Image Tool - V1.75 - New: Rufus - V3.3 In the section "Downloads" all links open corresponding websites to download the files. For beginners I added a small HowTo for bare-metal installation. Update New link for download: https://mega.nz/#F!BtViHIJA!uNXJtEtXIWR0LNYUEpBuiA The download link/folder also contains @IG-88's extra.lzma (V0.6) for the DS918+. You'll have to run it "As Administrator" because some of these tools (like Win32 DiskImager) need to be executed with higher rights. It's possible that the SmartScreen filter will give you a warning, because the EXE isn't signed. Bug reports and comments are welcome Cheers Current version: V1.4.2 (2018-11-19)

Before you begin to change something in your working system, it is strongly recommended to make backups of your most valuable data, so you do not regret about their irretrievable loss. Everything you do is your fear and risk, no one encourages you to do it. The easiest and most reliable way to safely try to do it, turn off all the disks and the boot flash drive from the current system, take a clean disk and another USB flash drive and try to install a new version of the bootloader and the system, if it rolled, then do already on the current system. 1. How to install (described for a computer with Windows): a) download the 1.04 b boot loader image (the original theme is here), create a directory in the root of the disk, for example, c:/918/ and put the bootloader image there b) determine the VID/PID of the flash drive or card reader into which it is inserted (control Panel-Device Manager-USB Controllers-Your flash drive/reader-Properties-Information-hardware ID, you need to ensure that the DSM system recognizes this disk and does not try to install itself on it, if you incorrectly define and register these parameters, the istall process will crash by mistake 13) c) download, install and run the OSFmount program, mount Partition 0 (15 Mb) from the bootloader file, remove the "Read-only drive" checkbox before mounting d) download, install and run Akelpad, open grub/grub file.cfg on previously mounted disk, edit and save: set vid=0xA234 #VID flash drive/reader set pid=0xB678 #PID of flash drive/reader set sn=1780PDN123456 #sn set mac1=001132123456 #mac of the first network card set mac2=001132123457 #mac of the second network card, the second and subsequent differ from the first by +1 in the last bit in the hex system ... set netif_num=2 #number of network cards ... set sata_args= 'SataPortMap=6' # sata controller, values: 6 - 1 controller on 6 ports; 22-2 controllers on 2 ports; 42-2 controllers, the first on 4 ports, the second on 2, etc. Where to get sn and mac - is your headache, Google will help you, the system will be installed and will work with those that are initially registered in the bootloader, but with the restriction of the functioning of some services and modules, such as: QC, push notifications, activation of codecs for transcoding, installation of syno licenses... e) unmount the disk in OSFmount f) download, install and run the Rufus program and record the previously prepared image on a flash drive g) insert the flash drive into the computer on which you plan to run xpen, connect the drives, turn on the power h) disable the firewall in the anti-virus, in the browser type http://find.synology.com or install Synology Assistant from the syno website and find the newly installed xpen on your network j) install DSM following the instructions of the installation program and start setting up (how to do it here is not described, because all the answers are in the syno knowledge base) There is a utility where the main programs for Windows x64 are collected 2. Transcoding (needs sn and mac from real syno hardware) Most likely to run on Intel processors starting from the 4th generation (Haswell), but there are nuances with motherboard models and BIOS. Check as follows: hardware (hw) transcoding - at the root of the system should be a directory /dev/dri with subdirectories in it, if not, but there is no HW transcoding to check - look for the directory with the terminal/ssh command cd /dev/dri . software (sw) transcoding - some codecs must run in DSM, you can check it with the command in the terminal / ssh cat /usr/syno/etc/codec/activation.conf If the result is the same, sw transcoding will ran {"success":true,"activated_codec":["h264_dec","h264_enc","mpeg4part2_dec","hevc_dec","aac_dec","aac_enc","ac3_dec","vc1_dec","vc1_enc"],"token":"123456789987654abc"} If there is nothing similar, there is no sw transcoding. 3. Perhaps the most optimal budget solutions with transcoding will be the following: ASRock J4105-ITX Asrock J5005-ITX Who wants more - use mb with the latest generation of Intel processors with Intel i210 or realtek 8111 . But this is already determined by the size of the your wallet and the functionality that you additionally want to get from xpen. P.S. Sorry for my english 😂

Also be sure you are setting up Legacy BIOS boot (not UEFI) with 1.03b. See more here: https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

I would expect that motherboard to run 1.03b and associated DSM platform well. Make sure you are building your system and connecting with the gigabit port first. Also, try DS3615xs instead of DS3617xs. You don't need the cores support of DS3617xs.

Практически обычным способом, описанным в руководстве по установке 6.x (загрузчик jun 1.03b, osfmount, Win32DiskImager), но в дополнение к копированию extra.lzma во второй раздел флэш-накопителя usb необходимо скопировать новое ядро dsm. 6.2.2 тоже, чтобы ядро (загруженное с usb) и extra.lzma "соответствовали" Вы можете извлечь 2 файла (zImage и rd.gz) из файла DSM * .pat, загруженного из Synology. https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3615xs_24922.pat Это в основном zip-файлы, поэтому вы можете извлечь эти два файла с помощью 7zip (или других программ) Вы заменяете файлы на 2-м разделе новыми и все, устанавливаете как в руководстве В случае «миграции» установщик dsm обнаружит вашу прежнюю установку dsm и предложит вам обновить (перенести) установку, обычно вы потеряете плагины, но сохраните настройки пользователя / общих ресурсов и сети

Xpenology doesn't need a video card at all. The monitor is only needed for setting BIOS parameters on mb.

Ton chipset réseau est un Broadcom 5751 qui effectivement n'a jamais été mentionné sur ce forum! Je doute qu'il soit compatible, donc : soit comme le suggère EVOTk tu tentes sur un disques vierge à part, soit tu restes telquel, soit tu investis dans un carte réseau Intel, soit tu virtualises, mais vu l'age du GX520 je ne pense pas que ça vaille le coup!

kernel modules/drivers are specifically compiled for a kernel (-versions) and even distributions it's not like windows where you can download a driver somewhere and just put it in so don't take any *.ko file, stick it in and expect it to work if you haven't build the *.ko yourself or don't know exactly where it came from, expect it to fail I'm no expert but as there is no how-to here in the forum - lets start one hopefully other will correct and help refine or take over and rewrite it some steps are made in windows (osfmount) but will also possible in the chroot environment on linux basic knowledge about using a linux console and command-line tools (or midnight commander) is needed, if you never used this you should not start with this how-to, choose something easier or invite someone who is able to help (do a workshop) doing all this from scratch will take at least 1-2 hours, in most cases (re-read, google, try, google, try again, ...) much longer, maybe plan a weekend of text-adventure fun edit: i think it also will do for 6.0.2 and loader 1.01 (not tested), kernel sources are available: https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/8451branch/bromolow-source/linux-3.10.x.txz/download, extra.lzma is a little differently placed (boot.img\image\DS3615xs\) but the steps will be the same 1. building the kernel module (driver) 1.1 what driver/module i need you will have to find out (google) what the name of the driver/module is that your hardware needs or you will have to know where to find the rigt option in the menu-system of the kernel when configuring it example: nForce 630 chipset with RTL8211E, you might expect it to be a realtek driver like rtl*.ko but it's not its "forcedeth.ko" because the RTL8211 is not a fully working PCIe Network Chip in some cases you might be forced to find out by booting a linux distribution and look in /var/log/, use lspci or other tools it also helps if the hardware provider has already compiled packages for specific distributions like redhat, you can look inside these packages for *.ko files you also can look in the .config file of the kernel (more below) with a text editor to find a section where the module is mentioned, this will also give you a hint where to find it in the menu-system when configuring the kernel 1.2 you need the kernel source in the case of synology that seemed sometimes difficult but at the moment there is kernel source for dsm 6.1 https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/ 15047 is the synology build version and tells you about what dsm version it is (15057 = dsm 6.1) and what kernel was used to build the modules, it !!!might!!! change in a later version so always check for what version your bootloader from usb stick is made for (jun 1.02 is for 15047) edit: dsm 6.1.1 has a new build number 15101 but seems to use the same kernel 3.10.102 as 6.1 so it should work with 6.1.1 too as i write this for ds3615xs it's bromolow as a platform, for ds3617xs it's broadwell and ds916+ is braswell (you usually see that name on the update files for a synology system like "synology_broadwell_3617xs.pat") so for ds3615xs we use this: https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/15047branch/bromolow-source/linux-3.10.x.txz/download edit: it looks like as for building the modules there is no difference for kernels modules build for 3615 and 3617 even if https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/15047branch/ has extra kernel sources for bromolow and broadwell, there are all intel x86_64, same might go for the 916+ (not testet yet), at least a evdev.ko build from 3615 kernel source did load without problems in a vm with the 3617 image 1.3 setting up a DSM 6.1 ds3615xs test environment with virtualbox (its free) or whatever works with juns loader look in the forum to find something that works, basics for virtualbox are - mac of the nic (intel pro 1000 desktop) in vm and grub.conf need to be the same - boot controller for jun's image (vmdk with reference to img file) is ide, controller for dsm disks is scsi lsi (!!!) - choose esx server option in grub menu 1.4 installing chroot put in http://packages.synocommunity.com for custom packages and change the setting that beside synology packages trusted ones are also to install install debian-chroot plugin (https://synocommunity.com/package/debian-chroot) from community section (some info's about it: https://github.com/SynoCommunity/spksrc/wiki/Debian-Chroot#configure-services) you might also install midnight commander if you are on it, makes things easier if you're not a command-line junky and more used to a graphical environment that give you clues activate ssh in dsm connect with ssh/putty to you dsm, login with user admin (and if you want to be root use "sudo -i") start the chroot with: /var/packages/debian-chroot/scripts/start-stop-status chroot after that you are inside the chroot, check with ls and you won't see "/volume1" or other sysnology specific directory's from the dsm environment, you can leave the chroot environment with "exit" later if you want now we have to update and install tools: apt-get update apt-get upgrade apt-get install locales dpkg-reconfigure locales dpkg-reconfigure tzdata apt-get install mc make gcc build-essential kernel-wedge libncurses5 libncurses5-dev libelf-dev binutils-dev kexec-tools makedumpfile fakeroot linux-kernel-devel lzma bc after that we create a directory (lets say "test") 1.5 copying kernel files and create kernel modules copy the downloaded kernel (linux-3.10.x.txz) to a share on the dsm, open a 2nd putty and copy the linux-3.10.x.txz (/volume1/...) to /volume1/@appstore/debian-chroot/var/chroottarget/test/ (that's where the "test" directory of the chroot environment is located in your real system) change back to your first putty where you are in chroot (the same way can be used to get the created files back to your shared folder on your volume1 which can be accessed from windows) change into "test", extract the linux-3.10.x.txz to a directory named "linux-3.10.x" and change into it the following copy's the kernel config file from synology to the right place for use/build cp synoconfigs/bromolow .config we make a fallback copy make ARCH="x86_64" oldconfig we start the ascii art menu and search for the missing driver to activate cursor/return are your friend in navigating, space selects, we activate the driver to an "M" so its build as module (*.ko file we need) there will be tons of descriptions how to do it, just google if needed make ARCH="x86_64" menuconfig on exit we save the configuration and with the following we make/create the modules (will take a while) make ARCH="x86_64" modules now you have to find your *.ko file (use some nice ls options, to be expanded later) usually you will have to look in /test/linux-3.10.x/drivers/scsi or block copy that file to /test for easy access when we put it in the boot image 2. modify the "synoboot.img" use osfmount (windows) to extract the "extra.lzma" (see dsm 5.2 to 6.0 guide, used there to edit grub.cfg in synoboot.img) in "extra.lzma" are the additional *.ko files and a config file where the files to be loaded on boot are named -> see forum thread "dsm 5.2 to 6.0" with howto to modify jun's loader for usb vid/pid and mac, its basically the same you just open the other partition (30MB) and extract the "extra.lzma" copy the "extra.lzma" to the share of the dsm so we have local access in a putty session on dsm in putty session #2 ("normal" session without chroot) we copy the "extra.lzma" to the "test" directory in the chroot environment go to putty session#1 (in chroot) decompress "extra.lzma" to "extra" ("extra.lzma" is a compressed cpio file) with: lzma -d extra.lzma with ls we can check that "extra.lzma" is now just ""extra" (a cpio file without the extension cpio) create a new directory, copy the "extra" there, change into it and extract it with: cpio -idv < extra delete the remaining file "extra" inside this directory we copy the *.ko file into usr/lib/modules/ and in /etc we edit the file rc.modules (easy with midnight commander, go to file, press F4, internal editor) network drivers seems to be added under EXTRA_MODULES, storage drivers under DISK_MODULES, just go to the end of the line and fill in the name of the *.ko file without the ".ko", what you add is basically a blank and the name rc.modules looks like this: EXTRA_MODULES="mii mdio libphy atl1 atl1e atl1c alx uio ipg jme skge sky2 ptp_pch pch_gbe qla3xxx qlcnic qlge netxen_nic sfc e1000 pcnet32 vmxnet3 bnx2 libcrc32c bnx2x cnic e1000e igb ixgbe r8101 r8168 r8169 tg3 usbnet ax88179_178a button evdev ohci-hcd" DISK_MODULES="BusLogic vmw_pvscsi megaraid_mm megaraid_mbox megaraid scsi_transport_spi mptbase mptscsih mptspi mptsas mptctl ata_piix megaraid_sas mpt2sas mpt3sas" EXTRA_FIRMWARES="bnx2/bnx2-rv2p-09ax-6.0.17.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-06-6.0.15.fw tigon/tg3_tso5.bin tigon/tg3_tso.bin tigon/tg3.bin" if your controller or nic needs a firmware, you add the file under usr/lib/modules/firmware/ and add the appropriate line in EXTRA_FIRMWARES, if a extra directory inside "firmware" is used it has to be added to the name, see the bnx2 firmware files after everything is in place we recreate the cpio file, re-compress it as lzma and write it in the directory above as "extra.lzma" the command is used inside the directory where we extracted the file "extra" (command line taken from https://github.com/kref/scripts, its what jun uses to create it): (find . -name modprobe && find . \! -name modprobe) | cpio --owner root:root -oH newc | lzma -8 > ../extra.lzma in putty session #2 (without the chroot) we copy "extra.lzma" from the chroot position in filesystem to the location where we can access it from windows if you still have osfmount open to the "synoboot.img" replace the "extra.lzma" with the new one, dismount and close osfmount - our new "synoboot.img" is ready to test it ps: i was asked to make a video - thats much harder to change and i'm to old for this

i guess not all drivers use that functionality maybe i won't then, on 2nd thought maybe dvb drivers tend to get exotic in a nas, now days we have internet, iptv and ip/sat (network tuner) i ditched my dvb recorder 2 years ago and and i dont miss it

Hmm, it turns out norecovery is not a valid option in Syno's compile of btrfs. Investigating.

Тема это импортная, и они нас переводами не балуют. Вот вроде основная тема

Я чутка про другое. D918+ DSM 6.1.2 23739 с этой версии dsm обновлялся на крайнюю. Вроде бы 6.2.2 тоже не взлетала сразу

99,9999999999% коряво прописали VID\PID в grub.cfg, проверьте.

Решил немного облегчить жизнь новичкам и тем, кто успел подзабыть, где и что лежит. 1. Ссылка на загрузчики от 5.0 до 6.2 2. Как установить на примере загрузчика 1.04b для DSM 6.2 (918+) 3. Совместимость загрузчиков 6.0-6.2 и железа 4. Тестирование и как проверить работает ли транскодинг на примере Asrock J4105-itx, там же сборка extra.lzma с гибернацией дисков 5. Как отредактировать grub.cfg и заменить extra.lzma на работающей хрени 6. Пакет для активации железной кнопки Power off на корпусе хрени (крайняя версия 6.2-0002, на нее и ссылка) 7. Корректное отображение процессора в Информационном центре 8. Librusec на хрени через COPS (скачивание в fb2 и mobi на читалку с wi-fi прямо с хрени) 9. Torrent TV через Ace Stream в docker (актуальные команды в посте ID 273, инструкция в следующем) Просьба ссылки тут не обсуждать, добавляйте свои, если посчитаете полезным.

Добрый вечер. DSM 5.2-5644 Update 5

Возможно стоит добавить какие то дрова....... А чем вызван выбор 918+ , ведь 3615 наиболее универсальная версия.

В декабре 2019 перешел на двухголовый huanan x79-16D. Плату покупал на авите, память на али, один проц достался на халяву, второй купил на ali. Сейчас у меня 44 ядра (88 потоков), 256 оперативы, нвороченный adaptec, 4xLAN недорогой hp (который по сути есть переименованный дорогой intel) и видеокарта. Переезд esxi и подключение виртуалок прошло без проблем. Потрудиться пришлось с opnsense из-за зоопарка сетевых интерфейсов. Что ещё нового: добавил терабайт m.2 как кэш в esxi; plex - отдал 64Г оперативы (у меня в нём много пользователей, все заметили ускорение проигрывания музыки), нарисовался касяк: бесплатная лицензия esxi позволяет добавить в вм только 8 ядер, а планировал 16. Засада! Теперь смотрю цены на esxi (если кто подскажет дельный совет по лицензии - буду премного благодарен). Изначально хотел поставить десятку на голое железо и посмотреть графики процессоров в диспетчере задач, но в процессе забыл про это дело...

@RangaWal Yes, the N40L has a Gb interface, make sure you have a good cable and that its well connected in both ends. Check the network status on your NAS: And also check any link LED's on your switch, to see if it says 1Gb active, might try another port?

/dev/md2 has a drive with an error state so do a mdadm --detail for each array when it's done, along with the /proc/mdstat. We aren't out of the woods yet. If everything is healthy, it probably doesn't matter. The point of booting to Ubuntu is when there is a boot problem on DSM - you can get to the files to fix whatever's wrong with DSM. I haven't ever heard of someone transporting a broken array over to Ubuntu for the purposes of fixing it. Not sure how that would be better than working with the same MDRAID in DSM.

does it make sense to create a repackaged loader (like a 1.03c or something) that is suitable for either fresh installs or upgrades to 6.2.2? The current way to create it/update it is convoluted and likely inaccessible to some folks.

Для примера, каждый блог по 4 знака в двоичном коде переводится в HEX и пишется в качестве параметра. Максимальное количество дисков берется из числа internalportcfg maxdisks="14" ... usbportcfg="0xff000" ... internalportcfg="0xfff" ... esataportcfg="0x300000" 0000 0000 0000 0000 0000 0011 0000 0000 0000 0000 0000 ==> eSata ports (2 drives) 300000 0000 0000 0000 0000 0000 0000 0000 0000 1111 1111 1111 ==> Sata ports (12 drives) fff 0000 0000 0000 0000 0000 0000 1111 1111 0000 0000 0000 ==> Usb ports (8 usb) ff000 P.S. Искать и менять значения параметров в файлах.

j'utilisais effectivement dd, sinon le docker de geekbench mais je ne me souviens plus s'il y avait un speed test des disques, je me dis que oui mais n'en ai pas souvenir. Un topic benchmark avait été créé ici-même. EDIT: pour des tests de vitesse entre le NAS et mon hackintosh, j'utilise Blackmagic Disk Speed Test qui a l'avantage d'être gratuit.

Железка ваша подойдёт.

Вам 918+ и не нужен тогда. Оставьте себе 3615 и не морочте себе голову. Разница только в реальном железе. Софт одинаковый.

Во как..... Что за Флешь такая своенравная...... ))) Там вроде просто всё. Почитайте на всякий случай Брали отсюда ? https://archive.synology.com/download/DSM/release/5.2/5644/ https://archive.synology.com/download/DSM/release/5.2/5644/DSM_DS3615xs_5644.pat

Загрузчик . Я использую 3615 - https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg!7AoyySoS Прошивка, файлы. Если со сторонней сетевой, то - https://archive.synology.com/download/DSM/release/6.2.2/24922/ Если с родной, то максимум это - https://archive.synology.com/download/DSM/release/6.2.1/23824/ По сетевой и настройки БИОС_а - Сетевая.... По сути, вроде бы любая с Интел чипсетом.

dvb drivers are not part of my package please open a new thread for this kind of problem you should ask the person who made this modules (presumably for dsm 6.2.0) if he is willing to redo the drivers for 6.2.2 i've already documented the change thats needs to be done when compiling new drivers for 6.2.2 https://xpenology.com/forum/topic/7187-how-to-build-and-inject-missing-drivers-in-jun-loader-102a/?do=findComment&comment=122631

Great work @IG-88!! Thanks to you I now have my HP ProLiant MicroServer Gen8 with DSM 6.2.2-24922 Update 4. Both built-in NICs are recognized and functional. I have done a fresh installation, simply replacing your files ('extra.lzma' -v0.5_test-, 'rd.gz' and 'zImage') on the 2nd partition (30MB) of Jun's Loader v1.03b (DS3615xs). But I have a problem that I can't solve and I need help: I have the PCI card DVBSky S952 v2. I have already compiled all the necessary modules that it needs. All load well except one, the last one that needs to be loaded: cx23885.ko When executing the 'insmod cx23885.ko' command, it keeps thinking for a while and a few seconds later returns this message: Killed. As I have seen here, to find out where it fails I have used the following command: dmesg And here is the problem: [ 5019.869526] cx23885 driver version 0.0.3 loaded [ 5019.869551] ------------[ cut here ]------------ [ 5019.869558] WARNING: at include/linux/kref.h:52 kobject_get+0x42/0x60() [ 5019.869559] Modules linked in: cx23885(OF+) dvbsky_m88ds3103(OF) snd_pcm snd_timer snd soundcore snd_page_alloc rc_core(OF) cx2341x(OF) v4l2_common(OF) videodev(OF) videobuf_dma_sg(OF) btcx_risc(OF) tveeprom(OF) videobuf_dvb(OF) videobuf_core(OF) tda18271(OF) altera_ci(OF) dvb_core(OF) bridge stp aufs macvlan veth xt_conntrack xt_addrtype nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE xt_REDIRECT xt_nat iptable_nat nf_nat_ipv4 nf_nat xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter ip_tables x_tables cifs udf isofs loop tcm_loop(O) iscsi_target_mod(O) target_core_ep(O) target_core_multi_file(O) target_core_file(O) target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) hid_generic [ 5019.869587] usbhid hid usblp bromolow_synobios(PO) xgmac(F) s2io(F) rtl8150(F) r8152(OF) plusb(F) pegasus(F) mcs7830(F) i40evf(OF) et131x(FC) cx82310_eth(F) asix(F) aqc111(OF) vxge(F) bna(F) cxgb4(F) cxgb3(F) cxgb(F) forcedeth(F) ixgb(F) e100(F) atl2(F) evdev(F) button(F) ax88179_178a(F) usbnet(F) tg3(OF) r8169(OF) r8125(OF) r8101(OF) ixgbevf(OF) igbvf(OF) bnx2(F) vmxnet3(F) pcnet32(F) e1000(F) sfc(F) netxen_nic(F) qlge(F) qlcnic(F) qla3xxx(F) pch_gbe(F) ptp_pch(F) sky2(F) skge(F) jme(F) ipg(F) uio(F) alx(F) atl1c(F) atl1e(F) atl1(F) libphy(F) mii(F) exfat(O) btrfs synoacl_vfs(PO) zlib_deflate hfsplus md4 hmac bnx2x(F) libcrc32c(F) mdio(F) mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) compat(O) qede(O) qed(O) atlantic(OF) r8168(OF) tn40xx(OF) i40e(OF) ixgbe(OF) be2net(F) igb(OF) i2c_algo_bit [ 5019.869622] e1000e(OF) dca(F) vxlan fuse vfat fat crc32c_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand acpi_cpufreq mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot crc_itu_t(F) crc_ccitt(F) quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram(C) sg etxhci_hcd nvme(F) hpsa(F) isci(F) arcmsr(F) mvsas(F) mvumi(F) 3w_xxxx(F) 3w_sas(F) 3w_9xxx(F) aic94xx(F) aacraid(F) sx8(F) mpt2sas(OF) megaraid_sas(F) megaraid(F) megaraid_mbox(F) megaraid_mm(F) BusLogic(F) usb_storage xhci_hcd uhci_hcd ohci_hcd(F) ehci_pci(F) ehci_hcd(F) usbcore usb_common cepsw(OF) [last unloaded: dvbsky_m88ds3103] [ 5019.869658] CPU: 0 PID: 24251 Comm: insmod Tainted: PF C O 3.10.105 #24922 [ 5019.869660] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 5019.869661] ffffffff814c5a5d ffffffff810355c6 ffff8800c5362008 ffff880105846098 [ 5019.869664] ffff880105846000 ffffffffa13f9040 ffff8800c5362008 ffffffff81275b42 [ 5019.869666] ffff8801058460a8 ffffffff8130655e ffffffffa0af13d5 ffff880105846090 [ 5019.869668] Call Trace: [ 5019.869674] [<ffffffff814c5a5d>] ? dump_stack+0xc/0x15 [ 5019.869677] [<ffffffff810355c6>] ? warn_slowpath_common+0x56/0x70 [ 5019.869680] [<ffffffff81275b42>] ? kobject_get+0x42/0x60 [ 5019.869684] [<ffffffff8130655e>] ? get_device+0xe/0x20 [ 5019.869689] [<ffffffffa0af13d5>] ? v4l2_device_register+0x55/0xf0 [videodev] [ 5019.869696] [<ffffffffa13dfe9a>] ? cx23885_initdev+0x4a/0x1170 [cx23885] [ 5019.869700] [<ffffffff8116c8d4>] ? sysfs_do_create_link_sd+0xc4/0x1f0 [ 5019.869703] [<ffffffff8129f810>] ? pci_device_probe+0x60/0xa0 [ 5019.869706] [<ffffffff8130aace>] ? driver_probe_device+0x7e/0x3e0 [ 5019.869709] [<ffffffff8130aeeb>] ? __driver_attach+0x7b/0x80 [ 5019.869712] [<ffffffff8130ae70>] ? __device_attach+0x40/0x40 [ 5019.869714] [<ffffffff81308b23>] ? bus_for_each_dev+0x53/0x90 [ 5019.869717] [<ffffffff8130a148>] ? bus_add_driver+0x1c8/0x280 [ 5019.869719] [<ffffffff8130b4d8>] ? driver_register+0x68/0x150 [ 5019.869726] [<ffffffffa13ff000>] ? 0xffffffffa13fefff [ 5019.869728] [<ffffffff8100038a>] ? do_one_initcall+0xca/0x180 [ 5019.869733] [<ffffffff8108b63c>] ? load_module+0x1d0c/0x2360 [ 5019.869737] [<ffffffff8128feb0>] ? ddebug_proc_write+0xe0/0xe0 [ 5019.869741] [<ffffffff810f9663>] ? vfs_read+0xf3/0x160 [ 5019.869744] [<ffffffff8108bdf5>] ? SYSC_finit_module+0x75/0xa0 [ 5019.869748] [<ffffffff814ccdc4>] ? system_call_fastpath+0x22/0x27 [ 5019.869749] ---[ end trace 9ed748a2788c3ee3 ]--- [ 5019.869756] BUG: unable to handle kernel NULL pointer dereference at (null) [ 5019.907575] IP: [<ffffffffa0af1403>] v4l2_device_register+0x83/0xf0 [videodev] [ 5019.942743] PGD c512e067 PUD e09c8067 PMD 0 [ 5019.963145] Oops: 0000 [#1] SMP [ 5019.978571] Modules linked in: cx23885(OF+) dvbsky_m88ds3103(OF) snd_pcm snd_timer snd soundcore snd_page_alloc rc_core(OF) cx2341x(OF) v4l2_common(OF) videodev(OF) videobuf_dma_sg(OF) btcx_risc(OF) tveeprom(OF) videobuf_dvb(OF) videobuf_core(OF) tda18271(OF) altera_ci(OF) dvb_core(OF) bridge stp aufs macvlan veth xt_conntrack xt_addrtype nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE xt_REDIRECT xt_nat iptable_nat nf_nat_ipv4 nf_nat xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter ip_tables x_tables cifs udf isofs loop tcm_loop(O) iscsi_target_mod(O) target_core_ep(O) target_core_multi_file(O) target_core_file(O) target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) hid_generic [ 5020.327357] usbhid hid usblp bromolow_synobios(PO) xgmac(F) s2io(F) rtl8150(F) r8152(OF) plusb(F) pegasus(F) mcs7830(F) i40evf(OF) et131x(FC) cx82310_eth(F) asix(F) aqc111(OF) vxge(F) bna(F) cxgb4(F) cxgb3(F) cxgb(F) forcedeth(F) ixgb(F) e100(F) atl2(F) evdev(F) button(F) ax88179_178a(F) usbnet(F) tg3(OF) r8169(OF) r8125(OF) r8101(OF) ixgbevf(OF) igbvf(OF) bnx2(F) vmxnet3(F) pcnet32(F) e1000(F) sfc(F) netxen_nic(F) qlge(F) qlcnic(F) qla3xxx(F) pch_gbe(F) ptp_pch(F) sky2(F) skge(F) jme(F) ipg(F) uio(F) alx(F) atl1c(F) atl1e(F) atl1(F) libphy(F) mii(F) exfat(O) btrfs synoacl_vfs(PO) zlib_deflate hfsplus md4 hmac bnx2x(F) libcrc32c(F) mdio(F) mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) compat(O) qede(O) qed(O) atlantic(OF) r8168(OF) tn40xx(OF) i40e(OF) ixgbe(OF) be2net(F) igb(OF) i2c_algo_bit [ 5020.665151] e1000e(OF) dca(F) vxlan fuse vfat fat crc32c_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand acpi_cpufreq mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot crc_itu_t(F) crc_ccitt(F) quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram(C) sg etxhci_hcd nvme(F) hpsa(F) isci(F) arcmsr(F) mvsas(F) mvumi(F) 3w_xxxx(F) 3w_sas(F) 3w_9xxx(F) aic94xx(F) aacraid(F) sx8(F) mpt2sas(OF) megaraid_sas(F) megaraid(F) megaraid_mbox(F) megaraid_mm(F) BusLogic(F) usb_storage xhci_hcd uhci_hcd ohci_hcd(F) ehci_pci(F) ehci_hcd(F) usbcore usb_common cepsw(OF) [last unloaded: dvbsky_m88ds3103] [ 5020.997978] CPU: 0 PID: 24251 Comm: insmod Tainted: PF WC O 3.10.105 #24922 [ 5021.033652] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 5021.068338] task: ffff88010598c040 ti: ffff8800e09bc000 task.ti: ffff8800e09bc000 [ 5021.104807] RIP: 0010:[<ffffffffa0af1403>] [<ffffffffa0af1403>] v4l2_device_register+0x83/0xf0 [videodev] [ 5021.152597] RSP: 0018:ffff8800e09bfc38 EFLAGS: 00010286 [ 5021.177959] RAX: 0000000000000000 RBX: ffff8800c5362008 RCX: 0000000000000006 [ 5021.213901] RDX: ffffffffa0afba5f RSI: 0000000000000024 RDI: ffff8800c5362022 [ 5021.247987] RBP: ffff880105846098 R08: ffffffff8183a600 R09: 000000000000fffe [ 5021.283746] R10: 0000000000000000 R11: 0000000000000459 R12: ffff880105846000 [ 5021.317977] R13: ffffffffa13f9040 R14: ffff8800c5362008 R15: ffffffffa13fa200 [ 5021.352947] FS: 00007ff7520eb700(0000) GS:ffff88010ba00000(0000) knlGS:0000000000000000 [ 5021.392514] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5021.419841] CR2: 0000000000000000 CR3: 00000000c464e000 CR4: 00000000001607f0 [ 5021.454973] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 5021.489549] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 5021.524634] Stack: [ 5021.534184] ffff880105846090 ffff8800c5362000 ffffffffa13dfe9a ffffffff8116c8d4 [ 5021.570823] 00000000ffffffff ffff880105846098 ffff880105846090 ffffffffa13f90a8 [ 5021.606562] ffff880105846000 ffffffffa13f9040 0000000000000001 ffffffffa13fa200 [ 5021.643598] Call Trace: [ 5021.655086] [<ffffffffa13dfe9a>] ? cx23885_initdev+0x4a/0x1170 [cx23885] [ 5021.687897] [<ffffffff8116c8d4>] ? sysfs_do_create_link_sd+0xc4/0x1f0 [ 5021.719379] [<ffffffff8129f810>] ? pci_device_probe+0x60/0xa0 [ 5021.747877] [<ffffffff8130aace>] ? driver_probe_device+0x7e/0x3e0 [ 5021.777623] [<ffffffff8130aeeb>] ? __driver_attach+0x7b/0x80 [ 5021.806853] [<ffffffff8130ae70>] ? __device_attach+0x40/0x40 [ 5021.834135] [<ffffffff81308b23>] ? bus_for_each_dev+0x53/0x90 [ 5021.862621] [<ffffffff8130a148>] ? bus_add_driver+0x1c8/0x280 [ 5021.890428] [<ffffffff8130b4d8>] ? driver_register+0x68/0x150 [ 5021.919177] [<ffffffffa13ff000>] ? 0xffffffffa13fefff [ 5021.944175] [<ffffffff8100038a>] ? do_one_initcall+0xca/0x180 [ 5021.971963] [<ffffffff8108b63c>] ? load_module+0x1d0c/0x2360 [ 5021.999276] [<ffffffff8128feb0>] ? ddebug_proc_write+0xe0/0xe0 [ 5022.027551] [<ffffffff810f9663>] ? vfs_read+0xf3/0x160 [ 5022.053584] [<ffffffff8108bdf5>] ? SYSC_finit_module+0x75/0xa0 [ 5022.082162] [<ffffffff814ccdc4>] ? system_call_fastpath+0x22/0x27 [ 5022.112424] Code: 48 89 2b 74 53 80 7b 1a 00 75 2a 4c 8b 45 50 4d 85 c0 74 64 48 8b 85 90 00 00 00 48 8d 7b 1a 48 c7 c2 5f ba af a0 be 24 00 00 00 <48> 8b 08 31 c0 e8 33 bb 78 e0 48 89 ef e8 eb 8e 81 e0 48 85 c0 [ 5022.204806] RIP [<ffffffffa0af1403>] v4l2_device_register+0x83/0xf0 [videodev] [ 5022.239300] RSP <ffff8800e09bfc38> [ 5022.255682] CR2: 0000000000000000 [ 5022.271686] ---[ end trace 9ed748a2788c3ee4 ]--- [ 5022.293644] [sched_delayed] sched: RT throttling activated But I don't know how to interpret all this code. If you could help me I would appreciate it very much ☺️ I THINK (but I don't know) the problem is because it conflicts with any of the new 6.2.2 drivers. Because in DSM 6.1 with Jun's Loader v1.02b (DS3615xs) everything works fine and I have no problems loading this module. I have searched and read some similar case in this forum and I think I have understood the same thing that I say, that there is a conflicting driver and if I delete it my module will work fine. For example in this thread you mention it: https://xpenology.com/forum/topic/24220-shutdownreboot-not-working/?do=findComment&comment=130036 The problem is that I have no idea what the conflicting module will be, to be able to erase it. In case it helps you, I attach a compressed file with all the necessary modules (and firmware) already compiled for DSM 6.2.X The correct order to load them is (remember that the problematic module is only the last one, but to load it depends on all the previous ones): insmod videobuf-core.ko insmod videobuf-dma-sg.ko insmod rc-core.ko insmod dvb-core.ko insmod altera-ci.ko insmod videodev.ko insmod v4l2-common.ko insmod cx2341x.ko insmod /lib/modules/soundcore.ko insmod /lib/modules/snd.ko insmod /lib/modules/snd-page-alloc.ko insmod /lib/modules/snd-timer.ko insmod /lib/modules/snd-pcm.ko insmod tveeprom.ko insmod videobuf-dvb.ko insmod btcx-risc.ko insmod tda18271.ko insmod dvbsky_m88ds3103.ko insmod cx23885.ko Thank you very much for your fantastic work! Regards! DVBSky-S952-v2_DSM-v6.2-bromolow.tar.gz

Нет не сбрасывает. Вообще можно взять стандартный биос от НР и самим подредактировать все что нужно, для этого и выложил редактор там можно выбрать любой параметр доступный в системе. Наверное надо так и сделать выложить стандартный биос с отключенным С1Е. Отправлено с моего MI 6 через Tapatalk

Да вроде всё несложно... Загрузчик под вашу версию - https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg!7AoyySoS Тут файлы Хрени. Так же выбирает под же: https://archive.synology.com/download/DSM/release/6.2.1/23824/ Тут как записать флешку : Для перестраховки, попробуйте обнову на чистом диске. Если никаких ошибок, то можно обновлять рабочие харды. Сделайте резервную копию конфигурации в Панели управления. Если какой сбой, всегда можно восстановиться. Ну а далее, система сама предложит обновление или миграцию. Если вдруг какие косяки возникли, достаточно удалить раздел : /etc.defaults и потом восстановиться из копии. Ну вот где то так или около того.... Если есть какая неясность, спрашивайте. Чем смогу, помогу

Download: 1. synoboot vmdk https://mega.nz/#!fdBWBJYB!P3MbGY2v_X_udUhaSgVBQZ74KNRf7vtjMCO39u1I91Y 2. juns loader for DSM 6.2 https://mega.nz/#F!ZlkHQTTb!keje3RK017OjTp3vuWb-Cw 3. synology DSM.pat for synology 3615xs https://www.synology.com https://archive.synology.com/download/DSM/release/ 4. open vm tools spk http://spk.4sag.ru/?fulllist=true 5. XPEnology Tool for Windows x64 PREPARATIONS unzip synoboot.vmdk from DS3615xs 6.0.2 Jun's Mod V1.01 (synoboot.vmdk works with 3615 and 3617 loaders) unzip synoboot.img from synoboot_3615 mount synoboot.img partition 0 with osf mount Make sure to uncheck Read-only drive Go to the mounted drive, Grub folder and edit grub.cfg with notepad++  If you want change default SN and mac1 comment boot option lines you dont need in esxi #menuentry "DS3615xs 6.2 Baremetal $VERSION" --class os { # set img= # savedefault # loadlinux 3615 usb # loadinitrd # showtips #} # #menuentry "DS3615xs 6.2 Baremetal $VERSION Reinstall" --class os { # set img= # loadlinux 3615 usb mfg # loadinitrd # showtips #} # #menuentry "DS3615xs 6.2 Baremetal AMD $VERSION" --class os { # set img= # set zImage=bzImage # savedefault # loadlinux 3615 usb # loadinitrd # showtips #} menuentry "DS3615xs 6.2 VMWare/ESXI $VERSION" --class os { set img= savedefault loadlinux 3615 sata loadinitrd showtips } save file, dismount all and exit. ESXi part: Upload synoboot.vmdk and synoboot.img to esxi (in one folder) Create new VM name the xpenology vm as you want and select Linux and Other 3.x Linux x64 select your storage and you should see customize settings now remove default disk remove scsi controller remove cd/dvd drive and if you are using 3617 loader you need to remove USB controller or change type to USB 3.0 now set cpu at 2 set memory 2GB change Network Adapter Type to E1000e set network adapter 1 mac addres you have in the grub.cfg for example 00:11:32:2C:A7:85 now add existing hard disk and point to the synoboot.vmdk uploaded before. Make sure its on SATA 0:0 now add another sata device and add vm disks to it (sata 1:0, 1:1 etc) and now, the vm is done and finish now start your VM and wait to see after few minutes open in new tab browser find.synology.com click connect accept EULA Set UP and manual install point to DSM 3615xs.pat file downloaded earlier after you confirm instalation you should see instalation progress after 10 minutes reboot enter username, password and server name for dsm skip configure quickconnect dont share location with synology (find.synology.com will not find virtual dsm) now DSM is ready This type of VM should work with dsm 6.2, 6.2.1, 6.2.2 and 3615xs/3617xs loaders

there would be no difference between 6.2.1 and 6.2.2. when using jun's normal extra.lzma drivers with 6.2.1 now as i'm using them in my new driver test version for 6.2.2 only things that make a difference atm is if you use jun's i915 driver at all or the one's coming with DSM (using real3x extra.lzma without jun's new i915 driver) i've done some documentation and J4105 (as J5005) would be a geminilake gpu (Intel UHD Graphics 600) using glk*.bin firmware and there is no refference in the original DSM i915.ko driver to that just bxt (apollolake), kbl (kabylake) and skl (skylake), as there only seems to be bxt firmware coming with 918+ dsm i guess only Intel HD Grraphics 500/505 based cpus will work ootb (J3xxx, J4200, J4205) people with network driver problems on 6.2.2 will have it solved with the new driver package but there are also other problems that might be wrong interpreted like when a system hangs because of load problems with i915 driver (in some cases its a monitor connected to the system, in some is it the lack of monitor connected in other even active vt-d in bios might be a problem) - symptom might be that it cant be found in network after boot but source has not to be the nic and i guess there are a lot of cases where its blamed to the nic and in reality its about gpu driver - its hard to see as there is no console to see the messages when booting (only few people are able to use the serial console to diagnose this) i dont expect to much success even with a new/better driver package i will release soon (there will be a version without new i915 drivers too) as most people don't understand the reasons to why the system does not show up in network (and in some cases people even miss to look in the network on the dhcp server to see that the system came up and wait on the screen for a message that never will come) - and even trying 3615/17 instead 918+ is not guaranteed to work, on my own new hardware i use for testing now the 3615/17 loader stops right after loading the kernel and not even gives a messages on the serial console

- Outcome of the update: SUCCESSFUL - DSM version prior update: Disks migration from DS3615xs/6.1.2/loader 1.02b - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: YES - Installation type: BAREMETAL - HP Gen8 Micro 12Gb i5 3470T - New install - Dell H310 w/LSI 9211-8i P20 IT Mode + extension Rack of SAS/SATA mixed HDD - Additional comments: Gen8 onboard Dual Broadcom NiC working (no need of additionnal NiC thanks to native drivers from IG-88)

Не переживай, все нормально. 😊

Ok Found out what the problem was... I read somewhere on the forum that sometimes there is problems when a monitor is connected... I disconnected it and it worked

I wouldn't bother with that CPU upgrade. Your current CPU is fine, I don't think you would be able to tell any difference. Cores are more important than hyperthreading. In regard to transcoding, the word simply refers to the action of transforming an audio/video stream from one output format to another. "Hardware" transcoding on Synology means that the transcoding software is leveraging Intel Quicksync instructions on the CPU, far faster than "software" transcoding which is just a program on the system (in most cases, FFMPEG). Software transcoding requires a lot of CPU, usually more than is available on Synology or XPenology systems. So many folks wants hardware transcoding so that they can watch their stored media in real-time on a variety of output devices without storing multiple copies. Video cards also perform hardware transcoding, but this is not supported at all in the DSM ecosystem. All that said... your entire hardware platform is unsuitable for transcoding due to age. You would need to build up a platform on a Haswell or later CPU and run the DS918+ version of DSM to even attempt it.

yes, also to consider is the power consumption and heat is produces (often equals noise level) having a system wasting 60 watt, 24h, 7days a week for years ... also xeon mainboards are often more expansive and ecc ram also adds to that beside virtualization as with VMM there is also docker, that seems to used a lot lately instead of synology specific packages, but in most cases more ram is far better then more cpu cores (there might be some cases where 4 cores is not enough when having multi user streaming with transcoding and lots o home automation vm's in background) just as file server and some streaming (without transcoding or using hardware support for transcoding) even a 2 core system can do it i've seen it be used as webserver for a online shop or lately one user had a 16 SSD's with a 40BGit nic hardware (i didn't wanted to be nosy so i did not ask what he wanted to do with it) i guess in most cases 4 cores of a 8 core system (in home use) are there just to make sure the owner has a better sleep, as long he is not concerned about global warming :-))) to small, to slow (i'm using a 12 disk system with 10G network) why? what about open media vault?

it does work on 3615/17 and also does on my current test version for 918+ (6.2.2) atm i'm using juns mpt3sas driver and i have no clue whey my compiled drivers do not work (kernel oops when drive is attached to controller) if we get no (recent) kernel source from synology and they alter things further then there might be no way for dsm versions that do not come with lsi support (like 918+) i got a 8 port ahci controller for my new build (additional network drivers seem to be no problem) https://xpenology.com/forum/topic/19854-sata-controllers-not-recognized/?do=findComment&comment=122709

С новым, 2020 годом вас друзья !!! Дорогие Друзья, форумчане..... С Русской ветки и с остальных, Многонациональных веток... Поздравляю вас с наступающим, да что там говорить, местами уже наступившим Новым годом. Желаю всем любви, мира в семье, понимания друзей и близких, благополучия. Хочется пожелать, чтобы всё задуманное и загаданное под бой курантов, обязательно сбылось. Пусть наши чувства друг к другу хоть и стары как мир и неизменны, но также сильны как и прежде ! Ну и что бы Хрень наша горячо любимая и местами обожаемая, радовала нас как прежде. Что бы Рейды не сыпались, что бы файлы прирастали мегабайтами нужными и всё заводилось с пол пинка ))) С новым годом вас всех !!! P.S Уважаемые модераторы, просьба перенести тему в раздел по назначению.

i can "offer" a HP DC7600 MT, bios does not offer AHCI mode and just SATA cant be used with xpe 6.2 (i still use it for testing with a 2port jmicron sata controlles that is ahci compatible) in some other cases the bios options to switch to ahci mode can be a little cryptic (had two cases like this) there are some rare cases where you cant switch to ahci even when the chipset does support it with the new extra.lzma for 1.03b and DSM 6.2.2 it should work (again) as it uses the latest intel drivers 1.04b for 918+ will get the same drivers soon if nothing special pops up in the process

Записываем загрузочную флешку. Редактируем grub.cfg программой OSFMount Начальная стадия установки DSM, это создание загрузочной флешки. После определения Хардового конфига (железо, его конфигурация) и дальнейших потребностей для себя от DSM, определяем версию DSM загрузчика под неё. На данный момент, имеется три версии загрузчика под разные эмуляции DSM , это : ds3615 , ds3617, ds918+ Под ds3615 , ds3617 - последний загрузчик v1.03 b Под ds918+ - последний загрузчик v1.04b Имеются и более ранние версии, всё зависит от вашей конфигурации и желаемого результата. Совместимость загрузчика и железа (возможно, список не полный): Все версии собраны здесь: https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg!7AoyySoS И так..... Определились с загрузчиком, начинаем его редактировать под себя и записываем на флешку. Нам необходимы, любая флешка от 128мб и установленные программы: OSFMount - небольшая бесплатная утилита, которая позволяет монтировать ранее сделанные образы дисков и представлять их в виде виртуальных приводов. Необходима для монтирования и последующей редакции образа загрузчика. https://www.osforensics.com/tools/mount-disk-images.html Notepad++ - свободный текстовый редактор с открытым исходным кодом для Windows. Необходима для редактирования grub.cfg https://notepad-plus-plus.org/ Rufus - это утилита, которая помогает форматировать и создавать загрузочные Flash. Необходима для записи загрузчика. https://rufus.ie/ Данные программы, кроме OSFMount, могут быть и другими, в зависимости от вашего предпочтения. Скачиваем необходимый вам загручик и открываем его в программе OSFMount, монтируем образ. Открываем ранее скачанный образ загрузчика Выбираем необходимый нам раздел. В нём находится нужный нам для редакции файл grub.cfg Обязательно снимаем галочку с опции: read only - только для чтения. Монтируем образ и открываем необходимый нам файл grub.cfg Редактируем в Notepad++ Редактируем значения: set vid=Ваш vid (обязательно) set pid=Ваш pid (обязательно) set sn=Ваш серийник set mac1=Ваш mac1 set mac1=Ваш mac2,3,4 (если сетевая карта имеет больше одного порта) Значения set sn и set mac можно оставить по дефолту, если ван не нужны такие функции, как транскодинг, Push уведомления и QuickConnect. Так же, необязательно, но лучше отредактировать значение: set timeout='1' - изменить значение "1" на другое, скажем на 5 или больше. Это значение отвечает на время видимости начального загрузчика из трёх пунктов. Многие не успевают прочесть то, что там написано. Изменение этого значения даст возможность увеличить время отображения начальной страницы Отредактировав под себя grub.cfg , сохраняем его и размонтируем образ Теперь можно записать загрузчик на флешку Открываем , выбираем наш, уже правленый образ загрузчика и записываем на флешку Ну вот и всё, загрузочная флешка готова. Можно начинать установку DSM Из личного опыта........ Всегда сохраняйте свой, правленый образ загрузчика. Всякое может случиться и всегда полезно иметь уже готовый для записи образ. Лично я, всегда делаю ДВЕ флешки. Тоже, на непредвиденный случай. 😉

Ce tuto est une mise à jour du tuto que j'ai déjà fait l'année dernière. Le tuto ci-dessous permet d'installer/migrer DSM 5.2 à DSM 6.1.7 directement sans devoir à passer par DSM 6.0.2. Si pour une raison ou une autre vous voulez migrer à DSM 6.0.2 d'abord ou alors tout simplement vous ne voulait pas migrer à DSM 6.1.7 mais souhaiter migrer à DSM 6.0.2 uniquement alors utilisez le lien ci dessus. Pour mettre à jour DSM 6.0.2 à DSM 6.1.7 voir ici. Comme la plupart de vous doivent déjà le savoir Jun a réussi un exploit en créant un loader permettant l'installation de DSM 6 sur du matériel non Synology. Voici le fil de la discussion pour ceux que ça intéressent: https://xpenology.com/forum/topic/6253-dsm-6xx-loader/. Il va vous falloir quelques outils. Je pars du principe que vous êtes sous Windows 10, 8, 7, Vista ou XP. Si vous êtes sur un MAC OS et que vous comprenez l'anglais réfèrerez vous au post que j'ai fait sur comment écrire et monter l'image sur une clef USB. Vous pouvez ensuite revenir sur ce tuto après avoir effectué les manips nécessaires sur MAC OS. Si vous avez des doutes n'hésitez pas à laisser un commentaire. Si vous êtes à DSM 5.1 ou sur une version antérieur, il faut tout d'abord mettre à jour DSM à la version 5.2. Si vous faites une installation fraîche de DSM 6.1 alors vous êtes bon pour la suite. Simplement omettez toute référence à DSM 5.2 Voici ce dont vous avez besoin: - Win32 Disk Imager. Application permettant de rendre une clef USB bootable. - Une clef USB que l'on utilisera pour y mettre le loader. 4GB suffiront largement. Je conseille une clef de marque (Kingston, SandDisk ou autre). Cela évitera les problèmes dans le future. - Comment connaitre le VID et PID de votre clef usb >>> voir ici - Un éditeur de texte avancé. Notepad++ fera l'affaire. L'éditeur de text Notepad inclu avec Windows est déconseillé. - DSM 6.1.4. Télécharger un des fichiers relatifs à un des 3 modèles suivant: DS3615sx ou DS3617sx ou DS916+. Télécharger uniquement le fichier avec l'extension ".pat" et non celui avec l'extension ".pat.md5". Les fichiers PAT viennent directement des serveurs de Synology, donc sans aucune altération. - Le loader (miroir) officiel v1.02b de Jun. Ce loader est hybrid c'est à dire qu'il marche en EFI ou BIOS donc il devrait marcher sur une majorité de machines capable de lire du GTP. Pour les machines plus vielles qui ne peuvent lire que du MBR ce loader ne marchera pas. Utilisez alors l'image du loader v1.02b faites par @Genesys construite à partir du loader de Jun mais faite avec une table de partitionnement de type MBR. Note: Le loader v1.02b de Jun est compatible avec les CPU Intel. Pour les CPU AMD cela n'est pas entièrement le cas mais plusieurs personnes ont mentionnée qu'il était possible d'utiliser ce loader. Il serait d'après eux nécessaire de désactiver la fonction C1E dans le BIOS (applicable aux machines HP comme le N40L ou N54L par exemple). Si vous avez un autre model/marque de machine AMD ne me demandez pas, je ne sais pas. Il faudra que vous regardiez dans le bios et fassiez des tests vous même. Partagez voter expérience ca en aidera surement d'autres. - Le ramdisk personnalisé extra.lzma. Ce ramdisk est optionnel et ne doit être utiliser que si le ramdisk par défaut inclus dans le loader ne permet pas la détection du matériel. Je le fourni pour ceux qui pourraient avoir des problèmes de détection réseau ou de contrôleurs de disques non reconnus. Ce ramdisk personnalisé contient des modules (drivers) additionnels qui ont été compilé par @IG-88 avec le code source de DSM 6.1.3. Je ne garantie pas qu'ils marchent tous. Vous devrez remplacer (ou renommer, au cas ou!) le ramdisk par défaut extra.lzma par celui ci. Si vous avez des questions spécifiquement liées au ramdisk de IG-88 merci de les poster directement dans le fil de discussion de IG-88, pas ici. - Faites attention à branchez vos HDD successivement en commençant par le premier port SATA normalement décrit comme SATA0 sur les cartes mères. Vérifiez avec le fabriquant de votre carte mère. Si vous faites une migration à partir de DSM 5.2 alors laissez tel quel. - OSFMount. Application permettant de modifier le fichier grub.cfg directement sur l'image. Ceci n'est pas strictement nécessaire car Jun a rendu possible la configuration du VID/PID, S/N et MAC directement à partir du Menu Boot Grub. Si vous préférez utiliser la nouvelle méthode il suffit d'omettre le Point 4, lisez plutôt la Note 4 et reprenez le tuto à partir du Point 5. SVP LISEZ TOUT LE TUTO AVANT DE FAIRE N'IMPORTE QUOI L'utilisation de ce loader relève de votre entière responsabilité. Ne me tenez pas responsable si vous perdez vos données ou que votre NAS part en fumée. Sachez aussi que ce loader contient moins de drivers que sous DSM 5.2 donc si il est primordiale pour vous d'avoir une machine opérationnelle h24 je vous conseille de lire en bas du tuto les drivers disponibles. Si votre module n'est pas inclus alors il vous faudra les compiler vous même ou utiliser le ramdisk personnalisé qui se trouve ci-dessus. Ne me demandez pas de compiler des modules à votre place, je ne le ferais pas. NE METTEZ PAS A JOUR DSM AU DELA DE LA VERSION 6.1.7 AVEC LE LOADER v1.02b. EN D'AUTRES TERMES NE METTEZ PAS A JOUR DSM A LA VERSION 6.2 A bon entendeur. Maintenant que vous avez tout ce qu'il vous faut, passons aux choses sérieuses: 1 - Faites un backup de vos données et de votre configuration avant toute chose. Cela évitera la pleurniche plus tard. Imprimez ce tuto si nécessaire. 2 - Eteignez votre NAS. Déconnectez votre clef USB avec votre loader 5.2. Je conseille que vous mettiez de coté la clef USB que vous utilisez actuellement avec DSM 5.2 et prenez une nouvelle clef USB pour DSM 6.1. Cela évitera de la refaire si l'upgrade ne marche pas pour vous et que vous avez besoin de revenir à DSM 5.2. 3 - Allez à votre PC, branchez votre clef USB et lancez votre application de choix permettant de voir le VID et PID de votre clef USB. Notez ça quelque part car vous en aurez besoin sous peu. 4 - Maintenant lancez OSFMount. Sélectionnez "Mount New", puis choisissez votre loader (fichier au format .img) dans "Image File". Une autre fenêtre s'ouvre. Sélectionnez la partition 0 (celle de 15 MB). Cliquez Ok. Sur la fenêtre principale décochez la case "Read only drive". Cliquez Ok. La partition de l'image devrait maintenant être montée dans votre explorateur de fichiers. Vous pouvez maintenant aller au dossier /grub et remplacer (ou renommé) le ramdisk par défaut extra.lzma par celui que j'ai fourni un peu plus haut. Maintenant revenez en arrière et aller dans le dossier /grub et éditer le fichier grub.cfg avec votre éditeur de texte avancé. Si vous avez besoin de remplacer le ramdisk par défaut par le ramdisk extra.lzma personnalisé il vous faudra alors aussi monter la partition 1 (celle de 30MB) avec OSFMount. Le contenue du fichier grub.cfg est le suivant: Je ne mets uniquement ici que la portion du code qui nous intéresse dans le cadre de ce tuto: [...] set extra_initrd="extra.lzma" set info="info.txt" set vid=0x058f set pid=0x6387 set sn=C7LWN09761 set mac1=0011322CA785 set rootdev=/dev/md0 set netif_num=1 set extra_args_3615='' set common_args_3615='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet' set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0' set default='0' set timeout='1' set fallback='1' [...] Les données à modifier sont les suivantes: vid=0x090C par vid=0x[le vid de votre clef usb] pid=0x1000 par pid=0x[le pid de votre clef usb] sn=C7LWN09761 par sn=générez votre sn ici avec le modèle DS3615xs ou DS3617xs ou DS916+ (cela va dépendre que quel loader vous avez choisi) mac1=0011322CA785 par mac1=[l'adresse MAC du port réseau #1]. Vous pouvez rajouter set mac2=[l'adresse MAC du port réseau #2] si vous avez un 2ième port réseau et ainsi de suite jusqu'à mac4 mais ceci n'est pas nécessaire. Conseil: changez timeout='1' par timeout='4' - Cela rallonge la durée d'affichage du Menu Boot Grub lorsqu'il apparaitra à l'écran. Une fois finie l'édition du fichier grub.cfg, sauvegardez les changements et fermez l'éditeur de texte. Sur OSFMount cliquez sur "Dismount all & Exit". Vous êtes maintenant fin prêt à écrire l'image sur votre clef USB. 5 - Utilisez Win32 Disk Imager pour rendre votre clef USB bootable avec l'image que vous venez d'éditer. 6 - Ejectez votre clef USB chaude et brulante proprement. Branchez la sur votre NAS (évitez les ports USB 3.0). Démarrez la machine et accédez immédiatement à votre BIOS afin de le reconfigurer pour que le boot se fasse à partir de la nouvelle clef usb. Faites les changements nécessaires pour redémarrer en UEFI ou en legacy bios, c'est à vous de choisir. Aussi, dans le BIOS, les HDD doivent être configurés en AHCI et non pas en IDE. Finalement et si possible, activez dans le BIOS le port série si il ne l'est déjà pas. Toutes les cartes mère n'ont pas forcément de port série. Si c'est le cas pour vous alors ce n'est pas bien grave, le loader se chargera du problème. Sauvegarder les changements fait au BIOS et redémarrez. 7 - Une fois redémarré, si vous avez un écran connecté au NAS vous verrez le Menu Boot Grub suivant: CONSEIL: avant même que le Menu Boot Grub n'apparaisse cliquez de façon répétée les touches haut ou bas. Cela aura comme effet d'arrêter le compte à rebours et vous donnera le temps de choisir la ligne que vous voulez. Vous verrez l'écran suivant après avoir fait entrer: Si vous avez démarrer la clef USB en mode EFI vous ne verrez normalement pas les 3 dernières lignes. Rien de grave. 8 - Retournez à votre PC et lancez de préférence Synology Assistant ou alors allez à http://find.synology.com. Normalement si vous avez bien tout suivi votre NAS devrait être détectée sur votre réseau local au bout d'une minute environ (j'ai testé avec un machine virtuelle et ça a prit ~55 secondes). Il suffit ensuite de suivre les indications pour soit faire une installation fraîche soit faire la migration de DSM 5.2 à DSM 6.1. A un moment donné DSM vous demandera le fichier PAT (DSM_DS3615xs_15217.pat ou DSM_DS3617xs_15217.pat ou DSM_DS916+_15217.pat) que vous avez normalement déjà téléchargé. 9 - Une fois finie la MAJ ou l'installation fraîche, accédez à votre NAS comme d'habitude. Il vous faudra surement mettre à jour plusieurs applications. Vous pouvez ensuite mettre à jour DSM 6.1 jusqu'à DSM 6.1.7-15284. Il est possible que vous soyez obligé de faire un reboot forcé. Certaines personnes ont dû refaire la clef usb aussi. Désactivez la mise à jour automatique dans DSM. Si besoin est, voici ou télécharger les fichiers individuels (DSM et updates): https://xpenology.com/forum/topic/7294-links-to-dsm-and-critical-updates/ 10 - Voila c'est fini. Si vous avez des questions cherchez le forum/Google d'abord. Si vous êtes toujours bloqué alors posez votre question en donnant les spécifications de votre matériel (model carte mère, contrôleur LAN, contrôleur disk etc) faute de quoi votre post sera supprimé ou sciemment ignoré. -------------- Note 1: Si après avoir suivi le tuto votre NAS n'est pas accessible via http://find.synology.com ou Synology Assistant la raison la plus probable c'est que les drivers de votre carte réseau n'ont pas été inclus dans le loader. Faites un effort et utilisez Google pour savoir quel module votre carte réseau et/ou votre contrôleur de disque utilisent sous linux suite à quoi vérifiez que ces modules soient inclus dans le ramdisk personnalisé. Si vous le voyez alors utilisez le ramdisk personnalisé. Si rien ne marche alors poser votre question. Note 2: Une fois passé à DSM 6.1 sachez que vous n'aurez plus accès au NAS via ssh avec le compte root. Vous pouvez ceci dit y accéder avec votre compte administrateur puis élever les droits en utilisant sudo -i Ceci est tout à fait normal. C'est Synology qui a voulu sécuriser l'accès à DSM. Note 3: Vérifiez bien le VID/PID de votre clef USB avant d'entamer la MAJ. Si lors de la migration vous obtenez l'erreur suivante: "Failed to install the file. The file is probably corrupted. (13)" (ou l'équivalent en français) c'est que le VID/PID ne correspond pas à votre clef USB. Si vous avez toujours des problèmes après avoir bien vérifié le VID/PID alors essayez une autre clef usb. Note 4: Les changements effectués sur le fichier grub.cg peuvent aussi être fait directement à partir du Menu Boot Grub donc en principe il est tout à fait possible d'ignorer le Point 4 et écrire l'image synoboot.img sur votre clef USB sans rien modifier (il suffit de continuer à lire à partir du Point 6). Pour faire les modifications il faut appuyer sur la lettre 'C' lorsque vous voyez le Menu Boot Grub apparaitre. Il faut être vif car vous n'avez qu'une seconde avant que le menu disparaisse. Apres avoir appuyé sur la lettre C vous vous retrouverez dans une invite de commande grub. Pour changer le VID vous devez écrire comme suit: vid 0xLES 4 CHIFFRES VID DE VOTRE CLEF USB Faites la même chose pour pid, sn et mac1. Appuyez sur entrer à chaque commande. Les commandes sont les suivantes: pid 0xLES 4 CHIFFRES PID DE VOTRE CLEF USB sn LE NUMERO DE SERIE DE VOTRE NAS mac1 L'ADRESSE MAC1 DE VOTRE NAS Si vous avez plusieurs cartes réseau vous pouvez les rajouter de la meme manière: Le maximum c'est mac4. Voir ci dessous: mac2 L'ADRESSE MAC2 DE VOTRE NAS mac3 L'ADRESSE MAC3 DE VOTRE NAS mac4 L'ADRESSE MAC4 DE VOTRE NAS Si vous pensez avoir fait une erreur il suffit de refaire la commande. Lorsque vous avez fini appuyez sur Esc et sélectionnez la ligne du menu qui convient. Ci dessous un example a quoi ressemble l'invite de commande grub avec les commandes: Note 5: Si lors de l'installation vous recevez un message d'erreur de type "Nous avons détecté des erreurs sur les disques [numero des disques] et les ports sata ont également été désactivés, remplacer les disques et réessayer" alors il faut rajouter SataPortMap dans l'invite de commande Grub (ou dans le fichier grub.cfg). Appuyer sur la letter C lors du Menu Boot Grub et écrivez ceci: append SataPortMap=XX XX est le nombre de HDD présent. N'oubliez pas de mettre à jour ce paramètres si vous rajouter des HDD. Par ailleurs, si vous êtes amené à utiliser Reinstall, il ne faut pas oublier de sélectionner le mode normal (première ligne du menu grub) lors du reboot automatique après l’installation, sinon le loader sélectionnera à nouveau Reinstall et cela occasionnera des problèmes ultérieurement. @@@@@@@@ Précisions sur ce que veut dire SataPortMap= @@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ ############## Problèmes connus ##################### - Sur des machines à coeur unique et lent le "patcher" charge trop tard. - Certains drivers de cartes réseau plantent lorsque le MTU est au delà de 4096 (Jumbo frame). ############# Modules inclus dans le Loader de Jun par défaut ############# ############### Log des modifications du Tuto ###################

Hi @Polanskiman the correct software for the 5005-itx can be found here :xxxps://1drv.ms/u/s!Ap4vsEUrPToyh2746hR4GRDPPocn direct from asrock support; work under windows!

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7u2 - Additional comments: test vm - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7u2 - Additional comments: main vm with rdm disks, 2 sata controllers, usb3 passthrough