• Content Count

  • Joined

  • Last visited

About Talkabout

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Device is RockPI as mentioned above. Your statement means that if I create a small partition, put only the /boot folder there and then export it via "dd" to an image file, restoring that to an SD should give me the ability to boot correctly?
  2. hm..., possible but not very nice Thanks for the hint! So with Armbian the boot partition and ext4 root partition are basically the same? And the bootloader simply points to the /boot folder? Bye
  3. My requirement is a little bit different: I would like to include this "boot image creation" into my backup process as an automatic action. Maybe the solution is to - create temporary partition - copy /boot to that partition - install boot loader on this partition => this is something I do not know how to do it - create img out of this partition The problem is I am not really into the whole "boot thing" that is why I am asking for help (or maybe some howtos). is the above process the best option? Thanks!
  4. I am using RockPI. While rsyncing the file system all the folder (including /boot) are backed up, but to restore a damaged sd card currently I would need to install stock armbian and modify the boot files in order to boot from nfs root. I would like to simplify this process by creating a small "img" file that I can restore easily on sd card failure. Is there any way to do that? Thanks!
  5. these files are loaded from sd card, this is why I would like to backup them as an image file to be able to quickly restore them.
  6. Hi guys, I am currently working on backing up my armbian installation. Following situation: boot: sd card file system: nfs root backing up the file system is not an issue, there I am using a rsync logic that transfers only changed files, which works great. The problem is with the boot files. In case of sd card failure I need an image that I can quickly restore to a new sd card, without the whole file system, as it is on nfs root and backed up differently. Now my question is: what is the best way to create an image file with only the boot log
  7. HI all, the issue was related to one of my network cables. After applying a different one the issue was gone. Thanks to everybody who took the time to think about it! Bye
  8. Hi guys, I recently bought a Rock PI 4 and installed Armbian Buster with kernel 5.4.6. The os is booting fine but I am facing major performance issues when trying to download from the internet. I have also a Raspberry Pi 4 connected to the same switch (via LAN) and when I execute the following command curl -L > /dev/null I am getting download speed of approx 8MB/s on my Raspberry but only 2MB/s on my Rock PI 4. From connection side and rooting there is no difference. While using the same Armbian version on my Rock64 I am get
  9. Thank you very much, pointing to the "sndbuf/rcvbuf" values was the key. After changing those the throughput showed "normal" values again. Bye
  10. Hi guys, I have recently bought a Rock64 to improve the performance of my VPN gateway. First tests look very promising as you can see here: root@rock64:~# openssl speed -evp aes-128-cbc -elapsed You have chosen to measure elapsed time instead of user CPU time. Doing aes-128-cbc for 3s on 16 size blocks: 15394610 aes-128-cbc's in 2.99s Doing aes-128-cbc for 3s on 64 size blocks: 12591175 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 256 size blocks: 6719021 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 1024 size blocks: 2448108 aes-128-cbc's in 3.00s Doing aes-1