On Wed, Aug 07, 2019 at 11:19:55AM +0200, J. Pietschmann wrote:
> The problem appears to be that grub 2.04 uses only devices by disk-id
> and didn't install on /dev/sda even though grub 2.02 did.
No, that's incorrect. GRUB 2.02 behaved just the same way; you just
didn't notice the problem
Hi,
I have a similar problem with plain grub-pc (no EFI)
I use the first two HDD as an MDM array and installed grub
on both /dev/sda and /dev/sdb. A few weeks ago the first HDD
failed and was replaced, and I used
update-grub
grub-install /dev/sda
afterwards and could reboot the computer without
Am Dienstag, 30. Juli 2019, 01:21:43 CEST schrieb Jiri Palecek:
> On 29. 07. 19 22:12, Max Hofer wrote:
> >> I was also hit by this bug after upgrading yesterday (it has been few
> >> weeks since I updated the machine). Just like others, I also had to
> >> downgrade the following packages to 2.02
> I was also hit by this bug after upgrading yesterday (it has been few
> weeks since I updated the machine). Just like others, I also had to
> downgrade the following packages to 2.02 to get it working.
>
> 1. grub-common
> 2. grub2-common
> 3. grub-efi-amd64-bin
> 4. grub-efi-amd64
> 5.
Hi,
I was also hit by this bug after upgrading yesterday (it has been few
weeks since I updated the machine). Just like others, I also had to
downgrade the following packages to 2.02 to get it working.
1. grub-common
2. grub2-common
3. grub-efi-amd64-bin
4. grub-efi-amd64
5. grub-pc-bin
> This
Package: grub-pc
Followup-For: Bug #931896
I ran into this bug, too. The values of all set variables (prefix, root)
seemed to be sane and "ls $prefix/i386-pc" returned a list of *.mod files as
expected. However, when I tried to load the "normal" module, the error was
risen again:
> grub rescue>
On Tue, Jul 16, 2019 at 11:08:25PM +0200, MiloMak wrote:
>Updated from 2.02+dfsg1-20 to 2.04-1 like the op and get similar to the op
>
>[1]https://i.imgur.com/jKYXOHs.png
>
>when i downgrade back to 2.02 grub boots without issue. I have debian
>installed as:
>/dev/sdc1
Updated from 2.02+dfsg1-20 to 2.04-1 like the op and get similar to
the op
https://i.imgur.com/jKYXOHs.png
when i downgrade back to 2.02 grub boots without issue. I have
debian installed as:
/dev/sdc1 /boot/efi
/dev/sdc2 / (/boot is
On maandag 15 juli 2019 11:22:55 CEST Colin Watson wrote:
> output of "sudo debconf-show grub-pc | grep install_devices:".
Ohhh, that is an interesting command :)
> You certainly do need to run "dpkg-reconfigure grub-pc" to match what
> your BIOS is configured to boot from. However, once you
On Mon, Jul 15, 2019 at 01:51:59AM +0200, Diederik de Haas wrote:
> On maandag 15 juli 2019 00:33:31 CEST Colin Watson wrote:
> > > In the not too distant future, I'll remove that old drive (with WinXP on
> > > it) from my system and my guess is that I then will have a problem.
> >
> > That
On maandag 15 juli 2019 00:33:31 CEST Colin Watson wrote:
> > In the not too distant future, I'll remove that old drive (with WinXP on
> > it) from my system and my guess is that I then will have a problem.
>
> That shouldn't be the case: we store the installation device using a
>
On Sun, Jul 14, 2019 at 11:56:39PM +0200, Diederik de Haas wrote:
> On zaterdag 13 juli 2019 09:05:44 CEST Sven Joachim wrote:
> > What I finally figured out after getting my system to boot again, is
> > that grub was still configured to install its core image to /dev/sda,
> > the old hard disk.
Thanks for your reply, it was very helpful :)
On zaterdag 13 juli 2019 09:05:44 CEST Sven Joachim wrote:
> Most likely you had grub configured to install to the wrong disk, this
> is what happened to me. When I installed an SSD into my old PC back in
> December 2016, I copied all files from the
On 2019-07-12 23:24 +0200, Diederik de Haas wrote:
> Package: grub-efi-amd64
> Followup-For: Bug #931896
>
> I don't have grub-efi-amd64 installed, but I ran into the same problem.
> The only enabled lines in /etc/default/grub are these:
> GRUB_DEFAULT=0
> GRUB_TIMEOUT=5
>
Package: grub-efi-amd64
Followup-For: Bug #931896
I don't have grub-efi-amd64 installed, but I ran into the same problem.
The only enabled lines in /etc/default/grub are these:
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
Package: grub-efi-amd64
Version: 2.04-1
Severity: grave
Hi,
since the last update the grub no longer works. It fails very early with
symbol `grub_file_filters` not found
and enters the rescue shell. After downgrading it back to 2.02+dfsg1-20
everything works again as expected.
Cheers
--
16 matches
Mail list logo
