No working network after some errors on startup & a fsck
When I start the server, first I have to wait because of this:
A start job is running for Raise network interfaces
Right after showing Ubuntu 16.04.5 LTS [...], before even logged in, following errors occur:
ata3.00: exception Emask 0x0 SAct 0x180000a SErr 0x0 action 0x0
... some more ata erros
blk_update_request: I/O error, dev sda, sector 82075687
But I can still login in and do everything, except the network is not working. the cable is of course plugged in.
I tried some changes to /etc/resolv.conf which only 127.0.0.1 listed, but eg adding dns-nameserver 8.8.8.8 did not help.
The /etc/network/interfaces is:
auto lo
iface lo inet loopback
auto enp2s0
iface enp2s0 inet dhcp
The enp2s0 is not started considering the output of ifconfig. If I try ifup enp2s0 I am stuck in a Network is down loop ...
Actually, I am not sure if the network is the real problem. Before this, I had to do a fsck of my /var partition (/dev/sda5) & then reboot. I must do this three times before the OS was running normally again.
Any tips, what to do to solve this problem?
Some more info: I ran this server for about 2 years without a problem. The /var/www contains some websites running using a LAMP stack.
networking server dns
asked Feb 11 at 16:49
SmeavenSmeaven
11
add a comment |
When I start the server, first I have to wait because of this:
A start job is running for Raise network interfaces
Right after showing Ubuntu 16.04.5 LTS [...], before even logged in, following errors occur:
ata3.00: exception Emask 0x0 SAct 0x180000a SErr 0x0 action 0x0
... some more ata erros
blk_update_request: I/O error, dev sda, sector 82075687
But I can still login in and do everything, except the network is not working. the cable is of course plugged in.
I tried some changes to /etc/resolv.conf which only 127.0.0.1 listed, but eg adding dns-nameserver 8.8.8.8 did not help.
The /etc/network/interfaces is:
auto lo
iface lo inet loopback
auto enp2s0
iface enp2s0 inet dhcp
The enp2s0 is not started considering the output of ifconfig. If I try ifup enp2s0 I am stuck in a Network is down loop ...
Actually, I am not sure if the network is the real problem. Before this, I had to do a fsck of my /var partition (/dev/sda5) & then reboot. I must do this three times before the OS was running normally again.
Any tips, what to do to solve this problem?
Some more info: I ran this server for about 2 years without a problem. The /var/www contains some websites running using a LAMP stack.
networking server dns
asked Feb 11 at 16:49
SmeavenSmeaven
11
Did you run fsck on the rest of your disk as well?
– Charles Green
Feb 11 at 16:52
No, I did not, as there was a severe warning to so when the disk is still mounted. On the other main partition, the OS is running.
– Smeaven
Feb 12 at 15:38
This is true - to run fsck currently on the root partition, you need to first boot from a live USB. On the other hand, I was stuck in a boot loop until I did this once...
– Charles Green
Feb 12 at 15:42
I did fsck from a live USB. It says both partitions are clean. Booting from the usb I also got internet, so it cannot be a hardware problem on the connectors or cable.
– Smeaven
Feb 12 at 17:45
add a comment |
When I start the server, first I have to wait because of this:
A start job is running for Raise network interfaces
Right after showing Ubuntu 16.04.5 LTS [...], before even logged in, following errors occur:
ata3.00: exception Emask 0x0 SAct 0x180000a SErr 0x0 action 0x0
... some more ata erros
blk_update_request: I/O error, dev sda, sector 82075687
But I can still login in and do everything, except the network is not working. the cable is of course plugged in.
I tried some changes to /etc/resolv.conf which only 127.0.0.1 listed, but eg adding dns-nameserver 8.8.8.8 did not help.
The /etc/network/interfaces is:
auto lo
iface lo inet loopback
auto enp2s0
iface enp2s0 inet dhcp
The enp2s0 is not started considering the output of ifconfig. If I try ifup enp2s0 I am stuck in a Network is down loop ...
Actually, I am not sure if the network is the real problem. Before this, I had to do a fsck of my /var partition (/dev/sda5) & then reboot. I must do this three times before the OS was running normally again.
Any tips, what to do to solve this problem?
Some more info: I ran this server for about 2 years without a problem. The /var/www contains some websites running using a LAMP stack.
networking server dns
asked Feb 11 at 16:49
SmeavenSmeaven
11
When I start the server, first I have to wait because of this:
A start job is running for Raise network interfaces
Right after showing Ubuntu 16.04.5 LTS [...], before even logged in, following errors occur:
ata3.00: exception Emask 0x0 SAct 0x180000a SErr 0x0 action 0x0
... some more ata erros
blk_update_request: I/O error, dev sda, sector 82075687
But I can still login in and do everything, except the network is not working. the cable is of course plugged in.
I tried some changes to /etc/resolv.conf which only 127.0.0.1 listed, but eg adding dns-nameserver 8.8.8.8 did not help.
The /etc/network/interfaces is:
auto lo
iface lo inet loopback
auto enp2s0
iface enp2s0 inet dhcp
The enp2s0 is not started considering the output of ifconfig. If I try ifup enp2s0 I am stuck in a Network is down loop ...
Actually, I am not sure if the network is the real problem. Before this, I had to do a fsck of my /var partition (/dev/sda5) & then reboot. I must do this three times before the OS was running normally again.
Any tips, what to do to solve this problem?
Some more info: I ran this server for about 2 years without a problem. The /var/www contains some websites running using a LAMP stack.
networking server dns
networking server dns
asked Feb 11 at 16:49
SmeavenSmeaven
11
asked Feb 11 at 16:49
SmeavenSmeaven
11
edited Feb 12 at 15:46
Smeaven
asked Feb 11 at 16:49
SmeavenSmeaven
11
asked Feb 11 at 16:49
SmeavenSmeaven
11
asked Feb 11 at 16:49
SmeavenSmeaven
11
11
Did you run fsck on the rest of your disk as well?
– Charles Green
Feb 11 at 16:52
No, I did not, as there was a severe warning to so when the disk is still mounted. On the other main partition, the OS is running.
– Smeaven
Feb 12 at 15:38
This is true - to run fsck currently on the root partition, you need to first boot from a live USB. On the other hand, I was stuck in a boot loop until I did this once...
– Charles Green
Feb 12 at 15:42
I did fsck from a live USB. It says both partitions are clean. Booting from the usb I also got internet, so it cannot be a hardware problem on the connectors or cable.
– Smeaven
Feb 12 at 17:45
add a comment |
Did you run fsck on the rest of your disk as well?
– Charles Green
Feb 11 at 16:52
No, I did not, as there was a severe warning to so when the disk is still mounted. On the other main partition, the OS is running.
– Smeaven
Feb 12 at 15:38
This is true - to run fsck currently on the root partition, you need to first boot from a live USB. On the other hand, I was stuck in a boot loop until I did this once...
– Charles Green
Feb 12 at 15:42
I did fsck from a live USB. It says both partitions are clean. Booting from the usb I also got internet, so it cannot be a hardware problem on the connectors or cable.
– Smeaven
Feb 12 at 17:45
Did you run fsck on the rest of your disk as well?
– Charles Green
Feb 11 at 16:52
Did you run fsck on the rest of your disk as well?
– Charles Green
Feb 11 at 16:52
No, I did not, as there was a severe warning to so when the disk is still mounted. On the other main partition, the OS is running.
– Smeaven
Feb 12 at 15:38
No, I did not, as there was a severe warning to so when the disk is still mounted. On the other main partition, the OS is running.
– Smeaven
Feb 12 at 15:38
This is true - to run fsck currently on the root partition, you need to first boot from a live USB. On the other hand, I was stuck in a boot loop until I did this once...
– Charles Green
Feb 12 at 15:42
This is true - to run fsck currently on the root partition, you need to first boot from a live USB. On the other hand, I was stuck in a boot loop until I did this once...
– Charles Green
Feb 12 at 15:42
I did fsck from a live USB. It says both partitions are clean. Booting from the usb I also got internet, so it cannot be a hardware problem on the connectors or cable.
– Smeaven
Feb 12 at 17:45
I did fsck from a live USB. It says both partitions are clean. Booting from the usb I also got internet, so it cannot be a hardware problem on the connectors or cable.
– Smeaven
Feb 12 at 17:45
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117424%2fno-working-network-after-some-errors-on-startup-a-fsck%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117424%2fno-working-network-after-some-errors-on-startup-a-fsck%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did you run fsck on the rest of your disk as well?
– Charles Green
Feb 11 at 16:52
No, I did not, as there was a severe warning to so when the disk is still mounted. On the other main partition, the OS is running.
– Smeaven
Feb 12 at 15:38
This is true - to run fsck currently on the root partition, you need to first boot from a live USB. On the other hand, I was stuck in a boot loop until I did this once...
– Charles Green
Feb 12 at 15:42
I did fsck from a live USB. It says both partitions are clean. Booting from the usb I also got internet, so it cannot be a hardware problem on the connectors or cable.
– Smeaven
Feb 12 at 17:45