Debian Bug report logs - #785149
grub-installer: NVMe boot drives not supported

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Steve Rowe <sarowe@gmail.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: grub-installer: NVMe boot drives not supported

Date: Tue, 12 May 2015 15:51:49 -0400

[Message part 1 (text/plain, inline)]

Package: debian-installer
Version: 20150422
Severity: critical
Tags: d-i patch
Justification: breaks the whole system

Dear Maintainer,

I used the Jessie DVD installer on a system with an NVMe SSD add-in-card (PCIe) that I wanted to make bootable, but there were two problems that halted the process:

1. In the install-the-base-system step, the initial ram disk creation step failed because it couldn't translate the nvme device name (nvme0n1p3) to the base name (nvme0n1).
2. In the boot loader installation step, the boot loader installation script again couldn't translate nvme0n1p3 to nvme0n1.

I reported #1, with a patch, at <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147>.

When I modified grub-installer to work with my NVMe disk, I missed the fact that it wasn't installed on permanent media, so I lost those changes.  The attached patch is my attempt at reconstructing what worked for me, so *please bear in mind that I have not tested it*.  One additional note: since I use the Linux kernel, my patch does not change the "hurd_convert" function, and looking at it, I'm guessing it should be modified too.

Steve Rowe

-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.2 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

[grub-installer.nvme.patch (text/x-diff, attachment)]

Message #10 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Cyril Brulebois <kibi@debian.org>

To: Steve Rowe <sarowe@gmail.com>, 785149@bugs.debian.org

Subject: Re: Bug#785149: grub-installer: NVMe boot drives not supported

Date: Tue, 12 May 2015 22:11:01 +0200

[Message part 1 (text/plain, inline)]

Control: reassign -1 grub-installer
Control: found -1 1.85
Control: severity important

Hi Steve,

Steve Rowe <sarowe@gmail.com> (2015-05-12):
> Package: debian-installer
> Version: 20150422
> Severity: critical
> Tags: d-i patch
> Justification: breaks the whole system

Failing to install isn't breaking the whole system. ;)

> Dear Maintainer,
> 
> I used the Jessie DVD installer on a system with an NVMe SSD add-in-card
> (PCIe) that I wanted to make bootable, but there were two problems that
> halted the process:
> 
> 1. In the install-the-base-system step, the initial ram disk creation step
> failed because it couldn't translate the nvme device name (nvme0n1p3) to the
> base name (nvme0n1).
> 
> I reported #1, with a patch, at <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147>.

ACK, thanks.

> 2. In the boot loader installation step, the boot loader installation
> script again couldn't translate nvme0n1p3 to nvme0n1.
> 
> When I modified grub-installer to work with my NVMe disk, I missed the
> fact that it wasn't installed on permanent media, so I lost those
> changes.  The attached patch is my attempt at reconstructing what
> worked for me, so *please bear in mind that I have not tested it*.
> One additional note: since I use the Linux kernel, my patch does not
> change the "hurd_convert" function, and looking at it, I'm guessing it
> should be modified too.

I'll have a look shortly and push something. Provided the patch for
#785147 is backported to jessie, we might do that as well.

Mraw,
KiBi.

[signature.asc (application/pgp-signature, inline)]

Message #23 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Cyril Brulebois <kibi@debian.org>

To: Steve Rowe <sarowe@gmail.com>, 785149@bugs.debian.org

Subject: Re: Bug#785149: grub-installer: NVMe boot drives not supported

Date: Tue, 12 May 2015 22:49:26 +0200

[Message part 1 (text/plain, inline)]

Control: tag -1 pending

Commenting on the patch now.

Steve Rowe <sarowe@gmail.com> (2015-05-12):
> -- System Information:
> Debian Release: 8.0
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.0.2 (SMP w/16 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)

> --- grub-installer-1.117/grub-installer	2015-01-12 23:01:14.000000000 -0500
> +++ grub-installer-1.117/grub-installer.fixed	2015-05-12 15:13:49.002358498 -0400
> @@ -134,7 +134,7 @@
>  # This should probably be rewritten using udevadm or similar.
>  device_to_disk () {
>  	echo "$1" | \
> -		sed 's:\(/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'
> +		sed 's:\(/dev/nvme[0-9]n[0-9]\|/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'

I moved the addition to the end, which makes visual inspection slightly
easier. I also made it possible to support multi-digit X and Y in
/dev/nvmeXnY (my second patch).

It seems other devices have inconsistent support for that BTW. I'm not
sure I'm going to dive into that right now though. ISTR Ben's mentioning
we might want to revisit this thing entirely at some point.

>  # Run update-grub in $ROOT
> @@ -252,7 +252,7 @@
>      /dev/mapper)
>  	disc_offered_devfs="$bootfs"
>  	;;
> -    /dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)
> +    /dev/nvme[0-9]n[0-9]|/dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)

Same story here.

>  	disc_offered_devfs="$prefix"
>  	;;
>      *)
> @@ -895,6 +895,10 @@
>  	disk=
>  	part=
>  	case $1 in
> +                /dev/nvme*n*p*)
> +			disk="$(echo "$1" | sed 's,\(/dev/nvme[0-9]n[0-9]\).*,\1,')"
> +			part="$(echo "$1" | sed 's,/dev/nvme[0-9]n[0-9]\(.*\),\1,')"
> +			;;
>  		/dev/[vhs]d[a-z]*)
>  			disk="$(echo "$1" | sed 's,\(/dev/[a-z]\+\).*,\1,')"
>  			part="$(echo "$1" | sed 's,/dev/[a-z]\+\(.*\),\1,')"

Moved the addition to the end of the block as well, but I mimicked the
/dev/mmcblk case a bit more closely, matching for [0-9]+ after “p”
instead of “everything”; also supporting multi-digit X and Y as above.
I also added an extra check on "$part" vs "$1" as done in the mmcblk
case.

I haven't performed any tests at all (even with a regular /dev/sda
setup) though, only pushed to master:
  https://anonscm.debian.org/cgit/d-i/grub-installer.git/commit/?id=beca4ad
  https://anonscm.debian.org/cgit/d-i/grub-installer.git/commit/?id=7046795

Mraw,
KiBi.

[signature.asc (application/pgp-signature, inline)]

Message #30 received at 785149-close@bugs.debian.org (full text, mbox, reply):

From: Christian Perrier <bubulle@debian.org>

To: 785149-close@bugs.debian.org

Subject: Bug#785149: fixed in grub-installer 1.122

Date: Wed, 13 May 2015 05:18:44 +0000

Source: grub-installer
Source-Version: 1.122

We believe that the bug you reported is fixed in the latest version of
grub-installer, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 785149@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Perrier <bubulle@debian.org> (supplier of updated grub-installer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 13 May 2015 06:57:05 +0200
Source: grub-installer
Binary: grub-installer
Architecture: source i386
Version: 1.122
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Christian Perrier <bubulle@debian.org>
Description:
 grub-installer - Install GRUB on a hard disk (udeb)
Closes: 785149
Changes:
 grub-installer (1.122) unstable; urgency=medium
 .
   [ Cyril Brulebois ]
   * Add support for /dev/nvme* devices (NVMe SSD Add-in-Card devices),
     by mimicking what is already done in the /dev/mmcblk* case. Thanks to
     Steve Rowe for the report and the initial patch! (Closes: #785149)
Checksums-Sha1:
 da73c8bc40cecfaf792ad416c4d334b18af787cd 1938 grub-installer_1.122.dsc
 42fcbb3e50405df220502664b3e6cccdbd0e8a8f 209760 grub-installer_1.122.tar.xz
 c81a353d4cffd6af1cb5b1a0c8e855ec526fad4a 284580 grub-installer_1.122_i386.udeb
Checksums-Sha256:
 7cb75584978437e2847f97c9a1acf0010f905723b570de7a5f531b4218814e83 1938 grub-installer_1.122.dsc
 6c3332f12d58d45f81d4042a36c932147871b73c49c8248d97500b03f34b5693 209760 grub-installer_1.122.tar.xz
 ca6f37cb5680022e3df2a3b841a14030556427f2df63d60cf3a186af793162ee 284580 grub-installer_1.122_i386.udeb
Files:
 20b82a836bee20aa312d85433cb3ae55 1938 debian-installer standard grub-installer_1.122.dsc
 eb3b5a70fa80fefffc9064345b2ec074 209760 debian-installer standard grub-installer_1.122.tar.xz
 edf99864d0730f58ed2a625c2cfdb915 284580 debian-installer standard grub-installer_1.122_i386.udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVUtpDAAoJEIcvcCxNbiWoT1UP/Amh1hOlR2We58atQC91KVMP
/i6ypR2VSG9Vk5HGBMZaPl0JpBkd4IPtsZl7BC4bnYpUdXdlbl3aS6HKicI94dXQ
3bUwHDmPgkZpAlurG4dHmayOe8SY5VYdE7TpSvXTxHkzwkCxAuMvo2AqOtaakxhO
f+Lcj4+TxA36VT0aJ7n1HUB/gfcVRRUU7ZB+9XSgVwGclY5KkEOewn6knvetXIL1
DOn+8YTDNgOBxgdwXOr8l4romqYOpkgvbbAUn4a+fZXWLdcWNvs0oU46sRp1wDh+
fUAIMsep7fNKUPqnDpbwsnK5yI4cQrsw0kCmQOUVGD4t8a1BlfnJq9lvhWfzSjyv
3L1pXraJpIrhLj8GBPmJTgGEYSJkQ7gJmVKA8n1eAK4a43eDU05YJUs9dPnL5WkG
1BM9xQvZLSRtOuFsXEZKvqymqMJu1eCWBqZKhg1AXYNM+zmT8kwkB91vzOHRVUu5
EeSHuW8sSlDxSu+TbrfwNRrpCoi/yaTjqRjNN2r3VY1xc+W386rOXLSn/wmlf1WX
STMipb744UBKBvDi6DRPedNNPzD2c7Z04wVrUnOPXe+SeVGmg7jdEgOcuQHRQFru
TU9J8WhY4J/5voUdd6De4P/i2tZn2/fbdaedkg8daLVTebpM3IUW28awzffhWk8k
rw86p94SlGi7UnKOHkKB
=+ASx
-----END PGP SIGNATURE-----

Message #35 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Steve Rowe <sarowe@gmail.com>

To: 785149@bugs.debian.org

Subject: Re: Bug#785149: grub-installer: NVMe boot drives not supported

Date: Wed, 27 May 2015 10:30:38 -0400

I just realized that an out-of-band email thread I had with Cyril didn’t make it to this issue - here’s the final email to me from Cyril:

-----
Steve Rowe <sarowe@gmail.com> (2015-05-12):
> 
>> On May 12, 2015, at 4:49 PM, Cyril Brulebois <kibi@debian.org> wrote:
>>> --- grub-installer-1.117/grub-installer	2015-01-12 23:01:14.000000000 -0500
>>> +++ grub-installer-1.117/grub-installer.fixed	2015-05-12 15:13:49.002358498 -0400
>>> @@ -134,7 +134,7 @@
>>> # This should probably be rewritten using udevadm or similar.
>>> device_to_disk () {
>>> 	echo "$1" | \
>>> -		sed 's:\(/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'
>>> +		sed 's:\(/dev/nvme[0-9]n[0-9]\|/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'
>> 
>> I moved the addition to the end, which makes visual inspection slightly
>> easier.
> 
> There’s a problem with this: the preceding pattern "/dev/[a-z]\+" will match "/dev/nvme.*”, so the nvme pattern will never be reached. 

Good catch, pushed this extra commit accordingly:
 https://anonscm.debian.org/cgit/d-i/grub-installer.git/commit/?id=22a8aef

>>> # Run update-grub in $ROOT
>>> @@ -252,7 +252,7 @@
>>>    /dev/mapper)
>>> 	disc_offered_devfs="$bootfs"
>>> 	;;
>>> -    /dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)
>>> +    /dev/nvme[0-9]n[0-9]|/dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)
>> 
>> Same story here.
> 
> Looks like there is no general pattern that will match “/dev/nvme.*”
> above, so putting it at the end isn’t a problem.

Adjusted for consistency.

Thanks again!

Mraw,
KiBi.
-----

Message #44 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Matteo Checcucci <matteo.checcucci@tgroup.unifi.it>

To: Steve Rowe <sarowe@gmail.com>, 785149@bugs.debian.org

Subject: Re: Re: Bug#785149: grub-installer: NVMe boot drives not supported

Date: Thu, 3 Dec 2015 16:28:32 +0100

Control: found -1 grub-installer/1.122


On 05/27/2015 04:30 PM, Steve Rowe wrote:
> I just realized that an out-of-band email thread I had with Cyril didn’t make it to this issue - here’s the final email to me from Cyril:
>
> -----
> Steve Rowe <sarowe@gmail.com> (2015-05-12):
>>
>>> On May 12, 2015, at 4:49 PM, Cyril Brulebois <kibi@debian.org> wrote:
>>>> --- grub-installer-1.117/grub-installer	2015-01-12 23:01:14.000000000 -0500
>>>> +++ grub-installer-1.117/grub-installer.fixed	2015-05-12 15:13:49.002358498 -0400
>>>> @@ -134,7 +134,7 @@
>>>> # This should probably be rewritten using udevadm or similar.
>>>> device_to_disk () {
>>>> 	echo "$1" | \
>>>> -		sed 's:\(/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'
>>>> +		sed 's:\(/dev/nvme[0-9]n[0-9]\|/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'
>>>
>>> I moved the addition to the end, which makes visual inspection slightly
>>> easier.
>>
>> There’s a problem with this: the preceding pattern "/dev/[a-z]\+" will match "/dev/nvme.*”, so the nvme pattern will never be reached.
>
> Good catch, pushed this extra commit accordingly:
>   https://anonscm.debian.org/cgit/d-i/grub-installer.git/commit/?id=22a8aef
>
>>>> # Run update-grub in $ROOT
>>>> @@ -252,7 +252,7 @@
>>>>     /dev/mapper)
>>>> 	disc_offered_devfs="$bootfs"
>>>> 	;;
>>>> -    /dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)
>>>> +    /dev/nvme[0-9]n[0-9]|/dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)
>>>
>>> Same story here.
>>
>> Looks like there is no general pattern that will match “/dev/nvme.*”
>> above, so putting it at the end isn’t a problem.
>
> Adjusted for consistency.

I installed Debian testing on a PC with NVMe Samsung 950 Pro as boot
disk.
I had to manually modify grub-installer (with nano within the d-i 
console), because it was failing.

The problem seems to be the following.
In the commit
https://anonscm.debian.org/cgit/d-i/grub-installer.git/commit/?id=22a8aef
there are two changes: the first one is for a sed command line and is 
OK. The second one is for a case command. In the case command the syntax 
is file globbing, not regular expression.
So, the * is interpreted differently.

In my opinion, in the case command

  /dev/nvme[0-9][0-9]*n[0-9][0-9]*

should be replaced by

  /dev/nvme[0-9]*n[0-9]*

This will result in actual consistency with the sed command.



N.B.: I personally tested the grub-installer script modified as 
previously proposed:

 sed 
's:\(/dev/nvme[0-9]n[0-9]\|/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'

and

/dev/nvme[0-9]n[0-9]|/dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)

It works.



Please fix the case command in grub-installer, so that next time someone 
installs Debian testing on an NVMe disk it will work without modifications.

Thanks!

Message #51 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Jeremy Ellison <jeremy.ellison@washburn.edu>

To: <785149@bugs.debian.org>

Subject: NVME and the Debian Installer 8.2.0

Date: Tue, 29 Dec 2015 13:44:41 -0600

[Message part 1 (text/plain, inline)]

I was trying to get a new NVME drive working and install Debian Stable on
it. I realized after my first failure that my image might be too old, and
got a copy of 8.2.0. It also failed on the grub-installer. I see there has
been some success since I last checked, is there any version of the stable
install image I should keep an eye out for so I can finish my install?

[Message part 2 (text/html, inline)]

Message #56 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Z G <ztg007@gmail.com>

To: 785149@bugs.debian.org

Subject: Re: Bug#785149: grub-installer: NVMe boot drives not supported

Date: Wed, 27 Jan 2016 21:52:51 -0500

[Message part 1 (text/plain, inline)]

Hi,

Following up on Jeremy's question above, does Debian 8.3.0 (image as of
early 2016) include a fix?

Alternatively, could someone (Matteo?) indicate the steps to fix this
during the install process? Not sure if you're patching the installer code
and recompiling during the install process or something else.

Thanks,
Z

[Message part 2 (text/html, inline)]

Message #61 received at 785149@bugs.debian.org (full text, mbox, reply):

From: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>

To: Z G <ztg007@gmail.com>, 785149@bugs.debian.org

Subject: Re: Bug#785149: grub-installer: NVMe boot drives not supported

Date: Thu, 28 Jan 2016 11:42:19 -0500

On Wed, Jan 27, 2016 at 09:52:51PM -0500, Z G wrote:
> Following up on Jeremy's question above, does Debian 8.3.0 (image as of
> early 2016) include a fix?
> 
> Alternatively, could someone (Matteo?) indicate the steps to fix this
> during the install process? Not sure if you're patching the installer code
> and recompiling during the install process or something else.

I tried with the stretch installer in late December, and that worked
on NVMe (which is good since this was a few weeks after it was supposed
to have been fixed).  I tested on a Samsung 950 Pro 256GB M.2 on an
Asus Z170-A.

It did not occur to me to test the jessie installer since I simply
assumed it didn't do NVMe.  Also I was under the impression that there
are issues with the graphics in the skylake CPUs that needed a 4.3+
kernel, which ruled out Jessie for that machine.

According to
http://www.poweredbyjeff.com/2015/10/29/Intel-750-SSD-in-Debian-Jessie/ it
needs a backported grub and kernel to work properly in Jessie.  Not sure.
It does have steps that is says works.

Of course if the kernel has some issues with NVMe, then I suspect getting
jessie fixed isn't that likely, but at least backports for the kernel
is still an option then.

-- 
Len Sorensen

Message #66 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Jeremy Ellison <ellison.jeremy@gmail.com>

To: 785149@bugs.debian.org

Subject: NVME and a future Debian Installer

Date: Fri, 5 Feb 2016 10:26:02 -0600

[Message part 1 (text/plain, inline)]

Please consider adding this to the Jessie installer? I have followed those
instructions on an existing install, and since it was booted using BIOS
compatibility I can't set the EFI variables. I have GRUB2 configured, but
when booted it can't find the device.

This would be easily resolved with the fixes backported to the Jessie
install image. I'm not sure about the newer kernel, but I see no reason why
the stable kernel is an issue?

[Message part 2 (text/html, inline)]

Message #71 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Cyril Brulebois <kibi@debian.org>

To: Jeremy Ellison <ellison.jeremy@gmail.com>, 785149@bugs.debian.org

Subject: Re: Bug#785149: NVME and a future Debian Installer

Date: Fri, 5 Feb 2016 18:08:30 +0100

[Message part 1 (text/plain, inline)]

Jeremy Ellison <ellison.jeremy@gmail.com> (2016-02-05):
> Please consider adding this to the Jessie installer? I have followed those
> instructions on an existing install, and since it was booted using BIOS
> compatibility I can't set the EFI variables. I have GRUB2 configured, but
> when booted it can't find the device.
> 
> This would be easily resolved with the fixes backported to the Jessie
> install image. I'm not sure about the newer kernel, but I see no reason why
> the stable kernel is an issue?

Well, I seem to have botched the patches when merging them, and I was
awaiting confirmation through stretch alpha releases that support is
now properly working.

Possibly getting this backported is on my todo list, but said list
isn't exactly empty.

Mraw,
KiBi.

[signature.asc (application/pgp-signature, inline)]

Message #76 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Jeremy Ellison <jeremy.ellison@washburn.edu>

To: <785149@bugs.debian.org>, Cyril Brulebois <kibi@debian.org>

Subject: Re: NVME and a future Debian Installer

Date: Fri, 5 Feb 2016 15:12:34 -0600

[Message part 1 (text/plain, inline)]

A thousand times, Thank you! I always appreciate all of the Debian team's
hard work! I'll be patient, and thank you for the confirmation that Jessie
will get this feature as well. (I like to live one or two releases back if
possible)

On Fri, Feb 5, 2016 at 10:26 AM, Jeremy Ellison <ellison.jeremy@gmail.com>
wrote:

> Please consider adding this to the Jessie installer? I have followed those
> instructions on an existing install, and since it was booted using BIOS
> compatibility I can't set the EFI variables. I have GRUB2 configured, but
> when booted it can't find the device.
>
> This would be easily resolved with the fixes backported to the Jessie
> install image. I'm not sure about the newer kernel, but I see no reason why
> the stable kernel is an issue?
>

[Message part 2 (text/html, inline)]

Message #81 received at 785149@bugs.debian.org (full text, mbox, reply):

From: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>

To: Cyril Brulebois <kibi@debian.org>, 785149@bugs.debian.org

Cc: Jeremy Ellison <ellison.jeremy@gmail.com>

Subject: Re: Bug#785149: NVME and a future Debian Installer

Date: Fri, 5 Feb 2016 17:32:29 -0500

On Fri, Feb 05, 2016 at 06:08:30PM +0100, Cyril Brulebois wrote:
> Well, I seem to have botched the patches when merging them, and I was
> awaiting confirmation through stretch alpha releases that support is
> now properly working.
> 
> Possibly getting this backported is on my todo list, but said list
> isn't exactly empty.

I successfully installed stretch at the end of December on NVMe.  So yes
the fixes that were done for stretch worked.  grub installed with
no problem.  So my test was shortly after Bug 799119 was fixed in
grub-installer 1.128.  I specifically tried it to check since I was
putting together a machine with the right hardware to test it even though
that machine was actually going to run windows 10.

-- 
Len Sorensen

Message #86 received at 785149@bugs.debian.org (full text, mbox, reply):

From: "Seidi, Stevenson" <s.seidi@unesco.org>

To: "Seidi, Stevenson" <s.seidi@unesco.org>

Subject: RE: Donation To You

Date: Thu, 26 May 2016 01:45:26 +0000

[Message part 1 (text/plain, inline)]

________________________________
From: Seidi, Stevenson
Sent: Thursday, May 26, 2016 2:10 AM
To: Seidi, Stevenson
Subject: Donation To You

Donation to you, contact David and Carol Martin  on   davidandcarolmartin4@gmail.com<mailto:davidandcarolmartin4@gmail.com> for more info

[Message part 2 (text/html, inline)]

Message #91 received at 785149@bugs.debian.org (full text, mbox, reply):

From: AKU KENNEDY <akukennedy8@gmail.com>

To: undisclosed-recipients:;

Subject: r

Date: Mon, 22 Aug 2016 09:02:47 +0000

[Message part 1 (text/plain, inline)]

[Message part 2 (text/html, inline)]

[Hello friend.pdf (application/pdf, attachment)]

Message #96 received at 785149@bugs.debian.org (full text, mbox, reply):

From: 张明杰 <mingjiezhang1000@gmail.com>

To: undisclosed-recipients:;

Subject: Dear Jeremy

Date: Tue, 11 Oct 2016 17:12:02 +0800

[Message part 1 (text/plain, inline)]

[image: Inline image 1]

[Message part 2 (text/html, inline)]

[image.png (image/png, inline)]

Message #101 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Sandra Head <head.sandra@bsd.ca>

To: "Noreply@ik.com" <Noreply@ik.com>

Subject: RE

Date: Tue, 24 Jan 2017 14:26:42 +0000

[Message part 1 (text/plain, inline)]

Hi Dear, I have a Proposal for you, Get back to me via: frymayy@gmail.com

________________________________
CONFIDENTIALITY NOTICE: This message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient you are hereby notified that any dissemination, distribution or copying of this transmission is prohibited. If you have received this transmission in error, please notify us immediately by return telephone, fax or email, and destroy the transmission by deleting the file and/or shredding any paper copy.

[Message part 2 (text/html, inline)]

Message #106 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Sandra Head <head.sandra@bsd.ca>

To: "Noreply@lk.com" <Noreply@lk.com>

Subject: RE

Date: Tue, 24 Jan 2017 17:45:33 +0000

[Message part 1 (text/plain, inline)]

Hi Dear, I have a Proposal for you, Get back to me via: frymayy@gmail.com

________________________________
CONFIDENTIALITY NOTICE: This message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient you are hereby notified that any dissemination, distribution or copying of this transmission is prohibited. If you have received this transmission in error, please notify us immediately by return telephone, fax or email, and destroy the transmission by deleting the file and/or shredding any paper copy.

[Message part 2 (text/html, inline)]

Message #111 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Sandra Head <head.sandra@bsd.ca>

To: "Noreply@lk.com" <Noreply@lk.com>

Subject: re

Date: Wed, 25 Jan 2017 12:46:01 +0000

[Message part 1 (text/plain, inline)]

Hi Dear, I have a Proposal for you, Get back to me via: frymayy@gmail.com

________________________________
CONFIDENTIALITY NOTICE: This message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient you are hereby notified that any dissemination, distribution or copying of this transmission is prohibited. If you have received this transmission in error, please notify us immediately by return telephone, fax or email, and destroy the transmission by deleting the file and/or shredding any paper copy.

[Message part 2 (text/html, inline)]

Message #116 received at 785149@bugs.debian.org (full text, mbox, reply):

From: geoffroy desvernay <dgeo@centrale-marseille.fr>

To: 785149@bugs.debian.org

Subject: patch working (and missing) on jessie

Date: Fri, 17 Mar 2017 16:34:13 +0100

[Message part 1 (text/plain, inline)]

Hi all,

Found this bug after trying to install "as usual" (network preseed) new
machines here.

Just to report that patching /usr/bin/grub-installer manually in d-i
works (and resulting debian works flawlessly with standard kernel)

Do you think backporting this to jessie will take time ? It would allow
me not to replace ~30 working disks on new machines :-/

Anyway, thank you all for inputs here !!
-- 
*geoffroy desvernay*
C.R.I - Administration systèmes et réseaux
Ecole Centrale de Marseille

[signature.asc (application/pgp-signature, attachment)]

Message #121 received at 785149@bugs.debian.org (full text, mbox, reply):

From: geoffroy desvernay <dgeo@centrale-marseille.fr>

To: 785149@bugs.debian.org

Subject: Re: patch working (and missing) on jessie

Date: Mon, 20 Mar 2017 12:23:26 +0100

[Message part 1 (text/plain, inline)]

If it can help, this can be worked arount by using testing installer to
install jessie.

Using in preseed.cfg:
d-i mirror/codename string jessie
d-i mirror/udeb/suite string stretch

This way I can wait for this fix to get in stable ;)
-- 
*geoffroy desvernay*
C.R.I - Administration systèmes et réseaux
Ecole Centrale de Marseille

[signature.asc (application/pgp-signature, attachment)]

Message #126 received at 785149@bugs.debian.org (full text, mbox, reply):

From: Carl Karsten <carl@personnelware.com>

To: 785149@bugs.debian.org

Subject: grub installer failing on nvme0n1

Date: Wed, 19 Apr 2017 01:56:28 -0500

[Message part 1 (text/plain, inline)]

Looks like the same problem.
I am running a preseeded instal of stretch.

If someone can provide a preseed file for me to test with I can give
it a go, or try to collect my setup and post.


-- 
Carl K

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.