I have a NAS in my living room with a bunch of services like GitLab, NextCloud, my personal Website etc. running on it. All these services are reachable via a reverse SSH tunnel between my Ionos VPS with a public IP address running the reverse proxy for my domain and my NAS. This works fine. However, I cannot for the life of me get a regular remote SSH connection from my terminal to the NAS to be established which means I have to SSH into the VPS first and then SSH into the NAS from there and can only use GitLab via HTTPS not SSH. Maybe someone here has an idea. Here's my setup:
NAS (main user malik):
autossh unit:

[Unit]
Description=Reverse SSH Tunnel to VPS
After=network-online.target
Wants=network-online.target

[Service]
User=malik
Environment=HOME=/home/malik
ExecStart=/usr/bin/autossh -M 0 -N \
  -o "ServerAliveInterval 60" -o "ServerAliveCountMax 3" \
  -i /home/malik/.ssh/vps_autossh \
  -R 8080:localhost:80 \
  -R 8443:localhost:443 \
  -R 3001:localhost:3001 \
  -R 8001:localhost:8000 \
  -R 8099:localhost:8099 \
  -R 8022:localhost:8022 \
  -R 2222:localhost:2222\
  tunneluser@212.227.63.142
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

SSHD config:

Include /etc/ssh/sshd_config.d/*.conf

AuthorizedKeysFile      .ssh/authorized_keys

Subsystem       sftp    /usr/lib/ssh/sftp-server

VPS: Main user root for admin and restricted user tunneluser for reverse tunnels SSHD config:

Include /etc/ssh/sshd_config.d/*.conf

KbdInteractiveAuthentication no

UsePAM yes

AcceptEnv LANG LC_*

Subsystem       sftp    /usr/lib/openssh/sftp-server

ClientAliveInterval 120
PermitRootLogin yes

Match User tunneluser
    PasswordAuthentication no
    AllowTcpForwarding yes
    GatewayPorts yes

I use 8022 for GitLab SSH and 2222 for my main NAS user. It looks like everything is working:

root@my-vps:~# sudo netstat -tulnp | grep 8022
tcp        0      0 0.0.0.0:8022            0.0.0.0:*               LISTEN      3546/sshd: tunnelus
tcp6       0      0 :::8022                 :::*                    LISTEN      3546/sshd: tunnelus
root@my-vps:~# sudo netstat -tulnp | grep 2222
tcp        0      0 0.0.0.0:2222            0.0.0.0:*               LISTEN      3627/sshd: tunnelus
tcp6       0      0 :::2222                 :::*                    LISTEN      3627/sshd: tunnelus

When I try to connect from my laptop I get a network unreachable error:

ssh -p 2222 malik@212.227.63.142
ssh -p 8022 git@212.227.63.142
telnet 212.227.63.142 2222
telnet 212.227.63.142 8022

What am I doing wrong?

Installing it via Packages -> Alt-F -> ownlcloud -> install worked, but I got an **empty page** accessing https://mynas:8443/owncloud (only for testing: http://mynas:8080/owncloud ) (which forwarded to .../index.php).

I logged in as root and tried to recursively delete the folder /volume2/Name using rm -rf It started and deleted all the files/directories inside this folder Name, but it cannot remove the folder itself even though I am root: rm: cannot remove 'Name’: Operation not permitted The command ls -l list the permissions for this folder as: d---------+ 1 root root Synology has a special tool called synoacltool for these ACL permissions, but I don't know to use it. So what do I need to do in order to be able to remove this (empty) folder?

I have several Synology NAS, running DSM 6.2.2-24922 Update 5, which I successfully mount on Ubuntu 18.04 with: sudo mount -t cifs //192.168.x.y/folder_name -o username=user,password=???????,uid=1000,sec=ntlm,vers=1.0 /local_mount_point I have bought a new one, which is running DSM 6.2.4-25556. I attempt to mount in the same way and I get this error: mount: /local_mount_point: mount(2) system call failed: Operation not supported. EDIT I removed the vers=1.0, and the error changed to //192.168.x.y/folder_name does not exist Enable SMB Share is enabled on the new NAS, with the same settings as the others. My smb.conf on the new NAS is: [global] printcap name=cups winbind enum groups=yes include=/var/tmp/nginx/smb.netbios.aliases.conf min protocol=SMB2 security=user local master=no realm=* passdb backend=smbpasswd printing=cups max protocol=SMB3 winbind enum users=yes load printers=yes workgroup=WORKGROUP And my smb.share.conf is: [folder_name] recycle bin admin only=yes ftp disable modify=no ftp disable download=no write list=nobody,nobody browseable=yes mediaindex=no hide unreadable=no win share=yes enable recycle bin=yes invalid users=nobody,nobody read list=nobody,nobody ftp disable list=no edit synoacl=yes valid users=nobody,nobody writeable=yes guest ok=yes path=/volume2/folder_name_1 skip smb perm=yes comment="" [folder_name_2] recycle bin admin only=yes ftp disable modify=no ftp disable download=no write list=nobody,nobody browseable=yes mediaindex=no hide unreadable=no win share=yes enable recycle bin=yes invalid users=nobody,nobody read list=nobody,nobody ftp disable list=no edit synoacl=yes valid users=nobody,nobody writeable=yes guest ok=yes path=/volume1/folder_name_2 skip smb perm=yes comment="" (For interest, the smb.conf on one of the NAS which are working is: [global] printcap name=cups winbind enum groups=yes include=/var/tmp/nginx/smb.netbios.aliases.conf security=user local master=no realm=* passdb backend=smbpasswd printing=cups max protocol=SMB2 winbind enum users=yes load printers=yes workgroup=WORKGROUP ) Can anyone advise?

We have a NAS server in the lab and I can reach it through the web interface at 192.168.1.100, and I have enabled NFS on the admin's panel. After that I did sudo aptitude install nfs-common sudo mount -t nfs4 192.168.2.254:/gwas_data /media/thecus Result: mount.nfs4: Connection timed out OS is Ubuntu 14.04. Any ideas?

I have a NAS share for my Linux server which I mount using the following command. mount -t nfs 172.16.2.115:/shares/OwnCloud /eStore/ now to automate this I added the following line in /etc/fstab 172.16.2.115:/shares/OwnCloud /eStore nfs rw,addr=172.16.2.115,auto 0 0 but it is not working and I am not getting any error also. If I execute mount -a then mount is able to mount the NAS based on /etc/fstab configuration. I would like it to mount at boot.

I'm running a NAS server with https://www.openmediavault.org/ on a Raspberry PI. I've made a "shared folder", activated SMB sharing and within it created a share for this folder with "only guests" mode. I can use the share over the network. But now I want to secure it with a login/password instead of "only guests" and I'm a bit overwhelmed. How do I make sure my share needs credentials for access (read/write)?

I am trying to setup SSH public keys to login to my GoFlex Home 2TB. These are the steps I took 1. Copy my public key to /home/user/.ssh/authorized_keys 2. Modify /etc/ssh/sshd_config to allow public key authentication and point to the authorized_keys file 3. End the SSH session 4. login to goflexhome.loal and reboot the NAS device ## Details of the client system: - OS: Linux Mint 17.3 - Network type: LAN (Ethernet) ## Details of the host system (NAS) - OS: hipserv2 (Linux based by Seagate, default OS in GoFlex Home) When I try to initiate the ssh session I get a password prompt instead of using my private key to login ## File Permissions at /home/user/.ssh -bash-3.2$ ls -la total 4 drwxr-xr-x 2 user root 232 Mar 18 16:49 . dr-xr-x--- 7 user www 616 Mar 18 16:48 .. -rwxr-xr-x 1 user root 746 Mar 18 16:49 authorized_keys -bash-3.2$ ## SSH verbose Full PasteBin . Excerpt:

ssh -v user_hipserv2_seagateplug_XXXX-XXXX-XXXX-XXXX@goflexhome.local
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
...
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure.  Minor code may provide more information
No Kerberos credentials available
...
debug1: Next authentication method: publickey
debug1: Offering RSA public key: user@user-system
debug1: Server accepts key: pkalg ssh-rsa blen 535
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Trying private key: /home/user/.ssh/id_rsa
debug1: Trying private key: /home/user/.ssh/id_dsa
debug1: Trying private key: /home/user/.ssh/id_ecdsa
debug1: Trying private key: /home/user/.ssh/id_ed25519
debug1: Next authentication method: password
user_hipserv2_seagateplug_XXX@goflexhome.local's password: 
debug1: Authentication succeeded (password).
Authenticated to goflexhome.local ([10.42.0.12]:22).

I have a Linux server running Ubuntu, on which I am trying to successfully set up our network-attached storage drive. I can mount it without issues, but after a few hours, the folder becomes inaccessible, displaying a "stale file handle" error. I can easily fix this by unmounting the drive and remounting it, but this requires root privileges, and so the users of the server aren't able to fix this on their own. Is there any reason this would be continually happening? And if so, how might fix it or have a workaround? My mount command is:

mount -t cifs -o username=MYUSER,workgroup=d,vers=2.0,uid=user,gid=user //NASLOCATION /home/user/MNT_DIR

I use this same command for my personal computer, and I get a stale file handle every month or so, but not every few hours. Any suggestions?

I'm trying to automatically mount a network drive at startup by editing /etc/fstab but doesn't work. If I execute this líne, sudo mount.cifs //192.168.0.67/test /home/pi/test -o username=myname,password=123 it works great. But I don't know how to properly write the same in /etc/fstab.

I have apparently a weird permission problem with a Western Digital MyCloud NAS. It is mounted by this fstab entry: //172.23.0.252/Public /mnt/NAS cifs vers=2.1,uid=1000,gid=1000,credentials=/root/.smbcredentials,iocharset=utf8,nobrl 0 0 the resulting mount: //172.23.0.252/Public on /mnt/NAS type cifs (rw,relatime,vers=2.1,sec=none,cache=strict,uid=1000,forceuid,gid=1000,forcegid,addr=172.23.0.252,file_mode=0755,dir_mode=0755,iocharset=utf8,soft,nounix,mapposix,nobrl,rsize=1048576,wsize=1048576,bsize=1048576,retrans=1,echo_interval=60,actimeo=1,closetimeo=1) The files on this WD NAS were created by restoring a backup from USB drive on May 20, 2022. I have no problem writing to NAS from a machine running Ubuntu 20.04. However I have a laptop I upgraded to 24.04 with a complete reformat. After much troubleshooting, I discovered the 25.04 install will not write to the NAS in any directory that was part of the 2022 restore. Directories created after May 20, 2022 seem to work OK. I though Apparmor was the problem but I have that disabled and still can't write. Here I am trying to write to directories from different dates: jbh@510S:/mnt/NAS$ touch Woodworking/DPWWC/Newsletter2025/2501/touch.test jbh@510S:/mnt/NAS$ touch Woodworking/DPWWC/Newsletter2024/2401/touch.test jbh@510S:/mnt/NAS$ touch Woodworking/DPWWC/Newsletter2023/2301/touch.test jbh@510S:/mnt/NAS$ touch Woodworking/DPWWC/Newsletter2022/2201/touch.test touch: cannot touch 'Woodworking/DPWWC/Newsletter2022/2201/touch.test': Permission denied jbh@510S:/mnt/NAS$ touch Woodworking/DPWWC/Newsletter2022/2207/touch.test jbh@510S:/mnt/NAS$ touch Woodworking/DPWWC/Newsletter2022/2204/touch.test jbh@510S:/mnt/NAS$ touch Woodworking/DPWWC/Newsletter2022/2203/touch.test touch: cannot touch 'Woodworking/DPWWC/Newsletter2022/2203/touch.test': Permission denied jbh@510S:/mnt/NAS$ I can write to Newsletter2022/2204/ but not to Newsletter2022/2203. 2203 was created by the restore on May 20 but modified after May 20 by the 20.04 machine. 2204 was created after May 20. jbh@510S:/mnt/NAS$ ls -ltr /mnt/NAS/Woodworking/DPWWC/Newsletter2022 | grep ^d drwxr-xr-x 2 jbh jbh 0 May 20 2022 2201 drwxr-xr-x 2 jbh jbh 0 May 20 2022 2202 drwxr-xr-x 2 jbh jbh 0 May 26 2022 2203 drwxr-xr-x 2 jbh jbh 0 Jul 29 2022 2206 drwxr-xr-x 2 jbh jbh 0 Aug 7 2022 2208 drwxr-xr-x 2 jbh jbh 0 Sep 7 2022 2205 drwxr-xr-x 2 jbh jbh 0 Nov 11 2022 2210 drwxr-xr-x 2 jbh jbh 0 Dec 11 2022 2212 drwxr-xr-x 2 jbh jbh 0 Oct 1 2023 2211 drwxr-xr-x 2 jbh jbh 0 Jan 19 15:02 2209 drwxr-xr-x 2 jbh jbh 0 Feb 9 14:15 2207 drwxr-xr-x 2 jbh jbh 0 Feb 9 14:15 2204 jbh@510S:/mnt/NAS$ This is blocking me from upgrading the remaining 20.04 machine. The MyCloud box runs Linux and I can SSH to it for more information if it helps.

I found many guides on how to mount a NAS drive via fstab. Quite some enter username and password right into the fstab file, others use a file .smbcredentialsfor that. I'd like to manage all my credentials with KeePassXC or some other portable database. Is there a way to tell the fstab fetching the username and password from such credential manager? My probably-a-lot-of-work-around idea was, to use some kind of [scriptfs](https://github.com/frodonh/scriptfs) (_this one seems unmaintained, but maybe there is a modern alternative_) to create a virtual filesystem, exposing a virtual file as proxy between the password store and the fstab (.smbcredentials). So any hints in this direction may be appreciated, if no simpler solution is available.

I have a new Synology NAS with 2 storage pools, and I have one volume per pool. I have added a single SSD to the NAS to serve as a cache, and was able to add it to the first storage pool. This is a fairly large SSD (4TB), so I would like to share it with the second storage pool. However, I am unable to add it to the second storage pool. According to the Synology Online Guide "SSD cache group supports cache creation on multiple volumes". Perhaps I misinterpreted this statement! Can I use my large SSD to provide caching for multiple volumes, across multiple storage pools? (I can't believe they want me to add 1 SSD for each storage pool) I'm using a SATA SSD in case that matters. I read that (I think) I can use NVMe card as cache instead. Does that behave the same way? (There are only 2 NVMe slots, so that would mean max 2 storage pools can be read cached, or 1 storage pool r+w cached).

I have a new Synology NAS (DS1621+), and have begun integration into my home network. I'm having some problems using it with my Linux hosts. I can mount the NAS, but the permissions (as seen from Linux) are not what I want them to be. I'm under the impression that ownership & permissions can be *"mapped"* from the NAS to my Linux clients, but it's unclear to me how this is done. My Linux hosts are all Debian-based units, and file services provided by the Synology NAS are via SMB. From Linux, I use the *cifs-utils suite* (mount -t cifs ...) to mount the shares. I've contacted Synology, and was surprised to learn: **1:** Synology does not provide tech support to "command line" users. **2:** Synology claimed their SMB implementation is proprietary, and do not provide any (useful) documentation on the interface. I *suspect* that Synology's implementation is not *that* far off mainstream, but after some trial-and-error, I'm still having *"permissions issues"*. Also, the mount.cifs manual has many options whose purpose and effect are vague to me. Are there any Linux tools available that can help identify how the various options and parameters in mount.cifs affect permissions as seen from the Linux client's perspective? I'd like to eliminate as much of the *trial-and-error* as possible. I'm interested in using SMB instead of NFS because I've heard more negatives on NFS than I have SMB. I have created the users on the Synology side and added them to the SMB config there. #### EDIT: 2022-07-12; More reading, findings The *variables* which seem to be in play are: 1. the state of the Linux implementation of the ["Unix Extensions"](https://wiki.samba.org/index.php/UNIX_Extensions) to SMB, and the version on my client machine 2. the state of the server's (Synology's) implementation of SMB/Samba 3. the state of the server's (Synology's) implementation of the "Unix Extensions" In an effort to improve the quality of this question, I've attempted to define these variables in the context of my question: 1. Re the state of the Linux implementation of the "Unix Extensions":

$ mount.cifs --version
   mount.cifs version: 6.11
   # NOTE1: Unix Extensions are enabled by default per man mount.cifs 
   # NOTE2: see also 'modinfo cifs'

2. Re server (Synology) version of SMB/Samba:

$ ssh admin@SynologyNAS-1
   /$ samba --version
   Version 4.10.18 
   /$ uname -srm
   Linux 4.4.180+ x86_64

3. Re server (Synology) version of the "Unix Extensions" ***I'm at a loss on how to do this, so I tried smbclient:***

$ smbclient \\\\SynologyNAS\\rpi_share -U=pi
   Enter WORKGROUP\pi's password:
   Try "help" to get a list of possible commands.
   smb: \> help
   ?              allinfo        altname        archive        backup
   blocksize      cancel         case_sensitive cd             chmod
   chown          close          del            deltree        dir
   du             echo           exit           get            getfacl
   geteas         hardlink       help           history        iosize
   lcd            link           lock           lowercase      ls
   l              mask           md             mget           mkdir
   more           mput           newer          notify         open
   posix          posix_encrypt  posix_open     posix_mkdir    posix_rmdir
   posix_unlink   posix_whoami   print          prompt         put
   pwd            q              queue          quit           readlink
   rd             recurse        reget          rename         reput
   rm             rmdir          showacls       setea          setmode
   scopy          stat           symlink        tar            tarmode
   timeout        translate      unlock         volume         vuid
   wdel           logon          listconnect    showconnect    tcon
   tdis           tid            utimes         logoff         ..
   !
   smb: \> ? posix
   HELP posix:
   	   turn on all POSIX capabilities
   
   smb: \> posix
   Server doesn't support UNIX CIFS extensions.
   smb: \> ? chmod
   HELP chmod:
	     chmod a file using UNIX permission
   
   smb: \> chmod test-touch-4B.txt 666
   Server doesn't support UNIX CIFS calls.
   ...

#### 2022-07-12; Conclusions & Revised Questions? The above results with smbclient ***suggest*** that with respect to SMB/CIFS, my client software is [*up to speed*](https://idioms.thefreedictionary.com/up+to+speed) , but my shiny new Synology NAS is far [*behind the curve*](https://idioms.thefreedictionary.com/behind+the+curve) . My original question now becomes, "Are these results accurate; is there a more conclusive or accurate method to determine the status of a product when the vendor refuses any information on it?" For those with similar questions, I can only offer this: >***In my case***: I mount using Synology user pi credentials. Doing so leaves my Linux user pi unable to write to the mounted share - despite the fact that Synology user pi had been given R&W privileges in the Synology DSM. I found that adding the uid=pi and gid=pi options to my mount -t cifs command, at least enabled the Linux user pi to write to the SMB share on the Synology server. ***Why*** this works I will have to leave for others to answer. ### Further Reading: 1. [The SMB UNIX Extensions Wiki](https://wiki.samba.org/index.php/UNIX_Extensions) 2. [CIFS VFS - Protocol extensions to the Common Internet File System for better POSIX file I/O semantics](https://www.samba.org/samba/CIFS_POSIX_extensions.html) 3. [A Search: what are the "Unix Extensions" for SMB/CIFS/Samba?](https://duckduckgo.com/?t=ffab&q=what+are+the+%22Unix+Extensions%22+for+SMB%2FCIFS%2FSamba&atb=v278-1&ia=web) . 4. [Samba version 4.3 or newer supports SMB 3.1.1](https://www.admin-magazine.com/Archive/2017/40/SMB-3.1.1-in-Windows-Server-2016) 5. [Linux cifs mailing list](http://vger.kernel.org/vger-lists.html#linux-cifs) 6. mount.cifs and mount.smb3 are *nearly* the same; ref man mount.cifs - which is also the manual for mount.smb3. 7. [The SMB3-Linux Wiki](https://wiki.samba.org/index.php/SMB3-Linux) 8. [Are SMB POSIX Extensions Same As SMB Unix Extensions?... *Apparently not*](https://snia.org/sites/default/files/SDC/2020/053-French-SMB3-POSIX-Extensions-Phase.pdf) 9. [CIFS Protocol Extensions Update, fm 2006 (This has been YEARS in the making)](https://download.samba.org/pub/samba/cifs-cvs/snia-developer-2006-cifs-extensions.pdf) 10. [A Tour through the CIFS Protocol Extensions and Linux CIFS client, fm. 2008](https://vdocument.in/a-tour-through-the-cifs-protocol-extensions-and-linux-cifs-almost-ntfscifs.html) . 11. [SMB3 POSIX Extensions Phase 2 ... what is next? (fm. 2020)](https://snia.org/sites/default/files/SDC/2020/053-French-SMB3-POSIX-Extensions-Phase.pdf) 12. [The video of #10 above](https://www.snia.org/educational-library/smb3-posix-extensions-phase-2-now-they-are-what-next-2020) 13. [The Linux kernel user’s and administrator’s guide » CIFS (note: more verbiage by Steve French)](https://www.kernel.org/doc/html/latest/admin-guide/cifs/index.html) 14. [What Is SMB Protocol and Why Is it a Security Concern?](https://cybersophia.net/articles/what-is/what-is-smb-protocol-and-why-is-it-a-security-concern/) 15. [Server Message Block - Wikipedia](https://en.wikipedia.org/wiki/Server_Message_Block)

I have a RasPi 4 connected to a 12TB EXT4 hard drive in a Sabrent cage hub which I use for an OpenMediaVault NAS. The drive worked fine for about a month until its file system started to go missing in OMV, either completely or visible and unmounted with the status "missing." I've tried automatically rebooting every 12 hours or manual restarts (the Pi and cage have separate power buttons) and cannot tell which method is more reliable. I've noticed the block device sometimes changes between sda(1) and sdb(1) and other times no partitions are listed in fdisk or df. Sometimes the drive is SMART compatible (and passes), other times it says it isn't. I've had error messages after the following commands:

**(1) [2024-11-02] sudo smartctl -a /dev/sda | less**

SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

General SMART Values:
Offline data collection status:  (0x80) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (   87) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        (   1) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   132   132   054    Pre-fail  Offline      -       96
  3 Spin_Up_Time            0x0007   155   155   024    Pre-fail  Always       -       425 (Average 425)

**(2) [2024-11-02] dmesg**

[ 1197.499680] critical target error, dev sda, sector 23437770624 op 0x0:(READ)                                                                                                                                                                                                                                              flags 0x0 phys_seg 1 prio class 2

[ 1197.499692] Buffer I/O error on dev sda, logical block 2929721328, async page                                                                                                                                                                                                                                              read

[Note: no errors in dmesg as of 2024-12-02]

**(3) [2024-12-01] sudo fdisk -l /dev/sda**

fdisk: cannot open /dev/sda: Input/output error

**(4) [2024-12-01] sudo fsck /dev/sda**

fsck.ext2: Input/output error while trying to open /dev/sda

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193  [Note: this option timed out]
 or
    e2fsck -b 32768  [Note: this option timed out]

**(5) [2024-12-01] sudo smartctl -i /dev/sda**

Read Device Identity failed: scsi error medium or hardware error (serious)

**(6) [2024-12-01] sudo smartctl --all /dev/sda1 --test=short -T permissive**

SMART support is:     Unavailable - device lacks SMART capability

Error Counter logging not supported

No Self-tests have been logged

It appears most likely to unmount after I'm away from home and don't perform updates for awhile (I have not set up a reverse proxy for the RasPi in general, only for a Plex server). I can't tell if the hard drive is about to fail or if this is all just an issue with booting.

I recently swapped from Windows 10 to Arch Linux. I connected to a Samba share on NAS but after restarting Arch desktop, the Nautilus file manager says "folder is empty". I connected to it via a symlink so I can acces all my files.

I'm trying to follow this https://kb.synology.com/en-uk/DSM/tutorial/How_can_I_recover_data_from_my_DiskStation_using_a_PC#x_anchor_encryptedvolume sudo -i apt-get update apt-get install -y mdadm lvm2 mdadm -AsfR && vgchange -ay mdadm: Found some drive for an array that is already active: /dev/md/brayc:2 mdadm: giving up. mdadm: No arrays found in config file or automatically cat /proc/mdstat Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md127 : active raid1 sdb3 3902196544 blocks super 1.2 [2/1] [_U] lvs mount /dev/md127 /home/ubuntu/nas mount: /home/ubuntu/nas: uknown filesystem type 'LVM2_member'. dmesg(1) may have more information after failed mount system call But I have problems when I run the mount command

I have a Synology NAS serving shared folders with SMB. On Windows and MAC I just have to indicate the IP of the NAS and all the shared folder are discovered and mounted. On linux (the latest Debian) (with cifs) I can only mount each folder individually. Meaning I have to know exactly the name of the folder to mount. I would like to have all the shared folders discovered automatically under a unique mounting point like on the others OSs

I'm having an issue **mounting a shared NAS drive that is hosted on a Windows 2000 server**. This is a drive that I'm certain I have access to, and I frequently access it from a Windows 7 machine and a Windows Server 2008 machine. Now, **I'm attempting to mount this drive from a RHEL7 machine**, but I'm having some issues. **What I've done:** mkdir /mnt/neededFolder mount -t cifs //DNS.forMyDrive.stuff/neededFolder /mnt/neededFolder -o username=myUserId,password=myPassword,domain=myDomain **What I expected:** I expected to be able to access the folder at */mnt/neededFolder* **What actually happened:** The error I'm receiving (partially shown in the subject line here) is mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) **What the log says:** **dmesg** output: [1712257.661259] CIFS VFS: Error connecting to socket. Aborting operation. [1712257.662098] CIFS VFS: cifs_mount failed w/return code = -115 We can all see that there is a connection issue, that is obvious. I know both machines are connected to the network. **What can I try next to get this drive mounted?** **EDIT:** It may be worth noting that I am able to ping the DNS name and the raw IP of the remote location that I am trying to mount.

I'm on a NAS and had been running some YAMLs. I have a user ID johnG(1042) G(100) which was used for the YAML. There were some updates along, and I'm not sure how it happened but suddenly it changed to abc(1042) G(100). Now both names exist with the same ID and Group. I did not make the change knowingly and no one else has access to the NAS. Everything seems to be running, but I don't want to wait until there is an issue. How do I get rid of that second name to the same id?