On Fri, Jul 20, 2018 at 08:47:05AM +0200, Romain Dolbeau wrote:
> t5120:~$ dpkg -l '*grub*' | grep ^ii
> ii  grub-common       2.02+dfsg1-4 sparc64      GRand Unified
> Bootloader (common files)
> ii  grub-ieee1275     2.02+dfsg1-4 sparc64      GRand Unified
> Bootloader, version 2 (Open Firmware version)
> ii  grub-ieee1275-bin 2.02+dfsg1-4 sparc64      GRand Unified
> Bootloader, version 2 (Open Firmware binaries)
> ii  grub2-common      2.02+dfsg1-4 sparc64      GRand Unified
> Bootloader (common files for version 2)

Okay, that matches mine.  Thanks.

> > and show me how your disk is labeled/partitioned?
> Device      Start       End   Sectors   Size Id Type       Flags
> /dev/sdd1       0    192779    192780  94.1M  1 Boot
> /dev/sdd2  192780 286707979 286515200 136.6G  0 Unassigned
> /dev/sdd3       0 286728119 286728120 136.7G  5 Whole disk
> Pool on sdd2, of course.

Interesting.  What tool is showing that?  I have been using parted, which
shows (for my first ZFS disk):

Number  Start  End    Size   File system  Flags
 1      0.00B  502MB  502MB  ext2         boot
 2      502MB  147GB  146GB  zfs

So, other than the different format, I notice:
1) I show ZFS where your sdd2 shows "Unassigned"
2) You have a 'c' whole disk partition, and I don't.  I wonder if that's
3) You have an "Id" field [in your tools output] that I don't.

> Available on <http://www.dolbeau.name/dolbeau/files/grub.cfg>

Thanks.  There are a few differences compared to mine, notably that the
"search" lines in your menuentry have a UUID of all 9's, and mine has a
UUID.  And I have hd0/ahci0 vs your hd3/ahci3, but that is expected.  I
also see that I'm due a kernel update (my grub.cfg still lists 4.16.0-2),
but since I'm not getting a kernel loaded at all, that's not my problem.

> BTW, when I installed the system, I had the sdd1 /boot mounted on
> /mnt/boot (ZFS root on /mnt).
> After doing "grub-mkconfig -o /boot/grub/grub.cfg" (in chroot) the
> pool name was missing in grub.cfg, only the dataset name was there. I
> added the pool name by hand.
> Then "grub-install --force  --skip-fs-probe /dev/sdd1" (also in chroot).
> Don't remember anything special beyond that ... and a bit of elbow
> grease :-) (several reboots to add the network interface
> configuration, the console, right klibc, ...).

Yeah.  This is about the same as what I've tried, but I'm not even able
to have grub load from the disk in my case.  I've been thinking about 
booting back to "reinstall the whole thing from CD", since my original
install was many months ago, but haven't done that yet.

Adrian, the ISOs I see still are dated mid-May.  Let me know if you may
have time to regenerate those at some point.

Thanks Romain.

         - Chris

Reply via email to