CIFS mount from fstab not working
Multi tool use
This method used to work with RHEL 5, and 6, so I used to just add this Line in /etc/fstab:
\192.168.1.50V$ /mnt/N cifs user,uid=500,rw,suid,username=Administrator,password=password 0 0
But now this is not working on RHEL 7.6
I found this link
CentOS / RHEL 7: How to follow the mount order in /etc/fstab. After following I copied /run/systemd/generator/mnt-N.mount file to /etc/systemd/system/mnt-N.mount. Rebooted but it's still not working.
Contents of mnt-N.mount:
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=remote-fs.target
[Mount]
What=192.168.1.205V$
Where=/mnt/V
Type=cifs
Options=user,uid=500,rw,suid,username=Administrator,password=PSCr0cks
linux mount redhat-enterprise-linux fstab cifs
edited Dec 24 '18 at 21:57
Kamil Maciorowski
24.8k155277
asked Dec 24 '18 at 21:34
SeanCltSeanClt
1,66231734
add a comment |
This method used to work with RHEL 5, and 6, so I used to just add this Line in /etc/fstab:
\192.168.1.50V$ /mnt/N cifs user,uid=500,rw,suid,username=Administrator,password=password 0 0
But now this is not working on RHEL 7.6
I found this link
CentOS / RHEL 7: How to follow the mount order in /etc/fstab. After following I copied /run/systemd/generator/mnt-N.mount file to /etc/systemd/system/mnt-N.mount. Rebooted but it's still not working.
Contents of mnt-N.mount:
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=remote-fs.target
[Mount]
What=192.168.1.205V$
Where=/mnt/V
Type=cifs
Options=user,uid=500,rw,suid,username=Administrator,password=PSCr0cks
linux mount redhat-enterprise-linux fstab cifs
edited Dec 24 '18 at 21:57
Kamil Maciorowski
24.8k155277
asked Dec 24 '18 at 21:34
SeanCltSeanClt
1,66231734
that worked, I feel stupid, can you please put that as answer
– SeanClt
Dec 24 '18 at 21:49
add a comment |
This method used to work with RHEL 5, and 6, so I used to just add this Line in /etc/fstab:
\192.168.1.50V$ /mnt/N cifs user,uid=500,rw,suid,username=Administrator,password=password 0 0
But now this is not working on RHEL 7.6
I found this link
CentOS / RHEL 7: How to follow the mount order in /etc/fstab. After following I copied /run/systemd/generator/mnt-N.mount file to /etc/systemd/system/mnt-N.mount. Rebooted but it's still not working.
Contents of mnt-N.mount:
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=remote-fs.target
[Mount]
What=192.168.1.205V$
Where=/mnt/V
Type=cifs
Options=user,uid=500,rw,suid,username=Administrator,password=PSCr0cks
linux mount redhat-enterprise-linux fstab cifs
edited Dec 24 '18 at 21:57
Kamil Maciorowski
24.8k155277
asked Dec 24 '18 at 21:34
SeanCltSeanClt
1,66231734
This method used to work with RHEL 5, and 6, so I used to just add this Line in /etc/fstab:
\192.168.1.50V$ /mnt/N cifs user,uid=500,rw,suid,username=Administrator,password=password 0 0
But now this is not working on RHEL 7.6
I found this link
CentOS / RHEL 7: How to follow the mount order in /etc/fstab. After following I copied /run/systemd/generator/mnt-N.mount file to /etc/systemd/system/mnt-N.mount. Rebooted but it's still not working.
Contents of mnt-N.mount:
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=remote-fs.target
[Mount]
What=192.168.1.205V$
Where=/mnt/V
Type=cifs
Options=user,uid=500,rw,suid,username=Administrator,password=PSCr0cks
linux mount redhat-enterprise-linux fstab cifs
linux mount redhat-enterprise-linux fstab cifs
edited Dec 24 '18 at 21:57
Kamil Maciorowski
24.8k155277
asked Dec 24 '18 at 21:34
SeanCltSeanClt
1,66231734
edited Dec 24 '18 at 21:57
Kamil Maciorowski
24.8k155277
asked Dec 24 '18 at 21:34
SeanCltSeanClt
1,66231734
edited Dec 24 '18 at 21:57
Kamil Maciorowski
24.8k155277
edited Dec 24 '18 at 21:57
Kamil Maciorowski
24.8k155277
edited Dec 24 '18 at 21:57
Kamil Maciorowski
24.8k155277
24.8k155277
asked Dec 24 '18 at 21:34
SeanCltSeanClt
1,66231734
asked Dec 24 '18 at 21:34
SeanCltSeanClt
1,66231734
asked Dec 24 '18 at 21:34
SeanCltSeanClt
1,66231734
1,66231734
that worked, I feel stupid, can you please put that as answer
– SeanClt
Dec 24 '18 at 21:49
add a comment |
that worked, I feel stupid, can you please put that as answer
– SeanClt
Dec 24 '18 at 21:49
that worked, I feel stupid, can you please put that as answer
– SeanClt
Dec 24 '18 at 21:49
that worked, I feel stupid, can you please put that as answer
– SeanClt
Dec 24 '18 at 21:49
add a comment |
1 Answer
1
active
oldest
votes
Your \192.168.1.50V$ from fstab becomes 192.168.1.205V$ later. Compare fstab-generator interprets backslashes in CIFS mounts.
You may try \\192.168.1.50V$ and it will probably generate a proper mount unit. However the linked discussion (from 2015) states you may experience problems with mount then. I don't know if the behavior of the two tools has finally been made uniform.
It's better to avoid backslashes at all and use forward slashes for CIFS mounts:
//192.168.1.50/V$
answered Dec 24 '18 at 21:52
Kamil MaciorowskiKamil Maciorowski
24.8k155277
Update I tried //192.168.1.50/V$ in the fstab and I didn't even had to copy /run/systemd/generator/mnt-N.mount file to /etc/systemd/system/mnt-N.mount so apparently all I needed was //192.168.1.50/V$
– SeanClt
Dec 24 '18 at 22:00
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1387461%2fcifs-mount-from-fstab-not-working%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
Your \192.168.1.50V$ from fstab becomes 192.168.1.205V$ later. Compare fstab-generator interprets backslashes in CIFS mounts.
You may try \\192.168.1.50V$ and it will probably generate a proper mount unit. However the linked discussion (from 2015) states you may experience problems with mount then. I don't know if the behavior of the two tools has finally been made uniform.
It's better to avoid backslashes at all and use forward slashes for CIFS mounts:
//192.168.1.50/V$
answered Dec 24 '18 at 21:52
Kamil MaciorowskiKamil Maciorowski
24.8k155277
Update I tried //192.168.1.50/V$ in the fstab and I didn't even had to copy /run/systemd/generator/mnt-N.mount file to /etc/systemd/system/mnt-N.mount so apparently all I needed was //192.168.1.50/V$
– SeanClt
Dec 24 '18 at 22:00
add a comment |
Your \192.168.1.50V$ from fstab becomes 192.168.1.205V$ later. Compare fstab-generator interprets backslashes in CIFS mounts.
You may try \\192.168.1.50V$ and it will probably generate a proper mount unit. However the linked discussion (from 2015) states you may experience problems with mount then. I don't know if the behavior of the two tools has finally been made uniform.
It's better to avoid backslashes at all and use forward slashes for CIFS mounts:
//192.168.1.50/V$
answered Dec 24 '18 at 21:52
Kamil MaciorowskiKamil Maciorowski
24.8k155277
Update I tried //192.168.1.50/V$ in the fstab and I didn't even had to copy /run/systemd/generator/mnt-N.mount file to /etc/systemd/system/mnt-N.mount so apparently all I needed was //192.168.1.50/V$
– SeanClt
Dec 24 '18 at 22:00
add a comment |
Your \192.168.1.50V$ from fstab becomes 192.168.1.205V$ later. Compare fstab-generator interprets backslashes in CIFS mounts.
You may try \\192.168.1.50V$ and it will probably generate a proper mount unit. However the linked discussion (from 2015) states you may experience problems with mount then. I don't know if the behavior of the two tools has finally been made uniform.
It's better to avoid backslashes at all and use forward slashes for CIFS mounts:
//192.168.1.50/V$
answered Dec 24 '18 at 21:52
Kamil MaciorowskiKamil Maciorowski
24.8k155277
Your \192.168.1.50V$ from fstab becomes 192.168.1.205V$ later. Compare fstab-generator interprets backslashes in CIFS mounts.
You may try \\192.168.1.50V$ and it will probably generate a proper mount unit. However the linked discussion (from 2015) states you may experience problems with mount then. I don't know if the behavior of the two tools has finally been made uniform.
It's better to avoid backslashes at all and use forward slashes for CIFS mounts:
//192.168.1.50/V$
answered Dec 24 '18 at 21:52
Kamil MaciorowskiKamil Maciorowski
24.8k155277
answered Dec 24 '18 at 21:52
Kamil MaciorowskiKamil Maciorowski
24.8k155277
answered Dec 24 '18 at 21:52
Kamil MaciorowskiKamil Maciorowski
24.8k155277
answered Dec 24 '18 at 21:52
Kamil MaciorowskiKamil Maciorowski
24.8k155277
24.8k155277
Update I tried //192.168.1.50/V$ in the fstab and I didn't even had to copy /run/systemd/generator/mnt-N.mount file to /etc/systemd/system/mnt-N.mount so apparently all I needed was //192.168.1.50/V$
– SeanClt
Dec 24 '18 at 22:00
add a comment |
Update I tried //192.168.1.50/V$ in the fstab and I didn't even had to copy /run/systemd/generator/mnt-N.mount file to /etc/systemd/system/mnt-N.mount so apparently all I needed was //192.168.1.50/V$
– SeanClt
Dec 24 '18 at 22:00
Update I tried //192.168.1.50/V$ in the fstab and I didn't even had to copy /run/systemd/generator/mnt-N.mount file to /etc/systemd/system/mnt-N.mount so apparently all I needed was //192.168.1.50/V$
– SeanClt
Dec 24 '18 at 22:00
Update I tried //192.168.1.50/V$ in the fstab and I didn't even had to copy /run/systemd/generator/mnt-N.mount file to /etc/systemd/system/mnt-N.mount so apparently all I needed was //192.168.1.50/V$
– SeanClt
Dec 24 '18 at 22:00
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1387461%2fcifs-mount-from-fstab-not-working%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
wx,5NAOQ,2ta WZa sPmVxVx92j4 Xgin1gwxPdC 3JIDKWyCqPrgVm7cdkF
that worked, I feel stupid, can you please put that as answer
– SeanClt
Dec 24 '18 at 21:49