Kernel panic after slackpkg upgrade-all

francesco bat · 04-20-2021, 03:22 PM

In any case i tried

Code:

srbds=off

but it don't solve.

My extlinux:

Code:

UI vesamenu.c32
PROMPT 0
MENU TITLE Boot options
MENU BACKGROUND splash.png
DEFAULT huge

LABEL huge
      MENU LABEL Slackware (Huge) 
      KERNEL /boot/vmlinuz-huge-4.4.261
      APPEND srbds=off root=/dev/sdd3 ro

LABEL generic
      MENU LABEL Slackware (Generic)
      KERNEL /boot/vmlinuz-generic-4.4.261
      APPEND srbds=off root=/dev/sdd3 ro
      INITRD /boot/initrd.gz

This is the current configuration with the option "srbds=off", but also it does same error.
I think that is not a problem of configuration in extlinux.
Maybe i can to add some option and slackware could to start but it could to be only a patch.
Bye
Francesco bat

enorbet · 04-20-2021, 03:36 PM

So is /dev/sdd mechanical or electronic? SATA or SSD or NVME? Is the partition table MBR or GPT?

bassmadrigal · 04-20-2021, 03:52 PM

I'm not familiar at all with extlinux, but do you need to write the bootloader to the MBR like lilo? If so, are you writing that bootloader from within Slackware (after chrooting) or from your other distro?

francesco bat · 04-20-2021, 04:40 PM

sdd is SATA and in GPT and it's mechanical.

enorbet · 04-20-2021, 06:01 PM

You probably should check sdd (gdisk -i /dev/sdd) to make certain it alos has protected MBR because, as you probably know, extlinux is Legacy Boot iirc.

colorpurple21859 · 04-20-2021, 08:27 PM

compare your kernel version in /lib/modules to the the kernel version in /boot

francesco bat · 04-21-2021, 05:55 AM

Thank you for answers.
Gdisk result:

Code:

gdisk -i /dev/sdd
GPT fdisk (gdisk) version 1.0.6

Usage: gdisk [-l] device_file

And this is the result of modules kernel:

Code:

# ls /media/Slackware/lib/modules
4.4.14/  4.4.202/  4.4.261/

Code:

# ls /media/Slackware/lib/modules/4.4.261
build@             modules.builtin      modules.devname  modules.symbols.bin
kernel/            modules.builtin.bin  modules.order    source@
modules.alias      modules.dep          modules.softdep
modules.alias.bin  modules.dep.bin      modules.symbols

Bye
Francesco bat

francesco bat · 04-21-2021, 06:11 AM

Since the previous command of gpdisk is only a number version, now i made:

Code:

gdisk -l /dev/sdd
GPT fdisk (gdisk) version 1.0.6

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdd: 3907029168 sectors, 1.8 TiB
Model: TOSHIBA HDWD120
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): 3A5257E7-D49B-4469-8C36-41F81C156AB7
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2157 sectors (1.1 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048           34815   16.0 MiB    8300  Microsoft Reserved ...
   2           34816       617338879   294.4 GiB   8300
   3       617338880       827879423   100.4 GiB   8300
   4       827879424      1246644223   199.7 GiB   8300
   5      1246644224      1454153727   98.9 GiB    8300
   6      1454153728      1660194815   98.2 GiB    8300
   7      1660194816      3511586815   882.8 GiB   8300
   8      3511586816      3907028991   188.6 GiB   8200

Bye
Francesco bat

francesco bat · 04-21-2021, 07:56 AM

Then... i solved in a crazy way.
I don’t even know if I can put "solved" for my madness

In sdb i have did an old slackware 14.2 because sdb is damaged and i must remove it from my pc.
I had an operation like Doctor Frankenstein and i copied kernel and config from old slackware and paste them in sdd3 (Slaxckware partition) in /boot.
Edited Extlinux in old config and it starts

Now i don't know if it is a just solution and if it's better to format it

Now it works
Bye
Francesco bat

francesco bat · 04-21-2021, 08:49 AM

As I feared.
The beast was born from this experiment.
In login, big screen, mouse and keyboard don't work.
It was just a game.

Petri Kaukasoina · 04-21-2021, 09:58 AM

Maybe you didn't copy the corresponding modules?

francesco bat · 04-21-2021, 12:11 PM

Quote:

Originally Posted by Petri Kaukasoina

Maybe you didn't copy the corresponding modules?

It is correct.
I solved it just like that.
I had also thought about the modules but I had seen that the folder of modules in reference to the kernel was present and I did not take a look inside.
Looking now, I noticed that many files were missing.
So I backed up the content and copied it from old Slackware.
It’s all working now.
Now i don't know if i must something else or i can to continue to use it as if nothing had happened.

Bye
Francesco bat

enorbet · 04-21-2021, 12:45 PM

My sincere apology, francesco bat, for my too hurried "gdisk -i /dev/foo" advice. The "-i" was transposed and in error. Eliminating the "-i" like "gdisk /dev/foo" is all that is needed for the desired results.

Regarding the copying of a working kernel to replace a non-working kernel on another system, as long as it's the same hardware and "lib/modules/foo" (and in some cases "/usr/src/linux-foo) are also copied it should at least boot and run equally well.

francesco bat · 04-21-2021, 01:17 PM

Yes! It's same hardware.
Before it was in sdb, then i cloned slackware partition from sdb in sdd with gparted.
The only thing: i made this operation 1 year ago and i changed my pc.
When i added sdb (old slackware) in new pc i cloned the slackware partition in new disk sdd.
It started without problems (i changes just something like fstab).
Could to be this the cause of update failed ?
But it's strange because the clone has always worked in all this time.
Bye
Francesco bat

enorbet · 04-22-2021, 03:39 PM

No. Cloning can't be the cause provided /etc/fstab is consistent with new system layout/assignments. On this Z490 box, new less than a year ago, I still have a 32 bit 14.2 install. It has been upgraded repeatedly since it's beginning as a 12.2 install. That install has also been cloned a droip-in drive to other motherboards/systems as well as cloned more than 3 times..IIRC that system was first installed fresh on a Socket 370 system. I can't even remember all the different systems it has run on, been altered, upgraded, cloned, copied into... you name it, and it still runs great.