Howdy, Stranger!

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


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.

MevSpace - The worst dedicated server in my experience. My honest review.

flexinovflexinov Member
edited 9:45AM in Providers

Hiya LowEndTalk, this is my first post here, after being a long time reader.

I run my own VMs via Proxmox, and recently I decided to move to MevSpace due to their prices and reputation in the market.

This was one of the worst decisions in my server-based career.
The server is UNUSABLE.
The server is dying every 5-6 hours like a clock, and only comes back up after a reboot.

The support have send technicians to see the server.
Their and our tests showed damaged RAM and SSD.

They told us, that backups is our own thing to look out for, and that they replaced the RAM.

They have given us the second server, messed up our configuration (RAID1 instead of RAID0), and told us it should be working. We are experiencing THE EXACT SAME ISSUE on their end. We are getting "ACPI power state transition occurred" error, and the whole node dies. We have lost over $500 using this service, I cannot recommend it any less...

This all happened in the span of 6 days!
We started to have issues starting day 2 of owning the server.

Comments

  • xHostsxHosts Patron Provider, Veteran

    Any screenshots of your tickets ?

    Thanked by 2forest itzsenu
  • NekoparaNekopara Member

    sounds exactly like the issue i had a year ago with a dedi with them. would randomly crash/get unrespronsive. they refused a refund after technicians looked at it and "everything was fine"

  • rpqurpqu Member

    6 days, $500
    Should have demand prorated refund immediately

  • AlyxAlyx Member, Host Rep

    Crying about loosing money and then using RAID0 with no own backups.

    Sure buddy 🤣

    Thanked by 2forest mrerenk
  • rpqurpqu Member

    @Alyx said:
    Crying about loosing money and then using RAID0 with no own backups.

    Sure buddy 🤣

    YOLO

  • @Alyx said:
    Crying about loosing money and then using RAID0 with no own backups.

    Sure buddy 🤣

    Now this seems to be referring to the money spend on the server rather than whatever they hosted since "shit don't work"

  • Update the BIOS from IPMI and reset it to default settings. Or ask them to do it

  • @Alyx said:
    Crying about loosing money and then using RAID0 with no own backups.

    Sure buddy 🤣

    It doesn't nullify the provider's incompetency and failed to provide a stable server for what client paid.

    Even if he sacrifice the data, the server still unusable and have hardware defects (According to OP)

  • flexinovflexinov Member

    @luckypenguin said:
    Update the BIOS from IPMI and reset it to default settings. Or ask them to do it

    We have done that for the first server, as BIOS was extremely outdated. It did not solved the problem

  • labzelabze Member, Patron Provider

    Is this an AMD Ryzen system and using Nested Virtualization with Proxmox?

    What you are describing has long been a known issue with Ryzen systems.

  • flexinovflexinov Member

    @Incognion said:

    @Alyx said:
    Crying about loosing money and then using RAID0 with no own backups.

    Sure buddy 🤣

    It doesn't nullify the provider's incompetency and failed to provide a stable server for what client paid.

    Even if he sacrifice the data, the server still unusable and have hardware defects (According to OP)

    It shouldn't matter which which RAID we are using for a setup lol.
    It should matter if server dies every 5-6 hours

  • flexinovflexinov Member

    @xHosts said:
    Any screenshots of your tickets ?

    incoming!

  • flexinovflexinov Member

    @labze said:
    Is this an AMD Ryzen system and using Nested Virtualization with Proxmox?

    What you are describing has long been a known issue with Ryzen systems.

    yes, we are running AMD Ryzen 9 7950x with 192GB of ram.

    we thought that was the issue too, but support confirmed the issue with RAM and SSD

  • flexinovflexinov Member

    Also, currently during migration between servers, the SSD just keep on dying LOL.

    root@n1a90ee:~# cat /sys/block/nvme1n1/device/model
    cat /sys/class/nvme/nvme1/state 2>/dev/null
    IRP-SSDPR-P44S-2K0-80
    dead

  • monmon Member

    @flexinov said: IRP-SSDPR-P44S-2K0-80

    That's Goodram IRDM Pro Slim 2TB. Consumer gaming drive. I assume you are not renting a gaming console, aren't you?

  • flexinovflexinov Member

    @mon said:

    @flexinov said: IRP-SSDPR-P44S-2K0-80

    That's Goodram IRDM Pro Slim 2TB. Consumer gaming drive. I assume you are not renting a gaming console, aren't you?

    Nope, we are renting their Dedicated Server AMD line.
    Just googled the RAM, LMAO i am speechless

  • monmon Member

    jokes aside: you should look into dmesg, NVMe driver usually complains loudly before giving up. Could be some incompatibility avoidable with some pci magic.

  • @Alyx said:
    Crying about loosing money and then using RAID0 with no own backups.

    Sure buddy 🤣

    His end-user's probably don't expect backups nor does he, he is selling VM's or using them for profit clearly why would backups matter here?

    It matter's Mevspace is still ass 3 years later.

  • flexinovflexinov Member

    @flexinov said:

    @mon said:

    @flexinov said: IRP-SSDPR-P44S-2K0-80

    That's Goodram IRDM Pro Slim 2TB. Consumer gaming drive. I assume you are not renting a gaming console, aren't you?

    Nope, we are renting their Dedicated Server AMD line.
    Just googled the RAM, LMAO i am speechless

    Circling back to this, i just found more info about the actual hardware:

    Motherboard: TUF GAMING A620-PRO WIFI
    SSD: IRP-SSDPR-P44S-2K0-80

    RAM (raw dump):

    root@n60d801:~# dmidecode -t memory

    dmidecode 3.6

    Getting SMBIOS data from sysfs.
    SMBIOS 3.6.0 present.

    Handle 0x0013, DMI type 16, 23 bytes
    Physical Memory Array
    Location: System Board Or Motherboard
    Use: System Memory
    Error Correction Type: None
    Maximum Capacity: 256 GB
    Error Information Handle: 0x0012
    Number Of Devices: 4

    Handle 0x0016, DMI type 17, 92 bytes
    Memory Device
    Array Handle: 0x0013
    Error Information Handle: 0x0015
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 48 GB
    Form Factor: DIMM
    Set: None
    Locator: DIMM 0
    Bank Locator: P0 CHANNEL A
    Type: DDR5
    Type Detail: Synchronous Unbuffered (Unregistered)
    Speed: 5600 MT/s
    Manufacturer: Wilk Elektronik S.A
    Serial Number: 0000C1D4
    Asset Tag: Not Specified
    Part Number: IL-5600D564L46/48G
    Rank: 2
    Configured Memory Speed: 3600 MT/s
    Minimum Voltage: 1.1 V
    Maximum Voltage: 1.1 V
    Configured Voltage: 1.1 V
    Memory Technology: DRAM
    Memory Operating Mode Capability: Volatile memory
    Firmware Version: Unknown
    Module Manufacturer ID: Bank 8, Hex 0x5D
    Module Product ID: Unknown
    Memory Subsystem Controller Manufacturer ID: Unknown
    Memory Subsystem Controller Product ID: Unknown
    Non-Volatile Size: None
    Volatile Size: 48 GB
    Cache Size: None
    Logical Size: None

    Handle 0x0019, DMI type 17, 92 bytes
    Memory Device
    Array Handle: 0x0013
    Error Information Handle: 0x0018
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 48 GB
    Form Factor: DIMM
    Set: None
    Locator: DIMM 1
    Bank Locator: P0 CHANNEL A
    Type: DDR5
    Type Detail: Synchronous Unbuffered (Unregistered)
    Speed: 5600 MT/s
    Manufacturer: Wilk Elektronik S.A
    Serial Number: 0000C1FB
    Asset Tag: Not Specified
    Part Number: IL-5600D564L46/48G
    Rank: 2
    Configured Memory Speed: 3600 MT/s
    Minimum Voltage: 1.1 V
    Maximum Voltage: 1.1 V
    Configured Voltage: 1.1 V
    Memory Technology: DRAM
    Memory Operating Mode Capability: Volatile memory
    Firmware Version: Unknown
    Module Manufacturer ID: Bank 8, Hex 0x5D
    Module Product ID: Unknown
    Memory Subsystem Controller Manufacturer ID: Unknown
    Memory Subsystem Controller Product ID: Unknown
    Non-Volatile Size: None
    Volatile Size: 48 GB
    Cache Size: None
    Logical Size: None

    Handle 0x001C, DMI type 17, 92 bytes
    Memory Device
    Array Handle: 0x0013
    Error Information Handle: 0x001B
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 48 GB
    Form Factor: DIMM
    Set: None
    Locator: DIMM 0
    Bank Locator: P0 CHANNEL B
    Type: DDR5
    Type Detail: Synchronous Unbuffered (Unregistered)
    Speed: 5600 MT/s
    Manufacturer: Wilk Elektronik S.A
    Serial Number: 0000C1CF
    Asset Tag: Not Specified
    Part Number: IL-5600D564L46/48G
    Rank: 2
    Configured Memory Speed: 3600 MT/s
    Minimum Voltage: 1.1 V
    Maximum Voltage: 1.1 V
    Configured Voltage: 1.1 V
    Memory Technology: DRAM
    Memory Operating Mode Capability: Volatile memory
    Firmware Version: Unknown
    Module Manufacturer ID: Bank 8, Hex 0x5D
    Module Product ID: Unknown
    Memory Subsystem Controller Manufacturer ID: Unknown
    Memory Subsystem Controller Product ID: Unknown
    Non-Volatile Size: None
    Volatile Size: 48 GB
    Cache Size: None
    Logical Size: None

    Handle 0x001F, DMI type 17, 92 bytes
    Memory Device
    Array Handle: 0x0013
    Error Information Handle: 0x001E
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 48 GB
    Form Factor: DIMM
    Set: None
    Locator: DIMM 1
    Bank Locator: P0 CHANNEL B
    Type: DDR5
    Type Detail: Synchronous Unbuffered (Unregistered)
    Speed: 5600 MT/s
    Manufacturer: Wilk Elektronik S.A
    Serial Number: 0000C206
    Asset Tag: Not Specified
    Part Number: IL-5600D564L46/48G
    Rank: 2
    Configured Memory Speed: 3600 MT/s
    Minimum Voltage: 1.1 V
    Maximum Voltage: 1.1 V
    Configured Voltage: 1.1 V
    Memory Technology: DRAM
    Memory Operating Mode Capability: Volatile memory
    Firmware Version: Unknown
    Module Manufacturer ID: Bank 8, Hex 0x5D
    Module Product ID: Unknown
    Memory Subsystem Controller Manufacturer ID: Unknown
    Memory Subsystem Controller Product ID: Unknown
    Non-Volatile Size: None
    Volatile Size: 48 GB
    Cache Size: None
    Logical Size: None

  • flexinovflexinov Member

    @mon said:
    jokes aside: you should look into dmesg, NVMe driver usually complains loudly before giving up. Could be some incompatibility avoidable with some pci magic.

    searched using:

    dmesg | grep -iE "ecc|mce|error|corrected"

    came back clean

  • Gaming hardware is not a shock at this price point, Hetzner essentially does the same with most components out-side there enterprise line, the mass savings up-front is logical to them for the increased replacements.

    What is, is the dedi turning off all the time which I can also vouch I've had countless issues with mevspace when I had 8+ servers with them.

  • flexinovflexinov Member

    @flexinov said:
    Also, currently during migration between servers, the SSD just keep on dying LOL.

    root@n1a90ee:~# cat /sys/block/nvme1n1/device/model
    cat /sys/class/nvme/nvme1/state 2>/dev/null
    IRP-SSDPR-P44S-2K0-80
    dead

    Both SSDs died on the main server.
    Server is fully dead and unresponsive after reboots.
    I think PS5 compatible SSD might have some issues in a server setup...

    RIP.

  • @flexinov said:

    @Incognion said:

    @Alyx said:
    Crying about loosing money and then using RAID0 with no own backups.

    Sure buddy 🤣

    It doesn't nullify the provider's incompetency and failed to provide a stable server for what client paid.

    Even if he sacrifice the data, the server still unusable and have hardware defects (According to OP)

    It shouldn't matter which which RAID we are using for a setup lol.
    It should matter if server dies every 5-6 hours

    Dude! I was supporting you and replying @Alyx

    Now I'm really confused if it's really provider's problem or yours (misunderstanding) lol

  • flexinovflexinov Member

    @Incognion said:

    @flexinov said:

    @Incognion said:

    @Alyx said:
    Crying about loosing money and then using RAID0 with no own backups.

    Sure buddy 🤣

    It doesn't nullify the provider's incompetency and failed to provide a stable server for what client paid.

    Even if he sacrifice the data, the server still unusable and have hardware defects (According to OP)

    It shouldn't matter which which RAID we are using for a setup lol.
    It should matter if server dies every 5-6 hours

    Dude! I was supporting you and replying @Alyx

    Now I'm really confused if it's really provider's problem or yours (misunderstanding) lol

    haha sorry, i was trying to agree with you!

    Thanked by 1Incognion
Sign In or Register to comment.