Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1033985: debian-installer: Installer sets grub up without existing Windows boot choice
0 views
Skip to first unread message
Bud Heal
Apr 5, 2023, 1:40:04 PM4/5/23
to
Package: debian-installer
Version: 20230401
Severity: important
X-Debbugs-Cc: budhe...@gmail.com
Dear Maintainer,
* What led up to the situation?
I installed the latest weekly build to test a different bug. This machine has Windows 7 in the first partition. At some point I copied the 320GB onto a 2TB, then installed Linux onto the residue. This time I overwrote Devuan Ascii. The install would not complete unless I reinitialized it as ext4.
* What exactly did you do (or not do) that was effective (or
ineffective)?
In the boot sequence, grub's list no longer included the Windows 7 partition. After completing tests, I used Microsoft's tools to reenable Windows and now have no longer have an option to boot into the Linux partition.
* What was the outcome of this action?
The last time I installed Buster and bullseye, on other computers, the Windows options were still shown at boot. This appear to be a regression of some kind. I have also complained (as a grub bug) that when I install different Debian versions, the (unused) Windows M.2 shows, the latest (M.2 or SATA SSD) shows, but the third doesn't show up - and I would really like to use that one when the testing install fails out. Okay, hunt and peck a little bit and it can happen anyway.
* What outcome did you expect instead?
I guess I am wishing for the Installer to enumerate all of the attached volumes and any of the bootable partitions and pack them into a tidy list for grub.
Now, for this install I used a 64GB USB stick with the DLBR image. The Installer duly asked if I wanted to boot from the hard disk or the USB drive next time. Listing the install volume seems a little silly, but not listing all of the options on the hard drive -- senseless.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-security
APT policy: (500, 'testing-security')
Architecture: amd64 (x86_64)
*** ignore the environment, it was an 4-core i7 in an old laptop ***
Kernel: Linux 6.1.0-6-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Version: 20230401
Severity: important
X-Debbugs-Cc: budhe...@gmail.com
Dear Maintainer,
* What led up to the situation?
I installed the latest weekly build to test a different bug. This machine has Windows 7 in the first partition. At some point I copied the 320GB onto a 2TB, then installed Linux onto the residue. This time I overwrote Devuan Ascii. The install would not complete unless I reinitialized it as ext4.
* What exactly did you do (or not do) that was effective (or
ineffective)?
In the boot sequence, grub's list no longer included the Windows 7 partition. After completing tests, I used Microsoft's tools to reenable Windows and now have no longer have an option to boot into the Linux partition.
* What was the outcome of this action?
The last time I installed Buster and bullseye, on other computers, the Windows options were still shown at boot. This appear to be a regression of some kind. I have also complained (as a grub bug) that when I install different Debian versions, the (unused) Windows M.2 shows, the latest (M.2 or SATA SSD) shows, but the third doesn't show up - and I would really like to use that one when the testing install fails out. Okay, hunt and peck a little bit and it can happen anyway.
* What outcome did you expect instead?
I guess I am wishing for the Installer to enumerate all of the attached volumes and any of the bootable partitions and pack them into a tidy list for grub.
Now, for this install I used a 64GB USB stick with the DLBR image. The Installer duly asked if I wanted to boot from the hard disk or the USB drive next time. Listing the install volume seems a little silly, but not listing all of the options on the hard drive -- senseless.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-security
APT policy: (500, 'testing-security')
Architecture: amd64 (x86_64)
*** ignore the environment, it was an 4-core i7 in an old laptop ***
Kernel: Linux 6.1.0-6-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Cyril Brulebois
Apr 5, 2023, 4:10:05 PM4/5/23
to
Hi,
Bud Heal <budhe...@gmail.com> (2023-04-05):
that was the plan, I don't think it has happened yet). Once Debian is
booted, you should be able to activate os-prober via some configuration
file under /etc (probably /etc/default/grub).
(I don't know anything about dual-booting, and I can't test it locally,
so I'm letting other people make the relevant decisions, hence the vague
answer…)
Cheers,
--
Cyril Brulebois (ki...@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
Bud Heal <budhe...@gmail.com> (2023-04-05):
> The last time I installed Buster and bullseye, on other computers, the
> Windows options were still shown at boot. This appear to be a
> regression of some kind.
This was a deliberate change, that might be reverted eventually (I think
> Windows options were still shown at boot. This appear to be a
> regression of some kind.
that was the plan, I don't think it has happened yet). Once Debian is
booted, you should be able to activate os-prober via some configuration
file under /etc (probably /etc/default/grub).
(I don't know anything about dual-booting, and I can't test it locally,
so I'm letting other people make the relevant decisions, hence the vague
answer…)
Cheers,
--
Cyril Brulebois (ki...@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
Diederik de Haas
Apr 5, 2023, 4:30:04 PM4/5/23
to
On Wednesday, 5 April 2023 22:04:57 CEST Cyril Brulebois wrote:
> you should be able to activate os-prober via some configuration
> file under /etc (probably /etc/default/grub).
Correct, the setting is GRUB_DISABLE_OS_PROBER=false
> you should be able to activate os-prober via some configuration
> file under /etc (probably /etc/default/grub).
/me wonders why that default changed ...
Holger Wansing
Apr 5, 2023, 4:50:05 PM4/5/23
to
Hi,
Diederik de Haas <didi....@cknow.org> wrote (Wed, 05 Apr 2023 22:14:48 +0200):
> On Wednesday, 5 April 2023 22:04:57 CEST Cyril Brulebois wrote:
> > you should be able to activate os-prober via some configuration
> > file under /etc (probably /etc/default/grub).
>
> Correct, the setting is GRUB_DISABLE_OS_PROBER=false
Or see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032374#10
for a more verbose description.
Holger
--
Holger Wansing <hwan...@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Diederik de Haas <didi....@cknow.org> wrote (Wed, 05 Apr 2023 22:14:48 +0200):
> On Wednesday, 5 April 2023 22:04:57 CEST Cyril Brulebois wrote:
> > you should be able to activate os-prober via some configuration
> > file under /etc (probably /etc/default/grub).
>
> Correct, the setting is GRUB_DISABLE_OS_PROBER=false
for a more verbose description.
Holger
--
Holger Wansing <hwan...@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
0 new messages