Kernel panic after installation via tar and chroot

NickF_93 · 08-09-2019, 06:26 AM

Hello everyone, I'm trying to install a slackware system on a PC with a live usb of Ubuntu 18.04.

PC has 2 disk: SDD and a Flash memory.
At boot Ubuntu see SDD as /dev/sda, Flash as /dev/sdc and Live USB as /dev/sdb.
I'm trying to install system on /dev/sdc (Flash memory).

So I formatted /dev/sdc1 to ext4 and mounted on /mnt

Code:

# mount /dev/sdc1 /mnt

and then extracted compressed system in /mnt

Code:

# tar -xvpzf /dir/with/tar/MySystem.tar.gz -C /mnt

Then I mounted proc, dev, sys:

Code:

# mount -t proc /proc /mnt/proc
# mount -o bind /dev /mnt/dev
# mount -o bind /sys /mnt/sys

Then I created lilo.conf in /etc with:

boot = /dev/disk/by-id/<FLASH-DISK-ID>

and

root = /dev/disk/by-uuid/<FLASH-DISK-PART1-FS-UUID>

I set right UUID in /etc/fstab:
/dev/disk/by-uuid/<FLASH-DISK-PART1-FS-UUID> / ext4 defaults 1 1

and then run mkinitrd:

Code:

# mkinitrd -c -k4.19.45 -f ext4 -r /dev/disk/by-uuid/<FLASH-DISK-PART1-FS-UUID> -u -o /boot/initrd.gz

it give me errors like:

tempnam: No such file or directory
cat: bin: Is a directory
...
rm: cannot remove 'bin': Is a directory
...

but at the end it say:

/boot/initrd.gz created

then I run

Code:

# lilo

At reboot if live USB is inserted the system boot without problems, if I remove live USB it give me the Kernel Panic error:

kernel panic not syncing vfs unable to mount root fs on unknown block

What's the problem?

Thanks in advance.

kgha · 08-09-2019, 07:47 AM

You write that Ubuntu sees both your Flash and your USB as dev/sdc ?
Can't understand how this can occur, but my tuppence is that it has created some confusion so that your boot setup is dependent on one thing or another that resides on your USB stick.

NickF_93 · 08-09-2019, 07:54 AM

Quote:

Originally Posted by kgha

You write that Ubuntu sees both your Flash and your USB as dev/sdc ?
Can't understand how this can occur, but my tuppence is that it has created some confusion so that your boot setup is dependent on one thing or another that resides on your USB stick.

Sorry, I correct my question:
SSD: sda
USB: sdb
FLASH: sdc

I want to install on sdc1 the system and my live system is on USB (sdb1)

Lysander666 · 08-09-2019, 08:03 AM

Can you post your fstab and lilo.conf?

kgha · 08-09-2019, 08:23 AM

Another tuppence:
This might be dependent on your BIOS, but I've experienced (with an old Asus eee) that USB sticks always take precedence over Flash (SD) cards.
With the flash in its slot (and no USB stick attached), it was recognised as sdb. If I booted from a USB, the stick was sdb and flash became sdc.
So my guess is that with the USB removed, there is no sdc.
As Lysander666 writes' you should check fstab and lilo and see what they contain.

NickF_93 · 08-09-2019, 08:50 AM

Quote:

Originally Posted by Lysander666

Can you post your fstab and lilo.conf?

fstab:

Code:

/dev/disk/by-uuid/3d847b09-cd7b-4758-8d72-c40519c96f33        /                ext4        defaults         1   1
#/dev/sdb1        /                ext4        defaults,remount,ro,noload         1   1
#/dev/sdb2        /mnt/part2       ext4        defaults                           1   1
#/dev/sda1        /mnt/data        ext4        defaults                            0   0
#/dev/cdrom      /mnt/cdrom       auto        noauto,owner,ro,comment=x-gvfs-show 0   0
#/dev/fd0         /mnt/floppy      auto        noauto,owner                       0   0
devpts           /dev/pts         devpts      gid=5,mode=620                      0   0
proc             /proc            proc        defaults                            0   0
tmpfs            /dev/shm         tmpfs       nosuid,nodev,noexec                 0   0

lilo.conf:

Code:

append=" vt.default_utf8=1 acpi=on pcie_aspm=off mitigations=off oops=panic idle=poll nohalt"
boot = /dev/disk/by-id/ata-CFast_3ME4_YCA11905060340088

#compact        # faster, but won't work on all systems.

  bitmap = /boot/slack.bmp
  bmp-colors = 255,0,255,0,255,0
  bmp-table = 60,6,1,16
  bmp-timer = 65,27,0,255

prompt
timeout = 100
change-rules
  reset
vga = normal

image = /boot/vmlinuz-4.19.45
  root = /dev/disk/by-uuid/3d847b09-cd7b-4758-8d72-c40519c96f33
  append = "4 vt.default_utf8=1 ipv6.disable=1 TOOLS=0  acpi=noirq pcie_aspm=off ramdisk_size=512000 usbcore.usbfs_memory_mb=256 mitigations=off oops=panic idle=poll nohalt quiet"
  label = Linux
  read-only  # Partitions should be mounted read-only for checking

image = /boot/vmlinuz-4.19.45
  root = /dev/disk/by-uuid/3d847b09-cd7b-4758-8d72-c40519c96f33
  append = "4 vt.default_utf8=1 ipv6.disable=1 TOOLS=1  acpi=on pcie_aspm=off ramdisk_size=512000"
  label = Tools
  read-only
image = /boot/vmlinuz-4.19.45
  root = /dev/disk/by-uuid/3d847b09-cd7b-4758-8d72-c40519c96f33
  append = "3 vt.default_utf8=1 ipv6.disable=1 acpi=on pcie_aspm=off ramdisk_size=512000"
  label = Console

NickF_93 · 08-09-2019, 08:51 AM

Quote:

Originally Posted by kgha

Another tuppence:
This might be dependent on your BIOS, but I've experienced (with an old Asus eee) that USB sticks always take precedence over Flash (SD) cards.
With the flash in its slot (and no USB stick attached), it was recognised as sdb. If I booted from a USB, the stick was sdb and flash became sdc.
So my guess is that with the USB removed, there is no sdc.
As Lysander666 writes' you should check fstab and lilo and see what they contain.

Ok, but I would be device name independent and refers to devices by their ids and uuids

Didier Spaier · 08-09-2019, 09:07 AM

Not sure it's the issue but the kernel per se doesn't know the file system UUIDs, so to find / you need to rely on an initrd that will run udev. I don't see "initrd=...' lines in your lilo.conf.

Lysander666 · 08-09-2019, 09:11 AM

Quote:

Originally Posted by Didier Spaier

Not sure it's the issue but the kernel per se doesn't know the file system UUIDs, so to find / you need to rely on an initrd that will run udev. I don't see "initrd=...' lines in your lilo.conf.

You may be onto something. As far as I remember persistent naming prefers a generic kernel if using UUIDs.