Howdy, Stranger!

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

Sign In Register

Quick Links


Categories

In this Discussion

› › dasabo.com change my vps cpu
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.

dasabo.com change my vps cpu

sujrsujr Member
in General

Why did my CPU change? I remember it used to be 7950X3D, but now it’s 3900

«13456789

Comments

  • sujrsujr Member

    I didn't receive any prompt. The CPU of my vps was replaced with a 3900 with worse performance.

  • zGatozGato Member

    Your package didn't include a guaranteed CPU model.

    Thanked by 1kkrajk
  • fredo1664fredo1664 Member

    Sorry about that.

    Thanked by 1emgh
  • sujrsujr Member

    @zGato said:
    Your package didn't include a guaranteed CPU model.

    So they can replace my cpu at will?

  • zGatozGato Member
    edited November 12

    @sujr said:

    @zGato said:
    Your package didn't include a guaranteed CPU model.

    So they can replace my cpu at will?

    Not guaranteed = you can't blame them if they decide to do so.

  • sujrsujr Member

    @zGato said:

    @sujr said:

    @zGato said:
    Your package didn't include a guaranteed CPU model.

    So they can replace my cpu at will?

    Not guaranteed = you can't blame them if they decide to do so.

    Has your CPU been replaced?

  • zGatozGato Member
    edited November 12

    @sujr said:

    @zGato said:

    @sujr said:

    @zGato said:
    Your package didn't include a guaranteed CPU model.

    So they can replace my cpu at will?

    Not guaranteed = you can't blame them if they decide to do so.

    Has your CPU been replaced?

    Have no clue, but I have a 9 3900 as of right now.
    And doesn't seem like so since my VM hasn't rebooted

  • itsTomHarperitsTomHarper Member
    edited November 12

    Head to their site and Davide at @Dasabo is almost always online in the live chat and just ask him, he might be able to move you back to a x3d node.

  • DasaboDasabo Member, Patron Provider

    Thanks for tagging me @itsTomHarper .
    We don't change the node and cpu assigned to the user once the VM is created so yours are false accusations, prove otherwise.
    Did you open a ticket to ask for clarification from our support team before making a defamatory post?
    @sujr

    Thanked by 1sucre13
  • sujrsujr Member

    @Dasabo said:
    Thanks for tagging me @itsTomHarper .
    We don't change the node and cpu assigned to the user once the VM is created so yours are false accusations, prove otherwise.
    Did you open a ticket to ask for clarification from our support team before making a defamatory post?
    @sujr

    My vps was restarted. After the restart, my cpu changed. I didn't expect that a business like you would change the user's vps, so I didn't take a screenshot to keep the evidence.

  • sujrsujr Member

    @Dasabo said:
    Thanks for tagging me @itsTomHarper .
    We don't change the node and cpu assigned to the user once the VM is created so yours are false accusations, prove otherwise.
    Did you open a ticket to ask for clarification from our support team before making a defamatory post?
    @sujr

    I can take responsibility for what I say

  • DasaboDasabo Member, Patron Provider
    edited November 12

    Again, we have logs of everything that happens in the VMs, and no changes have been made.
    If you cannot prove what you say simply don't do it and don't accuse us.
    @Arkas Can you please ask this user who is throwing shitstorm at us to prove what he says.

  • sujrsujr Member

    @itsTomHarper said:
    Head to their site and Davide at @Dasabo is almost always online in the live chat and just ask him, he might be able to move you back to a x3d node.

    I can take responsibility for what I said. The CPU of my VPS definitely changed. But I didn't keep any relevant evidence. He relied on this to conclude that I was lying.

  • sujrsujr Member

    @Dasabo said:
    Again, we have logs of everything that happens in the VMs, and no changes have been made.
    If you cannot prove what you say simply don't do it and don't accuse us.
    @Arkas Can you please ask this user who is throwing shitstorm at us to prove what he says.

    Show me your evidence

  • DasaboDasabo Member, Patron Provider

    @zGato said:

    @sujr said:

    @zGato said:
    Your package didn't include a guaranteed CPU model.

    So they can replace my cpu at will?

    Not guaranteed = you can't blame them if they decide to do so.

    What you say is correct, but all the more reason we did not migrate his VPS to a different node with a different CPU because we have no reason to do so.
    He is simply talking bad about us without proving what he says.

  • sujrsujr Member

    @Dasabo said:

    @zGato said:

    @sujr said:

    @zGato said:
    Your package didn't include a guaranteed CPU model.

    So they can replace my cpu at will?

    Not guaranteed = you can't blame them if they decide to do so.

    What you say is correct, but all the more reason we did not migrate his VPS to a different node with a different CPU because we have no reason to do so.
    He is simply talking bad about us without proving what he says.

    What is my motive for slandering you? If the CPU was 3900 when I bought it, why did I come to you now? I have already bought it for 10 days.

  • DasaboDasabo Member, Patron Provider

    @sujr said:

    @Dasabo said:
    Again, we have logs of everything that happens in the VMs, and no changes have been made.
    If you cannot prove what you say simply don't do it and don't accuse us.
    @Arkas Can you please ask this user who is throwing shitstorm at us to prove what he says.

    Show me your evidence

    Open a ticket a we will show you that.

  • sujrsujr Member

    @Dasabo said:

    @zGato said:

    @sujr said:

    @zGato said:
    Your package didn't include a guaranteed CPU model.

    So they can replace my cpu at will?

    Not guaranteed = you can't blame them if they decide to do so.

    What you say is correct, but all the more reason we did not migrate his VPS to a different node with a different CPU because we have no reason to do so.
    He is simply talking bad about us without proving what he says.

    You think I'm trying to get a better CPU? Show me your evidence

  • sujrsujr Member

    @Dasabo said:

    @zGato said:

    @sujr said:

    @zGato said:
    Your package didn't include a guaranteed CPU model.

    So they can replace my cpu at will?

    Not guaranteed = you can't blame them if they decide to do so.

    What you say is correct, but all the more reason we did not migrate his VPS to a different node with a different CPU because we have no reason to do so.
    He is simply talking bad about us without proving what he says.

    I didn't keep any evidence. You said I was slandering you. Do you think this is reasonable? What is my motive for slandering you? Do you think I was lying just because I didn't have any evidence?

  • rattlecattlerattlecattle Member

    You can check old kernel boot logs with journalctl. The processor model would be listed there. Grep for AMD.

    sudo journalctl --list-boots

# for each boot check
sudo journalctl -k -b -1 | grep AMD
sudo journalctl -k -b -2 | grep AMD

...
    Thanked by 7yoursunny emgh tiitae naphtha martheen Porlam khalequzzaman
  • DasaboDasabo Member, Patron Provider

    @sujr said:

    @Dasabo said:

    @zGato said:

    @sujr said:

    @zGato said:
    Your package didn't include a guaranteed CPU model.

    So they can replace my cpu at will?

    Not guaranteed = you can't blame them if they decide to do so.

    What you say is correct, but all the more reason we did not migrate his VPS to a different node with a different CPU because we have no reason to do so.
    He is simply talking bad about us without proving what he says.

    You think I'm trying to get a better CPU? Show me your evidence

    I don't think so, I am sure ;)

  • sujrsujr Member

    @Dasabo said:

    @zGato said:

    @sujr said:

    @zGato said:
    Your package didn't include a guaranteed CPU model.

    So they can replace my cpu at will?

    Not guaranteed = you can't blame them if they decide to do so.

    What you say is correct, but all the more reason we did not migrate his VPS to a different node with a different CPU because we have no reason to do so.
    He is simply talking bad about us without proving what he says.

    You are the only VPS merchant I have ever purchased that will replace the CPU. I don't have the habit of keeping evidence.

  • DasaboDasabo Member, Patron Provider

    @sujr said:

    @Dasabo said:

    @zGato said:

    @sujr said:

    @zGato said:
    Your package didn't include a guaranteed CPU model.

    So they can replace my cpu at will?

    Not guaranteed = you can't blame them if they decide to do so.

    What you say is correct, but all the more reason we did not migrate his VPS to a different node with a different CPU because we have no reason to do so.
    He is simply talking bad about us without proving what he says.

    I didn't keep any evidence. You said I was slandering you. Do you think this is reasonable? What is my motive for slandering you? Do you think I was lying just because I didn't have any evidence?

    I don't think you are lying, I am sure of it because I checked the logs and you were never moved from the initial node you were assigned.

  • sujrsujr Member

    @rattlecattle said:
    You can check old kernel boot logs with journalctl. The processor model would be listed there. Grep for AMD.

    sudo journalctl --list-boots

# for each boot check
sudo journalctl -k -b -1 | grep AMD
sudo journalctl -k -b -2 | grep AMD

...

    sudo journalctl --list-boots
    0 d26db597e37142038a2441cb1cd24993 Tue 2024-11-12 22:40:46 CST—Wed 2>
    lines 1-1/1 (END)

    I can't see any information. I have reason to believe it was deleted

  • sujrsujr Member

    @sujr said:

    @rattlecattle said:
    You can check old kernel boot logs with journalctl. The processor model would be listed there. Grep for AMD.

    sudo journalctl --list-boots

# for each boot check
sudo journalctl -k -b -1 | grep AMD
sudo journalctl -k -b -2 | grep AMD

...

    sudo journalctl --list-boots
    0 d26db597e37142038a2441cb1cd24993 Tue 2024-11-12 22:40:46 CST—Wed 2>
    lines 1-1/1 (END)

    I can't see any information. I have reason to believe it was deleted

    sudo journalctl -k -b -1 | grep AMD
    Specifying boot ID or boot offset has no effect, no persistent journal was found.

  • sujrsujr Member

    @Dasabo said:

    @sujr said:

    @Dasabo said:

    @zGato said:

    @sujr said:

    @zGato said:
    Your package didn't include a guaranteed CPU model.

    So they can replace my cpu at will?

    Not guaranteed = you can't blame them if they decide to do so.

    What you say is correct, but all the more reason we did not migrate his VPS to a different node with a different CPU because we have no reason to do so.
    He is simply talking bad about us without proving what he says.

    I didn't keep any evidence. You said I was slandering you. Do you think this is reasonable? What is my motive for slandering you? Do you think I was lying just because I didn't have any evidence?

    I don't think you are lying, I am sure of it because I checked the logs and you were never moved from the initial node you were assigned.

    Show me your logs

  • DasaboDasabo Member, Patron Provider
    edited November 12

    @sujr said:

    @rattlecattle said:
    You can check old kernel boot logs with journalctl. The processor model would be listed there. Grep for AMD.

    sudo journalctl --list-boots

# for each boot check
sudo journalctl -k -b -1 | grep AMD
sudo journalctl -k -b -2 | grep AMD

...

    sudo journalctl --list-boots
    0 d26db597e37142038a2441cb1cd24993 Tue 2024-11-12 22:40:46 CST—Wed 2>
    lines 1-1/1 (END)

    I can't see any information. I have reason to believe it was deleted

    Now you're saying we deleted them? without proving our access to the VM?
    Now it's too much.
    I no longer respond to your accusations on LET, open a ticket for assistance.
    I will let the admins decide on your false accusations.
    @DP @Arkas

  • sujrsujr Member

    @Dasabo said:

    @sujr said:

    @rattlecattle said:
    You can check old kernel boot logs with journalctl. The processor model would be listed there. Grep for AMD.

    sudo journalctl --list-boots

# for each boot check
sudo journalctl -k -b -1 | grep AMD
sudo journalctl -k -b -2 | grep AMD

...

    sudo journalctl --list-boots
    0 d26db597e37142038a2441cb1cd24993 Tue 2024-11-12 22:40:46 CST—Wed 2>
    lines 1-1/1 (END)

    I can't see any information. I have reason to believe it was deleted

    Now you're saying we deleted them? without proving our access to the VM?
    Now it's too much.
    @DP @Arkas

    If you have not visited my vps privately, why can't I see any information?

  • sujrsujr Member

    @Dasabo said:

    @sujr said:

    @rattlecattle said:
    You can check old kernel boot logs with journalctl. The processor model would be listed there. Grep for AMD.

    sudo journalctl --list-boots

# for each boot check
sudo journalctl -k -b -1 | grep AMD
sudo journalctl -k -b -2 | grep AMD

...

    sudo journalctl --list-boots
    0 d26db597e37142038a2441cb1cd24993 Tue 2024-11-12 22:40:46 CST—Wed 2>
    lines 1-1/1 (END)

    I can't see any information. I have reason to believe it was deleted

    Now you're saying we deleted them? without proving our access to the VM?
    Now it's too much.
    I no longer respond to your accusations on LET, open a ticket for assistance.
    I will let the admins decide on your false accusations.
    @DP @Arkas

    Please provide evidence to prove that my CPU has always been 3900

  • sujrsujr Member

    @Dasabo said:

    @sujr said:

    @rattlecattle said:
    You can check old kernel boot logs with journalctl. The processor model would be listed there. Grep for AMD.

    sudo journalctl --list-boots

# for each boot check
sudo journalctl -k -b -1 | grep AMD
sudo journalctl -k -b -2 | grep AMD

...

    sudo journalctl --list-boots
    0 d26db597e37142038a2441cb1cd24993 Tue 2024-11-12 22:40:46 CST—Wed 2>
    lines 1-1/1 (END)

    I can't see any information. I have reason to believe it was deleted

    Now you're saying we deleted them? without proving our access to the VM?
    Now it's too much.
    I no longer respond to your accusations on LET, open a ticket for assistance.
    I will let the admins decide on your false accusations.
    @DP @Arkas

    Why are you so afraid to reply to me on let? Post your evidence on let for everyone to see

Sign In or Register to comment.