Jump to content

Orange Pi PC armbian problem?


F-l-o-r-i-n

Recommended Posts

Armbianmonitor:

Hi. I run armbian on a opi pc for a while. It works fine for a couple days when I work with this board. After that I left the board unpowered for two weeks or so and when I want to powered it on, it does not boot, I need to reconnect the power again to boot. This was the first time when I encountered a problem, the uptime was wrong, it is shows me 2 weeks, I reboot the board and it was ok after, it stays on and all worked fine for 10 hours until I shut it down.

 

But I had this problem often, doest not want to boot from first time, board freeze after some time and I need to reboot to work properly. Uptime and date/time is correct but when I want to see the status of a service (eg. type systemctl status chronyd) it is showing me that was active for a long time, wich is not true, should be minutes ago, not a day. I dont know why keeps data from the past.

 

dMffdAC.png

 

I am a beginner with linux. I dont know what is the problem with booting from first time correctly like when I install armbian for first time and my debug skills are zero.

 

I am using a Sandisk Ultra Class 10 64gb , a Rpi 4 official power supply (jumpers to gpio) and has connected an external 480gb ssd (sata to usb case).

 

Sorry for my english.

Edited by F-l-o-r-i-n
Link to comment
Share on other sites

According to chrony, the system clock was wrong when it started up, and it was 97380 seconds late, which is roughly 27H, which fits with the "1 day 3 hours ago" diagnostic.

Now, I don't know how the clock is updated and it seems that systemd is displaying the "running" time based on the day time, instead of a monotonic clock. There might be a way to force it to display the "running" time using a monotonic clock, though.

Link to comment
Share on other sites

On 5/27/2020 at 7:53 PM, Myy said:

According to chrony, the system clock was wrong when it started up, and it was 97380 seconds late, which is roughly 27H, which fits with the "1 day 3 hours ago" diagnostic.

Now, I don't know how the clock is updated and it seems that systemd is displaying the "running" time based on the day time, instead of a monotonic clock. There might be a way to force it to display the "running" time using a monotonic clock, though.

I understand now. Thanks. So, if is not a problem, is good. I think I will make a fresh install with Bionic these days and see if is stable enough for my project.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines