Dear Steve,
I am sorry for the late reply, as I was on vacation.
Am 31.07.20 um 15:22 schrieb Steve McIntyre:
On Fri, Jul 31, 2020 at 06:39:20AM +0200, Paul Menzel wrote:
Am 31.07.20 um 06:30 schrieb Paul Menzel:
Am 30.07.20 um 23:54 schrieb Paul Menzel:
Package: grub-pc
Version: 2.04-9
Triggered this with an apt upgrade dist-upgrade
APT::Default-Release "buster";
grub-pc 2.02+dfsg1-20+deb10u2
,.,.
This system had mirrored drives -
Had to boot off a thumbdrive - enter rescue - when it asked for the boot drive - had to tell it to
build raid - then select the raid (
>From conversation in IRC:
1. If the device(s) mentioned in grub-pc/install_devices multiselect
don't exist when grub-install is run, it should stop and warn the
user that there might be a problem
DSA have this on a VM, for example:
grub-pc grub-pc/install_devices
[ Dropping the CC to Chad here ]
On Sat, Aug 01, 2020 at 02:36:25PM +0100, Colin Watson wrote:
>On Sat, Aug 01, 2020 at 01:52:41PM +0100, Steve McIntyre wrote:
>> * Do we need to scan? if grub is installed and doing an upgrade and
>>there is only one disk of an appropriate type (BIOS with
On Sat, Aug 01, 2020 at 01:52:41PM +0100, Steve McIntyre wrote:
> * Do we need to scan? if grub is installed and doing an upgrade and
>there is only one disk of an appropriate type (BIOS with DOS, or
>UEFI with GPT), then always install there?
Possibly. I'd still be inclined to have a
On Fri, Jul 31, 2020 at 11:49:06PM +0100, Colin Watson wrote:
...
>It looks like the base VM image provided by bento/debian-10 hardcodes
>some details of how it was built that don't carry over to other systems
>booting the same image, and this causes problems.
>
>debian/buster64 has a similar
On Sat, Aug 01, 2020 at 01:32:33PM +0200, Miklos Quartus wrote:
> I am reporting this bug here
Please could you file this as a *new* bug report, *not* as a followup to
#966575 which I would much rather keep for just the more common BIOS
case? Ideally you would do this by typing "reportbug
Hello,
My case was indeed a disk switch from USB to internal.
I probably had invoked directly grub-install (dunno if it'd make sense
to warn about the mismatch with debconf there?), now I know I should
rather use dpkg-reconfigure instead.
# debconf-get-selections |grep 'grub-pc/install_devices'
On Sat, Aug 01, 2020 at 01:23:30AM +0200, MichaIng wrote:
> we face the same issue whenever a ready-to-run image has been created and
> booted from a different device.
>
> From what we found, the Debian installer (or the grub install/config
> scripts) stores the hardware ID of the drive to
This bug appears to affect a standard Vagrant install of Debian Buster as
well. After booting, upgrading, and rebooting, I'm faced with the error.
The Vagrant base box is a fairly common one:
https://app.vagrantup.com/bento/boxes/debian-10
I'm guessing this is a fairly standard disk layout in
Hi John,
On Fri, Jul 31, 2020 at 09:29:43AM +0100, John Lines wrote:
>I have the same error, on a DNUK Workstar 700, dating back to 2014, so
>upgraded from squeeze on up to buster.It is possible this legacy which
>has resulted in something unusual in the grub configuration.
>
>I upgraded grub
Hi Paul,
On Fri, Jul 31, 2020 at 06:39:20AM +0200, Paul Menzel wrote:
>Am 31.07.20 um 06:30 schrieb Paul Menzel:
>
>> Am 30.07.20 um 23:54 schrieb Paul Menzel:
>> > Package: grub-pc
>> > Version: 2.04-9
>> > Severity: grave
>>
>> > On a Acer TravelMate 5735Z with Debian Sid/unstable, upgrading
I have the same error, on a DNUK Workstar 700, dating back to 2014, so
upgraded from squeeze on up to buster.It is possible this legacy which
has resulted in something unusual in the grub configuration.
I upgraded grub yesterday, and am working on recovering now. Posting
from another system.
Dear Debian folks,
Am 31.07.20 um 06:30 schrieb Paul Menzel:
Am 30.07.20 um 23:54 schrieb Paul Menzel:
Package: grub-pc
Version: 2.04-9
Severity: grave
On a Acer TravelMate 5735Z with Debian Sid/unstable, upgrading the
package `grub-pc` causes GRUB to fail on next boot and drop into a
Dear Debian folks,
Am 30.07.20 um 23:54 schrieb Paul Menzel:
Package: grub-pc
Version: 2.04-9
Severity: grave
On a Acer TravelMate 5735Z with Debian Sid/unstable, upgrading the
package `grub-pc` causes GRUB to fail on next boot and drop into a
rescue shell.
GRUB loading.
Package: grub-pc
Version: 2.04-9
Severity: grave
Dear Debian folks,
On a Acer TravelMate 5735Z with Debian Sid/unstable, upgrading the
package `grub-pc` causes GRUB to fail on next boot and drop into a
rescue shell.
GRUB loading.
Welcome to GRUB!
error: symbol 'grub_calloc'
16 matches
Mail list logo
