Get:1 http://raspbian.raspberrypi.org/raspbian bookworm InRelease \[15.0 kB\]
Get:2 http://archive.raspberrypi.org/debian bookworm InRelease \[54.9 kB\]
Err:1 http://raspbian.raspberrypi.org/raspbian bookworm InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY XXX-EDITED-XXX
Err:2 http://archive.raspberrypi.org/debian bookworm InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY XXX-EDITED-XXX
Reading package lists... Done
W: GPG error: http://raspbian.raspberrypi.org/raspbian bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY XXX-EDITED-XXX
E: The repository ' http://raspbian.raspberrypi.org/raspbian bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://archive.raspberrypi.org/debian bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY XXX-EDITED-XXX
E: The repository ' http://archive.raspberrypi.org/debian bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Above indicates the Pi experienced at least two power brownouts.
They can cause processes to crash or worst case corrupt the SD card filesystem.
I would recommend to fix that first by replacing the power supply and/or the USB cable supplying power.
And bc we dont know if files are already corrupted and to what extend, re-image the SD card with a fresh Pi-OS.
Thanks a lot for all the help and time spent responding to me. I understand that both the cable and the power supply unit are very good quality. Could this be due to a city-wide power outage (since it's not protected by a UPS)? Thanks,
Yes it could.
If power is cut without a proper shutdown, files could also corrupt.
But you would know better when this happened.
And according to the journal, one brownout happened today.
Did you have a power outage today?
Well, that's even stranger... No, there weren't any today, nor on the 14th. Yes, I often power it off at the wall switch/socket, meaning I cut the electricity to the entire rack to restart the router, etc., which is all connected to the same power strip... The odd thing is that if this is the cause, I do this multiple times a week for various reasons, and yet it only registers 2 instances here. Regardless, I'll take your suggestion to reinstall everything from scratch and plug the RPi into a separate, protected outlet. Thank you very much!
P.S. I will also start performing the proper shutdown process; that laziness that keeps me from typing one line...
The logs are showing "undervoltage", not a complete power failure.
Undervoltage happens when the power supply is not able to provide enough voltage for the system. Sometimes connecting an external HDD, a keyboard or mouse can cause a momentary undervoltage and this is logged.
Complete power failures (like in a power outage or powering off the wall socket) are not logged because the power is cut immediately and there is no time to log them.
Thank you very much. I'll thoroughly check everything before replacing it, since the power supply is good (SONY 5V / 2.1A), and I use the RPi exclusively for Pi-hole with nothing else connected—just the network and power cables.
How do you know that for sure?
Did you connect an oscilloscope to measure?
Its not only the Wattage that counts but also power stability (no fluctuations).
An AC adapter designed for charging cant always be used to power a Pi bc of this.
As long as you keep experiencing those "under-voltage" messages, you risk the FS getting corrupted or "cause unpredictable behaviour":
Power supply warnings
On all models of Raspberry Pi since the Raspberry Pi B+ (2014) except the Zero range, there is low-voltage detection circuitry that will detect if the supply voltage drops below 4.63V (±5%). This will result in an entry being added to the kernel log.
If you see warnings, switch to a higher quality power supply and cable. Low quality power supplies can corrupt storage or cause unpredictable behaviour within the Raspberry Pi.
Voltages can drop for a variety of reasons. You may have plugged in too many high-demand USB devices. The power supply could be inadequate. Or the power supply cable could use wires that are too thin.
Honestly, no, and you're right. I only trust that SONY power source because it's not a cell phone charger, but a USB power supply for different devices like power banks, etc., and the ones I have have always given me good results. But it's just my personal trust in it, nothing technical; you are correct.
Absolutely correct.
I somewhat minimized the consequences of not paying attention to the power supply, cable, and shutdown of the RPi. Lesson learned
I genuinely thank everyone very much for the excellent willingness to help and the quick response time.
Now I have learned something new, and reinstalling everything wasn't truly catastrophic. I believe if I had done that from the beginning, I would have saved time, but the positive thing about these processes is that you always learn something more. If I had just installed it, I wouldn't have noticed all these details. Again, thank you very much @deHakkelaar and @rdwebdesign !!!
Yeah you have to be a bit lucky when not using an official Raspi AC adapter.
Dont forget to try exchange the USB cable first if its not permanently attached to the AC adapter!
Thicker and shorter is usually better.
Booting and when the Pi is under heavy load, like a Pi-hole gravity update, is usually when you experience those under-voltage messages.
Also good to know below:
$ vcgencmd get_throttled
throttled=0x0
$ man vcgencmd
[..]
get_throttled
Returns the throttled state of the system. This is a bit
pattern - a bit being set indicates the following meanings:
Bit Meaning
──── ────────────────────────────────────
0 Under-voltage detected
1 Arm frequency capped
2 Currently throttled
3 Soft temperature limit active
16 Under-voltage has occurred
17 Arm frequency capping has occurred
18 Throttling has occurred
19 Soft temperature limit has occurred
A value of zero indicates that none of the above conditions
is true.
To find if one of these bits has been set, convert the value
returned to binary, then number each bit along the top. You
can then see which bits are set. For example:
0x50000 = 0101 0000 0000 0000 0000
Adding the bit numbers along the top we get:
19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
From this we can see that bits 18 and 16 are set, indicating
that the Pi has previously been throttled due to under-volt‐
age, but is not currently throttled for any reason.
