SodaWithoutSparkles

I havent seen any errors, but I havent view all of the logs, just some of them. From what I have remembered, systemctl showed that it was terminated. `boot.log` shows...

I manage to get it again, somehow ``` ● log2ram.service - Log2Ram Loaded: loaded (/etc/systemd/system/log2ram.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) since Tue 2021-10-19 17:23:41 HKT; 3min 14s...

The issue resolved again after I reinstalled, so I could not test it. But I remember that when I was debugging yesterday, I tried to start it manually, by `sudo...

I dont know, but the my log size was kept below 40M, tho I set the capacity to be 80M, but zram bumped that up to maybe 130M or so...

@XhmikosR the most simple solution is to check the status of log2ram right after reboot by sudo systemctl status log2ram If it said `active (exited)` its should be fine. Make...

You may need to use sudo to read boot.log Or you could try to reinstall log2ram, but be reminded that all logs, including the archived ones would be gone. Make...

@azlux I have an idea. Maybe log2ram was configured to start before zram, so it tried to write to a non-existing drive?

``` [Unit] Description=Log2Ram DefaultDependencies=no Before=basic.target rsyslog.service syslog-ng.service syslog.target systemd-journald.service sysinit.target shutdown.target zram-swap-conf.service apache2.service lighttpd.service After=local-fs.target Conflicts=shutdown.target reboot.target halt.target RequiresMountsFor=/var/log /var/hdd.log IgnoreOnIsolate=yes [Service] Type=oneshot ExecStart= /usr/local/bin/log2ram start ExecStop= /usr/local/bin/log2ram stop ExecReload=...

@clavay Strange. Both my zram and log2ram are working now, but that command I just ran give me this result: sudo systemctl --type=service | grep zram ``` [email protected] loaded active...

@azlux no, that does nothing. Maybe you could try setting up /var/www/html as another log2ram to test it urself