Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More - Page 76
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.

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

17374767879339

Comments

  • Invoice 1396995,Tokyo, can I set it today?

  • @360717125 said: Invoice 1396995,Tokyo, can I set it today?

    No. Next batch on Tuesday if everything goes good with shipping.

    Thanked by 1FrankZ
  • nobenobe Member

    @tooyoung said:
    Debian 11 restart via ssh, vps does not start, must be boot manually in the panel. Anyone in a similar situation? Still my problem?

    I have some similar issue:
    Debian 11
    Node:TYOC039

    I have been using the vps around one week. Everything is going smooth recently, but everyday the system will shutdown automatically at a random time, I have to boot it again manually through the panel, and everything back to happy again.

    Not sure if the system is still in test version, or only me. Anyway looks like we are 2 now.

  • totototototo Member
    edited April 2022

    TYOC039 + Ryzen Special 384 + Almalinux Template

    Mounted ISO ISO Boot Installation Note
    AlmaLinux 8.4 Boot ISO Boot failed - Could not read from CDROM
    AlmaLinux 8.4 Boot ISO Offline - -
    Alpine 3.1.0 64 Bit ISO OK OK? -
    CentOS 6.8 x86_64 Minimal ISO OK Error? You do not have enough RAM to install
    CentOS 7 Server x64 ISO OK Error? -
    CentOS-8-x86_64-1905-boot (ISO) Kernel Panic - -
    Debian 10 Server x64 ISO OK OK? -
    Debian 11.2 ISO Offline - -
    netboot.xyz (ISO) OK OK? Ubuntu 20.04 (Legacy)
    netboot.xyz (ISO) OK OK? Debian 10
    RockyLinux 8.5 Boot ISO Offline - -
    Ubuntu 21.04 Live Server x64 ISO Offline - -
    Ubuntu 20.04 Live Server x64 ISO Kernel Panic - -

    (edit) Some of the errors may be due to less RAM and may not result on machines with more RAM.

  • @leendon said:

    @riofredinand said:
    Node 40 YABS. IO and network issues seems to.

    What version of the system do you install, why can't I log in to SSH after installation?

    I install debian10 by mount iso boot.xyz and connect through VNC.

  • FrankZFrankZ Veteran
    edited April 2022

    Node39 - Installed Alma8 Template, then installed from Centos7 Server ISO with default disk setup. Changing disk from LVM to regular partitions caused crashes during install or kernel panic after install. Disk and network look good.

    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    #              Yet-Another-Bench-Script              #
    #                     v2022-02-18                    #
    # https://github.com/masonr/yet-another-bench-script #
    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    
    Sun Apr  3 06:27:05 CDT 2022
    
    Basic System Information:
    ---------------------------------
    Processor  : AMD Ryzen 9 5900X 12-Core Processor
    CPU cores  : 1 @ 3693.054 MHz
    AES-NI     : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM        : 1.4 GiB
    Swap       : 1020.0 MiB
    Disk       : 34.0 GiB
    
    fio Disk Speed Tests (Mixed R/W 50/50):
    ---------------------------------
    Block Size | 4k            (IOPS) | 64k           (IOPS)
      ------   | ---            ----  | ----           ----
    Read       | 268.44 MB/s  (67.1k) | 379.26 MB/s   (5.9k)
    Write      | 269.15 MB/s  (67.2k) | 381.26 MB/s   (5.9k)
    Total      | 537.59 MB/s (134.3k) | 760.52 MB/s  (11.8k)
               |                      |
    Block Size | 512k          (IOPS) | 1m            (IOPS)
      ------   | ---            ----  | ----           ----
    Read       | 585.68 MB/s   (1.1k) | 847.41 MB/s    (827)
    Write      | 616.80 MB/s   (1.2k) | 903.85 MB/s    (882)
    Total      | 1.20 GB/s     (2.3k) | 1.75 GB/s     (1.7k)
    
    iperf3 Network Speed Tests (IPv4):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed
                    |                           |                 |
    Clouvider       | London, UK (10G)          | 176 Mbits/sec   | 298 Mbits/sec
    Online.net      | Paris, FR (10G)           | 404 Mbits/sec   | 81.0 Mbits/sec
    WorldStream     | The Netherlands (10G)     | 416 Mbits/sec   | 565 Mbits/sec
    WebHorizon      | Singapore (400M)          | 404 Mbits/sec   | 263 Mbits/sec
    Clouvider       | NYC, NY, US (10G)         | 449 Mbits/sec   | 353 Mbits/sec
    Velocity Online | Tallahassee, FL, US (10G) | 578 Mbits/sec   | 276 Mbits/sec
    Clouvider       | Los Angeles, CA, US (10G) | 450 Mbits/sec   | 507 Mbits/sec
    Iveloz Telecom  | Sao Paulo, BR (2G)        | 281 Mbits/sec   | 337 Mbits/sec
    
    Thanked by 1tototo
  • @nobe said:

    @tooyoung said:
    Debian 11 restart via ssh, vps does not start, must be boot manually in the panel. Anyone in a similar situation? Still my problem?

    I have some similar issue:
    Debian 11
    Node:TYOC039

    I have been using the vps around one week. Everything is going smooth recently, but everyday the system will shutdown automatically at a random time, I have to boot it again manually through the panel, and everything back to happy again.

    Not sure if the system is still in test version, or only me. Anyway looks like we are 2 now.

    Me too......

    After the server was activated, I tested it, and the problems I found are as follows:
    1. Irregular automatic shutdown. The VPS found several (at least four) automatic shutdowns, most of which occurred without any action, and once suddenly interrupted while executing the “apt upgrade” command.
    After this problem occurred, I checked the “/var/log/messages.1” file and used the “cat messages.1 | grep error” command to check the error message, the prompt is as follows:
    root@jp:/var/log# cat messages.1 | grep error
    Dec 28 22:52:07 debiantemplate kernel: [ 2.926642] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 01:23:23 jp kernel: [ 1.177559] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 01:28:58 jp kernel: [ 1.438291] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 01:37:06 jp kernel: [ 1.191632] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 02:00:08 jp kernel: [ 1.323795] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 15:49:19 jp kernel: [ 0.950615] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 21:41:05 jp kernel: [ 1.069917] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    2. The server cannot be restarted using the "reboot" command. I tested it twice and each time it failed to reboot, only rebooted in the control panel.
    3. The network connection is unstable. The normal ping response time is about 60ms, and it often happens that the ping response time suddenly jumps to more than 200ms and there is packet loss. Since I'm from China, this might be due to GFW.

    Due to poor English, the above text is translated by google translate. The problems found above are for reference.

  • would someone give a download link so we can check the speed?

  • VirMachVirMach Member, Patron Provider

    Templates updated, let me know if it's better or worse.

    Thanked by 1Xrmaddness
  • nick_nick_ Member

    I'm on the node TYO-C040. I could install Debian 10 ISO and upgrade to 11 just fine. Network speed outside of Japan isn't looking great currently though.

  • This is not important, but...
    Linux Almalinux 8 X86 64 Gen2 V1

  • @VirMach said:

    @louiejordan said:
    my invoice# is 140xxxx, time is passing day by day, I don't know how long to wait.

    I can switch you over to an immediate location or refund you any time you don't wish to wait, but more Tokyo is being set up on Tuesday.

    hello
    I bought two machines at virmach. #1397158 was supposed to be in Tokyo, but it actually started in San Jose. I applied for #1405380STORAGE-500G to move to Tokyo eight days ago, but no one has responded so far. So, #1405380 apply for a refund. thanks

  • VirMachVirMach Member, Patron Provider
    edited April 2022

    @nick_ said:
    I'm on the node TYO-C040. I could install Debian 10 ISO and upgrade to 11 just fine. Network speed outside of Japan isn't looking great currently though.

    People are basically doing a constant 400Mbps to 1Gbps in network tests it seems at any given moment (and I/O.)

    Thanked by 2nick_ Xrmaddness
  • beta tester

    Looks the disk is gone again and VPS offline (try to reinstall from templates listed did not help)
    VPS ID: 652588
    Invoice #1397292 (In case the above ID not helped ) . thanks

    @VirMach said:
    Templates updated, let me know if it's better or worse.

  • VirMachVirMach Member, Patron Provider

    @derekyang said:
    beta tester

    Looks the disk is gone again and VPS offline (try to reinstall from templates listed did not help)
    VPS ID: 652588
    Invoice #1397292 (In case the above ID not helped ) . thanks

    @VirMach said:
    Templates updated, let me know if it's better or worse.

    Disk is fine on our end. Try powerdown, wait a little bit, and install.

    Thanked by 1derekyang
  • derekyangderekyang Member
    edited April 2022

    thanks,
    tried shutdown. power on, reinstall but the VPS continuously showing Offline status.

    Edit: update here, not sure if anything was done but when i remove the ubuntu iso ( routed before) and mount with netboot.xyz and reboot , it did help to boot up the VPS and i see the last reinstall from template (debian 10) works , will see if everything is going well.

    @VirMach said:

    @derekyang said:
    beta tester

    Looks the disk is gone again and VPS offline (try to reinstall from templates listed did not help)
    VPS ID: 652588
    Invoice #1397292 (In case the above ID not helped ) . thanks

    @VirMach said:
    Templates updated, let me know if it's better or worse.

    Disk is fine on our end. Try powerdown, wait a little bit, and install.

  • @yotall said:

    @nobe said:

    @tooyoung said:
    Debian 11 restart via ssh, vps does not start, must be boot manually in the panel. Anyone in a similar situation? Still my problem?

    I have some similar issue:
    Debian 11
    Node:TYOC039

    I have been using the vps around one week. Everything is going smooth recently, but everyday the system will shutdown automatically at a random time, I have to boot it again manually through the panel, and everything back to happy again.

    Not sure if the system is still in test version, or only me. Anyway looks like we are 2 now.

    Me too......

    After the server was activated, I tested it, and the problems I found are as follows:
    1. Irregular automatic shutdown. The VPS found several (at least four) automatic shutdowns, most of which occurred without any action, and once suddenly interrupted while executing the “apt upgrade” command.
    After this problem occurred, I checked the “/var/log/messages.1” file and used the “cat messages.1 | grep error” command to check the error message, the prompt is as follows:
    root@jp:/var/log# cat messages.1 | grep error
    Dec 28 22:52:07 debiantemplate kernel: [ 2.926642] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 01:23:23 jp kernel: [ 1.177559] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 01:28:58 jp kernel: [ 1.438291] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 01:37:06 jp kernel: [ 1.191632] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 02:00:08 jp kernel: [ 1.323795] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 15:49:19 jp kernel: [ 0.950615] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 21:41:05 jp kernel: [ 1.069917] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    2. The server cannot be restarted using the "reboot" command. I tested it twice and each time it failed to reboot, only rebooted in the control panel.
    3. The network connection is unstable. The normal ping response time is about 60ms, and it often happens that the ping response time suddenly jumps to more than 200ms and there is packet loss. Since I'm from China, this might be due to GFW.

    Due to poor English, the above text is translated by google translate. The problems found above are for reference.

    非常蛋疼,一下跳到100到800的ping,我终端cpu表示反应不过来,速度看480p应该没有问题😄

  • Invoice #1398549,Tokyo,can I set it Tuesday?
    @VirMach

  • @VirMach Just confirming, are all the new Ryzen nodes on 1GBPS uplinks in all locations? The 10G burst might be the only thing I'll miss from the CC nodes.

  • Invoice #503758,Tokyo,can I set it Tuesday?
    @VirMach

  • buckbuck Member

    Hello,May i join the test? My Invoice is 1400458. Thank you!

  • yotallyotall Member
    edited April 2022

    @leendon said:
    非常蛋疼,一下跳到100到800的ping,我终端cpu表示反应不过来,速度看480p应该没有问题😄

    我这里河北联通,出口走上海联通,正常的情况下非常好,ping值在60ms左右,但经常性跳到200多ms且有丢包,等一会可能就好了,而且不能怪virmach,很可能是GFW的原因。但无任何规律的自动关机太折腾了……
    ps.如果你有hostloc的账号的话,邀请我一下……没人邀请不能注册……

  • nobenobe Member

    @yotall said:

    @nobe said:

    @tooyoung said:
    Debian 11 restart via ssh, vps does not start, must be boot manually in the panel. Anyone in a similar situation? Still my problem?

    I have some similar issue:
    Debian 11
    Node:TYOC039

    I have been using the vps around one week. Everything is going smooth recently, but everyday the system will shutdown automatically at a random time, I have to boot it again manually through the panel, and everything back to happy again.

    Not sure if the system is still in test version, or only me. Anyway looks like we are 2 now.

    Me too......

    After the server was activated, I tested it, and the problems I found are as follows:
    1. Irregular automatic shutdown. The VPS found several (at least four) automatic shutdowns, most of which occurred without any action, and once suddenly interrupted while executing the “apt upgrade” command.
    After this problem occurred, I checked the “/var/log/messages.1” file and used the “cat messages.1 | grep error” command to check the error message, the prompt is as follows:
    root@jp:/var/log# cat messages.1 | grep error
    Dec 28 22:52:07 debiantemplate kernel: [ 2.926642] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 01:23:23 jp kernel: [ 1.177559] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 01:28:58 jp kernel: [ 1.438291] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 01:37:06 jp kernel: [ 1.191632] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 02:00:08 jp kernel: [ 1.323795] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 15:49:19 jp kernel: [ 0.950615] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    Apr 2 21:41:05 jp kernel: [ 1.069917] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro
    2. The server cannot be restarted using the "reboot" command. I tested it twice and each time it failed to reboot, only rebooted in the control panel.
    3. The network connection is unstable. The normal ping response time is about 60ms, and it often happens that the ping response time suddenly jumps to more than 200ms and there is packet loss. Since I'm from China, this might be due to GFW.

    Due to poor English, the above text is translated by google translate. The problems found above are for reference.

    Have you tried to re-install Debian 11? I'm going to quote what the boss said "Disk is fine on our end. Try powerdown, wait a little bit, and install." you can try it.

  • FrankZFrankZ Veteran
    edited April 2022

    I've been able to install Debian 11 from netboot.xyz ISO multiple times without issue on Node39.
    First I installed the Alma8 template from billing panel, then installed Debian 11 from the netboot.xyz ISO in SolusVM panel.


    For those of you mentioning packet loss and high ping times from China, this may be because you are in China and there may not be anything VirMach can do about this. Below is a graph of the dns request times every two minutes for the last 10 hours from Sydney AU, San Jose CA, Seacaucus NJ (NYC), and Sofia BG to my VPS on Node39. As you can see the response times are very consistent and without any failures.

    Larger image: https://i.postimg.cc/W1mx00Fx/Screenshot-2022-04-03-at-10-15-14.png

    Thanked by 2Xrmaddness FAT32
  • ravenchadravenchad Member
    edited April 2022

    until when is the beta testing?

  • The I/O and network speed in the Node39 are better than Node40.

  • noisycodenoisycode Member
    edited April 2022

    @VirMach said:
    Everyone's benchmarking and the other half are kernel panicking.

    Well said! The vm on Node40 is still drowning in the sea of panicking. Let me see what else I could do with it.

    Thanked by 1FrankZ
  • Looks like this is not normal, or maybe Everyone's benchmarking

    root@TYOC040:~# curl -sL yabs.sh | bash -s -- -r
    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    #              Yet-Another-Bench-Script              #
    #                     v2022-02-18                    #
    # https://github.com/masonr/yet-another-bench-script #
    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    
    Sun 03 Apr 2022 10:15:23 PM WIB
    
    Basic System Information:
    ---------------------------------
    Processor  : AMD Ryzen 9 5900X 12-Core Processor
    CPU cores  : 2 @ 3693.062 MHz
    AES-NI     : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM        : 2.4 GiB
    Swap       : 256.0 MiB
    Disk       : 49.0 GiB
    
    fio Disk Speed Tests (Mixed R/W 50/50):
    ---------------------------------
    Block Size | 4k            (IOPS) | 64k           (IOPS)
      ------   | ---            ----  | ----           ----
    Read       | 274.24 MB/s  (68.5k) | 416.24 MB/s   (6.5k)
    Write      | 274.96 MB/s  (68.7k) | 418.43 MB/s   (6.5k)
    Total      | 549.20 MB/s (137.3k) | 834.68 MB/s  (13.0k)
               |                      |
    Block Size | 512k          (IOPS) | 1m            (IOPS)
      ------   | ---            ----  | ----           ----
    Read       | 1.17 MB/s        (2) | 401.00 KB/s      (0)
    Write      | 1.33 MB/s        (2) | 448.00 KB/s      (0)
    Total      | 2.50 MB/s        (4) | 849.00 KB/s      (0)
    
    iperf3 Network Speed Tests (IPv4):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed
                    |                           |                 |
    Clouvider       | London, UK (10G)          | 21.9 Mbits/sec  | 91.0 Mbits/sec
    Online.net      | Paris, FR (10G)           | 33.2 Mbits/sec  | 18.8 Mbits/sec
    Clouvider       | NYC, NY, US (10G)         | 30.7 Mbits/sec  | 45.1 Mbits/sec
    
    Geekbench 5 Benchmark Test:
    ---------------------------------
    Test            | Value
                    |
    Single Core     | 1307
    Multi Core      | 2554
    Full Test       | https://browser.geekbench.com/v5/cpu/14066562
    
    
  • @FrankZ said:
    I've been able to install Debian 11 from netboot.xyz ISO multiple times without issue on Node39.
    First I installed the Alma8 template from billing panel, then installed Debian 11 from the netboot.xyz ISO in SolusVM panel.


    For those of you mentioning packet loss and high ping times from China, this may be because you are in China and there may not be anything VirMach can do about this. Below is a graph of the dns request times every two minutes for the last 10 hours from Sydney AU, San Jose CA, Seacaucus NJ (NYC), and Sofia BG to my VPS on Node39. As you can see the response times are very consistent and without any failures.

    Larger image: https://i.postimg.cc/W1mx00Fx/Screenshot-2022-04-03-at-10-15-14.png

    Please test Node40. Why the same configuration Node40 is much worse than Node39!For example, I/O and network speed.Thanks

  • FrankZFrankZ Veteran
    edited April 2022

    @vhhjkgl said: The I/O and network speed in the Node39 are better than Node40.

    @vhhjkgl said: Please test Node40. Why the same configuration Node40 is much worse than Node39!For example, I/O and network speed.Thanks

    It's the same uplink and transfer providers for Node 39 as Node 40, so as soon as everybody settles down the network should be more or less the same.

    Regarding I/O everybody is thrashing the disks on Node 40 right now and it is a beta test so if the I/O is bad after things settle down I am sure VirMach will make adjustment/improvments.
    Node 39 is better because 50 people have been on it for days already, and Node 40 had everyone put on it less then 24 hours ago.

    Just give things a little time.

This discussion has been closed.