New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More
This discussion has been closed.

Comments
my tokyo ip was verified in Indonesia by google,if i click ryzen fix ip,can it be verified as japan?@Virmach
I believe the button is for internal routing problems. Google has its own geo-ip database so the best you can do to fix the country/region binding with your ip on google is through this link: https://support.google.com/websearch/contact/ip
thank u,i'll try it
We're aware of TYOC025. We already began work on it some time ago but the situation only got worse. It rebooted every other hour and then rebooted every few minutes. Trying to get it back up and also running hardware tests to see what may need to be replaced. This will take some time.
Based on the errors though and how it's acting (pinging/online but nothing's running), I suspect a DIMM failed. Once I'm sure I'll post an official update and ETA on network status page.
I've solved the problem and it's fine now.
TYOC025 Can customers with virtual machines turn on the migration button?026,027,028,029,,,,
I was finally able to get everything temporarily functional on TYOC025.
The root problem is still not resolved.
Basically the disk holding the swap malfunctioned in some way due to memory errors and swap and virtual servers couldn't initialize as a result. Memory test didn't find any errors for the relatively brief period it ran (we'll need to later run this for several hours to a day to really find anything.) As memory errors and crashes were happening and the way swap was unloaded automatically to get it to boot, at some point the volume groups had the wrong UUIDs/metadata. Around 60 virtual servers got wiped but I dug through the backups and found the right metadata finally and restored it properly.
I'm still investigating to see what's causing the crashes. No logs whatsoever. It crashes during memory test as well but remains online longer if virtual machines don't start up, so current educated guess is RAM replacement.
Since we fixed the data issue which is most important we're comfortable moving forward with RAM swap now. We have RAM available on-site and I just ordered more to be delivered in the next 12 hours as well. Just waiting for maintenance time to be scheduled with datacenter and network status page will be updated with ETA.
Not stable enough and also not enough space. We're proceeding with RAM replacement first, and then most likely if that works we'll just send an advisory reminder to back up important files if disk issue re-appears but I'm fairly certain the potential RAM issue caused the disk issue as SMART looked healthy.
Unfortunately, several of my services are at 025, and one is not at 025, but has been suspended. . . . .
Paid migration to frankfurt WITHOUT data but broken VPS showing ram as 1.46PB in SolusVM.
Node name : FFME002
You could add your phone number in the post. might help make support faster.
I notice there is extra 5$ for 443/80 port in new order, which is unreasonable. It should be cancelled.
May I know what happened to LAKVM36 ? It has been down for 2 days
One week has passed, no answer to the ticket, vds unavailable. Great hoster

Ryzen Migrate still Spinning and spinning after time out.
Nice my BF special deal $9.92, 1vcpu, 2.8gb ram, 35gb disk & 5.37tb bandwidth deal is now migrated to Ryzen 😍
@VirMach I've received 5 emails from your system (the exact same content) within the last 3 hours.
You may want to check on your end why multiple instances of the mail is being sent.
me toooo
the network of LAXA019 is so so so bad, even it's very difficult to SSH

Just got email #6.
Hello, my vps in tyoc25 couldnot be connected, in the Rescue mode. and my data may be loss.
Maybe you are receiving one for each service that is still on the older Xeon nodes and needs to be migrated?
I got two of them and got excited due to...
But Miami doesn't seem to be available for migrations yet.
I received only four email notification until now. But would be better if the emails contain the affected services name or IP address. Or all older (not Ryzen based) VM affected now? (not clear for me).
The email content: https://i.ibb.co/2P8q8Lb/2022-06-22-093951.png
Probably in the next day's I can start to migrate my VMs manually, but i'm worry because of my first experience. I migrated previously only one but the new VM not booted, error messages via VNC, not worked the reinstall on SolusVM etc).
Edit: sorry, if I understood correctly, this is a generic notification only, and they will send notification for each affected services in the future.
oh, wow! that'll be interesting to see. I'm at email #11 so few more to go I guess
Same here, free migration to Frankfurt, yabs below.
Yo man, I migrated to LAXA025, the horrible and terrible network congestion...
I want to roll back to the shitty ColoCrossing San Jose, could Virmach add an roll back BUTTON?
I saw the migration email, will you continue to provide services in Seattle?