Here’s my boot screen
I think I know the problem. I’ve had PiHole running for some time so on boot, log2ram is writing the WHOLE log file to ram (or trying to) for the first time then gets to 128Mb and crashes with a kernel panic.
IF I installed this initially it wouldn’t have happened because there would be very little to write and it can complete its first task.
Problem now is it performs log2ram first, before even SSH launches or PiHole launches so not only do I have no useful apps running, but I can’t even ssh into it to fix things.
looks like a new build from scratch and yes, this time I’ll clone the card to another 4GB one beforehand
I will try log2ram again but reduce the size to 96M and see if it’s happy - hopefully it’ll all be fine (the biggest thing on starting from scratch is the 1.5hr first apt-upgrade....everything apart from this is easy and quick)
EDIT #1: Just done it. Install order was;
Format SDcard->Raspbian->Update/Upgrade->Log2RAM->PiHole
used your link for log2ram and currently everything working fine (space set at 96M btw)
EDIT #2: So after leaving it overnight there is an improvement over not having Log2RAM installed.
I have a voltmeter monitoring what the power supply is delivering and previously it would sit at 4.97V or 4.99V. The former indicated that the Pi was doing something, so when it was writing to the SDcard, most of the time I'd see 4.97V. Occasionally when it didn't I'd see 4.99V.
Now, most of the time I'm seeing 4.99V meaning the Pi isn't continuously "doing" something (ie. writing to card). Memory usage doesn't appear to be effected too much but the second thing I've noticed is that previously it would spend a lot of time with the red "high load" icon whreas now it spends a lot of time under normal load:
So I also recommend this program if you have a service which writes lots of log files like PiHole does
Author: G a f f e r
Author
2-12-2019 04:39:24