On 28/03/2025 01:28, Ben Hutchings wrote:

Hi Ben,

Thanks for your time and support.

No module loaded at all.

Indeed.  But the root device is there anyway, presumably because the
nvme driver is built-in.

I remember moving to builtin as a first try to fix the error. I can switch back but anyway the module will be loaded so...

So I think the "No such device" error is
actually because the *filesystem* module fails to load.

Or maybe the /dev is not correctly created/populated by kernel...
The no such device in the picture in the previous mail sound more like an incorrect/impossible dev access (but I know mount error can be esoteric).


So I have more questions:

- Your kernel config has ext4 enabled as a module.  Is that the root
   filesystem type?

Yes. Here are the complete info for the disk layout and file systems

mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=7870260k,nr_inodes=1967565,mode=755,inode64) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1576148k,mode=755,inode64) /dev/nvme0n1p5 on / type ext4 (rw,noatime,nodiratime,discard,errors=remount-ro) <========== securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=4388)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,nosuid,nodev,relatime,pagesize=2M) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) tmpfs on /run/credentials/systemd-journald.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) systemd-1 on /boot/efi type autofs (rw,relatime,fd=60,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=7528) systemd-1 on /multimedia type autofs (rw,relatime,fd=61,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=7530) tmpfs on /run/credentials/systemd-networkd.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
/dev/nvme0n1p6 on /var type ext4 (rw,noatime,nodiratime,discard)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/nvme0n1p7 on /usr/local type ext4 (rw,noatime,nodiratime,discard)
/dev/nvme0n1p9 on /tmp type ext4 (rw,noatime,nodiratime,discard)
/dev/nvme0n1p10 on /home type ext4 (rw,noatime,nodiratime,discard)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/sda1 on /multimedia type ntfs3 (rw,noatime,nodiratime,uid=1000,gid=1000,discard,iocharset=utf8,x-systemd.automount) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1576144k,nr_inodes=394036,mode=700,uid=1000,gid=1000,inode64) portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro,x-systemd.automount) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=1576144k,nr_inodes=394036,mode=700,inode64)

sfdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: LITEON CL1-8D512
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx <=edited

Device              Start       End   Sectors   Size Type
/dev/nvme0n1p1       2048    616447    614400   300M EFI System
/dev/nvme0n1p2     616448    878591    262144   128M Microsoft reserved
/dev/nvme0n1p3     878592 326473759 325595168 155.3G Microsoft basic data
/dev/nvme0n1p4 326475776 328153087 1677312 819M Windows recovery environment
/dev/nvme0n1p5  328157184 406282239  78125056  37.3G Linux filesystem
/dev/nvme0n1p6  406282240 455110655  48828416  23.3G Linux filesystem
/dev/nvme0n1p7  455110656 474642431  19531776   9.3G Linux filesystem
/dev/nvme0n1p8  474642432 494174207  19531776   9.3G Linux swap
/dev/nvme0n1p9  494174208 498079743   3905536   1.9G Linux filesystem
/dev/nvme0n1p10 498079744 791048191 292968448 139.7G Linux filesystem
/dev/nvme0n1p11 791048192 893448191 102400000  48.8G Microsoft basic data
root@pink-floyd3:~#


- What does the command "/usr/lib/klibc/bin/fstype /dev/nvme0n1p5"
   print?

/usr/lib/klibc/bin/fstype /dev/nvme0n1p5
FSTYPE=ext4
FSSIZE=40000028672

- Using the bad initramfs, in the rescue shell:

Will do later. I need to rebuild again the kernel.

   - What does "echo $ROOTFSTYPE" print?
   - What does "cat /proc/filesystems" print?
   - What does "modprobe fs-ext4" print, if anything?

Is this a particular syntax : I have ext4 module not fs-ext4?

lsmod | grep ext4
ext4                 1142784  5
crc16                  12288  3 bluetooth,amdgpu,ext4
mbcache                16384  1 ext4
jbd2                  200704  1 ext4
root@pink-floyd3:~# lsmod | grep fs
ntfs3                 335872  1
configfs               69632  1
efivarfs               28672  1
autofs4                57344  4
root@pink-floyd3:~#


   - If you then exit the rescue shell, does the boot process succeed?

No. I get first a long list of command and if I exit again a kernel panic from memory.

More latter on.

--
Eric Valette

Reply via email to