You are not logged in.
Pages: 1
I understand aur helpers are not supported by archlinux, so if this question is disallowed, please delete it.
During pakku install of babe-git, i experienced accidental power loss. I believe it happened during a very lengthy compile process.
https://aur.archlinux.org/packages/babe-git/
After reboot, my NTP was inactive and the clock was wrong. (timezone was still correct).
I reactivated NTP-- no problem with that.
Other things seem ok. But my concern is, if NTP got messed up, maybe something else got messed up too.
Any thoughts, suggestions?
Last edited by atomikegg (2020-05-28 19:30:53)
Offline
Run a SMART check for general harddisk health and a fsck on your filesystems. FWIW a clock getting broken on power loss can be normal (how did you need to "reactivate" NTP exactly?)
Offline
Thx
"need to"? `timedatectl` showed it was inactive.
timedatectl
Local time: Sun 2020-05-24 11:46:19 PDT
Universal time: Sun 2020-05-24 18:46:19 UTC
RTC time: Sun 2020-05-24 18:46:19
Time zone: America/Los_Angeles (PDT, -0700)
System clock synchronized: yes
NTP service: inactive
RTC in local TZ: no reactivated NTP with:
timedatectl set-ntp true
systemctl restart systemd-timesyncdAfter some experimenting, it seems the second command alone might have been sufficient.
What's a better word than "reactivated"?
thx
Last edited by atomikegg (2020-05-24 18:53:55)
Offline
If you haven't enabled the service, nothing has changed...
Offline
If you haven't enabled the service, nothing has changed...
After i ran the two commands above, my system clock corrected itself. Seems to be working.
Arch wiki says:
To enable and start it, simply run:
# timedatectl set-ntp true
https://wiki.archlinux.org/index.php/sy … yncd#Usage
So i guess you're saying both commands are required?
thx
Offline
But if you've never done that before this incident, then this is normal and expected. As far as I know using the set-ntp command should be sufficient, check the status of systemd-timesyncd
Offline
Pages: 1