Leaderboard

1.This is a shell script that executes several commands at once as described in the "Redpill Tinycore Loader DSM 7.1 Build" guide. To use, you can download and untar it as follows and use it in the /home/tc directory. Helps build DSM 7.1 by managing the PAT file directory required for decryption. ( It currently supports the latest version of the DSM, 7.1.0-42661 update 1 nanopack version. ) Automatically add mac2 to user_config.json file for dual NIC, a feature that TC doesn't have. ( Manual Response Version ) wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/m.sh.gz; tar -zxvf m.sh.gz; ( Auto Answer Version with y ) wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz; tar -zxvf my.sh.gz; Where y is unnecessarily asked, it automatically responds. Usage: ./my.sh <Synology Model Name> <Option> <Option> <Option> Options: noconfig, noclean, manual - noconfig: SKIP automatic detection change processing such as SN/Mac/Vid/Pid/SataPortMap of user_config.json file. - noclean: SKIP the 💊 RedPill LKM/LOAD directory without clearing it with the Clean now command. However, delete the Cache directory and loader.img. - manual: Options for manual extension processing and manual dtc processing in build action (skipping extension auto detection) Please type Synology Model Name after ./my.sh ./my.sh DS918+ ./my.sh DS3617xs ./my.sh DS3615xs ./my.sh DS3622xs+ ./my.sh DVA3221 ./my.sh DS920+ ./my.sh DS1621+ # Update : add noconfig, noclean, manual combination options # 2022.05.06 You can use it like this. ./my.sh DS918+ noconfig noclean manual ----------------------------------------------------------------------------------------------------- 2. Deploy scripts that you can leverage if you need to add a separate ext manually for VM users. It includes the fuction to add exts created by @FOXBI with multiple selections like capture. For the instructions on how to use, you can download and decompress as below and use it in /home/tc directory. ( Auto Answer Version with y ) wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/myv.sh.gz; tar -zxvf myv.sh.gz; The way to use it is existing same as my.sh. Where y is unnecessarily asked, it automatically responds. ---------------------------------------------------------------------------------------- Usage: ./myv.sh <Synology Model Name> <Options> Options: noconfig, noclean, manual - noconfig: SKIP automatic detection change processing such as SN/Mac/Vid/Pid/SataPortMap of user_config.json file. - noclean: SKIP the 💊 RedPill LKM/LOAD directory without clearing it with the Clean now command. However, delete the Cache directory and loader.img. - manual: Options for manual extension processing and manual dtc processing in build action (skipping extension auto detection) Please type Synology Model Name after ./myv.sh ./myv.sh DS918+ ./myv.sh DS3617xs ./myv.sh DS3615xs ./myv.sh DS3622xs+ ./myv.sh DVA3221 ./myv.sh DS920+ ./myv.sh DS1621+ CAUTION) Not all exts correspond to 7.1.0-42661. Please check @pocopico's ext GITHUB in advance and use it. We do not respond to errors caused by unsupported revisions.

Sounds familiar! Except there are a bunch of kids in my house, also watching Emby. 🤣

Yeah my box has 64gig ram and it’s just me at home with a lot of spare time and - plex media to store/watch so in my use case… it’s definitely marginal. But I got the 2x NVMe card cheap / mobo supports bifurcation and the msi drives for extremely cheap it was worth the test.

Yeah, I have 10gb lan to the box - but even in the case the speed benefit is kinda marginal Sent from my iPhone using Tapatalk

I blunted - I reset the bios and the time was reset to 2014 because of this and the certificates did not work.

The dialog between Peter Suh and pocopico was most informative to me. I don't think it's really documented at all. I'm working to improve that now, with this: https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/ and enhancements to the satamap tool, soon a specific device tree tool. Once that is online I'm planning to create some better documentation.

It must be the last controller listed in lspci (top to bottom).

ja das sollte gehen aber bei den zusätzlichen pakten hats di das gleich problem wie mit einer rp-loader version, dsm 7 hat gravierende änderungen beim format der spk und es braucht meist neue 7.x fähige pakete, das solltest du vorher prüfen normalerweise alte platte in die neue orginal syno und den syno assistenden das ding finden lassen, er sollte dann eine migration der 3615 zur 920+ vorschlagen (bei der die daten nicht angetastet werden), pakte müssen nachher noch erneuert werden da einigen nicht mehr starten werden mit dem tinycore loader ist es eigentlich recht überschaubar, bei der alten hardware wäre 3622 das neue zielsystem du kannst ja den bisherigen usb und die platten abziehen und mit einem neuen usb und einer leeren platte ein testinstall versuchen, bist du mit dem ergebnis zufrieden nimmst du den neuen usb mit den alten platten und startest damit, es sollte dann eine migration auf 3622 laufen und wenn die schon vorher weist weelche pakete gehen werden bzw. ein update mit neuen versionen brauchen gäbe es da auch keine überraschungen der rp loader an sich funktioniert schon seit 6 monaten, worum es meist geht ist comfort beim installieren und treiber einbinden und controller erkennen und korrekt einbinden (aber wenn du eine test install machst auf deiner hardware weißt du vorher ob es probleme gibt) man kann sich auch als fallback eine platte oder usb stick mit open media vault bereitlegen von der man alternativ booten kann um (über netzwerk) an seine daten zu kommen, das daten raid der syno ist "nur" lvm2 und mdadm, also normales linux zeug, die omv kann das einbinden und ist recht leicht über webinterface zu konfigurieren (https://xpenology.com/forum/topic/42793-hp-gen8-dsm-623-25426-update-3-failed/?do=findComment&comment=200475)

в сино нет понятия под систему - система храниться на всех дисках разом, делается так - от каждого диска откалывается 2гб под систему, 2 под своп и еще вроде 2 под что то остальное пространство под твои данные - то есть под приложения, под файлы и тд. из остальных свободных мест на дисках и собирается РАЙД или SHR - что бы выберешь. по этому система работает пока в ней есть хоть один исправный диск. Но приложения в случае развала массива слетят.

[Notice] M-SHELL's guide has been registered as a separate topic below. For inquiries about use of M-SHELL or request for improvement, please request it in the new topic below.

1) не надо делать RAID 1 - пусть остаётся SHR, который Synology предлагает по умолчанию. На двух дисках он будет работать точно так же, как RAID 1. Зато при добавлении новых дисков будет уже намного более выгодное увеличение общей ёмкости (см. калькулятор https://www.synology.com/ru-ru/support/RAID_calculator или описание разных RAID) 2) SSD в общий RAID с HDD вообще нет смысла пихать. SSD может иметь смысл как кэш, но это - только если требуются более высокие скорости чтения/записи, чем обеспечивают HDD (и сеть такие скорости тоже обеспечивает).

No, there is no any way to do it with this backups. According to opinions there is no any reason to use DSM 7. 918 version works only with Haswell or newer CPU. Use 3615xs or 3617xs instead.

No it just gives you more control. I can of course add the dts conversion as well. Thanks for the recommendations

Everything related to approval seems to depend on the will of the manager. There was a case where a user who was frustrated because it had not been approved for several days complained to me. I also requested approval of M SHELL's separate guide, but was ultimately rejected. Because the reason is not explained, there is no way to know, and there is no way to know the progress. No response from the manager is expected. That part is a little tedious.

+1

I just posted a tutorial guide with step by step instructions and pictures on how to setup and install on Proxmox. The thread is waiting for approval from the moderators. I actually did it side by side as I wrote it to verify each and every step. And it all worked 100%.. I will post the link, however I dont know how long it will be until its approved.

Usually virtual NICs represent 10Gbe or faster (check the port speed for a clue). This is meaningful if you have a 10Gbe network, or if there are other VMs that can take advantage of the virtual switch internal speed. If you are only running a single VM for the purpose of running DSM, and your physical NIC is 1 Gbe, it doesn't matter.

I dont have a personal experience but users claim that virtio net performance is superior than e1000.

Hold your mouse over the status LED's Temp will pop up Actually holding your mouse over a lot of things shows more info usually. .

The "16" in 616 is invalid. SataPortMap is only one digit with a maximum of "9" This is not good for LSI9201-16i obviously. However, SataPortMap = "1" should probably work for you to use 17 HDD. Specifically, if the last PCI controller (must be actually the highest PCI slot) has >9 ports, you can leave that entry on SataPortMap blank and it should use all the ports. I would advise maxdisks of 24 instead of 36 (internalportcfg must be modified accordingly).