Article 6MSAE Ubuntu Desktop 22.04.4 LTS - error 13 (Permission denied) opening credential file /etc/cred_1

Ubuntu Desktop 22.04.4 LTS - error 13 (Permission denied) opening credential file /etc/cred_1

by
porican
from LinuxQuestions.org on (#6MSAE)
Hello! This is my first post so please forgive me if I forget something. I'm pretty new to linux, I installed my first instance (Ubuntu Desktop 22.04.4 LTS) on a mini PC to run a Plex and Torrent server. I mount two network drives that host the filesione is a Drobo 5N, the other a Synology DS713+iusing CIFS. I had no idea what I was doing but did some reading, some trial an error, and managed to get both servers up and running, and they've been working flawlessly for several months.

Today while watching a movie, Plex lost access to the file. When I went to check the mini PC, and the drive had been umounted and the torrent client had shut down. There were system updates pending, so I installed them and rebooted. My Synology drive had no issues mounting, but the Drobo would not mount, and I got this error:

Quote:
error 13 (Permission denied) opening credential file /etc/cred_1
I use a credential file to mount both drives with (the same) admin login info, and edited etc/fstab to do it automatically upon reboot. This has worked flawlessly for four months. Some searching shows that recent updates to the linux kernel have broken SMB shares, but most of the errors I'm seeing people report refer to "Resource temporarily unavailable" which is not my specific error. And again, only one of the shares (the Drobo) brokeithe Synology still mounts just fine. And both shares are still fully accessible from other computers (running macOS).

When I try to force the mount in terminal with sudo mount -a, I get:

Quote:
mount error: Server abruptly closed the connection.
This can happen if the server does not support the SMB version you are trying to use.
The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
I then tried editing the smb.conf file, adding "client min protocol = NT1" below the "[global]" line, in case the drobo only used the old SMB version (I don't know if it does or not). It didn't work.

I foolishly do not have a backup to roll back to. How can I fix this? Both my Plex and Torrent servers are out of commission until I can mount this drive on my miniPC again. I'm a linux noob but willing to study up, I'm just baffled that my whole setup can break instantly from a random update.

Please help, and thank you in advance!
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments