Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot

Hi Marc, On 20/05/24 at 14:35, Marc SCHAEFER wrote: 3. grub BOOT FAILS IF ANY LV HAS dm-integrity, EVEN IF NOT LINKED TO / if I reboot now, grub2 complains about rimage issues, clear the screen and then I am at the grub2 prompt. Booting is only possible with Debian rescue, disabling the dm

Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot

Hello, On Wed, May 22, 2024 at 05:03:34PM -0400, Stefan Monnier wrote: > Hmm... I've been using a "plain old partition" for /boot (with > everything else in LVM) for "ever", originally because the boot loader > was not able to read LVM, and later out of habit. I was thinking of > finally moving /

Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot

> I found this [1], quoting: "I'd also like to share an issue I've > discovered: if /boot's partition is a LV, then there must not be a > raidintegrity LV anywhere before that LV inside the same VG. Otherwise, > update-grub will show an error (disk `lvmid/.../...' not found) and GRUB > cannot boot.

Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot

ity protected ones come first). I guess it's a general problem how grub2 parses LVM, yes, as soon as their are special things going on, it somehow breaks. However, if you don't have /boot on LVM, hand-fixing grub2 can be trivial, e.g. here on another system with /boot/efi on 1st disk'

Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot

Hello, On Wed, May 22, 2024 at 08:57:38AM +0200, Marc SCHAEFER wrote: > I will try this work-around and report back here. As I said, I can > live with /boot on RAID without dm-integrity, as long as the rest can be > dm-integrity+raid protected. I'm interested in how you get on. I don't (yet) us

Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot

including /, /var/lib/lxc, /scratch and swap, now boots without any issue with grub2 as long as /boot is NOT on the same VG where the dm-integrity over LVM RAID is enabled. This is OK for me, I don't need /boot on dm-integrity. update-grub gives out warning for every of the rimage subvolumes, but

Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot

Additional info: On Wed, May 22, 2024 at 08:49:56AM +0200, Marc SCHAEFER wrote: > Having /boot on a LVM non enabled dm-integrity logical volume does not > work either, as soon as there is ANY LVM dm-integrity enabled logical > volume anywhere (even not linked to booting), grub2 complains

Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot

3) the issue is not with the initrd -- I added the dm-integrity module and rebuilt the initrd (and actually the bug happens before grub2 loads the kernel & init) -- or at least "not yet"! maybe this will fail later :) 4) actually the issue is just grub2, be it when the syste

Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot

On 20/05/24 at 14:35, Marc SCHAEFER wrote: Any idea what could be the problem? Any way to just make grub2 ignore the rimage (sub)volumes at setup and boot time? (I could live with / aka vg1/root not using dm-integrity, as long as the data/docker/etc volumes are integrity-protected) ? Or how

Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot

N IF NOT LINKED TO / if I reboot now, grub2 complains about rimage issues, clear the screen and then I am at the grub2 prompt. Booting is only possible with Debian rescue, disabling the dm-integrity on the above volume and rebooting. Note that you still can see the rimage/rmeta sub LVs (lvs -a), th

Re: Uninstall grub2 on Sparc T2000

pvilt...@free.fr wrote: > Hello, > > I burned [ > https://cdimage.debian.org/cdimage/ports/current/debian-11.0.0-sparc64-NETINST-1.iso > | debian-11.0.0-sparc64-NETINST-1.iso ] on CdRom for a Sun T2000 (Sun4v) > Used Putty on windows 10 with SerManagement > > Boot OK > Startup OK > Partit

Uninstall grub2 on Sparc T2000

Hello, I burned [ https://cdimage.debian.org/cdimage/ports/current/debian-11.0.0-sparc64-NETINST-1.iso | debian-11.0.0-sparc64-NETINST-1.iso ] on CdRom for a Sun T2000 (Sun4v) Used Putty on windows 10 with SerManagement Boot OK Startup OK Partition not OK(?) : Warnings : Detects 256000 blo

Re: apt tells me that grub-efi, grub2-common are no longer needed

tion: > > The following packages have unmet dependencies: > grub-efi-amd64 : Depends: grub-common (= 2.02+dfsg1-20+deb10u3) > Depends: grub2-common (= 2.02+dfsg1-20+deb10u3) > Depends: grub-efi-amd64-bin (= 2.02+dfsg1-20+deb10u3) > E: Unable

Re: apt tells me that grub-efi, grub2-common are no longer needed

On 2021-07-08 at 04:21, Markus wrote: > Am 07.07.21 um 12:27 schrieb Markus: >> markus@bmtMB1:/etc/apt/preferences.d$ ls >> apt-listbugs >> markus@bmtMB1:/etc/apt/preferences.d$ cat apt-listbugs >> >> Explanation: Pinned by apt-listbugs at 2021-03-06 12:05:35 +0100 >> Explanation: #984520: 'err

Re: apt tells me that grub-efi, grub2-common are no longer needed

Markus writes: > Hi guys, it is nice that from all of this a little discussion took of. > But what can I actually do to fix my problem here? Any suggestions? What was the problem again? Just the suggestion to run apt autoremove which probably isn't a good idea now? Easiest is probably waiting u

Re: apt tells me that grub-efi, grub2-common are no longer needed

Am 07.07.21 um 12:27 schrieb Markus: Am 07.07.21 um 09:24 schrieb Andrei POPESCU: On Mi, 07 iul 21, 08:21:17, Markus wrote: Am 24.06.21 um 18:51 schrieb Greg Wooledge: On Thu, Jun 24, 2021 at 06:43:15PM +0200, Markus wrote: grub-efi-amd64:     Installed: (none)     Candidate: 2.02+dfsg1-20+de

Re: apt tells me that grub-efi, grub2-common are no longer needed

The Wanderer writes: > #990082 is for shim-signed, and it does seem to be closed now, but if > I'm reading the discussion correctly that's not the package we're > concerned with. True, especially as #990082 is specific to ARM. > $984520 is for grub-efi-amd64, which I think is the package we're

Re: apt tells me that grub-efi, grub2-common are no longer needed

On 2021-07-07 at 08:19, Anssi Saari wrote: > Markus writes: > >> So it seems that apt-listbugs has done the pinning. Right? > > Right and while I've never used apt-listbugs, it should've asked you > what to do when you updated your system? Since the issue concerns > ARM based systems only, bi

Re: apt tells me that grub-efi, grub2-common are no longer needed

Markus writes: > So it seems that apt-listbugs has done the pinning. Right? Right and while I've never used apt-listbugs, it should've asked you what to do when you updated your system? Since the issue concerns ARM based systems only, binning was not the correct choice. As the bug is fixed now

Re: apt tells me that grub-efi, grub2-common are no longer needed

On Wed, Jul 07, 2021 at 08:21:17AM +0200, Markus wrote: > Am 24.06.21 um 18:51 schrieb Greg Wooledge: > > On Thu, Jun 24, 2021 at 06:43:15PM +0200, Markus wrote: > > > grub-efi-amd64: > > >Installed: (none) > > >Candidate: 2.02+dfsg1-20+deb10u3 > > >Version table: > > > 2.02+dfsg1

Re: apt tells me that grub-efi, grub2-common are no longer needed

Am 07.07.21 um 09:24 schrieb Andrei POPESCU: On Mi, 07 iul 21, 08:21:17, Markus wrote: Am 24.06.21 um 18:51 schrieb Greg Wooledge: On Thu, Jun 24, 2021 at 06:43:15PM +0200, Markus wrote: grub-efi-amd64: Installed: (none) Candidate: 2.02+dfsg1-20+deb10u3 Version table: 2.02+d

Re: apt tells me that grub-efi, grub2-common are no longer needed

On Mi, 07 iul 21, 08:21:17, Markus wrote: > Am 24.06.21 um 18:51 schrieb Greg Wooledge: > > On Thu, Jun 24, 2021 at 06:43:15PM +0200, Markus wrote: > > > grub-efi-amd64: > > >Installed: (none) > > >Candidate: 2.02+dfsg1-20+deb10u3 > > >Version table: > > > 2.02+dfsg1-20+deb10u4 50

Re: apt tells me that grub-efi, grub2-common are no longer needed

Am 24.06.21 um 18:51 schrieb Greg Wooledge: On Thu, Jun 24, 2021 at 06:43:15PM +0200, Markus wrote: grub-efi-amd64: Installed: (none) Candidate: 2.02+dfsg1-20+deb10u3 Version table: 2.02+dfsg1-20+deb10u4 500 500 http://ftp.de.debian.org/debian buster/main amd64 Packages

Re: grub2 boot menu

Le vendredi 25 juin 2021 à 11:40 -0400, Cindy Sue Causey a écrit : > On 6/24/21, didier gaumet wrote: > [...] > > 'GRUB_OS_PROBER_SKIP_LIST' > >     List of space-separated FS UUIDs of filesystems to be ignored > > from > > os-prober output.  For efi chainloaders it's @" [...] > it would

Re: grub2 boot menu

On 6/24/21, didier gaumet wrote: > > Hello, > > Grub can ignore all or only certain OSes that os-prober detects by > setting up the desired behaviour in /etc/default/grub > > from the grub info page: > [...]" > 'GRUB_DISABLE_OS_PROBER' > Normally, 'grub-mkconfig' will try to use the external

Re: grub2 boot menu

On 24/6/21 11:51 pm, mick crane wrote: hello, I was dual booting but got another PC so I can have windows and debain at the same time. Just for tidiness of booting I'd have liked to comment out the submenu entry in /boot/grub/grub.cfg for windows just in case I wanted to put it back but not

Re: grub2 boot menu

Hello,  Grub can ignore all or only certain OSes that os-prober detects by setting up the desired behaviour in /etc/default/grub from the grub info page: [...]" 'GRUB_DISABLE_OS_PROBER' Normally, 'grub-mkconfig' will try to use the external 'os-prober' program, if installed, to discov

Re: grub2 boot menu

On Thu 24 Jun 2021 at 14:51:06 (+0100), mick crane wrote: > I was dual booting but got another PC so I can have windows and debain > at the same time. Just for tidiness of booting I'd have liked to > comment out the submenu entry in /boot/grub/grub.cfg for windows just > in case I wanted to put it

Re: apt tells me that grub-efi, grub2-common are no longer needed

On Thu, Jun 24, 2021 at 06:43:15PM +0200, Markus wrote: > grub-efi-amd64: > Installed: (none) > Candidate: 2.02+dfsg1-20+deb10u3 > Version table: > 2.02+dfsg1-20+deb10u4 500 > 500 http://ftp.de.debian.org/debian buster/main amd64 Packages > 500 http://security.debian.org

Re: apt tells me that grub-efi, grub2-common are no longer needed

More information: markus@bmtMB1:/var/log/apt$ sudo apt policy grub-efi-amd64 grub-common grub2-common grub-efi-amd64-bin grub-efi-amd64: Installed: (none) Candidate: 2.02+dfsg1-20+deb10u3 Version table: 2.02+dfsg1-20+deb10u4 500 500 http://ftp.de.debian.org/debian buster/main

Re: apt tells me that grub-efi, grub2-common are no longer needed

tion: > > The following packages have unmet dependencies: > grub-efi-amd64 : Depends: grub-common (= 2.02+dfsg1-20+deb10u3) > Depends: grub2-common (= 2.02+dfsg1-20+deb10u3) > Depends: grub-efi-amd64-bin (= 2.02+dfsg1-20+deb10u3) > E: Unable

Re: apt tells me that grub-efi, grub2-common are no longer needed

+deb10u3) Depends: grub2-common (= 2.02+dfsg1-20+deb10u3) Depends: grub-efi-amd64-bin (= 2.02+dfsg1-20+deb10u3) E: Unable to correct problems, you have held broken packages. markus@bmtMB1:/var/log/apt$ So...something is wrong here. Puhh...how to fix that

Re: apt tells me that grub-efi, grub2-common are no longer needed

Thank you, David, for the very useful hint. I found this in apt history: Start-Date: 2021-03-06 21:08:42 Commandline: apt full-upgrade Requested-By: markus (1000) Upgrade: grub-common:amd64 (2.02+dfsg1-20+deb10u3, 2.02+dfsg1-20+deb10u4), grub2-common:amd64 (2.02+dfsg1-20+deb10u3, 2.02+dfsg1-20

Re: grub2 boot menu

On 2021-06-24 at 10:32, Felix Miata wrote: > mick crane composed on 2021-06-24 14:51 (UTC+0100): > >> I was dual booting but got another PC so I can have windows and debain >> at the same time. Just for tidiness of booting I'd have liked to comment >> out the submenu entry in /boot/grub/grub.cf

Re: grub2 boot menu

mick crane composed on 2021-06-24 14:51 (UTC+0100): > I was dual booting but got another PC so I can have windows and debain > at the same time. Just for tidiness of booting I'd have liked to comment > out the submenu entry in /boot/grub/grub.cfg for windows just in case I > wanted to put it ba

Re: apt tells me that grub-efi, grub2-common are no longer needed

David Wright (12021-06-24): > Only if you'd gone ahead and removed all those other packages. Not even then. The GRUB packages are useful for installing the GRUB bootloader. Once it's installed, the computer will boot, and the package are not necessary, although they might be useful to automaticall

Re: grub2 boot menu

On Thu, Jun 24, 2021 at 02:51:06PM +0100, mick crane wrote: > I was dual booting but got another PC so I can have windows and debain at > the same time. Just for tidiness of booting I'd have liked to comment out > the submenu entry in /boot/grub/grub.cfg for windows just in case I wanted > to put i

Re: apt tells me that grub-efi, grub2-common are no longer needed

On Thu 24 Jun 2021 at 08:49:40 (+0200), Markus wrote: > Am 23.06.21 um 18:08 schrieb David Wright: > > On Wed 23 Jun 2021 at 17:01:07 (+0200), Markus wrote: > > > rc  grub-efi-amd64 2.02+dfsg1-20+deb10u3 > >↑↑ There's your problem. It's been removed (but not purged). > Ok so...hmmm...I did no

grub2 boot menu

hello, I was dual booting but got another PC so I can have windows and debain at the same time. Just for tidiness of booting I'd have liked to comment out the submenu entry in /boot/grub/grub.cfg for windows just in case I wanted to put it back but not allowed. Physically removing the windows d

Re: apt tells me that grub-efi, grub2-common are no longer needed

On Thu, Jun 24, 2021 at 08:49:40AM +0200, Markus wrote: > Ok so...hmmm...I did not remove it myself. I mean why would I want to do > that?!?! Nevertheless this is an issue now. > Interestingly when booting my computer this morning grub was there and > booted into Buster. Shouldn't it be gone if it

Re: apt tells me that grub-efi, grub2-common are no longer needed

ootloader, version 2 (EFI-AMD64 modules) ii  grub-efi-amd64-signed 1+2.02+dfsg1+20+deb10u4 amd64    GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian) ii  grub-firmware-qemu 2.02+dfsg1-20+deb10u4 amd64    GRUB firmware image for QEMU ii  grub2-common 2.02+dfsg1-20+deb10u4 amd64 

Re: apt tells me that grub-efi, grub2-common are no longer needed

2+dfsg1+20+deb10u4  > amd64    GRand Unified Bootloader, version 2 (amd64 UEFI signed by > Debian) > ii  grub-firmware-qemu 2.02+dfsg1-20+deb10u4    > amd64    GRUB firmware image for QEMU > ii  grub2-common 2.02+dfsg1-20+deb10u4  

Re: apt tells me that grub-efi, grub2-common are no longer needed

2 (amd64 UEFI signed by Debian) ii  grub-firmware-qemu 2.02+dfsg1-20+deb10u4    amd64    GRUB firmware image for QEMU ii  grub2-common 2.02+dfsg1-20+deb10u4    amd64    GRand Unified Bootloader (common files for version 2) markus@bmtMB1:~$ Cheers

Re: apt tells me that grub-efi, grub2-common are no longer needed

automatically installed and are no > longer required: > efibootmgr grub-efi-amd64-bin grub-efi-amd64-signed grub2-common > libappindicator3-1 libcanberra-gtk3-0 libcanberra-gtk3-module > libclutter-gtk-1.0-0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libindicator3-7 > libupsclient4 linux

Re: apt tells me that grub-efi, grub2-common are no longer needed

On Wed, Jun 23, 2021 at 03:55:04PM +0200, Markus wrote: >Hi, just before and also after today's "apt full-upgrade" apt tells me >that: > The following packages were automatically installed and are no longer > required: > efibootmgr grub-efi-amd64-bin grub

apt tells me that grub-efi, grub2-common are no longer needed

Hi, just before and also after today's "apt full-upgrade" apt tells me that: The following packages were automatically installed and are no longer required: efibootmgr grub-efi-amd64-bin grub-efi-amd64-signed grub2-common libappindicator3-1 libcanberra-gtk

kernel param vga=* and grub2

This can be suppressed by adding 'vga=off'. However, vga=* is deprecated in grub2 and will make your newly installation unbootable. I would prefer not to have to manually correct this issue. Does anyone has any idea on how to avoied that prompt while keeping grub2 happy? -- John Doe

Re: Grub2 on clean Stretch install

On 2017-06-27 17:37 +0200, Floris wrote: > Just wondering, why has the grub2-common package two update-grub files? > > One is just a symlink to the other > ls -asl update-grub* > 4 -rwxr-xr-x 1 root root 64 jun 23 12:35 update-grub > 0 lrwxrwxrwx 1 root root 11 jun 23 14:47 upda

Re: Grub2 on clean Stretch install

On Tue, Jun 27, 2017 at 06:14:10PM +0200, Floris wrote: Op Tue, 27 Jun 2017 18:04:19 +0200 schreef David Wright : On Tue 27 Jun 2017 at 17:37:53 (+0200), Floris wrote: Just wondering, why has the grub2-common package two update-grub files? One is just a symlink to the other ls -asl update

Re: Grub2 on clean Stretch install

Op Tue, 27 Jun 2017 18:04:19 +0200 schreef David Wright : On Tue 27 Jun 2017 at 17:37:53 (+0200), Floris wrote: Just wondering, why has the grub2-common package two update-grub files? One is just a symlink to the other ls -asl update-grub* 4 -rwxr-xr-x 1 root root 64 jun 23 12:35 update

Re: Grub2 on clean Stretch install

On Tue 27 Jun 2017 at 17:37:53 (+0200), Floris wrote: > Just wondering, why has the grub2-common package two update-grub files? > > One is just a symlink to the other > ls -asl update-grub* > 4 -rwxr-xr-x 1 root root 64 jun 23 12:35 update-grub > 0 lrwxrwxrwx 1 root root 11 j

Grub2 on clean Stretch install

Just wondering, why has the grub2-common package two update-grub files? https://packages.debian.org/stretch/amd64/grub2-common/filelist File list of package grub2-common in stretch of architecture amd64 /usr/sbin/grub-install /usr/sbin/grub-reboot /usr/sbin/grub-set-default /usr/sbin/update

Re: New install Jesse 8.6.0...grub2 problem

On Sunday 30 October 2016 15:47:59 Mark Fletcher wrote: > On Sun, Oct 30, 2016 at 10:35:59AM -0400, Cindy-Sue Causey wrote: > > On 10/30/16, Pascal Hambourg wrote: > > > Le 30/10/2016 à 13:13, Lisi Reisz a écrit : > > >> On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote: > > >>> The resul

Re: New install Jesse 8.6.0...grub2 problem

On Sun, Oct 30, 2016 at 10:35:59AM -0400, Cindy-Sue Causey wrote: > On 10/30/16, Pascal Hambourg wrote: > > Le 30/10/2016 à 13:13, Lisi Reisz a écrit : > >> On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote: > >>> > >>> The result of bootinfoscript would be a good starting point. > >> > >

Re: New install Jesse 8.6.0...grub2 problem

On 10/30/16, Pascal Hambourg wrote: > Le 30/10/2016 à 13:13, Lisi Reisz a écrit : >> On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote: >>> >>> The result of bootinfoscript would be a good starting point. >> >> I have Jessie fully updated and aptitude can't find bootinfoscript. > > How di

Re: New install Jesse 8.6.0...grub2 problem

On Sunday 30 October 2016 13:32:27 Pascal Hambourg wrote: > Le 30/10/2016 à 13:13, Lisi Reisz a écrit : > > On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote: > >> The result of bootinfoscript would be a good starting point. > > > > I have Jessie fully updated and aptitude can't find booti

Re: New install Jesse 8.6.0...grub2 problem

Le 30/10/2016 à 13:13, Lisi Reisz a écrit : On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote: The result of bootinfoscript would be a good starting point. I have Jessie fully updated and aptitude can't find bootinfoscript. How did you search ? It is a command, not a package name.

Re: New install Jesse 8.6.0...grub2 problem

On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote: > Le 06/10/2016 à 19:22, Mark Neidorff a écrit : > > Is there more information that you need to help me? > > The result of bootinfoscript would be a good starting point. I have Jessie fully updated and aptitude can't find bootinfoscript.

Re: Re: Reconfiguring grub2 UFEI system

oops, I notice it is solved now, must have missed those posts in the digest somehow, I was thinking however that maybe it was a case of 'I never installed that version of grub so I'm not going to write to it' as you probably had a slightly different version from the one on SuSE, I am no expert howe

Re: Reconfiguring grub2 UFEI system

On Sun, 2016-10-23 at 17:49 +0200, Pascal Hambourg wrote: > Le 22/10/2016 à 23:17, Mark Neidorff a écrit : > > On Friday, 10/21/16 10:19:47 PM Pascal Hambourg wrote: > > > > > What is the output of "os-prober" ? > > > > No output. (yes, I ran it as root) > > Then no other system was detected and

Re: Reconfiguring grub2 UFEI system **SOLVED**

od. >> > >> > I then ran >> > >> > #update-grub >> > >> > hoping that would regenerate the grub boot menu, (I also tried >> > #update-grub2) but the old entries still appear when the system boots. >> >> Are you ta

Re: Reconfiguring grub2 UFEI system **SOLVED**

; > > >> > I then ran > >> > > >> > #update-grub > >> > > >> > hoping that would regenerate the grub boot menu, (I also tried > >> > #update-grub2) but the old entries still appear when the system boots. > >>

Re: Reconfiguring grub2 UFEI system

Le 22/10/2016 à 23:17, Mark Neidorff a écrit : On Friday, 10/21/16 10:19:47 PM Pascal Hambourg wrote: What is the output of "os-prober" ? No output. (yes, I ran it as root) Then no other system was detected and added to the GRUB menu when you ran update-grub. Are you sure the GRUB that

Re: Reconfiguring grub2 UFEI system

and to expand other partitions to fill > the space. All is now good. > > I then ran > > #update-grub > > hoping that would regenerate the grub boot menu, (I also tried > #update-grub2) but the old entries still appear when the system boots. Are you talking about en

Re: Reconfiguring grub2 UFEI system

ace. All is now good. > > > > I then ran > > > > #update-grub > > > > hoping that would regenerate the grub boot menu, (I also tried > > #update-grub2) but the old entries still appear when the system boots. > > Are you talking about entries in GRUB&#x

Re: Reconfiguring grub2 UFEI system

menu, (I also tried #update-grub2) but the old entries still appear when the system boots. Are you talking about entries in GRUB's menu or in the UEFI boot menu ? update-grub only updates the former. What is the output of "os-prober" ? Are you sure the GRUB that shows up is the one from Debian ?

Reconfiguring grub2 UFEI system

would regenerate the grub boot menu, (I also tried #update-grub2) but the old entries still appear when the system boots. How do I make the system show an updated grub2 menu on boot? I feel like I have not provided some information which would be helpful in helping me. If that is the case

Re: New install Jesse 8.6.0...grub2 problem

Pascal Hambourg composed on 2016-10-06 20:30 (UTC+0200): ...if the OP followed the openSUSE installer defaults, the root filesystem is btrfs and can be shrinked while mounted. That depends on which openSUSE he installed, data he didn't provide. BTRFS became default between 13.2 and 42.1 relea

Re: New install Jesse 8.6.0...grub2 problem

-prober just detects other OS'es, it does not change anything. You need to run update-grub (or update-grub2 as openSUSE may name it) to add boot menu entries for the discovered OS'es.

Re: New install Jesse 8.6.0...grub2 problem

Le 06/10/2016 à 19:22, Mark Neidorff a écrit : Is there more information that you need to help me? The result of bootinfoscript would be a good starting point.

Re: New install Jesse 8.6.0...grub2 problem

ges. I'll be using backuppc to do the actual backups. I tried using a different distro--OpenSUSE and it didn't work out. I installed the distro on the 750 Gb drive (and it boots via grub2 from the 750 Gb drive), but couldn't get backuppc working. I didn't want to just wipe

New install Jesse 8.6.0...grub2 problem

actual backups. I tried using a different distro--OpenSUSE and it didn't work out. I installed the distro on the 750 Gb drive (and it boots via grub2 from the 750 Gb drive), but couldn't get backuppc working. I didn't want to just wipe out the OpenSUSE installation, so I carved a

Re: Jessie does not boot (GRUB2 complains with "mduuid not found"

Le 27/07/2016 à 22:16, deloptes a écrit : Pascal Hambourg wrote: Le 26/07/2016 à 23:38, deloptes a écrit : Did you check mdadm.conf - you usually regenerate it and recreate/update initrd Irrelevant. GRUB does not use mdadm.conf for booting. I understood OP has problem with assembling MD a

Re: Jessie does not boot (GRUB2 complains with "mduuid not found"

Hi, deloptes. On 27/07/16 17:16, deloptes wrote: >>> Did you check mdadm.conf - you usually regenerate it and recreate/update >>> initrd >> Irrelevant. GRUB does not use mdadm.conf for booting. > I understood OP has problem with assembling MD after boot. It is not clear > to me if his / is on r

Re: Jessie does not boot (GRUB2 complains with "mduuid not found"

Pascal Hambourg wrote: > Le 26/07/2016 à 23:38, deloptes a écrit : >> Daniel Guillermo Bareiro wrote: > (...) >>> The idea was to re-install without losing the containers I had >>> created. After finishing the installation process, GRUB failed >>> to boot with this message: > > > >> Did you che

Re: Jessie does not boot (GRUB2 complains with "mduuid not found"

Le 26/07/2016 à 23:38, deloptes a écrit : Daniel Guillermo Bareiro wrote: (...) The idea was to re-install without losing the containers I had created. After finishing the installation process, GRUB failed to boot with this message: Did you check mdadm.conf - you usually regenerate it and

Re: Jessie does not boot (GRUB2 complains with "mduuid not found"

Daniel Guillermo Bareiro wrote: > Hi all! > > Currently I have an old machine without hardware virtualization > support, which I was using for testing using Jessie i686 and LXC. > > I tried to migrate that installation to amd64 architecture but > things did not went as well as I would have liked

Re: Jessie does not boot (GRUB2 complains with "mduuid not found"

Hi, Pascal. On 07/23/16 05:48, Pascal Hambourg wrote: >> The idea was to re-install without losing the containers I had >> created. After finishing the installation process, GRUB failed >> to boot with this message: >> >> >>

Re: Jessie does not boot (GRUB2 complains with "mduuid not found"

Le 23/07/2016 à 03:19, Daniel Guillermo Bareiro a écrit : The idea was to re-install without losing the containers I had created. After finishing the installation process, GRUB failed to boot with this message: error: fail

Jessie does not boot (GRUB2 complains with "mduuid not found"

Hi all! Currently I have an old machine without hardware virtualization support, which I was using for testing using Jessie i686 and LXC. I tried to migrate that installation to amd64 architecture but things did not went as well as I would have liked and I had to reinstalling the operating syst

Re: grub2 security problem

David Christensen a écrit : > > A good defense against an attacker with physical access is LUKS > encryption on all partitions except /boot. Ecryption alone does not protect agains attack scenarios involving /boot tampering.

Re: grub2 security problem

On Sunday 20 December 2015 09:51:04 to...@tuxteam.de wrote: > On Sun, Dec 20, 2015 at 04:08:30PM +0100, Anders Andersson wrote: > > On Sun, Dec 20, 2015 at 5:00 AM, David Christensen > > > > wrote: > > > Another, additional, option is self-encrypting drives (SED), which > > > are operating system

Re: grub2 security problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Dec 20, 2015 at 04:08:30PM +0100, Anders Andersson wrote: > On Sun, Dec 20, 2015 at 5:00 AM, David Christensen > wrote: > > > > Another, additional, option is self-encrypting drives (SED), which are > > operating system agnostic and protect th

Re: grub2 security problem

On Sun, Dec 20, 2015 at 5:00 AM, David Christensen wrote: > > Another, additional, option is self-encrypting drives (SED), which are > operating system agnostic and protect the entire contents of drive with zero > CPU overhead. Emphasis on the word "additional" here. Unless you have access to the

Re: grub2 security problem

On 12/19/2015 08:59 AM, Joe Pfeiffer wrote: Michael Fothergill writes: I noticed some articles suggesting that there is a security problem in grub2. E.g. http://thehackernews.com/2015/12/hack-linux-grub-password.html ​Is there any substance to this? Yes, for the microscopic proportion of

Re: grub2 security problem

Michael Fothergill writes: > Dear Folks, > > I noticed some articles suggesting that there is a security problem in > grub2. > > E.g. > > http://thehackernews.com/2015/12/hack-linux-grub-password.html > > ​Is there any substance to this? Yes, for the microscopic

Re: grub2 security problem

On 19 December 2015 at 11:50, Brad Rogers wrote: > On Sat, 19 Dec 2015 09:35:57 + > Michael Fothergill wrote: > > Hello Michael, > > >​Is there any substance to this? > ​ > Yes, but it's been rectified. See > > for the f

Re: grub2 security problem

On Sat, 19 Dec 2015 09:35:57 + Michael Fothergill wrote: Hello Michael, >​Is there any substance to this? ​ Yes, but it's been rectified. See for the full security announcement. Further, I suggest subscribing to the Deb

Re: grub2 security problem

On Sat, 19 Dec 2015 09:35:57 + Michael Fothergill wrote: > Dear Folks, > > I noticed some articles suggesting that there is a security problem in > grub2. > > E.g. > > http://thehackernews.com/2015/12/hack-linux-grub-password.html > > ​Is there any subst

Re: grub2 security problem

Michael Fothergill [2015-12-19 09:35:57Z] wrote: > I noticed some articles suggesting that there is a security problem in > grub2. > http://thehackernews.com/2015/12/hack-linux-grub-password.html > > ​Is there any substance to this? Didn't check myself but it seems so: ht

grub2 security problem

Dear Folks, I noticed some articles suggesting that there is a security problem in grub2. E.g. http://thehackernews.com/2015/12/hack-linux-grub-password.html ​Is there any substance to this? Regards Michael Fothergill ​

Re: Configure Grub2 with Multiple Boot Options?

neration of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" On Tue, Oct 6, 2015 at 10:31 AM, Jeffrey Walton wrote: > I'm having trouble learning how to add multiple boot configurations to > De

Configure Grub2 with Multiple Boot Options?

I'm having trouble learning how to add multiple boot configurations to Debian's Grub2. Debian has Grub pages at https://wiki.debian.org/Grub and https://wiki.debian.org/GrubConfiguration, but they lack practical examples for multiple boot configurations. Would someone please update

Re: Wheezy amd64 grub2 error: file '/grub/i386-pc/normal.mod' not found

On Wed 26 Aug 2015 at 01:55:15 -0700, Ldten K wrote: > On Wed, 8/26/15, Pascal Hambourg wrote: > > // Didn't you install a more recent version of GRUB (possibly from a new > // installation) at some time on that disk ? > > That could be it. The drive originally had a working wheezy installation

Re: Wheezy amd64 grub2 error: file '/grub/i386-pc/normal.mod' not found

On Wed, 8/26/15, Pascal Hambourg wrote: // Didn't you install a more recent version of GRUB (possibly from a new // installation) at some time on that disk ? That could be it. The drive originally had a working wheezy installation that booted properly and worked just fine. I then decided to upg

Re: Wheezy amd64 grub2 error: file '/grub/i386-pc/normal.mod' not found

Ldten K a écrit : > On Tue, 8/25/15, Pascal Hambourg wrote: > >> What does "ls (hd0,msdos1)/grub/" show ? Just a few files >> and directories or plenty of *.mod files? > > I have the drive disconnected at the moment but, as far as I remember, "ls > (hd0,msdos1)/grub/" > shows all the files th

Re: Wheezy amd64 grub2 error: file '/grub/i386-pc/normal.mod' not found

On Tue, 8/25/15, Pascal Hambourg wrote: // What does "ls (hd0,msdos1)/grub/" show ? Just a few files // and directories or plenty of *.mod files? I have the drive disconnected at the moment but, as far as I remember, "ls (hd0,msdos1)/grub/" shows all the files that are normally expected to b

Re: Wheezy amd64 grub2 error: file '/grub/i386-pc/normal.mod' not found

Ldten K a écrit : > > grub rescue> ls (hd0,msdos1)/ > config-3.2.0-4-amd64 grub initrd.img-3.2.0-4-amd64 lost+found > System.map-3.2.0-4-amd64 vmlinuz-3.2.0-4-amd64 > > grub rescue> set prefix=(hd0,msdos1)/grub > grub rescue> insmod normal > file '/grub/i386-pc/normal.mod not found

Re: Wheezy amd64 grub2 error: file '/grub/i386-pc/normal.mod' not found

On Mon, 8/24/15, Brian wrote: // If the device and path for prefix is correct you should see a grub // directory in the output of // // ls ((hd0,msdos1)/ // // Do you? Yes. grub rescue> ls (hd0,msdos1)/ config-3.2.0-4-amd64 grub initrd.img-3.2.0-4-amd64 lost+found System.map-3.2.0-4-am

Re: Wheezy amd64 grub2 error: file '/grub/i386-pc/normal.mod' not found

Ldten K a écrit : > > Am trying to restore my regular working HD from backup HD but booting > from the restored HD results in "file '/grub/i386-pc/normal.mod' not > found" error. This seems a bit odd since 1) my wheezy system is amd64 Indeed this seems odd, but not for that reason. "i386-pc" is j

  1   2   3   4   5   6   7   8   9   10   >