Howdy, Stranger!

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


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
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

1170171173175176339

Comments

  • AlwaysSkintAlwaysSkint Member
    edited April 2022

    @Chandler said: Looking forward to getting good news!

    You should be fine in Phoenix. ;)

    Thanked by 1xmd5
  • AlwaysSkintAlwaysSkint Member
    edited April 2022

    @Virmach I presume that you realise SAEZ001 is still as dead as a can of spam.

    Operation Timed Out After 90001 Milliseconds With 0 Bytes Received

  • Btw, any chance PHXZ002 have XPG drive? :#

  • @VirMach said: There will be total 3.5TB space for services, so about 10GB for 384MB plan and 50GB for 2.5GB plan for a rough average of 30GB, or 116 services. There are currently 72 services we know that did not provision correctly so those will fit, plus about 44 others.

    great! hopefully we could be included here finally :)

  • VirMachVirMach Member, Patron Provider

    @Chandler said:
    Looking forward to getting good news!

    @AlwaysSkint said:
    @Virmach I presume that you realise SAEZ001 is still as dead as a can of spam.

    Operation Timed Out After 90001 Milliseconds With 0 Bytes Received

    Yeah, got the DC to finally move the disk over but they fumbled it a bit, trying to figure out where it is right now. If I can't get data off then we'll just recreate these as well and ship the disk over for a further look.

    @risturiz said:
    Btw, any chance PHXZ002 have XPG drive? :#

    I have a list of all XPG drives right now, PHXZ002 does not have an XPG drive.

  • @VirMach said:

    @Nico9999 said:
    I have to remind you that there are still some people in TYOC038, the status of our server is always offline, and we can't solve this problem through migration, because the migration option has been closed, when will this problem be solved?

    TYOC038 Update - All the people left with a broken service are not directly involved in the disk issue it had, but most likely affected by it in that the system stuttered while they were creating and didn't create as efficiently, it looks like a provisioning issue similar to the other node earlier, I forgot the name. They never created properly. These date back from 04/11/2021 until now. We're going to set them back to pending, adjust the due date again to make up for the lost time, and add them to the pending queue. These should still be created first on the script again but I want to be very clear that it's not a guarantee. I don't see any reason why they shouldn't since it's the same script that would select these first if they were already selected first.

    So if yours never provisioned correctly, today, you will see it go back to pending and due date changed to later.

    Tokyo Update

    Then, we're going to schedule maintenance with Tokyo to add in a new disk to TYOC038, as well as TYOC035. These nodes are both missing 2TB and have <65% CPU usage currently, so after the maintenance, creations will run again.

    There will be total 3.5TB space for services, so about 10GB for 384MB plan and 50GB for 2.5GB plan for a rough average of 30GB, or 116 services. There are currently 72 services we know that did not provision correctly so those will fit, plus about 44 others.

    TYOC033 has about 1.5TB of space, so up to another 50 here.

    TYOC036 already received another disk, for another 1.75TB or 58 more services.

    Total room for up to 152 services after TYOC038 is taken care of. Probably closer to 100 due to CPU constraints and since larger plans are left at the end due to previously discussed issue with the script.

    Other nodes, they still need to cool off or may already be at capacity. That means 50-100 services at the end without an immediate home. Going to go through another round of requested refunds and see if we can make it all work.

    TYOC037 has 1.5TB of space but it needs to calm down, we did just recently create a good amount on this one.

    TYOC034 has about 1.2TB of space, but same, needs to calm.

    TYOC039 has 660GB of space and it's pretty calm but I don't want to put anyone else here.

    TYOC040 has 690GB of space that can maybe be used but I'll have to monitor it.

    (edit) Actually a lot of this space issue can be resolved quickly, I'm going to go through anyone who has a ticket open about TYOC038 which has an active network status and start cancelling/refunding people since we request tickets not be opened in these cases. Email was sent as well already.

    My support ticket has been closed, do I still need to send you a new support ticket?

  • VirMachVirMach Member, Patron Provider

    @Nico9999 said: My support ticket has been closed, do I still need to send you a new support ticket?

    Ticket for what, TYOC038? There's a network status open, we're still aware, and we already provided an update that you quoted. No ticket is necessary for that.

  • VirMachVirMach Member, Patron Provider

    TYOC039 update we were able to get the disk back up. I'm not booting any virtual servers so we can get a quick transfer off for these VMs. It shouldn't take long.

    Thanked by 1FrankZ
  • VirMachVirMach Member, Patron Provider
    edited April 2022

    List of servers with probably XPG, due to the way the PCIe risers work in these I can't be 100% sure until going into BIOS but it's a high likelihood:

    SEAZ002
    SEAZ003
    PHXZ001
    ATLZ005

    These definitely have an XPG:

    TYOC040 (2)
    TYOC039 (And it's broken, people are getting moved right now.)
    SEAZ001 (And it's broken.)
    TYOC038 (And it already broken and people got moved.)
    TYOC037
    TYOC035 (And it's already broken and people got moved.)
    TYOC034

    These are broken in some way or missing disk and may be XPG, but no one will be affected, but it's likely it's completely unrelated.

    SJCZ009
    PHXZ003

    All others confirmed to not have XPG or already gotten rid of it.

  • VirMachVirMach Member, Patron Provider

    @VirMach said:
    TYOC039 update we were able to get the disk back up. I'm not booting any virtual servers so we can get a quick transfer off for these VMs. It shouldn't take long.

    These are transferring off at an average 500MB/s. Should only be another half hour of downtime for TYOC039. IP addresses will stay the same.

    Thanked by 1FrankZ
  • duckeeyuckduckeeyuck Member
    edited April 2022

    @VirMach I should get the hynix p31 if i buy more flash storage on my pc right?

  • VirMachVirMach Member, Patron Provider

    @duckeeyuck said:
    @VirMach I should get the hynix p31 if i buy more flash storage on my pc right?

    Overall, yes, I'd say it's the best drive. In terms of price, latency, and performance once it's full and where it matters.

  • VirMachVirMach Member, Patron Provider

    TYOC039 took a little bit longer as it ran into some I/O errors during the transfer but it's about to be done and everything is going to be booted back up.

    Thanked by 1FrankZ
  • VirMachVirMach Member, Patron Provider

    @cybertech said:

    zug zug

  • @VirMach The last Ticket :) #794490

  • VirMachVirMach Member, Patron Provider

    Chicago update. Psychz says this is ready now, and we need to send in the "correct" PDU to match the incorrect setup they did, so I've ordered one off Amazon to arrive Tuesday. We'll send off the servers as well and hope they do the right thing on Amsterdam. Of course I'll still keep an eye out for communication on Monday on Amsterdam.

    SEAZ001 update. DC hands and the team are struggling to understand my request. Disk was moved to potentially the wrong server which is fine but none of the servers detect it and they won't confirm where they put it. Last real information I got is that there's no 4TB drive, only 8TB (they're referring to an HDD. For some reason they can't tell the difference between PCIe and HDD.)

    I'll try to provide more updates later. Still waiting on SEAZ001 response and in the meantime packing while I do a few other things I talked about earlier today.

  • @reb0rn said:
    Chia ploters where also unhappy with XPG....

    btw samsung 500GB at hetzner dedi is atm at over 2500TB write no error no media wear, nothing just over 20x projected life going strong >:)
    just do not tell them or they kill me

    This is why we can't have nice things.

    Thanked by 1bulbasaur
  • VirMachVirMach Member, Patron Provider
    edited April 2022

    @TimboJones said:

    @reb0rn said:
    Chia ploters where also unhappy with XPG....

    btw samsung 500GB at hetzner dedi is atm at over 2500TB write no error no media wear, nothing just over 20x projected life going strong >:)
    just do not tell them or they kill me

    This is why we can't have nice things.

    I went over these numbers a while ago, but I just looked them up as a refresher. Something like 40 days time to kill a drive per 500GB and that's consumer grade/average. So, close to 3 months and $129 at Hetzner to kill two 500GB drives. Except that's based on one old source that doesn't provide much information, and if Hetzner is using Samsung, a 250GB drive lasts around 5000TBW. Even if we assume the 500GB is only as good as the 250GB, let's say that's 2,500~ plots at 6 hours a plot. That's closer to 625 days for a single drive and 1250 days for two of them. Hetzner makes $1,763 before their $100 in disks are killed.

    Maybe my math is completely wrong, I just remember looking all this up more thoroughly in the past and walking away from it without any concerns for losing money on dedi abuse.

  • None nvme samsung dies till now for me and I am on 12month now for 500GB, the writes where 100% 24h now slowing/stoping as dedi will e used for other stuff. but all 10+ drives health is 100% (no spare block used zero issue withing smart data) even the drives should be dead long time ago at least it stand for samsung SAMSUNG MZVLB512HBJQ
    critical_warning : 0x4
    temperature : 53 C
    available_spare : 100%
    available_spare_threshold : 10%
    percentage_used : 255%
    data_units_read : 9,336,543,944
    data_units_written : 13,229,512,524

    so that one is perfect health and TBW on 500GB model as atm 6160TB

    Thanked by 1DanSummer
  • @VirMach said:

    @TimboJones said:

    @reb0rn said:
    Chia ploters where also unhappy with XPG....

    btw samsung 500GB at hetzner dedi is atm at over 2500TB write no error no media wear, nothing just over 20x projected life going strong >:)
    just do not tell them or they kill me

    This is why we can't have nice things.

    I went over these numbers a while ago, but I just looked them up as a refresher. Something like 40 days time to kill a drive per 500GB and that's consumer grade/average. So, close to 3 months and $129 at Hetzner to kill two 500GB drives. Except that's based on one old source that doesn't provide much information, and if Hetzner is using Samsung, a 250GB drive lasts around 5000TBW. Even if we assume the 500GB is only as good as the 250GB, let's say that's 2,500~ plots at 6 hours a plot. That's closer to 625 days for a single drive and 1250 days for two of them. Hetzner makes $1,763 before their $100 in disks are killed.

    Maybe my math is completely wrong, I just remember looking all this up more thoroughly in the past and walking away from it without any concerns for losing money on dedi abuse.

    I don't know what that title is about, but a lot of these TBW tests test well beyond real world failure points and useless for such comparisons. I don't give a shit how long for the whole drive to get wrecked, it's unstable and blue screening after the first blocks get retired. Amplification writes goes to the fucking moon. The warranty also long blown, and newer models don't use MLC.

    Your calculation also for some reason only takes revenue into account for the drives and not for the entire machine, so erasing the two year roi for the whole server isn't seen. In other words, if they expected to make ~$100 profit in 625 days, they won't any longer.

    Lastly, they had to take action against this due to failed drives and the increase in technicians swapping drives and customers delayed/impacted. Try and argue with real world at your own peril.

  • @VirMach said:

    @vhhjkgl said:

    @tototo said:

    @vhhjkgl said:
    I found a strange appearance, first I installed Centos7 and then went to DD's debian11, Centos7's data was not cleared at all, but the latency became abnormally stable.Node40

    First install CENTOS7, then install bebian11 is unable to eliminate centos7 date, ssh connection still shows Centos7 information. I've tried a few times.

    I have some questions.
    What is "DD's Debian"? Is overwriting installed disk image (an image of a gz or xz compressed system disk instead of an ISO) to /dev/vda using the dd command?
    I've heard it's a bit popular in China, but I don't think it's very common.
    Also, if the overwrite by dd was successful, the CentOS data should have lost, so I think you failed in dd.
    To me, the machine has rebooted, so it's stable.

    When the cpu load is very low, the latency is low and stable, but when I enable the proxy and the cpu load increases, a slight increase causes huge fluctuations in latency, which is not normal . Further, when I have other operations, the latency becomes huge whenever there is a slight change in CPU, which I have tried many times.

    I'm looking into TYOC040 again right now. I may check your VPS out in the next hour, just letting you know.

    @VirMach said:
    TYOC039 took a little bit longer as it ran into some I/O errors during the transfer but it's about to be done and everything is going to be booted back up.

    Please look work order #749044. TYOC039 VPS suddenly lost its hard disk and stayed offline of a day long.

  • @VirMach said: Trying to send out Tokyo on Monday.

    Will the remaining Tokyo March pre-order vps run on the existing nodes or will they run on the upcoming new storage nodes?

  • @vincentwenad said:
    Please look work order #749044. TYOC039 VPS suddenly lost its hard disk and stayed offline of a day long.

    Please look what VirMach posted a while back!!

    @ VirMach said: TYOC039 (And it's broken, people are getting moved right now.)

  • VirMachVirMach Member, Patron Provider

    @TimboJones said: I don't know what that title is about, but a lot of these TBW tests test well beyond real world failure points and useless for such comparisons. I don't give a shit how long for the whole drive to get wrecked, it's unstable and blue screening after the first blocks get retired. Amplification writes goes to the fucking moon. The warranty also long blown, and newer models don't use MLC.

    Your calculation also for some reason only takes revenue into account for the drives and not for the entire machine, so erasing the two year roi for the whole server isn't seen. In other words, if they expected to make ~$100 profit in 625 days, they won't any longer.

    Lastly, they had to take action against this due to failed drives and the increase in technicians swapping drives and customers delayed/impacted. Try and argue with real world at your own peril.

    The only point I was trying to make is that it's likely that the impact is likely less than what was circulating at the peak of the anti-Chia movement and I of course over-simplified it to represent it as a potential ratio of the total revenue, which is often what companies may use in their pricing formulas when compared to the cost to acquire the hardware.

    Of course you do make a good point, when going in more depth, the negative externalities are more than just the cost of the drives. I definitely did not include that portion.

    Thanked by 1TimboJones
  • VirMachVirMach Member, Patron Provider

    @sky3967 said:

    @VirMach said: Trying to send out Tokyo on Monday.

    Will the remaining Tokyo March pre-order vps run on the existing nodes or will they run on the upcoming new storage nodes?

    Are you asking if the Ryzen VPS advertised with NVMe run on the HDD storage node?

  • VirMachVirMach Member, Patron Provider

    @vincentwenad said:

    @VirMach said:

    @vhhjkgl said:

    @tototo said:

    @vhhjkgl said:
    I found a strange appearance, first I installed Centos7 and then went to DD's debian11, Centos7's data was not cleared at all, but the latency became abnormally stable.Node40

    First install CENTOS7, then install bebian11 is unable to eliminate centos7 date, ssh connection still shows Centos7 information. I've tried a few times.

    I have some questions.
    What is "DD's Debian"? Is overwriting installed disk image (an image of a gz or xz compressed system disk instead of an ISO) to /dev/vda using the dd command?
    I've heard it's a bit popular in China, but I don't think it's very common.
    Also, if the overwrite by dd was successful, the CentOS data should have lost, so I think you failed in dd.
    To me, the machine has rebooted, so it's stable.

    When the cpu load is very low, the latency is low and stable, but when I enable the proxy and the cpu load increases, a slight increase causes huge fluctuations in latency, which is not normal . Further, when I have other operations, the latency becomes huge whenever there is a slight change in CPU, which I have tried many times.

    I'm looking into TYOC040 again right now. I may check your VPS out in the next hour, just letting you know.

    @VirMach said:
    TYOC039 took a little bit longer as it ran into some I/O errors during the transfer but it's about to be done and everything is going to be booted back up.

    Please look work order #749044. TYOC039 VPS suddenly lost its hard disk and stayed offline of a day long.

    Hi, first of all please do not use the outage report button like that. You didn't add the node name to the title, so it's not helpful, and it would just be closed. Also, we already sent out emails, as well as updated network status page for this issue.

    And we've also already fixed these as well.

    Yours is not directly related to this issue anymore. It seems like after the disk issue/outage, you spammed the buttons, some within the same minute, like re-install, boot, reboot, rescue mode, boot, re-install, then a couple minutes later re-install, boot, boot, re-install, etc. This caused yours to fully break and disappear. I'd recommend closing the outage report and use the appropriate button to create a ticket and explain what you did in what circumstance and mention that your disk is fully missing and it needs to be recreated.

  • @VirMach My VPS was disabled because the traffic was wrongly set to 1G, please check

  • @yanaxiao said:
    @ VirMach My VPS was disabled because the traffic was wrongly set to 1G, please check

    I believe you heard yesterday that the issue has already been recognized by VirMach and is awaiting a fix by their developers.

  • Please sync some ISO on ATLZ005 if you have free time on the next days :-)

    Thanks.

This discussion has been closed.