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.

ChunkServer Review: Unusable Hypervisor, Read-Only Root Disk, and Unresponsive Support

dgaroorkeedgaroorkee Member
edited 7:48PM in Reviews

Provider: ChunkServer (chunkserver.com)
Plan: 3 vCore Xeon Gold 6122 / 6 GB RAM / 100 GB NVMe / 4Gbps Network (Amsterdam, NL)
Price: €24.99/Year (Promotional deal from LET thread)
Purchase Date: April 25, 2026 (Invoice #5474)
Status: Unusable / Broken Infrastructure

Overview

I am writing this review to share my experience with ChunkServer over the past few months. While the specs advertised on LowEndTalk looked solid for the price, the VPS has been completely unusable due to underlying storage/hypervisor failures, compounded by days of ticket silence.

Timeline of Events

1. Unfulfilled Promotional Freebie (April 2026)

  • April 25, 2026: Purchased the VPS plan.
  • April 26, 2026: Submitted Ticket #XWA-981947 to claim the promotional order bonus advertised on their LET offer thread.
  • April 30, 2026 (4 days later): Support replied offering +10GB disk space. I agreed immediately and asked them to proceed.
  • Result: The update was never applied. After waiting weeks with no action, I closed the ticket on May 18.

2. Basic Support Delays

Routine requests, such as configuring rDNS/PTR records, routinely took 4 to 7 days per ticket response.

3. Critical Infrastructure Failure (July 2026)

The server stopped booting properly and started throwing filesystem errors. Even after rebuilding/rebooting via VirtFusion, the root filesystem immediately remounts as read-only (ro) on boot, preventing any system administration or temporary file creation.

  • Ticket Opened: Wednesday, July 15, 2026

  • Diagnostics provided to support:
    ```bash
    root@chnk1nl:~# mount | grep ' on / '
    /dev/vda3 on / type xfs (ro,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)

    root@chnk1nl:~# touch /tmp/testfile
    touch: cannot touch '/tmp/testfile': Read-only file system

July 19, 2026 (4 days later): Support replied stating they "made some adjustments" and asked me to check.

July 19, 2026 (same day): I tested and verified the issue was not resolved. The root filesystem was still mounting as ro. Because this is a fresh server with no production data, I explicitly requested a node migration or complete disk rebuild.

Current Status: Crickets. Support has stopped responding, and the server remains completely dead in the water.

Conclusion & Verdict
There is a big difference between "unmanaged hosting" (where the customer manages the OS) and broken host nodes. An XFS filesystem remounting read-only on every boot after a fresh deployment points to host-level I/O errors or storage backend failure.

Performance / Stability: 0/10 (Cannot write to disk)

Support Response Time: 1/10 (4+ days average delay)

Value for Money: 0/10 (Spent €24.99 for a useless IP address)

If you are looking for a reliable VPS where the hypervisor functions properly, look elsewhere.

Comments

Sign In or Register to comment.