[SOLVED] latest slackpkg upgrade-all bricks system on slackware64-current

jkh2cpu · 01-03-2018, 07:30 AM

I just did the download, did the slackpkg install-all, and now I've got a fine brick with pretty colored lights.

Here's what I read on the console:

Driver: sr

No file system. count not mount root - tried romfs.

Kernel panic, not syncing.

There is a lot of print-out, and then I read: Unable to mount root fs on unknown block (8.33)

Any thoughts on a quick fix, or do I need to reinstall starting from the 14.2 cd.

John.

willysr · 01-03-2018, 07:33 AM

did you forgot to create initrd or to run /sbin/lilo after installing the updated packages?

jkh2cpu · 01-03-2018, 07:39 AM

I don't use initrd, and I'm sure I did the lilo.

John.

bassmadrigal · 01-03-2018, 08:09 AM

What were the steps you took? Because you list upgrade-all in your subject, but install-all in your post. When running -current, you should issue (at a minimum), the following commands:

Code:

slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system

You should probably also do slackpkg new-config if it doesn't do it for you.

jkh2cpu · 01-03-2018, 08:21 AM

You're right of course, and I did it the correct way, but did not report it that way. Sorry for the confusion.

I just checked out the bricked system, and I did a lilo before I rebooted. So that's not it.

John.

Darth Vader · 01-03-2018, 08:22 AM

Quote:

Originally Posted by jkh2cpu

I just did the download, did the slackpkg install-all, and now I've got a fine brick with pretty colored lights.

Here's what I read on the console:

Driver: sr

No file system. count not mount root - tried romfs.

Kernel panic, not syncing.

There is a lot of print-out, and then I read: Unable to mount root fs on unknown block (8.33)

Any thoughts on a quick fix, or do I need to reinstall starting from the 14.2 cd.

John.

For whatever reason, our BDFL decided to use the same kernel for "generic" and "huge" variants, in the last update. Hence, they both needs an initrd to work properly.

Blame your bad luck and the usage of a huge kernel after its supposed life cycle (first boot, then you had been to customize your boot), and grab a live system, them generate and use a proper initrd.

aaazen · 01-03-2018, 08:26 AM

Quote:

Originally Posted by jkh2cpu

I just did the download, did the slackpkg install-all, and now I've got a fine brick with pretty colored lights.

Here's what I read on the console:

Driver: sr

No file system. count not mount root - tried romfs.

Kernel panic, not syncing.

There is a lot of print-out, and then I read: Unable to mount root fs on unknown block (8.33)

Any thoughts on a quick fix, or do I need to reinstall starting from the 14.2 cd.

John.

The 4.14.11 huge kernel is actually generic by mistake. (Hopefully it will be fixed soon?)

So it needs an initrd just like a generic kernel...

jkh2cpu · 01-03-2018, 08:26 AM

So is there a fix without doing a re-install?

John.

Darth Vader · 01-03-2018, 08:26 AM

Quote:

Originally Posted by aaazen

The 4.14.11 huge kernel is actually generic by mistake. (Hopefully it will be fixed soon?)

So it needs an initrd just like a generic kernel...

Not be so sure that's a mistake.

Darth Vader · 01-03-2018, 08:28 AM

Quote:

Originally Posted by jkh2cpu

So is there a fix without doing a re-install?

John.

Yes, on other computer download a live system, like those shipped by AlienBOB, then after booting on live, you can chroot in your host operating system to add a proper initrd.

There is your Savior:

https://slackware.nl/slackware-live/1.1.9.3/

jkh2cpu · 01-03-2018, 08:29 AM

Thanks, Darth.

And the technique for that (without actual hand-holding) is... ???

John.

Darth Vader · 01-03-2018, 08:32 AM

Quote:

Originally Posted by jkh2cpu

Thanks, Darth.

And the technique for that (without actual hand-holding) is... ???

John.

We will talk about the actual technique when you post back from the live system. They have graphical interface, then will be no issue to post from them.

Long story short, it is about chroot-ing as root in your real Linux installation, then you will be guided by execution of:

Code:

/usr/share/mkinitrd/mkinitrd_command_generator.sh

Didier Spaier · 01-03-2018, 08:32 AM

Quote:

Originally Posted by jkh2cpu

So is there a fix without doing a re-install?

Boot an installation media (or live as said Darth), login as root, don't run setup, mount your (installed) root partition as /mnt, bind mount /dev /proc and /sys as /mnt/dev, /mnt/proc and /mnt/sys, chroot /mnt and make the intrd, install it and run lilo.

That being said, asking the question is a hint that maybe you shouldn't run -current...

PS didn't see Darht's answer before posting mine.

jkh2cpu · 01-03-2018, 08:34 AM

Hi, Darth. I have the live boot stick from a previous excursion. Heh. That's how I know that I did the lilo on the bricked system.

I'm ready for hand-holding.

(PS: the firefox on AlienBob's boot stick will not run.)

John.

Darth Vader · 01-03-2018, 08:37 AM

Quote:

Originally Posted by jkh2cpu

Hi, Darth. I have the live boot stick from a previous excursion. Heh. That's how I know that I did the lilo on the bricked system.

I'm ready for hand-holding.

(PS: the firefox on AlienBob's boot stick will not run.)

John.

Do as Didier said, then use the command which I suggested. This will help you to generate a custom initrd for your system, then you will have to adjust your /etc/lilo.conf

Something like:

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz-generic
  root = /dev/sda2
  label = "Linux"
  initrd = /boot/initrd.gz
  read-only
# Linux bootable partition config ends

Of course, you should finally run "lilo"