Popular Content

Showing most liked content since 08/24/2017 in all areas

  1. 13 likes
    Loader Download: here / (link updated due to directory structure change of mega share) -- by jun 2-28 I've uploaded a 6.1 alpha build to mega, for brave guys only . (Note: AMD needs extra work.) scripts I use to generate bootable image https://github.com/kref/scripts ---Beginning of addition by polanskiman--- Tutorials by polanskiman: Install/Upgrade DSM 5.2 to DSM 6.0.2 here Install/Upgrade DSM 5.2 to DSM 6.1 here Loader download mirrors: Managed by Polanskiman. includes .iso format images made by myself. here Managed by Trantor. This mirror is currently offline. here For info: v1.01 (DS3615xs) is for DSM 6.0.2 - AMD compatible - Latest version for DSM 6.0.2 v1.02b (DS3615xs, DS3617xs and DS916+) is for DSM 6.1 - AMD loosely compatible and with Bios tweaks - Latest version for DSM 6.1 Deprecated loaders v1.02a (DS3615xs) is for DSM 6.1 - AMD not compatible - Deprecated v1.02a (DS3617xs and DS916+) is for DSM 6.1 - AMD not compatible - Deprecated - ('time bomb' bug fixed in v1.02a2) v1.02a2 (DS3617xs and DS916+) is for DSM 6.1 - AMD not compatible - Deprecated Hide DO NOT install DSM updates on your working machine BEFORE looking into the forum or testing the update on a test rig/vm. Further explanation by jun on AMD compatibly for loader v1.02a, v1.02a2 and v1.02b: ---End of addition by polanskiman--- OP History I've recently annouce that my work on a kernel mode dynamic patcher in this post https://xpenology.com/forum/topic/6213-xpenology-developers-contact-me-for-7393-kernel-src-code/?do=findComment&comment=54105 Now seems everything work out of box on VMware, so it's pretty close to an everybody useable loader, But lots of hardwares drivers are missing, to support as much hardware as possible requires some extra work, So I hope these is some help from the community to built & test drivers, make it usable for everyone. AMD users have a look 3rd Post. I've upload a tar archive of the boot partion, it should be untar in to a usb drive's EFI System Partition. I prefers EFI bootloader, so I used grub2-efi here, but you can install your prefered ones, even none-EFI ones. the zImage is a vanilla synology kernel, ramdisk.lzma is repacked to add some network drivers plus my patcher. you need change sn/mac/vid/pid as usual before installation. and to make installer happy, usb drive seem should have at least 2 partitions, one for boot, and one for recovery I guess. I suggest to test it on VM first, then add hardware drivers for boot on bare metals. Below is how my usb drive looks like $ sudo gdisk -l /dev/sdc GPT fdisk (gdisk) version 0.8.8 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sdc: 32784384 sectors, 15.6 GiB Logical sector size: 512 bytes Disk identifier (GUID): 4308A165-B0A6-4EC9-8B8E-9BEFB00BF33F Partition table holds up to 128 entries First usable sector is 34, last usable sector is 32784350 Partitions will be aligned on 2048-sector boundaries Total free space is 4061 sectors (2.0 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 31457280 15.0 GiB 8300 Linux filesystem 2 31459328 31868927 200.0 MiB 8300 Linux filesystem 3 31868928 32784350 447.0 MiB EF00 EFI System $ mount|grep tmp1 /dev/sdc3 on /mnt/tmp1 type vfat (rw) $ ls -l /mnt/tmp1/ total 24 drwxr-xr-x 3 root root 8192 Sep 18 17:19 EFI drwxr-xr-x 5 root root 8192 Sep 20 21:16 grub drwxr-xr-x 3 root root 8192 Sep 20 21:15 image $ lsusb |grep Flash Bus 001 Device 010: ID 058f:6387 Alcor Micro Corp. Flash Drive link https://mega.nz/#!c8kn3JAL!fy4a0sXuYfcv1Sx7adGbr2OS-guqMS4GLRH3TOFkNfY Edit: I add a few popular network & disk drivers, and create a boot image for VM. Just add some scsi or sata disk, then boot, and follow normal installation process. https://mega.nz/#!llU23QgA!oGaZQuQLe0fsx1tuGiSBoZ19DSfEQH5Aq3GJXfEjpHE for esxi, pls use this link https://mega.nz/#!Agt00ZDT!lN5blyZc4gMaj-mKt-xCxoTtle-7cLF0ui9bF6ZBnY0 Plus a usb boot image for bare metal in UEFI mode. pls consider it unstable, test at your own risk. https://mega.nz/#!Z4UzWZxZ!hu9SZXpzJBTakHk7lO8pJfyHYb-YgGatI-Em9E3JXWI EditEdit: Many people reported that DSM ask you to reinstall forever. It turn out that lack of a serial port caused the failure. That is really a surprise . Anyway, I upload a new ramdisk to workaround the issue. You should replace the image/DS3615xs/ramdisk.lzma in the boot partiton with this new one. Edited post The esxi and bare metal image are updated, so manually replace the ramdisk is not required. Alternatively, VM users may add a serial port as a workaround. Bare metal users can enable the serial port in bios if your board has one. remaining problem: Login to your DSM via ssh/telnet, your will see these messages in kernel log, this is another consequence of lack of a serial console. [ 1360.575754] init: tty main process (13856) terminated with status 1 [ 1360.575823] init: tty main process ended, respawning [ 1370.591635] init: tty main process (13881) terminated with status 1 [ 1370.591755] init: tty main process ended, respawning To stop it from spam your log, you can stop/disable the tty serivce. update: above workaround is not enough for boards without serial port, these unlucky guys should edit following serivce config manually, replace "console output" with "console none" after installation root@test:~# grep -r "^console output$" /usr/ 2> /dev/null /usr/share/init/syno_poweroff_task.conf:console output /usr/share/init/burnin_loader.conf:console output /usr/share/init/udevtrigger.conf:console output /usr/share/init/bs-poweroff.conf:console output /usr/share/init/udevd.conf:console output Another issue: I've found a hidden check related to console, everyone should edit grub.cfg, replace console=uart8250,io,0x3f8,115200n8 with console=ttyS0,115200n8 You have to change sn/mac/vid/pid as usual before installation ! If you don't edit vid/pid in grub.conf you will get error 13 (file corruption) during setup. How to see the value of my VID & PID stick EDIT by Trantor (10-28-2016): Updated loader by Arcao latest images (10-28-2016) : https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w Original post : https://xpenology.com/forum/topic/6253-dsm-602-loader-was-a-new-loader-for-latest-dsm/?do=findComment&comment=55903 Sources for dev: quicknick : https://github.com/quiknick/7274-kernel setsunakawa : http://setsunakawa.ddns.net/synology/dsm6/ 10/29: It's time to release a loader with a proper version number now. Here is my loader v1.0 https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA New features & fix: Support bios & uefi boot & VMware & ESXI Fix cmos reset issue( at least on bios mode VMware workstation) most configurations can be done via grub command line now. Remember last boot entry. Autodetect synoboot partitions, not extensively tested. It is still recommended to set correct vid/pid. AMD CPU support, not extensively tested, there are a few positive report on the forum. Add grub menu for reinstallation. Add grub menu to force installation when interrupted due to "Disks Disabled" message, not extensively tested Automatically apply workaround for boards without serial port. Fix SATA disk order remap, and allow to set SAS disk starting no, but disk order are still not deterministic between SAS disks. Fix SAS disk naming, not extensively tested, only with one SAS2008 based HBA and synology provided mpt2sas driver. Add ata_piix support, tested on VMware and it does not crash, only complain about "Read current link speed fail", so I assume it works , this driver requires a bit of patching to the kernel, so I include it in the package. Integrate up-to-date network drivers compiled by Arcao and Trantor. Known issue: When runing on a slow single core machine, there is a race condition causes the patcher loading too late. the most obvious sign is console not working properly. I don't expected this to happen normally, the only example is a VM on my laptop when running on battery. If anyone believes have this issue, please send me a message. Some ethernet drivers crash when set MTU above about 4096(Jumbo frame), I've not identified the culprit yet. How to install: find the vid/pid of your usb drive Burn the image to the drive, optionally edit grub.cfg to set vid/pid and boot entry, OR connect monitor/keyboard/serial console to your Box. Press C during Grub boot menu to enter command line vid 0xXXXX pid 0xYYYY to configure pid and vid ("pid" and "vid" are command, and "XXXX", "YYYY" are you usb drive's vid,pid) (There are a few other options can be config this way, you can read grub.cfg to know more detail.) Press Esc to go back to boot menu Select baremeta/baremetal AMD entry, press enter to boot. If your encounter the "disk port disabled" error during installation, try the force install menu entry. if both option does not work, you have to fallback to SataPortMap method, type this line in grub command line, replace XX with appropriate value. append SataPortMap=XX 11/2: as I promised, here is v1.01, download link is the same as v1.0 This update contains nothing fancy, mainly for inner peace, Plus, I revert megaraid_sas mpt3sas to old version. It's not shining new now, the title is obsolete Hide
  2. 6 likes
    This is an updated tutorial version from the one I made last year. It will enable you to migrate from DSM 5.2 to DSM 6.1.3 directly without the need to upgrade to DSM 6.0.2 first. If for some reason you want to upgrade to DSM 6.0.2 first or simply you do not want to upgrade to DSM 6.1 but only to DSM 6.0.2 then use the link above. As most of you know by now Jun was able to find a way to install DSM 6 on non Synology boxes. Here is the thread that I recommend reading. At least make an effort and read the OP: https://xpenology.com/forum/topic/6253-dsm-6xx-loader/ Below is what you need for the operation. I will assume you are doing all this under Windows 10, 8, 7 or XP. If you are on a MAC computer have a look at this post I made on how to burning the image to a USB drive and then mounting the USB drive for editing the content. The rest of the tutorial still applies. If you are currently using DSM 5.1 or below first update to DSM 5.2. If you are doing a fresh install of DSM 6.1 then carry on with the tutorial and omit references to DSM 5.2. - Win32 Disk Imager to make a bootable USB drive; - A 4GB (or any size really) USB drive (flash drive) to install the loader. Not that this is necessary but use preferably a brand name (Kingston, SanDisk...); - A way to read your USB drive VID/PID. Here is a how-to >>> VID and PID; - A good text editor: Notepad++ I really don't recommend using Windows's Notepad; - DSM 6.1.3 PAT file. The file comes straight from Synology servers. The one I link here if or DS3615sx. If you need DS3617sx or DS916+ then search. - Jun's official v1.02b loader (mirror). This is a hybrid UEFI/BIOS loader so it should work in most machines which are capable or reading GUID partition table (GPT). For older machines that can only read MBR the above loader will simply not boot. If that is your case then use @Genesys's v1.02b loader rebuilt image which is MBR based. Note: Jun's loader supports Intel CPUs. For AMD CPUs Jun has stated that the loader needs some work but it has been reported by many users that it actually works. The C1E function in the bios may need to be deactivated in AMD machines. - Custom extra.lzma ramdisk_v3 (only available for DS3615xs). This ramdisk is optional and should only be used if the default ramdisk included in the loader is not detecting your hardware. I am just providing it for those who are having issues with network detection or unrecognised HDD controllers. This custom ramdisk contains additional modules & firmwares. Credits go to @IG-88 for compiling the modules against the latest DSM 6.1.3 source code. I do not warranty they all work but I think most do. If you chose to use this ramdisk, you will need to replace (or rename, so you can revert) the default extra.lzma ramdisk from Jun's loader with this one. See the 'Modules & Firmware Log' at the end of the tutorial for more information on additional modules included in the custom ramdisk. Custom ramdisk temporarily offline - If you are doing a fresh install make sure your drives are plugged in direct succession starting from the 1st SATA port. Usually the first port is described as SATA0 on motherboards. Check with your MoBo manufacturer for exact nomenclature. - OSFMount to modify the grub.cfg file within the loader's image and if necessary to replace the extra.lzma ramdisk with the custom one. This is not strictly necessary as Jun has made it possible to configure what needs to be modified via the Grub Boot Menu. If you prefer using Jun's Grub Boot Menu configuration technic, simply skip Point 4, read Note 4 instead and pick up at Point 5. PLEASE READ EVERYTHING PRIOR ATTEMPTING ANYTHING Use this loader at your own risk. I wont be held responsible for any loss of data or black smokes that may result in the use of this loader. Please note that this loader has a limited amount of modules (drivers) included. If it is fundamental for you to have a NAS operating as quick as possible I recommend you look at the included drivers very carefully at the bottom of this tutorial before attempting an upgrade. If they are not there you will have to compile your own modules/firmwares. Don't ask me to compile them for you. You have been warned. Here we go: 1 - BACKUP your data and save your configuration prior any attempts to migrate from DMS 5.2 to DSM 6.1. I can't stress this enough. JUST DO IT, as Nike likes to say. Also, print this tutorial if you can. It will make your life easier. 2 - Turn off your NAS and unplug the USB drive you are currently using with DSM 5.2. I recommend you put this USB drive aside in case migration to DSM 6.1 doesn’t go as expected and you need to revert to DSM 5.2. It will just make your life easier. 3 - Now go to your workstation/PC, plug a new USB drive (or the old one if you really don’t have any spare USB drives). Use the link I provided earlier to check your USB drive VID/PID. Write down the info somewhere as we will need it later. 4 - Now launch OSFMount. Select Mount New, then select the image file you downloaded earlier (i.e. .img extension file) to open. Now select partition 0 (the one that is 15 MB). Click Ok. Then at the bottom of the window make sure to un-tick the "Read only drive". Click Ok. The partition should now be mounted in file explorer. At this point you can navigate to the /grub directory and edit the grub.cfg file. If you need to replace the extra.lzma ramdisk with the custom ramdisk provided above then you will also need to mount partition 1 (the one that is 30 MB). Below is what you will see in the grub.cfg file. I am only showing below the portion of the code that is relevant for the purpose of this tutorial [...] 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' [...] You want to modify the following: Change vid=0x090C to vid=0x[your usb drive vid] Change pid=0x1000 to pid=0x[your usb drive pid] Change sn=C7LWN09761 to sn=generate your sn here with DS3615xs or DS 3617xs model (this will depend on which loader you chose) Change mac1=0011322CA785 to mac1=[your NIC MAC address #1]. You can also add set mac2=[your NIC MAC address #2] and so on until mac4 if you have multiple NICs. However, this is not necessary. Recommended: Change set timeout='1' to set timeout='4' - This will allow you more time to make a selection in the Grub Boot Menu when it appears on screen. Once you are done editing the grub.cfg file, save it and close your text editor. Now in OSFMount click on Dismount all & Exit. You are now ready to burn the image to your USB drive. 5 - Now use Win32 Disk Imager to burn the image file onto the USB drive. This will also make the USB drive bootable. 6 - Eject and unplug the USB drive from your workstation. Plug it in your NAS (avoid USB 3.0 ports. Use USB 2.0 port if available). Boot your NAS and before doing anything fancy, access your BIOS so to make your USB drive the 1st boot drive if it's not the case. The Jun official loader can boot in UEFI or in legacy BIOS, so you chose what suits you best. Also, make sure your HDDs are booting in AHCI mode and not in IDE. Finally, if disabled, also enable the serial port in BIOS. Some BIOS don't have this option so don't get too cranky on this if you can't find it. Save changes to the BIOS and REBOOT the NAS. 7 - Once rebooted, if you have a monitor connected to your NAS you will see the following Grub Boot Menu: ADVICE: even before you see the Grub Boot Menu press the up/down key. This will stop the countdown so you will be able to select the desired line. You won’t see much other than the following after you press enter: If you booted the USB drive in EFI mode then you will see the same text without the last 3 lines but that's ok. 8 - Now go back to your workstation, and launch Synology Assitant or go to http://find.synology.com. Within one minute or so you should normally be able to see your NAS on your local network (it took ~55 seconds on a test I did on a VM). Just follow the instructions and either chose "Install" if you wish to have a clean install or chose “Migration” if you are coming from DMS 5.2 and wish to update while retaining your data. You will be asked to provide the .PAT file you downloaded earlier (DSM_DS3615xs_15152.pat). 9 - When the migration is finished you will most probably have to update some of your packages. You can then proceed and update DSM 6.1.3 up to DSM 6.1.3-15152 update 3. It is possible you might either need to hard reboot or re-image your usb drive. Make sure to deactivate auto-updates within DSM. Link to individual files (DSM and critical updates) can be found here: https://xpenology.com/forum/topic/7294-links-to-dsm-and-critical-updates/ 10 - You are done. If you have questions, first search the forum and/or Google then leave a comment if nothing helps. Please provide your hardware specifications (motherboard model, LAN controller, driver controller etc). Failure to prove such information will lead to the post being deleted. Click the 'Like this' button if you liked the tutorial. -------------- Note 1: If after following the tutorial you can’t find your NAS through http://find.synology.com ou Synology Assistant it is highly possible that the drivers of your NIC are not included in the ramdisk of the loader. Make an effort and use Google to know what modules your NIC and HDD controller are using, then check if those modules are included in the custom extra.lzma ramdisk. If yes then use the custom ramdisk. Don't ask me to look for you. If nothing works then ask your question. Note 2: Synology increased security since the introduction of DSM 6. Root access through SSH is no longer possible out of the box. You can however use your admin account and elevate permissions with the following command if you need root permissions: sudo -i Note 3: Please check you have the right VID/PID prior proceeding. If you get the following error ”Failed to install the file. The file is probably corrupted. (13)" it most certainly means your VID and/or PID is/are wrong. If you still have the same error message after verifying the VID/PID then try another USB drive. Note 4: Configuration added to the grub.cfg file can also be done directly during the Grub Boot Menu, so technically you can skip Point 4 and burn the image on the USB drive without editing anything (read Point 5 onward first). If you wish to do the changes from the Grub Boot Menu directly you need to press the letter 'C' when you see the Boot Menu. You will literally only have one second, so be fast. Once you press 'C' you will be in a Grub command line environment. To change your VID enter the following: vid 0xYOUR 4 DIGITS USB DRIVE VID Do the same for pid, sn and mac1. Press enter at each command. The commands are: pid 0xYOUR 4 DIGITS USB DRIVE PID sn YOUR NAS SERIAL NUMBER mac1 YOUR NAS MAC1 ADDRESS If you have multiple NICs you can also issue mac2, mac3 and mac4 as commands. Maximum is mac4. See below: mac2 YOUR NAS MAC2 ADDRESS mac3 YOUR NAS MAC3 ADDRESS mac4 YOUR NAS MAC4 ADDRESS If you think you made a mistake in the numbers simply re-issue the command. When you are done press esc and select the appropriate menu entry. Below is an example (fake numbers) of how it looks under the Grub command line environment : Note 5: If you encounter the error "We've detected errors on your hard drives [drive number] and the SATA ports have also been disabled" during installation, then you have to fallback to adding SataPortMap to the grub environment. Press the letter 'C' at the Grub Boot Menu and then add the following: append SataPortMap=XX where XX is the number of drives. Don’t forget to update this parameter if you add additional drives to your machine. If you use Reinstall, don't forget to re-select the first line of the Boot Menu once the NAS has rebooted after the installation else the Loader will re-select Reinstall and you will be faced with some issues so please beware of this. @@@@@@@@ What does SataPortMap mean? @@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ ############## Know issues ##################### - When running on a slow single core machine, there is a race condition that causes the patcher to load too late. The most obvious sign is that console is not working properly. - Some ethernet drivers crash when set MTU above about 4096 (Jumbo frame). ############# Included default modules & firmwares in Jun's Loader ############# Modules & Firmwares Log - Click HERE Modules alx.ko ata_piix.ko atl1.ko atl1c.ko atl1e.ko ax88179_178a.ko bnx2.ko bnx2x.ko BusLogic.ko button.ko cnic.ko e1000.ko ipg.ko jme.ko libcrc32c.ko libphy.ko mdio.ko megaraid_mbox.ko megaraid_mm.ko megaraid_sas.ko megaraid.ko mii.ko mpt3sas.ko mptbase.ko mptctl.ko mptsas.ko mptscsih.ko mptspi.ko netxen_nic.ko ohci-hcd.ko pch_gbe.ko pcnet32.ko ptp_pch.ko qla3xxx.ko qlcnic.ko qlge.ko r8168.ko r8169.ko scsi_transport_spi.ko sfc.ko skge.ko sky2.ko tg3.ko uio.ko usbnet.ko vmw_pvscsi.ko vmxnet3.ko Firmwares bnx2/bnx2-rv2p-06-6.0.15.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-09ax-6.0.17.fw tigon/tg3_tso.bin tigon/tg3_tso5.bin tigon/tg3.bin Hide ############# Additional modules & firmwares in the custom extra.lzma ramdisk made by IG-88 ############# Modules & Firmwares Log - Click HERE Modules 3w-9xxx.ko 3w-sas.ko aacraid.ko aic94xx.ko arcmsr.ko asix.ko alt2.ko cx82310_eth.ko e100.ko evdev.ko forcedeth.ko hpsa.ko hptiop.ko igbvf.ko isci.ko ixgb.ko ixgbevf.ko mvmdio.ko mvsas.ko mvumi.ko plusb.ko r8152.ko rtl8150.ko sx8.ko Firmwares bnx2/bnx2-mips-06-6.2.3.fw bnx2/bnx2-mips-09-6.2.1b.fw e100/d101m_ucode.bin e100/d101s_ucode.bin e100/d102e_ucode.bin tigon/tg357766.bin Hide ############## Tutorial UPDATES ################## Change log - Click HERE [12/09/2017] Tutorial creation [15/09/2017] "[...] Please provide your hardware specifications (motherboard model, LAN controller, driver controller etc). Failure to prove such information will lead to the post being deleted. Click the 'Like this' button if you liked the tutorial." [17/09/2017] Temporary removal of IG-88 custom ramddisk due to some modules creating issues. [18/09/2017] Changed S/N generator link with updated version (https://xpenogen.github.io/serial_generator/index.html) Hide
  3. 4 likes
    I generated an easy to install package to activate a mainboard connected power button for clean shutting down (instead login in web page). Install package for DSM 5.2, DSM 6.0 and DSM 6.1(.1): powerbutton_6.1-0004.spk I have tested DSM 5.2 and DSM 6.1 for the DS3617 versions only in VM. Please report if there are any problems. Changelog Version 6.1-004 Minor change for recognizing DSM 6.1.1 Version 6.1-003 Adding support for DSM 5.2 Version 6.1-0002 Combining DSM 6.0 and DSM 6.1 in one package Version 6.0/6.1-0001 Versions for DSM 6.0 and DSM 6.1 Hide
  4. 4 likes
    I have made a new updated tutorial for install/upgrade from DSM 5.2 to 6.1.3. Enjoy.
  5. 4 likes
    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 availible https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/8451branch/bromolow-source/linux-3.10.x.txz/download,'>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, youu 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 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 basicly 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" (commandline 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
  6. 4 likes
    download this: https://www.dropbox.com/s/ytimsezu9cl61xx/synoboot_1.02b_ESXi_only.zip?dl=0 the only option available is ESXi, so you should not have problems regarding boot choice, it's for DS3615xs (i find has a better custom package support than DS3517xs). - extract and upload synoboot.vmdk and synoboot.img in your datastore - create a new VM (HW Version 11 or 13) dependent if you are on ESXi 6.0u2 or ESXi 6.5b - operating system should be Other -> FreeBSD 64bit - set bios to EFI - set nic to VMXNET3, set the mac manual to the same as the one in the grub.cfg - set scsi controller 0 to "LSI logic SAS" - add sata controller 0 if not there yet present - add existing hdd -> browse datastore -> add synoboot.vmdk - edit this hdd to "independent - persistent" and sata 0:0 on controller 0 - add how many new scsi disk you like, thin provisioning - dependent - save and poweron the VM - from your browser, go to find.synology.com, it should pop-up, connect and install it (manual or from internet is the same), reboot after finish the setup - create a new volume to your needs, if you want shr you have to modify synoinfo.conf - download this zip for open-vm-tools https://www.dropbox.com/s/k4hc343gwdepiuf/open-vm-tools_bromolow-6.0_10.0.7-1.spk.zip?dl=0 - extract the zip, install the spk in package manager - now ESXi should see that vm tools are installed and running Pretty much done.
  7. 3 likes
    Ce tuto est une mise à jour du tuto que j'ai déjà fait l'année dernière. Ce tuto permet d'installer/migrer DSM 5.2 à DSM 6.1.3 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 mais souhaiter migrer à DSM 6.0.2 uniquement alors utilisez le lien ci dessus. 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.3. Le fichier PAT vient 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 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 necessaire de désactiver la fonction C1E dans le BIOS. - Le ramdisk personnalisé extra.lzma_v3 (seulement pour DS3615xs). 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. Voir la liste des Modules & Firmware en fin de tuto pour le détail. Ramdisk temporairement hors ligne - Faites attention à branchez vos HDD successivement en commençant par le premier port SATA normalement décrit come 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 de tuto les drivers disponibles. Si le ne sont pas inclus alors il vous faudra les compiler vous même. Ne me demandez pas de le faire à votre place, je ne le ferais pas. 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 (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_15152.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_DS3615xs update 3. 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é. Merci de cliquer sur le bouton 'Like this' si vous avez aimé le tuto. -------------- 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 ############# Modules & Firmware - Cliquez ICI Modules ata_piix.ko atl1.ko atl1c.ko atl1e.ko ax88179_178a.ko bnx2.ko bnx2x.ko BusLogic.ko button.ko cnic.ko e1000.ko ipg.ko jme.ko libcrc32c.ko libphy.ko mdio.ko megaraid_mbox.ko megaraid_mm.ko megaraid_sas.ko megaraid.ko mii.ko mpt3sas.ko mptbase.ko mptctl.ko mptsas.ko mptscsih.ko mptspi.ko netxen_nic.ko ohci-hcd.ko pch_gbe.ko pcnet32.ko ptp_pch.ko qla3xxx.ko qlcnic.ko qlge.ko r8168.ko r8169.ko scsi_transport_spi.ko sfc.ko skge.ko sky2.ko tg3.ko uio.ko usbnet.ko vmw_pvscsi.ko vmxnet3.ko Firmwares bnx2/bnx2-rv2p-06-6.0.15.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-09ax-6.0.17.fw tigon/tg3_tso.bin tigon/tg3_tso5.bin tigon/tg3.bin Hide ############# Modules additionnels contenus dans le ramdisk extra.lzma personnalisé compilé par IG-88############# Modules & Firmware - Cliquez ICI Modules 3w-9xxx.ko 3w-sas.ko aacraid.ko aic94xx.ko arcmsr.ko asix.ko alt2.ko cx82310_eth.ko e100.ko evdev.ko forcedeth.ko hpsa.ko hptiop.ko igbvf.ko isci.ko ixgb.ko ixgbevf.ko mvmdio.ko mvsas.ko mvumi.ko plusb.ko r8152.ko rtl8150.ko sx8.ko Firmwares bnx2/bnx2-mips-06-6.2.3.fw bnx2/bnx2-mips-09-6.2.1b.fw e100/d101m_ucode.bin e100/d101s_ucode.bin e100/d102e_ucode.bin tigon/tg357766.bin Hide ############### M.A.J du Tuto ################### Log des modifications - Cliquez ICI [13/09/2017] Création du tuto [15/09/2017] Ajout "[...] 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é. Merci de cliquer sur le bouton 'Like this' si vous avez aimé le tuto." [17/09/2017] Ramdisk personnalisé extra.lzma de IG-88 mis hors ligne temporaire pour cause de problèmes avec certains modules. [18/09/2017] Lien générateur de S/N changé à https://xpenogen.github.io/serial_generator/index.html Hide
  8. 3 likes
    про плекс и 916 собираю до кучи здесь есть возможность обсуждения, просто оставляйте свои коменты внизу текста само содержание по мере новой практики дополняется и исправляется, т.е. ещё в доработке...
  9. 3 likes
    Salut à tous, Ici je vais vous expliquez comment faire tourner le DSM 6 Xpenology sur Hyper-V. Téléchargez les VHDX (uploadés par moi même) prévues à cet effet : https://1drv.ms/u/s!Anih4xuqH7tysAOHkDHOqgim2CZ_ Créer une nouvelle machine virtuelle en respectant scrupuleusement les mêmes paramètres que ce screenshot : Appliquez les paramètres comme l'image ci-dessus. N'ajoutez pas votre VHDX de données tout de suite. Démarrez la machine virtuelle attendez 3 à 5 minutes le temps quelle démarre, et configurez là via http://find.synology.com/ Une fois quelle est démarrée et que tout est OK, éteignez-là et ajoutez votre disque VHDX de données : Démarrez de nouveau la machine virtuelle, est vous pouvez allez commencer à créer votre volume dans le Gestionnaire de disque. N'appliquez pas les mises à jour du DSM ! Enjoy !
  10. 2 likes
    Зеркальный ген(добавлен 916) пуск Hide
  11. 2 likes
    по правили скрипт в калькуляторе теперь работает
  12. 2 likes
    при сносе 1 раздела(или тоже самое при сносе папки etc.defaults) также останутся все файлы старых прог
  13. 2 likes
    на момент есть два способа: штатно и только с видеостейшн, нужна учётка и образ 916 с бетой плекса, нужна учётка плекса и уже подходит любая ds 3615 3617 и 916, проц только от интел и старших поколений которые поддерживают модуль i965_dri_video.so
  14. 2 likes
    P.S. буквально сейчас работаю по этому поводу и не только...
  15. 2 likes
  16. 2 likes
    very easy to use a usb to boot from Probably best to use the latest Syno release 6.1+ to install DEf do your bios firmware updatye before loading anything else on your box Even tho I would check that the bios update does something you need /desire otherwise leave alls well that stays well. pointing you to a good guide to installing is xpenology is a moving target. If you did the install to your N40l you should be ok BUT the Bios on the gen8 requires you to set your disks up first SUmmary update BIos if necessary create bootable usb stick (with NanoBoot or other software on it) insert usb stick into gen8 boot gen8 (takes afew minutes 5-10) use find.synology.com or synology web assistant to find your new xpeno on your lan. point installation to your PAT file (probably stored on your PC) have some nice fresh disk installed point installtion to your disk after some minutes you will have nice fresh installtion. I am lucky in that I have an old 19in monior (+kyb) attached to the gen8 so setting the bios , following all the prompts and watching the boot progress is much easier. My usb stick stays in the gen8 but the monitor can be safely stowed away when all is hunkydory. You could update your CPU to i3 or xeon, also you should be able to "import" you old n40l disks to your new installation you could also import your configuration if you save it on the n40l.
  17. 2 likes
    Removing the boot loader will simply prevent DSM from booting... There is a reason why it's called a "boot loader". Also I don't think using Jun's boot loader 1.02b will work on a laptop as I believe the modules are not included. Also be advised that even if it works you would need to access DSM from a different computer. DSM is a server OS and therefore is not meant to have a display attached to it. It is meant to be accessed through the network. In any case that black screen and a cursor tells me that the usb boot loader did not boot, perhaps because you removed it in the first place...
  18. 2 likes
    Hello again! It seems that I have found the sollution after all. After looking for any "BACKUP" entry in any file on the DSM through the console ( find / -type f -exec grep -H 'BACKUP' {} \; ) I found 2 refferences to the mentioned name in the /etc/samba/smb.conf file. [BACKUP] invalid users=nobody,nobody valid users=nobody,nobody comment="Backup D1" path=/volume3/BACKUP guest ok=yes browseable=yes fileindex=no mediaindex=no edit synoacl=yes win share=yes skip smb perm=yes enable recycle bin=no recycle bin admin only=no hide unreadable=no ftp disable list=no ftp disable modify=no ftp disable download=no read list=nobody,nobody write list=nobody,nobody writeable=yes [BACKUP 2] invalid users=nobody,nobody valid users=nobody,nobody comment="Backup disk 2" path=/volume1/BACKUP 2 guest ok=yes browseable=yes fileindex=no mediaindex=no edit synoacl=yes win share=yes skip smb perm=yes enable recycle bin=no recycle bin admin only=no hide unreadable=no ftp disable list=no ftp disable modify=no ftp disable download=no read list=nobody,nobody write list=nobody,nobody writeable=yes I then tried creating a new shared folder, and found out that there are 2 files that store information about the current SMB shares, the "smb.conf" and "smb.share.conf". But the newly created file is only visible in the smb.share.conf file. The other file smb.conf was probably the file used in the previous version of DSM. (In my case DSM 5.2) So it seems that DSM reads the samba configuration from both files, but only edits one of them. After I removed the "BACKUP" and "BACKUP2" from the smb.conf file, both of these shared folders were no longer visible on any client using samba/smb protocoll. I`m not sure if this is just a local bug on my DSM, but if not, i immagine that this will happen to a lot of people when they try to delete a shared folder that was created on a older version of the DSM. Hope this helps someone. @admins: Not sure how i can mark this topic as solved, so could you please do it? Thanks!
  19. 2 likes
    Можно прошить по другому без флешек. ILO - iLO Federation / Group Firmware Update Firmware URL : http://<server.example.com>/CPQJ0612.F62 где CPQJ0612.F62 файл BIOS из архива SP99000.exe
  20. 2 likes
    List of mirrors links to DSM 5.x and DSM 6.x boot loaders. Please drop a comment if you see a broken link. All other posts will be deleted without warning. DSM 6.1(.2/.3) - Read Jun's topic and Tutorial Jun's loader v1.02b DS3615xs DS3615xs 6.1 Jun's Mod V1.02b.img | 50.0 MB | MD5 = b4a2bc974070895407cd50990d96669a Jun's loader v1.02b DS3617xs DS3617xs 6.1 Jun's Mod V1.02b.img | 50.0 MB | MD5 = e5d1608a9f43cf9a084277eb5640b439 Jun's loader v1.02b DS916+ DS916p 6.1 Jun's Mod V1.02b.img | 50.0 MB | MD5 = 5ea01a50fd40426eb0e5344aa6d7bbff DSM 6.0.2 - Read Jun's topic and Tutorial Jun's loader v1.01 DS3615xs DS3615xs 6.0.2 Jun's Mod V1.01.zip | 24.0 MB | MD5 = cf9d920edef96d58ae709674dc71511b DSM 5.2 XPEnoboot 5.2-5967.1 DS3615xs XPEnoboot_DS3615xs_5.2-5967.1.img | 24.0 MB | MD5 = 4b204b8200ea5d12dea8b578ad95f7ef XPEnoboot 5.2-5644.5 DS3615xs XPEnoboot_DS3615xs_5.2-5644.5.img | 24.0 MB | MD5 = a329929e5a91095e9258036485e01c9c XPEnoboot_DS3615xs_5.2-5644.5.iso | 17.4 MB | MD5 = a92ea8c869c48fc340a91e41a01d4cfd XPEnoboot_DS3615xs_5.2-5644.5.vmdk | 17.3 MB | MD5 = 9d5cfdc69e0e19ef207de9aaba76acf3 XPEnoboot 5.2-5644.4 DS3615xs XPEnoboot_DS3615xs_5.2-5644.4.img | 24.0 MB | MD5 = 59e96a63333b5c6d8911f902a23ca99f XPEnoboot_DS3615xs_5.2-5644.4.iso | 17.1 M | MD5 = bfa92964103438abd0f93c4ef58d0e38 XPEnoboot_DS3615xs_5.2-5644.4.vmdk | 17.1 MB | MD5 = 860259eaa222186860bc52bd6dff4919 XPEnoboot 5.2-5644.1 DS3615xs XPEnoboot_DS3615xs_5.2-5644.1.img | 24.0 MB | MD5 = d16c8877744a2d26bf44fc1b49a36484 XPEnoboot_DS3615xs_5.2-5644.1.iso | 22.2 M | MD5 = bdcb7a1a7586e208878807f2504cf2d5 XPEnoboot_DS3615xs_5.2-5644.1.vmdk | 22.1 MB | MD5 = 2d947faf0419668c1278fbee4281acb5 XPEnoboot 5.2-5592.2 DS3615xs XPEnoboot_DS3615xs_5.2-5592.2.img | 24.0 MB | MD5 = fbeba655ca0a77b56b025192b08eb55d XPEnoboot_DS3615xs_5.2-5592.2.iso | 21.1 MB | MD5 = c508e80e8a795514497244f798c663e2 XPEnoboot_DS3615xs_5.2-5592.2.vmdk | 21.1 MB | MD5 = ddeef445edeaba3684fcbb50c50adbe0 XPEnoboot 5.2-5592.1 DS3615xs XPEnoboot_DS3615xs_5.2-5592.1.img | 16.0 MB | MD5 = ebda68e9a7589ed1d145399f975d1232 XPEnoboot_DS3615xs_5.2-5592.1.iso | 16.1 MB | MD5 = 65c6b150ea6d26c70cc0d96d010ce5a6 XPEnoboot_DS3615xs_5.2-5592.1.vmdk | 16.0 MB | MD5 = 78cb2ff5bfcd14c1edb3dea93084443f XPEnoboot 5.2-5565.2 DS3615xs XPEnoboot_DS3615xs_5.2-5565.2.img | 16.0 MB | MD5 = 3016d6ffb5ea794033567ab7eb816184 XPEnoboot_DS3615xs_5.2-5565.2.iso | 15.6 MB | MD5 = a3ade9b08d24be96e2da775e4e06f13d XPEnoboot_DS3615xs_5.2-5565.2_vmdk.zip | 15.2 MB | MD5 = 4c314bbd4116427c5c85ceb08da7479c XPEnoboot 5.2-5565.1 DS3615xs XPEnoboot_DS3615xs_5.2-5565.1.img | 16.0 MB | MD5 = 1806870fe0a7b83ff65b25a9af9dc487 XPEnoboot_DS3615xs_5.2-5565.1.iso | 15.6 MB | MD5 = cfe9937aa76458c9e99efea5d3fee2db XPEnoboot_DS3615xs_5.2-5565.1_vmdk.zip | 15.3 MB | MD5 = 8c317e99b3db3869a480a6debf24b7b4 DSM 5.1 XPEnoboot 5.1-5055.1 DS3615xs XPEnoboot_DS3615xs_5.1-5055.1.img | 15.8 MB | MD5 = b069342f3bc6a10d1e0111e7c5341df7 XPEnoboot_DS3615xs_5.1-5055.1.iso | 14.1 MB | MD5 = c5c049a3e1e06aa6f498fb70c15dc133 XPEnoboot_DS3615xs_5.1-5055.1_vmdk.zip | 13.7 MB | MD5 = a654f3bb05033da98b32e55724f0b1ce XPEnoboot 5.1-5022.3 DS3615xs XPEnoboot_DS3615xs_5.1-5022.3.img | 15.8 MB | MD5 = 72175a41e5855b57b4c8ffc3d92f4b06 XPEnoboot_DS3615xs_5.1-5022.3.iso | 14.8 MB | MD5 = 46854ce39415d736fa5abd446ffa4352 XPEnoboot_DS3615xs_5.1-5022.3.vmdk | 14.8 MB | MD5 = a7343f03fe63a5aa7ad0fe01f41a4b76 XPEnoboot 5.1-5022.2 DS3615xs XPEnoboot_DS3615xs_5.1-5022.2.img | 15.8 MB | MD5 = 06b8435e1322c7a5ee5725ff80ea2a77 XPEnoboot_DS3615xs_5.1-5022.2.iso | 14.0 MB | MD5 = 0e211d3d19b7b461ae5df3aa91e18630 XPEnoboot_DS3615xs_5.1-5022.2.vmdk | 13.9 MB | MD5 = 929730848a31fc19bddd457998477a5f XPEnoboot 5.1-5022.1 DS3615xs XPEnoboot_DS3615xs_5.1-5022.1.img | 15.8 MB | MD5 = 6f7cb585519c5cb3acfb026d34585dbd XPEnoboot_DS3615xs_5.1-5022.1.iso | 13.4 MB | MD5 = 88bd5177fa7a4f54b7fcd5e4001bae5b XPEnoboot_DS3615xs_5.1-5022.1.vmdk | 13.3 MB | MD5 = f03125c86b2da60b5d38db1c6c62bcba DSM 5.0 NanoBoot 5.0.x DS3612xs NanoBoot- | 15.6 MB | MD5 = 2f201876ef576f4ef78a3c3bbbcee529 NanoBoot- | 15.6 MB | MD5 = 89ce54b38e83c7b94c422f6c9a0dbedb NanoBoot- | 15.6 MB | MD5 = 07bd106a7f6204962c801ecf851f1dc9 NanoBoot- | 32.0 MB | MD5 = e1353d7143cbf8cc31ed320f82cf65d6 NanoBoot- | 15.6 MB | MD5 = 32e1f823219ec7963162e4e394687112 NanoBoot- | 15.6 MB | MD5 = 6fc6be138eb070938a9f14ff64fa4239 NanoBoot- | 15.6 MB | MD5 = 6bbf71f64909cda57c3a63e523d13ed8 NanoBoot- | 31.3 MB | MD5 = 60233f771b934b5237e2037be0e64b95 NanoBoot- | 15.6 MB | MD5 = 039abc91883e09fd2f443ee10ba5690e NanoBoot x86 5.0.x DS214Play NanoBoot-x86- | 15.6 MB | MD5 = 3c6776570962926497088e6b3889205c NanoBoot-x86- | 15.6 MB | MD5 = b76c423d39129b19b2e0a62f741aaa8c NanoBoot-x86- | 32.0 MB | MD5 = 8bc6d3b5aed1f41fa0ce4d93b17f9bf1 NanoBoot-x86- | 15.6 MB | MD5 = 90948500efde437ae56dfd51f31f55f8 NanoBoot-x86- | 15.6 MB | MD5 = 7acb8faf796a0e5d5a54a9734ecec728 NanoBoot-x86- | 15.6 MB | MD5 = f333038c8bcf1e530ddeb55075b9827c NanoBoot-x86- |15.6 MB | MD5 = 5bf7241df633ff48ce6a571aa27df88c
  21. 2 likes
    Держи http://gofile.me/5XDqp/YhMohNOl3
  22. 2 likes
    why not, raid5 is ok for 4 drives an can be expanded later, as the disks are empty there is no risk in trying if you are intrested in hardware trancoding (you mention the 916+) this feature is now protected with serial number from synology, so no go for now btw. if you are just intested in btrfs, you can use btrfs with open media vault, the wizard/gui doen not offer it but you can create it nabualy an use it with omv, i tryed my dsm created raid6/btrfs with omv and it showed up in omv (and in omv forum there was something about that btrfs will work if set up menualy) but as far as i can see the synology way of using btrfs uses mdadm for the raid and on top of that there is btrfs as filesystem, so no btrfs native (integrated) raid, just a plain single volume with btrfs file system
  23. 2 likes
    Here is an ovf with the latest version dsm installed (DS3615xs) https://mega.nz/#!t8xiVJ6K!aOmfjy8w-DSFTDKn7eX_8-0PSW6E1_PsWk8JDkJin7A It is dsm 6.1.3-15152 update 1; login with user admin and password 123456 I just created a volume and a folder in it to test, didn't touch any settings in there. working fine on esxi 6.5 on a hp gen8 microserver hw version 13, you need esxi 6.5 to use this ovf; you can convert to lower hw versions for older esxi I can't edit the first post to add the new file. If you have another xpeno vm running check the mac address and change if necessary; or just stop any other xpeno vm before running this one.
  24. 2 likes
    а форум как здесь называется? про QNAP ни разу не видно по адресу и ищите патчик
  25. 2 likes
    I have been running DSM 6.0.2-8451 Update 11 (DSM_DS3615xs_8451-patch11) , seems to working great
  26. 2 likes
    Thanks ... so I'll go for a Gen8 with Xeon processor and ILO port ...
  27. 1 like
    why not checking old school, boot a live linux (like ubuntu or a recover/rescue system) and have a look at the disks in question you will see every disk contains 3 partitions 1st the dsm system, 2nd swap, 3rd data (raid x) the first two are raid1 over all disks in the system, that what dsam does when in "initializes" a disks ~4.4GB reserved for dsm system and swap that way the dsm system keeps always availibe as long as one disk is working, thet the way synology designed it
  28. 1 like
    Bonjour, Migration de DSM 6.0.2-8451 update 11 à DSM 6.1.3 15152 update 4 effectué sans probléme, juste tjrs besoin de rebooter deux fois après install ou update DSM sur mon Gen8, peut être le bios? Merci à @Polanskiman pour ces Tutos tjrs aussi lisible et sa disponibilité, @jun pour son ltravail sur le loader ainsi que @Genesys pour avoir converti le boot en MBR, bien plus pratique pour moi et obligatoire sur certaine autre carte mére. Merci à vous !
  29. 1 like
    первый выбор это само сабой 3710 так как на 916 почти такой только n3710 второй выбор это 4205 так как уже стоит столько же как и 3710 но новее и поддержка таже самая осталась
  30. 1 like
    у меня было при миграции с дсм5.2 /3615 на дсм6.1.3 /916 Подготовил флешку Загрузил флешку и ничего не выбирал, по умолчанию baremetal Нашел NAS c http://find.synology.com Выбрал чистую установку Загрузился, всё чисто и новая дсм, всё настраивал поновому и устанавливал приложения какие нужны а файлы старых приложений пришлось искать и подчищать, что вообщем то без проблем
  31. 1 like
    when ssh is working system partition will be up? you can user mdadm or cat /proc/mdstat to check the state if the raid https://raid.wiki.kernel.org/index.php/Detecting,_querying_and_testing i suggest to read a little before starting to repair anything and also a littel practicing befor in am vm with virtual box can also help, just install a ubuntu, add some disks (thin) create a raid with the disks, shut down remove 1 disk or two an try to recreate and repair your szenario before messing with your real disks/data
  32. 1 like
    только сейчас заметил вы заходите как пользователь, так вас не пустит, нужно root получить! login as:admin admin@'s password: admin@916:~$ sudo -i Password: root@916:~# P.S. актуально сейчас эта сборка, подробнее здесь
  33. 1 like
    to hyperion LibreELEC никак не связано с Synology, никакие приложения Synology соответственно на LE не станут
  34. 1 like
    Buenas tardes a la comunidad. Llevo pasando mucho tiempo por el foro pero este es el primer post que escribo para intentar ayudar a todos si quereis montar el XPEnology virtualizado en ESXi 6.0 Tras pegarme con mi Microserver G8 y querer montar ESXi 6.0 u2 customizado para HP en el para virtualizar DSM, os dejo este pdf: https://mega.nz/#!mMo00Qja!AmEI5Lu-pUMb ... n7dTcVi-yg En el encontrareis un manual paso a paso que he realizado para la migración de la versión 5.2 a la 6.0 o instalación de esta o posteriores versiones del lanzador de JUN ya que parece ser que los que saca son prácticamente iguales. **Aviso que la migración de la 6.0 a la 6.1 no me ha funcionado tras intentarlo varias veces con el lanzador alpha que es el que actualmente existe para la 6.1, sin embargo la migración de la 5.2 a la 6.0 me ha ido sin problemas y funciona de mil maravillas. Espero que os sirva de ayuda. Un saludo
  35. 1 like
    - Si le problème était la clef USB alors elle ne 'booterait' même pas, donc non. - L'adresse MAC je ne peux pas la valider étant donné que je n'ai pas le matériel sous les yeux. Minuscule ou majuscule cela importe peu je pense mais vous pouvez essayer avec des majuscules voir si cela aide. le S/N il suffit de le généré. Lire le tuto. - Pour les partitions oui cela est normal. Lire le tuto. - Il n'y a pas de ligne AMD avec le loader v1.02(a/b) et cela est normal mais je tiens à rappeler que ce tuto est fait pour le loader v1.01 sous DSM 6.0.2. - Le switch ne pose pas de problème étant donné que cela marche avec DSM 5.2 > Refaites la clef USB avec le loader v1.01. Il n'est pas nécessaire de désactiver C1E avec le loader v1.01 à priori, du moins je n'ai pas le souvenir que quelqu'un ai eu à faire cela sour le loader v1.01. > Faites en sorte qu'il n'y ai pas de conflit d'IP / MAC sur votre routeur. C'est à dire que l'adresse MAC ne soit pas utilisée par un autre matériel sur le réseau. > N'utilisez pas le ramdisk extra.lzma personnalisé que je poste. Les gens sous N54L n'ont jamais eu à l'utiliser à ma connaissance. > Désactivez IDE dans BIOS. Activez AHCI. > Faites en sorte avant la migration que sous DSM 5.2 le MTU (Jumbo Frame) soit à 1500. Pas plus. > Dans le fichier grub.cfg changez set timeout='1' à set timeout='5' Cela vous donnera le temps de sélectionner la 4ième ligne dans le menu Grub 'AMD with Jun's Mod v1.01'. > Une recherche du fil de discussion et du forum ne fait jamais de mal: https://xpenology.com/forum/search/?&q=N54L&type=forums_topic&item=6367&sortby=relevancy
  36. 1 like
    This one works with DSM 6.0.
  37. 1 like
    http://spk.diablos-netzwerk.de/ Судя по обновлению Можно пробовать. Сам не проверял. Интересная тема-обсуждение.
  38. 1 like
    выбор у вас только между 3615 и 3617, для 916 железо, точнее проц полностью не совместим дсм 3615 предпочтительней для вашего проца и к тому же все приложения остаются 3617 имеет смысл только с новым железом и процем начиная с фамилии "broadwell" и по этой же причине большинство приложений не доступно так как они для "bromolow"
  39. 1 like
    Hi everyone, I`ve been having an interessting issue since the upgrade to DSM 6.1, and I can`t seem to find a solution. Before the upgrade i had 2 shared folders named backup and backup 2. After the upgrade, i removed these backup folders, as they were no longer necessary. The problem is, that these 2 folders are still visible on all windos clients using the SMB / Samba protocoll. (tested with 3 PCs, one of them was never connected to the DSM before, see picture "Shared folders client.jpg"). I checked the shared folders on the DSM, and also using the console (see pictures "SynologyControlPanel.jpg" and "folders Putty.jpg"). I also tried restarting the samba service on the DSM, disabling the "Local Master Browser" and restarting the DSM several times. None of this helped. Does anyone have a similar issue? Or maybe even know the solution? Any help would be appreciated. Thanks !
  40. 1 like
    Avez vous cherché le forum principale en anglais et le fil de discussion du développeur? https://xpenology.com/forum/topic/6253-dsm-6xx-loader/?do=findComment&comment=54156 Le loader est à la version 1.02b. Stable.
  41. 1 like
    hallo, das einzig konkrete das mit da einfällt wäre der support von mehr als 8 cores bei der 3617 je nach dem wann synology aufgehört hat die 3615 zu verkaufen wird es einige jahre danach keine neue dsm version mehr für diese "alte" hardware geben, die 3617 wird das endenziell später ereilen aber ob das in absehbarer zeit relevant ist bezweifle ich ich erwarte eher das die immer mehr funktionen mit seriennummer und anderem schutz absichern um den freeloadern das leben zu erschweren (aber OMV ist ja auch nicht so schlecht und arbeitet direkt mit den raid platten einer synology dsm ohne das man was ändern muss, ein switch ist also einfach zu machen)
  42. 1 like
    WOL finally works! I've created a short script saved in a file I named ETH0wake.sh and placed it in usr/local/etc/rc.d, along with S99PowersavingIntel.sh and S99ZZZ_Shutdown.sh. The content is very simple, enables (at boot and stop) the wakeup flag of the Q1900 LAN which was always "disabled" for me, you can test by typing: cat /sys/class/net/eth0/device/power/wakeup and the "ethtool -s eth0 wol g" to force enable WOL at boot and stop. I really suck at scripts and I know it's not a good idea to put sudo command, but it works for me, so you could try on your own Q1900 or other hardware if WOL is not working. If someone with good knowledge can make it better, that would be awesome! so, go to the rc.d folder by ssh, then "vi ETH0wake.sh", type "i" to switch to edit mode and copy/paste the following content: #!/bin/sh case $1 in start) sudo sh -c "echo enabled > /sys/class/net/eth0/device/power/wakeup " sudo ethtool -s eth0 wol g ;; stop) sudo sh -c "echo enabled > /sys/class/net/eth0/device/power/wakeup " sudo ethtool -s eth0 wol g ;; esac then hit "ESC", type ":wq" and give 755 permissions to the file. It works for me, I did test with DS Finder on my smartphone but I suppose it works too with my tomato router WOL menu, hope it will be the same for other Q1900 owners.
  43. 1 like
    только что переехал наконец то на железе из подписи с dsm5.2 на крайнюю 6.1.3 и всё ради того чтобы узнать про аппаратное кодирование на 916+ и докладаю что есть: при этом за процесс отвечает gst-launch-1.0 и нагрузка как видим в норме не более 10% : что касается переезда то в любом случае вам будет предложена миграция дальше два варианта: с сохранением всех данных чистая установка но разделы файлы все остаются я испробовал оба при первом действительно всё сохранилось но насколько корректно настройки приложений точно не проверял так как почти все приложения запросили востановления и обновления также слетела учётка сино что для меня не приемлимо из за лицензий на кодеки при чистой установке учётка прошла успешно но все настройки слетели при этом файла от приложений и даже контейнеры докера сохранились
  44. 1 like
    Update. The 6.1 loader is working on AMD Ryzen (with SMT/all cores & threads enabled) via ESXi 6.5 update 1.
  45. 1 like
    1 - Turn off machine and remove usb with v1.02a loader. Keep that usb aside in case you need it later. 2 - Burn new loader v1.02b on usb. Make sure to edit the grub.cfg file like you did for v1.02a (vid/pid, SN, MAC etc). When done, plug the usb key on the machine 3 - Turn on the machine 4 - Use find.synology.com or Synology Assistant to find the machine on the network 5 - Migrate the machine by following the steps indicated on screen. You will be asked to provide the PAT file for 6.1.3 so download it first. See my signature for download links. 6 - Let it update. After a while you should be under DSM 6.1.3. You can then apply through the GUI critical updates 1, 2 and 3 if desired.
  46. 1 like
    Hi! Use Jun's loader v1.02b + the latest DSM Just look at this video for a tutorial:
  47. 1 like
    because the loader packs a earlier kernel & ramdisk with it, and they are expected to be upgraded to latest version during install or upgrade process. that is how the loader is able to support multiple dsm version, and allows you to apply latest security fix, if kernel version code does not change. Thanks a lot for the clarification! I've also managed to get around the "general protection fault: 0000 [#1] SMP" issue when enabling SNMP or visiting the system info page. Seems like disabling the LSI cards BIOS and enabling CPU hotplug in ESXi will do the trick. I can't reproduce the bug anymore and everything works a lot better now. I now get a ton of these in dmesg, but it doesn't seem to do any hard (still trying to figure out how to remove them as well): [30377.275744] do_IRQ: 0.218 No irq handler for vector (irq -1)
  48. 1 like
    I'm having the same issue as you. noVNC no longer works after the first reboot at the end of the Windows installation. I started on DSM 6.1 -something, upgraded to 6.1.2-15132 then again to 6.1.3-1512, all on the same baremetal Dell. Reinstalling the VM each time I upgraded DSM (VMM had an update at 6.1.2). No luck. I did notice that installing Ubuntu 16.04 Server works after all reboots. I SSH to the xpenology box, ran top and noticed it is using qemu as the hypervisor. I've tinkered with qemu/kvm with Openstack before, but can't remember much about it. Though, I did notice that after about five seconds after powering on, the Windows VM goes into a "paused" State. To watch this from the terminal, type "virsh list --all". The number one cause of this error for qemu/virsh appears to be out of disk space on the storage (According to my Google searches ). I verified that my 100GB virtual disk fits just fine on the 500GB volume, and then recreated it on the 4TB volume just to make sure. No luck on either one. I lowered the RAM and the CPUs from 4GB/2Cores to 1GB/1Core. Still no good. Note that the Ubuntu VM is 2 cores and 2GB RAM. Sorry I don't have an answer yet, but I'll keep looking into it. I wanted to post this in case it may spark some interest. TLDR: The Ubuntu VMs stay in the "running" state, noVNC works fine. The Windows VMs go to a "paused" state, noVNC don't work.
  49. 1 like
    Normally yes by connecting a serial cable from your NAS to a laptop/computer and running a serial terminal on your laptop/computer. But I think HP n54L does not have a serial port. Did you try re-burning the usb drive?
  50. 1 like
    Hi I have installed version 6.0.4 onto my HP NL54 4GB Ram Baremetal has anyone noticed they whole system been slow? Was fine with DMS 5.2 Cheers