0

My rootserver's power supply died the day before and the hoster had to replace it. Since then, the server does not boot correctly anymore. Because of the sudden powerloss, it starts right in some kind of maintenance mode.

The hoster is not able to further help me and sent me the screenshot.

enter image description here I can login to the server using a remote "recovery" image (I have no access to KVM, only the hoster does) which I think is some kind of rescue image that allows me to mount my original sda (which I can do successfully).

How can I turn off the maintenance mode and boot into default mode using the rescue image? When I enter any systemctl command, it does not apply to my real system but apparently to the resuce image in RAM. I think I have to change a file on the mounted disc or something.

Please guide me out of this :-(

Update:

The support team sent me another screenshot: enter image description here

Daniel W.
  • 1,929

3 Answers3

1

Problem solved..

the second SSD in the server is damaged or not properly connected (thus the error A job is still running... for sdb).

I can mount sda but sdb is not in /dev.

Daniel W.
  • 1,929
0

Once you logged into maintenance mode, You should open vim /etc/fstab and uncomment # all the lines except UUID line. then run below commands

$systemctl daemon-reload $systemctl default

Kaviarasu G
  • 1
-1

If the server turn into recovery mode thats mean you have a bug somewhere on the boot.

Here is a common problem with some hardware.

Just boot from a CD and install driver-nonfree package to fix the boot. Maybe chroot can help you to make things work.

P0pR0cK5
  • 350