Unrecognized mount option “uid=33” or missing value
Clash Royale CLAN TAG#URR8PPP
I'm trying to mount a partition with -o option, however I get this error
root@blackbox:~# mount /dev/sda1 /media/ownclouddrive -o uid=33,gid=33
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
[ 365.432693] EXT4-fs (sda1): Unrecognized mount option "uid=33" or missing value
If I checl my /etc/passwd I can see the user there
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
Any idea why?
Thanks
mount
asked Jul 25 '16 at 13:24
FederiFederi
46321332
|
show 1 more comment
I'm trying to mount a partition with -o option, however I get this error
root@blackbox:~# mount /dev/sda1 /media/ownclouddrive -o uid=33,gid=33
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
[ 365.432693] EXT4-fs (sda1): Unrecognized mount option "uid=33" or missing value
If I checl my /etc/passwd I can see the user there
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
Any idea why?
Thanks
mount
asked Jul 25 '16 at 13:24
FederiFederi
46321332
2
uidandgidare options for filesystems that don’t support permissions, e. g. vfat. They’d make little sense for ext4.
– phg
Jul 25 '16 at 13:27
And to override ownership for all files on a file-system (without actually modifying the file metadata stored on the filesystem), you could look atbindfs
– Stéphane Chazelas
Jul 25 '16 at 13:30
So, the suggestion is to change the partition in NTFS?
– Federi
Jul 25 '16 at 13:39
1
A first suggestion would be to remove theuid=33,gid=33options to themountcommand. If that's not acceptable please edit your question to explain what you're trying to achieve.
– roaima
Jul 25 '16 at 13:47
1
@Federi In addition to what @roaima recommends, if you need all33:33permissions on that filesystem, then justchown -Rits contents once after mounting.
– phg
Jul 25 '16 at 14:01
|
show 1 more comment
I'm trying to mount a partition with -o option, however I get this error
root@blackbox:~# mount /dev/sda1 /media/ownclouddrive -o uid=33,gid=33
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
[ 365.432693] EXT4-fs (sda1): Unrecognized mount option "uid=33" or missing value
If I checl my /etc/passwd I can see the user there
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
Any idea why?
Thanks
mount
asked Jul 25 '16 at 13:24
FederiFederi
46321332
I'm trying to mount a partition with -o option, however I get this error
root@blackbox:~# mount /dev/sda1 /media/ownclouddrive -o uid=33,gid=33
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
[ 365.432693] EXT4-fs (sda1): Unrecognized mount option "uid=33" or missing value
If I checl my /etc/passwd I can see the user there
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
Any idea why?
Thanks
mount
mount
asked Jul 25 '16 at 13:24
FederiFederi
46321332
asked Jul 25 '16 at 13:24
FederiFederi
46321332
asked Jul 25 '16 at 13:24
FederiFederi
46321332
asked Jul 25 '16 at 13:24
FederiFederi
46321332
asked Jul 25 '16 at 13:24
FederiFederi
46321332
46321332
2
uidandgidare options for filesystems that don’t support permissions, e. g. vfat. They’d make little sense for ext4.
– phg
Jul 25 '16 at 13:27
And to override ownership for all files on a file-system (without actually modifying the file metadata stored on the filesystem), you could look atbindfs
– Stéphane Chazelas
Jul 25 '16 at 13:30
So, the suggestion is to change the partition in NTFS?
– Federi
Jul 25 '16 at 13:39
1
A first suggestion would be to remove theuid=33,gid=33options to themountcommand. If that's not acceptable please edit your question to explain what you're trying to achieve.
– roaima
Jul 25 '16 at 13:47
1
@Federi In addition to what @roaima recommends, if you need all33:33permissions on that filesystem, then justchown -Rits contents once after mounting.
– phg
Jul 25 '16 at 14:01
|
show 1 more comment
2
uidandgidare options for filesystems that don’t support permissions, e. g. vfat. They’d make little sense for ext4.
– phg
Jul 25 '16 at 13:27
And to override ownership for all files on a file-system (without actually modifying the file metadata stored on the filesystem), you could look atbindfs
– Stéphane Chazelas
Jul 25 '16 at 13:30
So, the suggestion is to change the partition in NTFS?
– Federi
Jul 25 '16 at 13:39
1
A first suggestion would be to remove theuid=33,gid=33options to themountcommand. If that's not acceptable please edit your question to explain what you're trying to achieve.
– roaima
Jul 25 '16 at 13:47
1
@Federi In addition to what @roaima recommends, if you need all33:33permissions on that filesystem, then justchown -Rits contents once after mounting.
– phg
Jul 25 '16 at 14:01
2
2
uid and gid are options for filesystems that don’t support permissions, e. g. vfat. They’d make little sense for ext4.– phg
Jul 25 '16 at 13:27
uid and gid are options for filesystems that don’t support permissions, e. g. vfat. They’d make little sense for ext4.– phg
Jul 25 '16 at 13:27
And to override ownership for all files on a file-system (without actually modifying the file metadata stored on the filesystem), you could look at
bindfs– Stéphane Chazelas
Jul 25 '16 at 13:30
And to override ownership for all files on a file-system (without actually modifying the file metadata stored on the filesystem), you could look at
bindfs– Stéphane Chazelas
Jul 25 '16 at 13:30
So, the suggestion is to change the partition in NTFS?
– Federi
Jul 25 '16 at 13:39
So, the suggestion is to change the partition in NTFS?
– Federi
Jul 25 '16 at 13:39
1
1
A first suggestion would be to remove the
uid=33,gid=33 options to the mount command. If that's not acceptable please edit your question to explain what you're trying to achieve.– roaima
Jul 25 '16 at 13:47
A first suggestion would be to remove the
uid=33,gid=33 options to the mount command. If that's not acceptable please edit your question to explain what you're trying to achieve.– roaima
Jul 25 '16 at 13:47
1
1
@Federi In addition to what @roaima recommends, if you need all
33:33 permissions on that filesystem, then just chown -R its contents once after mounting.– phg
Jul 25 '16 at 14:01
@Federi In addition to what @roaima recommends, if you need all
33:33 permissions on that filesystem, then just chown -R its contents once after mounting.– phg
Jul 25 '16 at 14:01
|
show 1 more comment
2 Answers
2
active
oldest
votes
You are getting that error message because you specify mount
options that don’t apply to the filesystem on the device.
The mount options uid= and gid= are not valid for all
available filesystems. The ones that support proper permissions
usually don’t accept them, as is the case for that ext4 device
you’re attempting to mount.
For filesystems with limited functionality like VFAT, the optionsuid and gid allow mapping the ownership of the entire
contents of a mounted filesystem to a single local user. Similar
options exist for other properties like the umask.
Note that this is not the proper way to grant permissions to the
contents, but rather a workaround to integrate certain FS into a
unixoid environment. On an ext4 partition like the one you’re
attempting to mount, just change the ownership directly:
mount -t ext4 /dev/sda1 /media/ownclouddrive
chown -R 33:33 /media/ownclouddrive/*
answered Jul 25 '16 at 14:57
phgphg
711518
1
Yes! Thanks for this answer. It seems obvious, in hindsight, that changing the ownership directly is the right approach, but... I just caught myself trying to do the exact same thing as the OP, i.e., manipulating permissions for an EXT4-formatted partition via theuid=option in/etc/fstab. Glad my Google search forUnrecognized mount option "uid=led me to this answer!
– evadeflow
Dec 17 '18 at 18:26
add a comment |
In addition to phg, you can use option user i.e.
mount /dev/sda1 /media/ownclouddrive -o user=www-data,rw
answered Mar 1 at 12:30
antonanton
1
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f298141%2funrecognized-mount-option-uid-33-or-missing-value%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You are getting that error message because you specify mount
options that don’t apply to the filesystem on the device.
The mount options uid= and gid= are not valid for all
available filesystems. The ones that support proper permissions
usually don’t accept them, as is the case for that ext4 device
you’re attempting to mount.
For filesystems with limited functionality like VFAT, the optionsuid and gid allow mapping the ownership of the entire
contents of a mounted filesystem to a single local user. Similar
options exist for other properties like the umask.
Note that this is not the proper way to grant permissions to the
contents, but rather a workaround to integrate certain FS into a
unixoid environment. On an ext4 partition like the one you’re
attempting to mount, just change the ownership directly:
mount -t ext4 /dev/sda1 /media/ownclouddrive
chown -R 33:33 /media/ownclouddrive/*
answered Jul 25 '16 at 14:57
phgphg
711518
1
Yes! Thanks for this answer. It seems obvious, in hindsight, that changing the ownership directly is the right approach, but... I just caught myself trying to do the exact same thing as the OP, i.e., manipulating permissions for an EXT4-formatted partition via theuid=option in/etc/fstab. Glad my Google search forUnrecognized mount option "uid=led me to this answer!
– evadeflow
Dec 17 '18 at 18:26
add a comment |
You are getting that error message because you specify mount
options that don’t apply to the filesystem on the device.
The mount options uid= and gid= are not valid for all
available filesystems. The ones that support proper permissions
usually don’t accept them, as is the case for that ext4 device
you’re attempting to mount.
For filesystems with limited functionality like VFAT, the optionsuid and gid allow mapping the ownership of the entire
contents of a mounted filesystem to a single local user. Similar
options exist for other properties like the umask.
Note that this is not the proper way to grant permissions to the
contents, but rather a workaround to integrate certain FS into a
unixoid environment. On an ext4 partition like the one you’re
attempting to mount, just change the ownership directly:
mount -t ext4 /dev/sda1 /media/ownclouddrive
chown -R 33:33 /media/ownclouddrive/*
answered Jul 25 '16 at 14:57
phgphg
711518
1
Yes! Thanks for this answer. It seems obvious, in hindsight, that changing the ownership directly is the right approach, but... I just caught myself trying to do the exact same thing as the OP, i.e., manipulating permissions for an EXT4-formatted partition via theuid=option in/etc/fstab. Glad my Google search forUnrecognized mount option "uid=led me to this answer!
– evadeflow
Dec 17 '18 at 18:26
add a comment |
You are getting that error message because you specify mount
options that don’t apply to the filesystem on the device.
The mount options uid= and gid= are not valid for all
available filesystems. The ones that support proper permissions
usually don’t accept them, as is the case for that ext4 device
you’re attempting to mount.
For filesystems with limited functionality like VFAT, the optionsuid and gid allow mapping the ownership of the entire
contents of a mounted filesystem to a single local user. Similar
options exist for other properties like the umask.
Note that this is not the proper way to grant permissions to the
contents, but rather a workaround to integrate certain FS into a
unixoid environment. On an ext4 partition like the one you’re
attempting to mount, just change the ownership directly:
mount -t ext4 /dev/sda1 /media/ownclouddrive
chown -R 33:33 /media/ownclouddrive/*
answered Jul 25 '16 at 14:57
phgphg
711518
You are getting that error message because you specify mount
options that don’t apply to the filesystem on the device.
The mount options uid= and gid= are not valid for all
available filesystems. The ones that support proper permissions
usually don’t accept them, as is the case for that ext4 device
you’re attempting to mount.
For filesystems with limited functionality like VFAT, the optionsuid and gid allow mapping the ownership of the entire
contents of a mounted filesystem to a single local user. Similar
options exist for other properties like the umask.
Note that this is not the proper way to grant permissions to the
contents, but rather a workaround to integrate certain FS into a
unixoid environment. On an ext4 partition like the one you’re
attempting to mount, just change the ownership directly:
mount -t ext4 /dev/sda1 /media/ownclouddrive
chown -R 33:33 /media/ownclouddrive/*
answered Jul 25 '16 at 14:57
phgphg
711518
answered Jul 25 '16 at 14:57
phgphg
711518
answered Jul 25 '16 at 14:57
phgphg
711518
answered Jul 25 '16 at 14:57
phgphg
711518
711518
1
Yes! Thanks for this answer. It seems obvious, in hindsight, that changing the ownership directly is the right approach, but... I just caught myself trying to do the exact same thing as the OP, i.e., manipulating permissions for an EXT4-formatted partition via theuid=option in/etc/fstab. Glad my Google search forUnrecognized mount option "uid=led me to this answer!
– evadeflow
Dec 17 '18 at 18:26
add a comment |
1
Yes! Thanks for this answer. It seems obvious, in hindsight, that changing the ownership directly is the right approach, but... I just caught myself trying to do the exact same thing as the OP, i.e., manipulating permissions for an EXT4-formatted partition via theuid=option in/etc/fstab. Glad my Google search forUnrecognized mount option "uid=led me to this answer!
– evadeflow
Dec 17 '18 at 18:26
1
1
Yes! Thanks for this answer. It seems obvious, in hindsight, that changing the ownership directly is the right approach, but... I just caught myself trying to do the exact same thing as the OP, i.e., manipulating permissions for an EXT4-formatted partition via the
uid= option in /etc/fstab. Glad my Google search for Unrecognized mount option "uid= led me to this answer!– evadeflow
Dec 17 '18 at 18:26
Yes! Thanks for this answer. It seems obvious, in hindsight, that changing the ownership directly is the right approach, but... I just caught myself trying to do the exact same thing as the OP, i.e., manipulating permissions for an EXT4-formatted partition via the
uid= option in /etc/fstab. Glad my Google search for Unrecognized mount option "uid= led me to this answer!– evadeflow
Dec 17 '18 at 18:26
add a comment |
In addition to phg, you can use option user i.e.
mount /dev/sda1 /media/ownclouddrive -o user=www-data,rw
answered Mar 1 at 12:30
antonanton
1
add a comment |
In addition to phg, you can use option user i.e.
mount /dev/sda1 /media/ownclouddrive -o user=www-data,rw
answered Mar 1 at 12:30
antonanton
1
add a comment |
In addition to phg, you can use option user i.e.
mount /dev/sda1 /media/ownclouddrive -o user=www-data,rw
answered Mar 1 at 12:30
antonanton
1
In addition to phg, you can use option user i.e.
mount /dev/sda1 /media/ownclouddrive -o user=www-data,rw
answered Mar 1 at 12:30
antonanton
1
answered Mar 1 at 12:30
antonanton
1
answered Mar 1 at 12:30
antonanton
1
answered Mar 1 at 12:30
antonanton
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f298141%2funrecognized-mount-option-uid-33-or-missing-value%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
2
uidandgidare options for filesystems that don’t support permissions, e. g. vfat. They’d make little sense for ext4.– phg
Jul 25 '16 at 13:27
And to override ownership for all files on a file-system (without actually modifying the file metadata stored on the filesystem), you could look at
bindfs– Stéphane Chazelas
Jul 25 '16 at 13:30
So, the suggestion is to change the partition in NTFS?
– Federi
Jul 25 '16 at 13:39
1
A first suggestion would be to remove the
uid=33,gid=33options to themountcommand. If that's not acceptable please edit your question to explain what you're trying to achieve.– roaima
Jul 25 '16 at 13:47
1
@Federi In addition to what @roaima recommends, if you need all
33:33permissions on that filesystem, then justchown -Rits contents once after mounting.– phg
Jul 25 '16 at 14:01