Leaderboard


Popular Content

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

  1. 23 points
    SS 8.1.2-5469.х86_х64 протестирован и работоспособен. Желающие могут постучать(только не громко) в личку. На заметку - Качаем архив и распаковываем. - Устанавливаем SS 8.1.2-5469!!!(взять можно Тут, но не запускаем(если запустили, останавливаем). - Заходим на свой NAS через web. - Заходим в Панель управления > терминал и SNMP. Ставим галку "включить службу ssh" и нажимаем применить. - Подключаемся к сино с помощью putty или другого ssh клиента под Админом - Вводим свой Админский пароль - Вводим команду: sudo su - - Вводим свой Админский пароль - Видим чудо в виде - root@... - Вводим команду: synouser --setpw root Ваш_Пароль_Для_Root - Далее можно заходить под root используя установленный пароль. - Скидываем файлики из архива на сино и при необходимости меняем владельца и права. Сделать это можно разными способами. p.s.При использовании WinSCP советую в настройках передачи установить тип файлов "двоичный/binary" для исключения возможных проблем. - Запускаем SS из центра пакетов.(если всё сделано правильно, имеем 25 камер) - Класть(или если хотите - ложить) сюда>>> /var/packages/SurveillanceStation/~target/lib/libssshm.so *chmod=644* *owner=SS* *group=SS* /var/packages/SurveillanceStation/~target/lib/libssutils.so *chmod=644* *owner=SS* *group=SS* /var/packages/SurveillanceStation/~target/sbin/ssmessaged *chmod=755* *owner=SS* *group=SS* /var/packages/SurveillanceStation/~target/webapi/Layout/src/SYNO.SurveillanceStation.Layout.so *chmod=644* *owner=SS* *group=SS* Hide
  2. 14 points
    Господа, товарищи.. Не пишите мне свою почту. Знать мне её не обязательно, а ответ всё равно прилетит в личку на ресурсе.
  3. 11 points
    У меня в личке тоже нет ничего, кроме сообщений от желающих получить файлы. И многие пришли на форум именно за ними. От некоторых получивших я даже спасибо не услышал. И как по вашему я должен реагировать на сообщения от людей, которые регистрируются тут только ради своей "экономии"? Отвечу вам - никак.
  4. 6 points
    Заканчивайте срач. Уже противно даже это читать.
  5. 4 points
    Все кто "обделен" файлами, просьба повторно написать в ЛС. Вас очень много, и все шлют не по одному сообщению. Понять кто получил а кто нет из за этой каши проблематично. Вас уже около сотни. Из этой толпы почти половина даже спасибо не сказали. Получили желаемое и досвидос. В общак выложить могу, но только с разрешения Администрации.
  6. 4 points
    Добро пожаловать в личку...
  7. 3 points
    за монеты в магазин имхо....странно кряк всего сино поощаряется а пакет ss нет??двойной стандарт))) и таки мы на форуме чтоб помочь друг другу или барыжить? думается мне монеты приемлемы как добровольное пожертвование....как и везде в линукс(только почемуто адекватного кошелька так никто и не завел) а вот хамить когда чегото просишь или забыть поблагодарить....так уже 2 поколения дегенератов (в большинстве)вырастили...но и тут сами виноваты "откуда в молодых культура если старший быдло?"
  8. 3 points
    x64-x86 тестируется. Если всё будет гуд, вероятно появится тут.
  9. 2 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.4 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.4 but only to DSM 6.0.2 then use the link above. To upgrade from DSM 6.0.2 to DSM 6.1.4 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 burn 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.4 PAT file. Chose the one you need: DS3615sx or DS3617sx or DS916+. Download the ".pat" file not the ".pat.md5" - 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 using HP machines that it actually works. The C1E function in the bios (in some HP machines) needs to be deactivated. I am unsure for other motherboards brands therefore if you have an AMD machine that is not an HP you might be out of luck. Try looking in the bios configuration and play around. - Custom extra.lzma ramdisk. 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 and updated 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. If you a have question specific to the custom ramdisk please post it in the topic of IG-88, not here. - 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 or use the custom ramdisk provided above. Don't ask me to compile modules for you. I wont do it. 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 or DS916+ 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_15217.pat or DSM_DS3617xs_15217.pat or DSM_DS916+_15217.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.4 up to DSM 6.1.4-15217 update 2. 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 or not answered. -------------- 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 ############## 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 [14/12/2017] Updated tutorial to 6.1.4. Removed Logs for Custom ramdisk; Instead a link to IG-88 custom ramdisk topic is provided. [07/01/2018] Improved note about AMD compatibility. Hide
  10. 2 points
    Win32 Disk Imager ни разу не подвела.
  11. 2 points
    Here's Synology's actual information about Meltdown/Spectre: https://www.synology.com/en-us/support/security/Synology_SA_18_01
  12. 2 points
    они не сильно ломают ) снимаем образ допихиваем туда дрова нужных версий будет свежая .... на 5 компах ни один вариант не встал полностью и даже на асус мамке с интел сетевкой два часа установки и сеть не поднялась... комп должен быть не моложе 5 лет видимо
  13. 2 points
    кстати 453a запустился на мамочке Intel BOXDG41AN LGA 775 на 2 sata порту полет был нормальный сетку подцепил на 8111
  14. 2 points
    Вот основа. Купить можно всё, но это не интересно и надоедает через пару дней. Главная проблема - занять моск! Эппл такой сервис не предлагает бгг )))) И вообще если проследить чего лишили купертиновские подхвостники ос х осиротев после ухода Жобса, с концептуальной идеей "Пользователю это не нужно", короче одн слово приходит на ум "ПРИДЖОБСЕТАКОГОНЕБЫЛО" ))) и ещё: Эта тема держится в топе ветки, только за счет флуда и флейма. )
  15. 2 points
    ok, напишу последний может быть оффтоп в эту в эту кстати сказать изначально флудильную тему про номерочки на xpenology буду сидеть конечно до последнего, пока "не постучатся в дверь" ну и по поводу всего холявно-атруиского баловства тоже согласен и особенно сильно укрепилось мнение со вчерашнего вечера когда я распаковал сие чудо Apple TV 4K, плексы, торренты, аппаратное перекодирование и прочее сразу улетели в топку не раздумывая на девайс поставил всего одно приложение Kinopuber(контент с kino.pub и ottclub.cc(live-tv)) и всё, моим ручкам и голове стало очень скучно и нечем занятся
  16. 2 points
    Как и всего холявно-атруиского, ну вот kodi исключение, хотя и там г... хватает
  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. 1 point
    DSM never touches the secondary partition where your data is. Fresh install or migration is virtually the same thing from a data standpoint. From a system standpoint it is different as one basically cleans up the system partition and then reinstalls DSM and the other simply updates all necessary files while keeping your settings and packages.
  19. 1 point
    To be accessible from outside your local network, PhotoStation needs port 80 (http) or port 443 (https) to be forwarded in your router. Personally I only open the secured port. PhotoStation does not use the same secured port as the GUI's access. Pay close attention to what is mentioned in DSM network settings: If you are ever in doubt what port is needed you can look at DSM's list of service ports: https://www.synology.com/en-global/knowledgebase/DSM/tutorial/General/What_network_ports_are_used_by_Synology_services You can also look in DSM's firewall to check what ports are being used for each service. Also don't forget to configure PhotoStation accordingly: There is another option where you could bypass all the above and that would consist of configuring your DSM as a VPN server and then accessing PhotoStation by VPN from DSPhoto. This is even more secure but it implies opening up a VPN connection each time you wish to access your photos through DSPhoto.
  20. 1 point
    V1.02b ds3615xs https://ru.aliexpress.com/item/PCI-e-to-2-port-M-2-B-key-SSD-Card-PCI-Express-to-NGFF-B/32745249555.html?spm=a2g0s.9042311.0.0.WwcYxz
  21. 1 point
    Система охлаждения работает исходя из данных системы... Тише он не станет. Но если будут винты перегреваться то охлаждения это исправит. Без AMS этого не будет.
  22. 1 point
    Yes exactly is what you are thinking!! But there are some traps Yes we can run xpenology on docker fully functional but inside a KVM VM but works pretty fine really. Right now what I have is a simple docker that execute an instance of xpenology (clean, so the page of installation is shown to install) I thinking which features do you think could be interesting for you? give support to docker volumes inside the xpenology? -v /myhost/data:/Volume1/myshare ? Please let me know what do you think could be interesting for you. when I have a more stable version I will publish to github for all of you. The image is based in an image a Did for my work (W2012 inside docker) but I reused to use for xpenology I Did the image because I wanted pretty UI of xpenology + Unraid Disk management(almost always spin down the HDD) You can share your unraid data using NFS/glusterFS and (if someone add 9p virtio driver to the synoboot image) 9p
  23. 1 point
    the dsm pat file can also be loaded from the internet in the process of installing if the installation is done you can open the webinterface of dsm with http://<ipadress>:5000 imho it's easier to use the assistent programm, it finds the booted up or runing system and shows the status
  24. 1 point
    тут ранее в теме были проблемы с сетью, из за обновления - в нем отрубались драйвера сетевух и надо было через виртуальный сом порт ilo копировать пару файлов обратно, даже скрипт давали. Потом у разных ревизий серверов могут быть разные сетевухи - у кого то интел, у меня по моему бродком.
  25. 1 point
    J'ai utilisé l'utilitaire VMware OVF Tool. Il suffit d'exporter 2 fichiers d'une VM qui fonctionne à savoir le fichier .vmx et le fichier .vmdk contenant le loader (pas ceux des données). Tu exécutes l'utilitaire avec en paramètre le fichier vmx et l'endroit où produire la l'ovf. Ensuite j'ai édité le fichier ovf pour le rendre générique en renommant le nom du disque par synoboot histoire de ne pas le confondre avec les futurs disques à rajouter. Ici je fais référence à la création du vmdk via l'outil StarWind V2V Converter à partir du fichier img. Dans le tuto on explique comment changer l'adresse mac dans le grub.conf il me semble donc dès lors que ce fichier est modifié avec ovfmount, il faut le retransformer en vmdk avec StarWind V2V Converter. simple non !.... j'avoue c'est pas hyper pratique, j'aurai préféré qu'il s'appuie nativement sur l'@mac fournie par VMware mais bon.
  26. 1 point
    Попробуйте RosaImageWriter. Запускать из под root.
  27. 1 point
    Yes I mean starting afresh by creating a new USB drive with Win32DiskImager & a fresh copy of jun's 1.02b loader & don't forget to set the correct vid & pid for the new drive.
  28. 1 point
    na bitte Brigitte, das mit der Prozessoranzeige ist so ein Ding, was mich noch nie wirklich interessiert hat ... es ist ein NAS ... ausreichend. Denke mal, in irgend einer Systemdatei kann man auch das verstellen ... mit der Laufwerksanzeige geht´s ja auch und die ist wichtiger. Die verbaute RAM-Menge wird ja angezeigt.
  29. 1 point
    ни то, ни другое. ты ошибаешься. крэнк работает, Вирус молодец, неблагодарным собакам - болт. Полански негативно относится к крэнкам на данном ресурсе, да и бурги не тупые, гугль транслэйтом пользоваться ради халявы не побрезгуют. а дальше затирания тем, баны, обиды и т.д.
  30. 1 point
    Коллеги, докопался до истины! Образ загрузчика не должен находиться в папке с названием кириллицей. OSFMount не видит разделы и не сможет его правильно смонтировать! Проверено!
  31. 1 point
    Причину почему не монтируется с помощью OSFMount так и не нашел, но проблему решил следующим образом (может кому-то пригодится). Записал скаченный образ на флешку. При загрузке DSM с флешки нажал "С". Нажимать нужно сразу после загрузки BIOS и прописал все новые значения вручную. grub> vid 0x1234 grub> pid 0x5678 grub> sn хххххLWNхххххх grub> mac1 0011хххххххх После каждой команды необходимо нажать «Enter». Если при вводе цифр была допущена ошибка, просто повторно введите команду с верным значением. После окончания нажмите «Esc».
  32. 1 point
    У меня sony bdv-3100, на профиле по умолчанию не воспроизводит mkv, хотя кинотеатр поддерживает данный формат. Сменил профиль на - общий dlna, стало все нормально.
  33. 1 point
    ща скину образ снятый акронисом Ораз Qnap453-A https://yadi.sk/d/o8WFx5ZQ3RCSUM снят с официалки
  34. 1 point
    Попробуй зайди в приложение Сервер мультимедиа, в нем есть вкладка Совместимость DMA. Далее ищешь список устройств, в данном списке найди свой телевизор, в этойже строке правее можно попробовать подобрать более подходящий вариант чем Профиль по умолчанию.
  35. 1 point
    а разве ты со своего настоящика не можешь снять образ загрузчика? как тут предлагали выше?
  36. 1 point
    не прокатывает вообще не запуститься
  37. 1 point
    виртуалка тоже ставиться и работает Обновления все работают ну ядро и микропрограмму не советую обновлять все рухнет А приложения без проблем все обновляеться
  38. 1 point
    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 3 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal on HP N54L - Additional comments: Requires reboot - No problems so far
  39. 1 point
    Пароль: 3m2y Извлечь пароль: 756e98065cb8cbf603a3dbef2afe9261
  40. 1 point
    вот ветка кунаповская основное обсужение http://www.gebi1.com/forum-37-1.html вот ветка с прошивками http://www.gebi1.com/forum.php?mod=forumdisplay&fid=37&filter=typeid&typeid=520 согласно описанию у китайцев все пашет они так его и называют черный q но зарегится не вышло кто скачать сможет хоть поделитесь чтоли
  41. 1 point
    У кого есть продолжение статьи в журнале ХАКЕР про XPNOLOGY? https://xakep.ru/2017/01/09/home-nas-server/
  42. 1 point
    Сам сказал, сам искал, сам ответил: статья https://justpaste.it/1a165
  43. 1 point
    у меня тоже установлен плагин IPTV.bundle только источник сеть acestream, сам движок acestream установлен в контейнере докера и там же пара скриптов которые парсят автоматом различные плейлисты и кидается всё в вебсервер dsm для доступа как локально так и удалённо as.m3u #EXTM3U #EXTINF:-1, Animal Family HD (educational) http://.online:6878/ace/manifest.m3u8?id=a7db104fe838a8041ab9145d5a1f5da160dadf78 #EXTINF:-1, Animal Planet HD (educational) http://.online:6878/ace/manifest.m3u8?id=23d6e6c1b3b812d70ab5ddebfbea8155e5c1d37b #EXTINF:-1, Cbs Reality (educational) http://.online:6878/ace/manifest.m3u8?id=acbfd8574084ffc68c65b0948485e5d0f82173e2 #EXTINF:-1, Da Vinci Learning (educational) http://.online:6878/ace/manifest.m3u8?id=e61b3ac960809be12896e1ae7098b076cc2aab60 #EXTINF:-1, Discovery Channel HD (educational) http://.online:6878/ace/manifest.m3u8?id=d021d13d21e4cb362f7391b32aca933710658474 #EXTINF:-1, Discovery HD (educational) http://.online:6878/ace/manifest.m3u8?id=912d93af230ff308b1c8d35a61952378b7af5f63 #EXTINF:-1, Discovery HD Showcase (educational) http://.online:6878/ace/manifest.m3u8?id=d01bcf8744de6d47cb280a3ef42e47e813d6ec23 #EXTINF:-1, Discovery Science HD (educational) http://.online:6878/ace/manifest.m3u8?id=f8eb7c3de35f75ea4ab8d36d5caba79b3985a7c7 #EXTINF:-1, Discovery Showcase HD (educational) http://.online:6878/ace/manifest.m3u8?id=6af76dc0c965069a1a6677ed27f87d707c3425fd Hide
  44. 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
  45. 1 point
    hy dire, according to you need at least a gen 4 core processor or a braswell device for example n3710 or newer like j3455 which i use with ds916+ image. stay with ds3615xs.
  46. 1 point
    Заметил глобальный трабл со спойлерами. Вообще bb коды хромать стали.
  47. 1 point
    Прошу прощения. Я допустил ошибку при написании поста (уже исправлено). /var/packages/SurveillanceStation/target/sbin/sscored *chmod=755* *owner=SS* *group=SS* Проверил специально на новой системе. Всё отлично работает.
  48. 1 point
    Подтверждаю, пока работает исправно. По аналогии запилил 8.0.3-5159, пока работает, будем посмотреть. P.S. Если всё будет жить, естественно нужно скинуться на минералочку с шашлычком.
  49. 1 point
    When you buy a Synology device, you're buying hardware, software and warranty support. The hardware appears overpriced because you can get the software and 'support' from here for free. Essentially, you're assigning 0 values to software and support in the cost = hardware + software + support equation.
  50. 1 point
    Очень хочется видеть развернутый FAQ для новичков.