DartNode: Black Friday Edition 2025 - Ryzen 9950X Dedicated Giveaway - Deals Inside - We Go to Space

simo · February 1

@SODaLC said:

@yoursunny said:

@keoir said:

@yoursunny said:

@keoir said:
For KC, we have allocated additional IPv6, so if your VM did not get assigned an IPv6 address, let us know in a ticket as well

We're continuing to work through the queue and appreciate your patience. If you want a refund, we 100% understand and will process these under the 7-day money-back guarantee we offer. Please give us time to process the refund before you open a dispute. We are not declining any refunds, and want to make sure you are taken care of even if you decide you want a refund.

Would you reset the starting date of both 1-year service period and 7-day money-back guarantee to align with the resolution of major problems? (1) IPv6 online (2) VNC operational.
Presently half of the 7-day period has elapsed and the machine is unusable.

Yes we will be pushing renewal dates and then also extending the 7 day money back persion until 1/1/2026

It's been two months since we purchased the server, and the server still does not work: VNC does not work, and the server is stuck in power off state for who knows how long whenever we reboot it from panel.
We are giving the provider a final 7-day period to resolve the technical issues.
If this cannot be resolved within this period, we would unfortunately have to request a refund.

Purchased one a couple days ago.

IPv6 doesn't work, it has no route out from the gateway.
VNC doesn't work on it either.

Best part, the refund button doesn't even work either.

It's a shame, it did look quite promising.

My apologies for the trouble you’re experiencing. This issue has affected some nodes, and many users have already reported it. I assure you it’s being prioritized and will be resolved soon

simo · February 1

@xingqing said:
There's no renewal function; payment can only be notified via invoice, but no prior notification was sent, and I haven't received it. It remains unresolved.

Can you please send me you ticket number?

simo · February 1

@fafad550 said:
I'm also waiting on US-West. I didn't get an e-mail, but sure enough my server had been commissioned and was available on the control panel. Mine got an IPv6 assigned, but it's not working at all, I was assigned 2602:f9f3:3000::x/36, but according to bgp.tools, this prefix isn't being announced at all, just 2602:f9f3::/36.

We’re aware that IPv6 connectivity isn’t working properly for many legitimate users. Part of the issue is spammers flooding certain prefixes, which is affecting routing and reachability. Some routes aren’t fully announced yet, and our network security and routing setup is being reworked. The team is actively testing a fix, and we’ll share updates here or via tickets as soon as the announcement problem is resolved.

ariq01 · February 2

Hi, can you process this Ticket #18151 ?
thanks

xingqing · February 2

@simo said:

@xingqing said:
There's no renewal function; payment can only be notified via invoice, but no prior notification was sent, and I haven't received it. It remains unresolved.

Can you please send me you ticket number?

Ticket #18700

xingqing · February 2

@simo said:

@xingqing said:
There's no renewal function; payment can only be notified via invoice, but no prior notification was sent, and I haven't received it. It remains unresolved.

Can you please send me you ticket number?

Ticket #18700

xingqing · February 2

@simo said:

@xingqing said:
There's no renewal function; payment can only be notified via invoice, but no prior notification was sent, and I haven't received it. It remains unresolved.

Can you please send me you ticket number?

Ticket #18700
Please handle this immediately; it's already February 1st.

fafad550 · February 3

IPv6 on US-West seems fixed to me. 2602:f9f3:3000::/36 is now routeable and after a bit of a fight with the configs (DHCP isn't pushing the gateway) I managed to ping to/from other servers. Haven't tested the routing/speed though.

simo · February 6

@xingqing said:

@simo said:

@xingqing said:
There's no renewal function; payment can only be notified via invoice, but no prior notification was sent, and I haven't received it. It remains unresolved.

Can you please send me you ticket number?

Ticket #18700
Please handle this immediately; it's already February 1st.

The ticket is being handled by Accounting Please don’t worry about the date it’s showing, it will be corrected soon.

default · February 7

@simo - Did everybody get provisioned?

simo · February 7

@default said:
@simo - Did everybody get provisioned?

Do you mean in LA? The provisioning team would be able to answer this more accurately, but I can check it for you if you share the order number

yoursunny · February 8

Our VNC is finally working, but we got dadfailed on the IPv6 address because someone else is using the same address.
What's a disaster!

We are slowly losing patient and considering to push the refound button.

keoir · February 8

@yoursunny said:
Our VNC is finally working, but we got dadfailed on the IPv6 address because someone else is using the same address.
What's a disaster!

We are slowly losing patient and considering to push the refound button.

Remind me the service # and I'll look at the network now

AlteredParadox · February 8

@keoir @simo there something going on with ip addressing? I'm starting to believe my ipv4 is attached to something else, as well. My vm is powered off, and the ip is still responding to pings and ssh connections, lol.

yoursunny · February 8

@keoir said:

@yoursunny said:
Our VNC is finally working, but we got dadfailed on the IPv6 address because someone else is using the same address.
What's a disaster!

We are slowly losing patient and considering to push the refound button.

Remind me the service # and I'll look at the network now

Ticket 15257

simo · February 8

@AlteredParadox said:
@keoir @simo there something going on with ip addressing? I'm starting to believe my ipv4 is attached to something else, as well. My vm is powered off, and the ip is still responding to pings and ssh connections, lol.

Ahh, got it! you’re referring to a visual glitch in the panel that’s affecting some VMs (not all). This has already been reported internally. If ping and SSH are working, then your server is actually running

We’re currently prioritizing some critical issues, but this one is also on our list to be fixed soon

AlteredParadox · February 8

@simo said:

@AlteredParadox said:
@keoir @simo there something going on with ip addressing? I'm starting to believe my ipv4 is attached to something else, as well. My vm is powered off, and the ip is still responding to pings and ssh connections, lol.

Ahh, got it! you’re referring to a visual glitch in the panel that’s affecting some VMs (not all). This has already been reported internally. If ping and SSH are working, then your server is actually running

We’re currently prioritizing some critical issues, but this one is also on our list to be fixed soon

Nah, I straight up powered it off, but was still getting pings and ash on port 22 (not the port I configure). My ipv4 ip got changed and my vm powered back on about 2 hours after this, tho there’s not been any update to the ticket I put in yet… so who knows. It’s at least online now? Heh.

forest · February 8

@simo said:

@AlteredParadox said:
@keoir @simo there something going on with ip addressing? I'm starting to believe my ipv4 is attached to something else, as well. My vm is powered off, and the ip is still responding to pings and ssh connections, lol.

Ahh, got it! you’re referring to a visual glitch in the panel that’s affecting some VMs (not all). This has already been reported internally. If ping and SSH are working, then your server is actually running

We’re currently prioritizing some critical issues, but this one is also on our list to be fixed soon

It might not only be a UI issue. If my server crashes, it turns off and stays off until I manually restart it from the dashboard. This results in severe downtime. Out of the ~40 VPSes I have, the two DartNode ones are the only ones that have this issue.

simo · February 10

@AlteredParadox said:

@simo said:

@AlteredParadox said:
@keoir @simo there something going on with ip addressing? I'm starting to believe my ipv4 is attached to something else, as well. My vm is powered off, and the ip is still responding to pings and ssh connections, lol.

Ahh, got it! you’re referring to a visual glitch in the panel that’s affecting some VMs (not all). This has already been reported internally. If ping and SSH are working, then your server is actually running

We’re currently prioritizing some critical issues, but this one is also on our list to be fixed soon

Nah, I straight up powered it off, but was still getting pings and ash on port 22 (not the port I configure). My ipv4 ip got changed and my vm powered back on about 2 hours after this, tho there’s not been any update to the ticket I put in yet… so who knows. It’s at least online now? Heh.

sorry about that! what's your ticket number?

simo · February 10

@forest said:

@simo said:

@AlteredParadox said:
@keoir @simo there something going on with ip addressing? I'm starting to believe my ipv4 is attached to something else, as well. My vm is powered off, and the ip is still responding to pings and ssh connections, lol.

Ahh, got it! you’re referring to a visual glitch in the panel that’s affecting some VMs (not all). This has already been reported internally. If ping and SSH are working, then your server is actually running

We’re currently prioritizing some critical issues, but this one is also on our list to be fixed soon

It might not only be a UI issue. If my server crashes, it turns off and stays off until I manually restart it from the dashboard. This results in severe downtime. Out of the ~40 VPSes I have, the two DartNode ones are the only ones that have this issue.

Thanks for sharing that. Could you please open a support ticket and include the affected service IDs along with the approximate time the last crashes occurred? I'll be happy to check this for you

forest · February 10

@simo said:

@forest said:

@simo said:

@AlteredParadox said:
@keoir @simo there something going on with ip addressing? I'm starting to believe my ipv4 is attached to something else, as well. My vm is powered off, and the ip is still responding to pings and ssh connections, lol.

Ahh, got it! you’re referring to a visual glitch in the panel that’s affecting some VMs (not all). This has already been reported internally. If ping and SSH are working, then your server is actually running

We’re currently prioritizing some critical issues, but this one is also on our list to be fixed soon

It might not only be a UI issue. If my server crashes, it turns off and stays off until I manually restart it from the dashboard. This results in severe downtime. Out of the ~40 VPSes I have, the two DartNode ones are the only ones that have this issue.

Thanks for sharing that. Could you please open a support ticket and include the affected service IDs along with the approximate time the last crashes occurred? I'll be happy to check this for you

It's already open, ticket #15503 (which is additionally about the graphical issue, since I suspect they may be related). Three weeks ago, I wrote:

This is beginning to cause issues. My servers are experiencing instability and frequent downtime, and it is difficult to revive them from the dashboard due to this bug.

Is there any chance you could enable the QEMU watchdog by adding -watchdog i6300esb -watchdog-action reset to the command line? Note that it will not adversely affect any customers, as it will do nothing unless the guest opens /dev/watchdog.

I was told it was fixed and to reply if any issues remained. A week ago I did:

The issue is persisting, and my VMs are not automatically powering on if rebooted in many cases, which makes crashes extremely frustrating to deal with.

Please note that it has been weeks since I have last been able to effectively use either of my VPSes. I do not believe this is only a UI issue, as every day I seem to need to go in and start them manually. I need the issue fixed so that I can resume use of my services.

However the crashes are caused, they do not trigger an automatic reboot like they do on the services I have with different providers. If the system has locked up due to slab memory pressure (which, unlike userspace memory pressure, does not trigger the OOM killer or panic_on_oom), the only way for me to tell would be to VNC in and look at the console, but VNC shows a strange situation where the system is unresponsive (it doesn't even reply to pings), but there are no messages that would indicate running out of slabs, and nothing can be typed into VNC.

If it is a problem of insufficient memory, I don't get why these two servers, out of the 40 I have, are the only ones having this problem, despite most of my other servers having the same amount of memory.

It would all be fixed if the QEMU watchdog was enabled.

six · February 10

@simo, is the NOC dead? My ticket has been open for more than two months now and I still haven't received a reply.

simo · February 10

@forest said:

@simo said:

@forest said:

@simo said:

@AlteredParadox said:
@keoir @simo there something going on with ip addressing? I'm starting to believe my ipv4 is attached to something else, as well. My vm is powered off, and the ip is still responding to pings and ssh connections, lol.

Ahh, got it! you’re referring to a visual glitch in the panel that’s affecting some VMs (not all). This has already been reported internally. If ping and SSH are working, then your server is actually running

We’re currently prioritizing some critical issues, but this one is also on our list to be fixed soon

It might not only be a UI issue. If my server crashes, it turns off and stays off until I manually restart it from the dashboard. This results in severe downtime. Out of the ~40 VPSes I have, the two DartNode ones are the only ones that have this issue.

Thanks for sharing that. Could you please open a support ticket and include the affected service IDs along with the approximate time the last crashes occurred? I'll be happy to check this for you

It's already open, ticket #15503 (which is additionally about the graphical issue, since I suspect they may be related). Three weeks ago, I wrote:

This is beginning to cause issues. My servers are experiencing instability and frequent downtime, and it is difficult to revive them from the dashboard due to this bug.

Is there any chance you could enable the QEMU watchdog by adding -watchdog i6300esb -watchdog-action reset to the command line? Note that it will not adversely affect any customers, as it will do nothing unless the guest opens /dev/watchdog.

I was told it was fixed and to reply if any issues remained. A week ago I did:

The issue is persisting, and my VMs are not automatically powering on if rebooted in many cases, which makes crashes extremely frustrating to deal with.

Please note that it has been weeks since I have last been able to effectively use either of my VPSes. I do not believe this is only a UI issue, as every day I seem to need to go in and start them manually. I need the issue fixed so that I can resume use of my services.

However the crashes are caused, they do not trigger an automatic reboot like they do on the services I have with different providers. If the system has locked up due to slab memory pressure (which, unlike userspace memory pressure, does not trigger the OOM killer or panic_on_oom), the only way for me to tell would be to VNC in and look at the console, but VNC shows a strange situation where the system is unresponsive (it doesn't even reply to pings), but there are no messages that would indicate running out of slabs, and nothing can be typed into VNC.

If it is a problem of insufficient memory, I don't get why these two servers, out of the 40 I have, are the only ones having this problem, despite most of my other servers having the same amount of memory.

It would all be fixed if the QEMU watchdog was enabled.

@forest said:

@simo said:

@forest said:

@simo said:

@AlteredParadox said:
@keoir @simo there something going on with ip addressing? I'm starting to believe my ipv4 is attached to something else, as well. My vm is powered off, and the ip is still responding to pings and ssh connections, lol.

Ahh, got it! you’re referring to a visual glitch in the panel that’s affecting some VMs (not all). This has already been reported internally. If ping and SSH are working, then your server is actually running

We’re currently prioritizing some critical issues, but this one is also on our list to be fixed soon

It might not only be a UI issue. If my server crashes, it turns off and stays off until I manually restart it from the dashboard. This results in severe downtime. Out of the ~40 VPSes I have, the two DartNode ones are the only ones that have this issue.

Thanks for sharing that. Could you please open a support ticket and include the affected service IDs along with the approximate time the last crashes occurred? I'll be happy to check this for you

It's already open, ticket #15503 (which is additionally about the graphical issue, since I suspect they may be related). Three weeks ago, I wrote:

This is beginning to cause issues. My servers are experiencing instability and frequent downtime, and it is difficult to revive them from the dashboard due to this bug.

Is there any chance you could enable the QEMU watchdog by adding -watchdog i6300esb -watchdog-action reset to the command line? Note that it will not adversely affect any customers, as it will do nothing unless the guest opens /dev/watchdog.

I was told it was fixed and to reply if any issues remained. A week ago I did:

The issue is persisting, and my VMs are not automatically powering on if rebooted in many cases, which makes crashes extremely frustrating to deal with.

Please note that it has been weeks since I have last been able to effectively use either of my VPSes. I do not believe this is only a UI issue, as every day I seem to need to go in and start them manually. I need the issue fixed so that I can resume use of my services.

However the crashes are caused, they do not trigger an automatic reboot like they do on the services I have with different providers. If the system has locked up due to slab memory pressure (which, unlike userspace memory pressure, does not trigger the OOM killer or panic_on_oom), the only way for me to tell would be to VNC in and look at the console, but VNC shows a strange situation where the system is unresponsive (it doesn't even reply to pings), but there are no messages that would indicate running out of slabs, and nothing can be typed into VNC.

If it is a problem of insufficient memory, I don't get why these two servers, out of the 40 I have, are the only ones having this problem, despite most of my other servers having the same amount of memory.

It would all be fixed if the QEMU watchdog was enabled.

I’m checking this for you and will reply in the ticket once I have an update

simo · February 10

@six said:
@simo, is the NOC dead? My ticket has been open for more than two months now and I still haven't received a reply.

That’s odd, I don’t see a ticket open that long. It might have been auto-closed or something, but I can check for you. What’s your ticket number?

yosbeda · February 11

@simo I need urgent assistance with ticket regarding VM #22447 (s22447.dartnode.com).

I've been experiencing critical recurring downtime for over 48 hours now with minimal communication from support:

Current situation:
- 16 separate downtime incidents in the past ~36 hours
- Total downtime: approximately 18+ hours
- Service availability: ~50% - the VM is down more than it's up
- Last support response: over 24 hours ago (just acknowledgment, no diagnostics or action plan)

Most recent downtime incidents:
- 1 hour ago: 1h 13min down
- 4 hours ago: 19min down
- 5 hours ago: 4min down
- 9 hours ago: 1h 34min down
- 14 hours ago: 2h 19min down
- 18 hours ago: 2h 14min down

This has been escalated multiple times in the ticket with no technical response or ETA.

I understand you're active here and helping others - could you please check on this ticket and provide an update? I need to know:
1. What's causing these recurring failures?
2. What action is being taken?
3. Whether I should plan to migrate elsewhere?

This is impacting production service and I've been very patient, but I need some communication and action at this point.

Thank you.

simo · February 11

@yosbeda said:

@simo I need urgent assistance with ticket regarding VM #22447 (s22447.dartnode.com).

I've been experiencing critical recurring downtime for over 48 hours now with minimal communication from support:

Current situation:
- 16 separate downtime incidents in the past ~36 hours
- Total downtime: approximately 18+ hours
- Service availability: ~50% - the VM is down more than it's up
- Last support response: over 24 hours ago (just acknowledgment, no diagnostics or action plan)

Most recent downtime incidents:
- 1 hour ago: 1h 13min down
- 4 hours ago: 19min down
- 5 hours ago: 4min down
- 9 hours ago: 1h 34min down
- 14 hours ago: 2h 19min down
- 18 hours ago: 2h 14min down

This has been escalated multiple times in the ticket with no technical response or ETA.

I understand you're active here and helping others - could you please check on this ticket and provide an update? I need to know:
1. What's causing these recurring failures?
2. What action is being taken?
3. Whether I should plan to migrate elsewhere?

This is impacting production service and I've been very patient, but I need some communication and action at this point.

Thank you.

Our team is currently looking into this

yoursunny · February 15

@yoursunny said:
Our VNC is finally working, but we got dadfailed on the IPv6 address because someone else is using the same address.
What's a disaster!

2½ month update:

IPv6: new /128 assigned that isn't duplicate.
VNC: still broken. The VNC session disconnects at approximately 10 minutes. We checked tcpdump and it shows FIN packet sent from server.
Billing: we trust Host Rep's agreement on not starting 1-year clock until IPv6 and VNC both working.
Daniel: still certified mentally strong, and we are pleased to see his name in tickets. We've interacted with three of 4-person team so far in tickets.

We originally bought this to replace our Hostodo and migrate Seafile.
However, Hostodo bumped RAM from 1024 to 1536 MB, so that the migration is officially cancelled.
We are currently looking this DartNode like it's an art piece, with periodic VNC disconnects and hair pulling slow IO (login takes 5 seconds, will try YABS later).

yoursunny · February 15

@yoursunny said:

@yoursunny said:
Our VNC is finally working, but we got dadfailed on the IPv6 address because someone else is using the same address.
What's a disaster!

2½ month update:

IPv6: new /128 assigned that isn't duplicate.

VNC: still broken. The VNC session disconnects at approximately 10 minutes. We checked tcpdump and it shows FIN packet sent from server.

Billing: we trust Host Rep's agreement on not starting 1-year clock until IPv6 and VNC both working.

Daniel: still certified mentally strong, and we are pleased to see his name in tickets. We've interacted with three of 4-person team so far in tickets.

We originally bought this to replace our Hostodo and migrate Seafile.
However, Hostodo bumped RAM from 1024 to 1536 MB, so that the migration is officially cancelled.
We are currently looking this DartNode like it's an art piece, with periodic VNC disconnects and hair pulling slow IO (login takes 5 seconds, will try YABS later).

VNC bug sent to Engineering (ticket 17186), but we got Debian installed after struggling through four VNC disconnects, and now YABS is ready.
I/O speeds are pure sadness and ServerVerify gave D rating.
https://serververify.com/benchmarks/a644cdaa-bcfe-43eb-95ea-63655245c286

# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
#              Yet-Another-Bench-Script              #
#                     v2025-04-20                    #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #

Sun Feb 15 14:45:06 UTC 2026

Basic System Information:
---------------------------------
Uptime     : 0 days, 10 hours, 12 minutes
Processor  : Intel(R) Xeon(R) CPU E5-2697A v4 @ 2.60GHz
CPU cores  : 2 @ 2599.996 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 3.8 GiB
Swap       : 0.0 KiB
Disk       : 99.9 GiB
Distro     : Debian GNU/Linux 13 (trixie)
Kernel     : 6.12.69+deb13-amd64
VM Type    : KVM
IPv4/IPv6  : ✔ Online / ✔ Online

IPv6 Network Information:
---------------------------------
ISP        : Snaju Development
ASN        : AS399646 Snaju Development
Location   : Houston, Texas (TX)
Country    : United States

fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/sda5):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 1.88 MB/s      (471) | 23.34 MB/s     (364)
Write      | 1.90 MB/s      (476) | 23.83 MB/s     (372)
Total      | 3.78 MB/s      (947) | 47.17 MB/s     (736)
           |                      |                     
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 14.08 MB/s      (27) | 4.89 MB/s        (4)
Write      | 15.29 MB/s      (29) | 5.11 MB/s        (4)
Total      | 29.38 MB/s      (56) | 10.00 MB/s       (8)

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 1.73 Gbits/sec  | 2.06 Gbits/sec  | 107 ms         
Eranium         | Amsterdam, NL (100G)      | 1.70 Gbits/sec  | 1.84 Gbits/sec  | 115 ms         
Uztelecom       | Tashkent, UZ (10G)        | 880 Mbits/sec   | 1.00 Gbits/sec  | 209 ms         
Leaseweb        | Singapore, SG (10G)       | 2.65 Mbits/sec  | 731 Mbits/sec   | 220 ms         
Clouvider       | Los Angeles, CA, US (10G) | 3.14 Gbits/sec  | 5.64 Gbits/sec  | 38.1 ms        
Leaseweb        | NYC, NY, US (10G)         | 3.44 Gbits/sec  | 6.05 Gbits/sec  | 39.1 ms        
Edgoo           | Sao Paulo, BR (1G)        | 1.16 Gbits/sec  | 1.65 Gbits/sec  | 144 ms         

iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 1.71 Gbits/sec  | 2.00 Gbits/sec  | 107 ms         
Eranium         | Amsterdam, NL (100G)      | 1.38 Gbits/sec  | 2.02 Gbits/sec  | 114 ms         
Uztelecom       | Tashkent, UZ (10G)        | 988 Mbits/sec   | 833 Mbits/sec   | 209 ms         
Leaseweb        | Singapore, SG (10G)       | 903 Mbits/sec   | 965 Mbits/sec   | 221 ms         
Clouvider       | Los Angeles, CA, US (10G) | 3.02 Gbits/sec  | 4.79 Gbits/sec  | 38.1 ms        
Leaseweb        | NYC, NY, US (10G)         | 3.82 Gbits/sec  | 5.63 Gbits/sec  | 39.1 ms        
Edgoo           | Sao Paulo, BR (1G)        | 1.57 Gbits/sec  | 1.65 Gbits/sec  | 144 ms         

Geekbench 6 Benchmark Test:
---------------------------------
Test            | Value                         
                |                               
Single Core     | 797                           
Multi Core      | 1466                          
Full Test       | https://browser.geekbench.com/v6/cpu/16595267

YABS completed in 22 min 51 sec

JohnnySac · February 16

@yoursunny said:

@yoursunny said:

@yoursunny said:
Our VNC is finally working, but we got dadfailed on the IPv6 address because someone else is using the same address.
What's a disaster!

2½ month update:

IPv6: new /128 assigned that isn't duplicate.

VNC: still broken. The VNC session disconnects at approximately 10 minutes. We checked tcpdump and it shows FIN packet sent from server.

Billing: we trust Host Rep's agreement on not starting 1-year clock until IPv6 and VNC both working.

Daniel: still certified mentally strong, and we are pleased to see his name in tickets. We've interacted with three of 4-person team so far in tickets.

We originally bought this to replace our Hostodo and migrate Seafile.
However, Hostodo bumped RAM from 1024 to 1536 MB, so that the migration is officially cancelled.
We are currently looking this DartNode like it's an art piece, with periodic VNC disconnects and hair pulling slow IO (login takes 5 seconds, will try YABS later).

VNC bug sent to Engineering (ticket 17186), but we got Debian installed after struggling through four VNC disconnects, and now YABS is ready.
I/O speeds are pure sadness and ServerVerify gave D rating.
https://serververify.com/benchmarks/a644cdaa-bcfe-43eb-95ea-63655245c286
fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/sda5):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 1.88 MB/s      (471) | 23.34 MB/s     (364)
Write      | 1.90 MB/s      (476) | 23.83 MB/s     (372)
Total      | 3.78 MB/s      (947) | 47.17 MB/s     (736)
           |                      |                     
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 14.08 MB/s      (27) | 4.89 MB/s        (4)
Write      | 15.29 MB/s      (29) | 5.11 MB/s        (4)
Total      | 29.38 MB/s      (56) | 10.00 MB/s       (8)

Have same issue with the Texas $13.99 VPS disk. Disk write request average waiting time (w_await) is 424ms and at times going to 5+ seconds. Disk read has issues too but not as bad and not as frequent. Otherwise is a very nice VPS so hoping it will improve.

yoursunny · February 16

@yoursunny said:
We are currently looking this DartNode like it's an art piece, with periodic VNC disconnects and hair pulling slow IO (login takes 5 seconds, will try YABS later).

We turned our DartNode into an actual art piece, full article posted in Reviews so that it can appear on ServerVerify: DartNode $13.99 Flash Deal: The 9Gbps Houston Firehose vs. The 5 IOPS Soda Straw
Art gallery webpage with benchmarks: https://freaky-fast-digital-coma.yoursunny.dev/

Howdy, Stranger!

Categories

In this Discussion

DartNode: Black Friday Edition 2025 - Ryzen 9950X Dedicated Giveaway - Deals Inside - We Go to Space

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

DartNode: Black Friday Edition 2025 - Ryzen 9950X Dedicated Giveaway - Deals Inside - We Go to Space

Comments