Leaderboard

Popular Content

Showing content with the highest reputation since 05/13/2021 in all areas

  1. So, you guys deserve an update like 3 days ago... but I hate doing updates with bad news so I decided to wait until I have good news I think you're mixing two different checksums here. There's a checksum of the PAT when it's uploaded and unpacked (which can be easily defeated) and there's a custom kernel-level checksum. Thanks! I didn't experiment with DSMv7 as, the last time I checked, it wasn't publicly avaialble and only invited people could access an early preview. Franken-DSM is still on the table as this will give us a newer kernel but since
    17 points
  2. Good to know, thanks! I didn't follow their DSM 7 release cycle closely as storage is definitely not an area where I like to experiment. Since all my real DSM systems are used for production tasks and I cannot make any configuration changes surprisingly (not even running a VDSM) I was waiting until some stable release is published Thanks! ---------------------------------------------------------------------------------------------------------------------------------------------------------------- There's a liar in the room I had
    15 points
  3. I decided to pursue franken-DSM route - newer VDSM kernel (which supports older CPUs!) with DS3617xs OS. Notable Changes Features only in DS: HA (can be fixed, but does anyone use that with xpenology?) Disk compatibility database (this is most likely easily fixable with manual DB update from settings) Drivers only in DS: igb (various Intel Gigabit ethernets) ip_tunnel ixgbe (Intel 82598/82599 10Gb ethernets) leds-lp3943 mpt2sas (LSI HBA) mpt3sas (LSI HBA)
    12 points
  4. Ok, this is gonna be a looooooong post. I spent some time digging around and I'm back. First some responses: To my knowledge the problem is the same as described in the first post - "va not found" (aka the patcher cannot execute the main DSM kernel). It doesn't seem like Synology did anything on purpose, they changed the kernel just enough for the Jun's loader to fail. Synology uses a separate "distro" for VMM. But why do we even need a kexec? VMM boots the kernel directly and just insmod couple of other modules for serial and virtio stuff.
    7 points
  5. After seeing a sea of report for 6.2.4-25554 and 6.2.4-25556 I fired up my test rig and got the same result as for for v7 release: va not found Failed to process header This seems to happen way before the kernel is actually loaded into memory. I compared before & after boot images and not surprisingly the kernel did change. From my limited knowledge of Linux boot process I started poking around and even binwalk doesn't recognize the new image: Scan Time: 2021-05-30 13:01:52 Target File: /mnt/_synoboot-old/zImage MD5 Checksum: e3d859f75819dda05e065c5da
    5 points
  6. Nice findings! Here is the Juns' stuff from loader v1.04. modprobe is kernel module injector, and jun.ko is the module itself. Happy reversing. jun.zip
    5 points
  7. I will say it's more fake-till-you-make-it for me My experience is very limited in this space really. Thank you! That helps immensely! A classical example why different people thinking differently can come up with something great. My whole goal is to actually describe everything and make the knowledge accessible. As of know most of the stuff is not publicly available and seems to be known only by a couple of devs which developed previous loaders. As of now no, I didn't share any repo (except some code snippets to e.g. gen
    4 points
  8. looks like Version 7.0-41882 is RC now, so might might not be that far to a 7.0 release https://www.synology.com/en-global/releaseNote/DSM beside the usual updated information about fixes and features "... DSM 7.0 for FS, SA, XS/XS+, and DVA series models are currently under development and will be available in the next quarter. ..." so it might be that 7.0 release finally is in q3/2021 also EOL for 6.2 seems to be out, might be 6/2023 https://www.reddit.com/r/synology/comments/npwo72/whats_the_plan_for_future_support_for_dsm_6/
    2 points
  9. DSM checks hda1 checksums / sigs upon install. If they fails, dsm will flag it then won’t to do switchroot anymore.
    2 points
  10. i do remember a comment from @Trantorabout missing kernel source for synology's "own" kernel modules related to the old 5.2 custom kernel and that they had to reverse engineer around that bios module and without that stuff a 6.x custom kernel would not be possible i also remember some trouble with the protection (24h) kicking in with loader 1.02a and that loader 1.02a2 fixed it and it was about some bios serial device (just from memory could not find that one)
    2 points
  11. Have your published your work so far anywhere as I would like to have a we look at it and study it to see if I can help with anything. I'm not a developer but I like to challenge myself and look into coding etc from time to time. In the past I have built kernels from source for different android devices so I might be able to help in some way.
    1 point
  12. Very interesting topic! Thank you very much @kiler129 for your work and for sharing with us this knowledge, I am pretty sure it will be very valuable.
    1 point
  13. These are all so similar I am not sure it matters that much. The likelihood of actually saturating a 4x bond with less than say 20 clients is very low. Unless you can nail up a Gbe connection all day, it's not even worth the complexity of setting up a bonded connection.
    1 point
  14. I believe that thread availability would impact throughput in that specific peak scenario.
    1 point
  15. 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.tar) (ch_cpuinfo_en.tar) / (ch_cpuinfo_kr.tar is file for korean) 2. Upl
    1 point
  16. Try and reboot and see if your volume mounts.
    1 point
  17. I realize you are posting in the other thread to try and recover your data. I'm posting on this one to help with some forensic reconstruction and to potentially explain why you cannot get more storage from your SHR based on replacing the 4TB with a 10TB drive. To recap, at some point in your history, you had 4TB and 1TB drives that comprised your SHR. It would appear that you replaced all your 1TB drives with 4TB and that left you the following SHR makeup: Because you had 1TB drives, the 4TB drives were split into two pieces, a 3TB RAID5 and a 1TB RAI
    1 point
  18. afaik you will need a driver in dsm to access a device from docker examples might be dvb devices that need to provide /dev/dvb/... to make dvb application in docker work or plex as docker that still needs /dev/dri/... to work even a zigbee device will need some kind of comport for docker and guess where that com port comes from ... a driver in dsm so there will be less support for other hardware that need special backported drivers for synology's older kernels, i guess some basic stuff that comes with the kernel like the usb com port for a zigbee might still work, but wifi and
    1 point
  19. its not clear if apollo lake can handle encoding 4k hevc 10bit, it states decoding only for 8k https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_encoding so it might only decode properly (up to 8k) and encoding might be off limit and needs gemini lake (as used in x20+ syno units) but the problem for not having "original" with hevc might be the browser only safari seems to support that https://caniuse.com/?search=hevc so it might be normal that you need to transcode all hevc to h.264 to see it in videostations webinterface as the browser y
    1 point
  20. This is not necessary if you have specified the correct vid/pid of usb flash drive inside grub.cfg Here is the kexec from Jun's loader v1.04b You can tinker with it. To invoke, just grab any x86-64 VM and run: ./kexec -d -z --args-linux ./zImage --type=bzimage64 --reuse-cmdline --initrd=./rd.gz zImage and rd.gz are from syno fw. Test both 6.2.3 and 6.2.4/7.0 beta (DS918+) sets. With 6.2.3 you'll get a pretty big load log then KP (normal behavior) but with 6.2.4/7.0 you'll get the <va not found> error and immediate return. Now you can investigate
    1 point
  21. https://xpenology.com/forum/applications/core/interface/file/attachment.php?id=10186
    1 point
  22. Да завсегда на здоровье ......)))
    1 point
  23. Если мне память не изменяет, то это сервак на Xeon....... Если так, то вполне возможно поставить последнюю версию 6.2.3. Версию 6.2.4 не ставить, не обновляться 6.2.3 новая, но уже вдоль и поперёк проверенная ))) Вот вам файлы: https://archive.synology.com/download/Os/DSM/6.2.3-25426 Вот вам загрузчики: https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg!7AoyySoS
    1 point
  24. You could verify if php 7.4 is installed properly by creating a phpinfo.php file in the /yourvolume/web/ folder, containing: <?php phpinfo(); ?> Then access it in a web browser by typing http://yournasip/phpinfo.php imagick should be listed with other activated extensions.
    1 point
  25. 1. Актуальная версия - DSM 6.2.3-25426 Update 3. 2. Первые две - по большому счёту без разницы, с переходом на DS916 насколько помню стоит заморачиваться только если нужен аппаратный транскодинг (и железо его поддерживает). 3. Смотря что иметь в виду под "системным диском". Раздел с системой зеркалирутся на все внутренние диски (ну на первые 5 из них - точно). На первый диск по умолчанию ставится дополнительный софт. Сам отключать часть дисков на момент обновления не пробовал, у меня их не так много. Может кто-то ещё подскажет. 4. Вроде так: делаешь бэкап настроек системы, выклю
    1 point
  26. Nothing from haveibeenpwned / dashlane Will change to be on the safe side though Standard reminder to never reuse passwords or derivatives of
    1 point
  27. En el MAC si ambas tarjetas de red están en el mismo segmento (p.ej. 192.168.1.0/24) va a ser difícil que le puedas especificar por donde deben salir las peticiones a según que IP de la misma subred. Yo utilizaría otro enfoque, a la red de 1gb por ejemplo la dejaría con la subred que tengas para acceder a Internet (supongamos 192.168.1.0), y a la de 10gb la pondría en otra subred (192.168.10.0). Cuando quieras acceder a través del máximo ancho de banda utilizarías la IP de la segunda subred y por tanto accederá con la tarjeta de esa subred. Y cuando accedas a la IP (normal de la pr
    1 point
  28. It‘s not the username AND password in combination but only the password itself which has been leaked. Even generated passwords can be found in those databases.
    1 point
  29. https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/#comments
    1 point
  30. Поиграться с заменой extra.lzma в загрузчике. 6.2.4 можете даже не пробовать, крайняя работающая 6.2.3.
    1 point
  31. While reading Important Upgrade Notes: I found this : USB devices (Wi-Fi dongle, Bluetooth dongle, 3G/4G dongle, USB DAC/speaker, and DTV dongle) are no longer supported. If your Synology NAS is currently connected via a wireless dongle, it will be disconnected after the update. Could this be the cause that we can't update from DSM 6.2.3-25426 and above due to the update breaking all USB devices, so that means the Loader will not load ! Hmmmm What do you think ?
    1 point
  32. Less than a gig That's normal behavior on windows machine. If you need to reformat, open command prompt type diskpart listdisk select disk X attributes disk clear readonly clean create partition primary select partition 1 active format fs=ntfs label=new assign That'll get it back and readable by windows. Can reformat and image over as needed
    1 point
  33. Перенес работающую систему на новую материнку - Успешно. Работало на Z87X-UD5H перенеслось на X10SRA-F - DSM 6.2.3-25426 Update 3 - доп модули не понадобились. В биос выбрано Legacy Отличная материнка так как в биосе можно вобще встроенные порты отключить и работать только на LSI USB порты работают отлично, для флешки использовал отдельный контроллер USB, система с него грузиться но вот Syno его не видит.
    1 point
  34. Outcome of the update: FAILED - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver N54L - Notes: Loader appears to boot normally, but there is no response to PING or find.synology. Rollback to previous DSM version was successful, thankfully!
    1 point
  35. @Omar: Relax. I have overlooked that. Sorry.
    1 point
  36. Планировщик задач->Создать->Запланированная задача->Скрипт заданный пользователем Основные: название: synoindex -R all права: root Расписание: любое Настройки задач : Выполнить команду Скрипт заданный пользователем: synoindex -R all
    1 point
  37. Установка и настройка DSM на основе версии 6.2.3 Ну вот, муки поиска позади и вы пришли к эпохальному решению создать сервер на основе Хрени.....)))) Надеюсь, что подошли к этому шагу с долей познаний и оценили свои возможности. Данный мануал является общим, без акцента на частные настройки и особенности применяемого вами железа, такие как настройки БИОС_а и хардово-софтовые нюансы вашего железа. Процедура описана на основе последней возможной (на данный момент) для установки версии DSM. Но она применима и на ранние версии DSM 6 . Более древние уже не помню )))
    1 point
  38. El usb no es em instalador. Es el boot de arranque, de modo q cada vez que arranques el equipo debe estar el usb stick insertado... una ez arrancado se podria expulsar, si se quieres, pero para un reinicio debes volver a insertarlo... lo mas comodo es si la placa tiene un usb inteeno, colocar alli el usb stick dentro de la caja, q ni se ve, ni molesta.... El sistema DSM esta instalado en todos los discos que tengas en una pequeña partición de poco mas de 2 Gbytes... Enviado desde mi iPhone utilizando Tapatalk
    1 point
  39. Good afternoon all. I've finally got round to updating both the website and PowerShell scripts. Both code improvements and new features. Website Update and Improvements. The website now hosts a 'SETTINGS' page, in which certain aspects can be controlled. Hard Drive order can now be set from small to large, large to small, Raw Device Mapping Naming convention, Controller Location, and Hard Drive Number. An option to hide Removed Drives (great for when you upgrade drives) Alter how many plot points there are on your temperature graph.
    1 point
  40. I am not trying to be rude also but this question was answered so many times already in different posts. There is no road map and this forum does not have a "development" team to work on loaders but very experienced members for troubleshooting. Is there a future? No one knows if this is the end of XPEnology or not. This is up to Jun or any other person with coding skills... As @flyride said on another post with similar question. If he was Jun, he would not spend his time creating a new boot loader just to support this last update. DSM 6 is at the end and the
    1 point
  41. @xReppa: you opened samba port to the world and you're surprised with the attack? Only safe way to share samba over internet is through Virtual LAN like ZerotierOne. There is Zerotier client for most of devices including DSM and any linux/android/windows etc. So you just need to register on their webpage, create virtual network, share network ID with clients and when they join you just accept them in your admin console. All traffic is encrypted and safe. Apart of that, it's good to separate upload section from download section. All downloads should be read-only for all external clien
    1 point
  42. I've created an Ansible Playbook for creating an Xpenology USB. https://github.com/stevenhrabok/ansible-xpenology-usb Currently it's only written for Mac OSX. In future I may add the ability to create USB Devices in Linux if there is interest in using the tool. I wrote this to help automate the workflow and make the USB drive creation process more consistent. It also helps avoid forgetting a steps in the process. Features: Prompts for information serial number - changed in grub.cfg nic 1 mac address - changed in grub.cfg
    1 point
  43. Just want to confirm that image work with 6.2.3-25426 and ds3615xs. After this we need to apply patch and after that could successfully update to 6.2.3-25426 Update 3. Tested on VmWare Workstation.
    1 point
  44. напишу небольшую инструкцию 1. скачиваем образ https://mega.nz/folder/LJ4wyaDY#MxOC2UgNqC-Y6gQXu-IUFA 2. при помощи софта Win32 Disk Imager записываем образ на флэшку 3. стартуем с флэшки (выставляем в биосе первой флэшку) 4. как загрузится графический интерфейс нажимаем буковку "a" - стартует OS Tinycore, по интерфейсу напоминает облегченный MacOS. 5. находим кнопку "terminal" (справа внизу) и жамкаем на нее 6. в открывшемся окне набираем sudo su и жмем enter 7. в следующей строчке вводим vi ./my_create_qnap_boot далее жмем enter 8. редактируем строчки MODEL_TYPE="QY380_
    1 point
  45. Adding "-it --entrypoint /bin/bash" makes the containers run "/bin/bash" instead of default "/usr/bin/vm-startup" (define in Dockerfile). This gives you access to the command line in the uxora/xpenology container and it's in there you can find "/usr/bin/vm-startup"! Maybe once you get command line access to the containers, I dont know ... try to find out what the issue by running for exemple: - $ iptables -A POSTROUTING -t mangle -p udp --dport bootpc -j CHECKSUM --checksum-fill - $ /usr/bin/vm-startup If you don't really make an effort to really find out, I cannot be much
    1 point
  46. Установка такая же, как и на другие мамки, за редким исключением. Вот вам тема про транскодинг и с чем его жуют..... Особые отношения только за большие деньги....))) Шутка Вот вам загрузчики: https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg!7AoyySoS Если нужен транскодинг, то 1.04. Если нет, то 1.03 Вот вам файлы: https://archive.synology.com/download/DSM/release/6.2.3/25426/ Если необходим транскодинг, то вам 918+ Если в нём нет нужды, то советую 3616, наиболее универсальная версия. Ваша мамка поддерживает транскодинг (если не ошиба
    1 point
  47. Found the issue for me. I hadn't thought that the website you need for the authorisation and verification to work (writes a file to your webspace/.well-known/acme-challenge/) is from the normal web service (nginx or apache2) running via Web Station which of course responds on ports 80 and 443. My initial redirecting and port forwarding from my public WAN to private LAN was forwarding to ports 5000 and 5001 for DSM. Whilst I need this to access DSM remotely, I actually need it to forward to the standard 80 and 443 for the certificate generation.
    1 point
  48. Да, все получилось, спасибо за наводку. Немного помучался т.к на матплате ASUS PX79 WS два разных сетевых интерфейса и с одним из них DSM никак не хотел работать даже с подкладыванием доп. драйверов. На втором интерфейсе все работает хорошо. Intel 82574L - не работает Intel 82579V - работает
    1 point
  49. Вставлю свои три копейки. Дано: TV 55" 4К, Internet 8 Мб (увы в регионах такая скорость). Вопрос: как смотреть 4К контент при такой скорости? Двух часовой фильм 30+ ГБ, скорость закачки 2-3 ГБ/Час Вот и приходится ставить на закачку с последующим просмотром.
    1 point