@olesovhcom@olesovhcom - How long until services restored? Why is there no backup/roll back plan? And why does it take nearly an hour to fix a config issue!
@FactoryOyster@olesovhcom Yes. Like i said ours was like this for 5 or more days. If you can't reboot or launch IPMI due to intervention (you'll get that error in the manager) then you'll have to wait until they finish what they're doing. SSH will connect because the network is connected.
@FactoryOyster@olesovhcom Yes. That means OVH are still working on it. They have the process much quicker now. Ours was pinging for 5 days or so before we got it back but i know they have been streamlining the process
@FactoryOyster@olesovhcom Have you tried to change the boot option again, reselect Rescue64-pro and enter an email, then reboot it. See if you get the email this time?
@FactoryOyster@olesovhcom Has your server previously been in rescue64-ovh (internal)? If it's already been in internal Rescue then you should have got an email with password. If it hasn't then they will likely put it in internal rescue, then you'll get an email when they boot it back in to Rescue64-pro.
@leviBKL@olesovhcom Did you check the disks and raid from Rescue64-pro?
If not reboot into rescue and then check they're intact.
You can also try netboot with the ovh kernel incase the ondisk kernel is the issue
@FactoryOyster@olesovhcom When your server is up you'll get an email with the credentials to login to the rescue system.
It's up to you what you do within the rescue system. I'd recommend doing a disk check and back up before normal boot.
There should be no issues but a backup is advisable.
@FactoryOyster@olesovhcom You'll get an email when it's ready and in Rescue64-pro. It's in rescue64-ovh at the moment i assume?
Feel free to DM if you need any assistance