Leaderboard

Hi, everyone, Thanks for you patience. I've uploaded a beta version of 3615/3617 loader to mega, please test and give your feedback. https://mega.nz/#F!ZlkHQTTb!keje3RK017OjTp3vuWb-Cw note: uefi boot still has issue, it will be fixed when I have more time. ---Beginning of addition by polanskiman--- ---End of addition by polanskiman---

This version is alpha, as the loader 1.03a2 is, so DO NOT use this on a "production" systems and be prepared to loose the data you have on the "test-system" (I recommend you have a very recent backup) !!!all sata_* and pata_* drivers are still not working because of the kernel source changes Synology did (same as in kernel 3.10.102 used and modded by Synology), as long as no one writes a patch for this I can use to fix this, it will stay this way !!! HP SmartArray Controller driver (hpsa.ko) is back in for testing (for now the one that comes with kernel 4.4.59), my P400 i had access to was to old for this driver so please try to test, newer controller even seem to have a IT mode so if present try it with this mode To check if the hardware is supported with a driver, use a running DSM installation or boot a live Ubuntu from usb. In console type the following: lspci -k | grep 'Kernel driver' That command will list the used kernel modules for the hardware. Modules for network and storage will be listed. Compare that with the list of modules that comes with the extra.lzma ramdisks provided below. extra.lzma for DS918+ v0.2 (still online for testing against new 0.4) http://s000.tinyupload.com/?file_id=07387126858558680182 extra.lzma for DS918+ v0.3 http://s000.tinyupload.com/?file_id=85595242169584467630 extra.lzma for DS918+ v0.4 http://s000.tinyupload.com/?file_id=02211720902276656395 extra.lzma for DS918+ v0.5_test http://s000.tinyupload.com/?file_id=01077994252925895830 Note: the driver list below with related hardware is based on Trantor/Quicknick's older list for 5.2 and 6.0 so thanks goes to them and all others who helped to build the older list for 5.2 and 6.0. Caption (…) Not compiled for now, ask for it […] Either confirmed by users that it is not working OR not supported for DSM 6.2 (kernel 4.4.59) OR does not load at all. Driver was compiled/tested but removed - if someone finds a way to get it working in some way, tell us here and it will be added  If you wish to make a driver request do so in the topic linked below: If you wish to discuss problems about modules in these ramdisks then drop a post below. Please be specific and provide relevant information such as: ramdisk version, loader model, motherboard and any additional storage/networks cards present in the system. Other things good to know about DS918+ image and loader 1.03a2: 1. DS918+ image comes with a limit for 2 internal network ports in synoinfo.conf (the original hardware has two ports and does not have a pcie slot for extending) jun's loader does not changes this (now?), so if you plan to user more then 2 ports you will have to manually change the synoinfo.conf (3615 and 3617 are bigger business models and have options for additional network card, the default from synology is 8 on this systems) further information can be read here: 2. hardware transcoding seems to crash the system when a monitor is attached, unplug monitor, reboot try again to see if there is decoding hardware present you can try this (there should be something in like card0) ls -al /dev/dri/ when using plex you should download the 64bit version from website, with plex pass active (hardware-accelerated streaming is a premium feature and requires an payed active Plex Pass subscription), Settings > Server > Transcoder, Turn on Show Advanced, Turn on Use hardware acceleration when available 3. if your screen goes blank during boot and the system does not show up in network the kernel might have crashed on boot while loading i915.ko driver (CPU internal GPU) look in your bios for a legacy mode option, disable it and try again (boot process and crash can be seen when using a "good old" serial cable and a console program like putty on a 2nd computer - that's rarely done but if you want to know for sure, that's your way to find out, DSM does not have a typical boot screen that shows log info and login prompt after boot, that's redirected to the serial port)

Всем привет! Долго искал и нашел как сделать, чтобы скачивать книги минуя MyHomeLib прямо на читалку. Особенно актуально в пору отпусков. Первоисточник тут. Итак, поехали: 1. Запоминаем путь где лежит Librusec, например, /volume2/Downloads/Librusec/lib.rus.ec 2. Ставим php 5.6 3. Ставим и настраиваем Web Station Проставляем все галки и выбираем все расширения, в open_basedir в конец строки через двоеточие добавляем путь к библиотеке из п.1 5.Скачать и распаковать архив copsfb2.zip в корень web-сервера 6. В директорию (от корня web-сервера) copsfb2/create_db/ скопировать librusec_local_fb2.inpx и соответственно отредактировать в copsfb2/create_db/create_db_conf.php параметр $inpx_file 7. На директорию (от корня web-сервера) copsfb2/fb2lib/ дать права на запись для группы http, под которой работает web-сервер. 8. Отредактировать в copsfb2/config_local.php параметры: $config['zipbook_directory'] должна указывать путь к архивам с книгами (п.1). Другие параметры пока не трогаем! 9. Запустить проверку: http://diskstation/copsfb2/checkconfig.php . diskstation - адрес вашей хрени. В выводе должны быть все Ok, кроме последнего, где говорит, что не найден metadata.db, это нормально 10. Запускаем загрузку INPX и создание metadata.db: http://diskstation/copsfb2/create_db/create_db.php 11. Если предыдущий пункт прошел успешно, запускаем http://diskstation/copsfb2/index.php, проверяем навигацию по библиотеке и закачку. Если есть проблемы, проверяем настройки путей и open_basedir 12. По желанию редактируем остальные параметры в copsfb2/config_local.php и copsfb2/config.php, например, ставим пароль на доступ к странице.

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.7 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.7 but only to DSM 6.0.2 then use the link above. To upgrade from DSM 6.0.2 to DSM 6.1.7 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. One last thing: DO NOT UPDATE DSM BEYOND VERSION 6.1.7 with loader v1.02b. IN OTHER WORDS DO NOT UPDATE TO DSM 6.2 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 up to DSM DSM 6.1.7-15284. 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/. DO NOT UPDATE TO DSM 6.2. The loader is not compatible. 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 ############# ############## Tutorial UPDATES ##################

Hallo, ich hab mich erst weider neu registrieren müssen... auch wenn ich seit Februar erst gefühlte 3x online war - hat sich irgendwas geändert? Nevertheless, auch ich hab versehentlich das Update auf 6.2 bei einem N54L Barebone Install gemacht - Bricked Aber es gibt einen Weg zurück, wenn auch unter Verlust der Konfiguration, zumindest wenn man wie ich keine Sicherung derselben hat. Aber das neu Aufsetzen der DSM mit gleichem Namen und IP und anschließender Konfiguration der User, Apps, Freigaben... alles Peanuts im Vergleich zum drohenden Datenverlust Das war mein Setup: - HP Proliant N54L - 4x4TB HDD - DS3615x mit DSM 6.1.x - JUN Loader 1.02, ich glaube noch die 1.02a oder sogar früher? Es wird benötigt: - USB Stick; der Alte kann dazu verwendet werden da sowieso nicht mehr nutzbar ist in dieser Form - neue Platte, komplett leer - Jun Loader 1.02b: synoboot.img Maga-Link - DSM 6.1.7-15284: DS3615xs_15284.pat Syno-Link - Rufus oder Win32DiskImager für die Vorbereitung des USB Stick Wichtig: Die Loader- und Image-Dateien müssen zusammenpassen. Ich habe hier wieder die DS3615x Versionen verwendet. Gleiches sollte auch für die DS3617x oder DS916 gelten, das habe ich aber nicht getestet. Ausserdem - wie bereits erwähnt - Wichtig: Es werden hier nur die VOLUMEs repariert und in eine neu aufgesetzte NAS mit eingebunden. Sprich: Alle Daten waren wieder da, aber die Konfiguration und die installierten APPS, das musste alles manuell neu gemacht werden. Eventuell könnte hier eine vorherige Konfig-Sicherung helfen... ich hatte keine. Vorgehensweise: Der Stick und die Platte sollten komplett leer sein. Z.B. unter Windows 10 mit Diskpart kein Problem; gegebenenfalls als Admin starten. 'diskpart' starten 'list disk' um die HD/Stick zu identifizieren (WICHTIG, gegebenenfalls mit Windows DiskManager=Datenträger Verwaltung überprüfen) 'select disk #' wobei # für die Nummer eurer Disk/Stick steht 'clean' !!! DAS LÖSCHT DIE KOMPLETTE AUSGEWÄHLTE DISK OHNE RÜCKFRAGE !!! Neu Aufsetzen: wenn noch nicht geschehen: Stick und alle HDD von NAS entfernen Stick mit JunLoader 1.02b aufsetzen (.bin file) neue leere HDD in Slot 1 einsetzen; slot 1 ist wichtig für die spätere Reparatur des alten Volume NAS starten und mit 'find.synology.com' die neue NAS suchen richtige NAS aussuchen und auf Verbinden klicken die neue NAS ist noch nicht installiert. Hier mit MANUELLER INSTALLATION (!) fortfahren und das geladene DSM Image auswählen (.pat file) NAS Installation minimal fertig machen (Name und Benutzer), kein Volume anlegen NAS rebooten zur Kontrolle dass alles funktioniert Wenn die neue Minimal-NAS funktioniert, runterfahern, die alten HDDs der Reihe Nach wieder einbinden, natürlich um einen Platz versetzt da in Slot1 die neue HDD steckt. Bei meinem N54L war damit die 4. Platte nicht mehr im Case sondern jetzt mit dem ESATA Port von hinten verbunden. Noch dazu mit einem fehlerhaften Kabel, was später zu extra Schritten führte, aber dazu gleich mehr... NAS wieder starten. Es sollte jetzt idealerweise die neue NAS starten und eine fehlerhafte Partition /in meinem Fall ein fehlerhaftes RAID/ anzeigen und zur Reparatur auffordern Reparatur starten (hat bei mir keine 10sec gedauert) Da mein Kabel zur 4. Platte defekt war wurde diese hier nicht erkannt. Auch ein weiterer Reboot mit neuem Kabel hat diese Platte dann nur noch als weitere "leere" Platte mit fehlerhaften Systemdaten ausgewiesen. Mit meinem Hybrid RAID und somit einer Platte Redundanz konnte ich kurzfristig auf diese Platte verzichten, also raus damit und weiter gemacht. NAS runterfahren neue HDD entfernen alte HDDs in alter Reihenfolge in Slot 1-x wieder einbauen NAS starten im idealfall: Alle Daten/Volumes/Folder wieder da! Das war auch bei mir mit den drei Platten so. Die vierte habe ich dann wieder über den Speicher Manager beim Verwalten der Raid Gruppe hinzugefügt. Das RAID Repair lief dann einige Stunden im Hintergrund während die NAS soweit schon erreichbar war. Hoffe damit auch mal einen sinnvollen Beitrag geliefert zu haben. Wenn es dem Ein oder Anderen hilft würde es mich freuen..

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.

nein, das geht ootb so nicht, mit viel trickserei an den config dateien kann man das zwar hinbekommen aber da wäre das downgrade der versionsdatei einfacher das mit dem löschen ist im grunde hier beschrieben, man bootet ein recovery linux and stellt das raid1 der system partition her https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/ hier hat auch jemand das downgrade über installation mit dem alten 5.2 loader vorgeschalgen, ist im grunde nicht viel anders als das mit dem migrieren auf die 3617, man nimmt halt nur den 5.2 usbloader und istalliert dsm 5.2 auf die system partition(en)

das mit der 10s reparatur ist beim bootloader, wenn da etwas angepasst werden muss (zu alter loader auf usb gegenüber der platte mit neuerem system, dann wird der loader von derplatte auf den stick geschrieben und neu gebootet) das eine platte aus dem raid "fällt" kann schon passieren wenn man einmal ohne diese platte startet dann ist das raid nicht mehr synchron und die platte muss neu intergiert werden, das dauer dann etwas, das raid ist ja auch ohne die 3. platte funktionsfähig und wird beschrieben, imho kennt das raid kein transaktionslog (das man nutzen könnte um alles nach transaktion x nachzuholen) so das alle sektoren der platte überprüft/synchronisiert werden müssen (bzw. eher die clustergröße im raid die mit prüfsummen geschützt ist)

the driver in the v4.8 extra.lzma is not recent anymore, maybe a newer driver helps i've compiled aquantia x2.0.10.0 driver for 3615 so you can test that v4.9_test version in the following link (only new compared to 4.8 ist the aquantia driver) http://s000.tinyupload.com/?file_id=05787267927444477854

Les informations CPU sont codées en dur dans DSM, donc quel que soit le CPU, les infos ne changerons pas. En revanche, tes 6 coeurs sont normalement pris en compte. Le meilleur moyen de savoir, c'est d'installer Virtual Machine Manager : tu verra directement le nombre de coeur que tu peux atribuer aux machines virtuelles ! Ou alors en SSH avec je ne sais plus quelle ligne de commande.... Pour ma part, j'ai un XEON E3-1270V3, affiché 4 dans DSM, et je peux attribuer 8 cœurs sur mes VM

Хорошо работают, если понимаете что делаете. В принципе роутер/фаервол PFSense отлично работает и на виртуалке т.к. требования к "железу" весьма скромные.

Поставил 6.2 с загрузчиком 1.03а2 (DS918+) на Asrock j4105-itx. Просто вставил подготовленную флешку и все сразу завелось. Что имеем в итоге сразу после чистой установки: - HW транскодинга нет (-sh: /dev/dri#: No such file or directory , серийник валидный, кодеки активированы, Квикконнект работает) -гибернация не работает, что то шевелит хард каждые 10-30 сек -не работают встроенные часы (при отключенной корректировке времени по интернету - в логе каждые 10 минут ругается что не может сам считать время) -скорость USB не проверял, по LAN неадекватных просадок не заметил, но общий уровень чтение\запись в районе 70 Мбайт. Вставил новый диск, флешку с 1.02b и 6.1.7 DS916+. Чистая установка без плясок с бубном: - HW транскодинга нет (-sh: /dev/dri#: No such file or directory , серийник валидный от 916, кодеки активированы, Квикконнект работает) -гибернация работает, НО продолжается ровно 9-11 секунд (время простоя 600 + 9-11 сек) -встроенные часы работают (в логе нет ошибок) -скорость не проверял Эксперимента ради создал 3 комплект: 1.02b и 6.1.7 DS3615xs - HW транскодинга нет (и не может быть на этом железе) -гибернация работает, (хард спит по 2-3 часа) -встроенные часы работают (в логе нет ошибок) -скорость LAN равна 1гигабиту - упирается в 112-115 Мбайт как при чтении так и при записи. Прогонял тест Geekbench 4 через докер, сложилось ощущение что на 6.1.7 процессор работает только на базовой частоте 1,50 GHz , а на 6.2 - активируется максимальная частота 2,50 GHz. 918 - http://browser.geekbench.com/v4/cpu/9140196 916- http://browser.geekbench.com/v4/cpu/9140049 3615- http://browser.geekbench.com/v4/cpu/9166203 Вопрос, какой командой можно проверить на какой частоте работает процессор?

Well, you have to download the old loader version, with the .vmdk file (if you cant find it, create a .vmdk file with this in it " # Disk DescriptorFile version=1 CID=6ccf51e5 parentCID=ffffffff isNativeSnapshot="no" createType="vmfs" # Extent description RW 102400 VMFS "synoboot.img" 0 # The Disk Data Base #DDB ddb.adapterType = "lsilogic" ddb.deletable = "true" ddb.encoding = "UTF-8" ddb.longContentID = "7e24a756b77e33e24ac940cc6ccf51e5" ddb.thinProvisioned = "1" ddb.uuid = "60 00 C2 9a ee da ca 33-df 5e 04 3f 80 55 f9 62" ddb.virtualHWVersion = "10" ddb.uuid.image="4b2539af-3baa-4d1d-9b66-767de4b8210d" ddb.uuid.modification="f4047fa2-67cb-456a-bbb0-066f2c69a462" ddb.uuid.parent="00000000-0000-0000-0000-000000000000" ddb.uuid.parentmodification="00000000-0000-0000-0000-000000000000" ddb.geometry.cylinders="101" ddb.geometry.heads="16" ddb.geometry.sectors="63" ddb.geometry.biosCylinders="101" ddb.geometry.biosHeads="16" ddb.geometry.biosSectors="63" "in it and the new loader. Now rename the new 1.03a2 file to synoboot.img and place both files in the same directory. after this, open virtualbox and create a new virtual machine. Select Linux version 2.6/3.x/4.x (64 bit) and and select "no harddrive". Then ok. Right click on the new virtual machine and edit it. First go to harddrives and delete everything that is in there. Click the first button on the bottom to create a new controller and pick sata (that worked for me). The click on the second button of you new controller and add a harddrive, but pick "existing one" and now select your .vmdk file. After this, click again on the second button of you controlle and add a harddrive but ths time, create a new one, minimum about 15gb as far as i know. After this, change to the network settings tab and anc change from "NAT" to "network bridge" (this could be changed, but this worked for me) Open the advanced settings and make absolutly sure, that you have this "001132112233" as you mac adress. For better compatibility you should choose "Promiscous mode: for all vms and the host" and for the adaptertype "Intel PRO/1000MT Desktop (82540EM)" Everything should be fine now and you can start you virtual machine, after about 5 minutes max you should be able to find you NAS with find.synology.com or with the synology assistant. Find.synology.com sometimes was not able to find it, but synology assistant was always able to find it. I hope this helps you

DSM: 6.1.7-15284 Update2 - результат обновления: УСПЕШНЫЙ - модель DSM: DS3615xs - версия DSM до обновления: DSM: 6.1.7-15284 Update1 - версия и модель загрузчика: Jun's Loader v1.02b - тип установки DSM: VM - платформа: VMWare ESXi 6.5 - дополнительные комментарии: требуется перезагрузка

i've redone the mpt2sas driver and got rid of the this message tested hot plugging, created a volume and unplugging a disk from the LSI 9211-8i, at least with the driver as its now it worked (did not tested it with the driver in the 0.2 extra.lzma) with the new driver that does not work the synology way, diskmanager does not show the correct values but "smartctl" does show correct values when called on the command line so the driver mpt2sas is working properly, only dsm fails to use the information, i guess synology has its ways to filter and the information gets lost on the way (with 918+ its not as with the business units 3615/3617 those come natively with lsi/sas support) for now its not a driver thing, smart does work as seen in the output, maybe some else might have the time to look into this to see if it can be fixed by addind some scripts or programs from the business units or adapt things from there i've test this too with the driver that will be in extra.lzma 0.3 (will be later this evening online), it did work without problems connected a disk already installed on a ahci port with dsm as sigle disk to the lsi, came up without problem emptied a disk and connected it to the lsi (2 port ahci + 8 port lsi) as disk 8 and booted up the the usb flash drive, installed to the disk without problems and booted after installed edit: looks like the reboot only happens when more then a system/swap partition is on the disk, reproduced the reboot with a SHR volume on the 2nd disk also when reconnecting the disk is not recognized as formerly used disk, only after reboot the system partition and SHR partiton was recognised so replugging is also not really working hotplugging should be avoided when using the mpt2sas driver so the driver is in basic working condition from my point of view (cant see how to improve it further) won't get better as i cant find out why the newer driver mpt3sas (that also support mpt2sas controllers) is not working - see my post above and the spoiler part with the log if someone has a idea whats wrong drop a comment here (i've tried mpt3sas from the kernel and v23 from external source, both have the same crash)

Поиск чтоль забанили? В соседней ветке

ich wüßte da noch eine abkürzung, dabei gehen nicht mal alle settings drauf da "migriert" wird wenn man eine 3615 hat die auf dsm 6.2 gekommen ist kann man einen 1.02b boot stick für 3617 erzeugen, die 3617 installieren (ist ja kein downgrade da man auf eine andere dsm version migriert, da spilet die installierte versionsnummer keine rolle), nach der installtion erzeugt man den stick für 3615 neu vom 1.02 image file (der alte stick hat ja bereits beim update den neuen kernel bekommen, weshalb man auch immer beim booten im synology assistant die neue version angezeigt bekomme), im synology assistant sollte jetzt wieder die alte (erste) 6.1 versionsnummer zu sehen sein, dsm 6.1.x (kann gleich 6.1.7 sein) *.pat file für 3615 installiren und das war's beim migrieren wird nur die system partiton neu geschrieben und dabei werden soweit möglich auch die settings übernommen, die daten partiton mi den eigenen daten wird dabei nicht gelöscht, da 3615 und 3617 fast gleich sind wird da so zielich alles an einstellungen mit übernommen wichtig ist das man immer wenn man den usb stick vom image file neu schreibt man dann auch vid/pid anpassen muss damit das geschribene image zum usb stick passt hat auch den vorteil man muss nichts rumstecken oder das gehäuse öffnen, nur 2 mal den usb stick neu schreben und an die box stecken

I just updated to the plex pass version from Plex.tv and when I click ADVANCED I now see the hardware transcoding option... USING DS3615XS

Hi all, Managed to get this working now! Thanks for those who read the post. I have created a brief guide below that may help someone else, my problem was that the http://find.synology.com/ would not find my TerraMaster. Once I went to the web address of the TerraMaster (previously reserved on my router) I was able to continue the installation. Good luck to those who are trying to do this. Installing XPenology on to TerraMaster F4-220.pdf

VirtualBox 5.0.40 package updated for the 6.1.7 version. Enjoy! VirtualBox_x64_5.0.40-115130-1_6.1.7.spk

9 - How do I reset DSM remotely without loosing my data? Contrary to a real Synology box, on an XPEnology box, reseting DSM from the Control Panel > Update & Restore > Reset will not only reset settings but ERASE ALL USER DATA. Therefore this method should not be used if you intend to preserve your data. The only way your data would be safe is if you had a real Synology box. Then you would also need to press the reset button located at the back of the box twice within a determined time frame to have your data preserved. More info here: https://www.synology.com/en-us/knowledgebase/DSM/tutorial/General/How_to_reset_your_Synology_NAS However there is a way to reset your XPEnology box without loosing data. DSM includes a tool to do so and it's called synodsdefault. Access your machine via ssh and type de following: sudo /usr/syno/sbin/synodsdefault This will output the following options: Synology DS Default Reset Util. Usage: synodsdefault --reset-config Reset DSM configs. --reinstall Reset to reinstall DSM. --factory-default Reset to brand new DSM. Include remove all data volumes. --help Show this help. Use the --reset-config or the --reinstall options to reset/reinstall DSM. The first one will only reset the settings while the second one will reinstall DSM. The third option --factory-default, you guessed it, will wipe clean you installation and all your data will also be erased so avoid that one if your point is to preserve your data.

well dsm/xpenology is a appliance and in some points restricted, imho best alternative when it comes to plugins/docker (ZFS based is not a real comparsion here, dsm does not have this) is open media vault (omv), looks nice and it still my fallback if dsm is not going to work for me, it can use the lvm/mdadm raids created from synology so you can boot up ant instantly use your data raid (i tested this with a raid6 from dsm, not tested with SHR raids) you can still buy a used 8port controller lot of people use sas2008/sas2108/sas2208/sas2308 based controllers flashed to it-firmware (it in this case means Initiator Target) there a tons of cheap ones from dell (perc h200), ibm, fujitsu, hp (Hxxx series) sas3004/sas3008/sas3108 will work too and all of them are very reliable also working with 6.1, 8-port and not too expansive Marvell 88SE648x based like the HighPoint RocketRAID 2680 Marvell 88SE948x based like the HighPoint RocketRAID 2720 Adaptec HBA 1000-8i, (PMC chip based?) a save bet are ahci compatible controllers, often used are marvell based ones (cheap) but they usualy come with 4 ports, dont know if there is a "real" 4+4 port marvel based controller (two 4 ports chips together linked by a pci-e bridge chip) they are possible (i think) but i cant remember if i ever saw one, i guess the costs for such tandem will be bigger or equal as the bigger marvel chips like 88SE9485

if the card is a normal 4 port controller and a 5 port multiplex chip in one card then you will see 4 sata ports (if multiplex does not work) and if multiplex does work you will have 3 ports plus 5 pots from the one with the multiplex behind it (88SM9705 is a 1to5 multiplex chip) so it sums up to 3+5=8 with multiplex and its just 4 without kind of the same as when you connect a external 1to5 multiplex to a eSATA port of a original synology (that port can do multiplex but only with synology hardware because of driver limitation) - i know because i've tried this with a 5-port enclosure years ago, i this case you only see the first disk so in your case the 4th port is more the 1st port of the multiplexer but thats just technical detail of no importance if you remove the heatspreader you will find a 88SE9215 (the usual 4 port card chip) and 88SM9705 i guess

Спасибо за совет Привык я к видео стэйшн просто

All the "missing" bits are already in loaders, so anyone can "find" them and reconfigure scripts to build boot image. In the next few days I will build one for DS916+ with minimal drivers for my board (MSI N3150I ECO), and with enabled Intel P-State driver.