Leaderboard

And, there is one more great thing I gained from this two-week study. 56 ~ 57% connected to disk damage error 3 FAT boot partitions on USB /dev/synoboot1, /dev/synoboot2, /dev/synoboot3 If it cannot be mounted boot-wait (tcrp) and automount (rr) complement this. There are addons such as: If these three boot partitions are not mounted properly, they cannot be created. There is a function that forces this. This is a method I researched and came up with. Force create the above three nodes with the /bin/mknod command. Because this forcefully created node is not a stable node, The 56-57% disk damage error still did not go away. However, as a result of this function, there is no need to forcibly fake these nodes. It seems to be more stable to connect to a USB device directly using "ln -s" in the form of a direct symbolic link. I will discuss this improvement plan with wjz304 and spread it to rr to improve it into a more stable addon.

I should have tried it with a native hard drive from the beginning. I ended up wasting several days by testing in the VMWARE FUSION virtual environment for a more convenient test. The main purpose of Redpill bootloader hard disk porting is to port the bootloader to the hard disk without using a USB stick. In a virtual environment, it is sufficient to use a virtual Sata disk as a boot loader anyway, so the function of porting it to a disk seems unnecessary. Anyway, due to the nature of Redfill lkm, it synoboots the moment a Sata SSD is seen. A healthy disk disappears. Only those who have at least two BASIC or JOB type disks in Native can use it. I will improve the functionality, distribute it soon, and also upload a user guide.

Hi, Adding all active repositories is now simpler with Synopackage Proxy Repository. You may add one link to Package Center: https://synopackage.com/repository/spk/All and Synopackage will query for you all active repositories under the hood and gives you combined response ;) More info at: https://synopackage.com/repository I plan to work on personalized repositories, so user could choose which repository to include in the link (no estimation date for now). For now there are two choices: All & SynopackageChoice.

And what was the solution?

Сам отвечу на свой вопрос. Забегая чуть вперед скажу, что испробовал на себе, все заработало и проблем я не заметил. Что я делал: 1) Остановил приложение которое хотел перенести. 2) Разрешил доступ по SSH и зашел через WinSCP 3) Скопировал директорию /volume1/@appstore/xxx в директорию /volume3/@appstore/xxx где xxx - это папка с нужным пакетом 4) Далее пошел в /var/packages/xxx и отредактировал линк на директорию /target 5) Вернулся в веб-морду и нажал кнопку "Refresh" в диспетчере пакетов, после этого у меня приложение поменяло номер тома на нужный. 6) Запустил приложение. Проверил что все работает. 7) Возрадовался! Такой трюк я проделал с Cloud Station, Surveillance Station и Photo Station