Data loss on the VPS

xavi commented

2024-10-25 22:51:21 +02:00

Collaborator

Possibly related to the FTTH Kosc incident, the remote VPS at 80.67.160.158 (btw, README.md still lists 80.67.160.150) cannot be accessed:

ssh: connect to host 80.67.160.158 port <redacted>: No route to host

Possibly related to the [FTTH Kosc incident](https://live.sewan.fr/incident/1701), the remote VPS at `80.67.160.158` (btw, `README.md` [still lists](https://forge.a-lec.org/cominfra/speed-dreams/src/commit/dc27158d42cb8c4cd331e1bdd9280b69226993c4/README.md) `80.67.160.150`) cannot be accessed: ``` ssh: connect to host 80.67.160.158 port <redacted>: No route to host ```

neox changed title from ~~Cannot access remote VPS~~ to Data loss on the VPS

2024-10-26 23:43:45 +02:00

neox commented

2024-10-26 23:46:08 +02:00

Owner

I worked on that today. It was unrelated to the Kosc Incident, but a partition corruption from an unknown cause. It started by a problem with kernel modules being corrupted and APT/DPKG broken with specific python3 packages also corrupted.

I was forced to restore a backup from september (2024-09-13T00:03).

I'm still investigating on the cause of that loss.

I worked on that today. It was unrelated to the Kosc Incident, but a partition corruption from an unknown cause. It started by a problem with kernel modules being corrupted and APT/DPKG broken with specific python3 packages also corrupted. I was forced to restore a backup from september (2024-09-13T00:03). I'm still investigating on the cause of that loss.

😕 1

neox added the

bogue

label 2024-10-26 23:46:13 +02:00

neox commented

2024-10-26 23:57:07 +02:00

Owner

Currently upgrading and repairing broken packages (from the september backup).

👀 1

neox commented

2024-10-27 20:52:01 +01:00

Owner