network connection error
I recently had to upgrade my ubuntu text-only server from 16.04 to 18.04. It was a complete install from scratch due to disk failure. Although I can see my network shares in Windows Explorer it appears as if the connection is dropped and immediately restored. The messages in kern.log are:
ata8.00: failed command: WRITE FPDMA QUEUED
ata8.00: cmd 61/00:f0:20:65:f3/0a:00:07:00:00/40 tag 30 ncq dma 1310720 out
res 40/00:b8:f8:ec:f3/00:00:07:00:00/40 Emask 0x10 (ATA bus error)
ata8.00: status: { DRDY }
This message is repeated a few times and then the following appears:
ata8: hard resetting link
ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata8.00: configured for UDMA/33
ata8: EH complete
It appears as if the share is dropped and reconnected almost immediately and this happens only when a Windows machine is connected to the network. I've chased the problem in the forums and followed all advice but it seems this is an ongoing problem. The 16.04 server never had this issue but I have found posts from people with this problem running 16.04 servers. So I'd prefer to stick with 18.04.
So far I've disabled avahi, tried NFS and removed it, and played with samba with no luck. It seems the problem lies with samba because apache is not experiencing any disruptions. I have a number of browser apps installed on the server and none have indicated any connection drops.
Ideas anyone?
networking server samba
asked Feb 8 at 23:24
SamSam
162
add a comment |
I recently had to upgrade my ubuntu text-only server from 16.04 to 18.04. It was a complete install from scratch due to disk failure. Although I can see my network shares in Windows Explorer it appears as if the connection is dropped and immediately restored. The messages in kern.log are:
ata8.00: failed command: WRITE FPDMA QUEUED
ata8.00: cmd 61/00:f0:20:65:f3/0a:00:07:00:00/40 tag 30 ncq dma 1310720 out
res 40/00:b8:f8:ec:f3/00:00:07:00:00/40 Emask 0x10 (ATA bus error)
ata8.00: status: { DRDY }
This message is repeated a few times and then the following appears:
ata8: hard resetting link
ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata8.00: configured for UDMA/33
ata8: EH complete
It appears as if the share is dropped and reconnected almost immediately and this happens only when a Windows machine is connected to the network. I've chased the problem in the forums and followed all advice but it seems this is an ongoing problem. The 16.04 server never had this issue but I have found posts from people with this problem running 16.04 servers. So I'd prefer to stick with 18.04.
So far I've disabled avahi, tried NFS and removed it, and played with samba with no luck. It seems the problem lies with samba because apache is not experiencing any disruptions. I have a number of browser apps installed on the server and none have indicated any connection drops.
Ideas anyone?
networking server samba
asked Feb 8 at 23:24
SamSam
162
add a comment |
I recently had to upgrade my ubuntu text-only server from 16.04 to 18.04. It was a complete install from scratch due to disk failure. Although I can see my network shares in Windows Explorer it appears as if the connection is dropped and immediately restored. The messages in kern.log are:
ata8.00: failed command: WRITE FPDMA QUEUED
ata8.00: cmd 61/00:f0:20:65:f3/0a:00:07:00:00/40 tag 30 ncq dma 1310720 out
res 40/00:b8:f8:ec:f3/00:00:07:00:00/40 Emask 0x10 (ATA bus error)
ata8.00: status: { DRDY }
This message is repeated a few times and then the following appears:
ata8: hard resetting link
ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata8.00: configured for UDMA/33
ata8: EH complete
It appears as if the share is dropped and reconnected almost immediately and this happens only when a Windows machine is connected to the network. I've chased the problem in the forums and followed all advice but it seems this is an ongoing problem. The 16.04 server never had this issue but I have found posts from people with this problem running 16.04 servers. So I'd prefer to stick with 18.04.
So far I've disabled avahi, tried NFS and removed it, and played with samba with no luck. It seems the problem lies with samba because apache is not experiencing any disruptions. I have a number of browser apps installed on the server and none have indicated any connection drops.
Ideas anyone?
networking server samba
asked Feb 8 at 23:24
SamSam
162
I recently had to upgrade my ubuntu text-only server from 16.04 to 18.04. It was a complete install from scratch due to disk failure. Although I can see my network shares in Windows Explorer it appears as if the connection is dropped and immediately restored. The messages in kern.log are:
ata8.00: failed command: WRITE FPDMA QUEUED
ata8.00: cmd 61/00:f0:20:65:f3/0a:00:07:00:00/40 tag 30 ncq dma 1310720 out
res 40/00:b8:f8:ec:f3/00:00:07:00:00/40 Emask 0x10 (ATA bus error)
ata8.00: status: { DRDY }
This message is repeated a few times and then the following appears:
ata8: hard resetting link
ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata8.00: configured for UDMA/33
ata8: EH complete
It appears as if the share is dropped and reconnected almost immediately and this happens only when a Windows machine is connected to the network. I've chased the problem in the forums and followed all advice but it seems this is an ongoing problem. The 16.04 server never had this issue but I have found posts from people with this problem running 16.04 servers. So I'd prefer to stick with 18.04.
So far I've disabled avahi, tried NFS and removed it, and played with samba with no luck. It seems the problem lies with samba because apache is not experiencing any disruptions. I have a number of browser apps installed on the server and none have indicated any connection drops.
Ideas anyone?
networking server samba
networking server samba
asked Feb 8 at 23:24
SamSam
162
asked Feb 8 at 23:24
SamSam
162
asked Feb 8 at 23:24
SamSam
162
asked Feb 8 at 23:24
SamSam
162
asked Feb 8 at 23:24
SamSam
162
162
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Events subsequent to my post pointed to another damaged disk and not samba. The network connectivity problem appears to have been corrected with a recent update and serendipity masked the disk defect. Fsck confirmed the damaged disk and a lengthy and uninterrupted process across the network confirmed that connectivity is no longer a problem. So far so good.
answered Feb 10 at 17:20
SamSam
162
add a comment |
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%2f1116803%2fnetwork-connection-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Events subsequent to my post pointed to another damaged disk and not samba. The network connectivity problem appears to have been corrected with a recent update and serendipity masked the disk defect. Fsck confirmed the damaged disk and a lengthy and uninterrupted process across the network confirmed that connectivity is no longer a problem. So far so good.
answered Feb 10 at 17:20
SamSam
162
add a comment |
Events subsequent to my post pointed to another damaged disk and not samba. The network connectivity problem appears to have been corrected with a recent update and serendipity masked the disk defect. Fsck confirmed the damaged disk and a lengthy and uninterrupted process across the network confirmed that connectivity is no longer a problem. So far so good.
answered Feb 10 at 17:20
SamSam
162
add a comment |
Events subsequent to my post pointed to another damaged disk and not samba. The network connectivity problem appears to have been corrected with a recent update and serendipity masked the disk defect. Fsck confirmed the damaged disk and a lengthy and uninterrupted process across the network confirmed that connectivity is no longer a problem. So far so good.
answered Feb 10 at 17:20
SamSam
162
Events subsequent to my post pointed to another damaged disk and not samba. The network connectivity problem appears to have been corrected with a recent update and serendipity masked the disk defect. Fsck confirmed the damaged disk and a lengthy and uninterrupted process across the network confirmed that connectivity is no longer a problem. So far so good.
answered Feb 10 at 17:20
SamSam
162
answered Feb 10 at 17:20
SamSam
162
answered Feb 10 at 17:20
SamSam
162
answered Feb 10 at 17:20
SamSam
162
162
add a comment |
add a comment |
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%2f1116803%2fnetwork-connection-error%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
