Howdy, Stranger!

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


$100 if you fix this Proxmox VM issue - Page 5
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.

$100 if you fix this Proxmox VM issue

1235»

Comments

  • mwmw Member

    @Falzo said:

    @mw said:

    @Falzo said:
    Is there any hardware environment where this is working as expected with proxmox? Like the one you had before.
    I am still not convinced that in between nothing changed on the providers end. Like some updates/upgrades in their routers/switches whatever...

    Before, yes the 7950X before it died

    Now, yes the other two dozen dedis running Proxmox in the same rack using the same prefix

    Interesting. Time to get creative and clone one of the working proxmox servers then (expecting them to not be at the all latest version for kernel and co).

    i think the fact that after booting from the same OS install that worked before it wasnt working, this might not be useful. at this point im not really concerned about ever using the box in production again as the VMs were spun back up on other servers/work redirection to another provider

    the only reason im still invested in this is that its genuinely interesting and might help someone down the line if the cause is identified

  • PA733PA733 Member

    Hey OP, just checking in – has this issue been resolved yet?

    Also, are you open to trying a routing solution (not bridge ) like PVE SDN? I might be able to help out with that if you're interested!

  • mwmw Member

    @PA733 said:
    Hey OP, just checking in – has this issue been resolved yet?

    Also, are you open to trying a routing solution (not bridge ) like PVE SDN? I might be able to help out with that if you're interested!

    I'll check out your PM

  • mwmw Member
    edited April 21

    Provider:

    Quick update about the Ryzen as well, going in on Tuesday evening with some hardware changes which should sort this once and for all, will use a intel nic.

    Hoping tomorrow comes with a fix

  • @mw said: will use a intel nic

    Maybe that's why Hetzner for all Ryzens use Intel NIC (iNIC)..

  • mwmw Member

    @mw said:
    Provider:

    Quick update about the Ryzen as well, going in on Tuesday evening with some hardware changes which should sort this once and for all, will use a intel nic.

    Hoping tomorrow comes with a fix

    Perhaps today :'(

  • FalzoFalzo Member

    @mw said:

    @mw said:
    Provider:

    Quick update about the Ryzen as well, going in on Tuesday evening with some hardware changes which should sort this once and for all, will use a intel nic.

    Hoping tomorrow comes with a fix

    Perhaps today :'(

    inspired by BilohRulesUpdate™

  • mwmw Member

    @Falzo said:

    @mw said:

    @mw said:
    Provider:

    Quick update about the Ryzen as well, going in on Tuesday evening with some hardware changes which should sort this once and for all, will use a intel nic.

    Hoping tomorrow comes with a fix

    Perhaps today :'(

    inspired by BilohRulesUpdate™

    i didnt spot the rule:

    Bumping threads because you're impatient.

    my bad yall ill post next when there's an update

  • Can’t wait to find out.

    I’m a principal network architect for a nationwide ISP during the day.

    DM’d you - if nobody has figured it out yet I’d love a chance to do so for free to share the knowledge back here.

    Thanked by 1mw
  • no updates till now? april is ending shortly...

  • mwmw Member

    @nanankcornering said:
    no updates till now? april is ending shortly...

    every time i ask its "tomorrow" and "shortly" so doesnt seem so

  • mwmw Member

    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Thanked by 1Falzo
  • FalzoFalzo Member
    edited June 1

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Appreciated! you can send USDT here: TBXjLTEQu5Waqh52bvtUdvV36fJAoDvvzD

    Ed: and btw, I think pinning the problem on the nic and fw is rather bs. But that's just me... easier to blame some weird hw constellation than admittung some config error somewhere.

    Thanked by 1Frameworks
  • AndreixAndreix Member, Host Rep

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    LooooooL. Still Royale?

    Thanked by 1mw
  • @Falzo said:

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Appreciated! you can send USDT here: TBXjLTEQu5Waqh52bvtUdvV36fJAoDvvzD

    Ed: and btw, I think pinning the problem on the nic and fw is rather bs. But that's just me... easier to blame some weird hw constellation than admittung some config error somewhere.

    Faulty silicon in nics and faulty drivers are pretty common to any experienced server administrator. You sound amateurish with that comment.

  • FalzoFalzo Member

    @TimboJones said:

    @Falzo said:

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Appreciated! you can send USDT here: TBXjLTEQu5Waqh52bvtUdvV36fJAoDvvzD

    Ed: and btw, I think pinning the problem on the nic and fw is rather bs. But that's just me... easier to blame some weird hw constellation than admittung some config error somewhere.

    Faulty silicon in nics and faulty drivers are pretty common to any experienced server administrator. You sound amateurish with that comment.

    Yeah, it is so common that they needed two months to figure it out, despite having switched all hardware weeks ago already...

    If it is amateurish to have doubts in such explanations, you can call me that 🤷🏻‍♂️

  • AndreixAndreix Member, Host Rep
    edited June 2

    @Falzo said:

    @TimboJones said:

    @Falzo said:

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Appreciated! you can send USDT here: TBXjLTEQu5Waqh52bvtUdvV36fJAoDvvzD

    Ed: and btw, I think pinning the problem on the nic and fw is rather bs. But that's just me... easier to blame some weird hw constellation than admittung some config error somewhere.

    Faulty silicon in nics and faulty drivers are pretty common to any experienced server administrator. You sound amateurish with that comment.

    Yeah, it is so common that they needed two months to figure it out, despite having switched all hardware weeks ago already...

    If it is amateurish to have doubts in such explanations, you can call me that 🤷🏻‍♂️

    Agree with Falzo here. Totally disappointed by this situation's handling of the provider... hope they heavily compensated the OP.

    Thanked by 1Frameworks
  • avamaxavamax Member

    bounty still ongoing ?

  • TimboJonesTimboJones Member
    edited June 2

    @Falzo said:

    @TimboJones said:

    @Falzo said:

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Appreciated! you can send USDT here: TBXjLTEQu5Waqh52bvtUdvV36fJAoDvvzD

    Ed: and btw, I think pinning the problem on the nic and fw is rather bs. But that's just me... easier to blame some weird hw constellation than admittung some config error somewhere.

    Faulty silicon in nics and faulty drivers are pretty common to any experienced server administrator. You sound amateurish with that comment.

    Yeah, it is so common that they needed two months to figure it out, despite having switched all hardware weeks ago already...

    If it is amateurish to have doubts in such explanations, you can call me that 🤷🏻‍♂️

    Switching out the hardware for the same would be how to confirm it's firmware issue...

    Go and read up on how long it takes Intel to find and then provide solutions for bugs in i225 and i226 chipsets. Years? Yep. Or in docsis 3.0 modems (puma).

    You'd rather it be a made up non-existent config issue than physically bad hardware? I have no idea why. It was the attitude that it was a misconfigured software issue that caused the solution to take two months, so that's the wrong conclusion.

  • mwmw Member

    @Falzo said:

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Appreciated! you can send USDT here: TBXjLTEQu5Waqh52bvtUdvV36fJAoDvvzD

    Ed: and btw, I think pinning the problem on the nic and fw is rather bs. But that's just me... easier to blame some weird hw constellation than admittung some config error somewhere.

    my bad homie i was getting my shit rocked by jeffrey bezos this week

    https://tronscan.org/#/transaction/6e017c03f85bad4a64dd3b20601e45d7edf3a1ba72e36603c9ca3468a9b161e0

    Thanked by 1Falzo
  • mwmw Member

    @Andreix said:

    @Falzo said:

    @TimboJones said:

    @Falzo said:

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Appreciated! you can send USDT here: TBXjLTEQu5Waqh52bvtUdvV36fJAoDvvzD

    Ed: and btw, I think pinning the problem on the nic and fw is rather bs. But that's just me... easier to blame some weird hw constellation than admittung some config error somewhere.

    Faulty silicon in nics and faulty drivers are pretty common to any experienced server administrator. You sound amateurish with that comment.

    Yeah, it is so common that they needed two months to figure it out, despite having switched all hardware weeks ago already...

    If it is amateurish to have doubts in such explanations, you can call me that 🤷🏻‍♂️

    Agree with Falzo here. Totally disappointed by this situation's handling of the provider... hope they heavily compensated the OP.

    what would yall even consider appropriate compensation?

  • AndreixAndreix Member, Host Rep

    @mw said:

    @Andreix said:

    @Falzo said:

    @TimboJones said:

    @Falzo said:

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Appreciated! you can send USDT here: TBXjLTEQu5Waqh52bvtUdvV36fJAoDvvzD

    Ed: and btw, I think pinning the problem on the nic and fw is rather bs. But that's just me... easier to blame some weird hw constellation than admittung some config error somewhere.

    Faulty silicon in nics and faulty drivers are pretty common to any experienced server administrator. You sound amateurish with that comment.

    Yeah, it is so common that they needed two months to figure it out, despite having switched all hardware weeks ago already...

    If it is amateurish to have doubts in such explanations, you can call me that 🤷🏻‍♂️

    Agree with Falzo here. Totally disappointed by this situation's handling of the provider... hope they heavily compensated the OP.

    what would yall even consider appropriate compensation?

    At least the server cost x downtime period.
    eg. if server is $100 and was down for 3months, $300.

  • mwmw Member

    @Andreix said:

    @mw said:

    @Andreix said:

    @Falzo said:

    @TimboJones said:

    @Falzo said:

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Appreciated! you can send USDT here: TBXjLTEQu5Waqh52bvtUdvV36fJAoDvvzD

    Ed: and btw, I think pinning the problem on the nic and fw is rather bs. But that's just me... easier to blame some weird hw constellation than admittung some config error somewhere.

    Faulty silicon in nics and faulty drivers are pretty common to any experienced server administrator. You sound amateurish with that comment.

    Yeah, it is so common that they needed two months to figure it out, despite having switched all hardware weeks ago already...

    If it is amateurish to have doubts in such explanations, you can call me that 🤷🏻‍♂️

    Agree with Falzo here. Totally disappointed by this situation's handling of the provider... hope they heavily compensated the OP.

    what would yall even consider appropriate compensation?

    At least the server cost x downtime period.
    eg. if server is $100 and was down for 3months, $300.

    we got a month free + didn't pay for the downtime period

    Thanked by 1Falzo
  • FalzoFalzo Member

    @mw said:

    @Falzo said:

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Appreciated! you can send USDT here: TBXjLTEQu5Waqh52bvtUdvV36fJAoDvvzD

    Ed: and btw, I think pinning the problem on the nic and fw is rather bs. But that's just me... easier to blame some weird hw constellation than admittung some config error somewhere.

    my bad homie i was getting my shit rocked by jeffrey bezos this week

    https://tronscan.org/#/transaction/6e017c03f85bad4a64dd3b20601e45d7edf3a1ba72e36603c9ca3468a9b161e0

    well received and thanks for coming through - much appreciated! gonna donate to some campaigns to put it to good use.

    Thanked by 2mw ehab
  • AndreixAndreix Member, Host Rep

    @mw said:

    @Andreix said:

    @mw said:

    @Andreix said:

    @Falzo said:

    @TimboJones said:

    @Falzo said:

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Appreciated! you can send USDT here: TBXjLTEQu5Waqh52bvtUdvV36fJAoDvvzD

    Ed: and btw, I think pinning the problem on the nic and fw is rather bs. But that's just me... easier to blame some weird hw constellation than admittung some config error somewhere.

    Faulty silicon in nics and faulty drivers are pretty common to any experienced server administrator. You sound amateurish with that comment.

    Yeah, it is so common that they needed two months to figure it out, despite having switched all hardware weeks ago already...

    If it is amateurish to have doubts in such explanations, you can call me that 🤷🏻‍♂️

    Agree with Falzo here. Totally disappointed by this situation's handling of the provider... hope they heavily compensated the OP.

    what would yall even consider appropriate compensation?

    At least the server cost x downtime period.
    eg. if server is $100 and was down for 3months, $300.

    we got a month free + didn't pay for the downtime period

    If you dont have any active clients, that could work. Else, I would see the downtime as a "bad work" done to your potential earnings.

  • ehabehab Member

    Finally Falzo got paid.

    Thanked by 1Marx
  • AndreixAndreix Member, Host Rep

    @Falzo said:

    @mw said:

    @Falzo said:

    @mw said:
    Final update

    From provider:

    different batch nic (same type just different batch) updating nic firmware + different pci riser + updating motherboard firmware

    Now running Mellanox MT28800 ConnectX-5 100G and it works.

    @Falzo post your TRC20 address

    Appreciated! you can send USDT here: TBXjLTEQu5Waqh52bvtUdvV36fJAoDvvzD

    Ed: and btw, I think pinning the problem on the nic and fw is rather bs. But that's just me... easier to blame some weird hw constellation than admittung some config error somewhere.

    my bad homie i was getting my shit rocked by jeffrey bezos this week

    https://tronscan.org/#/transaction/6e017c03f85bad4a64dd3b20601e45d7edf3a1ba72e36603c9ca3468a9b161e0

    well received and thanks for coming through - much appreciated! gonna donate to some campaigns to put it to good use.

    I do have some Google Ads campaigns that could use them for sure. Thanks! <3

  • FalzoFalzo Member

    @ehab said:
    Finally Falzo got paid.

    need new pants soap? I'll buy, you'll pick up ;-) ;-)

    Thanked by 1ehab
Sign In or Register to comment.