Leaderboard
Popular Content
Showing content with the highest reputation on 01/26/2022 in all areas
-
1) Yes it's "abandoned" like Juns, but this time it's open source 2) To be honest... If you don't want to read the 144+ pages you should invest into a real Synology that just works. Here there will be dragons (and lots of) 3) Most/all people use this for testing only and it's not as stable as Juns loader 4) If you are happy with Juns loader I recommend you to stay on it, especially if you use it for "production". Redpill is not ready for production. If you have hardware to spare you should look into the amazing TinyCore project to get up and running quickly. Synology will also launch DSM 7.1 sometimes Q1, so the grand question is if that will be supported/stable at all going forward3 points
-
Redpill as in the project isn't gone, but the core developer(s) @ThorGroup is. No, unfortunately there is no additional information information available regarding. Thanks to the developers being awesome and making the project open source anyone can contribute this time. You should not use this project if you depend on future updates or intend to make this a production system/make it available on the Internet. As mentioned before, it's only for testing purposes and that will probably always be the case. I wouldn't recommend running Plex on DSM if you are highly dependent on performance. It's way better on a Linux VM with a later kernel and a GPU in passthrough. Some have also reported DSM 7 to be unstable when stressed, not sure thats only tied to Docker or also the Plex package though. I've never been able to get sleep to work, but honestly it's not recommened either as it most likely will decrease the life expectancy of your drives depending on how often you wake them up. Spinning up/down is what kills most drives, not spinning 24/7. I was also looking into this for a long time, but concluded with spindown being a silly thing unless you are pretty sure that the disks can be spinned down for at least a day at a time, preferable over several days. QuickConnect and face recognition is only working for real devices as it requires a real serial/mac. There are ways to get around those limitations, but at that point I would highly recommend to buy a real Synology. Especially if you want something that just works and doesn't waste energy. They are great devices, low power consumption and rock solid. Without the use of docker the performance is also not that bad given the dated hardware they use. There is no such thing as robust or stable branch. Everything is done in development branches that might break tomorrow, but a good starting point is the config used by TinyCore: https://github.com/pocopico/tinycore-redpill/blob/main/global_config.json You need to play around with SataPortMap in order to get the disk order correct. Havent tried TinyCore much myself, but it has a auto-detect feature that might help you. I also recommend to read through the other link with very easy to understand information on how SataPortMap and DiskIdxMap works.2 points
-
Thank you a lot for your help in this topic, let me check it tomorrow and I will try again if I'm able to install the 6.2.4 version. For the moment I'm interested to keep the tdt usb option.1 point
-
@zahniThe command shows that jq was able to process the files as valid json. Though, their content could be still problematic. If jq throws an error (like it did in your and jarugut's case), then its safe to asume the build is incomplete. I looked at the files jarugut provided. It is a valid json with minor formating issue - nothing that should break the file. First I though the "u2" in the revesion broke the processing logic (rploader recycled most parts of this logic from rphelper), but it does not care for the revision. You could try ` bash -xe rploader.sh bromolow-6.2.4-25556u2 static` and paste the output. It will execute the script in debug mode up to the first error it encounters. I can imagine the problem is originated in an incomplete profile, a typo or a missing comma. update: I found it! is caused by missing "add_extensions": [] in the platform profile. Add it to each profile where it's missing and you will be good. Note: no officialy available version of rp-helper or rp-tool-chain was affected by this. It must have found it's way into rploader.sh from an early beta for rp-helper 0.12 where I had a function to add the extensions provided by the list. I haven't checked if the logic that actualy makes use of the field made it's way over to rploader as well, as the logic was in the Makefile inside the container. Personaly I like rploader way better than rp-helper All the additional bells and whistles realy add an amazing value to the overal experience!1 point
-
@zahni and @jarugutare you sure your json files are not corrupt? Please use this command to check in the tc home folder (the default folder): find . -name "*.json" -not -path "*redpill-load*" -exec bash -c 'jq . < {} > /dev/null && echo "{}: OK" || echo "{}: broken"' \;1 point
-
Ed_co, just check this website: https://xpenology.club/install-dsm-7-on-baremetal-or-vm/ please make sure you check with a spare hdd and usb stick. If you can install dsm 7 on your system then you will know that hardware is supported or not.1 point
-
Open Vm tool is updated add support dsm 7, please check in use https://github.com/NeverEatYellowSwissSnow/synology-dsm-open-vm-tools1 point
-
Hello @apiros There was a dependency problem with the dpkg package that is not present with the pocopico's tool . This dependency was removed which caused the impossibility of generating an image for ds3617xs. However I send an alternative two days ago on the develop branch https://github.com/jimmyGALLAND/redpill-load . You can try and make your feedback1 point
-
It is very easy. Read this small tutorial. https://xpenology.club/install-dsm-7-on-baremetal-or-vm/1 point
-
Yes, that is true, if an extension fails to load correctly it exits with error code 99 which is then misinterpreted as an exit code 99 for DSM init and fails back to install mode. I have updated the 3617xs, bnx2x extension to satisfy the missing symbols. Please retry. As for the VID:PID error, i need to dig into redpill code. @g4sho As for the USBSHIM error, as you can see below comes from the fact that you have used a different device VID:PID that the one you are booting from. https://github.com/RedPill-TTG/redpill-lkm/blob/master/shim/boot_dev/usb_boot_shim.c1 point
-
Virtual or physical ? For virtual you can use sata boot entry while on GRUB For physical, you can run the following prior building the loader. ./rploader.sh identifyusb now1 point
-
hello, the api url change try this (it's working for me) https://your-ip:5001/webapi/auth.cgi?api=SYNO.API.Auth&version=3&method=login&account=admin&passwd=your_admin_password&format= cookie the other url (for activation) not change https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="SERIALNUMBER" regards1 point
-
Thanks for providing information. We will try to reflect it as much as possible in the next version.1 point
-
напишу небольшую инструкцию 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_QY390_10_11" PATCHED_FIRMWARE="TS-X85_20201123-4.5.1.1495" DOWNLOAD_URL="https://download.qnap.com/Storage/TS-X85/" больше ничего трогать нет смысла, если только знаете что делайте, то делайте. В ином случае можно все испортить. - где взять MODEL_TYPE? из поста https://xpenology.com/forum/topic/1003-qnap-как-альтернатива-synology-и-xpenology/?do=findComment&comment=189973 или здесь http://www.92nas.com/forum.php?mod=viewthread&tid=46. Пример: для TS-253B соответствует тип модели QY470_QY570_11_10 его и прописываем. - где взять PATCHED_FIRMWARE? Выбрали модель что понравилась (MODEL_TYPE), заходим на оффсайт https://www.qnap.com (https://www.qnap.ru не вариант) и выбираем закладку "downloads" где выбираем крайнюю версию QTS по ссылке глобал (пример к TS-253B ссылка https://download.qnap.com/Storage/TS-X53B/TS-X53B_20210202-4.5.2.1566.zip) из этой ссылки нам нужна только строчка TS-X53B_20210202-4.5.2.1566 которую мы прописываем в PATCHED_FIRMWARE - где взять DOWNLOAD_URL? Как писал выше, с сайта https://www.qnap.com (пример к TS-253B ссылка https://download.qnap.com/Storage/TS-X53B/TS-X53B_20210202-4.5.2.1566.zip, нам нужно прописать только путь из этой ссылки в виде https://download.qnap.com/Storage/TS-X53B/ ) - перемещаться по строкам - буква w - для редактирования строки - буква i - после окончания редатирования строки - нажать esc - вернуться в начало файла - сочетание клавиш shift + S - закончили редактирование - набираем :wq и жмем enter - чтобы все заработало набираем в строке - sudo ./my_create_qnap_boot и жмем enter далее начинается загрузка и установка выбранного образа qnap. Примечание: делал все на виртуалке (все заработало), т.к. сетевая карта моего девайса не поддерживается. Как подгрузить драйвера для сетевых карт - обсуждали много на форуме: надо компилировать пакет данных и вставлять в образ. Всем удачи!1 point
-
Perfect, as this is ment for developers and not ready you could test all the things you want and help the community out with your test rig. Quickconnect is impossible without a real sn and mac. And even this is not advised by anyone.0 points