Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BareMetal server unusable after installing linux header #380

Open
bbichero opened this issue Aug 26, 2018 · 3 comments
Open

BareMetal server unusable after installing linux header #380

bbichero opened this issue Aug 26, 2018 · 3 comments

Comments

@bbichero
Copy link

bbichero commented Aug 26, 2018

Hi,
Today I wanted to install wireguard on others server than Basic Start servers.
So after following Kernel-tool guide to install new kernel headers, I installed wireguard with the official installation steps .
When installation was finished I restarted my BareMetal server, and after that, impossible to connect to it.
On the serial console I get all thoses messages :
screenshot1
screenshot2
I restart the steps severals times, and follow multiple tutorials but after each reboot I get the same errors.

I'm on a debian stretch image with boot script : x86_64 mainline 4.9.93 rev1

@zar3bski
Copy link

Looks like they are using custom Debians to me. I am struggling with a similar mess (unmatching headers). How did it end?

@bbichero
Copy link
Author

It's not a custom debian.
it never end :( I abandon the idea to install custom module on basic start servers.
It work perfectly on the start server. So wait for a fix or an answer from scaleway is the best solution.

@zar3bski
Copy link

I posted a ticket about it. Keep in touch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants