Upgraded, now my other distro not found at boot: SOLVED

[Dai_trying]

The fstab info I posted is for Debian, for Hyperbola you would need to modify its fstab to the following

Code: Select all

UUID=dbc9438f-1ad4-4fe9-9b82-ba8df589d81d / ext4 rw,relatime,errors=remount-ro   0 1
UUID=a56aa0ac-dcf0-4d43-b38b-8fac5979cfbc swap swap defaults 0 0

[p.H]

lsinitramfs /mnt/boot/initramfs-linux-libre-lts.img

All required kernel modules seem to be included (USB HID, SATA AHCI, ext4), although all in kernel/ instead of in their own usual paths as in Debian initramfs.
The SATA controller is set in AHCI mode in the BIOS/UEFI setup ?
Is the kernel image the same version ?

Code: Select all

file /mnt/boot/vmlinuz-linux-libre-lts

should report version 4.9.176-gnu-0-lts.

Hyperbola is identified by a different UUID now because I played with gparted. Is that going to cause a problem?

Possibly. What did you do exactly ?
For now, the UUID in grub.cfg must match the current UUID of Hyperbola's root filesystem.

[bentHnau]

The SATA controller is set in AHCI mode in the BIOS/UEFI setup ?

Yes

Is the kernel image the same version ?

Code: Select all

file /mnt/boot/vmlinuz-linux-libre-lts

should report version 4.9.176-gnu-0-lts.

No.

Code: Select all

Linux kernel x86 boot executable bzImage, version 4.9.200-gnu-1-lts (builduser@eden_packages_autobuilder_gnu_plus_linux-libre) #1 SMP Mon Nov 11 , RO-rootFS, swap_dev 0x4, Normal VGA

Hyperbola is identified by a different UUID now because I played with gparted. Is that going to cause a problem?

Possibly. What did you do exactly ?
I just right-clicked on /dev/sdb2 and chose "New UUID" from the menu. Since then, I've been typing in the new UUID whenever I try to boot Hyperbola.

[p.H]

The kernel image version is more recent than the kernel modules version in the initramfs. This explains why the initramfs cannot find the root filesystem and the keyboard does not work, as the kernel image cannot load kernel modules of a different version. I suspect that the initramfs was not rebuilt properly after a kernel upgrade.

Are there other vmlinuz or initramfs files in Hyperbola's /boot ?

Can you rebuild Hyperbola's initramfs ?

[bentHnau]

Are there other vmlinuz or initramfs files in Hyperbola's /boot ?

Here is the contents of boot/

Code: Select all

config-linux-libre-lts	initramfs-linux-libre-lts-fallback.img	syslinux
grub			initramfs-linux-libre-lts.img		vmlinuz-linux-libre-lts

Can you rebuild Hyperbola's initramfs ?

Probably not since I don't even know what that means. I can look it up, but that sounds complicated.

[p.H]

In Debian with the default initramfs generator initramfs-tools you would simply run

Code: Select all

update-initramfs -u

or reinstall the current kernel with apt or so.

But I don't know about Hyperbola. You may need to search the documentation or seek help from the Hyperbola community.

EDIT : You can also check the kernel modules version in the fallback initramfs (boot/initramfs-linux-libre-lts-fallback.img) with lsinitramfs. If it matches the vmlinuz version, you can boot with this initramfs instead of the default one.

[bentHnau]

or reinstall the current kernel with apt or so.

But I don't know about Hyperbola. You may need to search the documentation or seek help from the Hyperbola community.

Reinstallation fixed the problem. I reinstalled it with

Code: Select all

sudo pacman -S linux

after chrooting into Hyperbola with arch-chroot (which is available in the Debian repo). Thank you.

[sunrat]

I suspect your problems may have been from doing the Hyperbola upgrades via chroot. Never heard of anyone doing that before. Maybe it should work, maybe it didn't.

[p.H]

Yes. I avoid doing system upgrades in a chroot.
Whatever happened, something went wrong when upgrading Hyperbola's kernel the first time.