★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More

Ademan · July 2022

@FrankZ said: Am I correct in assuming that you do not wish to attempt to reinstall the VPS?

Yeah, no one to blame but myself on this, but my last backup is unacceptably old.

lolee · July 2022

@MallocVoidstar said:

@lolee said:
$20.57/YR $16.46/YR (RECURRING)
ORDER: https://virmach.com/special-offers/

2.5GB RAM -- Limit 800 Quantity
50GB NVMe
2 vCore Ryzen* CPU
6TB @ 1Gbps Bandwidth
1x IPv4 Address

Will this VPS be available again?

The first post says "This will be the lowest prices we will offer for Ryzen, over the next 12 months." and this deal is no longer available. So check back March 2023.

Price is not important
Can increase the price
Just want this configuration and Tokyo line
So when can you put a new one on the shelves

lolee · July 2022

@MallocVoidstar said:

@lolee said:
$20.57/YR $16.46/YR (RECURRING)
ORDER: https://virmach.com/special-offers/

2.5GB RAM -- Limit 800 Quantity
50GB NVMe
2 vCore Ryzen* CPU
6TB @ 1Gbps Bandwidth
1x IPv4 Address

Will this VPS be available again?

The first post says "This will be the lowest prices we will offer for Ryzen, over the next 12 months." and this deal is no longer available. So check back March 2023.

If there is better service and quality
Price increase two times is also acceptable

Reaperofpower · July 2022

@VirMach any update on this ticket?

714343

s12321 · July 2022

@netrix said:

@s12321 said:

@netrix said:

@s12321 said:
@VirMach LAXA024 has no internet for more than a week, looks like the gateway has not plugged in.

no problem at all with laxa024. my vps has 9 days uptime

My subnet don't have internet at the moment. Most machines are "online" but not connecting internet. If I know there is a working gateway, i may manually point to that one.

up & running and connected to internet for 9 full days rn. the gateway is: 149.57.138.1, os Debian 11 ryzen compatible.

The vps in the same node is under 149.57.137.x/24 subnet, arrived on 11th, and no internet since then. Debian 11 too, you are lucky.

netrix · July 2022

@s12321 said:

@netrix said:

@s12321 said:

@netrix said:

@s12321 said:
@VirMach LAXA024 has no internet for more than a week, looks like the gateway has not plugged in.

no problem at all with laxa024. my vps has 9 days uptime

My subnet don't have internet at the moment. Most machines are "online" but not connecting internet. If I know there is a working gateway, i may manually point to that one.

up & running and connected to internet for 9 full days rn. the gateway is: 149.57.138.1, os Debian 11 ryzen compatible.

The vps in the same node is under 149.57.137.x/24 subnet, arrived on 11th, and no internet since then. Debian 11 too, you are lucky.

maybe you could try use ryzen fix ip button under "switch ip"? my other vps works after clicking that button.

julensm · July 2022

NYCB040 server was down for several hours, it's now back online. Unfortunately, my NYCB030 server is still 'no bootable device'.

karjaj · July 2022

@FrankZ said:
@Ademan - I am seeing comments that DALZ004 was working on July 7th and I have messaged the poster to see if his VM on DALZ004 is still working at this time. Figure we can make sure the node is up first then go from there. Am I correct in assuming that you do not wish to attempt to reinstall the VPS?

Don't add or bump tickets, as I expect they will just be merged and dropped to the bottom of the queue.

My DALZ004 VPS was migrated from Xeon and if I remeber, I fixed manually network file. Now I tried to re-install, template install from Solus, VNC ok but not newtork. Also no network if try to install from ISO. Reconfigure-Network not fix problem. Not yet tested fix network config file.

s12321 · July 2022

@netrix said:

@s12321 said:

@netrix said:

@s12321 said:

@netrix said:

@s12321 said:
@VirMach LAXA024 has no internet for more than a week, looks like the gateway has not plugged in.

no problem at all with laxa024. my vps has 9 days uptime

My subnet don't have internet at the moment. Most machines are "online" but not connecting internet. If I know there is a working gateway, i may manually point to that one.

up & running and connected to internet for 9 full days rn. the gateway is: 149.57.138.1, os Debian 11 ryzen compatible.

The vps in the same node is under 149.57.137.x/24 subnet, arrived on 11th, and no internet since then. Debian 11 too, you are lucky.

maybe you could try use ryzen fix ip button under "switch ip"? my other vps works after clicking that button.

There is no ryzen fix ip button under "switch ip", but there is $3 or $5
Their tbs tool says Node Online: false so same node, your subnet is ok, mine is not.

FrankZ · July 2022

@s12321 - Just out of curiosity if you manually set the gateway to 149.57.138.1 and the netmask to 255.255.254.0 or 255.255.252.0 and then reboot. Does the network work?

Sometimes the Ryzen fix IP button is there, sometimes it is not. I am not sure why.

Their tbs tool says Node Online: false

Don't put too much faith in this on Ryzen nodes.

--

@julensm - "No bootable device" is something that VirMach will need to fix, just wait it will get fixed eventually.

--

@lolee - I would expect that VirMach will start selling Tokyo VPS again after the transition to Ryzen is complete. I can't say when that will be exactly, but I do expect it to happen.

FrankZ · July 2022

@Totti said: @FrankZ my ip:185.97.146.236, Can't access control center,
The page says "Operation Timed Out After 90001 Milliseconds With 0 Bytes Received",

I also have a VPS on this node and have the same issue as you. This node NYCB036 is having some issues and is offline. VirMach is aware of this, and it is on the priority list, but the DC has a backlog of work and they are being slow to resolve this. There is nothing more you, me, or Virmach can do until the DC works through the backlog. Good news is that it will be resolved soon™ (as in before CC gets ipv6)

VirMach · July 2022

@FrankZ said: @lolee - I would expect that VirMach will start selling Tokyo VPS again after the transition to Ryzen is complete. I can't say when that will be exactly, but I do expect it to happen.

Tokyo has a ton of IPv4 left over and space. It's also relatively quick to set up, I just needed to avoid it because while it's a highly desired location, it's also highly support-intensive and no good way of automatically knowing who to move there so we have to stick to nearby locations first.

Otherwise honestly xTom has the best track record in setup for Tokyo, we could have probably got all the servers stuck currently in DC queues set up last week in Tokyo even including shipping and customs but we'd probably have 10,000 tickets and thousands of broken VMs from Ryzen button being smashed to pieces. I'd assume even more so now, since the networking problems have been ironed out.

tototo · July 2022

If only I could migrate from DALZ003 to DALZ004 or DALZ007 so I could play with it.
(Yes, I know it is almost impossible from a technical or business standpoint)

Yunen · July 2022

@FrankZ said:

@Yunen said: If you don't know how to fix these problems, contact the relevant technical experts instead of trying to fix the problems by yourself while learning.

IMO this is a rather naive comment. You do realize don't you, that many of these issues were the result of DC hands, hardware manufacturer, and industry leading software. "experts" ? Besides what good is it really going to do if you try to make yourself feel better by taking a dump on VirMach?

Hahaha, I think you should figure it out why more and more customer angry with vir (in your words it's "takeing a dump on vir").
I miss VirMach before the migration of Ryzen, although the performance is a bit worse, but stable.
Allow me to make one last grumble~

risturiz · July 2022

@tototo said:
If only I could migrate from DALZ003 to DALZ004 or DALZ007 so I could play with it.
(Yes, I know it is almost impossible from a technical or business standpoint)

Are you sure about that?

uptime
13:08:26 up 8 days, 19:40,  1 user,  load average: 0.15, 0.17, 0.09

DALZ003 is perfect actually :-) ... Network was fixed too

JDMcPea · July 2022

I'm on DALZ008 and haven't been able to get my VPS online. It will boot up everytime but using Virmach VNC see "A start job is running for Wait for Network to be Configured" which stalls the boot for about 2.5 minutes.

Once it starts I run "ip a" and get this:

Troubleshooter says:

Main IP pings: false
Node Online: false
Service online: online
Operating System: linux-ubuntu-16.04-server-x86_64-minimal-latest

Since it's booting I'd say the node is considered to be online and the troubleshooter is wrong.

Have tried everything in the control panel and Virmach management including trying to reinstall an OS (doesn't resinstall anything), mounting TinyCore ISO (won't boot at all until unmounted), reconfigure networking (has no effect).

Is it possible to reconfigure networking from the command line to get this VPS online and if so how would you go about it?

The OS is Ubuntu 20 server, troubleshooter says it's 16.04 because that's the last one I tried to install from Virmach management page. I've also tried the Ryzen compatible templates, no luck

donb · July 2022

@FrankZ said:

@Nothingsoul said: Problems here too, at RYZE.DEN-Z001.VMS node. Various weeks no booting

@donb

I am on DENZ001 and have not had any issues at all, so the node is up and working well.
Lets see if we can get you going regarding your VM...

Have you gone into SolusVM* panel and made sure that no ISOs are mounted?
This will keep your VM from booting.

Have you tried installing a "Ryzen Compatible" template version of ubuntu also from the SolusVM panel, not the billing panel.

Does your VM show online in the billing panel ? If so what errors do you show when you access via VNC ?

*The SolusVM panel can be accessed by clicking the "VPS Control Panel" button from your VM in the billing panel.

Hey, thanks for trying to help me out with fixing things.

It shows TinyCoreISO as mounted, but in the CDROM settings of the SolusVM, the dropdown has only TinyCoreISO and doesn't show as mounted. This is a weird mismatch within the SolusVM itself. Tried mounting & unmounting, but there's no change in the state.
I haven't tried installing (reinstalling) any OS due to the fear of data loss. I suppose I'd lose the data post reinstalling & hence I'm not trying that out.
VM shows offline in both Billing & SolusVM panels. The VNC connection shows "Authentication failed" from both the panels. Rescue mode fails since the IP:port for SSH gets timed out. Telnet on port 22 of the said IP fails as well.

drizbo · July 2022

It will all be alright on Monday.

FrankZ · July 2022

@donb said:

@FrankZ said:

@Nothingsoul said: Problems here too, at RYZE.DEN-Z001.VMS node. Various weeks no booting

@donb

I am on DENZ001 and have not had any issues at all, so the node is up and working well.
Lets see if we can get you going regarding your VM...

Have you gone into SolusVM* panel and made sure that no ISOs are mounted?
This will keep your VM from booting.

Have you tried installing a "Ryzen Compatible" template version of ubuntu also from the SolusVM panel, not the billing panel.

Does your VM show online in the billing panel ? If so what errors do you show when you access via VNC ?

*The SolusVM panel can be accessed by clicking the "VPS Control Panel" button from your VM in the billing panel.

Hey, thanks for trying to help me out with fixing things.

It shows TinyCoreISO as mounted, but in the CDROM settings of the SolusVM, the dropdown has only TinyCoreISO and doesn't show as mounted. This is a weird mismatch within the SolusVM itself. Tried mounting & unmounting, but there's no change in the state.

I haven't tried installing (reinstalling) any OS due to the fear of data loss. I suppose I'd lose the data post reinstalling & hence I'm not trying that out.

VM shows offline in both Billing & SolusVM panels. The VNC connection shows "Authentication failed" from both the panels. Rescue mode fails since the IP:port for SSH gets timed out. Telnet on port 22 of the said IP fails as well.

If it shows a mounted ISO it will not boot. I understand that you have tried to unmount it in SolusVM without success, but this is probably the reason it will not boot. Just throwing this out there, but did you try unmounting from the billing panel as well?

I do understand you not wanting to reinstall if you have data on there you don't want to lose. Based on what you have said, it might still be broken after reinstall anyway.

I may be completely wrong here but another possibility is that your VM was broken because of some of the SolusVM issues VirMach mentioned earlier. I expect that VirMach is aware of these, and if there are, and I am only guessing here, 3% like this, that could be a couple hundred broken ones that have to be fixed one at a time, so it may take a while to fix all of them. Good news is that my Denver VM is really fast all around, so when you do get going I think you are really going to like your VirMach VM in Denver.

FrankZ · July 2022

@JDMcPea said: Since it's booting I'd say the node is considered to be online and the troubleshooter is wrong.

You are correct the trouble shooter is wrong about the node being off line. The trouble shooter does not work correctly on Ryzen yet in this regard.

@JDMcPea said: Is it possible to reconfigure networking from the command line to get this VPS online and if so how would you go about it?

Yes you can manually reconfigure networking from VNC. With Ubuntu 20 you can try using sudo nmtui and once you get networking configured I expect you should be good to go. Use static network settings shown in SolusVM network for IP, gateway, and netmask, not DHCP.

If you have any further issues just ask.

EDIT: If you do not have nmyui available here is a tutorial on how to edit netplan file. https://linuxize.com/post/how-to-configure-static-ip-address-on-ubuntu-20-04/

s12321 · July 2022

@FrankZ said:
@s12321 - Just out of curiosity if you manually set the gateway to 149.57.138.1 and the netmask to 255.255.254.0 or 255.255.252.0 and then reboot. Does the network work?

Sometimes the Ryzen fix IP button is there, sometimes it is not. I am not sure why.

Their tbs tool says Node Online: false

Don't put too much faith in this on Ryzen nodes.

--

@julensm - "No bootable device" is something that VirMach will need to fix, just wait it will get fixed eventually.

--

@lolee - I would expect that VirMach will start selling Tokyo VPS again after the transition to Ryzen is complete. I can't say when that will be exactly, but I do expect it to happen.

Thanks @FrankZ, tested above suggestion, they cannot route (even on rescue OS). My subnet's dhcp is working on 149.57.137.1, but there is no route to the 1.1.1.1 etc... looks like the internet is unplugged for this subnet...

tototo · July 2022

@risturiz said:

@tototo said:
If only I could migrate from DALZ003 to DALZ004 or DALZ007 so I could play with it.
(Yes, I know it is almost impossible from a technical or business standpoint)

Are you sure about that?
uptime
13:08:26 up 8 days, 19:40,  1 user,  load average: 0.15, 0.17, 0.09
DALZ003 is perfect actually :-) ... Network was fixed too

Yes, DALZ003 is working fine so I'm interested in DALZ004 and DALZ007.

# uptime
 20:22:55 up 9 days,  1:52,  1 user,  load average: 0.15, 0.04, 0.01

tototo · July 2022

@s12321 said:

@FrankZ said:
@s12321 - Just out of curiosity if you manually set the gateway to 149.57.138.1 and the netmask to 255.255.254.0 or 255.255.252.0 and then reboot. Does the network work?

Sometimes the Ryzen fix IP button is there, sometimes it is not. I am not sure why.

Their tbs tool says Node Online: false

Don't put too much faith in this on Ryzen nodes.

Thanks @FrankZ, tested above suggestion, they cannot route. My subnet's dhcp is working on 149.57.137.1, but there is no route to the 1.1.1.1 etc... looks like the internet is unplugged for this subnet...

Have you tried setting it to 149.57.138.1 manually without DHCP? I remember that it worked for me at another node.

FrankZ · July 2022

@s12321 +1 what @tototo said. You will need to turn DHCP off by configuring the network interface as static with the above settings. Still may not work, but it definitely will not work with DHCP active.

s12321 · July 2022

@tototo said: Have you tried setting it to 149.57.138.1 manually without DHCP? I remember that it worked for me at another node.

yes, static and no internet (as in cannot find route and ping switch and external ip address).

jakechen · July 2022

ping.pe

@VirMach DALZ008 node still have some network issre with NY,100% package lost

JDMcPea · July 2022

@FrankZ said:

@JDMcPea said: Since it's booting I'd say the node is considered to be online and the troubleshooter is wrong.

You are correct the trou

Thanks @FrankZ. Unfortunatly my VPS will no longer boot into Ubuntu so I can't try your suggestion. I think the last thing I did before it stopped working was try to reinstall through the CP Ryzen Compatible Debian 10. Now when it boots VNC says:

Booting from Hard Disk...
error: file '/boot/grub/i386-pc/normal.mod' not found
Entering rescue mode...
grub rescue>

I checked that folder and there is a file called normal.mod there... I tried some commands found online working from the grub rescue CLI but got errors. For example if I enter "ls (hd0, msdos1)" I always get the error "error: missing the ')" symbol. The command "insmod normal" doesn't work as the file can't be found. And more of the same.

BUT have found that when I click on Rescue Mode in the CP it now works- and I can SSH into Rescue mode. So at least in that respect my virmach IP address is working. Tried this to fix:

rescue # lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sr0     11:0    1 1024M  0 rom
vda    254:0    0   25G  0 disk
├─vda1 254:1    0 24.8G  0 part
└─vda2 254:2    0  256M  0 part
vdb    254:16   0  1.1G  0 disk
└─vdb1 254:17   0  1.1G  0 part /
rescue # mkdir /mnt/root
rescue # mount /dev/vda1 /mnt/root
rescue # cd /mnt/root
rescue # chroot /mnt/root
chroot: failed to run command ‘/bin/bash’: No such file or directory
rescue #

Ran ifconfig:

rescue # ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 45.xx.xx.xx  netmask 255.255.255.0  broadcast 45.xx.xx.xx
        inet6 xxxx::2xxx:fxx:d0e8:2xx  prefixlen 64  scopeid 0x20<link>
        ether 00:26:3d:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 21211  bytes 74042587 (70.6 MiB)
        RX errors 0  dropped 559  overruns 0  frame 0
        TX packets 6160  bytes 631922 (617.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

If I could just mount an ISO and boot from it or resinstall any operating system I'd probably be good to go but none of them are working for me.

Is there a way to reinstall OS from Rescue Mode? Can use suggestions on what to try next as I am stuck.

FrankZ · July 2022

@JDMcPea said: Is there a way to reinstall OS from Rescue Mode?

IIRC @AlwaysSkint had a way to do that, so I will tag him and see what shakes out.

Also to mount the O/S from rescue mode

After you login via ssh execute the following commands.

Mount the root partition of the O/S install with:
mount /dev/vda1 /mnt

Then mount the O/S by issueing the following commands:

mount -t proc none /mnt/proc
mount --rbind /sys /mnt/sys
mount --rbind /dev /mnt/dev

If that all goes well then mount

ln -s /etc/resolv.conf /mnt/etc/resolv.conf

Then finally chroot into the mounted O/S

chroot /mnt /bin/bash

@s12321 said: yes, static and no internet (as in cannot find route and ping switch and external ip address).

Can you please post the results of ip show route

@jakechen said: @VirMach DALZ008 node still have some network issre with NY,100% package lost

That is not a problem that VirMach can fix as it is on the New York end.

s12321 · July 2022

@FrankZ said:

@JDMcPea said: Is there a way to reinstall OS from Rescue Mode?

IIRC @AlwaysSkint had a way to do that, so I will tag him and see what shakes out.

Also to mount the O/S from rescue mode

After you login via ssh execute the following commands.

Mount the root partition of the O/S install with:
mount /dev/vda1 /mnt

Then mount the O/S by issueing the following commands:
mount -t proc none /mnt/proc
mount --rbind /sys /mnt/sys
mount --rbind /dev /mnt/dev
If that all goes well then mount
ln -s /etc/resolv.conf /mnt/etc/resolv.conf
Then finally chroot into the mounted O/S

chroot /mnt /bin/bash

--

@s12321 said: yes, static and no internet (as in cannot find route and ping switch and external ip address).

Can you please post the results of ip show route

@jakechen said: @VirMach DALZ008 node still have some network issre with NY,100% package lost

That is not a problem that VirMach can fix as it is on the New York end.

Thanks @FrankZ

default via 149.57.138.1 dev ens3 onlink
149.57.137.0/24 dev ens3 Proto kernel scope link src 149.57.137.(hidden)

also,
255.255.n.0, n=254 subnet 136, subnet n=252 subnet 139 both not working.

it's so sad to discuss this here. not sure if anyone is on the same boat.

not sure if @VirMach needs any volunteers ...

JDMcPea · July 2022

@FrankZ said:

Also to mount the O/S from rescue mode>
After you login via ssh execute the following commands. ...

Tried but did not work, here is the error:

rescue # mount /dev/vda1 /mnt
rescue # mount -t proc none /mnt/proc
rescue # mount --rbind /sys /mnt/sys
rescue # mount --rbind /dev /mnt
rescue # ln -s /etc/resolv.conf /mnt/etc/resolv.conf
ln: failed to create symbolic link '/mnt/etc/resolv.conf': No such file or directory

Howdy, Stranger!

Categories

In this Discussion

★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More

Comments

714343

Howdy, Stranger!

Quick Links

Categories

In this Discussion

★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More

Comments

714343