Popular Content

Showing most liked content since 10/17/2017 in all areas

  1. 5 points
    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. To upgrade from DSM 6.02 to DSM 6.1 read here. 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) [27/09/2017] Added link to upgrade procedure from DSM 6.0.2 to DSM 6.1 in top paragraph [22/10/2017] Update jun's loader link to https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng!EscjTCAB and mirror link to https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg!iJZjAJoa - Directly to v1.02b Hide
  2. 5 points
    Unfortunately, this topic has become a dump and that's not right. It is time for members to start respecting the work that I and others moderators are doing here. I have totally re-structured the forum so that you can post your questions in the appropriate sections/forums/sub-forums. The time of wild posting is over people. Either you respect the rules and guidelines or your post will be deleted without any hesitation, no warning given. I prefer spending my time helping people resolve their issues rather than wasting my time moving around posts and topics. There are 5 new moderators onboard that will make sure the rules are being respected. I am temporarily locking this topic so that people can start looking around the forum and ask their questions in the appropriate sub-forums. Do not ask me to unlock this topic. Your request will be ignored.
  3. 3 points
    open-vm-tools 6.1_10.1.15 http://spk.4sag.ru/
  4. 3 points
    Hello, The Jun's versions 1.01 (DSM 6.0.2) and 1.02B (DSM 6.1X) are rebuild with a MBR partition table. I have put on the repository all images that i have rebuild with my automated conversion (MBR Partition table versions) tool. The repository link is here : https://mega.nz/#F!cIUXnCSS!VruDf235t2uLcRxIjji3qQ Hoping to move forward the XPEnology community. PS : The files "Convert_By_Genesys" contains the number of loader version and the partition table format use. PS2 : I will continue to make MBR Partition table version for next loaders. PS3 : The code base of my Automated Conversion Tool is the same as Jun's : https://github.com/kref/scripts
  5. 2 points
    Смаунтить диски в другой системе, поискать файл group и поправить его. /etc/group -- это ASCII-файл, описывающий группы, к которым принадлежат пользователи. В нем находятся однострочные записи в формате group_name:passwd:GID:user_list для примера можно посмотреть на другой сино какие там записи и как они правильно выглядят. Либо тоже смаунтить диски и попробовать сделать chroot и уже из системы включить ssh: т.е. обычно порядок такой: загрузился в убунту, сделал маунт proc, sysfs и dev, потом винты, и потом делаешь chroot в папку + указывают путь до bash. Все, ты в своей сино с её окружением. Находишь конфиг ssh правишь его, и добавляешь в автозапуск.
  6. 2 points
    DS3615xs 6.1 Jun's Mod V1.02b на флешку запиши и будет тебе счастье!
  7. 2 points
    Can everyone specify what hardware they are using when posting please.
  8. 2 points
    Hi All If you read my thread about the boot loader updating itself you will understand. I've assembled a revised 'boot loader' that has been updated to 15152 (6.1.3) and should be able to be used to 'reflash' a damaged USB without the risk of version errors and also a clean build. This is based on Jun's 1.02b (DS3615 only) with the v3.2 extra.lzma file from @IG-88 and apart from my vid/pid changes is otherwise unchanged. Process Used:- Created a new image incorporating v3.2 extra.lzma and my vid/pid with OFSMount Flashed a new USB with that image Booted system, found as 6.1-15047 Install DSM 6.1-15047 to HDD Manual update to 6.1.3-15152 Shutdown/remove HDD/reboot to check - came up as 6.1.3-15152 'uninstalled' Created boot .img file from the updated USB disk Flashed a different USB with this image (changed vid/pid) and booted - came up as 6.1.3-15152- uninstalled. Putty Serial output all looked ok with no serious errors I've put a copy of this in a dropbox folder for others to check/test, its a zip file to extract. Note that I had to choose UEFI boot partition 1 for the USB to boot . https://www.dropbox.com/sh/1l0ibcm90ophsz6/AAAIgnajXZx0f98FVDNFrZLea?dl=0 Note that this is purely an exercise to help and is not meant to replace the forum ratified loaders and any use is at your own risk, so please test before use and backup any critical data.
  9. 2 points
    радуют сообщения от бобика который бывший билдер который теперь Архип. Дружище, держи нас в курсе, только уточняй, что используешь оригинальную\пизженую пару и что твоё "а у меня такая же нога и не болит" не относится к данной теме
  10. 2 points
    open-vm-tools 6.1_10.1.15 http://spk.4sag.ru/
  11. 2 points
    HP Gen 8 microserver baremetal install no raid arrays or anything fancy, 6.1.4 all OK here thanks Synology and XPenology teams
  12. 2 points
    а смысл? генератор больше не рабочий совсем! забудте про сервисы сино, настраивайте ddns доступ своими средствами здесь революционная раздача на весь ноябрь раздача активируется через промокод 1917, который необходимо ввести в "Комментарий"
  13. 2 points
    you mean "the source of the kernel" if they decide to secure the compiled code or any package with a signature there is nothing wrong, as long as you dont have the private key you can't reproduce the signature, and the fact that you can read the source code for the checking procedure does'nt help you to use a original dsm file as it's done yet one way would be to "invalidate" the code that is checking it at runtime/booting (nicer words for hacking the running system to not do checks) lets not jump to conclusions as it is to early, and looking into this might be the task of someone trying to make 6.2 run on "unauthorised" hardware 1st step might be to just make it run on a system thats not made by synology with the drivers that come with the dsm release btw the melanox drivers are not part of 916+, i have not "mapped" the drivers in that release yet but a addition to signed drivers would be to only release drivers in a package that are needed and nothing additional, makeing it harder to succeed after 1st step (and every hardware plattform/box gets there own private keys so you can't swap drivers from one to another), but thats just mind games of what might be, atm we can only stand on the fance and wait (and there is no urgent need, 6.1 is running fine, and i have'nt spotted a killer feature in 6.2 that is missed by everyone)
  14. 2 points
    Problem solved! Ok, what happened and what people should try. Because while I had problems described in the first post, the system kinda worked, so I planned to migrate it on weekend. Thus on Friday I got a warning from the Security Advisor that DSM system files have incorrect hash values, more precisely, libsynostoragemgmt.so The file had the same size and date as in other, perfectly working server, namely: However, when I replaced it with a version from the working server, the system was able to reboot normally (previously only hard reboot helped) and is ok ever since. So, if you have a similar problem 1. Scan your system with the Security Advisor 2. If there are wrong hashes, replace the mentioned files, check that their attributes are correct 3. reboot
  15. 2 points
    Да! Но при установке выбрать с сохранением данных, и в принципе лучше через ассистент сиро это делать, там как по мне проще...
  16. 2 points
    поздравляю с успехом! на будущее (мож ещё кому пригодится): если нужно только прочитать данные - можно попробовать UFS Explorer Professional Recovery тестировал под виндой чтение стандартных рейдов, создаваемых из-под Synology, и она показала себя очень хорошо. SHR не тестировал, работает ли с ним - не знаю.
  17. 2 points
    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
  18. 2 points
    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.
  19. 2 points
    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
  20. 2 points
    Hi, Thanks to Aigor and IG-88 i managed to compile drivers in Bash for windows. I used snippets from both users to make this tutorial! Thanks for that! Follow the tutor here: http://xpenology.club/compile-drivers-x ... d-in-bash/
  21. 1 point
    @worlok https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg!DYRAXCpB вот этот
  22. 1 point
    I have updated it on my G7 N54L, but DSM doesnt need a reboot. Everything run like always (transmission, docker, plex, owncloud, filestation, etc)
  23. 1 point
    вариантов решения несколько: - разобраться с пробросом портов и с маршрутами - завести умный ролтер (ака pfsense) в котором прописать ns записи для локального адреса, чтобы локальная сеть знала, что хрено.маясеть.ру это (пример) - прописать на каждой машине в хостах значения "имя.домена ip"
  24. 1 point
    Hi All I was doing some testing to prep for updating some systems and noticed that the 1.02b boot loader updates to the latest version of DSM installed/updated to. In my test; Created a new flash drive with 1.02b vid/pid etc Booted system with a clean hdd attached and Syno Assistant found as '6.1-15047' uninstalled Installed DSM 6.1-15047 - ok Setup rest of system - ok Update to DSM 6.1.3-15152 - ok I removed the attached drive and rebooted (no drives attached) - Assistant found the system as '6.1.3-15152' uninstalled. I hadn't thought that a DSM update would 'write back' and alter the boot loader, of course its not a problem and makes sense because thats what happens in a real Syno system. However it could be a problem if a boot loader gets corrupted, reflashing with the default 1.02b/6.1 image may cause version problems. You would need to have a spare drive/hardware to install 6.1-15047 then update to 6.1.3-15152 to bring the loader back into sync with your production DSM version.
  25. 1 point
    Yes same file. You can compare md5 you will see. I simply renamed it in the mirror to make it more explicit and avoid people confusion when they downloaded several images.
  26. 1 point
    Synology have withdrawn this update for now, so I would suggest staying on 6.1.3-15152.
  27. 1 point
    вообще-то разницы большой нет, всё равно модуль один и тот же r8168, должно работать, причина в другом дров хватает для 916 интересны и нужны модули i915
  28. 1 point
    I did an update for my HP Gen8 Server with an Intel Xeon E3 1265L 16Gbyte Ram and LSI Raid Controller. Everthink seems to be ok.
  29. 1 point
    HI All, Just finished upgrading from DSM 5.2 to DSM 6.1 on my DC7900 HP Tower, there are some things that need to be taken into account when proceeding: -UEFI boot is not wokring on this machine so you need the other loader on top of the page. -Nic card is recognized, but not stable on the build in NIC, looses ping and not reachable for some devices in the network, so a added an Intel MT1000 card which work fine. -After updating packages all seems to work fine and sync and backup jobs even work well. What does not work: -My Sundek TV tuners are not recognized anymore, even when re-installing the drivers -TVHEADend acting strange (keeps asking for password), first need to figure out the TVtuners Rest seems to be stable and I can now use the latest packages available, docker was actyually the one i wanted to have on the latest version. If someone figures out on how to get the SUNDTEK DVB-C and DVB-S tuners working, please share so I can used TVH again. If you have any questions regarding the DC7900 just let me know. Cheers, Hemant
  30. 1 point
    если нужна 3615 то нужен новый номер из 13 знаков
  31. 1 point
    Я цитирую не первоначального автора, а предидущего, что бы было легче понять, о чем речь... Если я не правильно понимаю, то как бы можно меня поправить, написав, как правильно, я не обижусь, а без этого вы выглядите как-то не убедительно, и даже немного странно, это все же технический форум, а не место для тренировки собственного эго. П.с. Архип, а вы случайно не Bob The Builder? Очень уж манера общатся характерная...
  32. 1 point
    Делюсь опытом. Установил я сначала 4 HDD по 3 ТБ отформатировал в SHR-1 btrfs, потом решил добавить еще 2 диска по 2 ТБ с трудом нашел куда все слить с них. Вставил в систему и решил добавить к SHR-1 но не тут то было не захотел массив расширяться хотя я изначально выбрал максимальное количество дисков 24 для системы. Не знаю почему он не захотел добавлять прочитал кучу мануалов все делал как пишут ну ни в кукую. Решено было ставить все заново снес все установил 4 по 3 ТБ и 2 по 2ТБ объединил в один массив SHR-1 c одним отказоустойчивым диском и получил общий объем в 12 ТБ из 16 ТБ реальных, думаю неплохой результат. Если выбрать 2 отказоустойчивых диска то предлагается 9 ТБ. Фото системы 6 дисков Hide
  33. 1 point
    да, будет поменять нужно только на соответствующую каждой модели серию из букв старые модели до сих пор ещё имеют 10 значные номера, что по новее уже 13 значные
  34. 1 point
    а в чем сакральный смысл экспериментировать не на последнем загрузчике? последний - v.1.02b vid и pid нужны для загрузки с флеш-накопителя, подключенного по usb. без них только на виртуальных машинах будет работать. прописывать в grub.cfg (плес, не спрашивай где этот фаил - в гайдах всё максимально подробно разжевано)
  35. 1 point
    потаму что в вашем плексе не активированно аппаратное ускорение кодирования и декодирования видео аппаратное ускорение Hide для этого вам нужна учётка плекса: https://forums.plex.tv/discussion/comment/1530030/#Comment_1530030
  36. 1 point
    I'm using Jun's 1.02b loader.
  37. 1 point
    Hi To remove the app. Did this last night as been getting the same error's as above just have not reinstalled to test again. was going to look for virtualbox spk as had that on DSM 5.2 SSH in ls /volume1/@appstore to get a list of apps installed Try synopkg stop Virtualization synopkg uninstall Virtualization OR This will remove all the files rm -rf /volume1/@appstore/Virtualization Reboot and it will be uninstalled on my test vm i had to open package center and the uninstall again and rebooted.
  38. 1 point
    не надо тут ничего организовывать !!! все через личку !
  39. 1 point
    Фух, решил проблему, короче получилось только так: 1. На загрузчике 5.2 устанавил через веб последнюю версию, с форматированием раздела для хреньки. После перезагрузки вставил загрузчик (но не каждый подходит) мой назывался "synoboot102b.img", другие не справляются, затем нажал на восстановить и вуаля запустился после ребута. Данные все целые. Спасибо всем кто старался помочь.
  40. 1 point
    А собственно что вы пробовали и что получалось? Из dsm (там где емейл уведомления) отправку почты настроили? Тестовые емейлы проходят? Если это все сделано - то потом из php емейлы можно отправлять как-то так: // Set the email header // Generate a boundary $boundary = md5(uniqid(time())); // Email header $header = "From: ".$from_name." <".$from_mail.">\r\n"; $header .= "Reply-To: ".$reply_to."\r\n"; $header .= "MIME-Version: 1.0\r\n"; // Multipart wraps the Email Content and Attachment $header .= "Content-Type: multipart/mixed; boundary=\"".$boundary."\"\r\n"; $header .= "This is a multi-part message in MIME format.\r\n"; $header .= "--".$boundary."\r\n"; // Email content // Content-type can be text/plain or text/html $header .= "Content-type:text/plain; charset=iso-8859-1\r\n"; $header .= "Content-Transfer-Encoding: 7bit\r\n\r\n"; $header .= $message."\r\n"; //last boundary, with "--" on the end $header .= "--".$boundary."--\r\n"; mail($mail_to, $subject, $message, $header, "-f your_email@something.com"); Но удобнее использовать готовый php class, я пользуюсь скачанным отсюда: http://github.com/PHPMailer/PHPMailer Тогда отправка письма выглядит примерно так: require_once ('/volume1/your_path/PHPMailer-master/class.phpmailer.php'); // $email = new PHPMailer(); $email->From = $from_mail; $email->FromName = $from_name; $email->Subject = $subject; $email->Body = $message; $email->AddAddress($mail_to); $email->Send(); Оба куска кода выдраны из готового скрипта, первый работал, но был заменен на второй. Возможно при выдирании первого куска я мог что-то и пропустить (во втором пропустить что-то сложно), если не заработает - дайте знать.
  41. 1 point
    Sorry haven't been around for a while - and as I'm running DSM on ESXi not using powerbutton anymore myself. I added braswell to INFO: powerbutton_6.1-0005.spk
  42. 1 point
    beside this if i open the kernel modules in a hex editor there is the following at the and of each module "...Synology SDG kernel module signing key...~Module signature appended~" could mean the modules to load have to be signed and i dont expect the signig key to be part of a open source kernel release so this might be a additional hurdel for a using dsm with other hardware
  43. 1 point
    Not surprising. DSM 6.2 kernel version is 4.4 admin@VMMDSM62beta:/$ uname -a Linux VMMDSM62beta 4.4.59+ #22259 SMP PREEMPT Mon Oct 2 02:45:21 CST 2017 x86_64 GNU/Linux synology_kvmx64_virtualdsm Jun's loader would need to be updated first and more specifically his hack. This is just a beta so no real value of updating a loader for that. You can either try the Live demo or install DS 6.2 on VMM.
  44. 1 point
    You need to stopp all virtaul services from cli and remove the app folders manually. There was a thread about it, i did not find em anymore. sorry. Its also not working with my xeon bare metal.
  45. 1 point
    maybe you can use the (internal) cdrom/dvd connector with a adapter for a hdd? also i would have said the same as abced but then i found this: https://hedichaibi.com/fix-xpenology-problems-viewing-internal-hard-drives-as-esata-hard-drives/ that guys intension was to correct the numbering on his sata drives (a "gap" seems prevented the normal numbering in a row), but if you have a look to the last picture he kind of accidently made his usb flash drive a intern hdd (disk21), so you might be able to convince dsm that a usb drive is internel (even if no one would recommend doing it) i'm still not getting it why the flash drive is a hdd, from the configuration data it looks ok, only "mistake" i can spot is that he did not set the "maxdisks" drive numer (if not changed it will be 12 so the flash drive is number 13 and above the maxdisks) @vladiwan as you are new i dont think you should try this, if things go wrong or you make mistakes you can easyly mess up your system
  46. 1 point
    Всем привет. Наконец я решился и совершил переход с XPEnology 5.2 на 6.1 под ESXi с сохранением всего (настроек и данных) по максимуму. Конфигурация: Мат. плата / CPU: GA-N3150N-D2H Плаформа DS3615xs (до и после обновления) ESXi 6.5.0 (Build 5310538) За основу взял конфигурацию виртуальной машины, приведенной в этом топике, которую изменил. Хочу обратить внимание, что загрузочный диск сделал просто IDE и удалил SATA контроллер. Диски кроме Storage, все RDM (Raw Device Mapping). Единственный контроллер дисков: SCSI Controller 0 : VMware Paravirtual Вся сеть тоже на паравиртуальных адаптерах VMXNET 3 Загручик я выбрал BIOS Вместо UEFI. Также я убрал все ненужные мне USB контроллеры. Все как обычно: пропиывание SN, прописывание MAC-ов сетевух. При загрузке выбирал пункт DS3615xs 6.1 VMWare/ESXI with Jun's Mod v1.02b. Далее загрузка pat и т.д. На выходе получилась работающая система с 90% сохранением настроек из 5.2, в том числе сохранился SSL сертификат, настройки OpenVPN сервера, большинство пакетов и их настройки (Udpxy, Transmission, Serviio) . Пришлось только отдельно ставить Web Station + PHP, т.к. web сервер в 6.1 был выделен в отдельных пакет, еще функция бекапа тоже в отдельном пакете Hyper Backup, настройку которой я еще не проверял/не делал. Единственно, что не могу побороть еще со времен 5.2 (на 6.1 та же проблема) это при выключении XPEnology через Web-меню происходит не выключение, а перезапуск виртуалки. Может кто знает решение?
  47. 1 point
    virtio drivers are supported in my loader which will be released once I iron out ESXi upgrades. KVM and baremetal are solid though. Also performance is great as iperf3 has proved great performance. DiskStation> iperf3 -c -i 1 -t 20 -R Connecting to host, port 5201 Reverse mode, remote host is sending [ 4] local port 44805 connected to port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 844 MBytes 7.08 Gbits/sec [ 4] 1.00-2.00 sec 879 MBytes 7.38 Gbits/sec [ 4] 2.00-3.00 sec 898 MBytes 7.53 Gbits/sec [ 4] 3.00-4.00 sec 768 MBytes 6.44 Gbits/sec [ 4] 4.00-5.00 sec 883 MBytes 7.41 Gbits/sec [ 4] 5.00-6.00 sec 899 MBytes 7.54 Gbits/sec [ 4] 6.00-7.00 sec 900 MBytes 7.55 Gbits/sec [ 4] 7.00-8.00 sec 878 MBytes 7.37 Gbits/sec [ 4] 8.00-9.00 sec 907 MBytes 7.61 Gbits/sec [ 4] 9.00-10.00 sec 883 MBytes 7.40 Gbits/sec [ 4] 10.00-11.00 sec 906 MBytes 7.60 Gbits/sec [ 4] 11.00-12.00 sec 828 MBytes 6.94 Gbits/sec [ 4] 12.00-13.00 sec 898 MBytes 7.54 Gbits/sec [ 4] 13.00-14.00 sec 910 MBytes 7.64 Gbits/sec [ 4] 14.00-15.00 sec 758 MBytes 6.36 Gbits/sec [ 4] 15.00-16.00 sec 753 MBytes 6.32 Gbits/sec [ 4] 16.00-17.00 sec 841 MBytes 7.05 Gbits/sec [ 4] 17.00-18.00 sec 960 MBytes 8.05 Gbits/sec [ 4] 18.00-19.00 sec 858 MBytes 7.20 Gbits/sec [ 4] 19.00-20.00 sec 933 MBytes 7.83 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-20.00 sec 17.0 GBytes 7.29 Gbits/sec 0 sender [ 4] 0.00-20.00 sec 17.0 GBytes 7.29 Gbits/sec receiver iperf Done. And it is better to use synoboot.img as virtual USB drive because then it properly works with upgrades.
  48. 1 point
    DSM PAT files can be found here (Major updates): DSM 6.0.2: http://usdl.synology.com/download/DSM/release/6.0.2/8451/ Chose .pat file DS3615xs DSM 6.1: http://usdl.synology.com/download/DSM/release/6.1/15047/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.1: http://usdl.synology.com/download/DSM/release/6.1.1/15101/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.2: http://usdl.synology.com/download/DSM/release/6.1.2/15132/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.3: http://usdl.synology.com/download/DSM/release/6.1.3/15152/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates for all DSM versions can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/ or http://usdl.synology.com/download/DSM/criticalupdate/update_pack/ Critical Updates specifically for DSM 6.0.2 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-2/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-3/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-4/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-5/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-6/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-7/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-8/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-9/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-10/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-11/ Chose .pat file DS3615xs Critical Updates specifically for DSM 6.1 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15047-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15047-2/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.1 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-2/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-3/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-4/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.2 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15132-1/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.3 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-2/ - Does not apply to DS3615xs or DS3617xs or DS916+ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-3/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-4/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-5/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-6/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-7/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-8/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly --------------------------------------------------------------------------------------------- All links above are provided for the sake of completeness but simply going to: https://www.synology.com/en-global/support/download or http://usdl.synology.com/download/DSM/ and then clicking the desired subsequent links will yield all the above. Seek and you shall find. Change log [22/09/2017] Changed http://download.synology.com/download/DSM/release/ to http://usdl.synology.com/download/DSM/release/. Synology closed all DSM release downloads from http://download.synology.com/download/DSM/release/. Only Critical updates are available in that repository to this date. Hide
  49. 1 point
    Why not just either pay for or use a DDNS service? I do this and have no issues.
  50. 1 point
    now that i've had 3 months of testing with these drives. I can say they can't be used reliably. I've tested this in a 4 bay synology and my own built box. For some reason, 1-3 of these drives loaded in one box is FINE. runs ok. Once I add the 4th drive, it starts slowing down and hanging when browsing directories. It will eventually freeze. Sometimes a few minutes after boot -- sometimes a few hours in. This causes me to have to reboot and recover the volume. I thought it might have been just one drive out of the four have gone bad, but that didn't end up being the case as I've tried it rotating all 4 drives in as the final 4th addition. Mine are also all Recertified (from the early failing issues these had) with CC1H FW. I also found a few threads online stating these drivings are not recommended for more than 2+ raid configurations (which sounds like BS) As far as my own rig, I removed one drive and let the volume run in Degraded for a while until I had time to play with it. Now I have 2x 5TB Red's in there and all is well.