Re: Updated installer images 2021-04-16
On Wed, Apr 21, 2021, at 4:26 AM, John Paul Adrian Glaubitz wrote:
> >> This issue might not even specific to PowerMacs, so it
> >> would make more
> >> sense first to test this on x86 systems and report a bug against
> >> src:grub2 or partman-lvm
> >> if the issue shows there as well.
> >
> > I'll try that. Would the "daily build" sid iso for amd64 have the same version of grub2 as your ppc64 iso?
>
> This should do the trick, yes:
>
> > https://cdimage.debian.org/cdimage/daily-builds/daily/current/amd64/iso-cd/
I just tried that on an amd64 VM. I chose the default install from the installer's menu. When it got to partitioning the disk, I chose use whole disk and set up LVM. I chose separate /home logical volume. All went well, and when it came to reboot from the newly installed disk, I did not see any of the messages that I saw on the ppc64 PowerMac G5 install. However:
The amd64 install created a separate /boot partition on /dev/sda1. In addition to kernel and initrd, it contained a /boot/grub directory.
> rbthomas@burnout:~$ df | grep -v tmpfs ; lsblk
> Filesystem 1K-blocks Used Available Use% Mounted on
> udev 1995140 0 1995140 0% /dev
> /dev/mapper/burnout--vg-root 6930164 962864 5593952 15% /
> /dev/sda1 480618 48562 407122 11% /boot
> /dev/mapper/burnout--vg-home 12028924 40 11396052 1% /home
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> sda 8:0 0 20G 0 disk
> |-sda1 8:1 0 487M 0 part /boot
> |-sda2 8:2 0 1K 0 part
> `-sda5 8:5 0 19.5G 0 part
> |-burnout--vg-root 254:0 0 6.8G 0 lvm /
> |-burnout--vg-swap_1 254:1 0 976M 0 lvm [SWAP]
> `-burnout--vg-home 254:2 0 11.8G 0 lvm /home
> sr0 11:0 1 1024M 0 rom
> rbthomas@burnout:~$
The ppc64 install, on the other hand, created a separate hfs type /boot/grub partition on /dev/sda2, and let the parent /boot be a directory in the ext4 root partition/logical-volume
> rbthomas@kmac:~$ df | grep -v tmpfs ; lsblk
> Filesystem 1K-blocks Used Available Use% Mounted on
> udev 1874880 0 1874880 0% /dev
> /dev/mapper/kmac--vg-root 19047080 1372148 16682064 8% /
> /dev/sda2 249988 11228 238760 5% /boot/grub
> /dev/mapper/kmac--vg-home 158766164 60 150628376 1% /home
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> sda 8:0 0 232.9G 0 disk
> |-sda1 8:1 0 31.5K 0 part
> |-sda2 8:2 0 244.1M 0 part /boot/grub
> |-sda3 8:3 0 232.6G 0 part
> | |-kmac--vg-root 254:1 0 18.6G 0 lvm /
> | |-kmac--vg-swap_1 254:2 0 10G 0 lvm [SWAP]
> | `-kmac--vg-home 254:3 0 154.9G 0 lvm /home
> `-sda4 8:4 0 56.5K 0 part
> sdb 8:16 0 931.5G 0 disk
> `-backup-lvol0 254:0 0 500G 0 lvm
> sr0 11:0 1 1024M 0 rom
> rbthomas@kmac:~$
I suspect that this difference is what's producing the "error: can't open device" messages on the ppc64, and why they do not appear on the amd64. If I did a manual partitioning install on the amd64 that mimicked the layout of the ppc64, I suspect I would probably see the same "can't open device" error messages there as well. (I do plan to try that, and I'll report what I find)
Rick
Reply to: