jcorbet

First I have to thank all maintainers for their work. I ran this server for 1.5 years before something broke. Since armbian is maintained by volunteers I want to cheer you up and thank you for your hard work. However just today my little server would die after apt-update/upgrade. I use a SATA drive together with a boot SD-card (only containing /boot). I can observe the following behavior: The system leds indicate that booting is sucessful (blue LED does blink regularly, I can detect HDD usage by observing the green LED), yet SSH login that I have been using for years no

bump

So, now I compiled the kernel with the script and also managed to install the .deb packages. Then I checked for kvm support via dmesg | grep but found none. Ultimately I chose to delete all dtb files in the dtb-latest folder under /boot but the one tagged xu4-kvm, but this resulted in the machine failing to start. Luckily I have made a backup so I could go back. However I have no clue what goes wrong and even more important I do not know how to find out. What should I be looking for? Edit: I have got the machine running again. It was me having set (correctly at the time

Hi. I am now at looking around and modifying things. Oh man - there is so much to decide. Can I safely make appropiate decisions or should I only make the slightest modification possible solving the problem? Any way: I have found virtualization support, but I have not actually found KVM. I diffed the two configs of hardkernel to look for the options. Yet I do not seem to have every option that they tick. Have a look: https://www.diffchecker.com/y8uJifYA (right at the end is the most juicy stuff regarding KVM) What does this mean?

Thank you for your answer. Can you explain to me how to exactly configure the kernel for KVM? I can for sure setup the buldenvironment and stuff .. but then I am a bit clueless what to do? What do I have to adjust? And where do I find the data? And when the process runs how do I update my existing installation with the new stuff? Is there some general guide on compiling ARMbian with KVM?

Hi forum, I want to try out KVM virtualization since I found out that Odroid HC-1 (=Odroid XU4) does in fact support hardware virtualization and should therefore have a good performance. (Is this true, has someone already done this and can confirm?) In the past I have worked with other virtualization software but this would be my first time to use kvm. Not long ago I started a server projet which works very very well and serves all my needs. The little board is so efficient indeed that I got more than 1GB of unused RAM and also a lot of unused performance. T

OK. Then I will complete my installation and set it up as a productive system. I am not so sure about how to backup this. But I am sure I will come up with a solution. Maybe I will just create an installation script and backup the content. When reading your bash scripts I feel like I really should learn it. Best to you both and the rest of the team

Okay. Can I help in any way? What commands shall I run/what outputs shall I generate? As I own the hardware maybe I can give back by providing information/testing software Found this when googling: https://github.com/hardkernel/u-boot/tree/odroidxu4-v2017.05 (XU4 is the "same" hardware as HC-1) However I just started out with SBCs so I am really not knowledgeable ^^.

Thank you. Really. And everyone who contributes to this software obviously

Ok. I see. So what one ought to do is disable resizing (systemctl disable armbian-resize-filesystem on first boot) in order to maximize spare SD size for the controller to be able to survive. Then you clone it to SSD with armbian-config. Then you have everything deleted but /boot. Then you enjoy SSD speed and surviving SD with enough space for kernel update. Correct way of doing this in the future?

Ok. Have tried it. Error message also gone. Shoudl hopefully work now. Thank you for the clarification PS: Since SD is small - will I have problems with kernelupdates in the future? I plan to use the serverfor ~4-5 years. Can I manually erase the old rootfs files after the transfer? Or is this done automatically and everything is OK? Sorry, for all the confusion I might be causing. When editing the fstab I noticed that only /boot is mounted. So I can erase everything else from /media/mmcboot, right?

I will start to list all the commands I have tried to resolve the problem here: systemctl start armbian-resize-filesystem (run as root) - no visible output, does not seem to change anything /usr/lib/armbian/armbian-resize-filesystem - ran the script there with the parameter start. Did not work either. I am now reading the comments in the script to understand what it does and what my options are :). Any help however at this point would be very appreciated since I think it might be a problem with the software and not with my install alone. Maybe we can fix it togethe

Hi, can someone point me towards the next best thing to try out? I would really like to advance my understanding of this problem If you need more data I can run every test that you like. Best Julian

New Upload Hi, I hope this helps. I am very irritated that it displays January 19th as logdate. What I have done to obtain it is use armbian-config and then System/3rd Party -Diagnostics. Best Julian

Hi community, I am a newbie when it comes to SBCs and Armbian, but I will do my best to thoroughly explain the problem. Problem: Armbian (Ubuntu 18.04 based, release for HC-1) Despite me rebooting a zillion times, resizing does not happen/finish/...: Error message (displayed exactly like this): Warning: a reboot is needed to finish resizing the filesystem Please reboot the system as soon as possible ilesystem Please reboot the system as soon as possible Hardware: SBC: Odroid HC-1 2GB RAM (known work