On Tue 06 Aug 2019 at 12:18:21 (-0500), Dennis Wicks wrote:
> Thomas Schmitt wrote on 8/6/19 10:30 AM:
> > Dennis Wicks wrote:
> > > I *cannot* mount *any* partition on /wa1
> > > but I *can* mount *any* partition on any other mount point.
> >
> > So what do you get from these shell commands ?
> I am currently running with "ln -s /wa11 /wa1" so this isn't the
> config I booted with. Anyway;
> >
> > ls -ld /wa1 /wa11
>
> wix@dgwicks:~$ ls -ld /wa1 /wa11
> lrwxrwxrwx 1 root root 4 Aug 1 17:40 /wa1 -> wa11
> drwxrwxrwx 17 root root 4096 Jun 17 14:07 /wa11
> wix@dgwicks:~$
>
> >
> > find /wa1
>
> wix@dgwicks:~$ cd /
> wix@dgwicks:/$ find /wa1
> /wa1
> wix@dgwicks:/$ lg wa1
> lrwxrwxrwx 1 root root 4 Aug 1 17:40 wa1 -> wa11/
> drwxrwxrwx 17 root root 4.0K Jun 17 14:07 wa11/
> lrwxrwxrwx 1 root root 7 Aug 1 17:43 www -> wa1/www/
> wix@dgwicks:/$
>
> >
> > What happens if you create a new /wa1 ?
> >
> > mv /wa1 /wa1_old
> > mkdir /wa1
> > mount /dev/sdb2 /wa1
> >
>
> Same failure. One of the many things I tried to get the mount on /wa1
> to work, without any success.
Shouldn't that fail with:
~# mkdir /wa1
~# mount /dev/sda4 /wa1
mount: /dev/sda4 is already mounted or /wa1 busy
/dev/sda4 is already mounted on /ya
~#
> > --------------------------------------------------------------------
> >
> > As for your fstab, there is this "x-systemd.device-timeout=20" where
> > all others have "=60". But the web says this is for automounting.
>
> This param is to stop the boot process from stopping because all of
> the mounts have failed, temporarily. A previous thread from a few
> weeks(?) back.
> >
> > I fail to imagine any explanation for the symptoms you report. Especially
> > the silent failure riddles me.
Unfortunately there's too much reported speech in this thread,
and not enough direct speech. Some timely copy/paste might help.
> Me too! Happens during boot and when done manually!
Cheers,
David.
