[Bug 207188] gptzfsboot may choose wrong pool

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207188

--- Comment #4 from Matthias Pfaller <matthias.pfaller at familie-pfaller.de> ---
(In reply to Andriy Gapon from comment #3)
>> But it might be nicer to skip pools without bootfs (imho).
> I think that that would not be unreasonable.
> But it certainly requires a wider discussion first, because there could be
> people who depend on the current behaviour in one way or another,

Maybe one should fall back to the old behaviour when no pool is marked with
bootfs.

>> The other thing I don't like, is that gptzfsboot doesn't seem to be able to
>> boot from a pool when there is only the zil on the boot device. It fails
>> with "all block copies unavailable". I think it should just skip a pool it
>> can't use anyway.
> Hmm, this is unexpected if other devices comprising the pool are fully  
> visible to the firmware (BIOS).  Could you please provide some more details?

All five disks (and the embedded micro-sdcard) are visible to the bios. 
zfsloader will list them as c:, d:, e:, f:, g: and h:.

But when gptzfsboot decides to boot from ada0:data (instead of ada0:root) it
will complain about "all block copies unavailable". 

Typing "status" at the gptzfsboot prompt will crash...

Please note that I had to patch zfsloader as described in
https://wiki.freebsd.org/HPBIOS3TBHDD. Maybe gptzfsboot needs the patch as
well?

-- 
You are receiving this mail because:
You are the assignee for the bug.