1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL.TESTIN

  • don't boot: last line autofs4 module inserted

    From Paul Dufresne@21:1/5 to All on Wed Dec 18 20:30:01 2024
    Previously today I was fighting to upgrade: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090715

    So after the 3 months of not using Debian Testing, I finally succeeded to upgrade.
    At first I did just apt upgrade.

    After that, I began to not be able to boot with most kernels except one that I compiled myself long ago (using now):
    paul@albukerk:~$ cat /proc/version
    Linux version 4.19.302paul45 (paul@albukerk) (gcc version 13.2.0 (Debian 13.2.0-7)) #1 SMP Tue Dec 19 05:04:05 EST 2023
    paul@albukerk:~$

    As it was not booting: autofs4 module inserted being last line....
    I finally did a apt full-upgrade

    But did not fix the problem...

    Other error are shown but believe not to be relevant:
    tomoyo-init not found
    selinux defaut.33 file not found...

    But as I saw those for this working 4.19 kernel.... I think they are not the real cause.

    Not subscribe here.... but seems relevant place to post about this.

    Need to search what is autofs4 module... as I don't really knows.

    Found similar problem on the net as: https://www.linuxquestions.org/questions/linux-general-1/boot-problem-failed-to-insert-module-'autofs4'-4175485121/

    Maybe this helps:
    root@albukerk:/home/paul# lsblk -f
    NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
    sda ├─sda1
    │ │ LVM2_m LVM2 NAtJ8b-iMoM-PIOI-YIQc-xFRU-nvxd-VyxJZC
    │ ├─main-myswap
    │ │ swap 1 5d8325c5-27b7-4c42-8c73-ac2dc5936b4b [SWAP]
    │ └─main-myroot
    │ ext4 1.0 a9d23244-eea3-4239-b6d4-43b6e9339321 111,5G 65% /
    ├─sda2
    │ vfat FAT32 8A31-4125 947,7M 0% /boot/efi
    ├─sda3
    │ │ LVM2_m LVM2 jz04eq-vTHC-dMd5-vYmr-C8A2-nkb8-e1PZB0
    │ ├─main-myswap
    │ │ swap 1 5d8325c5-27b7-4c42-8c73-ac2dc5936b4b [SWAP]
    │ └─main-myroot
    │ ext4 1.0 a9d23244-eea3-4239-b6d4-43b6e9339321 111,5G 65% /
    └─sda4
    │ LVM2_m LVM2 p20fYY-MaRl-W0kk-3GQe-Sqsn-yKqT-0znd8X
    └─main-myroot
    ext4 1.0 a9d23244-eea3-4239-b6d4-43b6e9339321 111,5G 65% / sr0 root@albukerk:/home/paul#

    I check a bit journalctl -b.... but I don't find the errors mentioned... maybe boot messages
    are before journalctl messages begin to be recorded.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Dufresne@21:1/5 to All on Wed Dec 18 20:40:02 2024
    I have been able to boot latest kernel by modifying (with E key) the boot entry:

    replaced:

    set root='lvmid/sMjw7e-rWxK-OkJd-RNtY-4599-Hz1q-3DtcNn/nbU01K-S2Qi-z01i-W3xO-s27B-UrZD-Fs8YLE'

    by

    set root=/dev/mapper/main-myroot



    So now:

    paul@albukerk:/boot/grub$ cat /proc/version

    Linux version 6.11.10-amd64 (mailto:debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-8) 14.2.0, GNU ld (GNU Binutils for Debian) 2.43.1) #1 SMP PREEMPT_DYNAMIC Debian 6.11.10-1 (2024-11-23)

    paul@albukerk:/boot/grub$



    I am not much familiar with lvmid...

    https://unix.stackexchange.com/questions/298068/system-unbootable-grub-error-disk-lvmid-not-found seems to suggest:

    paul@albukerk:/boot/grub$ ls -l /dev/disk/by-uuid

    total 0

    lrwxrwxrwx 1 root root 10 18 déc 14:20 5d8325c5-27b7-4c42-8c73-ac2dc5936b4b -> ../../dm-0

    lrwxrwxrwx 1 root root 10 18 déc 14:20 8A31-4125 -> ../../sda2

    lrwxrwxrwx 1 root root 10 18 déc 14:20 a9d23244-eea3-4239-b6d4-43b6e9339321 -> ../../dm-1

    paul@albukerk:/boot/grub$



    vgs -v

      VG   Attr   Ext   #PV #LV #SN VSize   VFree VG UUID                                VProfile

      main wz--n- 4,00m   3   2   0 437,01g    0  sMjw7e-rWxK-OkJd-RNtY-4599-Hz1q-3DtcNn        





    Guess I would need to replace that string... still not knowing exactly where. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10pt;"><div>I have been
    able to boot latest kernel by modifying (with E key) the boot entry:<br></div><div>replaced:<br></div><div>set root='lvmid/sMjw7e-rWxK-OkJd-RNtY-4599-Hz1q-3DtcNn/nbU01K-S2Qi-z01i-W3xO-s27B-UrZD-Fs8YLE'<br></div><div>by<br></div><div>set root=/dev/mapper/
    main-myroot<br></div><div><br></div><div>So now:<br></div><div>paul@albukerk:/boot/grub$ cat /proc/version<br></div><div>Linux version 6.11.10-amd64 (<a target="_blank" href="mailto:debian-kernel@lists.debian.org">debian-kernel@lists.debian.org</a>) (x86_
    64-linux-gnu-gcc-14 (Debian 14.2.0-8) 14.2.0, GNU ld (GNU Binutils for Debian) 2.43.1) #1 SMP PREEMPT_DYNAMIC Debian 6.11.10-1 (2024-11-23)<br></div><div>paul@albukerk:/boot/grub$<br></div><div><br></div><div>I am not much familiar with lvmid...<br></div>
    <div><a target="_blank" href="https://unix.stackexchange.com/questions/298068/system-unbootable-grub-error-disk-lvmid-not-found">https://unix.stackexchange.com/questions/298068/system-unbootable-grub-error-disk-lvmid-not-found</a> seems to suggest:<br></
    <div>paul@albukerk:/boot/grub$ ls -l /dev/disk/by-uuid<br></div><div>total 0<br></div><div>lrwxrwxrwx 1 root root 10 18 déc 14:20 5d8325c5-27b7-4c42-8c73-ac2dc5936b4b -&gt; ../../dm-0<br></div><div>lrwxrwxrwx 1 root root 10 18 déc 14:20 8A31-4125 -&
    gt; ../../sda2<br></div><div>lrwxrwxrwx 1 root root 10 18 déc 14:20 a9d23244-eea3-4239-b6d4-43b6e9339321 -&gt; ../../dm-1<br></div><div>paul@albukerk:/boot/grub$<br></div><div><br></div><div>lvm&gt; vgs -v<br></div><div>&nbsp; VG&nbsp;&nbsp; Attr&nbsp;&
    nbsp; Ext&nbsp;&nbsp; #PV #LV #SN VSize&nbsp;&nbsp; VFree VG UUID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    VProfile<br></div><div>&nbsp; main wz--n- 4,00m&nbsp;&nbsp; 3&nbsp;&nbsp; 2&nbsp;&nbsp; 0 437,01g&nbsp;&nbsp;&nbsp; 0&nbsp; sMjw7e-rWxK-OkJd-RNtY-4599-Hz1q-3DtcNn&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br></div><div>lvm&gt;<br></div><div><br></
    <div>Guess I would need to replace that string... still not knowing exactly where.<br></div></div><br></body></html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Dufresne@21:1/5 to All on Wed Dec 18 21:20:01 2024
    I did what the file says not to do: edit /boot/grub/grub.cfg file...
    I added the line:
    set root=/dev/mapper/main-myroot
    in Warning... some lines exceed the width and are truncated:
    ### BEGIN /etc/grub.d/10_linux ###
    function gfxmode {
    set gfxpayload="${1}"
    }
    set linux_gfx_mode=
    export linux_gfx_mode
    menuentry 'Debian GNU/Linux GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-a9d23244-eea3-4>
    load_video
    insmod gzio
    if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
    insmod part_gpt
    insmod part_gpt
    insmod part_gpt
    insmod lvm
    insmod ext2
    set root='lvmid/sMjw7e-rWxK-OkJd-RNtY-4599-Hz1q-3DtcNn/nbU01K-S2Qi-z01i-W3xO-s27B-UrZD-Fs8YLE'
    set root=/dev/mapper/main-myroot
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint='lvmid/sMjw7e-rWxK-OkJd-RNtY-4599-Hz1q-3DtcNn/nbU01K-S2Qi-z01i-W3xO-s27B-UrZD-Fs8YLE' a9d2>
    else
    search --no-floppy --fs-uuid --set=root a9d23244-eea3-4239-b6d4-43b6e9339321
    fi
    echo 'Loading Linux 6.11.10-amd64 ...'
    linux /boot/vmlinuz-6.11.10-amd64 root=/dev/mapper/main-myroot ro pcie_aspm=off nouveau.debug=info nouveau.noaccel=0 drm.debug=0 log_buf_l
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-6.11.10-amd64
    }

    So now it boot by default correctly...
    until a new kernel will be installed or that I do update-grub.

    Would like to know how to improve this.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)