Dev1 Galaxy Forum / [SOLVED] No automount after update to Excalibur

Re: [SOLVED] No automount after update to Excalibur

dummy@example.com (stargate-sg1-cheyenne-mtn) — Tue, 09 Sep 2025 11:13:25 +0000

^^^this

Re: [SOLVED] No automount after update to Excalibur

dummy@example.com (Altoid) — Mon, 08 Sep 2025 21:36:14 +0000

Hello:

Roberto wrote:

... shares that I entered in fstab, are no longer automatically mounted at system startup.

I see that you have marked the issue you posted about as [SOLVED] but have posted nothing on the cause / solution.

I am sure that the members of the forum who came to your aid as well as those who may eventually come across the same problem would like to know about how you solved it.

Best,

Re: [SOLVED] No automount after update to Excalibur

dummy@example.com (rolfie) — Sun, 07 Sep 2025 17:24:28 +0000

I think so.

Re: [SOLVED] No automount after update to Excalibur

dummy@example.com (greenjeans) — Sun, 07 Sep 2025 17:16:42 +0000

There will be some complaints within the upgrade process if that wasn't done.

I thought as much, but would it error-out the process?

Re: [SOLVED] No automount after update to Excalibur

dummy@example.com (rolfie) — Sun, 07 Sep 2025 17:08:11 +0000

... you did install usrmerge before updating ...

There will be some complaints within the upgrade process if that wasn't done.

Re: [SOLVED] No automount after update to Excalibur

dummy@example.com (greenjeans) — Sun, 07 Sep 2025 17:00:36 +0000

To update, I changed the entries daedalus to excalibur in /etc/apt/sources.list.

I'm sure you probably did this, but just to rule out the small stuff, you did install usrmerge before updating yes?

I actually don't know what would happen if you had not, likely wouldn't have succeeded in updating, but I always like to start with the simple stuff when troubleshooting.

Re: [SOLVED] No automount after update to Excalibur

dummy@example.com (fsmithred) — Sun, 07 Sep 2025 13:04:59 +0000

What kind of shares are they? NFS, Samba, local partitions or something else?

What's in /etc/fstab?

Also please post the output of blkid and maybe lsblk. Maybe other stuff, too after we narrow it down.

Re: [SOLVED] No automount after update to Excalibur

dummy@example.com (Altoid) — Sun, 07 Sep 2025 11:43:07 +0000

Hello:

Roberto wrote:

Thank you ...

You're welcome.

Roberto wrote:

... already thought that it was due to the project status.
... might have made a mistake.

Can happen, but provided you followed instructions, it should have been more or less straightforward, albeit keeping in mind that it is still in-development.

I want my WS to be stable and reliable above all things, so I stay away from dist-upgrades for as long as I can.
ie: only after all wrinkles have been straightened out and even then after careful consideration.

This Sun U24 WS is ca. 2007 and my Devuan system started off as Jesse in 2017, upgraded only as necessary.
Excalibur is a threshold I may not cross, Daedalus is already fat enough.
Jury is still out on that and what to do.

Roberto wrote:

... see if I can find the error log to send to the developers.

Please do, Devuan maintainers are understaffed and overworked.
They need all the help we can give them.

The dmesg printout will most probably give you the first clues, there should be something pointing to your shares not being found or something such.

If not, it could be because the system is not looking for them so that could/would be a config issue.

eg: this is a sample of my dmesg printout on boot:

$ sudo dmesg | grep mounted
[   24.743697] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Quota mode: none.
[   26.341730] EXT4-fs (sdb1): re-mounted. Quota mode: none.
[   27.749364] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Quota mode: none.
[   27.751511] EXT4-fs (sdb6): mounted filesystem with ordered data mode. Quota mode: none.
[   27.775098] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Quota mode: none.
[   27.793504] EXT4-fs (sdf1): mounted filesystem with ordered data mode. Quota mode: none.
[   27.834654] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none.
[   27.882843] EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none.
$

Your box/laptop is undoubtedly mounting the file system in the main drive and that will show up in the printout.
I expect that your shares not being mounted or not found should also show up.

Just a guess.

Best,

Re: [SOLVED] No automount after update to Excalibur

dummy@example.com (igorzwx) — Sun, 07 Sep 2025 10:57:31 +0000

Have you tried to mount them manually?

Re: [SOLVED] No automount after update to Excalibur

dummy@example.com (Roberto) — Sun, 07 Sep 2025 10:41:34 +0000

Thank you very much for your reply.

I already thought that it was due to the project status. It was just a question of whether I might have made a mistake.

Then I will be patient and see if I can find the error log to send to the developers.

Re: [SOLVED] No automount after update to Excalibur

dummy@example.com (Altoid) — Sun, 07 Sep 2025 10:34:07 +0000

Hello:

Roberto wrote:

... any idea why my previously successful entries in fstab are no longer mounting ...

It is (most probably) due to the fact that Devuan Excalibur is still in development.
ie: testing / not released yet

From https://www.devuan.org/os/releases

devuan.org/os/releases wrote:

In development
Devuan release Suite Released Planet nr. Debian release Status
Excalibur testing Not released 9499 Trixie Maintained

To quote the same source:

◦ testing is where the next stable suite is developed. Software is usually more up-to-date but there may still be issues.
testing becomes stable "when it is ready".

Your shares not mounting properly after upgrading to Excalibur is most probably one of many issues.
Or maybe not.

That said, you may want to consider submitting a bug report.

The information you can relay should be very useful to our developers; they will be able to dilucidate its origin.
ie: whether it is related to the upgrade process, to a specific package or something in your system's configuration.

Best,

[SOLVED] No automount after update to Excalibur

dummy@example.com (Roberto) — Sun, 07 Sep 2025 09:59:29 +0000

After successfully updating Devuan Daedalus to Excalibur, my shares that I entered in fstab, are no longer automatically mounted at system startup.
To update, I changed the entries daedalus to excalibur in /etc/apt/sources.list.

Here is my system:

System:
  Kernel: 6.12.43+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
  Desktop: Cinnamon v: 6.4.10 Distro: Devuan GNU/Linux 6 (excalibur/ceres)
Machine:
  Type: Laptop System: Dell product: Latitude 7490 v: N/A
    serial: 
  Mobo: Dell model: 0KP0FT v: A00 serial:  UEFI: Dell
    v: 1.41.0 date: 11/06/2024
Battery:
  ID-1: BAT0 charge: 12.0 Wh (34.2%) condition: 35.1/60.0 Wh (58.6%)
    volts: 8.0 min: 7.6 model: SMP DELL DM3WC64 status: charging
CPU:
  Info: quad core model: Intel Core i5-8350U bits: 64 type: MT MCP
    arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 800 min/max: 400/3600 cores: 1: 800 2: 800 3: 800 4: 800
    5: 800 6: 800 7: 800 8: 800 bogomips: 30399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel
    arch: Gen-9.5 bus-ID: 00:02.0
  Device-2: Sunplus Innovation Integrated_Webcam_HD driver: uvcvideo
    type: USB bus-ID: 1-5:2
  Display: x11 server: X.Org v: 21.1.16 driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: iris,swrast platforms:
    active: gbm,x11,surfaceless,device inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.7-2 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
  Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3
  API: ALSA v: k6.12.43+deb13-amd64 status: kernel-api
  Server-1: PipeWire v: 1.4.2 status: off
  Server-2: PulseAudio v: 17.0 status: active
Network:
  Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6
  IF: eth0 state: down mac: 
  Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel
    bus-ID: 02:00.0
  IF: wlan0 state: up mac: 
  IP v4:  type: dynamic noprefixroute scope: global
  IP v6:  type: temporary dynamic scope: global
  IP v6:  type: dynamic mngtmpaddr noprefixroute scope: global
  IP v6:  type: temporary dynamic scope: global
  IP v6:  type: dynamic mngtmpaddr noprefixroute scope: global
  IP v6:  type: noprefixroute scope: link
  IF-ID-1: virbr0 state: down mac: 
  IP v4:  scope: global
  WAN IP: 
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
    bus-ID: 1-7:3
  Report: hciconfig ID: hci0 rfk-id: 3 state: up address:  bt-v: 4.2
    lmp-v: 8
Drives:
  Local Storage: total: 471.44 GiB used: 237.35 GiB (50.3%)
  ID-1: /dev/sda vendor: SK Hynix model: SC401 SATA 256GB size: 238.47 GiB
  ID-2: /dev/sdb vendor: SanDisk model: USB 3.2Gen1 size: 232.97 GiB
    type: USB
Partition:
  ID-1: / size: 100.28 GiB used: 14.11 GiB (14.1%) fs: ext4 dev: /dev/sda3
  ID-2: /boot/efi size: 511 MiB used: 38 MiB (7.4%) fs: vfat dev: /dev/sda1
  ID-3: /home size: 125.01 GiB used: 3.16 GiB (2.5%) fs: ext4 dev: /dev/sda4
Swap:
  ID-1: swap-1 type: partition size: 7.45 GiB used: 0 KiB (0.0%)
    dev: /dev/sda2
Sensors:
  System Temperatures: cpu: 52.0 C mobo: 48.0 C
  Fan Speeds (rpm): cpu: 0
Info:
  Memory: total: 16 GiB available: 15.5 GiB used: 2.25 GiB (14.5%)
  Processes: 273 Uptime: 10m Init: SysVinit runlevel: 2
  Packages: 2727 Compilers: gcc: 14.2.0 Shell: Bash v: 5.2.37 inxi: 3.3.38

Does anyone have any idea why my previously successful entries in fstab are no longer mounting my shares?

Thanks in advance.