Code: Select all
Fatal: Bios device code 0x80 is being used by two disks /devsdb (0x0810) and /dev/sde (0x0800).
Sorry, but the attempt to install Lilo has returned an error...
Code: Select all
Fatal: Bios device code 0x80 is being used by two disks /devsdb (0x0810) and /dev/sde (0x0800).
Sorry, but the attempt to install Lilo has returned an error...
That's a little surprising since form your posting of the outputs of lslblk -f and blkid I concluded the following:globetrotterdk wrote:I used cfdisk to check, and /sdb is my Windows system, while /sde is my Devuan system.
Google "Bios device code 0x80 is being used by two disks". There are some answers there but it very complex and beyond my current knowledge of lilo. You might want to also consider simplifying your system a bit. sdb is not being used and it is apparently one of the drive causing the latest issue. I suggest you take it out along with sde since that one appears to have no purpose in your current scheme, and see if you can get it working with the three other drives.I just don't quite understand what it means:Code: Select all
Fatal: Bios device code 0x80 is being used by two disks /devsdb (0x0810) and /dev/sde (0x0800). Sorry, but the attempt to install Lilo has returned an error...
Read the hit from the Google search, it has nothing to do with boot flags. The problem seems to be with BIOS IDs being passed from lilo and the bios at either the time that lilo is installed or at boot up. It also appears that the use of both grub and lilo may have added to the confusion of the BIOS ID. There appears to be some lines that can be added to lilo.conf to resolve it but again, I couldn’t really get a full understanding in my brief review of the subject.Lilo is supposed to be able to multiboot, but it seems like the boot flags on both installs are somehow preventing Lilo from getting installed.
You do know that even though your are booting legacy that you really are still running UEFI. UEFI is just emulating bios booting by running UEFI code. Since UEFI is a specification, there are many vendors producing their own UEFI compliant firmware. You can expect and do get bugs.I don't think that this is a limitation of a modern BIOS.
Absolutely.laprjns wrote:Is this the changing disk ordering that drove you to change to UUID?
My thoughts exactly. I tried this with a couple of drives and ended up with my BIOS insisting on booting Windows 10, but I eventually got it sorted. I BTW have an ASRock 970 Pro3 Rev2.0 motherboard at this time. I will have to try to find the correct drive and unplug everything else, to see if I can get Lilo installed on the Salix disk.laprjns wrote:You might want to also consider simplifying your system a bit. sdb is not being used and it is apparently one of the drive causing the latest issue. I suggest you take it out along with sde since that one appears to have no purpose in your current scheme, and see if you can get it working with the three other drives.
Good to know.laprjns wrote:I will be trailing over the next week or so and will have little to no access to the internet, so I will not be able to follow or post during this time. Hopefully you will get this working soon
Regards
Rich
It is probably better to try just unplugging the one or two drives you aren't even using, because otherwise, you are liable to mess things up again when you put them back. The idea is not so much to install the bootloader come what may as to simplify the configuration to make that possible straightforwardly.I will have to try to find the correct drive and unplug everything else
Code: Select all
# mkinitrd
Nothing found at location /boot/initrd-tree, so we will create an
initrd directory structure there... done.
Now cd to /boot/initrd-tree and install some modules in your
module directory (lib/modules/4.4.19). Then see init
for more information (there are a few other files to edit).
Finally, run mkinitrd again once the initrd-tree is ready,
and /boot/initrd.gz will be created from it.
Code: Select all
sudo spi -U
Thanks for the very timely reply mimosa. OK, I ran:mimosa wrote:Right - excellent! Interesting that it now boots without panicking.
Before you get on to the initrd, though, you should upgrade your kernel. Instructions for how to do that are on the wiki. Remember to run lilo (locally this time) before rebooting. You shouldn't need to edit lilo.conf, but it may be as well to check. You want the image line to point to /boot/vmlinuz.
https://docs.salixos.org/wiki/How_to_in ... ent_kernel
I will pop back in after breakfast.
Edit
You might as well do a full upgrade as well:I think that will pull in a new LILO package, among other things.Code: Select all
sudo spi -U
Code: Select all
$ sudo slapt-get -i kernel-huge kernel-modules kernel-headers kernel-firmware
Code: Select all
sudo /usr/share/mkinitrd/mkinitrd_command_generator.sh /boot/vmlinuz
Code: Select all
#
# mkinitrd_command_generator.sh revision 1.45
#
# This script will now make a recommendation about the command to use
# in case you require an initrd image to boot a kernel that does not
# have support for your storage or root filesystem built in
# (such as the Slackware 'generic' kernels').
# A suitable 'mkinitrd' command will be:
mkinitrd -c -k 4.4.111 -f btrfs -r /dev/sda2 -m usb-storage:xhci-hcd:xhci-pci:ohci-pci:ehci-pci:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:btrfs -u -o /boot/initrd.gz
# An entry in 'etc/lilo.conf' for kernel '/boot/vmlinuz-huge-4.4.111' would look like this:
# Linux bootable partition config begins
# initrd created with 'mkinitrd -c -k 4.4.111 -f btrfs -r /dev/sda2 -m usb-storage:xhci-hcd:xhci-pci:ohci-pci:ehci-pci:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:btrfs -u -o /boot/initrd.gz'
image = /boot/vmlinuz-huge-4.4.111
initrd = /boot/initrd.gz
root = /dev/sda2
label = 4.4.111
read-only
# Linux bootable partition config ends
Code: Select all
sudo mkinitrd -c -k 4.4.111 -f btrfs -r /dev/sda2 -m usb-storage:xhci-hcd:xhci-pci:ohci-pci:ehci-pci:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:btrfs -u -o /boot/initrd.gz
Code: Select all
wget http://mirrors.nix.org.ua/linux/salixos/x86_64/slackware-14.2/patches/packages/linux-4.4.118/kernel-generic-4.4.118-x86_64-1.txz
I had a problem with the slackware.uk repo for Salix crapping out for some reason. I had to give it some time, but ended up having to do a CTRL C escape and then re-run. Everything seems to be OK, however. OK, I ranmimosa wrote:Did you run lilo and reboot?
Code: Select all
$ sudo /usr/share/mkinitrd/mkinitrd_command_generator.sh /boot/vmlinuz
Code: Select all
$ sudo /usr/share/mkinitrd/mkinitrd_command_generator.sh /boot/vmlinuz
#
# mkinitrd_command_generator.sh revision 1.45
#
# This script will now make a recommendation about the command to use
# in case you require an initrd image to boot a kernel that does not
# have support for your storage or root filesystem built in
# (such as the Slackware 'generic' kernels').
# A suitable 'mkinitrd' command will be:
mkinitrd -c -k 4.4.118 -f ext4 -r /dev/sda1 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4 -u -o /boot/initrd.gz
# An entry in 'etc/lilo.conf' for kernel '/boot/vmlinuz-huge-4.4.118' would look like this:
# Linux bootable partition config begins
# initrd created with 'mkinitrd -c -k 4.4.118 -f ext4 -r /dev/sda1 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4 -u -o /boot/initrd.gz'
image = /boot/vmlinuz-huge-4.4.118
initrd = /boot/initrd.gz
root = /dev/sda1
label = 4.4.118
read-only
# Linux bootable partition config ends
Code: Select all
mkinitrd -c -k 4.4.118 -f ext4 -r /dev/sda1 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4 -u -o /boot/initrd.gz