unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Franz Geffke <franz@dkkma.com>
To: help-guix@gnu.org
Subject: Trouble mounting cifs share
Date: Thu, 30 Nov 2023 17:22:38 +0000	[thread overview]
Message-ID: <aecba645-3bf9-401e-b2c1-451e4d02bc41@dkkma.com> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 2586 bytes --]

I'm having trouble mounting cifs; Initially I thought it's a network issue of 
some sort, but it happens on a number of systems and I assume the Hetzner 
Storagebox is OK (as in, configured correctly):

- 2x 6.6.2-gnu Guix: Failed
- 1x 6.1.0-13 Debian: Failed
- 1x 5.10.0-21 Debian: Success

Here's what I'm trying (always as root):

```
mount.cifs -o user=abc,pass=abc //abc.your-storagebox.de/backup /mnt/storage-box
```

SUCCESS:

```
[22217175.369726] FS-Cache: Loaded
[22217175.370661] Key type dns_resolver registered
[22217175.425899] FS-Cache: Netfs 'cifs' registered for caching
[22217175.428484] Key type cifs.spnego registered
[22217175.428593] Key type cifs.idmap registered
[22217175.428940] CIFS: Attempting to mount //abc.your-storagebox.de/backup
[22217175.429066] CIFS: No dialect specified on mount. Default has changed to a 
more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use 
the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 
(or even SMB3 or SMB2.1) specify vers=1.0 on mount.
```

FAILURE:


```
mount.cifs -o user=abc,pass=abc //abc.your-storagebox.de/backup /mnt/storage-box
mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg)
```

dmesg first run:

```
[   47.720337] FS-Cache: Loaded
[   47.832455] Key type cifs.spnego registered
[   47.832480] Key type cifs.idmap registered
[   47.833652] CIFS: No dialect specified on mount. Default has changed to a 
more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use 
the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 
(or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[   47.833657] CIFS: Attempting to mount //u379354.your-storagebox.de/backup
[   47.834369] CIFS: VFS: cifs_mount failed w/return code = -2
```

dmesg second run:

```
[84327.549100] CIFS: Attempting to mount //abc.your-storagebox.de/backup
[84327.549388] CIFS: VFS: cifs_mount failed w/return code = -2
```

third one, directly after 2nd:

```
mount.cifs -o user=abc,pass=abc //abc.your-storagebox.de/backup /mnt/storage-box
mount error(126): Required key not available
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg)
```

dmesg third run:

```
[84355.299014] CIFS: Attempting to mount //abc.your-storagebox.de/backup
[84355.299032] CIFS: VFS: cifs_mount failed w/return code = -126
```

Am I missing something? Thank you.

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2493 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]

             reply	other threads:[~2023-12-03 13:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 17:22 Franz Geffke [this message]
2024-01-12 11:55 ` Trouble mounting cifs share Simon Tournier
2024-01-15 10:30   ` Efraim Flashner
2024-01-16  9:35     ` Reza Housseini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aecba645-3bf9-401e-b2c1-451e4d02bc41@dkkma.com \
    --to=franz@dkkma.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).