Popular Content

Showing content with the highest reputation since 01/20/2019 in all areas

  1. 6 points
    In addition to bricked boxes due to inattentive upgrades, there seems to be a surge of questions regarding how to select a DSM platform, version and loader. This table should help navigate the options and current state of the loaders. While situations rapidly change, it should be correct as of the listed date. 6.x Loaders and Platforms as of 12/Jan/2019 Loader DSM Platform DSM Version Kernel DSM /dev/dri DSM NVMe cache Boot method CPU Needed Notes 1.04b DS918 6.2 to 6.2.1 4.4.x Supported Supported EFI or Legacy BIOS Haswell or later recommended 1.03b DS3615 6.2 to 6.2.1 3.10.x Not Supported Not Supported Legacy BIOS only Nehalem or later 6.2.1 requires Intel NIC 1.03b DS3617 6.2 only 3.10.x Not Supported Not Supported Legacy BIOS only Nehalem or later 6.2.1 crashes on USB kernel drivers 1.02b DS916 6.0.3 to 6.1.7 3.10.x Supported Not Supported EFI or Legacy BIOS (Jun) MBR (Genesys) Nehalem or later 1.02b DS3615 6.0.3 to 6.1.7 3.10.x Not Supported Not Supported EFI or Legacy BIOS (Jun) MBR (Genesys) Nehalem or later recommended 1.02b DS3617 6.0.3 to 6.1.6 3.10.x Not Supported Not Supported EFI or Legacy BIOS (Jun) MBR (Genesys) Nehalem or later 6.1.7 crashes under ESXi for unknown reason 1.01 DS916 or DS3615 or DS3617 6.0 to 6.0.2 3.10.x Not Supported Not Supported EFI or Legacy BIOS (Jun) MBR (Genesys) Nehalem or later obsolete
  2. 3 points
    Which DSM version shall I use? This is an oft-repeated question, complicated by the fact that different loaders support different DSM versions AND hardware platforms. In simple terms, DS3615/DS3617 has the widest support for hardware and packages, and DS916/DS918 has support for newer, low-cost CPU's, transcoding and NVMe cache (DS918 only). But the real questions are, what hardware do you have? What hardware do you want to buy in order to support what you want to do? And how does a DSM loader and platform support this? In order to answer, it's useful to understand what hardware is natively supported by DSM. Each DSM version is different as Synology does not need to support many types of hardware, as they build up a specific DSM for each hardware platform they sell. Fortunately, the base Linux kernel has much broader support for hardware than they intend. Most of us guessed at the hardware requirements and made (hopefully) intelligent selections on DSM versus hardware. Some build systems and then are distressed when the hardware isn't fully supported by the DSM platform they choose (sometimes this can be fixed by extra.lzma, and sometimes not). Unfortunately, Synology hardware knowledge is often imperfect, as the main boards are custom designed. Refer to the example below for DS3615 (I hope it will be completed more precisely in the future). DS3615xs Reference Hardware: CPU: Intel Core i3-4130 (Haswell) Chipset: Intel C20x? 4x1Gbe Ethernet: ??? Secondary SATA: ??? 10Gbe OEM: E10G18 (Aquantia AQC107) E10G17 (Mellanox Connect X-2/3/4) E10G15 (Tehuti) With even this information, we can make some good guesses on what hardware might be supported. We certainly can act on the 10Gbe cards since those are well known. Wouldn't it be great if we knew ALL the different drivers that are natively supported? Unfortunately this is a fairly difficult process if you are not a Linux guru (and a bit laborious even if you are). There are "user-reported" hardware compatibility threads out there, but many don't understand that those reports are both DSM version and platform specific. Furthermore, with the way hardware manufacturers reissue hardware with the same name but new PCI device number (such as the Intel PHYs on desktop motherboards), often not enough information is reported to confirm whether a specific piece of hardware is suitable for use. If you aren't sure if your hardware is supported, this post and the complementary DS918 driver guide aim to help you. Download the appropriate Excel spreadsheet to see key driver support in the DS3615 6.1.7 or 6.2.1 Synology custom kernel, and via loadable modules supplied with DSM. Hopefully it will help you select the best DSM platform for your purposes, and possibly inform your hardware purchases. DSM 6.1.7 DS3615 V1.04 2019-Feb-04.xls DSM 6.2.1 DS3615 V1.0 2019-Feb-04.xls
  3. 3 points
    extra.lzma for 1.04b 918. Seems that hdd's hibernation will work and speeds in vmm have become prohibitive. Try and report. P.S. To replace extra.lzma on working DSM you need to mount synoboot2 as described here, replace extra.lzma and reboot xpenology. Thanks so much @TeleDDim for his idea to modify extra.lzma.
  4. 3 points
    This is just one person's opinion and I do not speak for anyone else: I'm not an admin here, I did not write the loaders. I'm just a tech-savvy user, that likes DSM and how it performs on my own hardware - far better than on Synology hardware. Over time, I have figured out a lot of things about XPEnology, and am willing to spend some personal time to help others, just like countless other contributors here. You are on a forum where the stated purpose is to enable people to use a hack. It's not a product support page. This collective effort has spanned 10 years of DSM releases, and people are still using some of the old software versions. So ALL the information here is still relevant to someone, and nobody's being paid to curate the part you think you need, just for you. If you want to use XPEnology, you need to put in the time (and have the tech skills) to understand the ecosystem and the tools involved. Many people, myself included, have done research and written up documentation or coded tools to try and help with this. But it won't be delivered on a platter like FreeNAS, which is bankrolled by the commercial side of the product. As you perceive a need for things to be organized differently, may I suggest that you become an expert here and start contributing instead of lecturing to people you don't know, and who don't owe you anything on how a loosely structured forum and its content should be presented. Again, I personally am happy to help when I have something useful to contribute, but I'm having a hard time getting over the attitude and general lack of patience that I perceive from you. This has caused me to delete several draft posts (intended to be of assistance to you) out of exasperation. In a prior post, I suggested that "maybe XPEnology wasn't for you" and while it's not for me to defend that, I do believe that your approach may prove to be very frustrating, should you persist.
  5. 2 points
    Hello! I am xpenology user. And I am an IT engineer who creates shell scripts as hobbies. Please understand that it is written by a google translate site. because i’m korean who is not fluent in English. I created a tool to change cpu information for Xpenology’s users. Modify the actual cpu name and cores of your pc or server. Howto Run ============================================================= 1. Download attached file on your PC (ch_cpuinfo_en.tar) / (ch_cpuinfo_kr.tar is file for korean) 2. Upload file to your DSM location (by filestation, sftp, webdav etc....) 3. Connect to ssh by admin account. (dsm > control panel > terminal & snmp > terminal > enable ssh check) 4. Switch user to root: sudo su - (input admin password) 5. Change directory to where ch_cpuinfo_en.tar file is located: cd /volume1/temp 6. Decompress file & check file: tar xvf ch_cpuinfo_en.tar ls -lrt (check root’s run auth) 7. Run to Binary file ./ch_cpuinfo or ./ch_cpuinfo.sh (If you use busybox in DSM 5.x, you can use it as a source file) 8. When you execute it, proceed according to the description that is output. 9. Check your DSM’s CPU name, CPU cores at “information center” ==================================================== Addtional, Adjust binary to excute file made by shc(http://www.datsi.fi.upm.es/~frosal) The tool does not inclue worms, bad code. If you want to edit the CPU information yourself manually, please refer to the contents below. ——————————————————————————————————————————————————————————————— Location : /usr/syno/synoman/webman/modules/AdminCenter Source : admin_center.js / admin_center.js.gz(above 6.2) Add Before -> if(Ext.isDefined(f.cpu_vendor)&&Ext.isDefined(f.cpu_family)&&Ext.isDefined(f.cpu_series)){ o.push([_T("status","cpu_model_name"),String.format("{0} {1} {2}",f.cpu_vendor,f.cpu_family,f.cpu_series)])} if(Ext.isDefined(f.cpu_cores)){o.push([_T("status","cpu_cores"),f.cpu_cores])} Add contents: f.cpu_vendor="Intel";f.cpu_family="Xeon";f.cpu_series="E3-1230 V2";f.cpu_cores="1"; ——————————————————————————————————————————————————————————————— Finally, All descriptions are based on version 6.2, and the actual executable file supports both 5.x and 6.x. Please contact me by comment or bug report, i’ll respond to you as much as possible within my ability. Test & Made Environment ———————————————————————————————————— Base Server : HP Microserver gen8 + VMware ESXi 6.0 + RDM DSM : 6.2-23739 Update 2 (DS3615xs/DS3617xs) 6.1-15284 Update 2 (DS3615xs) ———————————————————————————————————— Thank you!! Have a nice day!! ============================================= Update new version 2018.08.26 I made the tool by adding and improving the function. Please refer to above for how to use it. I delete the old version attached files, new version uploaded and attached. If you use last version tool, you can use without restore. Additional,  It does not yet apply to "mobile web" and "DS finders". it's working.... and... Polanskiman give editable permission to me. so, i can do first article.. thanks Polanskiman !!! ============================================================================ Update new version (ch_cpuinfo ver 4.0) 2018.09.13 1. Mobile support (just 6.x / not yet 5.x) You can see it when you go into mobile browser or "DS mobile" menu in "DS Finder" 2. Improved CPU information collection command Some dmidecode commands have been found to be missing information and have been improved.(Thanks stefauresi !!! ) 3. Edited some variable names I adjusted some inconsistently coded variables Addtional, Usage is the same as before. and Existing users can apply by "2) Rerun". Unfortunately, DS Finder's own app does not reflect system information. It seems to refer to other information and it seems to have to study more. I checked as much as I could ... There may be errors found. Let me know in that time and I will reflect it If you want to edit the CPU information yourself manually, please refer to the contents below. ——————————————————————————————————————————————————————————————— Location : /usr/syno/synoman/mobile/ui (6.x), /usr/syno/synoman/webman/mapp(not yet 5.x) Source : mobile.js / mobile.js.gz(above 6.2) {name: "model",label: _T("common", "ds_model")}, -> Add Back Add Contents: {name: "cpu_series",renderer: function(value){var cpu_vendor="Intel";var cpu_family="Xeon";var cpu_series="E3-1230 V2";var cpu_cores="1"; return Ext.String.format('{0} {1} {2} ({3}Core)', cpu_vendor, cpu_family, cpu_series, cpu_cores);},label: _T("status", "cpu_model_name")}, ——————————————————————————————————————————————————————————————— ============================================================================ Update new version (ch_cpuinfo ver 5.0) 2018.10.30 1. Improved CPU information collection command (Thanks to gericb, Vileserver) Change to pure core value without applying thread, and For Native H/W users, changed to display the number of cpus, the number of cores per cpu, and the number of threads. ## Vmware 1 CPU / 1 Core Setting ## Vmware 1CPU / 2Core Setting ## ex. 1 CPU 1 Core Not support HT -> 1 Core (1 CPU | 1 Thread) 1 CPU 2 Core Support HT -> 2 Cores(1 CPU/2 Cores | 4 Threads) 2 CPU 4 Core Support HT -> 8 Cores(2 CPUs/4 Cores | 16 Threads) Addtional, Let me give you my excuse.... Where I work I count the number of threads by the number of logical cores. It was a habit of judging it because of work, so I was able to display the total number of cores without any thought. I apologize for the wrong information. Core information collection method, please refer to the contents below. ============================================================================================ ## before cat /proc/cpuinfo | grep "processor" | wc -l ## After(The result of the following command is combined and dispalyed.) cat /proc/cpuinfo | grep "processor" | sort -u | wc -l cat /proc/cpuinfo | grep "physical id" | sort -u | wc -l cat /proc/cpuinfo | grep "core id" | sort -u | wc -l cat /proc/cpuinfo | grep "siblings" | sort -u | awk '{print $NF}' cat /proc/cpuinfo | grep "cpu cores" | sort -u | awk '{print $NF}' Update new version (ch_cpuinfo ver 5.2) 2018.12.07 1. Use bash change to sh (for compatibility with DSM 5.x version) #!/bin/bash change to #!/bin/sh 2. Publish the source through github(https://github.com/FOXBI/ch_cpuinfo). For versions DSM 6.x and later, you can use the binary as before. If you use busybox in DSM 5.x, you can use it as a source file(ch_cpuinfo.sh). ============================================================================================ Reference images 1) First run 2) Redi 3) Restore 4) Mobile View Download files ch_cpuinfo ver 1.0 - delete -> ch_cpuinfo_en.tar -> ch_cpuinfo_ko.tar ch_cpuinfo ver 3.0 - delete -> ch_cpuinfo_en.tar -> ch_cpuinfo_ko.tar ch_cpuinfo ver 4.0 - delete -> ch_cpuinfo_en.tar -> ch_cpuinfo_ko.tar ch_cpuinfo ver 5.0 - delete -> ch_cpuinfo_en.tar -> ch_cpuinfo_ko.tar ch_cpuinfo ver 5.2 - update new version -> ch_cpuinfo_en.tar -> ch_cpuinfo_ko.tar
  6. 2 points
    Download: 1. synoboot vmdk https://mega.nz/#!fdBWBJYB!P3MbGY2v_X_udUhaSgVBQZ74KNRf7vtjMCO39u1I91Y 2. juns loader for DSM 6.2 https://mega.nz/#F!ZlkHQTTb!keje3RK017OjTp3vuWb-Cw 3. synology DSM.pat for synology 3615xs https://www.synology.com https://archive.synology.com/download/DSM/beta/6.2/23648/ 4. open vm tools spk http://spk.4sag.ru/?fulllist=true 5. XPEnology Tool for Windows x64 https://mega.nz/#!V480zKjC!ktZ2irGALS9EkX3XJHxkKIb2NedWMGIliTdcczSGt8A PREPARATIONS unzip synoboot.vmdk from DS3615xs 6.0.2 Jun's Mod V1.01 unzip synoboot.img from synoboot_3615 mount synoboot.img partition 0 with osf mount Make sure to uncheck Read-only drive Go to the mounted drive, Grub folder and edit grub.cfg with notepad++  set SN and mac1 fro example 0011322CA785 mark boot option lines you dont need in esxi #menuentry "DS3615xs 6.2 Baremetal $VERSION" --class os { # set img= # savedefault # loadlinux 3615 usb # loadinitrd # showtips #} # #menuentry "DS3615xs 6.2 Baremetal $VERSION Reinstall" --class os { # set img= # loadlinux 3615 usb mfg # loadinitrd # showtips #} # #menuentry "DS3615xs 6.2 Baremetal AMD $VERSION" --class os { # set img= # set zImage=bzImage # savedefault # loadlinux 3615 usb # loadinitrd # showtips #} menuentry "DS3615xs 6.2 VMWare/ESXI $VERSION" --class os { set img= savedefault loadlinux 3615 sata loadinitrd showtips } save file, dismount all and exit. ESXi part: Upload synoboot.vmdk and synoboot.img to esxi (in one folder) Create new VM name the xpenology vm as you want and select linux and for example ubuntu x64 select your storage (no pic needed) and you should see customize settings now remove default disk remove scsi controller remove cd/dvd drive now set cpu at 2 set memory 2GB set network adapter 1 mac addres you have in the grub.cfg for exapmple 00:11:32:2C:A7:85 now add existing hard disk and point to the vmdk uploaded before. Make sure its on SATA 0:0 now add another sata device and add vm disks to it (sata 1:0, 1:1 etc) and now, the vm is done and finish now start your VM and wait to see after few minutes open in new tab browser find.synology.com click connect and configure and manual install point to DSM 3615xs.pat file downloaded earlier after you confirm instalation you should see after 10 minutes reboot enter user password and name for dsm unmark autoupdate and SMART test skip configure quickconnect dont share location with synology (find.synology.com will not find virtual dsm) now DSM is redy
  7. 2 points
    Hi! I made a little tool which can help you to get your XPEnology up & running without installing any software. It contains (as portable versions): - Nirsoft's USB device view (helps to identify the VID & PID of your USB boot media) - V2.76 - XPEnology Serial Generator for DS3615XS, DS3617XS and DS916+ (a converted version of the HTML site) - Win32 DiskImager (to write your modified synoboot.img to your USB boot media) - V1.0 (only available in V1.4.1) - OSFMount x64 (to mount the synoboot.img and modifiy it) - V1.5 - Notepad++ (best editor for changing values inside grub.cfg) - V7.5.3 - Synology Assistant (useful tool from Synology to find your XPEnology and install DSM) - V6.2-23733 - TFTP/DHCP portable (a small TFTP, DHCP and Syslog server by Ph. Jounin) - V4.6.2 - MiniTool Partition Wizard 10 (helps assigning already formatted/written USB devices to modify existing grub.cfg) - V10.3 - SoftPerfect Network Scanner - V6.2.1 - USB Image Tool - V1.75 - New: Rufus - V3.3 In the section "Downloads" all links open corresponding websites to download the files. For beginners I added a small HowTo for bare-metal installation. Update New link for download: https://mega.nz/#F!BtViHIJA!uNXJtEtXIWR0LNYUEpBuiA You'll have to run it "As Administrator" because some of these tools (like Win32 DiskImager) need to be executed with higher rights. It's possible that the SmartScreen filter will give you a warning, because the EXE isn't signed. Bug reports and comments are welcome Cheers Current version: V1.4.2 (2018-11-19)
  8. 2 points
    Ну про 8.2.2 я предупреждал. Косяк там присутствует. 8.1.3 работает стабильно. С перезагрузкой службы.
  9. 2 points
    Для тех кто хочет побаловаться с редактированием extra.lzma, скомпилил пакеты для VirtualDSM (ибо нефига это делать на основном хосте): python_kvmx64-6.1_2.7.14-18.spk - требуется для установки основного пакета debian-chroot_kvmx64-6.1_8.4-7.spk Как компилировать пакеты synocommunity для разных DSM (в т.ч. docker) - теория тут. Как править extra.lzma и что еще дополнительно ставить - теория тут (респект @IG-88). Ну, и бонус, для тех кто дочитал до конца - extra.lzma для 1.04b 918, должны гебирнироваться винты, если не крутятся пакеты, которые тормозят этот процесс и со скоростями какие-то чудеса произошли (походу память начала кэшироваться как положено). Пробуем, отписываемся. Как заменить не вытаскивая флешку - тут. Отдельное спасибо @TeleDDim за его идею, которая привела к неожиданным результатам.
  10. 2 points
    Yes, 6.2.1 is a Synology recommended update from 6.2. If you do NOT have an Intel NIC serviced by the e1000e driver, installing that update will brick your installation, otherwise it should be okay. You can confirm you have such a NIC by SSH to your box and type "lspci -k" and you should receive something similar to the following in your output: # lspci -k 0000:13:00.0 Class 0200: Device 8086:10d3 Subsystem: Device 15ad:07d0 Kernel driver in use: e1000e #
  11. 2 points
    Перед тем как что-то менять в своей работающей системе, настоятельно рекомендуется сделать резервные копии своих особо ценных данных, чтобы потом не жалеть об их безвозвратной потере. Все, что вы творите - это ваш страх и риск, никто не побуждает вас это делать. Самый простой и надежный способ безопасно попробовать - выключить хрень, отключить все диски и загрузочную флешку от действующей системы, взять чистый диск и другую флешку и попробовать установить новую версию загрузчика и системы, если прокатило, то делать уже на действующей системе. 1. Как установить (подготовительные работы описаны для компа с Windows): а) скачать образ загрузчика 1.04b (исходная тема тут), создать каталог в корне диска без символов на кириллице, например, c:/918/ и поместить туда образ загрузчика б) определить VID/PID флешки или картридера в который она вставлена (Панель управления - Диспетчер устройств - Контроллеры USB - Ваша флешка/ридер - Свойства - Сведения - ИД оборудования, нужно для того, чтобы система DSM опознала этот диск и не пыталась устанавливать себя на него, если неправильно определите и пропишите эти параметры, то система будет вылетать по ошибке 13 при установке в) скачать, установить и запустить программу OSFmount, смонтировать Partition 0 (15 Mb) из файла загрузчика, перед монтированием убрать галку Read-only drive г) скачать, установить и запустить программу Akelpad, открыть файл grub/grub.cfg на ранее смонтированном диске, правим, сохраняем: set vid=0xA234 #VID флешки/ридера set pid=0xB678 #PID флешки/ридера set sn=1780PDN123456 #sn set mac1=001132123456 #mac первой сетевой карты set mac1=001132123457 #mac второй сетевой карты, второй и последующий отличаются от первого на +1 в последнем разряде в шестнадцатеричной системе ... set netif_num=2 #количество сетевых карт ... set sata_args='SataPortMap=6' #контроллер sata, значения: 6 - 1 контроллер на 6 портов; 22 - 2 контроллера по 2 порта; 42 - 2 контроллера, первый на 4 порта, второй на 2 и т.п. Где брать sn и mac - ваша головная боль, гугл в помощь, система установится и будет работать с теми, которые изначально прописаны в загрузчике, но с ограничением функционирования некоторых сервисов и модулей, таких как: QC, пуш уведомления, активация кодеков для транскодинга, установка лицензий syno... Но для большинства и без них будет достаточно. На форуме писали, что прокатывало с sn и mac от других реальных моделей syno, но так не пробовал, поэтому утверждать не буду, кто хочет - дерзайте. д) размонтировать диск в OSFmount е) скачать, установить и запустить программу Rufus и записать ранее подготовленный образ на флешку з) вставить флешку в машину, на которой планируете запустить хрень, подключить диски, включить питание ж) отключить брандмауэр в антивирусе, в браузере набрать http://find.synology.com или установить Synology Assistant с сайта syno и найти вновь установленную хрень в вашей сети и) установить DSM установить хрень следуя инструкциям программы установки и приступить к настройке (как это делать здесь не описываю, ибо все ответы есть в базе знаний syno) Для ленивых есть утилита, где собраны основные проги для Windows x64 2. Если хрень не обнаружилась в сети, то скорее всего в загрузчике нет драйверов для ваших сетевых карт и/или для sata контроллеров. a) запустить программу OSFmount, смонтировать Partition 1 (30 Mb) из файла загрузчика, перед монтированием убрать галку Read-only drive б) скачать extra.lzma из этой темы и перезаписать в смонтированном диске в) размонтировать диск и перезаписать образ с добавленными драйверами на флешку г) попробовать запустить и найти хрень в сети, если не получилось, то увы и ах, либо просить, чтобы добавили дрова для ваших устройств в этой теме или самому их добавлять - теория тут 3. Транскодинг (нужны sn и mac от реальной железки) С наибольшей степени вероятности запустиnся на процессорах Intel начиная с 4го поколения (Haswell), но есть нюансы с моделями материнских плат и биосами. Проверяем следующим образом: hardware (hw) транскодинг - в корне системы должен быть каталог /dev/dri с тремя подкаталогами внутри, если его нет, но нет и hw транскодинга, чтобы проверить - ищем каталог в терминале/ssh командой cd /dev/dri. software (sw) транскодинг - должны подняться соответствующие кодеки, проверить можно командой в терминале/ssh cat /usr/syno/etc/codec/activation.conf Если результат такой, то он есть: {"success":true,"activated_codec":["hevc_dec","h264_dec","h264_enc","mpeg4part2_dec","ac3_dec","vc1_dec","vc1_enc","aac_dec","aac_enc","mpeg4part2_enc"],"token":"абракадабра"} Если ничего похожего нет, то нет и транскодинга. P.S. Просьба к админам прибить тему в шапке и дать мне доступ на редактирование первого поста этой темы, буду добавлять по мере поступления вопросов, ибо задолбали оленеводы, которые задают вопросы по установке, во всех подряд темах.
  12. 2 points
    Login (replace URL, PORT, USER, PASS) https://URL:PORT/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=USER&passwd=PASS for ActiveBackup its the following urls Get Activationstatus https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=get&version=1 Set ActivationStatus (use your SERIALNUMBER) https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="SERIALNUMBER"  for Office365 its the following urls Get Activationstatus https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupOffice365&method=get_activation&version=1 Set ActivationStatus (use your SERIALNUMBER) https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupOffice365&method=set_activation&version=1&serial_number="SERIALNUMBER" for GSuite its the following urls Get Activationstatus https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=get_activation&version=1 Set ActivationStatus (use your SERIALNUMBER) https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=set_activation&version=1&serial_number="SERIALNUMBER"
  13. 1 point
    Let me introduce my build First of all Thank you guys for your help & advises. So I got my first NAS two years ago. (WD My cloud ex2 ultra) and couple months ago I got WD PR4100... Initially I choose WD just because I had no experience and I got a deal. I wasn't happy with that. I had many problems with almost everything. Customer support is terrible... Very poor OS and etc. Finally I decide to go to Synology and good for me I found this great website and project. Thanks! Parts list: 1. ASRock Motherboard Motherboards Z370M-ITX/AC ($95.90 + $8.87 Tax = $104.77) 2. Intel i7 8600k (I had 8700k but gave it to my friend on NY) = $259.89 3. EVGA 450 BT, 80+ Bronze 450W = $24.99 + $2.31 = $27.30 4. Patriot Viper Elite Series DDR4 8GB PC4-21300 2666 MHz Memory Module = $53.99 + $4.99 = $58.98 5. Lian-li q25b = $40 (Craiglist) = $490.94 1.03b + DSM 6.2 + DS3617XS. Especially want to mention MB. Happy with that. 6SATA + Mini ITX form-factor. Exactly what I want for my case. WIFI + 2 LAN ports. Good price also. I didn't include HDDs because it's all up to you. But I have 2x2TB Hitachi & 2xWD4TB Red NAS. Now I am testing the system Hitachi's HDD. Also I want copy/paste my post from my first thread about issues. I wasn't able to find NAS after first boot. I did 4 things and problem is gone. 1. Turn off Audio Controller 2. Change priority to onboard graphics. 3. Turnoff bluetooth controller. 4. Turn off wireless adapter. Please, see pictures. I will glad to know your feedback. P.S. English is second language. Post can (for sure) have linguistic/grammar mistakes.
  14. 1 point
    Кому лениво перезаписывать флешку или нужно сделать это удаленно при редактировании grub.cfg и замене extra.lzma, вспомнил про старый трюк, как это сделать прямо на работающей хрени: 1. Заходим по ssh через Putty или терминал 2. Делаем следующее: Admin@your_DS:~$ sudo -i #Заходим под root Password: #Вводим пароль Adminской учетки root@your_DS:~# mkdir -p /tmp/synoboot_part0 #Создаем временный каталог для монтирования 0 раздела загрузочной флешки root@your_DS:~# mkdir -p /tmp/synoboot_part1 #Создаем временный каталог для монтирования 1 раздела загрузочной флешки root@your_DS:~# cd /dev root@your_DS:/dev# mount -t vfat synoboot1 /tmp/synoboot_part0 #Монтируем 0 раздел загрузочной флешки root@your_DS:/dev# mount -t vfat synoboot2 /tmp/synoboot_part1 #Монтируем 1 раздел загрузочной флешки root@your_DS:/dev# ls /tmp/synoboot_part0 #Проверяем монтирование 0 раздела загрузочной флешки bzImage EFI grub info.txt root@your_DS:/dev# ls /tmp/synoboot_part1 #Проверяем монтирование 1 раздела загрузочной флешки checksum.syno extra2.lzma extra.lzma grub_cksum.syno rd.gz Sone.9 zImage 3. С помощью nano/mc правим grub.cfg и/или с помощью команд/mc заменяем extra.lzma 4. Перезагружаем хрень штатными средствами 5. Если перезагрузка сразу не планируется, то на всякий случай размонтируем и зачищаем: root@your_DS:/dev# cd / root@your_DS:/# umount /tmp/synoboot_part0 # Размонтируем 0 раздел загрузочной флешки root@your_DS:/# umount /tmp/synoboot_part1 # Размонтируем 1 раздел загрузочной флешки root@your_DS:/# rm -r /tmp/synoboot_part0 # Удаляем временный каталог root@your_DS:/# rm -r /tmp/synoboot_part1 # Удаляем временный каталог
  15. 1 point
  16. 1 point
    ясно-понятно )) ни одного глюка, а транскод - так не глюк ))) я выкидывал из extra.lzma модуль i915 и выключение начинало работать в 6.2.1 - могу поделиться на пробу, В 6.2 выключение работало и так с родным джуновским 1.03.
  17. 1 point
    дыа ) но я пока такой план наметил: прошить последнюю прошивку для этого адапетра и попробовать 1.04 ещё раз )) ну если смотреть на лог, то первой идёт вот такая процедура i2c_transfer+0x79/0x90 Она я так понимаю в модуле i2c, а не agppart. Этот адаптер HDMI как раз так и управляется через i2c. И с ним под виндой косяки тоже, так что может прошивка спасет )) Но чтоб прошить надо поставить винду 10 - я попробовал PE загрузить, там дрова нормально не встают для этого ) Вобщем, наши руки не для скуки ))
  18. 1 point
    Отвечу сам себе. Проблема возникает при конфигурации процессора - N одноядерных. Если сделать один процессор N ядерный, все в порядке.
  19. 1 point
    И совсем простое решение.
  20. 1 point
    собрал флешку с вашим файлом, воткнул в порт. но саму систему не переустанавливал. а надо? система загрузилась, транскод работает, все хорошо кстати, на 916+ диски спать не умели на хренологии. сейчас без проблем, что тоже гуд
  21. 1 point
  22. 1 point
    - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 u2 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: YES - Installation type: BAREMETAL - Microserver Gen8 - Additional comments: Need Reboot
  23. 1 point
    Может пригодится кому. Я долго бодался с j3455n-d3h. С загрузчиком 1.04b 918+ скорость копирования была порядка 30 Мбайт/c с просадками до 0. Вопрос решился установкой C-States = disabled в BIOS. Теперь +-100 стабильно по SMB.
  24. 1 point
    Perhaps a little bit too early, but will there be a Powerbutton Package for DSM 6.2?
  25. 1 point
    download this: https://www.dropbox.com/s/ytimsezu9cl61xx/synoboot_1.02b_ESXi_only.zip?dl=0 the only option available is ESXi, so you should not have problems regarding boot choice, it's for DS3615xs (i find has a better custom package support than DS3517xs). - extract and upload synoboot.vmdk and synoboot.img in your datastore - create a new VM (HW Version 11 or 13) dependent if you are on ESXi 6.0u2 or ESXi 6.5b - operating system should be Other -> FreeBSD 64bit - set bios to EFI - set nic to VMXNET3, set the mac manual to the same as the one in the grub.cfg - set scsi controller 0 to "LSI logic SAS" - add sata controller 0 if not there yet present - add existing hdd -> browse datastore -> add synoboot.vmdk - edit this hdd to "independent - persistent" and sata 0:0 on controller 0 - add how many new scsi disk you like, thin provisioning - dependent - save and poweron the VM - from your browser, go to find.synology.com, it should pop-up, connect and install it (manual or from internet is the same), reboot after finish the setup - create a new volume to your needs, if you want shr you have to modify synoinfo.conf - download this zip for open-vm-tools https://www.dropbox.com/s/k4hc343gwdepiuf/open-vm-tools_bromolow-6.0_10.0.7-1.spk.zip?dl=0 - extract the zip, install the spk in package manager - now ESXi should see that vm tools are installed and running Pretty much done.