smb drives can't write after upgrade to 18.04
I have a home NAS accessed via smb share.
I used ubuntu 16.04 before and everythings fine. After I changed to 18.04, (not upgrading but erase-and-installing a new system, with the /home mounted at a different drive so not changed), It seems fine until I found all the folders in the NAS can only be read, any write operation will give an error.
I installed Xubuntu 18.04 first, when I tried to create a new folder in a NAS folder, the error message is :
Fail to create directory "New Folder".
Function not implemented.
Do you want to skip it?
I tried Ubuntu 18.04 and get the same. And if I re-install the system with 16.04, the problem is gone.
I searched internet but couldn't find the answer. I found 16.04 and 18.04 have different cifs module versions, 16.04's cifs.ko is V2.08, while in 18.04 it's V2.10, is this the cause ? how to fix it?
p.s.:
If I mount the NAS folder by command line using:
sudo mount.cifs -o user=username,pass=mypwd //192.168.1.254/Documents /mnt
it can mount correctly, buy when I try to create a new file or folder in /mnt
, I got this error:
mn$ mkdir sjk
mkdir: cannot create directory ‘sjk’: Operation not supported
or
mnt>$ touch test
touch: cannot touch 'test': Operation not supported
Can anybody help with it?
18.04 mount samba
asked Jan 1 at 11:56
Jian JiaoJian Jiao
1
add a comment |
I have a home NAS accessed via smb share.
I used ubuntu 16.04 before and everythings fine. After I changed to 18.04, (not upgrading but erase-and-installing a new system, with the /home mounted at a different drive so not changed), It seems fine until I found all the folders in the NAS can only be read, any write operation will give an error.
I installed Xubuntu 18.04 first, when I tried to create a new folder in a NAS folder, the error message is :
Fail to create directory "New Folder".
Function not implemented.
Do you want to skip it?
I tried Ubuntu 18.04 and get the same. And if I re-install the system with 16.04, the problem is gone.
I searched internet but couldn't find the answer. I found 16.04 and 18.04 have different cifs module versions, 16.04's cifs.ko is V2.08, while in 18.04 it's V2.10, is this the cause ? how to fix it?
p.s.:
If I mount the NAS folder by command line using:
sudo mount.cifs -o user=username,pass=mypwd //192.168.1.254/Documents /mnt
it can mount correctly, buy when I try to create a new file or folder in /mnt
, I got this error:
mn$ mkdir sjk
mkdir: cannot create directory ‘sjk’: Operation not supported
or
mnt>$ touch test
touch: cannot touch 'test': Operation not supported
Can anybody help with it?
18.04 mount samba
asked Jan 1 at 11:56
Jian JiaoJian Jiao
1
1
Welcome to Ask Ubuntu. At Ubuntu 17.10 I found I needed to add a,vers=1.0to my cifs/samba parameters, so I'd try that. I primarily rely on NFS, using NFS devices only for backup so haven't paid much attention, but I have a number of parameters on mine you don't have "sec=ntlm,iocharset=utf8,vers=1.0,dir_mode=0777,file_mode=0777" but I'd suspect the version was what you are missing (version bump made to avert WannaCry on windows clients)
– guiverc
Jan 1 at 12:29
Thanks vuiverc, I've tried to use the vers=xxx methods but seems not helping. As it will be back to normal if downgraded to 16.04, I reckon it would be a bug in 18.04?
– Jian Jiao
Jan 2 at 3:53
I doubt a bug in 18.04, lots of people would have had it, and it would have been reported (bugs aren't bugs until they have been reported [& confirmed] on launchpad.net for Ubuntu, and I can't find any). Did you try the sec=ntlm too? I added the other lines in from my NAS lines so you could use them to try (as stated; I don't rely on samba but needed to add that on mymountsome time back (I forget which Ubuntu version but it was long ago) for it to work for my devices.
– guiverc
Jan 2 at 4:08
add a comment |
I have a home NAS accessed via smb share.
I used ubuntu 16.04 before and everythings fine. After I changed to 18.04, (not upgrading but erase-and-installing a new system, with the /home mounted at a different drive so not changed), It seems fine until I found all the folders in the NAS can only be read, any write operation will give an error.
I installed Xubuntu 18.04 first, when I tried to create a new folder in a NAS folder, the error message is :
Fail to create directory "New Folder".
Function not implemented.
Do you want to skip it?
I tried Ubuntu 18.04 and get the same. And if I re-install the system with 16.04, the problem is gone.
I searched internet but couldn't find the answer. I found 16.04 and 18.04 have different cifs module versions, 16.04's cifs.ko is V2.08, while in 18.04 it's V2.10, is this the cause ? how to fix it?
p.s.:
If I mount the NAS folder by command line using:
sudo mount.cifs -o user=username,pass=mypwd //192.168.1.254/Documents /mnt
it can mount correctly, buy when I try to create a new file or folder in /mnt
, I got this error:
mn$ mkdir sjk
mkdir: cannot create directory ‘sjk’: Operation not supported
or
mnt>$ touch test
touch: cannot touch 'test': Operation not supported
Can anybody help with it?
18.04 mount samba
asked Jan 1 at 11:56
Jian JiaoJian Jiao
1
I have a home NAS accessed via smb share.
I used ubuntu 16.04 before and everythings fine. After I changed to 18.04, (not upgrading but erase-and-installing a new system, with the /home mounted at a different drive so not changed), It seems fine until I found all the folders in the NAS can only be read, any write operation will give an error.
I installed Xubuntu 18.04 first, when I tried to create a new folder in a NAS folder, the error message is :
Fail to create directory "New Folder".
Function not implemented.
Do you want to skip it?
I tried Ubuntu 18.04 and get the same. And if I re-install the system with 16.04, the problem is gone.
I searched internet but couldn't find the answer. I found 16.04 and 18.04 have different cifs module versions, 16.04's cifs.ko is V2.08, while in 18.04 it's V2.10, is this the cause ? how to fix it?
p.s.:
If I mount the NAS folder by command line using:
sudo mount.cifs -o user=username,pass=mypwd //192.168.1.254/Documents /mnt
it can mount correctly, buy when I try to create a new file or folder in /mnt
, I got this error:
mn$ mkdir sjk
mkdir: cannot create directory ‘sjk’: Operation not supported
or
mnt>$ touch test
touch: cannot touch 'test': Operation not supported
Can anybody help with it?
18.04 mount samba
18.04 mount samba
asked Jan 1 at 11:56
Jian JiaoJian Jiao
1
asked Jan 1 at 11:56
Jian JiaoJian Jiao
1
asked Jan 1 at 11:56
Jian JiaoJian Jiao
1
asked Jan 1 at 11:56
Jian JiaoJian Jiao
1
asked Jan 1 at 11:56
Jian JiaoJian Jiao
1
1
1
Welcome to Ask Ubuntu. At Ubuntu 17.10 I found I needed to add a,vers=1.0to my cifs/samba parameters, so I'd try that. I primarily rely on NFS, using NFS devices only for backup so haven't paid much attention, but I have a number of parameters on mine you don't have "sec=ntlm,iocharset=utf8,vers=1.0,dir_mode=0777,file_mode=0777" but I'd suspect the version was what you are missing (version bump made to avert WannaCry on windows clients)
– guiverc
Jan 1 at 12:29
Thanks vuiverc, I've tried to use the vers=xxx methods but seems not helping. As it will be back to normal if downgraded to 16.04, I reckon it would be a bug in 18.04?
– Jian Jiao
Jan 2 at 3:53
I doubt a bug in 18.04, lots of people would have had it, and it would have been reported (bugs aren't bugs until they have been reported [& confirmed] on launchpad.net for Ubuntu, and I can't find any). Did you try the sec=ntlm too? I added the other lines in from my NAS lines so you could use them to try (as stated; I don't rely on samba but needed to add that on mymountsome time back (I forget which Ubuntu version but it was long ago) for it to work for my devices.
– guiverc
Jan 2 at 4:08
add a comment |
1
Welcome to Ask Ubuntu. At Ubuntu 17.10 I found I needed to add a,vers=1.0to my cifs/samba parameters, so I'd try that. I primarily rely on NFS, using NFS devices only for backup so haven't paid much attention, but I have a number of parameters on mine you don't have "sec=ntlm,iocharset=utf8,vers=1.0,dir_mode=0777,file_mode=0777" but I'd suspect the version was what you are missing (version bump made to avert WannaCry on windows clients)
– guiverc
Jan 1 at 12:29
Thanks vuiverc, I've tried to use the vers=xxx methods but seems not helping. As it will be back to normal if downgraded to 16.04, I reckon it would be a bug in 18.04?
– Jian Jiao
Jan 2 at 3:53
I doubt a bug in 18.04, lots of people would have had it, and it would have been reported (bugs aren't bugs until they have been reported [& confirmed] on launchpad.net for Ubuntu, and I can't find any). Did you try the sec=ntlm too? I added the other lines in from my NAS lines so you could use them to try (as stated; I don't rely on samba but needed to add that on mymountsome time back (I forget which Ubuntu version but it was long ago) for it to work for my devices.
– guiverc
Jan 2 at 4:08
1
1
Welcome to Ask Ubuntu. At Ubuntu 17.10 I found I needed to add a
,vers=1.0 to my cifs/samba parameters, so I'd try that. I primarily rely on NFS, using NFS devices only for backup so haven't paid much attention, but I have a number of parameters on mine you don't have "sec=ntlm,iocharset=utf8,vers=1.0,dir_mode=0777,file_mode=0777" but I'd suspect the version was what you are missing (version bump made to avert WannaCry on windows clients)– guiverc
Jan 1 at 12:29
Welcome to Ask Ubuntu. At Ubuntu 17.10 I found I needed to add a
,vers=1.0 to my cifs/samba parameters, so I'd try that. I primarily rely on NFS, using NFS devices only for backup so haven't paid much attention, but I have a number of parameters on mine you don't have "sec=ntlm,iocharset=utf8,vers=1.0,dir_mode=0777,file_mode=0777" but I'd suspect the version was what you are missing (version bump made to avert WannaCry on windows clients)– guiverc
Jan 1 at 12:29
Thanks vuiverc, I've tried to use the vers=xxx methods but seems not helping. As it will be back to normal if downgraded to 16.04, I reckon it would be a bug in 18.04?
– Jian Jiao
Jan 2 at 3:53
Thanks vuiverc, I've tried to use the vers=xxx methods but seems not helping. As it will be back to normal if downgraded to 16.04, I reckon it would be a bug in 18.04?
– Jian Jiao
Jan 2 at 3:53
I doubt a bug in 18.04, lots of people would have had it, and it would have been reported (bugs aren't bugs until they have been reported [& confirmed] on launchpad.net for Ubuntu, and I can't find any). Did you try the sec=ntlm too? I added the other lines in from my NAS lines so you could use them to try (as stated; I don't rely on samba but needed to add that on my
mount some time back (I forget which Ubuntu version but it was long ago) for it to work for my devices.– guiverc
Jan 2 at 4:08
I doubt a bug in 18.04, lots of people would have had it, and it would have been reported (bugs aren't bugs until they have been reported [& confirmed] on launchpad.net for Ubuntu, and I can't find any). Did you try the sec=ntlm too? I added the other lines in from my NAS lines so you could use them to try (as stated; I don't rely on samba but needed to add that on my
mount some time back (I forget which Ubuntu version but it was long ago) for it to work for my devices.– guiverc
Jan 2 at 4:08
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%2f1105999%2fsmb-drives-cant-write-after-upgrade-to-18-04%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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1105999%2fsmb-drives-cant-write-after-upgrade-to-18-04%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
1
Welcome to Ask Ubuntu. At Ubuntu 17.10 I found I needed to add a
,vers=1.0to my cifs/samba parameters, so I'd try that. I primarily rely on NFS, using NFS devices only for backup so haven't paid much attention, but I have a number of parameters on mine you don't have "sec=ntlm,iocharset=utf8,vers=1.0,dir_mode=0777,file_mode=0777" but I'd suspect the version was what you are missing (version bump made to avert WannaCry on windows clients)– guiverc
Jan 1 at 12:29
Thanks vuiverc, I've tried to use the vers=xxx methods but seems not helping. As it will be back to normal if downgraded to 16.04, I reckon it would be a bug in 18.04?
– Jian Jiao
Jan 2 at 3:53
I doubt a bug in 18.04, lots of people would have had it, and it would have been reported (bugs aren't bugs until they have been reported [& confirmed] on launchpad.net for Ubuntu, and I can't find any). Did you try the sec=ntlm too? I added the other lines in from my NAS lines so you could use them to try (as stated; I don't rely on samba but needed to add that on my
mountsome time back (I forget which Ubuntu version but it was long ago) for it to work for my devices.– guiverc
Jan 2 at 4:08