• Content Count

  • Joined

  • Last visited

About MattCostamagna

  • Rank

Profile Information

  • Gender
  • Location
    Cuneo, Italy

Contact Methods

  • Github

Recent Profile Visitors

96 profile views
  1. Yes you are right, making a new image won't take me that long and it's something I've been considering since I saw the sort of problem I was facing. I'll just leave this thread as unresolved so if someone in the future will manage to find a solution they can post the answer here. Thanks a lot for your support.
  2. Thanks @TRS-80 That might be the reason (also because I've excluded all the other possible causes), but I don't understand what could be the cause... I didn't quite understand what you meant here: And yes, I can make a new version of the image of our project, but before doing that I wanted to be sure that I can't do anything else.
  3. @Werner I meant that I tried flashing a vanilla version of Armbian into one of the SD cards that are not working with the production image I've been using, and with a vanilla image I don't see the errors that I see with the other image (which however works with the old SD cards). Hopefully that's more clear.
  4. @TRS-80 Thanks for your reply. The SD cards are brand new and they've never been used. We have verified that all sectors are writable using h2testw and we've got zero errors. We also tried different SD cards coming from the same batch but the outcome was the same.
  5. Hi @Werner I tried making an exact copy of the source image using etcher without modifying anything else. The validation of the written data was successful and I didn't get any errors, but unfortunately the result was the same: card stuck in programming state and sometimes I can't even reach the login.
  6. Actually I didn't. I supposed that if dd doesn't return any error it means that the operation went succesfully. What can I do to verify it?
  7. Hi, I've been using Armbian for three years on some work's project and this is the first time I see this issue. Basically I have an image of the operative system and all the programs and scripts already saved in it, so when I have to prepare a new SD card I just use the command "dd" and then I modify some registry stuff specific for the object I'm creating. It has always worked without problem, but now we bought a new batch of SD cards and I'm facing this issue: the dd command goes succesfully and if I mount the partitions after it has finished I can see all my data, but
  8. I found out that the networking.service has a param called TimeoutStartSec that defaults to 5min in /lib/systemd/system/networking.service. I lowered that value to 15 seconds and the problem is gone. Here's a useful command: sed -i -r 's/TimeoutStartSec=.*/TimeoutStartSec=15/' /lib/systemd/system/networking.service
  9. Hi, I'm facing a problem with my Orange Pi Zero with the latest Armbian version. I noticed that when I provide an internet connection type that is not valid (wrong psk, ethernet but no cable plugged in, etc.) and I reboot the system, it hangs just before asking the username and password. Sometimes it takes up to 10 minutes before keeping going. These are the last boot logs that I see: [ 11.209226] systemd[1]: Starting Create list of static device nodes for the current kernel... [ 11.219428] systemd[1]: Condition check resulted in Load Kernel Module
  10. @xwiggen Yes, this is something I didn't know before, so now I removed the tmpfs entry in fstab. When I did this yesterday, the copyctruncate in logrotate magically started working. I have no idea why the tmpfs conflicted with logrotate. I wanted to post this yesterday but the Armbian forum didn't let me because I reached the maximum number of posts I can make per day (1 I guess)... Yes I know but for the type of application I have to develop I don't care that much o logging because it's all saved on a cloud environment; local logs are useful to me only when eve
  11. @xwiggen Thank you for your reply. I tried doing what you suggested and it worked. I still don't understand why /var/log does not work while /var/log.hdd works. Now I have two problems: I configured /var/log as a tmpfs in /etc/fstab (tmpfs /var/log tmpfs nodev,nosuid 0 0) so that log files do not count as writes to the SD card. I previously didn't know about /var/log.hdd, so I think that now this doesn't make much sense. I'd still like to write logs in a way that do not spoil the SD card on the long term, how can I do it? How can I disable the writes t
  12. Hi everyone, I'm facing a problem with logrotate on my OrangePi Zero with Armbian Focal mainline. Basically I have a process that is always running with a `tee` command that outputs the stdout to a log file in the /var/log/ directory. My logrotate configuration file looks like the following: /var/log/smartbit/gocpp.log { rotate 10 daily compress missingok notifempty copytruncate dateext } It's all working correctly except the copytruncate part: logs are daily rotated and gzipped but the gocpp.log is not truncated to 0 bytes, so it gets bigger and bi