Leaderboard

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--- Tutorial by polanskiman: here (made for loader v1.01 but can be used for loader v1.02a and above. Just keep in mind that if you wish to customised the extra.lzma ramdisk, Jun changed partitioning since v1.02 so now kernel and ramdisk are in the second partition) Loader download mirrors: here (managed by Polanskiman) including .ISO format. These are plain and simple copies of Jun's loaders, no mods. here (this mirror is currently offline) For info: v1.01 (DS3615xs) is for DSM 6.0.2 - AMD compatible - Latest version for DSM 6.0.2 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 v1.02b (DS3615xs, DS3617xs and DS916+) is for DSM 6.1 - AMD not compatible - Latest version for DSM 6.1 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

its an old script bug due to my oversight, I am uploading a new version to fix it, hopefully without introduce new bugs

Есть у меня старенький UPS Powercom IMP-425AP. Давно хотел его подключить к Synology, но дело осложнялось тем, что он является устройством типа USB to Serial, и официально не поддерживается. В интернете гуглится статья на эту тему, по адресу: https://forum.synology.com/enu/viewtopic.php?f=39&t=17658 Но статья давно устарела, т.к. там идёт речь о DSM 3.0-1337 Сразу предупреждаю, я не очень "грамотный" пользователь *nux систем, но, собрав по крупицам некоторую информацию, я всё же смог подключить свой UPS Powercom IMP-425AP к DSM 6.1-15047 Может, я где-то допустил ошибки, но и итоге всё работает. Надеюсь мой опыт будет кому-то полезен. И так, наш UPS в системе определяется как: Bus 002 Device 004: ID 0d9f:0002 Powercom Co., Ltd Black Knight PRO / WOW Uninterruptible Power Supply (Cypress HID->COM RS232) (С таким ID 0d9f:0002 есть целая серия старых IMP-*25AP) Для DSM 6.1-15047 я использую загрузчик Jun's Loader v1.02b Вначале мы воспользуемся советами, описанными в этой статье: https://xpenology.com/forum/topic/7187-how-to-build-and-inject-missing-drivers-in-jun-loader-102a/ Качаем исходный код ядра: https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/15047branch/bromolow-source/linux-3.10.x.txz/download Synology 3615xs построен на архитектуре bromolow, нам нужна версия 15047 (я использую эту версию, т.к. в ней работает нужный мне VirtualBox) Устанавливаем плагин debian-chroot ( https://synocommunity.com/package/debian-chroot ) из раздела сообщества. Запускаем chroot: /var/packages/debian-chroot/scripts/start-stop-status chroot Ставим пакеты 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* lzma Создаём рабочий каталог «/volume1/@appstore/debian-chroot/var/chroottarget/test/» Распаковываем в каталог /volume1/@appstore/debian-chroot/var/chroottarget/test/ исходники ядра linux-3.10.x.txz Заходим в каталог linux-3.10.x и запускаем cp synoconfigs/bromolow .config Делаем резервную копию конфигурации make ARCH="x86_64" oldconfig Настраиваем конфигурацию make ARCH="x86_64" menuconfig Выбираем «М» напротив драйвера Device Drivers/USB support/USB Serial Converter support/USB Cypress M8 USB Serial Driver Сохраняем конфигурацию и компилируем модули make ARCH="x86_64" modules Копируем скомпилированные модули cypress_m8.ko, usbcore.ko, usbserial.ko в рабочий каталог synology /lib/modules/ Не забываем проверять/выставлять права файлам: chmod 644 Дальше переходим к работе с пакетом NUT. Это нужно, чтобы скомпилировать модуль powercom Информацию по исправлению драйвера я нашёл тут: http://forum.pcm.ru/viewtopic.php?f=3&t=2627 Качаем исходники NUT 2.4.1 http://pkgs.fedoraproject.org/repo/extras/nut/nut-2.4.1.tar.gz/609ebaf2123fc7171d25a6c742dd7d66/nut-2.4.1.tar.gz Распаковываем их в каталог /volume1/@appstore/debian-chroot/var/chroottarget/test/ В каталоге /volume1/@appstore/debian-chroot/var/chroottarget/test/nut-2.4.1 создаём файл патча «patch-nut» с содержимым: --- drivers/powercom.c 2009-02-17 12:20:48.000000000 +0300 +++ drivers/powercom.c 2010-03-02 15:48:25.354735038 +0300 @@ -852,21 +852,30 @@ /* setup flow control */ types[type].flowControl.setup_flow_control(); - if (!strncmp(types[type].name, "BNT",3) || !strcmp(types[type].name, "KIN") || !strcmp(types[type].name, "IMP")){ + if (getval("type") == NULL){ if (!ups_getinfo()) return; if (raw_data[UPSVERSION]==0xFF){ types[type].name="IMP"; - model=IMPmodels[raw_data[MODELNUMBER]/16]; } if (raw_data[MODELNAME]==0x42){ if (!strcmp(types[type].name, "BNT-other")) types[type].name="BNT-other"; else types[type].name="BNT"; - model=BNTmodels[raw_data[MODELNUMBER]/16]; } if (raw_data[MODELNAME]==0x4B){ types[type].name="KIN"; + } + } + if (!strncmp(types[type].name, "BNT",3) || !strcmp(types[type].name, "KIN") || !strcmp(types[type].name, "IMP")){ + if (!ups_getinfo()) return; + if (!strcmp(types[type].name, "IMP")){ + model=IMPmodels[raw_data[MODELNUMBER]/16]; + } + if (!strncmp(types[type].name, "BNT",3)){ + model=BNTmodels[raw_data[MODELNUMBER]/16]; + } + if (!strcmp(types[type].name, "KIN")){ model=KINmodels[raw_data[MODELNUMBER]/16]; } linevoltage=voltages[raw_data[MODELNUMBER]%16]; Применяем патч: patch -p0 -l <patch-nut В драйвере powercom по умолчанию включена самопроверка батарей при каждом старте драйвера. Настройки или возможности отключения этой проверки – нет. Метод устранения этой особенности я подсмотрел здесь: http://forum.lissyara.su/viewtopic.php?t=17735&start=25 Если Вам это не актуально, можете данный шаг пропустить. В файле: /volume1/@appstore/debian-chroot/var/chroottarget/test/nut-2.4.1/drivers/powercom.c находим строчки: ... upsdebugx(1,"Detected: %s , %dV",modelname,linevoltage); if (ser_send_char (upsfd, BATTERY_TEST) != 1) { upslogx(LOG_NOTICE, "writing error"); dstate_datastale(); return; } ... и комментируем лишнее: ... upsdebugx(1,"Detected: %s , %dV",modelname,linevoltage); /*if (ser_send_char (upsfd, BATTERY_TEST) != 1) { upslogx(LOG_NOTICE, "writing error"); dstate_datastale(); return; }*/ ... Компилируем NUT (пути для конфигов и т.д. выставляем такие же, как у synology): ./configure --with-user=root --with-group=root --prefix=/usr/syno/etc/ups --sysconfdir=/usr/syno/etc/ups --datadir=/usr/syno/share make Копируем скомпилированный файл powercom из каталога /volume1/@appstore/debian-chroot/var/chroottarget/test/nut-2.4.1/drivers/ в рабочий каталог synology /bin Не забываем проверять/выставлять права файлам: chmod 644 Теперь нужно добавить скомпилированные драйвера, в загрузчик Jun's Loader v1.02b. Используем osfmount (под windows), чтобы извлечь «extra.lzma» (сжатый файл cpio) из synoboot.img (находится «extra.lzma» на втором разделе FAT). Osfmount часто используют для редактирования файла grub.cfg в synoboot.img. («extra.lzma» - содержит дополнительные драйвера *.ko, которые стартуют при загрузке) Скопируем «extra.lzma» в /volume1/@appstore/debian-chroot/var/chroottarget/test/extra-drv Для распаковки «extra.lzma» выполним команду: lzma -d extra.lzma Далее, извлекаем файлы из «extra»: cpio -idv <extra После чего файл «extra.lzma» можно удалить. В распакованный каталог …/usr/lib/modules/ копируем скомпилированные модули cypress_m8.ko, usbcore.ko, usbserial.ko, а в /etc редактируем файл rc.modules В конце списка EXTRA_MODULES добавляем свои три драйвера, без *.ko rc.modules выглядит примерно так: 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 cypress_m8 usbcore usbserial" 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" Дальше, внутри каталога, /volume1/@appstore/debian-chroot/var/chroottarget/test/extra-drv, создаём новый файл cpio, и сжимаем его lzma. Полученный, новый «extra.lzma» записывается в каталог уровнем выше. Выполняем команду: (find . -name modprobe && find . \! -name modprobe) | cpio --owner root:root -oH newc | lzma -8 > ../extra.lzma Полученный файл «extra.lzma», при помощи osfmount, записываем обратно в образ synoboot.img. Теперь произведём настройку DSM 6.1 Выполняем: insmod /lib/modules/cypress_m8.ko mknod /dev/ttyUSB0 c 188 0 chmod 644 /dev/ttyUSB0 Настраиваем скорость порта: stty -F /dev/ttyUSB0 speed 1200 cs8 raw (Дальнейшая настройка подсмотрена тут: https://xpenology.com/forum/topic/4413-dsm-52-5592-update-4-amp-serial-apc-ups/#comment-38621) Редактируем файл: /etc/rc Добавляем в KERNEL_MODULES драйвера «usblp cypress_m8 usbserial»: if [ $KERNEL_VCODE -ge $(KernelVersionCode "4.4") ]; then KERNEL_MODULES="usblp cypress_m8 usbserial llc p8022 psnap usbcore quota_tree quota_v2 crc-ccitt crc-itu-t zlib_inflate dm-bufio dm-snapshot" else KERNEL_MODULES="usblp cypress_m8 usbserial llc p8022 psnap usbcore quota_tree quota_v2 crc-ccitt crc-itu-t zlib_inflate dm-snapshot" fi В конце файла, перед exit 0 добавляем строку запуска службы UPS: /usr/syno/etc/rc.sysv/ups-usb.sh start В файле /usr/syno/etc/rc.sysv/ups-usb.sh правим строку StartAllDrv() { local DRV_LIST="usbhid-ups blazer_usb bcmxcp_usb richcomm_usb tripplite_usb" на StartAllDrv() { local DRV_LIST="powercom usbhid-ups blazer_usb bcmxcp_usb richcomm_usb tripplite_usb" Редактируем файл /usr/syno/etc/ups/ups.conf [ups] driver = powercom port = /dev/ttyUSB0 type = IMP Загружаем файл https://github.com/networkupstools/nut/raw/master/data/cmdvartab и копируем его в каталог /usr/syno/share/ На этом всё. После перезагрузки, UPS должен автоматически появиться в GUI: P.S. Посмотреть более подробный статус UPS можно командой: upsc ups admin@serv01:~$ upsc ups battery.charge: 100.0 driver.name: powercom driver.parameter.pollinterval: 5 driver.parameter.port: /dev/ttyUSB0 driver.parameter.type: IMP driver.version: 2.4.1 driver.version.internal: 0.12 input.frequency: 50.00 input.voltage: 226.0 input.voltage.nominal: 220 output.frequency: 50.00 output.voltage: 226.0 ups.load: 12.0 ups.mfr: PowerCom ups.model: IMP-425AP ups.model.type: IMP ups.serial: Unknown ups.status: OL

Тестирую новый генератор SN. Могу в ЛС поделиться SN + MAC для 3617 и 916, валидацию на сино проходят.

DSM PAT files can be found here: DSM 6.0.2: http://download.synology.com/download/DSM/release/6.0.2/8451/ Chose DS3615xs DSM 6.1: http://download.synology.com/download/DSM/release/6.1/15047/ Chose DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.1: http://download.synology.com/download/DSM/release/6.1.1/15101/ Chose DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.2: http://download.synology.com/download/DSM/release/6.1.2/15132/ Chose 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 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 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 DS3615xs or DS3617xs or DS916+ accordingly I am providing all links above for the sake of completeness but simply going to: http://download.synology.com/download/DSM/ or http://usdl.synology.com/download/DSM/ and then clicking the desired subsequent links will yield all the above.

Нас уже трое ) ok, кидайте мне в лк, кто сколько может на пиво и будет вам номерок и мак в придачу + в довесок белый ddns ovh

If you have a dynamic IP, you will need to setup a DDNS to access your NAS from outside your local network. So to start thing off you will need to open an account with a DDNS service provider. There are plenty out there, some paid, some free. The two below are the ones that I use personally. They are free. If you find others then you should also be able to use those. The configuration example I am giving below will be based on duckdns because it's the easiest I have seen out there. - http://www.duckdns.org - http://www.nsupdate.info Once you have chosen your domain with duckdns.org you will need to configure DSM accordingly. So here is how to: In Control Panel go to External Access (1), then click on Customize (2). A new window should open. You need to fill in as per the image. To save you some time you can copy paste from the code tag provided below the image: http://www.duckdns.org/update?domains=__HOSTNAME__&token=__PASSWORD__&ip=__MYIP__ When you are done click Save. The window should close. Now click on Add (3), see first image. A new window should open. Select *DuckDns from the service provider list and fill in your duckdns domain, username and token: Click on Test Connection to verify that it's working. If it is working you should see the word Normal in green next to Status. You can then click Ok. If it is not working then it means you screwed up somewhere. Recheck query URL, domain, username and token. All that is left to do is to configure port forwarding on your router. This is called at times "port forwarding" or "port mapping". You need to check with your router's user guide as sometimes the wording differs from one brand to the other. The port(s) you will be forwarding to your box also need to be opened on DSM's firewall else DSM will refuse access to the port/service requested. If your ISP implements double NAT you might have to do some additional configuration to your router to allow the ports to be forwarded correctly. Check with your ISP first and also check this site or this site on how to overcome double NAT. Google is your friend. Note of caution here: If you want to make things very safe you would only port forward VPN ports. This means that you can only access your box via VPN which in turn then gives you full access to the box (and to your local network if configured accordingly) once a VPN connection is established. You could also port forward the GUI ports (usually 5000/5001 or the ones you would have customised). This would give you full GUI access to DSM from outside of your network but this can be unsafe specially if you don't have a strong password and proper firewall and safety mechanisms configured in DSM. You could also just forward the port(s)/service(s) that you need. It really all depends what you are using your box for but in most cases the VPN solution is the safest although not the most convenient. NEVER EVER port forward port 22 unless you know exactly what you are doing. To test that your box is accessible from the outside world while being at home you could use your smart phone in data mode (not in wifi) at the following address: http://[yourdomain].duckdns.org:[port number] or https://[yourdomain].duckdns.org:[port number] - Do no put www

Hello, my first post and I really want to say thank you to all the community I've upgraded with success from 5.2-5967.1 update 3 to 6.1.2-15132 with loader 1.02b esxi 6.0 update 2 on Microserver gen8 with xeon E3 1220L v2 1 ssd for datastore on internal controller and passthrough of a LSi 9211-8i flashed in IT mode with 4 HDDs migration, no clean install and volume repair what I've done: 1) download the image file from first post here (I've used loader 1.02b ds3615) 2) edit settings of your current vm with xpenoboot 5.2 and write down MAC address 3) login to your DSM 5.2 web interface and write down serial number; shutdown the vm 4) download and install OSFmount, then mount the image file downloaded at point 1 (untick "read-only drive"); choose partiton 0 15MB 5) with notepad++ or similar edit grub.cfg with serial and MAC address from point 2 and 3, you can also change the default timeout; I haven't changed anything related to vid and pid 6) download and install StarWind V2V Image converter; convert the image file with modified grub.cfg (choose VWware ESX server image) 7) this will result in 2 files synoboot.wmdk and synoboot-flat.wmdk 8) upload them to the same datastore where you have xpenoboot.wmdk; you can use datastore browser to upload files 9) edit settings of the vm and delete the hard disk pointing to xpenoboot.vmdk virtual disk 10) add new hard disk scsi 0:0 independent non persistent pointing to synoboot.vmdk 11) I haven't added any serial port 12) start the vm and open immediately the console, because you have to select the third entry of the boot menu, the one related to esxi (I wasn't enough quick and needed a vm reset..) 13) open a web browser to find.synology.com 14) connect, install, migrate, manual install with the latest pat file you can download from links here https://xpenology.com/forum/topic/7294-links-to-dsm-and-critical-updates/ 15) in my case the ip was changed, so log in and update it, then update packeges in the package center... backup and replication is now called hyperbackup hope this helps someone bye

этот же конфиг из архива очень распространён и тоже использую уже давно только без микротика а всё средствами самой dsm с установкой винды вначале почему то не пошло а теперь уже и не помню по какой причине, скорее всего иза битых winpe файлов http://www.synology-wiki.de/index.php/PXE#Windows_7_.2F_8_.2F_8.1_.2F_10 LABEL winpe_7x86 MENU LABEL WinPE 7x86 LINUX memdisk APPEND iso raw INITRD images/winpe/WinPE_7x86.iso LABEL winpe_7x64 MENU LABEL WinPE 7x64 LINUX memdisk APPEND iso raw INITRD images/winpe/WinPE_7x64.iso можно посмотреть этот уже готовый пакет, где надо только кинуть файл iso оси и выделить открыть порты которые кстати не всегда свободны уже https://github.com/dreamcat4/docker-images/tree/master/pxe в докер он же https://hub.docker.com/r/dreamcat4/pxe

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

Today (2017-06-15) DSM 6.1.2-15132 has been released. I tried an update on a bare-metal Intel system (Loader 1.02a, DS3615XS) with NO luck! To get the system up and running again you have to boot from a live linux system, mount the system partitions and copy all files from /lib/modules/update to /lib/modules After that unmount the partitions, shut down the system and plug in your XPEnology boot stick/card. Polanskiman wrote an excellent tutorial on how to gain access to this partitions:

Jun's loader contains 4 files. I did the following steps: 1) modified ds3615.vmx ( virtualHW.version = "11" ) 2) uploaded all 4 files to a new directory on the ESXi server 3) added ds3615.vmx to the list of Virtual Machines. 4) in the VM settings: deleted the network adapter and added a new one 5) in the VM settings: created and added 8GB virtual drive 6) started the vm an connected to it in the browser 7) installed DSM 6.1.1 on DS3615xs 8) upgraded within DSM to 6.1.1-15101 Update 4 9) configured DS3615xs to my likes and shut it down 10) in the VM settings: created and added 4TB virtual drive 11) started VM 12) on DSM: added new Raid Group (basic, btrfs) 13) on DSM: added a new volume 14) installed Hyper Backup and Hyper Backup Vault from the Package Center 15) tested my backup concept after a few hours all data were restored ...

Hi, I have successfully migrated my HP N54L from version 6.0.2 to 6.1.3 15152 and created a step by step guide below which worked for me. First Please read the upgrade tutorial by Polanskiman and this thread! Use this guide at your own risk. I won’t be held responsible for any loss of data or failures that may result in the use of this step by step guide! 1. Backup your data and system configs! You have the full responsibility!!! 2. Disable C1E setting in bios!!! 3. Start with the workaround script to copy network drivers at boot to prevent the HP micro server from not getting a network connection and become un-accessible a. Create a shared folder called Scripts in volume1 b. Download the script update_patch.sh by Eduardo c. Enable SSH port 22 in Control Panel / Terminal & SNMP d. Use Putty to connect to your server log in with your admin account and password. Check that admin password is set. e. In Putty to become super user type Sudo –i f. Change permissions of your update file, type chmod 0744 /volume1/Scripts/update_patch.sh g. Log out, exit putty, disable SSH access h. Go to Control Panel / Tasks Scheduler and create a triggered task, select user root and select event boot up and then go to task settings and type in /volume1/Scripts/update_patch.sh and finally enable the task! 4. Go to Control Panel /Update & Restore and update to DSM 6.1.3-15152 5. When the server reboots turn it off and unplug your usb stick 6. Make a backup of your usb stick with image writer 7. Note VID, PID, mac address and serial of your grub config file of your usb stick 8. Write with Image writer the loader image file JunsMod102a-test-NICadd.img by Khile to your usb stick 9. Update the grub config file of your usb stick with VID, PID, serial number and mac address 10. Update the GRUB_VER file of your usb stick with DSM Version to 15152 11. Put back the updated USB stick to your server and start the server 12. Start Synology assistant to check when the server comes online, if it does not come online wait about 15 minutes for the update_patch script to run and to copy the network files to the right folder after that is done it will reboot. Mine rebooted twice however my server always needs to be turned off at boot as it does not reboot the usb stick for some reason. If your migration does not work out for some reason you can reinstall by pulling out all the hard disks from the server and select forced install, when the server appears in the Synology assistant insert the hard disks and install fresh.

I created a tutorial for the French section so I thought, what the heck, let's do it for the English one as well. Here it goes. 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.0 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.0.2. The file comes straight from Synology servers; - Jun's official v1.01 loader (mirror). This is a hybrid UEFI/BIOS loader so it should work in most machines. Loader supports Intel and AMD CPUs; - Extra.lzma ramdisk. This custom ramdisk is optional but I recommend it. I am just providing it for those who are having issues with network detection or unrecognised HDD controllers. This custom ramdisk contains additional modules (drivers) that were mostly taken from Quicknick's loader. I don't warranty they all work but I think most do. You will need to replace (or rename, so you can revert) the default extra.lzma ramdisk from Jun's loader with this one. See change log at the end of the tutorial for additional modules. - 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 MB manufacturer for exact nomenclature. - OSFMount to modify the grub.cfg file within the loader's image. This is not strictly necessary as Jun has made it possible to configure what needs to be modified via the Grub Boot Menu. I recommend you use OSFMount for now although it adds an extra step. If you prefer using Jun's new feature simply skip Point 5, read Note 4 instead and pick up at Point 6. 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 is based on DSM 6.0 Beta 2 branch 7274 and that a limited amount of drivers are included in the loader. If it is fundamental for you to have a NAS operating as quick as possible I recommend you look at the included drivers first at the bottom of this tutorial. If they are not there you will have to compile your own drivers. One last thing: DO NOT UPDATE DSM TO VERSIONS 6.0.3, 6.1, 6.1.1 or 6.1.2 with loader v1.01. 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.0.2. 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.0.2 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 - Unzip the loader you downloaded earlier. You will end up with a folder containing several files. Since we are installing on bare-metal you will only need the image file "synoboot.img". 5 - Now launch OSFMount. Select Mount New, then select the image file (i.e. synoboot.img) to open. Now select partition 0 (the one that is 30 MB). Click Ok. Then at the bottom of the window make sure to un-tick the "Read only drive". Click Ok. The EFI partition of the image file should now be mounted in file explorer. At this point you can navigate to the /image/DS3615xs directory and replace the extra.lzma ramdisk with the one provided above. When you are done come back to the root directory and go to the /grub directory and edit the grub.cfg file. Below is what you will see in the 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 model Change mac1=0011322CA785 to mac1=[your NIC MAC address]. 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. Optional: 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. 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. 6 - Now use Win32 Disk Imager to burn the image file onto the USB drive. This will also make the USB drive bootable. 7 - 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 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, else it wont work. 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. 8 - Once rebooted, if you have a monitor connected to your NAS you will see the following Grub Boot Menu: If you are on an Intel based machine you can simply let it be and the loader will automatically start. However, if you are on a AMD based machine you will need to select the 4th line and then press enter. 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. 9 - 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 the 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_8451.pat). 10 - When the migration is finished you will most probably have to update some of your packages. You can then proceed and update DSM 6.0 up to DSM 6.0.2-8451 update 11. It is possible you might either need to hard reboot or re-image your usb drive. DO NOT UPDATE DSM TO VERSIONS 6.0.3, 6.1, 6.1.1 or 6.1.2 with loader v1.01. Make sure to deactivate auto-updates within DSM. 11 - Enjoy. If you have questions or recommendations leave a comment. -------------- 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. In doubt, just ask. Note 2: Synology increased security in DSM 6. Root access through SSH is no longer available out of the box. You can however use your admin account and elevate permissions with the following command 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 means your VID and/or PID is wrong. If you are 200% sure that your VID/PID is correct and you still get that error message then try to 'Force Install'. Note 4: Changes made to the grub.cfg file can also be done directly during the Grub Boot Menu, so technically you can skip Point 5 and burn the image on the USB drive without editing anything (read Point 6 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 of how it looks under the Grub command line environment: Note 5: If your encounter the error "We've detected errors on your hard drives [drive number] and the SATA ports have also been disabled" during installation, try the Force Install menu entry in the Grub Boot Menu. If this does not work 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 Force Install, 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 Force Install 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 in Jun's Loader ############# Change log - Trantor » 23 Oct 2016 20:50 Original Post Updated broadcom tg3, bnx2, bnx2x, cnic Updated intel e1000e (I219 support) Add/Updated realtek r8168, r8169 and r8101 (r8169 from realtek website no the one inside the kernel tree) Hide Change log - Arcao » 25 Oct 2016 20:22 Original Post Added below kernel modules: r8101: RTL8100E/RTL8101E/RTL8102E-GR/RTL8103E(L) RTL8102E(L)/RTL8101E/RTL8103T RTL8401/RTL8401P/RTL8105E RTL8402/RTL8106E/RTL8106EUS r8168: RTL8111B/RTL8168B/RTL8111/RTL8168 RTL8111C/RTL8111CP/RTL8111D(L) RTL8168C/RTL8111DP/RTL8111E r8168: RTL8168E/RTL8111F/RTL8411 RTL8111G/RTL8111GUS/RTL8411B(N) RTL8118AS * Note: r8169 from Trantor archive doesn't work with my on-board Realtek RTL8111GR. So I kept the existing which is also much bigger. e1000e: 82573L/82572EI/82571EB/82573E/82573V/82567/82574L/82566MM/82566MC e1000e: 82566DM/82566DC/82563EB/82574IT/82583V/82579LM/82579V/82577LC/82577LM e1000e: 82578DC/82578DM/Gigabit CT Desktop Adapter/PRO/1000 PT/PF/I217-LM/V/I218-V/LM/I219 LM/V bnx2: Broadcom NetXtremeII BCM5706/BCM5708/5709/5716 bnx2x: Broadcom NetXtremeII 10Gb BCM57710/BCM57711/BCM57711E/BCM57712 tg3: Broadcom Tigon3 BCM5705/BCM5703/BCM5702/BCM5701/BCM5700/BCM5721/BCM5751/BCM5788/BCM5704/BCM5752/BCM5789 tg3 : BCM5723/BCM5761/BCM5787/BCM5755/BCM5722/BCM5754/BCM57781/BCM57785/BCM5718BCM57765/BCM57761 tg3: BCM5719/BCM5725/BCM5762/BCM5720/BCM57790/BCM57795/BCM57766/BCM57780 * Note: Existing modules updated with version from Trantor archive. I also added missing firmware files. ax88179_178a : ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet mpt2sas: LSI SAS 6Gb/s Host Adapters SAS2004, SAS2008, SAS2108, SAS2116, SAS2208, SAS2308 and SSS6200 * Note: It's already included in existing ramdisk but not loaded. By dmesg it's started correctly. evdev, button: for acpid Hide Change log - Arcao » 28 Oct 2016 10:47 Original Post * Fixed loading modules after installation step and upgrading from previous ramdisk version * Fixed order of loading kernel modules (cause not loading cnic) -------------------------------------------------------------------------------- Recompiled kernel modules: r8169: r8169-6.022.00 sources * Note: Compiled by Trantor igb: igb-5.3.5.4 sources ixgbe: ixgbe-4.4.6 sources * Note: Compiled from latest sources at intel.com megaraid_sas: megaraid_sas-06.812.07.00 sources mpt2sas: mpt2sas-20.00.04.00 sources * Note: Compiled from latest sources at lsi.com/avagotech.com -------------------------------------------------------------------------------- Added kernel modules: mpt3sas: mpt3sas-14.00.00.00 sources * Note: Compiled from latest sources at lsi.com/avagotech.com ftdi_sio, cp210x, ch341, pl2303 * Note: ftdi_sio is compiled by Synology, others are compiled from 7274 kernel sources Hide ############# Additional modules in the custom extra.lzma ramdisk ############# Change log 3c59x.ko 3w-9xxx.ko 3w-sas.ko 3w-xxxx.ko 8021q.ko 8139cp.ko 8139too.ko a100u2w.ko aacraid.ko acard-ahci.ko advansys.ko ahci_platform.ko aic7xxx.ko aic79xx.ko aic94xx.ko amd-rng.ko amd8111e.ko ata_generic.ko atl2.ko atp870u.ko b44.ko broadcom.ko caif.ko catc.ko ch.ko cn.ko crc-ccitt.ko crc-itu-t.ko cxgb.ko cxgb3.ko cxgb4.ko dl2k.ko dm-log.ko dm-mirror.ko dm-region-hash.ko dummy.ko forcedeth.ko gf128mul.ko isci.ko iscsi_boot_sysfs.ko isp116x-hcd.ko isp1362-hcd.ko isp1760.ko kaweth.ko macvlan.ko mlx4_core.ko mlx4_en.ko mpt2sas.ko mvsas.ko mvumi.ko nvme.ko pata_ali.ko pata_amd.ko pata_artop.ko pata_atiixp.ko pata_atp867x.ko pata_cmd64x.ko pata_hpt3x2n.ko pata_hpt3x3.ko pata_hpt37x.ko pata_hpt366.ko pata_it821x.ko pata_it8213.ko pata_jmicron.ko pata_marvell.ko pata_netcell.ko pata_ninja32.ko pata_oldpiix.ko pata_pdc202xx_old.ko pata_pdc2027x.ko pata_rdc.ko pata_sch.ko pata_serverworks.ko pata_sis.ko pata_via.ko pdc_adma.ko pegasus.ko pl2303.ko pm80xx.ko qla1280.ko r8152.ko rng-core.ko rtl8150.ko sata_highbank.ko sata_inic162x.ko sata_nv.ko sata_promise.ko sata_qstor.ko sata_sil.ko sata_sis.ko sata_svw.ko sata_sx4.ko sata_uli.ko sata_via.ko sata_vsc.ko sc92031.ko scsi_transport_srp.ko sis190.ko ssb.ko stex.ko sundance.ko sym53c8xx.ko udf.ko via-rng.ko via-velocity.ko zlib_deflate.ko zlib.ko Hide ############## Tutorial UPDATES ################## Change log [30/10/2016] Jun loader updated to version v1.0. This loader now supports AMD [03/11/2016] Jun's loader updated to version v1.01 [18/11/2016] Overhaul of the tutorial to reflect new features and fixes in the loader [19/11/2016] Minor edits and clarifications [20/11/2016] Minor edits + added link on how to burn & mount image in MAC OS. 3rd Paragraph [05/12/2016] Added note about SATA0. Modified/improved warning + detailed note 5 (Force Install) [09/12/2016] Title changed from "Tutorial: Migrate from DSM 5.2 to 6.0 - Baremetal" to "Tutorial: Install/Migrate DSM 5.2 to 6.0 (Jun's loader)" [19/01/2017] Point 10. Added following comment: "Update 9 seems to be causing some issues, so stay on update 8 until further notice" [20/01/2017] Minor edits [30/01/2017] Note 5 clarified [22/02/2017] Edit Warning message due to inaccuracy: DSM 6.0.2 Beta branch 7274 to DSM 6.0 Beta 2 branch 7274 [23/02/2017] Point 10. Added following comment: DO NOT UPDATE DSM TO VERSION 6.1. [27/02/2017] Trantor added a mirror to loader [02/03/2017] Link to Loader updated [08/03/2017] Added following comment to Warning message: DO NOT UPDATE DSM TO VERSION 6.1 with loader v1.01 + Minor edits [24/04/2017] Point 10. You can update to Update 11 [28/04/2017] Do not update to DSM 6.1.1 [09/05/2017] Do not update to DSM 6.0.3 [12/05/2017] Added link to serial generator & clarification about MAC address [19/05/2017] Added custom extra.lzma ramdisk link + how to replace ramdisk in loader + ramdisk change log + additional minor edits [28/05/2017] Updated custom ramdisk -- broadcom.ko module was not loading due to module not being mentioned in to rc.modules [18/06/2017] Updated tutorial links to new forum platform [21/06/2017] Do not update to DSM 6.1.2 + Title changed from "Tutorial: Install/Migrate DSM 5.2 to 6.0 (Jun's loader)" to "Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)" Hide

DS3617xs 1.02b and 6.1.3-15152.pat on Baremetall working fine too.

Might be an esx issue; read about it here, there is also an easy fix; read at least the last 3 pages : https://homeservershow.com/forums/topic/9602-esxi-notes/?page=10 this is the solution, from that topic (working for me with esxi 6.5): " downloaded the hpvsa-5.5.0-88.zip archive (as per HP advisory) and uploaded the vib to the datastore. eg /datastore1/patch/scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib via the ESXi web interface http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c05026755 8. remove the exsisting scsi-hpvsa_5.5.0.102-1O driver (via SSH) (enable maintenance mode first) # esxcli software vib remove -n HPE:scsi-hpvsa Removal Result Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. Reboot Required: true VIBs Installed: VIBs Removed: HPE_bootbank_scsi-hpvsa_5.5.0.102-1OEM.550.0.0.1331820 VIBs Skipped: 9. Install the scsi-hpvsa-5.5.0-88 downgraded driver # esxcli software vib install --viburl=/vmfs/volumes/datastore1/patch/scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib Installation Result Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. Reboot Required: true VIBs Installed: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0-88OEM.550.0.0.1331820 VIBs Removed: VIBs Skipped: 10. Disable ESXi vmc_ahci module (if not completed, ahci is used by default. eg array is not initialised via hpvsa and ahci initialises disks as 4 separate physical disks) # esxcli system module set --enabled=false --module=vmw_ahci 11. Reboot Server 12. Re-test file write speed to local data store (disable maintenance mode and enable TSM-SSH first) # cd /vmfs/volumes/datastore1 # time dd if=/dev/zero of=tempfile bs=8k count=1000000 1000000+0 records in 1000000+0 records out real 1m 40.79s user 0m 3.70s sys 0m 0.00s much better " for esxi 6.0 you don't need to disable vmc_ahci module (step 10) but it is required on 6.5

Your options are to either install on a clean formated hdd and if you need files off other hdd load it up in a Linux live cd and copy over. I will update to version 1.02b over weekend

Guys with memory problems add this to the grub.cfg disable_mtrr_trim Example: set common_args_3617='disable_mtrr_trim syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3617xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_port_thaw=1' Now I got: total used free Mem: 16034 260 15458 3 315 15560 Swap: 11665 0 11665 /proc/mtrr is editable even from a command shell: you can disable register records and/or write new values there this seems to be a Bios bug. Adding disable_mtrr_trim disables it without losing any performance as far as I know.

Два варианта. При условии, что загрузились не правив под себя grub.cfg: 1. из консоли: cat /proc/bus/usb/devices | grep -e "^$" -e "Vendor" -e "Manufacturer" -e "Product" Скрин: Hide 2. из GUI: Скрин: Hide После правки grub.cfg VID/PID уже не увидите (что будет свидетельствовать о верных значениях VID/PID). P.S. Так же не трудно заметить, что на MicroServer Gen8 всегда vid=0x0424 pid=0x4030 (на моих железках - именно такой)!

Предложу свой сценарий работы связки DHCP-PXE-TFTP: 1. Есть микротик (ip:192.168.88.1), он раздает intrnet, он же - DHCP: Параметры: Hide 2. Есть syno(ip:192.168.88.10), он TFTP-сервер. a. Создадим папку общего доступа PXE (назвать можно как угодно) и дадим TFTP-сервису: Параметры: Hide 3. Качаем архив 4. Распаковываем его в каталог на syno\pxe: Параметры: Hide 5. Правим под себя меню загрузки: pxe\pxelinux.cfg\default 6. Получаем, что хотели: Показать содержимое Hide

Будут равномерно генерироваться по разным партиям, об этом я подумал в самом начале. Так примитивно генерировать как это делали предыдущие генераторы я не собираюсь.

Indeed it is possible you need the below loader (added drivers for hp microservers) and select Force install this will show the device on network then do the update/fresh install and select the DSM 15047 once it reboots select the top option (dont have to select amd option) and you should find your hp server is now on version 6.1 and fully working Loader: Click Me Please disable C3 in bios as it causes issue with installation/running 6.1 Known issues: sometimes after install the login page will not recognise your username/password Solution: before update enable admin account with a password you can remember and login via that

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 !

Just fixed my issue by following a howto on other sites on how to generate the SN/MAC pairs. The other that have the same issue, please note that there is a specific algorithm that binds the SN you use with the MAC you need to set. I think I am not allowed anymore to put links to this kind of sites on this forum, but google is your friend.

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 192.168.0.2 -i 1 -t 20 -R Connecting to host 192.168.0.2, port 5201 Reverse mode, remote host 10.1.0.2 is sending [ 4] local 192.168.0.212 port 44805 connected to 10.1.0.2 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.

Einfach Migration im DSM Menü wählen, so hatte ich das damals gemacht, ging ohne Probleme. Tutorial: Install/Migrate DSM 5.2 to 6.0 (Jun's loader) dort ist es perfekt Beschrieben. 9 - 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 the 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_8451.pat).

Its all here - Step by Step in a 'perfect' tutorial by Polanskiman. https://xpenology.com/forum/topic/7507-tutorial-installmigrate-dsm-52-to-602-juns-loader/ My advice would be to 'test' your hardware first using a spare hdd and usb key to make sure your hdd controllers and nic work. I upgraded to 6.0.2 U11 with this method - I'm not using 6.1.1 as its the boot loader is beta

Там был косяк с CloudStation вот именно он съедает все место. Он хранит версии файлов. Даже если ты указываешь хранить 1 версию. Он все равно делает кучу вариантов. Следующий раз делай так заходишь через Putty и делаешь "du -ch /volume1" и смотришь что у тебя сожрало столько места [root@********]# du -ch /var/log/ 4.0K /var/log/sssd 25M /var/log/audit 28K /var/log/tomcat6 9.6M /var/log/cups 4.0K /var/log/samba/old 8.0K /var/log/samba 8.0K /var/log/ConsoleKit 21M /var/log/sa 64M /var/log/httpd 4.0K /var/log/ntpstats 36K /var/log/prelink 4.0K /var/log/smsd/smsd_stats 8.0K /var/log/smsd 769M /var/log/ 769M total

Le bon message qui fait avancer les choses ...

De rien et bonne soirée.

Yes of course. You need custom bios for N40L/N54L , to have this menu : Chipset >> Southbrigde configuration >> SB SATA Configuration Sata IDE Combined Mode ==> DISABLED Sata ESP on all port ==> Enabled Source : https://homeservershow.com/forums/topic/3397-modified-bios-for-microserver-n40l-enables-hidden-features/

can this bootloaer updated to 1.02b ? i'll try it this weekend : JunsMod102a-test-NICadd Thanks

reset the bios to defaults, then disable all unnecessary peripherals, set to boot from usb and disable all other boot options. try booting with no drives attached first to see if the nas appears on the network. also try your usb boot loader in another machine as a check that your image/grub settings are good

я знаю... сам актуально пока использую vps от ovh за те же 3,49€ но только 1 ядро, 2 GB RAM и всего 10 GB SSD предложение за 3,90€ только с договором и оплатой вперёт за год(потом уже 7,90€ но при таких кондициях всё равно вкусно) заказ не из германии проблематичен точнее такой опции вообще нет в отличии от hetzner, но всё решаемо могу заказать провайдер только что недавно обновил свою линейку серверов вот и зазывает клиентов https://www.1blu.de/server/vserver

open-vm-tools_bromolow-6.0_10.0.7-1.spk

Оффтоп: majordomo лучше на линуксе держать, свой перевел с винды на малину третью, гораздо стабильнее и меньше жрет.

disabled audio- and videotranscoding in the mediaserver settings (via the webinterface) fai;ing that then maybe a clean install is only way

Kizilkum Вместе с моделью не забываем указывать количество необходимых MAC адресов (Lan портов).

That's not going to be possible unless editing some system files which I honestly don't recommend. DSM checking if there is an update is not a bad thing. The bad thing is letting DSM install it automatically and that's a feature you can deactivate within the GUI.

примерный план действий: - экспорт баз данных из текущего рабочего сервера - удаление не нужного сервера бд (в твоём случае мария_5 или мария_10) - импорт баз в оставшийся сервер насчёт команд точно не скажу, но если исходить из полной совместимости в отношении мускула - команды сохранятся зачем тебе 2 сервера бд? оставь 10 если нужна новизна.

Kernel config give the choice of AMD support. (until 3.10.77, don't know for .102, but i think it's same). We can compil the kernel with what we want... But i believe, before the kernel was with bromolow and now it's with broadwell architecture. These screens are from bromolow source : Not sure, but i think jun doesn't support all and keep the default config. The kernel file will be bigger, if we include everything.... And the default config from Synology machine support less hardware than before, you are right on this.... Same for modules... I have some USB device which worked in 4.3 and no in 6.02.... I am trying to compil my own kernel, but it's not easy.... If you can have debug on serial with your AMD machine, you will see nothing... You can be sure, it's not just a problem with network driver, but with entire architecture... But no serial on the N40L or N54L... Maybe the solution can be add PCI card on it... Because on my VM , i cannot virtualize AMD machine... Maybe can do on ESXI... But it's not same, because last loader works on ESXI...

The problem with my N54L is that if I use any newer loader then 1.01 (e.g. 1.02b) then the box is not visible in network. Cannot see it using web not using Synology Assistant. And the problem of 1.01 is that is supports only DSM 6.0.2

+7 for AMD support I think there is still plenty of people having the older HP Gen7 with AMD as it is small and fast enough for NAS. Using ESXI is possible, but I need to sacrifice one disk for VM Datastore instead of using it for data.

I think you can, but I've read that the latest update to 6.1 will not load properly unless you have clean built the installation; I'm cautious about moving my 6.1 to the latest for this reason! You'll be better of using the new VM and attaching what ever storage you have (PCI-passthrough etc.) to it and then get DSM to repair the drives to fix their boot partitions. Once you've done that you can then remove the virtual HDD you used to install DSM on for the 6.1 install... There is a thread on updating 5.2 to 6...

Что ж... не совсем уверен конечно что мой способ генерации мака не подвергается бану (скоро узнаю)), но удалось. Скрины Hide И да... я могу купить exfat теперь

Попробуй эти 13A0LWN007948 00113226B345 00113226B346 00113226B347 00113226B348 Hide

Push notifications should also be considered as abusing Synology's services similar to QuickConnect. As stated in the description, the service is using Synology's email servers. Just configure email notifications and use a Gmail account as provider.

From my experience testing, selecting the ESXI/VMware option causes the VM to not see any of the disks. Leaving it on the default works fine in VMware.

I would advice against using DSM 6.1 just yet as it has a few critical issues according to other posts here. Even DSM 6.0 isn't as stable as DSM 5.2 in my opinion. I would also not recommend to just use any image/export you find online, but stick to Jun's. Regarding the logs: Make sure SSH is enabled. Use Putty to login as admin and use "sudo su" in order to elevate to root. Now you can write "tail /var/log/messages" in order to see the last messages. You can also read them in VI by using "vi /var/log/messages" and quit by using ":q!".

Hola a todos hago este tutorial cogido de la seccion de ingles que a su vez se ha copiado de la seccion frances para que la gente de habla hispana disponga tambien de un tutorial rapido, sencillo y en su idioma. Esto es lo que necesitas para la migración: -https://sourceforge.net/projects/win32diskimager/ para crear un usb booteable con la imagen -Pendrive 1gb minimo, recomendable 4gb. Yo he usado uno de 1gb para la instalacion del boot y es suficiente. -Un programa para leer la informacion del usb como puede ser http://www.usbdev.ru/files/usbflashinfo/. -Un buen editor de texto: Notepad++. No recomiendo el uso del editor de Windows. -DSM 6.0.2 directamente de los servidores de Synology. -Bootloader oficial Jun's version 1.1https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA. Funciona en la mayoria de equipos haciendo migración/instalación. Ahora con soporte para AMD. Pasos para la instalación: 1 - Copia tus datos y guarda tu configuracion antes de cualquier intento de actualización desde DSM 5.2 a 6.0. 2 - Apaga tu NAS y desconecta el pendrive que actualmente tiene instalado DSM 5.2. Recomiendo copiar este pendrive o usar otro en caso de que la migracion falle y tengas que regresar a DSM 5.2. 3 - Ahora ve a un PC, conecta el pendrive y utiliza el programa que dejé anteriormente para extraer la informacion VID y PID del pendrive, de lo contrario la instalación fallará. Escribela en algun lado de momento y guardala. 4 - Descomprime el bootloader de Jun, abre Win32DiskImager, selecciona synoboot.img y escribelo(write) en el pendrive, esto ya hará el pendrive booteable y escribirá los archivos necesarios en el pendrive. 5 - Ahora ve al pendrive y abre el archivo grub.cfg que se encuentra dentro de la carpeta grub del pendrive. Esto es lo que veras en el archivo: Code: Select all serial --port=0x3F8 --speed=115200 terminal_input serial console terminal_output serial console set default='0' set timeout='1' set fallback='0' menuentry 'Synology DS3615xs' --class os { insmod fat linux /image/DS3615xs/zImage root=/dev/md0 syno_hdd_powerup_seq=0 netif_num=1 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 vid=0x090C pid=0x1000 console=uart,io,0x3f8,115200n8 sn=C7LWN09761 mac1=0011322CA785 withefi elevator=your_magic_elevator quiet initrd /image/DS3615xs/ramdisk.lzma } Tienes que modificar lo siguiente, de lo contrario no funcionará: Cambia vid=0x090C to vid=0x[tu usb drive vid] Cambia pid=0x1000 to pid=0x[tu usb drive pid] Cambia console=uart,io,0x3f8,115200n8 to console=ttyS0,115200n8 (ESTO CREO QUE YA NO ES NECESARIO YO NO TUVE QUE HACERLO) Cambia sn=C7LWN09761 to sn=[tu sn] Cambia mac1=0011322CA785 to mac1=[tu mac address] Tambien puedes añadir mac2=[tu mac2 address]Si tienes una 2º interfaz de red. Para que funcione quickconnect es recomendable que metais un SN y MAC validos, hay un excel que te genera SN y MAC válidos, yo lo tengo y funciona todo perfectamente. Tambien recomiendo añadir el siguiente parámetro ya que a algunos le has dado fallo y con esto se soluciona: SataPortMap=[numero de HDDs en tu sistema]. Puedes añadirlo despues de HddHotplug=0 por ejemplo. No te olvides de actualizar el parámetro si añades más discos. Una vez hecho todo, guardamos el archivo. Ya estamos preparados para actualizar. 6 - Desconecta el pendrive. Enchufalo en tu NAS. Inicia desde el pendrive y asegurate de que es el primer dispositivo en iniciar. Puedes iniciar en modo UEFI o modo BIOS. Asegurate tambien de que tus disco esten en modo AHCI y no IDE. Reiniciar. 7 - Si tienes un monitor conectado en tu NAS veras algo como esto: Code: Select all early consol in decompress_kernel Decompressing Linux.. Parsing ELF… done. Booting the kernel. Ahora ve a find.synology.com y busca tu NAS. Deberias verlo como anteriormente lo hacias. Sigue las instrucciones normalmente, haz la migración si vienes desde DSM 5 y quieres mantener tus datos, despues instala manualmente DSM 6. NOTA: Se puede realizar una instalación limpia igualmente si no tienes DSM 5. 8 - Cuando la migracion esté terminada tendrás que actualizar algunos de tus paquetes. Despues puedes proceder a actualizar DSM 6 a los diferentes updates que existan directamente desde DSM. 9 - Disfrutar. -------------------------------------------------------------------------------------- Nota 1: Si despues de seguir el tutorial no puedes encontrar tu NAS a través de find.synology.com o el asistente de Synology, es muy probable que los drivers de tu tarjeta de red no esten integrados en el bootloader, pregunta en el foro de ingles para mas informacion. Nota 2: Synology incrementó la seguridad de DSM 6.0. El acceso root sobre SSH ya no está disponible de fábrica. Sin embargo puedes usar tu cuenta de administrador para elevar los permisos con el siguiente comando Code: Select all sudo -i Nota 3: Por favor revisa que tengas los VID/PID correctos antes de proceder. Si obtienes el siguiente error ''Failed to install the file. The file is probably corrupted. (13)'' significa que tu VID/PID es incorrecto. ---------------------------------------------------------------------------------------