Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic: New Kernel seems broken for me  (Read 1944 times)

Offline GoinEasy9

  • User
  • Posts: 508
New Kernel seems broken for me
« on: 2021/11/07, 15:37:13 »
Hello folks

Today after the DU, my install brings me through grub and then gives mdadm:no arrays found in config file or automatically, then drops me to a initramfs shell.

Booting to the previous kernel allows for a normal boot.

new kernel 5.15.1-1
working kernel 5.14.15-2

I'm attaching a screen pic of the error screen.

Edit: No errors occurred after updating my lxqt install, new kernel boots fine.

TIA
Tom
Linux Counter number 348347

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.577
Re: New Kernel seems broken for me
« Reply #1 on: 2021/11/08, 17:23:19 »
That looks like, the kernel is not installed propper.

dpkg -l | egrep -i "x-image|x-head"
df -h
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline GoinEasy9

  • User
  • Posts: 508
Re: New Kernel seems broken for me
« Reply #2 on: 2021/11/08, 20:58:54 »
Thanks towo

root@siduction-kde:/home/goineasy9# dpkg -l | egrep -i "x-image|x-head"
ii  linux-headers-5.14.15-2-siduction-amd64       5.14-15.1                          amd64        Header files for Linux 5.14.15-2-siduction-amd64
ii  linux-headers-5.15.1-1-siduction-amd64        5.15-1                             amd64        Header files for Linux 5.15.1-1-siduction-amd64
ii  linux-headers-siduction-amd64                 5.15-1                             amd64        Linux headers for siduction on 64-bit PCs
rc  linux-image-5.14.10-1-siduction-amd64         5.14-10                            amd64        Linux 5.14 for 64-bit PCs
rc  linux-image-5.14.13-1-siduction-amd64         5.14-13                            amd64        Linux 5.14 for 64-bit PCs
rc  linux-image-5.14.14-1-siduction-amd64         5.14-14                            amd64        Linux 5.14 for 64-bit PCs
ii  linux-image-5.14.15-2-siduction-amd64         5.14-15.1                          amd64        Linux 5.14 for 64-bit PCs
rc  linux-image-5.14.5-3-siduction-amd64          5.14-5.2                           amd64        Linux 5.14 for 64-bit PCs
rc  linux-image-5.14.6-1-siduction-amd64          5.14-7                             amd64        Linux 5.14 for 64-bit PCs
rc  linux-image-5.14.7-1-siduction-amd64          5.14-7.1                           amd64        Linux 5.14 for 64-bit PCs
rc  linux-image-5.14.9-1-siduction-amd64          5.14-9                             amd64        Linux 5.14 for 64-bit PCs
ii  linux-image-5.15.1-1-siduction-amd64          5.15-1                             amd64        Linux 5.15 for 64-bit PCs
ii  linux-image-siduction-amd64                   5.15-1                             amd64        Linux image for siduction on 64-bit PCs
root@siduction-kde:/home/goineasy9# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            1.9G     0  1.9G   0% /dev
tmpfs           387M  1.5M  386M   1% /run
/dev/sda1        49G  9.3G   38G  20% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           1.9G  4.0K  1.9G   1% /tmp
/dev/sda3       401G  327M  380G   1% /home
tmpfs           387M   72K  387M   1% /run/user/1000

Appreciate your help.
Linux Counter number 348347

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.577
Re: New Kernel seems broken for me
« Reply #3 on: 2021/11/08, 21:05:50 »
There i can't find any issue.

Code: [Select]
ls -al /boot
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline GoinEasy9

  • User
  • Posts: 508
Re: New Kernel seems broken for me
« Reply #4 on: 2021/11/08, 21:27:40 »
Thanks again

root@siduction-kde:/home/goineasy9# ls -al /boot
total 98556
drwxr-xr-x  3 root root     4096 Nov  7 08:45 .
drwxr-xr-x 20 root root     4096 Nov  7 08:42 ..
-rw-r--r--  1 root root   222293 Oct 28 12:57 config-5.14.15-2-siduction-amd64
-rw-r--r--  1 root root   223480 Nov  6 09:57 config-5.15.1-1-siduction-amd64
drwxr-xr-x  5 root root     4096 Nov  7 08:45 grub
-rw-r--r--  1 root root 37115107 Oct 31 10:11 initrd.img-5.14.15-2-siduction-amd64
-rw-r--r--  1 root root 37237059 Nov  7 08:43 initrd.img-5.15.1-1-siduction-amd64
-rw-r--r--  1 root root   182704 Aug 15  2019 memtest86+.bin
-rw-r--r--  1 root root   184884 Aug 15  2019 memtest86+_multiboot.bin
-rw-r--r--  1 root root  5317883 Oct 28 12:57 System.map-5.14.15-2-siduction-amd64
-rw-r--r--  1 root root  5339427 Nov  6 09:57 System.map-5.15.1-1-siduction-amd64
-rw-r--r--  1 root root  7514912 Oct 28 12:57 vmlinuz-5.14.15-2-siduction-amd64
-rw-r--r--  1 root root  7548416 Nov  6 09:57 vmlinuz-5.15.1-1-siduction-amd64
Linux Counter number 348347

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.577
Re: New Kernel seems broken for me
« Reply #5 on: 2021/11/08, 22:41:36 »
Looks all good, i don't see any reason, why that kernel should not boot.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline GoinEasy9

  • User
  • Posts: 508
Re: New Kernel seems broken for me
« Reply #6 on: 2021/11/08, 23:35:55 »
Thanks towo

I think I'll try removing, then, reinstalling it and see what happens.

I'll post again afterwards.
Linux Counter number 348347

Offline GoinEasy9

  • User
  • Posts: 508
Re: New Kernel seems broken for me
« Reply #7 on: 2021/11/09, 02:24:52 »
Hello again

Removing the kernel, then, reinstalling it led to the same error as before. So, I'll wait till a new kernel is ready, and, see if the same thing happens, Very strange, but it is the first of the 5.15 kernels.

Thanks for your help towo
« Last Edit: 2021/11/09, 02:34:47 by GoinEasy9 »
Linux Counter number 348347

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.172
    • Land of the Buckeye
Re: New Kernel seems broken for me
« Reply #8 on: 2021/11/09, 11:35:17 »
Here's a thread that describes the issue and some possible fixes (if a new kernel doesn't resolve it):

https://unix.stackexchange.com/questions/559140/debian-buster-uuid-does-not-exist-dropping-to-shell-problem
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline GoinEasy9

  • User
  • Posts: 508
Re: New Kernel seems broken for me
« Reply #9 on: 2021/11/09, 17:49:24 »
Thanks dibl

I played with the advice from the forum post. I couldn't fix or even have a different result come up. So, hopefully the next kernel will fix the problem, since it seems I'm the only one experiencing it.

Thanks again, obviously your Google Fu is a lot letter than mine.
Linux Counter number 348347

Offline GoinEasy9

  • User
  • Posts: 508
Re: New Kernel seems broken for me
« Reply #10 on: 2021/11/11, 22:34:47 »
Hello again.

It seems that 5.15.1-3 is giving me the same "can't find root" error. I'm waiting to see what happens when Tumbleweed releases a 5.15 kernel. Maybe I can do some comparisons. at least my 5.14 kernel still works.

Tom
Linux Counter number 348347

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.172
    • Land of the Buckeye
Re: New Kernel seems broken for me
« Reply #11 on: 2021/11/11, 23:05:22 »
Your error message where the UUID is not recognized makes me suspect something is not quite right on your system. Have you recently added any drives, or changed partition layout, or anything like that? If you are using the UUIDs in /etc/fstab, which I highly recommend, then you might want to compare the UUIDs in fstab with the UUID in the grub config file and make sure that it matches the boot partition. Do you have a swap partition -- your grub couldn't seem to recognize the UUID for resume, which would be the swap partition.
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline GoinEasy9

  • User
  • Posts: 508
Re: New Kernel seems broken for me
« Reply #12 on: 2021/11/11, 23:44:32 »
Hi dibl

Thanks for the ideas.

The machine has been running siduction for many years, hasn't changed a bit. It has a rack mount for the HDD. I have 4 disks that I can easily slip in, one with windows 10, one with siduction, one with Leap and one with Tumbleweed. anyway ...

The UUID in fstab, for root, is the same as the one showing in the error. Works with 5.14, errors out with 5.15. I have all the normal partitions /root, /home & swap.

I'm going to see if I can find something in the logs, Eventually the answer will turn up.

Tom
Linux Counter number 348347

Offline vindeliker

  • User
  • Posts: 78
Re: New Kernel seems broken for me
« Reply #13 on: 2021/11/13, 10:16:59 »
Hi GoinEasy9,
just to stand by you, my little server has the same problem with kernel 5.15, you're not alone :-)

It's an old installation, maybe 8 years, but dist-upgraded up to date and running fine with Kernel 5.14.16-2. Siduction is installed on the SanDisk SSD /dev/sda. There is no firmware update available. The three HDD are newer.

Code: [Select]
root@turing:~# inxi -D
Drives:    Local Storage: total: 5.52 TiB used: 1 TiB (18.2%)
           ID-1: /dev/sda vendor: SanDisk model: SDSSDP064G size: 59.63 GiB
           ID-2: /dev/sdb vendor: Seagate model: ST2000VN004-2E4164 size: 1.82 TiB
           ID-3: /dev/sdc vendor: Western Digital model: WD20EFRX-68EUZN0 size: 1.82 TiB
           ID-4: /dev/sdd vendor: Western Digital model: WD20EFRX-68EUZN0 size: 1.82 TiB

I hope it is an error in the Kernel and will be fixed in a new version. But I have the vague suspicion that something was dropped and will never come back  :'(

Roland

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.577
Re: New Kernel seems broken for me
« Reply #14 on: 2021/11/13, 12:22:04 »
Have you more than one distro installed on your PC?
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.