Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #261740 > unrolled thread

Can't mount NFS NAS after major upgrade

Back to article view | Back to linux.debian.user

Contents

  Can't mount NFS NAS after major upgrade Steve Matzura <sm@noisynotes.com> - 2023-09-17 21:50 +0200
    Re: Can't mount NFS NAS after major upgrade Charles Curley <charlescurley@charlescurley.com> - 2023-09-17 22:30 +0200
    Re: Can't mount NFS NAS after major upgrade Tom Dial <tddial@comcast.net> - 2023-09-18 03:30 +0200
    Re: Can't mount NFS NAS after major upgrade <tomas@tuxteam.de> - 2023-09-18 06:40 +0200
    Re: Can't mount NFS NAS after major upgrade debian-user@howorth.org.uk - 2023-09-18 10:50 +0200

#261740 — Can't mount NFS NAS after major upgrade

[Multipart message — attachments visible in raw view] — view raw

I upgraded a version 8 system to version 11 from scratch--e.g., I 
totally reinitialized the internal drive and laid down an entirely fresh 
install of 11. Then 12 came out about a week later, but I haven't yet 
upgraded to 12 because I have a show-stopper on 11 which I absolutely 
must solve before moving ahead, and it's the following:


For years I have had a Synology NAS that was automatically mounted and 
directories thereon bound during the boot process via the following 
lines at the end of /etc/fstab:


# NAS box:
//192.168.1.156/BigVol1 /mnt/bigvol1 cifs 
_netdev,username=<username>,password=<password>,ro 0 0

Then I had the following line, replicated for several directories on 
bigvol1, to bind them to directories on the home filesystem, all in a 
script called /root/remount that I executed manually after each reboot:


mount /mnt/bigvol1/dir-1 /home/steve/dir-1 -o bind,ro

I had directories set up on the home filesystem to accept these binds, 
like this:


mount /mnt/bigvol1/dir-1 /home/steve/dir-1 -o bind,ro


None of this works any more on Debian 11. After boot, /mnt/bigvol1 is 
empty, so there's no need to even try the remount script because there's 
nothing to which those directories can bind, so even if those mount 
commands are correct, I would never know until bigvol1 mounts correctly 
and content appears in at least 'ls -ld /mnt/bigvol1'.


Research into this problem made me try similar techniques after having 
installed nfs-utils. I got bogged down by a required procedure entailing 
exportation of NFS volume information in order to let nfs-utils know 
about the NFS drive, but before I commit to that, I thought I'd ask in 
here to make sure I'm not about to do anything horribly wrong.


So, summarily put, what's different about mounting a networked NFS drive 
from 8 to 11 and 12?


Thanks in advance.

[toc] | [next] | [standalone]

#261742

On Sun, 17 Sep 2023 14:43:16 -0400
Steve Matzura <sm@noisynotes.com> wrote:

> # NAS box:
> //192.168.1.156/BigVol1 /mnt/bigvol1 cifs 
> _netdev,username=<username>,password=<password>,ro 0 0

Possibly part of the problem is that this is a CIFS (Samba) mount, not
an NFS mount.

Is samba installed?

If you try to mount that mount manually, what error message(s) and
return value do you get? e.g. a successful mount:

root@jhegaala:~# mount /home/charles/samba 
root@jhegaala:~# echo $?

0
root@jhegaala:~# 

You may also want to rethink that line in fstab. I have, e.g.:

//samba.localdomain/samba /home/charles/samba cifs _netdev,rw,credentials=/etc/samba/charles.credentials,uid=charles,gid=charles,file_mode=0644,noauto	0	0

The noauto is in there because this is a laptop, and I have scripts to
mount it only if the machine is on a home network. For a desktop, I
remove the noauto and have x-systemd.automount instead.


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#261747

On 9/17/23 12:43, Steve Matzura wrote:
> I upgraded a version 8 system to version 11 from scratch--e.g., I totally reinitialized the internal drive and laid down an entirely fresh install of 11. Then 12 came out about a week later, but I haven't yet upgraded to 12 because I have a show-stopper on 11 which I absolutely must solve before moving ahead, and it's the following:
> 
> 
> For years I have had a Synology NAS that was automatically mounted and directories thereon bound during the boot process via the following lines at the end of /etc/fstab:
> 
> 
> # NAS box:
> //192.168.1.156/BigVol1 /mnt/bigvol1 cifs _netdev,username=<username>,password=<password>,ro 0 0
> 
> Then I had the following line, replicated for several directories on bigvol1, to bind them to directories on the home filesystem, all in a script called /root/remount that I executed manually after each reboot:
> 
> 
> mount /mnt/bigvol1/dir-1 /home/steve/dir-1 -o bind,ro
> 
> I had directories set up on the home filesystem to accept these binds, like this:
> 
> 
> mount /mnt/bigvol1/dir-1 /home/steve/dir-1 -o bind,ro
> 
> 
> None of this works any more on Debian 11. After boot, /mnt/bigvol1 is empty, so there's no need to even try the remount script because there's nothing to which those directories can bind, so even if those mount commands are correct, I would never know until bigvol1 mounts correctly and content appears in at least 'ls -ld /mnt/bigvol1'.
> 

Are there relevant messages in the output of dmesg or in the systemd journal? If so, they might give useful information.

This is out of range of my usage and experience, but from others I have found that some consumer NAS units still use, and are effectively stuck at, SMB1. SMB version 1 has a fairly serious uncorrectable vulnerability and Microsoft deprecated it (but continued to support it through, I think Windows 11. I believe Samba no longer supports it by default, but still can be configured to use it, with some effort, if you wish. Another, and preferable fix would be to configure the Synology to use SMB version 3, if that appears to be the cause of the problem.

If the Synology NAS supports NFS, that might be a better approach in the long run, though.

Regards,
Tom Dial
> 
> Research into this problem made me try similar techniques after having installed nfs-utils. I got bogged down by a required procedure entailing exportation of NFS volume information in order to let nfs-utils know about the NFS drive, but before I commit to that, I thought I'd ask in here to make sure I'm not about to do anything horribly wrong.
> 
> 
> So, summarily put, what's different about mounting a networked NFS drive from 8 to 11 and 12?
> 
> 
> Thanks in advance.
> 
> 

[toc] | [prev] | [next] | [standalone]

#261750

[Multipart message — attachments visible in raw view] — view raw

On Sun, Sep 17, 2023 at 02:43:16PM -0400, Steve Matzura wrote:

As Charles points out, this looks rather like CIFS, not NFS:

> # NAS box:
> //192.168.1.156/BigVol1 /mnt/bigvol1 cifs
                                       ^^^^
> _netdev,username=<username>,password=<password>,ro 0 0

If Charles's (and my) hunch is correct, perhaps this wiki page
contains leada for you to follow:

  https://wiki.debian.org/Samba/ClientSetup

Cheers
-- 
tomás

[toc] | [prev] | [next] | [standalone]

#261752

Steve Matzura <sm@noisynotes.com> wrote:
 
> mount /mnt/bigvol1/dir-1 /home/steve/dir-1 -o bind,ro

In addition to what others have observed it might be worth mentioning
that the -v option to mount (i.e. verbose) often gives more information
about what's going on.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web