Fedora 29 and 30 - EDAC skx: Can't Get tolm/tohm Error on Vultr
-
Upon boot, I am getting the EDAC skx: Can't Get tolm/tohm error after upgrading my Vultr instances from Fedora 29 to Fedora 30. Has anyone else experienced this? Is there a fix for it?
EDIT: Changed the thread title to reflect my findings in posts 16-21
-
@wrx7m Have you asked Vultr support yet?
-
@travisdh1 said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
@wrx7m Have you asked Vultr support yet?
Not yet. I wasn't sure how common it was. I'll try them.
-
@wrx7m Did you use a custom ISO or their image?
-
@wirestyle22 said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
@wrx7m Did you use a custom ISO or their image?
Their Fedora 29 image. Then upgraded to 30 using dnf upgrade.
-
Put a ticket in with Vultr. I'll see what they have to say.
-
That was fast. No help from them-
"Hello,Thank you for your inquiry. Please note that our staff is responsible for infrastructure and system critical functions of the platform itself, not for administration of individual instances. You, or members of your project team are responsible for the administration of the VPS instance deployments on your account.
In the event that you have difficulties making a deployment, or performing some other task within your my.vultr.com account portal, please feel free to raise a ticket and we will address any platform issues where applicable.
While our services are self-managed, we do offer an extensive community library of tutorials in our Vultr Docs section which you can review at:
Can't find what you are looking for? You can request new articles from our community by visiting this URL:
-
@wrx7m well, you have to be realistic. That's not a question that they can provide support for. It's not a Vultr issue, they can't start being system admins for instances. They don't have the staff, experience, or access for that, and their business model doesn't accommodate the cost. The cost of system admin is 100x the cost of providing a VM. Or more.
-
@wrx7m I would try to create a new instance with their image of 29 and upgrade to 30 to see if it works. If that doesn't work then I'd try to re-create what you are running on a custom iso and see if you can upgrade that successfully.
-
@scottalanmiller said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
@wrx7m well, you have to be realistic. That's not a question that they can provide support for. It's not a Vultr issue, they can't start being system admins for instances. They don't have the staff, experience, or access for that, and their business model doesn't accommodate the cost. The cost of system admin is 100x the cost of providing a VM. Or more.
Totally. I didn't think they would be able to help, and wasn't thinking of involving them until someone suggested it in this thread. I thought maybe they would say that you can't upgrade one of our Fedora 29 instances to 30 because the virtual machines will complain about drivers or something.
-
@wirestyle22 said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
@wrx7m I would try to create a new instance with their image of 29 and upgrade to 30 to see if it works. If that doesn't work then I'd try to re-create what you are running on a custom iso and see if you can upgrade that successfully.
I can try the upgrade of a stock instances to see what happens. If not, I can just start at 30 and install and configure it as needed. Then snapshot it and make the necessary customization. Just like I did to get these 4 servers.
-
@wrx7m said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
@wirestyle22 said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
@wrx7m I would try to create a new instance with their image of 29 and upgrade to 30 to see if it works. If that doesn't work then I'd try to re-create what you are running on a custom iso and see if you can upgrade that successfully.
I can try the upgrade of a stock instances to see what happens. If not, I can just start at 30 and install and configure it as needed. Then snapshot it and make the necessary customization. Just like I did to get these 4 servers.
In the future I would definitely avoid using their images. I have run into some insanity and I wasn't sure if it was a mistake I made or the image. Ended up being the image.
-
@wirestyle22 I saw the complete opposite advice from others on this forum.
-
@wrx7m tag them and we can talk about it
-
Let's see if I can remember/find who it was.
-
@wirestyle22 said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
@wrx7m tag them and we can talk about it
Couldn't find where it was. Might have been a chat outside ML. I created this post to see what people say.
https://mangolassi.it/topic/19920/vultr-or-other-vps-provider-stock-os-instance-vs-custom-iso -
@wirestyle22 said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
@wrx7m I would try to create a new instance with their image of 29 and upgrade to 30 to see if it works. If that doesn't work then I'd try to re-create what you are running on a custom iso and see if you can upgrade that successfully.
Just deployed a new Fedora 29 instance on Vultr. Updated it and rebooted. Got the same error in the logs. I went back in some other instances and found that the error started appearing between the end of May and beginning of June. So, this has nothing to do with my customization of the OS. All I did was- Deploy, Login, Update, Reboot.
Now, I am going to deploy and reboot without updating.
-
Rebooting 29, without updating, remains error free.
-
Fedora 30-
Deploy, Login, Reboot - No error
Deploy, Login, Update, Reboot - ErrorTo me, this means, anyone using Vultr's Fedora 29 or 30 instances will have this error. Now, is it something that I need to be concerned about? I don't know.
-
Tried ruling out region/data center (maybe different hardware/hypervisor version). Tried Dallas Fedora 30 and got the same error after updating.
