Hi Josep,

On Thu, Aug 08, 2019 at 12:12:34PM +0200, Josep Guerrero Sole wrote:
>Package: cdrom
>Severity: important
>Tags: d-i
>
>-- System Information:
>Debian Release: 9.9
>  APT prefers oldstable
>  APT policy: (500, 'oldstable')
>Architecture: amd64 (x86_64)
>Foreign Architectures: i386
>
>Kernel: Linux 4.9.0-9-amd64 (SMP w/8 CPU cores)
>Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), 
>LANGUAGE=ca:en_US:es:en_GB (charmap=UTF-8)
>Shell: /bin/sh linked to /bin/dash
>Init: systemd (via /run/systemd/system)
>
>Since the problem prevents me from installing the system, I'm writing
>the bug report from another system, so the automatically gathered
>data above is not correct.
>
>The correct values (those that I know) are:
>
>Debian Release: 10.0
>Architecture: amd64 (x86_64)
>Kernel: Linux 4.19.0-5-amd64
>
>I'm trying to install Debian Buster on a system with 1 500GB NVMe
>disk (intended to be the system and boot disk) and 4 12TB disks
>intended to store data.
>
>When partitioning the NVME disk, I create a 1GB EPS partition and a
>1GB grubbios partition. The rest of the disk is configured as a RAID1
>partition (it will only have one component, but I may be able to add
>a second disk later, so I prefer configuring it as a RAID from the
>beginning). The RAID partition is then configured as an LVM physical
>volume which ends as the only physical volume of a LVM volume group,
>which is further partitioned into several logical volumes to be
>mounted on some system directories (/, /tmp, /usr, /var, swap, ...).

OK, that makes sense.

>The 4 12TB disks are partitioned with just one Linux raid partition,
>and the 4 of them are configured as a RAID6 device, that again is
>configured as an LVM physical volume which ends as the only component
>of another volume group, with just one logical volume.
>
>The whole installation seems to work flawlessly, but when installing
>the grub boot loader, I get the error:
>
>grub-install dummy failed
>
>In the syslog, I can find the message
>
>grub-install: error: failed to get canonical path of `/dev/nvme0n1p1`
>
>Executing manually:
>
>chroot /target grub-install --force "dummy"
>
>results in exactly the same message. As a result, I am unable to
>install the system.
>
>This bug seems to have appeared in some Ubuntu forums, and there is a
>sort of workaround in this comment:
>
>https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1507505/comments/25
>
>but I would prefer avoiding creating the eps partition on the 12TB
>disks (I would have to do that on all the disks to keep the raid
>partitions the same size).

You don't describe the system hardware that you're working with. What
do you have? This sounds like *potentially* a firmware issue, but it's
not 100% clear yet.

When you tried to run grub-install by hand, did you have /dev and
/sys mounted ok in the chroot? If you could try again and add a "-v"
to the grub-install command line that will give us more
information. It *will* be verbose, but only the last few lines are
likely to matter.

-- 
Steve McIntyre, Cambridge, UK.                                st...@einval.com
"Because heaters aren't purple!" -- Catherine Pitt

Reply via email to