1.4.0 Release Candidate 2

[Snoopy8]

Have tried NFSv3, NFSv4, NFSv4.1 as mount options, issue still there. 

Came across this article.  Could it be that my problem is a large partition?  But I do not have Fstab entries for my NFS partitions, so SO is doing things differently.
https://wiki.archlinux.org/index.php/Fst...th_systemd

[agent_kith]

Have tried NFSv3, NFSv4, NFSv4.1 as mount options, issue still there. 

Came across this article.  Could it be that my problem is a large partition?  But I do not have Fstab entries for my NFS partitions, so SO is doing things differently.
https://wiki.archlinux.org/index.php/Fst...th_systemd

Did it work when you try to add the entries in /etc/fstab?

Your NFSv4 mount definitions is a bit non-standard as NFSv4 is just supposed to be server:/share_name (this way it's more secure than nfsv3). However you also said NFSv3 and CIFS isn't working.

Still at a loss what is wrong to be honest, can you show me a screencap of the mount configuration in Snakeoil WebApp? Just am interested to see what is in there. Any hints you can get from `sudo dmesg`? 

Also, RC-3 is delayed a little as suddenly a lot of things start to break/die around the house. Annoying because have to take time out to address those issues.. Hopefully will release RC-3 later tomorrow or the weekend (depending on how long it'll take to address the latest breakdown).

[Snoopy8]

Did it work when you try to add the entries in /etc/fstab?

Tried. Still same problem.
 

Your NFSv4 mount definitions is a bit non-standard as NFSv4 is just supposed to be server:/share_name (this way it's more secure than nfsv3). However you also said NFSv3 and CIFS isn't working.

Have tried NFSv3. NFSv4, NFSv4.1, CIFS. All require manual remounting.
 

Still at a loss what is wrong to be honest, can you show me a screencap of the mount configuration in Snakeoil WebApp? Just am interested to see what is in there. Any hints you can get from `sudo dmesg`? 

No obvious errors in sudo dmesg.

And guess what? 1.4RC2 installs on Ubuntu 22.04 and NFS disks remount automatically on reboot.


This is for 22.04
 

Code:

sudo systemd-analyze blame
[sudo] password for cs:
6.771s systemd-networkd-wait-online.service
1.028s dev-mapper-ubuntu\x2d\x2dvg\x2dubuntu\x2d\x2dlv.device
607ms dev-loop0.device
606ms dev-loop2.device
606ms dev-loop1.device
471ms snap.lxd.activate.service
423ms snapd.seeded.service
373ms cloud-init-local.service
356ms cloud-init.service
354ms snapd.service
341ms cloud-final.service
333ms cloud-config.service
232ms systemd-binfmt.service
198ms apport.service
187ms smbd.service
183ms systemd-resolved.service
177ms dev-hugepages.mount
175ms plymouth-read-write.service
174ms lighttpd.service
173ms dev-mqueue.mount
169ms sys-kernel-debug.mount
165ms sys-kernel-tracing.mount
160ms systemd-udev-trigger.service
158ms systemd-tmpfiles-setup.service
158ms ufw.service
147ms keyboard-setup.service
145ms grub-common.service
142ms kmod-static-nodes.service
137ms lvm2-monitor.service
133ms polkit.service
131ms systemd-journald.service
128ms [email protected]
124ms [email protected]
120ms modprobe@efi_pstore.service
116ms [email protected]
116ms secureboot-db.service
115ms finalrd.service
114ms networkd-dispatcher.service
113ms ModemManager.service
109ms systemd-logind.service
100ms systemd-timesyncd.service
  98ms systemd-modules-load.service
  97ms nmbd.service
  94ms e2scrub_reap.service
  94ms systemd-remount-fs.service
  91ms multipathd.service
  88ms thermald.service
  80ms rsyslog.service
  78ms snapd.apparmor.service
  71ms [email protected]
  69ms sys-fs-fuse-connections.mount
  69ms sys-kernel-config.mount
  67ms swap.img.swap
  63ms update-notifier-download.service
  61ms lvm2-pvscan@259:3.service
  56ms systemd-sysusers.service
  54ms systemd-networkd.service
  51ms systemd-journal-flush.service
  50ms apparmor.service
  49ms console-setup.service
  49ms systemd-timedated.service
  47ms systemd-random-seed.service
  44ms systemd-update-utmp.service
  44ms systemd-sysctl.service
  41ms grub-initrd-fallback.service
  40ms systemd-fsck@dev-disk-by\x2duuid-1327\x2dD196.service
  39ms proc-sys-fs-binfmt_misc.mount
  38ms run-rpc_pipefs.mount
  38ms systemd-fsck@dev-disk-by\x2duuid-cc0b2e29\x2d962a\x2d4fc3\x2daa10\x2d393>
  38ms systemd-udevd.service
  37ms plymouth-quit.service
  35ms plymouth-quit-wait.service
  27ms setvtrgb.service
  26ms systemd-backlight@backlight:acpi_video0.service
  25ms snapd.socket
  24ms rpcbind.service
  23ms snap-core20-2318.mount
  23ms systemd-backlight@backlight:acpi_video1.service
  23ms snap-lxd-29351.mount
  22ms boot.mount
  22ms snap-snapd-21759.mount
  16ms systemd-user-sessions.service
  16ms ssh.service
   8ms rpc-statd-notify.service
   6ms systemd-update-utmp-runlevel.service
   6ms boot-efi.mount
   5ms systemd-tmpfiles-setup-dev.service
   4ms avahi-daemon.service
   4ms [email protected]
  19us blk-availability.service
lines 68-90/90 (END)
cs@nuc7:~$ ^C

 

Code:

sudo systemd-analyze critical-chain
[sudo] password for cs:
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

└─multi-user.target @9.514s
  └─avahi-daemon.service @10.183s +4ms
    └─basic.target @8.957s
      └─sockets.target @8.952s
        └─snapd.socket @8.918s +25ms
          └─sysinit.target @8.823s
            └─cloud-init.service @8.455s +356ms
              └─systemd-networkd-wait-online.service @1.680s +6.771s
                └─systemd-networkd.service @1.621s +54ms
                  └─network-pre.target @1.617s
                    └─cloud-init-local.service @1.240s +373ms
                      └─systemd-remount-fs.service @330ms +94ms
                        └─systemd-journald.socket @183ms
                          └─-.mount @175ms
                            └─-.slice @175ms
cs@nuc7:~$

This is for 24.04 (and both are fresh installs).
 

Code:

sudo systemd-analyze blame
[sudo] password for cs:
8.190s nmbd.service
565ms systemd-networkd.service
523ms systemd-binfmt.service
481ms proc-sys-fs-binfmt_misc.mount
414ms run-rpc_pipefs.mount
402ms snapd.seeded.service
400ms rpcbind.service
399ms snapd.apparmor.service
388ms dev-mapper-ubuntu\x2d\x2dvg\x2dubuntu\x2d\x2dlv.device
352ms snapd.service
289ms apport.service
212ms e2scrub_reap.service
191ms lighttpd.service
155ms rsyslog.service
155ms secureboot-db.service
143ms polkit.service
131ms grub-common.service
119ms [email protected]
116ms apparmor.service
110ms systemd-udev-trigger.service
  98ms systemd-resolved.service
  95ms samba-ad-dc.service
  88ms dev-hugepages.mount
  86ms dev-mqueue.mount
  85ms sys-kernel-tracing.mount
  84ms sys-kernel-debug.mount
  78ms keyboard-setup.service
  77ms kmod-static-nodes.service
  74ms lvm2-monitor.service
  72ms [email protected]
  71ms systemd-journald.service
  71ms systemd-tmpfiles-setup.service
  69ms modprobe@dm_mod.service
  67ms [email protected]
  66ms ModemManager.service
  66ms smbd.service
  61ms thermald.service
  61ms systemd-logind.service
  60ms modprobe@efi_pstore.service
  55ms multipathd.service
  55ms [email protected]
  51ms systemd-timesyncd.service
  49ms console-setup.service
  49ms [email protected]
  48ms dbus.service
  47ms rpc-statd-notify.service
  46ms sysstat.service
  45ms finalrd.service
  42ms systemd-udevd.service
  42ms systemd-modules-load.service
  41ms plymouth-read-write.service
  41ms systemd-journal-flush.service
  37ms systemd-remount-fs.service
  36ms plymouth-quit-wait.service
  36ms grub-initrd-fallback.service
  34ms plymouth-quit.service
  31ms systemd-fsck@dev-disk-by\x2duuid-41ab4360\x2db9c9\x2d4db7\x2d9eed\x2d787>
  30ms swap.img.swap
  29ms sys-fs-fuse-connections.mount
  27ms sys-kernel-config.mount
  22ms boot.mount
  20ms systemd-fsck@dev-disk-by\x2duuid-9DDC\x2dAB5C.service
  19ms systemd-tmpfiles-setup-dev.service
  19ms systemd-tmpfiles-setup-dev-early.service
  19ms systemd-update-utmp.service
  18ms systemd-random-seed.service
  18ms ssh.service
  18ms systemd-user-sessions.service
  16ms systemd-sysctl.service
  13ms lxd-installer.socket
  12ms ufw.service
  12ms [email protected]
   8ms setvtrgb.service
   7ms boot-efi.mount
   4ms systemd-update-utmp-runlevel.service
   2ms avahi-daemon.service
   1ms snapd.socket
  66us blk-availability.service
lines 56-78/78 (END)
cs@nuc7:~$

Code:

sudo systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

└─multi-user.target @9.641s
  └─smbd.service @9.574s +66ms
    └─nmbd.service @1.374s +8.190s
      └─network-online.target @1.367s
        └─network.target @1.346s
          └─systemd-networkd.service @780ms +565ms
            └─network-pre.target @761ms
              └─ufw.service @745ms +12ms
                └─local-fs.target @679ms
                  └─boot-efi.mount @669ms +7ms
                    └─boot.mount @630ms +22ms
                      └─systemd-fsck@dev-disk-by\x2duuid-41ab4360\x2db9c9\x2d4d>
                        └─dev-disk-by\x2duuid-41ab4360\x2db9c9\x2d4db7\x2d9eed\>
lines 1-16/16 (END)

Far from an expert on this, but on 22.04
6.771s systemd-networkd-wait-online.service
54ms systemd-networkd.service

On 24.04
No systemd-networkd-wait-online.service ?
565ms systemd-networkd.service

[Primare11]

I have also tried now and the mounted folder does NOT remount after reboot of SnakeOil .
However if I shutdown SnakeOil and start it again then the mounted folder remounts .
I have also test to first do an reboot (= it does NOT remount) and then a shutdown and a restart (= it does remount). I hope this can give some clue what the problem is.

NAS setttings
----------------
Synology DS1512+ (DSM 6.2.4-25556 Update 8)

File Services / NFS
- Enable NFS: Yes
- Enable NFSv4.1 support: Yes
  - NFSv4 domain: "empty"

Shared Folder / NFS Permissons / NFS rule
- Hostname: "IP of SnakeOil"
- Privilege: Read only
- Squash: Mapp all users to admin
- Security: sys
- Enable asynchronous: Yes
- Allow connections from non-privileged ports (ports higher than 1024): No
- Allow users to access mounted subfolders: Yes
Mont path: /volume1/Media


SnakeOil settings
-----------------
Music Library / Mount Points Configuration:
- Media: "NAS IP":/volume1/Media/Musik
- Mount Point: NAS
- Media Type: NFS


Exact the same settings has work in previous versions of Snakeoil and I also use this in my Linux Mint fstab ("NAS IP":/volume1/Media/Musik /home/robban/Music/NAS.Music nfs defaults 0 0) without any problems for many years.

[skel]

Tried today the rc2 and there was no usb device detected. Don't know why. Aplay -l  sees no soundcards at all (since I deactivated the computers soundcard in the bios). Maybe not a problem of SO (but I remeber that it worked with SO 1.3 and Ubuntu 22.04). I even tried to load sound_usb_audio via modprobe. Any idea to this?

[Snoopy8]

I have also tried now and the mounted folder does NOT remount after reboot of SnakeOil .
However if I shutdown SnakeOil and start it again then the mounted folder remounts .
I have also test to first do an reboot (= it does NOT remount) and then a shutdown and a restart (= it does remount). I hope this can give some clue what the problem is.

NAS setttings
----------------
Synology DS1512+ (DSM 6.2.4-25556 Update 8)

File Services / NFS
- Enable NFS: Yes
- Enable NFSv4.1 support: Yes
  - NFSv4 domain: "empty"

Shared Folder / NFS Permissons / NFS rule
- Hostname: "IP of SnakeOil"
- Privilege: Read only
- Squash: Mapp all users to admin
- Security: sys
- Enable asynchronous: Yes
- Allow connections from non-privileged ports (ports higher than 1024): No
- Allow users to access mounted subfolders: Yes
Mont path: /volume1/Media


SnakeOil settings
-----------------
Music Library / Mount Points Configuration:
- Media: "NAS IP":/volume1/Media/Musik
- Mount Point: NAS
- Media Type: NFS


Exact the same settings has work in previous versions of Snakeoil and I also use this in my Linux Mint fstab ("NAS IP":/volume1/Media/Musik /home/robban/Music/NAS.Music nfs defaults 0 0) without any problems for many years.

Thank you for testing and listing your setup.  I have  DS923+ running latest DSM 7.2.2-72806 Update 2.

Unfortunately, my NFS folders will not remount by themselves.  Tried reboot, shutdown (& power up button, take out power chord).  Have even set DSM to use NFSv3.

[agent_kith]

Far from an expert on this, but on 22.04
6.771s systemd-networkd-wait-online.service
54ms systemd-networkd.service

On 24.04
No systemd-networkd-wait-online.service ?
565ms systemd-networkd.service

Gawd I really hate systemd sometimes. Looks like on 24.04 it's now network-online.service. Which should work.

I wonder, what happens if you enable "allow > 1024" in your synology settings? Can you try that and see if it works? Another reason why it didn't work for you could be because of this. NFS requires a service called port-mapper which may not be up, however I also added a dependency nfs-client which should remedy that.

I fixed my NFS port mapper ports (not dynamic) because I have setup firewalls, maybe this is why it works for me.

Regardless I can add code to fix this and it should work outside systemd.

[agent_kith]

I have also tried now and the mounted folder does NOT remount after reboot of SnakeOil .
However if I shutdown SnakeOil and start it again then the mounted folder remounts .
I have also test to first do an reboot (= it does NOT remount) and then a shutdown and a restart (= it does remount). I hope this can give some clue what the problem is.

I wouldn't call myself a Linux expert, even though I have used Linux for well over 2 decades. And yet I have no idea why it's dong this. Cold boot vs warm boot differences usually show up with hardware, but I would consider networking mounting software related?

Let me know if you guys can find out anything on this as my googling turns up nothing so far.. (I don't have ChatGPT).

[agent_kith]

Tried today the rc2 and there was no usb device detected. Don't know why. Aplay -l  sees no soundcards at all (since I deactivated the computers soundcard in the bios). Maybe not a problem of SO (but I remeber that it worked with SO 1.3 and Ubuntu 22.04). I even tried to load sound_usb_audio via modprobe. Any idea to this?

You'll need to add "sudo" in front as your normal user account may not have access to the audio device groups. try

"sudo aplay -l" and see what devices are available.

Failing that, you can run "sudo dmesg" to see if there's any USB audio devices listed.

This is usually OS related, but can't confirm for certain right now as 1.4.0 is kind of a big change so somethings may be missed. Please let me know how you go with the above two commands. Thanks.

[Snoopy8]

I wonder, what happens if you enable "allow > 1024" in your synology settings? Can you try that and see if it works?

I did try it but drives do not reload.

Another reason why it didn't work for you could be because of this. NFS requires a service called port-mapper which may not be up, however I also added a dependency nfs-client which should remedy that.

I fixed my NFS port mapper ports (not dynamic) because I have setup firewalls, maybe this is why it works for me.

I did look at port mapper, but not sure I got that working?

Regardless I can add code to fix this and it should work outside systemd.

Thank you