SerjProch

@qtnw_ @olesovhcom Je recommande d'écrire au support technique et d'indiquer votre numéro de commande. J'ai également passé une commande. J'ai attendu 12 jours. Il n'y a eu aucun résultat. J'ai écrit au support technique et le lendemain, la commande a été exécutée.

@olesovhcom Toujours en attente de nos 3 serveurs dédiés qui étaient situés en SBG2, payés à l'année. Annoncez des dates ou au moins une progression chiffrée.

We have a major incident on SBG2. The fire declared in the building. Firefighters were immediately on the scene but could not control the fire in SBG2. The whole site has been isolated which impacts all services in SGB1-4. We recommend to activate your Disaster Recovery Plan.

@biondiclaudio4 @olesovhcom IMHO: The rack S332A07 is on the 3rd floor. It does not exists here travaux.ovh.net/vms/index_sbg3…, because they haven't had time to update VMS page yet. Recently, the same situation was with the S350xxx racks, but later the page was updated and these racks became visible.

@olesovhcom I repeat a question hoping to have an answer. why do i see this information in my panel? Strasburgo (SBG3) - Francia Rack S332A07 DOWN ID del server 1266953 Rack S332A07 doesn't exist and you said that all 61e and 62e should be migrated to Rack 350 or Rack 351. Is a mistake?

@kikko85dj @olesovhcom They will switch boot mode from "internal rescue" to "customer rescue" and then you will recieve email like "Access settings for RESCUE mode". There will be password and instruction what to do next 🙂

@olesovhcom We need to wait the email? How can I know when it is ready?

@Joodalhawa You should check your hardware (memory, disk sectors, etc.) and extract the most critical data before rebooting to the server’s operating system. See this guide: help.ovhcloud.com/en/faq/strasbo…

@ProchSerj Can you help me prochserj 🥺

@Joodalhawa @FactoryOyster @olesovhcom You should check your hardware (memory, disk sectors, etc.) and extract the most critical data before rebooting to the server’s operating system. See this guide: help.ovhcloud.com/en/faq/strasbo…

@ProchSerj @FactoryOyster @olesovhcom Can any one help me! What should I do when I get email my server on rescue mode I am really confused what should I do?

@olesovhcom >> If you have a request, DM me My request to ovh or ovh request to me? What kind of request? I've recieved the email only with general info about that my service will be put back into service in SBG3 by 23 April 2021 at the latest.

Update April,18 12am BM: SBG1/E > Croix > SBG3 - Floor 5: all servers are there and we fix the issues, rack after rack, 24/7 - Floor 3: first racks comes by Tue VPS: - restart SBG2 in SBG3, case « no paid backup ». new HW will be in SBG3 in 10 days If you have a request, DM me

@FactoryOyster @olesovhcom What is boot mode in your control panel on general information page of your server? if "rescue64-ovh (Internal rescue)", then it is for internal diagnostic by ovh. Wait until they switch it to "rescue64-pro (Customer rescue system (Linux))" and they'll send you email with psw

@olesovhcom Everything showing of backend and server PING but STILL waiting for Recovery Password???? Just send the email already please 😓

@biondiclaudio4 @olesovhcom Your server is already in the SBG3 building (3rd or 5th floor), but not yet loaded into the rack. They want to place half of the servers on the 5th floor and the other half on the 3rd floor. Hopefully it will be put in the rack soon, and then you will see the rack number.

@olesovhcom Hi Octave. can you tell me why my dedicated server that was in sbg1 on the panel I still seeing it on the old rack 61E04 and not on one of the new racks S350 or S351?

@Charley25862957 @olesovhcom WIP (Work In Progress): BM (Bare Metal): SBG1/E in SBG3 (**through** Croix) SBG2 in GRA (new HW) IMHO: HW - hardware

@olesovhcom When S350A08 will be UP?

Update April,17 2am SBG global status: BM: 98% UP pCI: 95% UP VPS: 95% UP HPC/pCC: 85% UP WIP: BM: SBG1/E in SBG3 (thought Croix) SBG2 in GRA (new HW) VPS: SBG2 in SBG3 (need new HW) We keep working 24/7.

@olesovhcom "thought Croix" or "through Croix"? I do not understand

@biondiclaudio4 @kikko85dj @olesovhcom Stai vedendo il numero di rack da SBG1 perché il tuo server non è stato ancora posizionato in un rack nell'edificio SBG3. Non appena il server viene posizionato nel nuovo rack, vedrai il nuovo numero nel pannello di controllo.

@kikko85dj @olesovhcom ciao. Da quando vedi questa informazione sul pannello del rack S351A02? noi vediamo data center SBG3, ma ancora il vecchio rack di SBG1.

@olesovhcom Useful information from the article - 0% How does it relate to the scope of work performed today in the context of SBG1 / E?

@kikko85dj @kevfication @olesovhcom I, too! And my friend too! Business class tickets for us please😎

@kevfication @olesovhcom I’m with you, is unbelievable all this time.

@IamAgonia @ASUCloud @olesovhcom Well, I will hope that my data also remained in place. I will wait 1 day. If it is not switched to the normal rescue boot mode, then I will write to the support.

@ProchSerj @ASUCloud @olesovhcom Everything is back now and recovered. Went back into internal rescue, but they changed me to regular rescue. And now im in regular hardrive not

@IamAgonia @ASUCloud @olesovhcom Is your data still intact after "rescue64-recycling (Rescue recycling 64bits)" boot mode? Didn't they delete them?

@ProchSerj @ASUCloud @olesovhcom mine is back UP. 100% in hard drive reboot. Contacted support and they responded in record time. 10 minutes.

@ASUCloud @IamAgonia @olesovhcom But I still can't log into the server, because don't know the password. If they recycled (removed) my data, I'll shoot myself 😪

@ASUCloud @IamAgonia @olesovhcom Oh.. just now it was switched to rescue64-ovh (Internal rescue)

@IamAgonia @olesovhcom

@IamAgonia @olesovhcom my server now is also in "rescue64-recycling (Rescue recycling 64bits)" boot mode. ping is ok, but I can not login. I do not know password. I am afraid they gonna to recycle my data (deleting them). 🙁 HELP!