rdonovan

Thank you very much for your help, tried to edit the armbianEnv.txt but the system doesn't boot...I guess my HHD partition has been corrupted for good... :-\

So basically I should just edit armbianEnv.txt from rootdev=UUID=64383220-a185-4473-b3ab-ef1612d4d94c to rootdev=/dev/sda2 and then just reboot? Or I still need to recompile boot.scr? rootdev parameter can be set using the dev path or the UUID method is mandatory? Thanks again!

Hi, I have a question regarding the new Banana Pi (A20) boot script created in Armbian 5.25. Many months ago I switched my roots from the SDCard to the sata disk using the sata-nand-install script, after that I used to switch between SD and HDD and vice versa, mostly for maintenance operations on the HDD (sometime the system gets corrupted and I have to restore the HDD partition with e2fsck from the SD). Until Armbian 5.20 I used to edit the boot.cmd file pointing to the desired root device, recompile the boot.scr and then the system were loaded from the desired partition. Now with Armbian 5.25 I'm not sure which file I have to edit to do the same, boot.cmd or ArmbianEnv.txt? I've tried both but the boot didn't seem to be right and I don't understand if it's because my HDD is dead or because I badly edited the new boot script. Could someone help me please? Thanks!

We can close this, Like an Idiot I've broke my system while trying to switch kernel so I've reinstalled Xenial which I found I like more than Jessie. I've already set up the system as before and it seems to work fine so far. Likely the problem was related to some mess I did or an upgrade gone wrong. Thanks for the support.

No one else having this problem? It's driving me nuts. Could also be releated to the upgrade of Python which has come with Armbian 5.20? The problem seems related only to some Python Processes. Thanks. Giulio.

Hi guys, I'm running Armbian on my BananaPi for almost a year now and it has always run seamlessly, since the latest upgrade to Arabian 5.20 (Kernel 4.7.3) I've started to experience problems with the stability of the daemons. Monit is doing an hard job lately restarting many times a day almost all the processes I'm running as damons, the most affected by the Killing are Python 2.7 (running Sickrage) and Deluge daemon. In particular Deluge being killed so many times a day is quite annoying since I have to recheck the integrity of many files almost every time I get the service up again. I didn't install any additional software that could have created this instability apart the new version of Armbian so I'm asking: Is there the possibility that the Out Of Memory Killer has become too aggressive on the latest Arabian? Is that a common issue or something I can do to solve? Thanks a lot. Giulio