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

Kernels & Hardware, configuring network, installing services

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

Postby Dai_trying » 2019-11-19 16:05

But it does match the output reported in #8
Dai_trying
 
Posts: 833
Joined: 2016-01-07 12:25

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

Postby bentHnau » 2019-11-23 20:59

Dai_trying wrote:Your swap partition is wrong in your fstab, usually this would result in a 90 second boot delay but maybe you don't wait that long? try changing that to the correct one and see if that helps.

Your fstab entry
UUID=ac2b1f54-c797-4f5e-9656-834ae2d6ccbb none swap sw 0 0

should be
UUID=ef6867ad-887c-4270-bbb9-6b7b4e28b048 swap swap sw 0 0

It looks like you are trying to mount your 454Gb partition as swap.

I made this change. The root partition is still not found. I tried waiting 90 seconds; nothing changed.
Debian Stretch x64 on a Dell XPS 17 laptop
bentHnau
 
Posts: 138
Joined: 2014-01-07 01:43
Location: California

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

Postby bentHnau » 2019-11-23 21:06

p.H wrote:Can you check the contents of the initramfs with lsinitramfs ?

lsinitramfs /mnt/boot/initramfs-linux-libre-lts.img
Code: Select all
init
init_functions
sbin
lib
tmp
lib64
dev
config
run
new_root
hooks
hooks/udev
bin
usr
usr/sbin
usr/lib
usr/lib/libe2p.so.2
usr/lib/libuuid.so.1
usr/lib/libmount.so.1
usr/lib/libkmod.so.2
usr/lib/libpthread.so.0
usr/lib/libc.so.6
usr/lib/librt.so.1
usr/lib/libext2fs.so.2
usr/lib/libcom_err.so.2
usr/lib/libz.so.1
usr/lib/ld-linux-x86-64.so.2
usr/lib/libblkid.so.1
usr/lib/modprobe.d
usr/lib/modprobe.d/dummy.conf
usr/lib/udev
usr/lib/udev/rules.d
usr/lib/udev/rules.d/80-drivers.rules
usr/lib/udev/rules.d/64-btrfs.rules
usr/lib/udev/rules.d/60-persistent-storage.rules
usr/lib/udev/rules.d/50-udev-default.rules
usr/lib/udev/scsi_id
usr/lib/udev/ata_id
usr/lib/libcrypt.so.1
usr/lib/liblzma.so.5
usr/lib/modules
usr/lib/modules/4.9.176-gnu-0-lts
usr/lib/modules/4.9.176-gnu-0-lts/modules.symbols.bin
usr/lib/modules/4.9.176-gnu-0-lts/modules.alias.bin
usr/lib/modules/4.9.176-gnu-0-lts/modules.softdep
usr/lib/modules/4.9.176-gnu-0-lts/modules.devname
usr/lib/modules/4.9.176-gnu-0-lts/modules.builtin.bin
usr/lib/modules/4.9.176-gnu-0-lts/modules.dep.bin
usr/lib/modules/4.9.176-gnu-0-lts/kernel
usr/lib/modules/4.9.176-gnu-0-lts/kernel/usb-storage.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/ehci-pci.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/serio_raw.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/i8042.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/libahci.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/xhci-pci.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/xhci-hcd.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/atkbd.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/scsi_mod.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/fscrypto.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/usbhid.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/serio.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/mbcache.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/ehci-hcd.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/ahci.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/sr_mod.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/libata.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/jbd2.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/sd_mod.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/libps2.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/usb-common.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/hid.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/hid-generic.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/crc16.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/cdrom.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/usbcore.ko
usr/lib/modules/4.9.176-gnu-0-lts/kernel/ext4.ko
usr/lib/libdl.so.2
usr/lib64
usr/local
usr/local/sbin
usr/local/lib
usr/local/bin
usr/bin
usr/bin/ps
usr/bin/printf
usr/bin/false
usr/bin/init
usr/bin/uptime
usr/bin/rmmod
usr/bin/truncate
usr/bin/kmod
usr/bin/mkfifo
usr/bin/[[
usr/bin/pwd
usr/bin/basename
usr/bin/sh
usr/bin/wc
usr/bin/rm
usr/bin/umount
usr/bin/kill
usr/bin/sha256sum
usr/bin/cttyhack
usr/bin/chgrp
usr/bin/chroot
usr/bin/sha512sum
usr/bin/insmod
usr/bin/nsenter
usr/bin/losetup
usr/bin/dirname
usr/bin/blkdiscard
usr/bin/ip
usr/bin/fsck.ext2
usr/bin/grep
usr/bin/tftp
usr/bin/pgrep
usr/bin/nslookup
usr/bin/ipaddr
usr/bin/seq
usr/bin/mount
usr/bin/poweroff
usr/bin/cut
usr/bin/sort
usr/bin/hexdump
usr/bin/md5sum
usr/bin/true
usr/bin/iprule
usr/bin/echo
usr/bin/mktemp
usr/bin/tac
usr/bin/du
usr/bin/iptunnel
usr/bin/less
usr/bin/free
usr/bin/iproute
usr/bin/wget
usr/bin/unlink
usr/bin/sync
usr/bin/openvt
usr/bin/unshare
usr/bin/kbd_mode
usr/bin/cp
usr/bin/rmdir
usr/bin/lsmod
usr/bin/iplink
usr/bin/halt
usr/bin/nc
usr/bin/route
usr/bin/mkdir
usr/bin/clear
usr/bin/chown
usr/bin/telnet
usr/bin/pidof
usr/bin/udevadm
usr/bin/env
usr/bin/shuf
usr/bin/ash
usr/bin/netstat
usr/bin/setfont
usr/bin/yes
usr/bin/killall
usr/bin/depmod
usr/bin/loadkmap
usr/bin/mknod
usr/bin/fsck.ext4
usr/bin/fatattr
usr/bin/[
usr/bin/tail
usr/bin/expr
usr/bin/chmod
usr/bin/ping6
usr/bin/blkid
usr/bin/fsck
usr/bin/sleep
usr/bin/install
usr/bin/egrep
usr/bin/test
usr/bin/ping
usr/bin/readlink
usr/bin/cat
usr/bin/mkpasswd
usr/bin/ln
usr/bin/getopt
usr/bin/fstrim
usr/bin/modprobe
usr/bin/stat
usr/bin/head
usr/bin/mountpoint
usr/bin/awk
usr/bin/vi
usr/bin/fsck.ext3
usr/bin/sed
usr/bin/ls
usr/bin/df
usr/bin/touch
usr/bin/reboot
usr/bin/switch_root
usr/bin/mv
usr/bin/modinfo
usr/bin/dd
usr/bin/uniq
usr/bin/busybox
usr/bin/loadfont
usr/bin/ifconfig
usr/bin/strings
usr/bin/sha1sum
usr/bin/dmesg
usr/bin/udevd
usr/bin/uname
VERSION
proc
sys
buildconfig
etc
etc/fstab
etc/ld.so.conf
etc/mtab
etc/ld.so.cache
etc/initrd-release
etc/modprobe.d
etc/udev
etc/udev/udev.conf

Some flavours of mount with limited capabilities (which may be used in the initramfs) may require to specify rootfstype= in the kernel command line.

What do I use for the filesystem type? I tried rootfstype=ext4 (which gparted says is the correct type for Hyperbola). Nothing changed, same error.
Debian Stretch x64 on a Dell XPS 17 laptop
bentHnau
 
Posts: 138
Joined: 2014-01-07 01:43
Location: California

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

Postby Dai_trying » 2019-11-23 21:36

You could try this in your fstab, you could either comment out all other lines or backup the file and create a fresh one with just this content.

Code: Select all
UUID=ac2b1f54-c797-4f5e-9656-834ae2d6ccbb / ext4 rw,relatime,errors=remount-ro   0 1
UUID=ef6867ad-887c-4270-bbb9-6b7b4e28b048 swap swap defaults 0 0


I don't know if you need the data=ordered my limited understanding is that it is more used with ext3 filesystem, but as you are using ext4 this should not be required. If you want to check the filesystem types you can use the command (and maybe post it here for brevity)
Code: Select all
lsblk -o +uuid,fstype
Dai_trying
 
Posts: 833
Joined: 2016-01-07 12:25

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

Postby bentHnau » 2019-11-23 23:45

Dai_trying wrote:You could try this in your fstab, you could either comment out all other lines or backup the file and create a fresh one with just this content.

Code: Select all
UUID=ac2b1f54-c797-4f5e-9656-834ae2d6ccbb / ext4 rw,relatime,errors=remount-ro   0 1
UUID=ef6867ad-887c-4270-bbb9-6b7b4e28b048 swap swap defaults 0 0


What is the first UUID entry for? Apparently I don't understand what is supposed to be in fstab. Is there normally a listing for every mountable filesystem on the computer?

I don't know if you need the data=ordered my limited understanding is that it is more used with ext3 filesystem, but as you are using ext4 this should not be required. If you want to check the filesystem types you can use the command (and maybe post it here for brevity)
Code: Select all
lsblk -o +uuid,fstype

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID FSTYPE
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 454G 0 part / ac2b1f54-c797-4f5e-9656-834ae2d6ccbb ext4
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 11.8G 0 part [SWAP] ef6867ad-887c-4270-bbb9-6b7b4e28b048 swap
sdb 8:16 0 465.8G 0 disk
├─sdb1 8:17 0 3.5G 0 part a56aa0ac-dcf0-4d43-b38b-8fac5979cfbc swap
└─sdb2 8:18 0 462.3G 0 part /mnt dbc9438f-1ad4-4fe9-9b82-ba8df589d81d ext4
sr0 11:0 1 1024M 0 rom

Hyperbola is identified by a different UUID now because I played with gparted. Is that going to cause a problem?
Debian Stretch x64 on a Dell XPS 17 laptop
bentHnau
 
Posts: 138
Joined: 2014-01-07 01:43
Location: California

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

Postby Dai_trying » 2019-11-24 08:24

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
Dai_trying
 
Posts: 833
Joined: 2016-01-07 12:25

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

Postby p.H » 2019-11-24 08:40

bentHnau wrote: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.
bentHnau wrote: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.
p.H
 
Posts: 1184
Joined: 2017-09-17 07:12

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

Postby bentHnau » 2019-11-24 21:58

p.H wrote: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



bentHnau wrote: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.
Debian Stretch x64 on a Dell XPS 17 laptop
bentHnau
 
Posts: 138
Joined: 2014-01-07 01:43
Location: California

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

Postby p.H » 2019-11-24 22:32

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 ?
p.H
 
Posts: 1184
Joined: 2017-09-17 07:12

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

Postby bentHnau » 2019-11-24 22:40

p.H wrote:
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.
Debian Stretch x64 on a Dell XPS 17 laptop
bentHnau
 
Posts: 138
Joined: 2014-01-07 01:43
Location: California

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

Postby p.H » 2019-11-25 05:46

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.
p.H
 
Posts: 1184
Joined: 2017-09-17 07:12

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

Postby bentHnau » 2019-11-25 23:50

p.H wrote: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.
Debian Stretch x64 on a Dell XPS 17 laptop
bentHnau
 
Posts: 138
Joined: 2014-01-07 01:43
Location: California

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

Postby sunrat » 2019-11-26 00:19

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.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 2920
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

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

Postby p.H » 2019-11-26 05:51

Yes. I avoid doing system upgrades in a chroot.
Whatever happened, something went wrong when upgrading Hyperbola's kernel the first time.
p.H
 
Posts: 1184
Joined: 2017-09-17 07:12

Previous

Return to System configuration

Who is online

Users browsing this forum: peer and 19 guests

fashionable