ASU Web Services

[ASU Web Services @ASUCloud]

@olesovhcom It shouldn't take this long to remove the bad router, and restart services to the rest of the world!

[ASU Web Services @ASUCloud]

@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!

[ASU Web Services @ASUCloud]

@VergeresP It means the status is normal. It will have a normal status if it's in normal boot or rescue64-ovh but has ping and no faults logged.

[ASU Web Services @ASUCloud]

@VergeresP Have you tried to change boot option, reselect Rescue64-pro and enter a different email address, and then reboot? This should work

[ASU Web Services @ASUCloud]

@FactoryOyster @olesovhcom No problem at all. Hope you're back up and running soon and your business recovers.

[ASU Web Services @ASUCloud]

@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.

[ASU Web Services @ASUCloud]

@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

[ASU Web Services @ASUCloud]

@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?

[ASU Web Services @ASUCloud]

@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.

[ASU Web Services @ASUCloud]

@FactoryOyster @olesovhcom Are you in Rescue64-pro or rescue64-ovh?

[ASU Web Services @ASUCloud]

@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

[ASU Web Services @ASUCloud]

@leviBKL @olesovhcom Does it boot into Rescue64-pro ok? It only has issue in normal boot?

[ASU Web Services @ASUCloud]

@leviBKL @olesovhcom Have you tried checking IPMI for any issues?

[ASU Web Services @ASUCloud]

@ProchSerj @IamAgonia @olesovhcom No you won't get the password until they boot it into Rescue64-pro. They are still working on it

[ASU Web Services @ASUCloud]

@ProchSerj @IamAgonia @olesovhcom Not sure what that one is I'm afraid. Haven't seen that before

[ASU Web Services @ASUCloud]

@IamAgonia @ProchSerj @olesovhcom That was a generic email sent to all customers in SBG1 who weren't destroyed.

[ASU Web Services @ASUCloud]

@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.

[ASU Web Services @ASUCloud]

@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

[ASU Web Services @ASUCloud]

@JMarcBlanchard @olesovhcom Yes, any Linux utility will work in rescue mode. Rsync / NFS / scp etc