lzb

Members
  • Content Count

    10
  • Joined

  • Last visited

Everything posted by lzb

  1. So I've installed and I'm running watchdog for some months now on BananaPi M1. I think it reboots the board when the default gateway has some issues. And that's fine, no problem with that. The board works 24/7 and it made 14+ days uptime without problems. But things have changed and the board reboots at least few times a day (seems I have a problem with armbianmonitor -u - the board rebooted twice before it ended). And here's the problem. watchdog doesnt log anything or I'm unable to find any usefull info. And watchdog.conf: (it seems that the board went offline -
  2. Just a simple little question - I've moved my system to SATA, but there are still full OS on the SD Card: ~# ls /media/mmcboot/ bin boot dev etc home lib lost+found media mnt opt proc root run sbin selinux srv sys tmp usr var I would like to remove unused stuff to make some space.
  3. This patch is included in -next already? I can test it with BananaPi M1. ::edit commit messages seems to confirm it is in -next. Bleh, more like in -dev. I need more coffee... ::edit2 4.9.38 (next), only one test made. fs: btrfs random random kB reclen write rewrite read reread read write 102400 4 3951 5919 14107 14547 1337 4955 102400 16 9908 14394 17473 32988 3338 10818 102400
  4. I've made my install on SATA hard drive few weeks ago without issues, but I can see something weird over here. I suppose you should use rootdelay, not bootdelay.
  5. A little update, as I've updated and rebooted the board, but it's still here: root@bananapi:~# armbianmonitor -m >> armmon.log /usr/bin/armbianmonitor: line 385: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 386: [: 43.2: integer expression expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 386: [: 43.0: integer expression expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 386: [: 43.1: integer expression expected /usr/bin/armbian
  6. @guidol I can spot some difference in uptime and "a board just booted" and "a board with some uptime doing things". My is running urbackup (mostly active two or three times a day) and nextcloud (mostly idle at the moment). I had issues running this setup for more than 24h (freezes), but it seems to improve: root@bananapi:~# uptime 08:56:57 up 2 days, 8:13, 3 users, load average: 0.59, 0.56, 0.55 And current uptime is still growing after some serious testing (running stress, running btrfs scrub and btrfs balance to simulate "typical" workload). Not sure where this 4.76V came
  7. Sorry for grave digging, but I have the same error messages in BananaPi M1: root@bananapi:~# armbianmonitor -m >> armmon.log /usr/bin/armbianmonitor: line 385: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 386: [: 43.5: integer expression expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 386: [: 43.3: integer expression expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 386: [: 43.2: integer expression expected /usr/bin/armbianmo
  8. Yeah, I remember from somewhere that OPi has "compatible" GPIO with RPI, but rotated (180 degrees?). (as an important side note - would be nice if pin description on the breadboard adapter fit actual pins - I can live without this or with a piece of paper, but it's usefull to have valid description for kids )
  9. I'm looking at GPIOs and I'm not sure - can I buy an "old" (26 pin) Raspberry Pi gpio adapter-breadboard-cable package (like this one) and use it on Orange Pi Zero GPIOs as on Raspberry Pi GPIOs?
  10. So there is some improvment over recent kernels or 1.4 is just "randomly broken"?