Dirty filesystem on a VPS

Asked Jul 20 '19 at 15:08

Active Jul 20 '19 at 15:08

Viewed 53 times

I was alerted to my site, on a VPS, going down by Uptime monitor. I SSHd to it to reboot, which is usually what it needs, and then it all went bad.

Turns out the underlying NAS was rebooting for no apparent reason (according to my service provider) and I rebooted in the middle of that.

I have a dirty file system - but I can't run fsck fsck from util-linux 2.31.1 and I can't sudo sudo: unable to resolve host asimov: Resource temporarily unavailable.

The web interface refuses to respond.

Apparently I have to reboot in recovery mode but all I have is the command line.

asked Jul 20 '19 at 15:08

Adaddinsane

Related: Error message “sudo: unable to resolve host (none)” – Melebius Jul 20 '19 at 15:13
Yes I've been through every post I could dig up on the web on this subject. I only have SSH access and I can't edit anything because I can't sudo. (No, 'asimov' is not in /etc/hosts but I can't change it because I can't edit, because I can't sudo. Which I said in the OP.) – Adaddinsane Jul 20 '19 at 15:36
"sudo: unable to resolve host asimov: Resource temporarily unavailable." when does that show? Cuz the sudo command should still execute. like explained here in comments: https://askubuntu.com/a/524368/15811 – Rinzwind Jul 20 '19 at 16:24

Dirty filesystem on a VPS

0 Answers0