Results 1 to 6 of 6

Thread: No automount on boot with kernel 5.4

  1. #1
    Join Date
    Dec 2016
    Location
    Somewhere in Italy
    Posts
    62

    Default No automount on boot with kernel 5.4

    Hi,
    I've 2 PCs with the same hw and the same configuration (expect for tumbleweed snapshot).
    On PC1 I have Tumbleweed with kernel 5.3 : automount on boot of some partitions work.
    On PC2 I have Tumbleweed with kernel 5.4 : automount doesn't work.

    PC1 :
    Code:
    output of lsblk
    NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
    nvme0n1     259:0    0  477G  0 disk 
    ├─nvme0n1p1 259:1    0  260M  0 part /boot/efi
    ├─nvme0n1p2 259:2    0   40G  0 part 
    ├─nvme0n1p3 259:3    0   40G  0 part /
    ├─nvme0n1p4 259:4    0   20G  0 part [SWAP]
    ├─nvme0n1p5 259:5    0  300G  0 part /VM
    ├─nvme0n1p6 259:6    0   50G  0 part /DatiLinux
    └─nvme0n1p7 259:7    0 26,7G  0 part /Scambio
    
    output of journalctl -b | grep mount
    gen 13 18:10:41 HPTIZY systemd[1]: Condition check resulted in dracut pre-mount hook being skipped.
    gen 13 18:10:41 HPTIZY kernel: EXT4-fs (nvme0n1p3): mounted filesystem with ordered data mode. Opts: (null)
    gen 13 18:10:41 HPTIZY systemd[1]: Condition check resulted in dracut mount hook being skipped.
    gen 13 17:10:48 HPTIZY kernel: EXT4-fs (nvme0n1p3): re-mounted. Opts: (null)
    gen 13 17:10:48 HPTIZY kernel: EXT4-fs (nvme0n1p7): mounted filesystem with ordered data mode. Opts: data=ordered
    gen 13 17:10:48 HPTIZY kernel: EXT4-fs (nvme0n1p5): mounted filesystem with ordered data mode. Opts: data=ordered
    gen 13 17:10:48 HPTIZY kernel: EXT4-fs (nvme0n1p6): mounted filesystem with ordered data mode. Opts: data=ordered
    gen 13 17:11:03 HPTIZY plasmashell[2013]: org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/libkcm_device_automounter.so"
    PC2:
    Code:
    output of lsblk
    NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
    nvme0n1     259:0    0  477G  0 disk 
    ├─nvme0n1p1 259:1    0  260M  0 part 
    ├─nvme0n1p2 259:2    0   40G  0 part 
    ├─nvme0n1p3 259:3    0   40G  0 part /
    ├─nvme0n1p4 259:4    0   20G  0 part [SWAP]
    ├─nvme0n1p5 259:5    0  300G  0 part 
    ├─nvme0n1p6 259:6    0   50G  0 part 
    └─nvme0n1p7 259:7    0 26,7G  0 part 
    
    output of journalctl -b | grep mount
    gen 13 18:27:53 HPELTMAX systemd[1]: Condition check resulted in dracut pre-mount hook being skipped.
    gen 13 18:27:53 HPELTMAX kernel: EXT4-fs (nvme0n1p3): mounted filesystem with ordered data mode. Opts: (null)
    gen 13 18:27:53 HPELTMAX systemd[1]: Condition check resulted in dracut mount hook being skipped.
    gen 13 18:27:59 HPELTMAX kernel: EXT4-fs (nvme0n1p3): re-mounted. Opts: (null)
    gen 13 18:27:59 HPELTMAX kernel: EXT4-fs (nvme0n1p7): mounted filesystem with ordered data mode. Opts: data=ordered
    gen 13 18:27:59 HPELTMAX kernel: EXT4-fs (nvme0n1p6): mounted filesystem with ordered data mode. Opts: data=ordered
    gen 13 18:27:59 HPELTMAX kernel: EXT4-fs (nvme0n1p5): mounted filesystem with ordered data mode. Opts: data=ordered
    gen 13 18:28:00 HPELTMAX systemd[1]: Unmounting /DatiLinux...
    gen 13 18:28:00 HPELTMAX systemd[1]: Unmounting /Scambio...
    gen 13 18:28:00 HPELTMAX systemd[1]: Unmounting /VM...
    gen 13 18:28:00 HPELTMAX systemd[1]: Unmounting /boot/efi...
    gen 13 18:28:00 HPELTMAX systemd[1]: DatiLinux.mount: Succeeded.
    gen 13 18:28:00 HPELTMAX systemd[1]: Unmounted /DatiLinux.
    gen 13 18:28:00 HPELTMAX systemd[1]: Scambio.mount: Succeeded.
    gen 13 18:28:00 HPELTMAX systemd[1]: Unmounted /Scambio.
    gen 13 18:28:00 HPELTMAX systemd[1]: boot-efi.mount: Succeeded.
    gen 13 18:28:00 HPELTMAX systemd[1]: Unmounted /boot/efi.
    gen 13 18:28:00 HPELTMAX systemd[1]: VM.mount: Succeeded.
    gen 13 18:28:00 HPELTMAX systemd[1]: Unmounted /VM.
    gen 13 18:28:15 HPELTMAX plasmashell[1981]: org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/libkcm_device_automounter.so"
    As you can see on PC2 partitions /DatiLinux, /Scambio, /VM & /boot/efi are mounted, unmounted, mounted & unmounted .....

    Code:
    Output on both PCs of fstab (the files are exatly the same except for UUID
    UUID=e1c59715-af0e-41ef-9176-ee236cc2e9b1    swap        swap   defaults                 0  0
    UUID=daf40bed-d6f1-429d-8cbd-0d345f61b41a    /           ext4   defaults                 0  1
    UUID=70A5-3994                                                /boot/efi   vfat   defaults                 0  0
    UUID=36a03623-e135-404c-b8a7-a3928d95acea  /Scambio    ext4   data=ordered             0  2
    UUID=522e3334-6d7a-442e-b20e-8b49da69e638  /VM         ext4   data=ordered             0  2
    tmpfs                                                                 /tmp        tmpfs  rw,nodev,nosuid,size=2G  0  0
    UUID=f51ffdb8-67a2-4b02-87dd-27bc0d1b3bb6   /DatiLinux  ext4   data=ordered             0  2
    What do you suggest to check?

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,780

    Default Re: No automount on boot with kernel 5.4

    There are more threads about file systems that mount at boot (because they are configured for that in /etc/fstab and are then immediatly unmounted again. A
    Code:
    mount -a
    (or s specific mount of such a fs) will cure it for the rest of the session (but that is of course only a by-pass).
    I guess this is another emanation of this.


    BTW, you seem to call that the mounting of file systems done on boot because they are configured for that in /etc/fstab "automounting". Please do not.

    Automounting is mounting done at request (by some process trying to access something inside the yet unmounted file system). See
    Code:
    man automount
    Nowadays this can also be done using systemd. See https://wiki.archlinux.org/index.php...t_with_systemd
    Henk van Velden

  3. #3
    Join Date
    Dec 2016
    Location
    Somewhere in Italy
    Posts
    62

    Default Re: No mount on boot with kernel 5.4

    Quote Originally Posted by hcvv View Post
    ... BTW, you seem to call that the mounting of file systems done on boot because they are configured for that in /etc/fstab "automounting". Please do not....
    I learnt something new, thanks for that Henke.
    I don't need 'automount' simply I need mount at boot time of what is listed fstab (in the same way as happen on Leap & Tumbleweed with kernel 5.3).

  4. #4
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,780

    Default Re: No mount on boot with kernel 5.4

    Quote Originally Posted by MaxRiservo View Post
    I learnt something new, thanks for that Henke.
    I don't need 'automount' simply I need mount at boot time of what is listed fstab (in the same way as happen on Leap & Tumbleweed with kernel 5.3).
    And that worked in Unix/Linux for already at least 40 years .

    So there is something wrong. You may try to find the other threads to see if a bug report is attached to one of those.
    Henk van Velden

  5. #5
    Join Date
    Dec 2016
    Location
    Somewhere in Italy
    Posts
    62

    Default Re: No mount on boot with kernel 5.4

    I switched on indicted PC and this boot it mounted as expected all partitions .... so it's a very random issue.
    In the meanwhile I've found also this https://forums.opensuse.org/showthre...ght=mount+boot and it seems a known bug ....

  6. #6
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,780

    Default Re: No automount on boot with kernel 5.4

    Yes, that is one of them. You can now read the bug report and see if it fits your problem. You could also add to the report if you have ne information that might help in solving it.

    You can also subscribe t the bug report so you will get an e-mail when things happen tehere.
    Henk van Velden

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •