> On 21. May 2024, at 23:21, Eric J Bowman via illumos-discuss > <discuss@lists.illumos.org> wrote: > > Jakey needs a new PDB before I can resume testing, but I already know I can > boot from USB to tribblix-sparc.iso on s0 (+34b). Question is, from there, > can I chainload into my rpool on s5, where altroot=SPARC? I know one rpool > can have alternate BE's, can they be different platforms? > > -Eric
Yes and no. from point of view of BE itself, sure, no problem. BE is just another filesystem and it really does not matter which platform it will serve. You need to be careful about different endians; I would rather suspect that sparc boot code does not check (and perform) the endian conversion; loader on x86 needs patch (from my queue;) to make it happen. It means, once you have either platform done with pool update, the other or neither is able to boot… (ok, with loader the code is already ready, so we can fix it for x86). rgds, toomas > > > > ---- On Tue, 21 May 2024 07:39:40 -0700 Eric J Bowman via illumos-discuss > <discuss@lists.illumos.org> wrote --- > > > > > When user did opt to use SMI label, we will create single > > Solaris2 MBR partition, with SMI label in it and slice 0 is > > created for boot pool. > > > > Thank you, Toomas! I think I understand. I'm installing rpool to a partition, > not "whole disk", under SMI. But, if the ESP is on the "active" partition, > once rpool boots, fdisk assumes it's a 100% EFI disk. This does not match > what it says in VTOC, so I get that i/o error? > > I need to leave the first 34 sectors in "no-man's land" though, not inside > the UEFI partition. Hmmm... "PMBCylinder", where fdisk partition 1 = PC98, > partition 2 = SOLARIS2, set partition 1 active and put ESP there, let > partition 2 be SMI with my rpool/zonepool partitioning? I believe that's my > way forward. > > -Eric > > > > ---- On Tue, 21 May 2024 06:29:22 -0700 Toomas Soome via illumos-discuss > <discuss@lists.illumos.org <mailto:discuss@lists.illumos.org>> wrote --- > > > > On 21. May 2024, at 16:02, Eric J Bowman via illumos-discuss > <discuss@lists.illumos.org <mailto:discuss@lists.illumos.org>> wrote: > > Changing my search from "multiboot interop" to "zfsboot interop" has proven > fruitful. I just need to know if this answer... > > " > Solaris by default will create EFI label when presented with whole disk > for zfs pool. The exception is when it's going to be used for boot (rpool), > on which it will use SMI label. > " > > ...is the *right* answer? It was written in 2011 in reference to Oracle ZFS. > > -Eric > > [1] https://github.com/openzfs/zfs/issues/94 > > > Oracle Solaris 11.4 does create EFI (GPT) label with slice 0 for whole disk > data pool, EFI (GPT) label with slice 0 for ESP and slice 1 for boot pool > (rpool) on UEFI system. On BIOS system, on boot disk, it will create > BIOS_boot partition + rpool partition, where BIOS_boot is used by grub2 as > raw space. > > On illumos, for boot disk, we do create EFI label with slice 0 for ESP and > slice 1 for boot pool (rpool). On BIOS system, the ESP is created, but not > used; the boot program is stored in zfs label boot program area. This allows > us to switch between UEFI and BIOS configuration (where supported). > > When user did opt to use SMI label, we will create single Solaris2 MBR > partition, with SMI label in it and slice 0 is created for boot pool. > > Thats about defaults. Then there are other options - we still can boot from > ufs, but since boot block area with ufs is very small, we need to use boot > slice (raw space), either in SMI label or in EFI label, but this is > no-default because boot environments (beadm) will not with ufs and you need > to set bootpath property with correct device name for rootfs mount to happen. > > rgds, > toomas > > > > > illumos <https://illumos.topicbox.com/latest> / illumos-discuss / see > discussions <https://illumos.topicbox.com/groups/discuss> + participants > <https://illumos.topicbox.com/groups/discuss/members> + delivery options > <https://illumos.topicbox.com/groups/discuss/subscription>Permalink > <https://illumos.topicbox.com/groups/discuss/T8c9973e131d44516-M346cdf9186395b0910d6e668> ------------------------------------------ illumos: illumos-discuss Permalink: https://illumos.topicbox.com/groups/discuss/T8c9973e131d44516-M35fe4843586d54f9fcd902b9 Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
