Error disk lvmid not found grub rescue - Исправление ошибок и поиск оптимальных решений проблем

Index
» Newbie Corner
» [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

Pages: 1

#1 2022-11-11 08:36:15

lv426: Member; Registered: 2022-11-11; Posts: 13

[SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

Greetings,

Yesterday I ran `pacman -Syu` for the first time. Upon reboot, I could no longer get into Arch Linux. I honestly don’t remember what the **original** problem was. Something with a kernel mismatch maybe? I spent an hour trouble shooting it to no avail. A post I found said I should reinstall GRUB, which I did. Doing that, completely broke the system and now I can’t get past the rescue screen.

I spent over 2 hours trying to solve this on my own and I am at a loss.

I am running Arch Linux with an encrypted root partition using LVM. Boot is not encrypted.

What I have tried:
— Use live USB to chroot in and…
— Confirm UUID’s match in etc/fstab
— Reinstall GRUB multiple times
— Recreate /boot/grub/grub.cfg
— `pacman -Syu linux`
— `mkinitcpio -p linux`
— Mount `boot` at `/boot` or `/boot/efi` or `/boot/EFI`, then reinstall GRUB, make the config again, confirm fstab matches.
— Confirm the lvmid shown in GRUB rescue matches `vgdisplay` and `lvdisplay`

Thanks

Last edited by lv426 (2022-11-16 03:30:09)

#2 2022-11-11 08:41:57

d.ALT: Member; Registered: 2019-05-10; Posts: 577

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

Topic solved, but /boot is encrypted. I suggest you taking a look at it anyway.

<49,17,III,I> Fama di loro il mondo esser non lassa;
<50,17,III,I> misericordia e giustizia li sdegna:
<51,17,III,I> non ragioniam di lor, ma guarda e passa.

#3 2022-11-11 16:43:25

lv426: Member; Registered: 2022-11-11; Posts: 13

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

Morning,

My boot partition is not encrypted. It’s not under lvm / luks.

I followed your instructions in the link, but am still presented with the same problem.

I created a keyfile and regenerated mkinitcpio.conf. I still get the same error.

Everything was working flawless before running `pacman -Syu`. Why would an upgrade break it? I never had to enter 2 passwords like the article mentions. Just once to unlock LUKS and the user or root password. I also never had a keyfile before this.

#4 2022-11-12 00:34:59

cfr: Member; From: Cymru; Registered: 2011-11-27; Posts: 7,127

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

If you boot the live media and mount your partitions what does

file /mnt/boot/vmlinuz-linux
pacman --root=/mnt/ -Qi linux
lsblk -f

give?

CLI Paste | How To Ask Questions

#5 2022-11-12 05:09:34

lv426: Member; Registered: 2022-11-11; Posts: 13

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

cfr wrote:

If you boot the live media and mount your partitions what does
file /mnt/boot/vmlinuz-linux
pacman --root=/mnt/ -Qi linux
lsblk -f
give?

`/mnt/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 6.0.8-arch1-1 (linux@archlinux) #1 SMP PREEMPT_DYNAMIC Thus, 10 Nov 2022 21:14:24 +0000, RO-rootFS, swap_dev 0XA, Normal VGA`

Name: linux
Version: 6.0.8.arch1-1
Description: The Linux kernel and modules
Architecture: x86_64
URL: https://github.com/archlinux/linux/commits/v6.0.8-arch1
Licenses: GPL2
Groups: None

sda
sda1 vfat FAT32 /mnt/boot
sda2 crypto_LUKS 2
lvm
volgroup0-lvol
ext4 /mnt

#6 2022-11-12 05:32:26

cfr: Member; From: Cymru; Registered: 2011-11-27; Posts: 7,127

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

OK, so the kernel in /boot matches your installed kernel. So if you did have a mismatch, that problem seems to be solved. You need to arch-chroot into the system before reinstalling grub and remaking its configuration file. It is important that you boot the live ISO in UEFI mode if you’re booting in UEFI mode. What commands are you using to reinstall grub and remake the config file once arch-chrooted? And do you get any errors or warnings?

CLI Paste | How To Ask Questions

#7 2022-11-13 05:41:59

lv426: Member; Registered: 2022-11-11; Posts: 13

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

cfr wrote:

OK, so the kernel in /boot matches your installed kernel. So if you did have a mismatch, that problem seems to be solved. You need to arch-chroot into the system before reinstalling grub and remaking its configuration file. It is important that you boot the live ISO in UEFI mode if you’re booting in UEFI mode. What commands are you using to reinstall grub and remake the config file once arch-chrooted? And do you get any errors or warnings?

Yeah, I think the kernel mismatch was the original problem, but I solved it (but not before breaking GRUB) after reading around.

Before running any commands and when in the live USB, boot is mounted to `mnt/boot`

To reinstall GRUB I am using `grub-install —target=x86_64-efi —bootloader-id=grub_uefi —recheck

then `grub-mkconfig -o /boot/grub/grub.cfg`

GRUB is installing to `/boot/efi`, which is default as far as I know. Also, that path is `etc/fstab`

I have tried other methods, such a mounting boot to `mnt/boot/efi` or changing `etc/fstab` to `/boot`. Nothing worked.

GRUB always installs. No errors, but I can’t actually get into GRUB. I always get the lvmid error.

#8 2022-11-13 06:04:46

cfr: Member; From: Cymru; Registered: 2011-11-27; Posts: 7,127

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

Are you doing

after mounting your partitions and before installing grub?
You need something like

grub-install --target=x86_64-efi --efi-directory=<path to your EFI partition in the chroot> --bootloader-id=GRUB

The above is just copy-pasted from the wiki.

You say you’re mounting boot to /mnt/boot. Is your EFI partition separate? If so, are you mounting it to /mnt/boot/EFI. Because if grub is installing to /boot/EFI, then your ESP needs to be mounted there. If your boot partition IS your EFI partition, you need to tell grub-install that. And you must be arch-chrooted for the grub-install step.

Last edited by cfr (2022-11-13 06:05:27)

CLI Paste | How To Ask Questions

#9 2022-11-14 07:47:55

lv426: Member; Registered: 2022-11-11; Posts: 13

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

These are my steps:

— Boot into live USB
— `cryptsetup open —type=luks /dev/sda2 lvm` > enter password
— `mount /dev/volgroup0/lvol /mnt`
— `mount /dev/sda1 /mnt/boot`
— `arch-chroot /mnt`

Then I run any of the commands I posted above.

There is only 1 boot / — EFI partition. That is /dev/sda1

When I am done, I exit chroot, unmount all, then reboot.

#10 2022-11-14 11:48:02

cfr: Member; From: Cymru; Registered: 2011-11-27; Posts: 7,127

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

You need to specify the directory for grub.

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB

As you say, grub is installing into /boot/efi, but that’s not your ESP. Your ESP is /boot.

CLI Paste | How To Ask Questions

#11 2022-11-14 20:39:36

lv426: Member; Registered: 2022-11-11; Posts: 13

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

cfr wrote:

You need to specify the directory for grub.
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
As you say, grub is installing into /boot/efi, but that’s not your ESP. Your ESP is /boot.

It worked! Thank you cfr. Now, when booted into Arch, the path looks like this: `/boot/efi/EFI/GRUB/grubx64.efi` I assume that’s correct considering it’s working.

What I don’t understand is why this didn’t work before when I changed `/mnt/boot` to `/mnt/boot/efi`. GRUB installed with no errors then, but still couldn’t boot. It seems like the `—efi-directory=<path>` was essential to making this work.

Unrelated to booting, but I had to remove the keyfile that was suggested in a linked post above. Otherwise, it wouldn’t prompt me for my encryption password and that is no good.

My final question:

— To prevent GRUB from breaking again, am I supposed to be mounting /boot every time I run `pacman -Syu` ?

Thanks

#12 2022-11-14 23:58:30

cfr: Member; From: Cymru; Registered: 2011-11-27; Posts: 7,127

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

lv426 wrote:

What I don’t understand is why this didn’t work before when I changed `/mnt/boot` to `/mnt/boot/efi`. GRUB installed with no errors then, but still couldn’t boot. It seems like the `—efi-directory=<path>` was essential to making this work.

I’m not sure why this would be expected to work. You have to do something special to install grub without arch-chrooting (which the wiki explains) but grub needs to know your ESP is not mounted at the default /boot/efi. If you just mount your ESP there, your kernels etc. won’t be under /boot but also under /boot/efi. I’m not sure that would matter for installing grub, but it would certainly screw up generating the configuration file.

lv426 wrote:

Unrelated to booting, but I had to remove the keyfile that was suggested in a linked post above. Otherwise, it wouldn’t prompt me for my encryption password and that is no good.

Agreed. That’s expected, though. People use keyfiles so they won’t have to type passwords or so they don’t have to rely on passwords. It can make sense if, say, you have boot encrypted, decrypt that with a password and then want other stuff decrypted without further intervention. Or if you keep the keyfile on an external device.

My final question:

— To prevent GRUB from breaking again, am I supposed to be mounting /boot every time I run `pacman -Syu` ?

Yes. If it is not mounted anyway, you need it mounted when you update the system. Specifically, you need it mounted when the kernel (or one of the kernels) is updated, but that is pretty frequent so mounting it before a system upgrade is safest. You might also need it mounted for other updates, but it will depend on what you have installed etc.

CLI Paste | How To Ask Questions

#13 2022-11-15 05:11:18

lv426: Member; Registered: 2022-11-11; Posts: 13

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

cfr wrote:

lv426 wrote:

What I don’t understand is why this didn’t work before when I changed `/mnt/boot` to `/mnt/boot/efi`. GRUB installed with no errors then, but still couldn’t boot. It seems like the `—efi-directory=<path>` was essential to making this work.

I’m not sure why this would be expected to work. You have to do something special to install grub without arch-chrooting (which the wiki explains) but grub needs to know your ESP is not mounted at the default /boot/efi. If you just mount your ESP there, your kernels etc. won’t be under /boot but also under /boot/efi. I’m not sure that would matter for installing grub, but it would certainly screw up generating the configuration file.

lv426 wrote:

Unrelated to booting, but I had to remove the keyfile that was suggested in a linked post above. Otherwise, it wouldn’t prompt me for my encryption password and that is no good.

Agreed. That’s expected, though. People use keyfiles so they won’t have to type passwords or so they don’t have to rely on passwords. It can make sense if, say, you have boot encrypted, decrypt that with a password and then want other stuff decrypted without further intervention. Or if you keep the keyfile on an external device.

My final question:

— To prevent GRUB from breaking again, am I supposed to be mounting /boot every time I run `pacman -Syu` ?

Yes. If it is not mounted anyway, you need it mounted when you update the system. Specifically, you need it mounted when the kernel (or one of the kernels) is updated, but that is pretty frequent so mounting it before a system upgrade is safest. You might also need it mounted for other updates, but it will depend on what you have installed etc.

Still confused about the efi directory. I guess I will just have to research this. I remember seeing examples of people using `/boot/efi` as the mount point, but I guess they used that option `—efi-directory=/boot/efi`, whereas I just assumed GRUB didn’t need to point to that path because it’s the default.

Is there a reason why /boot is not mounted by default during `pacman -Syu` when it is in my `/etc/fstab`? Having to manually mount for kernel upgrades, which happens so frequently on Arch compared to say, Ubuntu, seems like an annoyance. I haven’t run Ubuntu in sometime, but I don’t remember a kernel upgrade every breaking GRUB because /boot was not mounted. Then again, maybe Ubuntu’s kernel upgrade automatically mounted /boot in the background without me knowing.

#14 2022-11-15 16:35:28

cfr: Member; From: Cymru; Registered: 2011-11-27; Posts: 7,127

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

It depends how you configured things in fstab (or equivalent). On my system, boot is mounted at /boot all the time, so there’s no problem with upgrades. I believe this is pretty standard (and probably what happens on Ubuntu).

The point about the ESP path is that you’re mounting your ESP at /boot and NOT at /boot/efi. Grub probably assumes /boot/efi by default, but /boot is a common choice on Arch.

CLI Paste | How To Ask Questions

#15 2022-11-16 03:29:55

lv426: Member; Registered: 2022-11-11; Posts: 13

Re: [SOLVED] Stuck in GRUB rescue mode. error: disk ‘lvmid’ not found.

cfr wrote:

It depends how you configured things in fstab (or equivalent). On my system, boot is mounted at /boot all the time, so there’s no problem with upgrades. I believe this is pretty standard (and probably what happens on Ubuntu).

The point about the ESP path is that you’re mounting your ESP at /boot and NOT at /boot/efi. Grub probably assumes /boot/efi by default, but /boot is a common choice on Arch.

I changed `/boot/efi` to `/boot` in `/etc/fstab`. Hopefully I won’t have any problems when the next kernel upgrade comes along. If I do, I know how to fix it now through the live USB.

Thank you again for all your help. I really appreciate it.

Marking this solved.

Источник

I’ve been told I made a double post on how to fix my problem , which is not really the same question I asked at first .

O.K something stupid today while trying to use gpu passthrough which locked it up.
after a reboot I got the grub recover screen and started following this : https://pve.proxmox.com/wiki/Recover_From_Grub_Failure
Got a Ubuntu live cd , removed the other SSD drives which was passed to some VMs direct and started to follow it .

**** i’ve found the fault , how do I fix the :—-

/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr’ not found.

Code:

sudo vgscan
  Found volume group "pve" using metadata type lvm2
ubuntu@ubuntu:~$ sudo vgchange -ay
  26 logical volume(s) in volume group "pve" now active
ubuntu@ubuntu:~$ sudo mkdir /media/rescue
ubuntu@ubuntu:~$ sudo mount /dev/pve/root /media/rescue/
ubuntu@ubuntu:~$ sudo mount /dev/sda2 /media/rescue/boot/efi
ubuntu@ubuntu:~$ sudo mount -t proc proc /media/rescue/proc
ubuntu@ubuntu:~$ sudo mount -t sysfs sys /media/rescue/sys
ubuntu@ubuntu:~$ sudo mount -o bind /dev /media/rescue/dev
ubuntu@ubuntu:~$ sudo mount -o bind /run /media/run
ubuntu@ubuntu:~$ sudo mount -o bind /run /media/rescue/run
ubuntu@ubuntu:~$ chroot /media/rescue
ubuntu@ubuntu:~$ sudo chroot /media/rescue
root@ubuntu:/# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.13.19-4-pve
Found initrd image: /boot/initrd.img-5.13.19-4-pve
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
Found linux image: /boot/vmlinuz-5.13.19-3-pve
Found initrd image: /boot/initrd.img-5.13.19-3-pve
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
Found linux image: /boot/vmlinuz-5.13.19-2-pve
Found initrd image: /boot/initrd.img-5.13.19-2-pve
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
Found linux image: /boot/vmlinuz-5.13.19-1-pve
Found initrd image: /boot/initrd.img-5.13.19-1-pve
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
Found linux image: /boot/vmlinuz-5.11.22-7-pve
Found initrd image: /boot/initrd.img-5.11.22-7-pve
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
Found linux image: /boot/vmlinuz-5.11.22-5-pve
Found initrd image: /boot/initrd.img-5.11.22-5-pve
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
Found linux image: /boot/vmlinuz-5.11.22-4-pve
Found initrd image: /boot/initrd.img-5.11.22-4-pve
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
done
root@ubuntu:/# grub-install /dev/sda
Installing for x86_64-efi platform.
File descriptor 4 (/dev/sda2) leaked on vgs invocation. Parent PID 1295811: grub-install.real
File descriptor 4 (/dev/sda2) leaked on vgs invocation. Parent PID 1295811: grub-install.real
grub-install.real: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr' not found.

root@ubuntu:/# proxmox-boot-tool format /dev/sda2
UUID="0AB5-0AB6" SIZE="536870912" FSTYPE="vfat" PARTTYPE="c12a7328-f81f-11d2-ba4b-00a0c93ec93b" PKNAME="sda" MOUNTPOINT="/boot/efi"
E: '/dev/sda2' is mounted on '/boot/efi' - exiting.
root@ubuntu:/# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
E: /etc/kernel/proxmox-boot-uuids does not exist.
root@ubuntu:/# umount /dev/sda2
root@ubuntu:/# proxmox-boot-tool format /dev/sda2
UUID="0AB5-0AB6" SIZE="536870912" FSTYPE="vfat" PARTTYPE="c12a7328-f81f-11d2-ba4b-00a0c93ec93b" PKNAME="sda" MOUNTPOINT=""
E: '/dev/sda2' contains a filesystem ('vfat') - exiting (use --force to override)
root@ubuntu:/#

vgscan … found volume group pve using type lvmw …. looking good
vgchange -ay … 26 logical volumes on group pve … so far so good
mounted /dev/pve/root and can see the contents

Last edited: Mar 15, 2022

The recover from grub failure most be wrong ?
I’ve loaded proxmox on a second machine to workout how to fix it and made a couple of VMs on it.

I don’t think from all I’ve read you can’t mount a bios boot partition sda1 ? I think it should be sda2 ?

root@pve:~# lsblk -o +FSTYPE,UUID /dev/sda*
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT FSTYPE UUID
sda 8:0 0 447.1G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 512M 0 part /boot/efi vfat 8365-463F
└─sda3 8:3 0 446.6G 0 part LVM2_member YpaNXr-Chct-9n7A-HYP1-oTeo-tCI4-kuYfs2
├─pve-swap 253:0 0 8G 0 lvm [SWAP] swap fb96e8b0-d5a6-4090-ba8e-04387e36371e
├─pve-root 253:1 0 96G 0 lvm / ext4 db97cf6d-8f19-4df8-88ef-bae662e95bf7
├─pve-data_tmeta 253:2 0 3.3G 0 lvm
│ └─pve-data-tpool 253:4 0 320.1G 0 lvm
│ ├─pve-data 253:5 0 320.1G 1 lvm
│ ├─pve-vm—100—disk—0 253:6 0 16G 0 lvm
│ └─pve-vm—101—disk—0 253:7 0 16G 0 lvm
└─pve-data_tdata 253:3 0 320.1G 0 lvm
└─pve-data-tpool 253:4 0 320.1G 0 lvm
├─pve-data 253:5 0 320.1G 1 lvm
├─pve-vm—100—disk—0 253:6 0 16G 0 lvm
└─pve-vm—101—disk—0 253:7 0 16G 0 lvm
sda1 8:1 0 1007K 0 part
sda2 8:2 0 512M 0 part /boot/efi vfat 8365-463F
sda3 8:3 0 446.6G 0 part LVM2_member YpaNXr-Chct-9n7A-HYP1-oTeo-tCI4-kuYfs2
├─pve-swap 253:0 0 8G 0 lvm [SWAP] swap fb96e8b0-d5a6-4090-ba8e-04387e36371e
├─pve-root 253:1 0 96G 0 lvm / ext4 db97cf6d-8f19-4df8-88ef-bae662e95bf7
├─pve-data_tmeta 253:2 0 3.3G 0 lvm
│ └─pve-data-tpool 253:4 0 320.1G 0 lvm
│ ├─pve-data 253:5 0 320.1G 1 lvm
│ ├─pve-vm—100—disk—0 253:6 0 16G 0 lvm
│ └─pve-vm—101—disk—0 253:7 0 16G 0 lvm
└─pve-data_tdata 253:3 0 320.1G 0 lvm
└─pve-data-tpool 253:4 0 320.1G 0 lvm
├─pve-data 253:5 0 320.1G 1 lvm
├─pve-vm—100—disk—0 253:6 0 16G 0 lvm
└─pve-vm—101—disk—0 253:7 0 16G 0 lvm
root@pve:~#

so is the problem with sda1 or sda2 and how do I fix it ? , because I don’t think the guide works now ?

Last edited: Mar 13, 2022

I think that guide is too old. sda1 is a biosboot partition that is not intended to be mounted. sda2 is an ESP parition, but I don’t think you should mount that as /boot. Nowadays, Proxmox uses proxmox-boot-tool instead of running grub-install manually.

I think that guide is too old. sda1 is a biosboot partition that is not intended to be mounted. sda2 is an ESP parition, but I don’t think you should mount that as /boot. Nowadays, Proxmox uses proxmox-boot-tool instead of running grub-install manually.

Thanks , from what they say that looks correct it makes 3 partition , I’ve looked at all the what to do with a grub fault on debian and don’t think any would work. but I’m not sure how to use it on a dead system.
The created partitions are:

a 1 MB BIOS Boot Partition (gdisk type EF02)
a 512 MB EFI System Partition (ESP, gdisk type EF00)
a third partition spanning the set hdsize parameter or the remaining space used for the chosen storage type

Last edited: Mar 13, 2022

The partitions look fine (for a modern version of Proxmox). I suggest chroot-ing (as done in the old guide) into the pve-root and running proxmox-boot-tool to fix GRUB.
EDIT: Or maybe a grub-install /dev/sda1 is enough (from within the chroot of pve-root)?

Last edited: Mar 13, 2022

The partitions look fine (for a modern version of Proxmox). I suggest chroot-ing (as done in the old guide) into the pve-root and running proxmox-boot-tool to fix GRUB.
EDIT: Or maybe a grub-install /dev/sda1 is enough (from within the chroot of pve-root)?

Thank you , I’ve spent a full day going nowhere , so I will try that on my test machine and make sure it doesn’t do any thing stupid like deleting the LVM partition .

The partitions look fine (for a modern version of Proxmox). I suggest chroot-ing (as done in the old guide) into the pve-root and running proxmox-boot-tool to fix GRUB.
EDIT: Or maybe a grub-install /dev/sda1 is enough (from within the chroot of pve-root)?

good try on the proxmox boot tool , on a fully working system I tried following the guide with just a couple of changes , eg the mount points sda2 to boot/efi and the grub install and install didn’t kill it , them tried the proxmox-boot-tool , and that didn’t kill my system .
So now it’s the real system I doing to be format and working on …. Can’t be any worse that the place I’m in now.

Anyone got any ideas what the missing disk is and how to fix it.

root@ubuntu:/# update-grub
Generating grub configuration file …
Found linux image: /boot/vmlinuz-5.13.19-4-pve
Found initrd image: /boot/initrd.img-5.13.19-4-pve
/usr/sbin/grub-probe: error: disk `lvmid/vOy1fK-X2mn-83hH-h36r-9S2m-9QfZ-2ZYdTl/YdnS0p-FaHM-D2yz-DMca-5bla-10Hy-VDYIvr’ not found.

fiona

Proxmox Staff Member

Hi,
you may be hitting Debian bug 987008. According to message 21 there, the workaround is to change something in the LVM, e.g. adding a new volume to the thin pool might work, and then re-run update-grub.

This worked for me. Thanks!

I tried everything for a week , but in the end I just pulled all the VM backups from the disk , which was only a day old at the time, formatted and started again , one of my VMs was a Emby server which had a sperate zfs drive passed to it directly and was glad I could see all that data .
It was not what I wanted to do , but was getting nowhere fast or even slow .

Thanks .

HI,
I got this exact problem but..
I got no room to lvextend root partition.
Lv reduce seems to corrupt the install. Good thing I’m testing everything on a clone.

Still. it repairs grub anyway so I was able to confirm, booting off two drives, that my proxmox is still alive but locked under the broken GRUB.
I can’t believe this suddenly happened, I don’t even think it was caused by an update. The day before it booted fine.

Is there any other way to »nudge» the lv to commit a grub-update than to play with it’s boundaries?
Or, is there ANY other way at all to simply restore grub with proxmox….? In the past, i know there were some automated tools to do this but I suspect it can’t be that easy as I read threads about Proxmox Grub repairs.

any help will be appreciated.

HI,
I got this exact problem but..
I got no room to lvextend root partition.
Lv reduce seems to corrupt the install. Good thing I’m testing everything on a clone.

Still. it repairs grub anyway so I was able to confirm, booting off two drives, that my proxmox is still alive but locked under the broken GRUB.
I can’t believe this suddenly happened, I don’t even think it was caused by an update. The day before it booted fine.

Is there any other way to »nudge» the lv to commit a grub-update than to play with it’s boundaries?
Or, is there ANY other way at all to simply restore grub with proxmox….? In the past, i know there were some automated tools to do this but I suspect it can’t be that easy as I read threads about Proxmox Grub repairs.

any help will be appreciated.

Instead if playing with lvexpand, you can nudge the lvs another way:

Did a vgrename to pve (like pvee)
Revert back to pve,
did the grub-update, and it worked
(Note: It took a while, probably because it’s changing sub reps names for all my 52 lvs)

*Warning, In another occurrence, I tried renaming the LV (root) as I thought it would be more gentle, (like root to roooty back to root)
The update-grub worked and the instance booted but the screen got painted with errors with read only file system jazz and everything.
Still trying to determine if I’m dealing with a failed drive in the first place… Just wanted to avoid people trying to get as smart as I tried if it’s related, the Above pve vgrename method worked on the other drive.
* I really can’t confirm this aforementioned method is safe, but it can be.
https://forum.proxmox.com/threads/ext4-fs-error.116822/
This thread shows the errors I got, I suspect the m.2 drive to be dying or somehing wrong with the mobo … But at the moment I don’t have a perfect clue.

Last edited: Oct 19, 2022

Hi,

I also had issues with grub /usr/sbin/grub-probe: error: disk `lvmid/xxxxxxxxxxxx’ not found.

I’ve done that:

lvextend -L +1g /dev/pve/root
resize2fs /dev/pve/root
update-grub
and reboot

Now grub is ok but I have another issue during the boot process.

Superblock checksum does not match superblock while trying to open /dev/mapper/pve-root
….
….
…. you might try running efsck with an alternate block
….
….
mount: mounting /dev/mapper/pve-root on /root failed: Bad message.
Failed to mount /dev/mapper/pve-root as root file system.

And I only have BusyBox prompt after that.

I’ve try to fix the bad block while booting Proxmox from CD in advanced install (Linux prompt) but without success.

I’m using nvme ssd and I have 3 partitions : /dev/nvme0n1p1 , /dev/nvme0n1p2 and /dev/nvme0n1p3

Any suggestions / recommendations are welcome.

Regards,

Last edited: Jan 7, 2023

Hi,

I also had issues with grub /usr/sbin/grub-probe: error: disk `lvmid/xxxxxxxxxxxx’ not found.

I’ve done that:

Now grub is ok but I have another issue during the boot process.

And I only have BusyBox prompt after that.

I’ve try to fix the bad block while booting Proxmox from CD in advanced install (Linux prompt) but without success.

I’m using nvme ssd and I have 3 partitions : /dev/nvme0n1p1 , /dev/nvme0n1p2 and /dev/nvme0n1p3

View attachment 45328

Any suggestions / recommendations are welcome.

Regards,

I tried a week to fix my problem and in the end I just give up and started again with the backups . But what a learned is don’t keep the backups on the same disk it boots from . do daily backup of VM which change .
If you have all your backup which you can get to easy it is just a install proxmox , install from backups and you are off in under a hour .

I tried a week to fix my problem and in the end I just give up and started again with the backups . But what a learned is don’t keep the backups on the same disk it boots from . do daily backup of VM which change .
If you have all your backup which you can get to easy it is just a install proxmox , install from backups and you are off in under a hour .

Hi peter,

Thanks, I’m also considering this option but I would like to move VM and LXC data disk from my previous lvm pve partition to the new partition.

Hi peter,

Thanks, I’m also considering this option but I would like to move VM and LXC data disk from my previous lvm pve partition to the new partition.

I did that to one of my VMs I didn’t backup . I just did the create a new VM with the same number and just replaced the data disk for that VM.
That looked easier than working out to write all the config files .

Hi,

I also had issues with grub /usr/sbin/grub-probe: error: disk `lvmid/xxxxxxxxxxxx’ not found.

I’ve done that:

Now grub is ok but I have another issue during the boot process.

And I only have BusyBox prompt after that.

I’ve try to fix the bad block while booting Proxmox from CD in advanced install (Linux prompt) but without success.

I’m using nvme ssd and I have 3 partitions : /dev/nvme0n1p1 , /dev/nvme0n1p2 and /dev/nvme0n1p3

View attachment 45328

Any suggestions / recommendations are welcome.

Regards,

yes. as Peter suggested.
I’ve personally found similar issues with two Proxmox node having a single m.2 as Os/boot drive.
— In the process I cloned the m.2 to a ssd. And the instance ran fine… without this error.
— Pushed fresh backups, reinstalled, rejoin cluster, import backups. Less than 15 minutes
Never had an issue with any Sata SSD. And dedicate your m.2 storage for your Vms.

Источник

KaliDevHacker: Posts: 7; Joined: 2020-05-26 22:01; Location: Norway

grub rescue, error: disk ‘lvmid..’ not found,after grub-inst

Post

by KaliDevHacker » 2020-05-26 23:11

I am using a ‘Debian Jessie’ based debian kali linux. My system information, the output of the ‘sudo uname -a‘ command.
[Linux kali 5.5.0-kali2-amd64 #1 SMP Debian 5.5.17-1kali1 (2020-04-21) x86_64 GNU/Linux]
I deleted all partitions before i installed Windows 10 Enterprise. Before that my Linux worked perfectly. And it wont boot anymore, because i deleted my bootloader that was on my windows disk. I came across some solutions to my problem that was going to fix my bootloader. The solution i came across is the commands 6-31.I had to change the command 6 with command 1-5 because my /dev/sdb3 partition is crypto_LUKS filesystem. I beleive i fucked it up some place between command 1-5. I am not an experienced user, and after i rebooted my system i was in grub rescue mode.I hope there is someone here that can see where i fucked it up, and tell me what to do to fix the problem.

1. sudo cryptsetup open /dev/sdb3 backup
2. sudo lsblk -f /dev/sdb
3. sudo vgdisplay —short
4. sudo lvs -o lv_name,lv_size -S vg_name=server-vg
5. sudo mount /dev/server-vg/root /mnt
6. /*sudo mount /dev/sdb3 /mnt*/
7. sudo mount —bind /dev /mnt/dev
8. sudo mount —bind /proc /mnt/proc
9. sudo mount —bind /sys /mnt/sys
10. sudo mkdir /mnt/sys/firmware/efi/efivars
11. sudo mount —bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars
12. sudo mkdir /mnt/boot/efi
13. sudo mount /dev/sdb1 /mnt/boot/efi
14. sudo mount -o remount,rw /dev/sdb1 /mnt/boot/efi
15. sudo mkdir /mnt/hostrun
16. sudo mount —bind /run /mnt/hostrun
17. sudo chroot /mnt
18. mkdir /run/lvm
19. mount —bind /hostrun/lvm /run/lvm
20. grub-install /dev/sdb
21. update-grub
22. exit
23. sudo umount /mnt/dev
24. sudo umount /mnt/proc
25. sudo umount /mnt/sys/firmware/efi/efivars
26. sudo umount /mnt/sys
27. sudo umount /mnt/boot/efi
28. sudo umount /mnt/hostrun
29. sudo umount /mnt/run/lvm
30. sudo umount /mnt
31. sudo shutdown -r

error: disk ‘lvmid/C5jYs5-VQXZ-2Aak-Cm6v-QEvf-F9UM-BBDwOD/RK6yu3-loSB-MyBU-H7w3-ALqX-2tRO-570YLW’ not found.
grub rescue> ls
(hd0) (hd1) (hd2)
grub rescue>

[Linux server 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux]

DevPiggy

CwF: Section Moderator; Posts: 1775; Joined: 2018-06-20 15:16; Location: Colorado; Has thanked: 13 times; Been thanked: 53 times

sunrat: Administrator; Posts: 5215; Joined: 2006-08-29 09:12; Location: Melbourne, Australia; Has thanked: 56 times; Been thanked: 197 times

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

Post

by sunrat » 2020-05-27 02:46

cuckooflew wrote:«KaliDevHacker», where do they get the user names ?

The «Mr. Robot Effect» is still alive and kicking.
If I had a dollar for every time someone who shouldn’t be using Kali posts here, I’d have a few dollars. It’s definitely not for people who are «not an experienced user» and certainly won’t instantly turn anyone into a 133t h4x0r.

“ computer users can be divided into 2 categories:
Those who have lost data
…and those who have not lost data YET ” Remember to BACKUP!

cuckooflew: Posts: 680; Joined: 2018-05-10 19:34; Location: Some where out west; Been thanked: 1 time

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

Post

by cuckooflew » 2020-05-27 13:24

KaliDevHacker wrote:Thanx sickpig, looks like you are the only serious person in here

You should have asked at the kali forums, did you not notice : this is ; Debian User Forums Kali linux is NOT Debian
we (most of us)like to keep the forum strictly Debian related, and yes , as you can see we take that seriously, …so go figure.

Please Read What we expect you have already Done
Search Engines know a lot, and
«If God had wanted computers to work all the time, He wouldn’t have invented RESET buttons»
and
Just say NO to help vampires!

cuckooflew: Posts: 680; Joined: 2018-05-10 19:34; Location: Some where out west; Been thanked: 1 time

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

#10

Post

by cuckooflew » 2020-05-27 13:52

KaliDevHacker >> I am not an experienced user,

So why are you using Kali ? and why a user name that pretends to be Dev and Hacker ?
Please read these: https://www.kali.org/docs/introduction/ … ali-linux/

Is Kali Linux Right For You?

As the distribution’s developers, you might expect us to recommend that everyone should be using Kali Linux. The fact of the matter is, however, that Kali is a Linux distribution specifically geared towards professional penetration testers and security specialists, and given its unique nature, it is NOT a recommended distribution if you’re unfamiliar with Linux or are looking for a general-purpose Linux desktop distribution for development, web design, gaming, etc.

Even for experienced Linux users, Kali can pose some challenges. Although Kali is an open source project, it’s not a wide-open source project, for reasons of security. The development team is small and trusted, packages in the repositories are signed both by the individual committer and the team, and — importantly — the set of upstream repositories from which updates and new packages are drawn is very small. Adding repositories to your software sources which have not been tested by the Kali Linux development team is a good way to cause problems on your system.

While Kali Linux is architected to be highly customizable, don’t expect to be able to add random unrelated packages and repositories that are “out of band” of the regular Kali software sources and have it Just Work. In particular, there is absolutely no support whatsoever for the apt-add-repository command, LaunchPad, or PPAs. Trying to install Steam on your Kali Linux desktop is an experiment that will not end well. Even getting a package as mainstream as NodeJS onto a Kali Linux installation can take a little extra effort and tinkering.

If you are unfamiliar with Linux generally, if you do not have at least a basic level of competence in administering a system, if you are looking for a Linux distribution to use as a learning tool to get to know your way around Linux, or if you want a distro that you can use as a general purpose desktop installation, Kali Linux is probably not what you are looking for.

In addition, misuse of security and penetration testing tools within a network, particularly without specific authorization, may cause irreparable damage and result in significant consequences, personal and/or legal. “Not understanding what you were doing” is not going to work as an excuse.

However, if you’re a professional penetration tester or are studying penetration testing with a goal of becoming a certified professional, there’s no better toolkit — at any price — than Kali Linux.

And this:
http://www.isc.cnrs.fr/informatique/TheSmartWay.htm

When You Ask
Choose your forum carefully

Be sensitive in choosing where you ask your question. You are likely to be ignored, or written off as a loser, if you:

post your question to a forum where it’s off topic

KaliDevHacker: Posts: 7; Joined: 2020-05-26 22:01; Location: Norway

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

#11

Post

by KaliDevHacker » 2020-05-27 15:56

I started using Linux 30 years ago, i have just been away for 15 years. I know Linux, and i have no problem changing to Debian, and i will do that. I can install what package from Kali i want selves into Debian.

[Linux server 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux]

DevPiggy

cuckooflew: Posts: 680; Joined: 2018-05-10 19:34; Location: Some where out west; Been thanked: 1 time

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

#12

Post

by cuckooflew » 2020-05-27 16:28

Ok, and yes, actually all (or most) of the tools that Kali uses are available for Debian and in the Debian repositoriess,
and for Desktop use , Debian will be better. So any way, welcome back to Linux and welcome to the forum, apology if we seem «snobbish», but honestly we (most of us) really take Debian pretty seriously,..especially about keeping the forum dedicated to Debian. Thanks
Ahh, edit P.S. If you do re-install Debian, be more carefull when the installer asks where you want to install grub.

p.H: Section Moderator; Posts: 3015; Joined: 2017-09-17 07:12; Has thanked: 5 times; Been thanked: 122 times

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

#13

Post

by p.H » 2020-05-28 08:19

KaliDevHacker wrote:12. sudo mkdir /mnt/boot/efi

You should not have to create /boot/efi, it should already exist. Standard Debian installation with encrypted root creates a separate unencrypted /boot partition. It must be mounted before running grub-install, update-grub, update-initramfs or installing/removing/updating a kernel.

KaliDevHacker wrote:14. sudo mount -o remount,rw /dev/sdb1 /mnt/boot/efi

What is the point of this command ? The previous command already mounted the partition read-write.

If Kali was using the EFI partition on the Windows drive which was deleted, you should also update /etc/fstab with the UUID of the new EFI partition.

KaliDevHacker wrote:20. grub-install /dev/sdb

There is no point in specifying a device such as /dev/sdb when installing GRUB for EFI boot. It is ignored.

KaliDevHacker wrote:21. update-grub

That was not needed. /boot/grub/grub.cfg was not deleted and did not need to be updated.

KaliDevHacker wrote:Thanx sickpig, looks like you are the only serious person in here

At least you are wise enough to exclude yourself from the liste of serious people. If you were serious, you would have provided more information about your setup :
— boot scheme (UEFI or BIOS)
— drives
— partitions
— encrypted volumes
— LVM volumes
— /etc/fstab…

sickpig wrote:@OP

after installing grub
install lvm2 in chroot before installing grub if not already installed

Both useless actions. The initramfs does not need to be updated and lvm2 is already installed.

sunrat: Administrator; Posts: 5215; Joined: 2006-08-29 09:12; Location: Melbourne, Australia; Has thanked: 56 times; Been thanked: 197 times

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

#14

Post

by sunrat » 2020-05-28 09:04

KaliDevHacker wrote:I started using Linux 30 years ago, i have just been away for 15 years. I know Linux, and i have no problem changing to Debian, and i will do that. I can install what package from Kali i want selves into Debian.

Congratulations on using it 2 years before Linus Torvalds published the source code for the kernel!
Yeah we are a bit snobbish about Debian. Those of us who have been on this forum for a while have seen a plethora of help requests which have eventually been a pointless waste of time due to people using Debian-based systems rather than Debian. Many of these distros make modifications which make any help we try to give irrelevant. Kali is the worst as it attracts lots of script kiddies who have no idea what they are doing or why they are doing it, just that somehow they heard real hackers use it.
There are a lot of knowledgeable people here who will be happy to help with Debian questions if you have any. And I would advise to change your user name for people to take you seriously.

“ computer users can be divided into 2 categories:
Those who have lost data
…and those who have not lost data YET ” Remember to BACKUP!

trinidad: Posts: 253; Joined: 2016-08-04 14:58; Been thanked: 10 times

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

#15

Post

by trinidad » 2020-05-28 15:25

just that somehow they heard real hackers use it

Kali is fast becoming something that is at contretemps within itself in design and its reasonable purposes. Seems almost a hobbyist pursuit at times, though it claims to be both convenient and serious; still both claims are false. It is, like anything with a name, responsible for creating its own user base cache often filled with imbeciles, and yet it seems to struggle mightily against such incursions into its ego ridden claim to fame and name. All the more reason for Debian users to be peevish about the spillover into a Debian forum. I tested it once a few years ago in the Debian 8 era. Never since. It seems, though it has good tools available, to be geared to alluring the kind of audience it seems to haughtily reject. Maybe it is an ego exercise for its developers… i/e lure ’em in and then humiliate them. They seem to enjoy working that way with their audience. Yes the Debian forum absolutely should kick Kali users questions to the trash bucket, or start giving destructive answers… a humorous possibility, or send them a mail bot that keeps repeating «I am not Debian»

You can’t believe your eyes if your imagination is out of focus.

cuckooflew: Posts: 680; Joined: 2018-05-10 19:34; Location: Some where out west; Been thanked: 1 time

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

#16

Post

by cuckooflew » 2020-05-28 17:11

Congratulations on using it 2 years before Linus Torvalds published the source code for the kernel!

Good catch, I missed that,…but based on the wiki, and my calculator, it is only 1 year, so pretty close,..

Linux (/ˈlɪnəks/ (About this soundlisten) LIN-əks)[9][10] is a family of open source Unix-like operating systems based on the Linux kernel,[11] an operating system kernel first released on September 17, 1991, by Linus Torvalds.[12][13][14] Linux is typically packaged in a Linux distribution.

RU55EL: Posts: 545; Joined: 2014-04-07 03:42; Location: /home/russel

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

#17

Post

by RU55EL » 2020-05-28 18:39

Kali is (I believe) a tool for system administrators and others responsible for the care and security of computers, usually servers. It’s ironic, if you have to ask how to fix Kali, you are not one of the people it was designed for. In my exploration of Kali, I have come to the conclusion that I am nowhere near qualified to make use of it.

Kali is defiantly, a very poor choice as an everyday desktop system. That is not what it was designed for. Debian is a much better choice.

[edit]
I will also emphasize that Kali questions should be directed to the Kali Linux forum.
[/edit]

KaliDevHacker: Posts: 7; Joined: 2020-05-26 22:01; Location: Norway

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

#18

Post

by KaliDevHacker » 2020-05-29 21:53

You have absolutely right. In 1989-1992 i went computer engineer school in Bergen. It was Unix, not Linux.
I can see i have done a lot of failure here. Wrong distro, wrong forum, have to change my username or you all are going to
laugh at me for the rest of my life.
I am so sorry for doing all this mistakes. A forum moderator can delete my user, and you will never see me again.
I bet you were all expert users when you started the Linux, and you probably never did anything wrong.
Thank you very much for everything and goodbye

[Linux server 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux]

DevPiggy

cuckooflew: Posts: 680; Joined: 2018-05-10 19:34; Location: Some where out west; Been thanked: 1 time

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

#19

Post

by cuckooflew » 2020-05-30 01:00

Oh no , I feel so bad, almost makes me want to cry, but hey, you know, and we know, we all started out not knowing anything, made and still make mistake, some learned and still learn from their mistakes, and continue to make mistakes,learn and grow,…instead of just giving up.
The username , well I am sure we would get over that, and a little humour is good for everyone, but you could ask a admin to change the username, or you also could start a new account, and use a new username, or just keep the one you have…

cuckooflew wrote:Ok, and yes, actually all (or most) of the tools that Kali uses are available for Debian and in the Debian repositoriess,
and for Desktop use , Debian will be better. So any way, welcome back to Linux and welcome to the forum, apology if we seem «snobbish», but honestly we (most of us) really take Debian pretty seriously,..especially about keeping the forum dedicated to Debian. Thanks
Ahh, edit P.S. If you do re-install Debian, be more carefull when the installer asks where you want to install grub.

============

KaliDevHacker > Thank you very much for everything and goodbye

You are welcome, and all ways will be if and when you return, but any way, for now good bye, and don’t give up, next time probably will be better.
Oh, and P.S,

A forum moderator can delete my user,

No, sorry about this, the moderators and admins do not delete accounts, just like that, how ever you can read this :
Account Deletion the theread explains how you can disable your account yourself, if you really want to. But think seriously on that, once disabled it can not be re-enabled,….and I seriously doubt a admin would do it for you.

KaliDevHacker: Posts: 7; Joined: 2020-05-26 22:01; Location: Norway

Re: grub rescue, error: disk ‘lvmid..’ not found,after grub-

#20

Post

by KaliDevHacker » 2020-05-31 00:18

For me its all or nothing. I am a stubborn person, i will never give up, not Debian, and not my username. If you are gonna **** me because of my username, i would rather go for Arch linux if this is the only forum there is on Debian, or show you all that you are wrong for thinking i am stupid or a wannabe hacker that never will be anything more than a script kiddie.
I have allways been the comedian, or the funny guy because i like being that. I never said i was a hacker, i dont wanna be a hacker, and in the situations were people tell me how to act, i just do the opposite to **** them off. I like Debian, and i am serious about it, not because i work with it, just because i like it and i wanna be good in everything i do, or else its no point in doing it. You probably think i am 12 years old for picking a username like this, but i hope you one day will see past that and see me for my who i am, and not for a dumbass picking the wrong username. I was also trying to post this post in Kali Forum a week ago, it looks like they are not serious people at all. It never got on the forum, and i did not get any answer for why, so i ditch those people, and when i think about it, why use Kali, its probably just a couple of tools i am going to use from there anyway.

1) If you are willing to point me in the right direction for which debian distro i am gonna pick?
Please dont say Ubuntu, i dont like doing things the easy way, i will do it the hard way, because i learn more that way, better to force myselves using the terminal. I am learning python programming for the moment, and i wanna learn NASM programming. I was programming in Basic, Pascal, C, C++ and database back in the days.
2) What books will you recommend be buying?
I am currently reading «Kali Linux, Revealed», «Gray hat Hacking», and «Unix and Linux system administration Handbook»

[Linux server 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux]

DevPiggy

Источник

Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

Qortal1Windozz0: Level 1; Posts: 1; Joined: Mon Dec 20, 2021 7:30 pm

LVM: error: disk ‘lvmid/(uuid)’ not found. Entering grub rescue

Aloha! I keep having boot issues after I add a second disk. I thought maybe I could Avoid rebooting but that’s not true. System completes POST and never Grub- instead lands me in a black screen that says:

error: disk ‘lvmid/(uuid)’ not found.
Entering rescue mode …
grub rescue> _

What do I need to learn to command my computer to boot? I’m attempting to run a Qortal data node if I can ever get passed this problem.

Relevant hardware: gigabyte gbace w glued-on Celeron N3150 external Tb SSD was /dev/sda and Tb HDD was /dev/sdb before adding to VG. still a noob tho my skills at the command line have been increasing as I deal w new and more complex tissues TYVM for any time u have to help.

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

jwiz: Level 4; Posts: 276; Joined: Tue Dec 20, 2016 6:59 am

Re: LVM: error: disk ‘lvmid/(uuid)’ not found. Entering grub rescue

Post

by jwiz » Thu Dec 23, 2021 8:12 am

You’ve somehow managed to mess up grub so that it now doesn’t find the boot loader installation at startup.

For further info how to remedy this look here: https://www.howtoforge.com/tutorial/rep … ub-rescue/

Basically, you run the ‘set’ command to see the current grub default values, then do an ‘ls’ to figure out where the hdd with the grub installation now is.
Then do a ‘set prefix’ and ‘set root’ to point grub to that correct destination.
After that do an ‘insmod normal’ to load the module for normal start and then run the ‘normal’ command to boot the system.

Once you’ve succeded to boot up into your system do a ‘(sudo) grub reinstall’ to repair the broken boot installation.

Источник

This document (7024181) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 for POWER including all Service Packs

SUSE Linux Enterprise Server 15 for POWER including all Service Packs

Situation

After rebooting the system, grub2 can’t find the root volume anymore and is stuck with an error message similar to:

error: disk 'lvmid/eBY8sJ-l5YB-nVGq-dhld-lbDa-hQxT-P8eXl9/zbpPOS-yUU1-pgTr-QLJC-5jeK-d3ts-gNwtzw' not found.

The root volume group (LVM) was consisting of one physical volume (PV) but was running out of space, thus the VG was extended with new PV — the PV is located on a disk without partitions, ie. raw disk.

Resolution

On Power systems every boot disk must have partitions and its first partition must be PReP type.

An example of two root VG PVs which has PReP partition:

If a disk where root VG PV is located is a raw disk or does not have PReP partition as the first partition, new disk has to be used, partitioned, and existing LVM physical extends (PEs) have to be moved from to the correctly partitioned disk, that is, to the PV located on such disk.

GRUB2 uses PReP partitions to save boot data, thus raw disks, formatted as physical volumes (LVM), do not have a reserved space for the bootloader and boot may fail.

To correct the boot issue, the correct workflow would be (for demonstration purposes let’s assume the raw disk PV is /dev/mapper/360000000000000000000000000000000):

assign another LUN to the system (e.g. /dev/mapper/360000000000000000000000000000010)
boot from ISO
setup multipath if required (see link in ‘Additional information‘)
chroot to the installed system (see link in ‘Additional information‘)
update grub2 package to latest version! (old versions of GRUB2 had issues if root VG was extended over multiple PVs); eg: zypper up grub2*
create a GPT partition table on the newly added disk; eg. via fdisk /dev/mapper/360000000000000000000000000000010
create a PReP partition of about 8MB size on the newly added disk; eg. /dev/mapper/360000000000000000000000000000010-part1
create a second partition consuming all free space on the LUN, eg: /dev/mapper/360000000000000000000000000000010-part2
use `pvcreate‘ to create PV on the second partition on the newly added disk; eg: pvcreate /dev/mapper/360000000000000000000000000000010-part2
extend root VG with newly created PV; eg: vgextend system /dev/mapper/360000000000000000000000000000010-part2
use `pvmove‘ to move all physical extends (PEs) from the raw disk PV to the newly added PV; eg: pvmove /dev/mapper/360000000000000000000000000000000 /dev/mapper/360000000000000000000000000000010
modify /etc/default/grub_installdevice to refer to first partition on all disks where root VG is located
reinstall bootloader to first partition on all disks where root VG is located; eg: grub2-install /dev/mapper/360000000000000000000000000000000-part1 and continue with first partitions on the remaining root volume group disks
regenerate bootloader configuration: grub2-mkconfig -o /boot/grub2/grub.cfg

Cause

NOTE: This issue is only seen on POWER, other architectures are not affected as it’s caused by an issue in OpenFirmware.

Whenever there is more than one disk/LUN in the LVM volume group Openfirmware cannot find the bootloader so there must a PReP partition on each LUN and the bootloader needs to be installed (or refreshed in case of any changes) on all disks/LUNS.

Additional Information

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented «AS IS» WITHOUT WARRANTY OF ANY KIND.

Document ID:7024181
Creation Date:
15-Oct-2019
Modified Date:24-Oct-2022
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

Источник