Fedora 29 and 30 - EDAC skx: Can't Get tolm/tohm Error on Vultr
-
@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.
-
Used Fedora 30 netinstall iso and first boot had the error. So, Fedora doesn't like something there.
-
By default Fedora 30 Server uses ext4 for boot and xfs for /.
Change xfs to ext4 instead.
When using your uploaded ISO. -
@black3dynamite said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
By default Fedora 30 Server uses ext4 for boot and xfs for /.
Change xfs to ext4 instead.
When using the your uploaded ISO.Just to be clear - This error occurs during boot, but doesn't prevent the system from booting. I just don't know if it is something that will cause actual issues, or can be ignored.
-
I wonder if its the CPU model that you are assign to.
-
If you want there is a Vultr forum that you can post the error you are getting.
https://discuss.vultr.com/ -
@black3dynamite said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
I wonder if its the CPU model that you are assign to.
That is what I was thinking and why I tried a different region. I also updated my Vultr ticket to let them know. They may or may not even care. We shall see.
-
@black3dynamite said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
I wonder if its the CPU model that you are assign to.
This would be my guess. It looks to be related to the Intel i10nm Ice Lake(?) CPUs.
-
@dafyre said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
@black3dynamite said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
I wonder if its the CPU model that you are assign to.
This would be my guess. It looks to be related to the Intel i10nm Ice Lake(?) CPUs.
Yeah, the few Google results I found mentioned a CPU, although I thought I saw skylake.
-
Vultr replied -
"Hello,
The software one your VPS is outside of our scope of support.
Thank you."
I replied -
"I understand. Just thought your guys might want to figure out why your instances can't handle fully-patched versions of Fedora." -
@wrx7m said in Fedora 29 and 30 - EDAC skx: Can't Get tolm/tohm Error on Vultr:
@dafyre said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
@black3dynamite said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):
I wonder if its the CPU model that you are assign to.
This would be my guess. It looks to be related to the Intel i10nm Ice Lake(?) CPUs.
Yeah, the few Google results I found mentioned a CPU, although I thought I saw skylake.
What Vultr "level" is the VM?
-
@wirestyle22 said in Fedora 29 and 30 - EDAC skx: Can't Get tolm/tohm Error on Vultr:
@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.
What insanity was that? If their image is bad, they have support for that. If you don't use it, you are left on your own. I would not advise avoiding their images.
-
@wrx7m said in Fedora 29 and 30 - EDAC skx: Can't Get tolm/tohm Error on Vultr:
I replied -
"I understand. Just thought your guys might want to figure out why your instances can't handle fully-patched versions of Fedora."This isn't quite stated properly. The issue is that Fedora cannot properly handle the Vultr instance, not the other way around. Vultr is handling Fedora 30 just fine.
It is Fedora to whom this should be reported, it is in their court to fix, not Vultr's.
