Comment 2 for bug 1872463

Our use case is that we test remote systems that have both physical USB sticks and virtual USB sticks so that we can validate both modes of operation (we're looking to validate specific platforms, not just the correctness of the installer). If we left an installer dd'd onto a physical stick and boot an installer over a virtual stick, we can hit this problem. Removing the physical stick (or destroying its contents, as @taihsiangho did in this case) would of course workaround the problem - but that assumes the user is able to recognize the cause.

One option might be to generate a /.disk/info-$(uuid) into the ISO and have grub search for that instead of the generic /.disk/info. Another might be to just provide a hint to the user on failure that multiple installation media maybe what blew things up.