Bug#766920: produces unbootable initramfs with lilo hexadecimal syntax (root=803)
On Sat, 17 Jan 2015 16:06:15 +0000
Ben Hutchings <ben@decadent.org.uk> wrote:
> Control: tag -1 moreinfo
>
> I'm unable to reproduce the numeric root in /etc/mtab. I tried using
> lilo with a non-UUID root, using the Debian packaged kernel and then
> with a custom kernel with no initramfs. In both cases I see / mounted
> from /dev/root and that device node does exist. I also tested using
> both systemd and sysvinit. In all cases /etc/mtab is a symlink
> to /proc/mounts (as both init systems create it).
I think it is a misunderstanding. I created a symlink in the root
directory (mind, in the meantime I changed to sda5 instead of sda3):
# ln -s /dev/sda3 /805
# ls -al /805
lrwxrwxrwx 1 root root 9 Jan 17 21:41 /803 -> /dev/sda5
> - Did you boot from an initramfs before running update-initramfs?
Yes, it's a Debian testing distro, using the debian kernels
> - Which init system are you using, and which version of it?
I use sysv-init
> - Is /etc/mtab a regular file or symlink?
It is a symlink to /proc/mounts as expected. But: I use lilo, not grub.
And this is what I can reproduce, the issue is in lilo.conf:
boot=/dev/sda
map=/boot/map
delay=20
compact
prompt
timeout=20
default=Linux-nosd
image=/vmlinuz
label=Linux-nosd
root="UUID=d94d08f7-4b3d-47be-acaf-d425e71efece"
read-only
initrd=/initrd.img
image=/vmlinuz
label=test-805
root=/dev/sda5
read-only
initrd=/initrd.img
When I choose "Linux-nosd" using "root=UUID", the system boots and a
mount shows this:
/dev/sda5 on / type ext4 (rw,noatime,nodiratime,discard,data=ordered)
mtab:
rootfs / rootfs rw 0 0
/dev/disk/by-uuid/d94d08f7-4b3d-47be-acaf-d425e71efece / ext4
rw,noatime,nodiratime,discard,data=ordered 0 0
When a new initrd.img is generated by apt, everything is ok.
When I choose "test-805" using "root=/dev/sda5", the system boots, but
"mount" shows:
805 on / type ext4 (rw,noatime,nodiratime,discard,data=ordered)
mtab:
rootfs / rootfs rw 0 0
/dev/root / ext4 rw,noatime,nodiratime,discard,data=ordered 0 0
The problem finally occurs when I boot "test-805" and apt produces a new
initrd.img. With the generated initrd.img the system refuses to boot. A
workaround is:
# ln -s /dev/sda5 /805
Please note that I'd rather do not test an update-initramfs as I have
to take the HDD out of the laptop and "lilo" it manually on other
sytem ;-)
HTH, if I can so some further tests, I's be at your service :)
R.
--
___________________________________________________________________
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.
+------------------------------------------------------------------+
| Richard Lucassen, Utrecht |
+------------------------------------------------------------------+
Reply to: