So you're running a LAMP stack, and a web browser on the same 1GB Pi 4 - is that right? Sounds like that first attempt at running Chromium has caused an out of memory (OOM) condition which has hard hung the system, then you've ended up with some filesystem corruption.
I suggest you're going to need a Pi with a lot more memory to run a LAMP stack and a web browser on the same machine. However, the problem is made worse by the default configuration of Raspberry Pi OS, which only configures 200 MB of swap by default.
If you can start with a clean install of the OS - ideally on another SD card - then after the first boot config is complete, and before you do anything else, edit the file /etc/dphys-swapfile to increase the amount of swap allocated:
Change the line that reads:
so that it reads:
For a 2048MB = 2GB swap file, then reboot. The system will still be slow when under memory pressure, but should potentially be a bit more stable and usable. But as I said above, the real solution is more RAM.
I suggest you're going to need a Pi with a lot more memory to run a LAMP stack and a web browser on the same machine. However, the problem is made worse by the default configuration of Raspberry Pi OS, which only configures 200 MB of swap by default.
If you can start with a clean install of the OS - ideally on another SD card - then after the first boot config is complete, and before you do anything else, edit the file /etc/dphys-swapfile to increase the amount of swap allocated:
Code:
sudo nano /etc/dphys-swapfileCode:
CONFIG_SWAPSIZE=200Code:
CONFIG_SWAPSIZE=2048Statistics: Posted by andrum99 — Mon Jul 15, 2024 11:47 am