Blown Raspberry
What I had planned to do with this self-hosted website and what I'm doing are two different things. Best laid plans and all that...
For the website I use the Ghost blogging platform in a Docker container, all hosted on a Raspberry Pi 4 using Cloudflare to cache web requests. So far, so good. That was until I made a change on my home network, powering back on the Pi resulted in extremely long boot time and distressed EXT4 journaling error messages.
The Pi is using SSD as its root storage and hoping this wasn't a hardware failure (SD cards are more susceptible to read/write failure over time) I could recover the data.
What did I do?
- Easy enough, popped the back off the Argon that the Pi lives in and inserted a SD card formatted with the latest version of raspbian OS.
- As the Pi normally operated header less, plugged HDMI, keyboard, and mouse.
- Started the Pi up.
- Issued the command sudo fdisk -l
5. The Linux partition that contained my data is SDA2.
6. As /dev/sda wasn't mounted issued the command sudo fsck /dev/sda2
7. fsck reported that the journaling had been repaired.
8. Removed the SD card and rebooted the Pi.
9. All is well, normal boot times and the website is back up and running.
What does that teach me?
Back up your data, always back up your data before making any network change. No matter how trivial.