Leaderboard


Popular Content

Showing content with the highest reputation since 02/10/2019 in all areas

  1. 5 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. Просьба к админам прибить тему в шапке и дать мне доступ на редактирование первого поста этой темы, буду добавлять по мере поступления вопросов, ибо задолбали оленеводы, которые задают вопросы по установке, во всех подряд темах.
  2. 4 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)
  3. 3 points
    You were so close, that knowledge arrives on the 16th minute of looking. https://xpenology.com/forum/topic/9392-general-faq/?tab=comments#comment-95507
  4. 3 points
    Hello @FOXBI. Is it possible to update your tool so that it is fully functional with the latest release of DSM 6.2? Thanks.
  5. 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
  6. 2 points
    Einfachste Vorgehensweise: - System herunterfahren und alle HDDs abklemmen - eine einzelne leere HDD anschließen - System wieder hochfahren und aktuelles DSM installieren - testen, ob alles funktioniert; besonders die Netzwerkverbindung - System wieder herunterfahren, alte HDDs dran und dann upgraden
  7. 2 points
    У меня стоит MidnightCommander из репозитория Synocommunity. Соответственно захожу через putty по ssh под учётной записью админа, далее ввожу sudo su и запускаю Миднайт - mc. В нем есть редактор по F4. Можно ещё редактор nano поставить, может ещё какой можно линуксовый.
  8. 2 points
    Please see this for loaders vs. versions. 6.2.x has a number of hardware constraints on it, so you may need to pick your loader and platform carefully, referencing your hardware.
  9. 2 points
    très bien , contacter moi mercredi ou jeudi je vous donnerais les info pour l'envoie etc ......
  10. 2 points
    Que dire à ta question.... : http://www.reseau-des-marabouts.com/
  11. 2 points
    Решил позволить себе жить с размахом(с) и взял в рассрочку на год Asrock J4105-ITX и две планки памяти DDR4 Crucial 4Gb 2666Mhz (BLS4G4S26BFSD) вышло чуть больше тысячи месяц - могу себе позволить ))) Перекинул жесткий диск на неё, сделал флешку с 1.04 и мигрировал с 6.2 3617 на 6.2.1 918. Всё встало, папка dev/dri появилась, но транскодинг нормально не заработал - при этом в dmesg было примерно такое: Форматнул на жестком первые два раздела, сделал заново флешку - та же хрень. А всё почему? - потому что не надо было трогать настройки биоса - влючил зачем то vt-d. Вернул всё в дефолт и всё заработало без переустановки, думаю и смиграцией бы срослось если не лазил бы. Да - биос 1.4 сразу был на борту. Обратите внимание на скрине выше какаят о ошибка про gen8, а в 4105 - gen9, то есть драйвер не заточен так скзть под проц полностью. Теперь о транскоде вот такого видео hevc, 77272.2 Kbps, 3840 x 2160, кадров 59.940 Профиль Main Level 153: в VideoStation проц на одном этом видео в районе 15-20%, Emby - аналогично, через "Сервер мультимедиа" по DLNA так же, и теперь мои древние Соньки могут видеть всё - сэкономлю на приставке ))) А с плексом какая то дурь, аппаратный работает, но существенно сильнее грузит проц на 100%: Да, по поводу установки - я ставлю PAT файл DSM_DS918+_23824.pat "ручками", но после установки система стоит уже 6.2.1 u4 - во время установку, бутается она два раза - после того как счетчик процентов дойдет до 100 и пойдет обратный таймер, и один раз сама во время обратного отсчета 10 минут, - видимо как раз и ставит обновы. Система грузится меньше минуты, скорость по сети не максимуме - 109-112 мб/сек. Вобщем рекомендую к покупке )
  12. 1 point
    Before you begin to change something in your working system, it is strongly recommended to make backups of your most valuable data, so you do not regret about their irretrievable loss. Everything you do is your fear and risk, no one encourages you to do it. The easiest and most reliable way to safely try to do it, turn off all the disks and the boot flash drive from the current system, take a clean disk and another USB flash drive and try to install a new version of the bootloader and the system, if it rolled, then do already on the current system. 1. How to install (described for a computer with Windows): a) download the 1.04 b boot loader image (the original theme is here), create a directory in the root of the disk, for example, c:/918/ and put the bootloader image there b) determine the VID/PID of the flash drive or card reader into which it is inserted (control Panel-Device Manager-USB Controllers-Your flash drive/reader-Properties-Information-hardware ID, you need to ensure that the DSM system recognizes this disk and does not try to install itself on it, if you incorrectly define and register these parameters, the istall process will crash by mistake 13) c) download, install and run the OSFmount program, mount Partition 0 (15 Mb) from the bootloader file, remove the "Read-only drive" checkbox before mounting d) download, install and run Akelpad, open grub/grub file.cfg on previously mounted disk, edit and save: set vid=0xA234 #VID flash drive/reader set pid=0xB678 #PID of flash drive/reader set sn=1780PDN123456 #sn set mac1=001132123456 #mac of the first network card set mac2=001132123457 #mac of the second network card, the second and subsequent differ from the first by +1 in the last bit in the hex system ... set netif_num=2 #number of network cards ... set sata_args= 'SataPortMap=6' # sata controller, values: 6 - 1 controller on 6 ports; 22-2 controllers on 2 ports; 42-2 controllers, the first on 4 ports, the second on 2, etc. Where to get sn and mac - is your headache, Google will help you, the system will be installed and will work with those that are initially registered in the bootloader, but with the restriction of the functioning of some services and modules, such as: QC, push notifications, activation of codecs for transcoding, installation of syno licenses... e) unmount the disk in OSFmount f) download, install and run the Rufus program and record the previously prepared image on a flash drive g) insert the flash drive into the computer on which you plan to run xpen, connect the drives, turn on the power h) disable the firewall in the anti-virus, in the browser type http://find.synology.com or install Synology Assistant from the syno website and find the newly installed xpen on your network j) install DSM following the instructions of the installation program and start setting up (how to do it here is not described, because all the answers are in the syno knowledge base) There is a utility where the main programs for Windows x64 are collected 2. Transcoding (needs sn and mac from real syno hardware) Most likely to run on Intel processors starting from the 4th generation (Haswell), but there are nuances with motherboard models and BIOS. Check as follows: hardware (hw) transcoding - at the root of the system should be a directory /dev/dri with subdirectories in it, if not, but there is no HW transcoding to check - look for the directory with the terminal/ssh command cd /dev/dri . software (sw) transcoding - some codecs must run in DSM, you can check it with the command in the terminal / ssh cat /usr/syno/etc/codec/activation.conf If the result is the same, sw transcoding will ran {"success":true,"activated_codec":["h264_dec","h264_enc","mpeg4part2_dec","hevc_dec","aac_dec","aac_enc","ac3_dec","vc1_dec","vc1_enc"],"token":"123456789987654abc"} If there is nothing similar, there is no sw transcoding. 3. Perhaps the most optimal budget solutions with transcoding will be the following: ASRock J4105-ITX Asrock J5005-ITX Who wants more - use mb with the latest generation of Intel processors with Intel i210 or realtek 8111 . But this is already determined by the size of the your wallet and the functionality that you additionally want to get from xpen. P.S. Sorry for my english 😂
  13. 1 point
    Bien vu, réinstallation propre et import de la config à l'issue et ça refonctionne. Merci beaucoup
  14. 1 point
    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 available: 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, you 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 bc 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 basically 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" (command line 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
  15. 1 point
    Hi, Dsm 6.2 (DS3615XS) WORK to Virtualbox. I managed to run dsm 6.2 (ds3615) on Virtualbox, be careful that version 6.2.1 does not work). It will be necessary to download the good spk on the syno download center. You must first configure grub (the mac address must match the one entered in the vm), then convert the .img file to .vdi (VBoxManage convertfromraw --format VDI "source file path" "target file path" ). In the settings of the VM, you have to use as storage manager: SATA (override all others). In first pausition put the IMG file converted to VDI, then all other virtual disks. In the system settings of the machine (tab motherboard), choose the number of processor and memory allocated (2 processors for me and 2048MB of RAM) and especially used chipset ICH9 (otherwise does not start correctly). In the network card part, enable card, bridge access, advanced settings, choice of Intel PRO / 1000MT Desktop card. Be careful to fill in the correct mac (same as grub). Usb: default (use usb 1.1) Serial port: enabled (COM1 - disconnected) When starting the machine, choose baremetal option. Good fun
  16. 1 point
  17. 1 point
    Do I need to have a nvme card installed?
  18. 1 point
    The easy way would be to - shut down your Nas - unplug all hdds - plug in a blank hdd (can be a small or older model, 250gb for example) - start up your Nas and do a new installation - install the updates and check if everything is working - shut down your Nas again - unplug the test hdd and plug in your previously used hdds - start the Nas and install the update
  19. 1 point
    My guess is that the maximum thread represented in DSM is 8. I have not had a system with more than 8 threads, so I have not checked, can you show me the full results of your system cat /proc/cpuinfo ?
  20. 1 point
    Salut, DSM 4 ? C'est vieux, le loader n'est même plus dispo Se que je te conseillerai c'est d'essayer de migrer vers 5.2 ! https://xpenology.com/forum/topic/7848-links-to-loaders/ D'abord essaye ta config, voir si elle est compatible avant de faire quoi sue se soit sur les disques dur avec tes données ! L'idéal étant de débrancher tout des DD, de brancher un disque de test et d'essayer linstallation de DSM 5.2 ! Si le hack fonctionne bien ( et donc le NAS ) alors tu peut essayer la migration !
  21. 1 point
    Hi Everyone! Aldo here, wanted to thank you for the awesome work on Xpenology! Did not yet start my first box, but lots of useful infos to read.. thanks anyone!
  22. 1 point
    Oui et d'ailleurs vous allez vous calmer rapidement même. @JacquesF a poster pour vous aidez alors qu'il en avait aucune obligation. Si sa réponse ne vous convient pas ou alors qu'elle ne répond pas à votre problématique, la moindre des choses serait d'avoir un peu de courtoisie et de reconnaissance au lieu d'avoir une attitude agressive est désagréable envers un member respecté par la communauté. Vous ferez bien de relire les règles du forum et de faire en sorte que ce type d'attitude ne resurgissent plus. Merci d'avance.
  23. 1 point
    Every time a raid with parity (raid5, 6 or shr-x) is created, expanded or repaired, DSM will perform the parity check. It’s possible to skip this by rebooting the system, but not advisable. Other raid setups like mirroring (raid 1 or 10), stripes (raid 0) or jbod don‘t need this.
  24. 1 point
    Conseil pour la suite, une fois le mot de passe récupéré : - activer SSH - configurer le NAS (manuellement) pour autoriser les connexions SSH par clefs - mettre en place un accès root (ou un autre compte administrateur) via cette option Ça évite l'échec de connexion suite à des mots de passes erronés. Configuration à faire sur le NAS pour SSH pour ceux qui sont intéressés : Fichier /etc/ssh/ssd_config Rien à modifier, les valeurs par défaut autorisent la connexion : #PermitRootLogin yes #RSAAuthentication yes #PubkeyAuthentication yes #AuthorizedKeysFile .ssh/authorized_keys Placer simplement la clef RSA publique dans le dossier (à créer) .ssh du répertoire home du compte à utiliser dans le fichier authorized_keys Donner les bons droits au dossier et fichier : chmod 755 .ssh chmod 600 .ssh/authorized_keys chown -R NomUtilisateur:NomUtilisateur .ssh Se connecter avec la clef privée (et la bonne identité bien entendu). Pour une procédure plus détaillée (création des clefs, etc...), les tutos ne manquent pas sur le net, tout dépend de l'OS à partir duquel vous ferez la connexion Jacques
  25. 1 point
    Salut, Un redémarrage en mode "Reinstall" devrait te permettre de faire une réinstallation de DSM via Synology Assistant avec pertes de la configuration mais conservation des données. Par contre, pour moi, avec Loader 918+ 1.04b cela n'avait pas marché ( le mode "Reinstall" au boot ne semblai pas fonctionner ), j'avais donc fait une migration vers un autre loader ( ds3615 pour ensuite revenir vers 918+ ).
  26. 1 point
    AFAIK the limit is in the kernel itself, as compiled by Synology. The platforms enabled by the current loaders have the following compute characteristics: DS3617xs - Xeon D-1527 - 4C/8T DS3615xs - Core i3-4130 - 2C/4T DS918 - J3455 - 4C/4T There has been some confusion about cores vs. threads. I think that 16 threads is the kernel limit. As you can see, 16 threads covers all these CPUs and we have evidence that 16 threads are supported on all three platforms. If you have more than 8 cores, you will get better performance by disabling SMT. @levifig, you are already doing this. I don't think there is any other way to support @Yossi1114's 10C/20T processor other than to disable SMT. If someone wants to develop a loader against a platform with more thread support, may I suggest investigating the FS3017 (E5-2620v3 x 2 = 12C/24T) FS2017 (D-1541 = 8C/16T) or RS3618xs (D-1521 = 8C/16T). It would stand to reason that the kernel thread limits might be higher for those platforms.
  27. 1 point
    Awesome help! I was able to make it work with that script as a base with some slight modifications. Name of service had to have "ctl" after "pkg" and no "-synovideopreprocessd" after package name. #!/bin/sh if synoservicectl --status pkgctl-VideoStation | grep 'start/running' then curl --retry 3 https://example.com else curl --retry 3 https://example.com/fail fi Thank you @Olegin!
  28. 1 point
    Пробовал и на виртуалке и на железной хрени, нужно привязать ее к учетке. Как-то так...
  29. 1 point
    Нашелся на работе ненужный винт на 160 gb, решил помучать хреню. И хреня последняя на 918+ завелась. Мать asrock j3455-itx, биос 1.80, сетевая стоковая от матери Использовал ds918+(V1.04b for DSM 6.2.1) + DSM_DS918+_24922.pat lzma НЕ правленый, установка локальная. После установки хреня ушла в перезагруз и висела минут так 7, сходил проверил - сетевая вообще ничем не моргает. Решил отключить монитор и клаву, тут же очухалась сетевая и на нее пошел пинг, после хреня загрузилась и заработала. В биосе отключено все, что можно отключить, включен режим спорт (вроде так называется) - эти настройки были сделаны еще для 6.1.7 и не менял для текущей установки.
  30. 1 point
    Salut, Je ne suis sur mobile, mais je vais déjà t'apporter quelques élément de réponses. 1. Oui niveau sécurité, il faut passer à 6.2, 6.1 n'est plus maintenu ( actuellement seul 5.2 et 6. 2 il me semble) Edit : 6.1.7 et aussi maintenu, il n'y a donc aucune "urgence" a migrer sur 6.2.2 si 6.1.7 fonctionne ! 2. Si tu en trouve pas de config similaire sur le forum, dur de savoir. 3. Oui, je te conseil malgré tout de faire une sauvegarde de ta configuration du nas dans le panneau de config, et une sauvegarde de tes conteneurs. Que se soit pour n'importe quoi, avant une maj, on prend ses précautions ! Dans le pire des cas, les partitions des donnés sont accessibles via un Linux live dont tu trouvera la procédure sur le forum ou sur le site Web de synology. Je te conseil egalement d'activer ssh avant la maj s'il ne les pas, en cas de panne, l'accès par ssh peut sauver la mise ! Ensuite si tu préfère qu'il soit désactivé tu le ré désactive. 4. Oui c'est possible, les migrations marche très bien. Par contre il n'y a pas de réel avantage pour toi je pense à choisir 3617xs, sachant que 3615xs est celui qui apporte la plus grande compatibilité. 5. Non, se que je te conseil c'est une fois sauvegardé le max, (config, conteneurs, donnes sensibles,..) d'éteindre ton nas et de débrancher tout tes disques. Tu ne branchera que sur le 1er port sata un disque dur vierge ( un truc de recup par exemple). Sur une nouvelle clé usb tu installe le loader pour 6.2 ds 3615xs à l'aide du tuto sur le forum. Et tu fait une installation propre afin de tester le fonctionnement du nas. S'il l'installation se passe bien, que tu accède au nas, que tu peu créer un volume sur ton disque, que tu peu installer des paquets, que le nas redémarre bien même après l'avoir éteint alors tu peut lancer la mise à jour. Tu éteint tout, tu rebranche tes disques comme à l'origine et tu démarre sur ta nouvelle clé en mode upgrade pour faire la maj. Si déjà l'installation "propre" ne marche pas alors ne fait pas la maj sans comprendre ou cela a planté !
  31. 1 point
    Thx man, it is working fine with both eth interface. I am running DSM 6.2.1 at the moment without any pb !
  32. 1 point
    Стратегически правильное решение не заниматься костылями, а поставить сетевуху Intel или HP и юзать без виртуализации... Я отказался от виртуальной DSM когда попробовал пробросить диски и попытался покрутить бесперебойник к EXSI по USB... После этого я понял что такой гемморой не для меня...
  33. 1 point
    - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: HP Proliant MicroServer Gen8 with E3-1265L V2 2.50GHz - Additional comments: Migrated from DS3617xs, internal nics do not work but Mellanox ConnectX-3 10GBe (MCX311A-XCAT) works, no need to disable internal nic in bios, you need them during installation, Shutdown and restart do not work
  34. 1 point
    I add a new parameter "MAX PWM for normal use" until overheat, then jump to 255. -So it start with pwminit -use cicle testing setpoint temperature and set the fan between pwmmin and pwmmax_n -when overheat, the fan jump directly to 255... it look something like lm-sensor did, more or less So now the parameters are: <debug> <test_temp> <pwminit> <setpoint> <interval> <overheat> <pwmmin> <pwmmax_n> <kp> <ki> <imax> <kd> I scheduled at boot: /root/fancontrol 0 1 40 35 20 42 40 160 you have to tuning the temperature for DISK or CPU... setpoint 35° and overheat 42° for CPU, seems to work for me (maybe have to be a little bigger, but for now i want the fan to "spin up and down" to control code, so it's ok) source fancontrol.cpp and executable for DSM 6.2.1 fancontrol
  35. 1 point
    Это не ваше железо, а то на чем 3612 сделана была, кроме объема памяти и частоты процессора. Нужно реальное железо: мать, проц, сетевуха. Только по железу. В 6.1 точно уже было.
  36. 1 point
    Hi guys, I am new to this such a great project. I am making a plan to build a server using Xpenology. I was born in Japan and now I am in New York. I am really excited to see my own build. thanks
  37. 1 point
    Penso in Pannello di controllo --> Notifica --> Sistema
  38. 1 point
  39. 1 point
    Когда добавляешь камеру выбери не название а -определяется пользователем. Там введи тот путь который я тебе написал. Конечно же изменив ип и пароль на свои. rtsp://admin:Password@IP:554/h264_hd.sdp
  40. 1 point
    There's a great tutorial video on youtube. Install 3515 instead of 3617 though. Also download the xpenology tool from this website. It really helps.
  41. 1 point
    Фигня, @montagnic уже указал как устранить.
  42. 1 point
    Thanks @Olegin, seems to have worked flawlessly now. This was the output:
  43. 1 point
  44. 1 point
    Just delete the XML tag with the serial number of the drive in question. When you reboot the tag will be regenerated and any reconnect history will start from 0.
  45. 1 point
    Hi everyone, stupid question but I have not found an answer to the problem I currently have. I have only seen a few other people who have the same experience, but no solution. So I have tried Jun's loader V1.03b for the 3617xs and I have tried V1.04b for the 918+ on my ESXi host. But unfortunately no network connection shows up. I have used the "ESXi" option, tried the e1000 and e1000e but no success. I have changed the serial and matched the MAC with the one on the host with no luck. I guess the loader does no support that network card? How can I figure that out? Can I activate the dmesg log when the loader starts? If yes, how can I do that? I am running ESXi 6.5u2 on two Xeons L5630 on my test-host. Thanks in advance.
  46. 1 point
    When you download a pat form this page (https://www.synology.com/en-global/support/download/DS3617xs#utilities) it will always be the mose recent Version. This Version, 6.2.1-23824-2, didn't work with bootloader 1.03b on the Gen10. The Bootloader 1.04b did not work proper on the Gen10, network is okay, but access to the hdd controller fails. I tried it more than once and every test system was bricked. To get an running DSM you have to use an older DSM pat, i recommend to go there: https://archive.synology.com/download/DSM/release/6.2/23739/, pick the xs3617xs an make an manual insallation. Should work like a charm!
  47. 1 point
    Если скучно то опишите как на роуторе mi-mini xiaomi, по pxe через tftp загрузчик подгружать чтобы не плясать с флешкой вокруг сервака, и грузиться на прямую с сети.
  48. 1 point
    Hi, I can confirm thant Intel X550-T2 with ds3617xs + Jun's loader 1.02b work without any software mod. Full Plug and Play for me. Regards
  49. 1 point
    Salut, donc si je te suis bien, tu revends un HP54L que tu as acheté 100€ qui a donc resservi 2mois au même prix ?! Sans moi dsl
  50. 1 point
    Juns bootloader he creates a custom zImage which loads up the DSM software, could he, compile a new kernel with the LIMIT set to something like 24/32 something in the region of 2017... server cores. Seeing as we can get a single CPU with 8 cores then HT to 16 logical, 8 is becoming rather limiting.