Recently have been experiencing this error after each restart. It takes 3-4 reboots just to get to the system. Logs (fstab and inxi): https://0x0.st/HiLv.txt
The error itself:
you have what appears to be a corrupt system. It tells you that ext4 is unknown file type. you could have a corrupt file system or you can have a harddrive that is failing. When did this first happen? Was it after an update did you install a program then this happended. We can sit and guess all day. You should post the log files. explain to us what you were doing when this first started. since ext4 is showing as unknown I would say that you lost / corrupted your filesystem
i would like to get the full boot log to have view?
but do not post it here send me in PM… it can include some persional data like IP and stuff…
journalctl -b -0 | eos-sendlog
Do you have multiple Linux installs? Did you modify the bootloader at any point? unknown filesystem type: ext4 is caused by attempting to mount the wrong partition in my opinion, not a hardware failure.
Send the output of these:
sudo blkid
sudo cat /etc/default/grub # if you are using GRUB, I don't recall the file path for systemd-boot
systemd-boot does not have any advanced config file… its mainly /etc/kernel/cmdline
and this looks fine it the default with resume uuid added…
No, I dual boot the endeavor with Windows 11, but I’ve experienced that even before (clean Cassini Neo install) and I haven’t changed default config files
ĐĽĐ°Ń€ 11 13:35:54 hly-w19r kernel: EXT4-fs (nvme0n1p7): mounted filesystem 6cb-XXX with ordered data mode. Quota mode: none.
in this case it loads ext4 just fine … boot journal do not show any issue related…
yes i do not think this is hardware failing…
But could be the ESP is corruüted or kernel images having a brick falling off…
I would go to first check ESP partition (EFI fat32) and rebuild kernel images:
sudo dosfsck /dev/sdxN
sudo reinstall-kernels
do not post UUIDS not that bad but you should not post any unifique data …
i see 2 fat32 partitions…
/dev/nvme0n1p5
/dev/nvme0n1p1
so your fstab would tell wich one you are using for Linux…
what happens?
I have run the first command, but the second cannot be found by sudo [ximierr@hly-w19r ~]$ sudo reinstall-kernels [sudo] password for ximierr: sudo: reinstall-kernels: command not found
you do use grub maybe?
Yes, I do
so run sudo dracut-rebuild
was it showing any thing fixing or only that backup warning?
Yes, it was showing that there is dirty bit and the fs haven’t been unmounted properly
Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
[12?q]?
When I ran the kernel rebuild some commands haven’t been found, so after the reboot error reappeared.
dracut: dracut module 'dash' will not be installed, because command 'dash' could not be found!
dracut: dracut module 'mksh' will not be installed, because command 'mksh' could not be found!
dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!
dracut: dracut module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found!
dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found!
dracut: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found!
dracut: dracut module 'dmraid' will not be installed, because command 'kpartx' could not be found!
dracut: dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
dracut: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'dcbtool' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'fipvlan' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'lldpad' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'fcoemon' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'fcoeadm' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found!
dracut: dracut module 'nbd' will not be installed, because command 'nbd-client' could not be found!
dracut: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found!
dracut: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found!
dracut: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found!
dracut: memstrack is not available
dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng
dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found!
dracut: dracut module 'squash' will not be installed, because command 'unsquashfs' could not be found!
“will not be installed” output is only warnings no issue it is only the process on checking what options/modules are avaialble…
and do you fix the esp filesystem?
Yes, i did
and does the UUID fit to the device ? check in /etc/fstab and compare with the one from blkid …
Yes, it fits
so it is the state of the partition causing issue… is this the same used for windows?
I am off the desk mainly now, so not responding fast 