TRS-80

Imagine getting this sort of honesty and transparency from some mass market mfr. of NAS (or almost anything nowadays). I don't think so!

It's not that you "can't" but rather, tracking that down and finding out exactly what and where went wrong may take longer and be more effort than just sort of starting anew, blowing out the whole OS and flashing fresh, etc. The decision will weigh on just how heavily configured your old setup is, and how much effort that is to reproduce on the new OS. I ran in to, not exactly the same issue as you, recently, however it was a similar sort of decision to make (i.e., whether or not to re-flash OS again "from scratch"). In the end, I was able to get it working, luckily (as I had quite some config on that old Cubietruck!). However the experience made me think more in general about how I organize my "services" which are running on top of base Armbian. Now in my case I'm just a home gamer, running few services like an XMPP server for friends and family, etc. In my case I start to play with containers, because I think that is a solution that will work for my needs while isolating the "services" from the underlying OS. Then I can blow out the whole OS with the latest from scratch and it's no problem. Such is the nature of these devices and the hardware support (well, at least on the relatively limited resources a community project such as Armbian has to work with, anyway). I have no idea what "your project" is or if such a solution might work for you. And those sort of questions are slightly outside the scope of the Armbian project to be honest (I just have a personal interest in this area, and thus am sharing my thoughts / experience). However another path may be to hire @Igor and/or some of project devs to sort out whatever issue you are having, especially if this is some commercial project and you can afford to do so (I have no idea, just throwing it out there). Another solution, if you don't like the idea of containers (or they are not appropriate for whatever reason), may be to come up with some sort of Ansible type thing, or even a Makefile to provision "your project" on top of a base install of Armbian. There are many solutions, which is best depends a great deal on exactly what "your project" really is...

OK, this pretty much eliminate such concerns, good work. Reading more carefully now your last post: ... made me go back and read OP (again) more closely, and I notice: OK, so some times things are updated in new Armbian versions, including perhaps even bootloaders, naming conventions, etc. So perhaps some of those "other" things been updated in the meantime. This may be why "vanilla" Armbian works fine, but whatever you have just keep copying forward, does not work any longer?

And even those, the first run are sold out already! I am pretty sure they will be doing another... I am also interested, I'm sure others, too. An ECC version is also supposed to be coming in 2021.

Anything is appreciated. I started working on docs recently, it's a little bit of set up with git and Markdown, maybe not for everybody. Even if you notice something, make a post about or send me PM. Newer people often think they can't contribute anything valuable but that's not true. Newer people have the unique perspective of being new. And thus if things are unclear (docs, etc.) please say so, as you are "target market" (for lack of better term) for these docs. Not the devs who already know much more. In that vein, you already gave me some good feedback which is what we need to make docs better toward new users. So, if you have any more just make note, send me a note, start a new thread, come to IRC or whatever. This goes for everybody!

This is Armbian? I don't use Ubuntu, I am Debian user, so those sources look weird to me. But you can get both Debian and Ubuntu flavors of Armbian, so, not sure...

Welcome aboard, newfren!

You installed Debian? Or Armbian?

Yes that would give you every third day at 01:00, with the caveat that you may get a slightly shorter interval at the end of the month, depending on how many days are in that month (which does not really matter for your purposes). Maybe sure and check the cron tab is working first (do one like 5 min from now). Also make sure all your services come back up properly when you test. And remember, this is a work around. Continue to diagnose the original issue (memory leak) as time and energy allow.

I meant plain old cron. Not very elegant, but not terrible, either, as a temporary workaround, IMO. I don't know anything about watchdogs (outside understanding the general concept). Maybe someone else can speak to that.

Ha! SteeMan type faster than me. I agree with all that was said in both posts above, and strongly urge you to consider advice of experienced forum members and devs (which JMCC is). Otherwise you may end up having a bad time. In addition, OP did not explicitly state one way or the other if they actually even care about watching TV or not (even though that might be assumed from wanting a TV box)? If you don't care about TV (or maybe even if you do!) I can only highly recommend something from Armbian official Supported Devices list. There you will have a much better time, in general, but specifically if you are trying to run any sort of "server." I run a couple "servers" and they have been flawless for years but I stick to Recommended Devices and Armbian Stable only.

I will just interject to say that sdcard errors are so common that verification needs to be done first in order to be eliminated before proceeding to other troubleshooting steps. So thanks for taking that necessary step. Now if anyone knowledgeable read this, they are more likely to respond. For example, only after writing above paragraph do I decide to actually go and read OP. And now I think possibly the card might be starting to go out. How old is it and how much use has it seen? As you can see, we are right back to suspecting sdcard again (it is very, very common).

@Chris Bognar, Thanks for reporting back. There are quite a number of optimizations that Armbian / Kobol do to these boards, as hardware wise they are not exactly like the "normal" x86 you may be used to. I would recommend leaving them as is for the most part, unless you really know what you are doing. Of course, the whole point of GNU/Linux is to tinker though, so... Maybe get another cheap board for such tinkering / learning, instead of your (home?) "production" NAS. Just a thought! Cheers!

Maybe do some scheduled reboot every night (or two, or whatever you feel is appropriate) as a temporary work-around until the memory leak is found. Because it might take them a while to figure that out (and they will likely also need your help/feedback). If scheduled in the middle of the night (assuming everything comes back up OK) you probably would not even notice it?

Thanks, I been working on docs, maybe I add link at bottom as "additional resources."

I came in part way, forgive me if this is incorrect advice. But there are some generalized instructions here which have been updated somewhat recently, maybe helpful for you?

And yet, none of that was helpful in getting your device to work, was it? I was trying to tell you, these little devices are a whole another kettle of fish. But you don't seem to want to listen. There are quite a lot of quite good docs at https://docs.armbian.com. Judging from some of the things you have said, I am not sure you have read (or perhaps just not absorbed) them. First and foremost, your device is not even supported.[0] And therefore has nothing to do with "this project" but rather the kindness of some community members (mostly balbes150) who decide to create and release such "community" (i.e., not officially supported) images. If your time is worth so much, why are you picking random devices out from recycling and trying to get them to work? Do you think you are the only one who's time is valuable? What about all the people who try and help you, the devs, all others involved? What about their time? And yet it's not enough for you. I am not sure what you expect but from my point of view at the moment, it seems quite entitled. [0] I did not read everything, only back far enough to see you mention something about downloading Aml-s812 and we are in TV box section, after all.

If you learned anything at all, the time was not wasted. I understand your frustration. We have all been there. Respectfully I would submit to you that those who make it look easy ("toothpick guy" for instance), are likely on the far side of much more than 30 hours of tinkering. Perhaps even up to a lifetime worth. If you have an interest in these SBC (or any tech, really), be more patient with yourself. Results will eventually come if you put in the time. But you will have to read, potentially a lot. It's not for everybody. Or maybe a different board will be easier to achieve early success with (I don't know this particular board). But in general, what I have read on forums is there are so many "random TV boxes" it is absolutely impossible to support them all. Read more threads, look for a known supported device, and then purchase that. Even better, use Armbian Supported Devices list as a starting point for any purchases (if you want a much easier experience). Good luck. I know it can be frustrating. Take a step back, take a break maybe, try and enjoy the journey.

The original place I noticed it was in P2P. Did you change/fix anything? Otherwise I am going crazy. Or I just missed it. Because it seems to be back now.

Thanks for reporting back. I'm glad to hear it worked out! To whatever extent you are able/willing, please consider helping out. Armbian is just us, mate. Cheers! EDIT: Because title of OP was about kernel education, I took the liberty to mark my own answer as the solution, instead of one right above this, as thread was not directly about getting Tailscale itself working (rather that's a symptom).

I could swear I read this being discussed (even recently), but I'll be damned if I can find it right now. Have there been some recent changes? It seems only 1-2 days ago I could mark any post as the solution, but this seems to have gone away?

FWIW, I never used them because it was unclear to me exactly what they did (until you explained in detail above, so thanks for that). My personal take is also a little more nuanced, but I have not been doing it as long as some of you guys either.

I was just kidding. I had to look mine up (I have a Kill-A-Watt and do periodic power testing on things) and the KGPE-D16 idles about 165 W and 372 at full power. But it's older tech, much less powerful than this brand new Threadripper of course. I trade efficiency for freedom (and happy to do so). Until NSA launch their back doors, and then I am the only one left standing with a running computer. Muhahahahah! Hello, this is John Connor. But I don't need it most of the time, for personal use. In fact just talking to Nico about his videos making me think very hard about using SBC for daily driver desktop and save some electricity.

Yes, good promo, bring more attention. So turn it on between specified hours, build all images, and off the rest of the time. Or that power increase is only at load?

OK. Thanks, Igor. In case it was not clear, I did not explicitly install any kernel, it was installed by Debian just by doing regular `apt upgrade`. Sounds like there is nothing to be done then? Other then be aware and go in manually and change it after each upgrade? If all of above is the case, I start to wonder if apt provides any sort of post-update hook... /wheelsturning