Jump to content

Pedro Lamas

  • Posts

  • Joined

  • Last visited

 Content Type 


Member Map




Everything posted by Pedro Lamas

  1. Not sure what the governor is or how I can change it (granted, haven't looked into the docs yet) but if there's any setting I can change to test I'll be willing to do just that! At the moment, the best I've seen my nanopi m4v2 work without crashing was about 3 days, but on average I have to reboot it daily...
  2. A few more errors this morning: Message from syslogd@localhost at Sep 20 10:50:09 ... kernel:[59823.225830] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP Message from syslogd@localhost at Sep 20 10:50:09 ... kernel:[59823.252559] Code: f9401bf7 17ffff7d a9025bf5 f9001bf7 (d4210000)
  3. The device gets completely unresponsive after this, is there a way to as least make it automatically reboot on failure instead of waiting for me to do it manually?
  4. Another one just now while I had an SSH session open: Message from syslogd@localhost at Sep 19 16:57:04 ... kernel:[ 2638.817744] Internal error: Oops: 96000005 [#1] PREEMPT SMP
  5. Just got yet another of those errors while using docker: pedro@nanopim4v2:~/docker$ docker-compose down Stopping docker_mariadb_1 ... Stopping docker_homeassistant_1 ... Stopping docker_nginx_1 ... Stopping docker_zigbee2mqtt_1 ... done Stopping docker_esphome_1 ... Stopping docker_telegraf_1 ... done Stopping docker_acme.sh_1 ... done Stopping docker_mosquitto_1 ... Stopping docker_portainer_1 ... Stopping docker_vscode_1 ... Stopping docker_grafana_1 ... Stopping docker_adguardhome_1 ... Message from syslogd@localhost at Sep 19 16:10:14 ... kernel:[108790.564123] Kernel panic - not syncing: bad mode System stalled after that and I had to manually restart it.
  6. I'm still getting these daily, not sure what else can I do to fix it... any ideas or thoughts would be quite welcome!
  7. Just updated to the latest firmware, will keep you posted if I still experience the same issue! pedro@nanopim4v2:~$ uname -a Linux nanopim4v2 5.8.6-rockchip64 #20.08.2 SMP PREEMPT Fri Sep 4 20:23:22 CEST 2020 aarch64 GNU/Linux
  8. I looked at the logs in /var/log/kern.log and found this: https://pastebin.com/aTaSaPFM I clearly remember the error shown when it crashed to mention "PREEMPT SMP" which is shown above! If there's any specific log I can provide to help with this please do tell me and I will upload.
  9. Yes, I have a standard 5V 4A Power Adapter charger that came with the board, unfortunately that too causes the same issue...
  10. I'm powering it with a 5V 4A PoE adapter. I'm using a 256GB Sabrent M.2 NVME SSD as the main disk (configured via armbian-config), so the Samsung SD card is for initial booting only. I'll try to get a screenshot of the error and post it here the next time I get that error.
  11. My NanoPi M4V2 is currently being used completely headless just to run a few Docker containers (AdGuard Home, Home Assistant, Zigbee2Mqtt, etc.) and I've been noticing more and more crashes happening... sometimes they occur while I have an open SSH terminal, and I get a glimpse of a "kernel panic" type error... Here's the output from armbianconfig: http://ix.io/2vFX Any ideas on what this is or how to fix it? Thanks in advance!
  12. FYI, I found that this was due to a missing entry in debian-config-functions so I submitted a PR to add it (here) and this has now been merged so it should be available on the next update of armbian-config!
  13. Like the title says, when I open armbian-config on my brand new NanoPi M4N2 I don't see a "Hardware" entry in the menu... is this expected? Only reason I wanted to access is to ensure I disable WiFi as I am only using Ethernet. For the record, I'm powering it with a 5V 4A PoE adapter, using a Samsung SD-card flashed with Armbian_20.05.7_Nanopim4v2_buster_current_5.4.49.img. I'm using a 256GB Sabrent M.2 NVME SSD as the main disk (configured via armbian-config), so the SSD card is for initial booting only.
  • Create New...