[Pkg-zfsonlinux-devel] Bug#962509: Not always boot arguments must include a root= parameter
kvaps
kvapss at gmail.com
Mon Sep 7 10:00:59 BST 2020
Hi Richard,
Thanks for your intention to help.
It seems I already found the correct solution for my case,
The problem persists only for the scripts/local, which is set by
default (BOOT=local)
We can review two cases where it might be caused:
1. LTSP and booting over the network
I implemented option to boot rootfs image over HTTP and it is
conflicting with scripts/local
https://github.com/ltsp/ltsp/pull/90
The solution was to implement another boot script
(scripts/ltsp-http) with empty functions
and call it by setting BOOT=ltsp-http
2. Root on ZFS. Mainly used in Ubuntu.
Another potential problem may occur if rootfs is located on ZFS.
ZFS does not require to set any specific root= to boot, but
scripts/local does.
Not sure if Ubuntu hackers solved this somehow for now.
Best Regards,
Andrei Kvapil
On Mon, Sep 7, 2020 at 7:33 AM Richard Laager <rlaager at wiktel.com> wrote:
>
> On Tue, 9 Jun 2020 01:25:58 +0200 kvaps <kvapss at gmail.com> wrote:
> > Package: initramfs-tools
> > Version: 0.133+deb10u1
> >
> > Hi, after the change introduced in f8ceeb90 both zfs and http booting
> > methods are not working anymore, it stops on the message:
> >
> > No root device specified. Boot arguments must include a root= parameter.
>
> Please add "debug" to your kernel command line*, reboot, and send me a
> copy of /run/initramfs/initramfs.debug.
>
> * If you're not sure how to do this: When you see GRUB, hit "e" to stop
> the timer and go into edit mode. Use the arrow keys to find the line
> starting with "linux" and navigate to the end of it. Add "debug" (no
> quotes). Press Ctrl-x or F10 to boot.
>
> --
> Richard
>
More information about the Pkg-zfsonlinux-devel
mailing list