I migrated my VPS from DAL10GKVM7 to LAXA011 and I have tried almost the templates in the SolusVM but failed to boot with message "Booting from Hard Disk... error: invalid arch-independent EL

(Quote)

(Quote)

The button appears for me and i get an error when I try to migrate. I gave details about this in the migration special thread.

When I press the ryzen button, I get the error message " We failed to submit the request. Please try again tomorrow "

(Quote)

almalinux 8.3 installed and worked except for the networking part but debian 11 failed at grub with message `error: file /boot/grub/i386-pc/normal.mod' not found. I didn't verify other templates.

script is likely trivially simple with no error checking or handling.

And here comes the thing that disappointed me:. After one hour of a support call, technicians found that.... RHEL-based images do not work on this custom setup!. That disappointed me a bit. Instead of

After one of my VM migration it was not able to boot, and the OS reinstall also not worked on the SolusVM, I got several and various error messages etc.. Luckily I was able to solve it with a LET comm

HH sure is having issues lately... My only issue ATM is my home ip address shows error code 500 when hitting manage.hosthatch.com (the old panel) every other ip I have can load it fine...

Chrome shows funny errors for this, Firefox shows less funny errors.

(Quote)

You'd need to explain what happened in the ticket better for us to be able to help you. Unless it's some weird error on our end that I haven't seen before it sounds like you would have just picked Los

Thanks for all your time, this is after action what i have mentioned in previous comment (reboot in rescue sys & disk checking + correction of some errors is VPS again working and reachable).

After e2fsck and some error corrections it works now and is reachable, so i assume something on disk happened/ or some errors by raid controller, but VPS was nearly to idling, no load was there

anyone succeed install win2002 from the cp? it gave me "windows failed to start" error on windows boot manager

Which will result in a Deployment error if you still choose it.

On top of the alpha test, we also had an entire node migrated early 1:1 from a dual E5 and everything went really well. That one is actually also on an XPG disk mostly, no failure or errors, and nothi

e: Something is wrong with their status page, though, SSL error