(Quote)

(Quote)

(Quote)

(Quote)

(Quote)

(Quote)

it turns to read-only and throws out a lot of IO errors and has to be hard rebooted. This can happen after being online for >1 year without issues. Even if the drives are never actually 'faile

(Quote)

I had the xz-compression error. I ended up with 300000 entries in lost+found, which wasn't much fun! Here's a general outline of how I handled it:

Restoring from backup (another storage VPS via Borgbackup) is still network IO bound, going at ~90Mb/s so it's taking a loooong time. 45% done so far.

I've got an error on mine as well 'the root filesystem on /dev/vda1 requires a manual fsck' when booting... this does not look promising!

Getting this error, and googling it tells me to check the RAM. May this be a host node issue?

(Quote)

Anyone knows how to fix this error? this happened after shutting down system and booting it up again from website

(Quote)

as for narrowing down, am am unsure, whatever i try it comes down to same error message every time (tried different tokens, generating them differently, etc) i can't even find lead how to debug this f

What's the error?

Now I try to re-attach github profile and it gives me "Internal server error" in their panel :-/ the shit is lit.

When you VNC in do get any VNC error messages?

(Quote)