On Jun 26, 2017, at 4:40 AM, Theodore Ts'o <tytso@xxxxxxx> wrote: > On Sun, Jun 25, 2017 at 08:16:39PM +0200, Felipe A Rodriguez wrote: >> >> Sysllinux chain-loading is not a factor (GRUB 2.00 still fails to >> boot w/o it). GRUB 2.02 does resolve the issue. The command line >> for 2.02 required a “-p” switch which 2.00 does not. This probably >> caused an uncaught and unnoticed failure during installation in my >> previous testing. > > Again, Debian is using e2fsprogs 1.43.4 and uses ext4 as the default > file system, and GRUB 2.02 as the default boot system. No one has > complained about failures in the instsall process, and I'm pretty sure > the Debian installer team has done their usual great job in testing > and QA. So if there was an issue in the combination of ext4, > e2fsprogs 1.43.4 and Grub 2.02 in Debian Stretch (the latest Debian > Stable, version 8.0) they would have found it. > > … snip > So when you say that enabling the 64-bit file system feature causes a > regression by causing Grub to fail to be able to read the root file > system, I have to respectfully disagree. I do it all the time when I > reboot my kernel, and it Works For Me... > > - Ted Huh ??? I indicated GRUB 2.00 stopped working with the upgrade to 1.43.4, but GRUB 2.02 works fine. Felipe
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
