Can LILO use UUID?

[root]

I get conflicting answers from google. I tried
a root = "UUID=........"

and lilo accepted the .conf file but the boot
ends in a kernel panic. I am running 15.0

the /etc/fstab file accepts the UUID entry
and works if the lilo.conf file uses /dev/sda1
instead of the UUID.

Thanks for any help.

[Marco Moock]

Post by root
and lilo accepted the .conf file but the boot
ends in a kernel panic. I am running 15.0

What is the message of that panic?

[root]

Post by Marco Moock

Post by root
and lilo accepted the .conf file but the boot
ends in a kernel panic. I am running 15.0

What is the message of that panic?

I can't see a way to literally capture the
Panic message, but it says cannot loak Block(0).
I take that as meaning it can't find the device?

[Marco Moock]

Post by root
Panic message, but it says cannot loak Block(0).
I take that as meaning it can't find the device?

Maybe. Check the configuration again.

[Henrik Carlqvist]

On Wed, 30 Nov 2022 06:34:42 +0000, root wrote:

I haven't tried it myself, still use good old /dev/sda for boot and /dev/
sda1 for root. However, it does seem as if lilo does have support for
uuid and that your syntax is correct.

I get conflicting answers from google. I tried a root = "UUID=........"
and lilo accepted the .conf file but the boot ends in a kernel panic.

My guess is that you wrote the uuid itself wrong.

the /etc/fstab file accepts the UUID entry and works if the lilo.conf
file uses /dev/sda1 instead of the UUID.

Maybe you can get it to work if you revert lilo.conf to /dev/sda1 and
then use the /usr/sbin/lilo-uuid-diskid utility and hope it gets it
right. There is also a man page for lilo-uuid-diskid.

regards Henrik

[root]

Post by Henrik Carlqvist
I haven't tried it myself, still use good old /dev/sda for boot and /dev/
sda1 for root. However, it does seem as if lilo does have support for
uuid and that your syntax is correct.

I get conflicting answers from google. I tried a root = "UUID=........"
and lilo accepted the .conf file but the boot ends in a kernel panic.

My guess is that you wrote the uuid itself wrong.

the /etc/fstab file accepts the UUID entry and works if the lilo.conf
file uses /dev/sda1 instead of the UUID.

Maybe you can get it to work if you revert lilo.conf to /dev/sda1 and
then use the /usr/sbin/lilo-uuid-diskid utility and hope it gets it
right. There is also a man page for lilo-uuid-diskid.
regards Henrik

Thanks Henrik, I only wanted to experiment with the UUID with lilo.
This isn't my main machine on which I use grub2 and UUID successfully.

Thanks for responding Henrik.

[Giovanni]

Post by root
I get conflicting answers from google. I tried
a root = "UUID=........"

The syntax you are using does not work in lilo.
You have to use disk/by-uuid syntax. e.g.

## /dev/md0: UUID="bc1274d8-cbb5-4130-bf9f-a00f998b64b6" TYPE="ext4"
boot = /dev/disk/by-uuid/bc1274d8-cbb5-4130-bf9f-a00f998b64b6

## root = /dev/md/root: UUID="e0004d10-1559-4392-bd97-01bde36df4e4"
root = /dev/disk/by-uuid/e0004d10-1559-4392-bd97-01bde36df4e4

Ciao
Giovanni

[root]

Post by Giovanni

Post by root
I get conflicting answers from google. I tried
a root = "UUID=........"

The syntax you are using does not work in lilo.
You have to use disk/by-uuid syntax. e.g.
## /dev/md0: UUID="bc1274d8-cbb5-4130-bf9f-a00f998b64b6" TYPE="ext4"
boot = /dev/disk/by-uuid/bc1274d8-cbb5-4130-bf9f-a00f998b64b6
## root = /dev/md/root: UUID="e0004d10-1559-4392-bd97-01bde36df4e4"
root = /dev/disk/by-uuid/e0004d10-1559-4392-bd97-01bde36df4e4
Ciao
Giovanni

Thanks Giovanni, that did the trick.