ERROR: device ‘/dev/mapper/volumegroup-logicalvolume_root’ not found

This appears to be a duplicate from here, but I've been through that post many times and the solution (LVM#Troubleshouting) is already in place.

I'll post what I can about my system but it's not entirely accurate since I'm getting information via a live usb and using chroot:

[root@manjaro /]# inxi -Fx
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
System:
  Host: manjaro Kernel: 4.4.33-1-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 6.2.1 Desktop: Xfce 4.12.4 Distro: Manjaro Linux 
Machine:
  Type: Laptop System: Hewlett-Packard product: HP Pavilion dv6 Notebook PC 
  v: 0790100000205710000620100 serial: 2CE2250X6V 
  Mobo: Hewlett-Packard model: 181B v: 52.24 serial: PCRGD3A2G2T5EN 
  UEFI [Legacy]: Insyde v: F.2E date: 09/07/2016 
CPU:
  Topology: Quad Core model: Intel Core i7-3610QM bits: 64 type: MT MCP 
  arch: Ivy Bridge rev: 9 L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 36731 
  Speed: 1200 MHz min/max: 1200/3300 MHz Core speeds (MHz): 1: 1200 2: 1200 
  3: 1200 4: 1200 5: 1200 6: 1200 7: 1200 8: 1200 
Graphics:
  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel 
  bus ID: 00:02.0 
  Device-2: NVIDIA GF108M [GeForce GT 620M/630M/635M/640M LE] driver: N/A 
  bus ID: 01:00.0 
  Display: x11 server: X.Org 1.18.4 driver: intel resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 18.1.8 
  direct render: Yes 
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Sound Server: ALSA v: k4.4.33-1-MANJARO 
Network:
  Device-1: Intel Centrino Wireless-N 2230 driver: iwlwifi v: kernel 
  bus ID: 0a:00 
  IF: wlo1 state: up mac: 68:5d:43:8f:46:cf 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  driver: r8169 v: 2.3LK-NAPI port: 2000 bus ID: 0b:00 
  IF: eno1 state: down mac: a0:b3:cc:44:0a:2b 
Drives:
  Local Storage: total: 938.98 GiB used: 16.73 GiB (1.8%) 
  ID-1: /dev/sda vendor: Seagate model: ST1000LM024 HN-M101MBB 
  size: 931.51 GiB 
  ID-2: /dev/sdb type: USB vendor: OCZ model: OCZ size: 7.47 GiB 
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci 
  v: 3.0 bus ID: 00:1f.2 
Partition:
  ID-1: / size: 28.71 GiB used: 16.68 GiB (58.1%) fs: ext4 dev: /dev/dm-0 
  ID-2: /boot size: 247.0 MiB used: 47.9 MiB (19.4%) fs: ext2 dev: /dev/sda1 
Sensors:
  System Temperatures: cpu: 44.0 C mobo: 44.0 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 216 Uptime: 24m Memory: 7.70 GiB used: 1.49 GiB (19.4%) 
  Init: systemd Compilers: gcc: 8.2.1 Shell: bash v: 4.4.23 inxi: 3.0.21 

This started after trying linux414. I was running linux47 which has EOL status, but was working with the least number of issues in the journal log.

Now, I can't boot using any kernel.

I did remove linux414, from the live environment thinking a grub rebuild would help. It didn't.

Here is the error, prior to any attempts at fixing it - chrooting etc.:
(Sorry about the image. I don't know how to get this information in text format.)
ManjaroBoot

I've been researching this for days, and am now going in circles.

I'm hoping the great community here can help resolve this so I don't have to start fresh.

If there is a way to pull Home, and /etc for config files off the machine, I'd be more open reinstalling.

I was also in the process of trying to setup Amanda for backup - didn't get there.

So you chroot into your existing Manjaro and then use sudo mhwd-kernel -r linux[version] to remove the kernel? Were there errors logging in or using chroot?
Have you tried 4.9 kernel?
What method of chrooting did you use?

I thought with chroot there were no rich graphics output.. I didn't know that!

Was it similar to this?

This is amazingly old, so you did updates to the whole system to get to kernel 4.14 or other or did you just update the kernel?

I really feel like we are at a disadvantage to help here if you did not update the whole system and then the kernel. I mean there may be bugs with LVM older with the new kernel or maybe the rebuild of grub and the startup file system may not be working too.

I think this is from the Live ISO..

It is amazingly old. :grin:

1 Like

Anyway, it seems to me that somehow his grub is broken and I was only trying to get from the OP if he had actually chrooted correctly without errors so that when he ran the update-grub command it worked on the correct boot drive etc...
I am out of ideas atm.

1 Like

Here is what I did to chroot into my existing system - no errors using this method, taken from Restore the GRUB Bootloader:

[manjaro@manjaro ~]$ su
[manjaro manjaro]# lsblk -f
NAME   FSTYPE  LABEL       UUID                                   MOUNTPOINT
loop0  squashf                                                    /run/miso/sfs/
loop1  squashf                                                    /run/miso/sfs/
loop2  squashf                                                    /run/miso/sfs/
loop3  squashf                                                    /run/miso/sfs/
sda                                                               
├─sda1 ext2    ManjaroBoot 5da5dba5-d2bd-41c4-94f0-7057443d9124   
└─sda2 LVM2_me             SNe6HN-oLT6-1z7t-irA4-ySpE-TLqh-D3Nixa 
  ├─ManjaroVG-ManjaroRoot
  │    ext4    ManjaroRoot 868f3df5-8717-4ae2-8c2d-bb27ce09a2bd   
  ├─ManjaroVG-ManjaroHome
  │    ext4    ManjaroHome 13b9ba2c-eef1-43ac-a0f5-97bfe7559a49   
  └─ManjaroVG-ManjaroSwap
       swap    ManjaroSwap d8bd07d3-cd1a-4b14-8ac8-7c736dd0bdd5   
sdb                                                               
├─sdb1 vfat    E2B         9E9E-A033                              /run/media/man
├─sdb2 vfat    PTN2        2C5B-148A                              
└─sdb4 iso9660 MJR17112    2018-08-18-15-15-54-00                 /run/miso/boot
sr0                                                               
[manjaro manjaro]# mount /dev/ManjaroVG/ManjaroRoot /mnt
[manjaro manjaro]# mount /dev/sda1 /mnt/boot
[manjaro manjaro]# cd /mnt
[manjaro mnt]# mount -t proc proc /mnt/proc
[manjaro mnt]# mount -t sysfs sys /mnt/sys
[manjaro mnt]# mount -o bind /dev /mnt/dev
[manjaro mnt]# mount -t devpts pts /mnt/dev/pts/
[manjaro mnt]# chroot /mnt
[root@manjaro /]# 

After which, I use mhwd-kernel -r linux414 to remove the kernel. There were some warnings (from what I recall) when grub was rebuilding:

WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.

This was repeated many times, but I read that it was only because I was using a live environment.

I haven't tried 4.9. There doesn't seem to be a way of installing kernel on your existing system chrooting in. I did find some discussion on it here.

This is the Live ISO. I used it because I was getting mount: unknown filesystem type 'ext4' when I tried to mount using a newer ISO; manjaro-xfce-17.1.12-stable-x86_64.iso.

That said I just tried again - nth time - to get the error for you, and it worked. Hate that. :stuck_out_tongue_winking_eye:

I didn't actually run the update-grub command directly, as it's triggered automatically when installing/removing a Kernel, from what I understand.

Okay, here's what happens when mounting with manjaro-chroot using a newer Live ISO ([manjaro@manjaro ~]$ inxi -Fx System: Host: manjaro Kernel: 4.14.65-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: N/A Distro: Manjaro Linux )
and attempting update-grub:

[manjaro manjaro]# manjaro-chroot -a
File descriptor 3 (pipe:[36481]) leaked on vgs invocation. Parent PID 3305: grub-probe
File descriptor 9 (pipe:[46469]) leaked on vgs invocation. Parent PID 3305: grub-probe
File descriptor 3 (pipe:[36481]) leaked on vgs invocation. Parent PID 3305: grub-probe
File descriptor 9 (pipe:[46469]) leaked on vgs invocation. Parent PID 3305: grub-probe
File descriptor 3 (pipe:[36481]) leaked on vgs invocation. Parent PID 3384: grub-probe
File descriptor 9 (pipe:[46469]) leaked on vgs invocation. Parent PID 3384: grub-probe
File descriptor 3 (pipe:[36481]) leaked on vgs invocation. Parent PID 3384: grub-probe
File descriptor 9 (pipe:[46469]) leaked on vgs invocation. Parent PID 3384: grub-probe
==> Mounting (ManjaroLinux) [/dev/mapper/ManjaroVG-ManjaroRoot]
 --> mount: [/mnt]
 --> mount: [/mnt/boot]
 --> mount: [/mnt/home]
[root@manjaro /]# pacman -S mtools os-prober
warning: os-prober-1.76-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (2) mtools-4.0.18-4  os-prober-1.76-2

Total Download Size:   0.17 MiB
Total Installed Size:  0.48 MiB
Net Upgrade Size:      0.34 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 mtools-4.0.18-4-x86_64   179.1 KiB   779K/s 00:00 [######################] 100%
(2/2) checking keys in keyring                     [######################] 100%
(2/2) checking package integrity                   [######################] 100%
(2/2) loading package files                        [######################] 100%
(2/2) checking for file conflicts                  [######################] 100%
(2/2) checking available disk space                [######################] 100%
:: Processing package changes...
(1/2) installing mtools                            [######################] 100%
Optional dependencies for mtools
    libx11: required by floppyd [installed]
    libsm: required by floppyd [installed]
(2/2) reinstalling os-prober                       [######################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating the info directory file...
[root@manjaro /]# lsblk -f
NAME                      FSTYPE LABEL UUID MOUNTPOINT
loop0                                       
loop1                                       
loop2                                       
loop3                                       
sda                                         
|-sda1                                      /boot
`-sda2                                      
  |-ManjaroVG-ManjaroRoot                   /
  |-ManjaroVG-ManjaroHome                   /home
  `-ManjaroVG-ManjaroSwap                   
sdb                                         
|-sdb1                                      
|-sdb2                                      
`-sdb4                                      
sr0                                         
[root@manjaro /]# grub-install /dev/sda1
Installing for i386-pc platform.
grub-install: warning: File system `ext2' doesn't support embedding.
grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
grub-install: error: will not proceed with blocklists.
[root@manjaro /]# 

Try this again without the "1" >> grub-install /dev/sda

1 Like

Thanks for responding.

Here are the results:

[root@manjaro /]# grub-install /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.
[root@manjaro /]# grub-install --recheck /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.
[root@manjaro /]# update-grub
Generating grub configuration file ...
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Found background: /usr/share/grub/background.png
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Found linux image: /boot/vmlinuz-4.7-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.7-x86_64.img
Found initrd fallback image: /boot/initramfs-4.7-x86_64-fallback.img
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
grub-probe: error: cannot find a GRUB drive for /dev/sdb4.  Check your device.map.
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
[root@manjaro /]# 

You have to chroot to the installed system to properly repair and update grub.
It seems you used Live session. Was it?

Edit: You may have chrooted, but lvm not seen/setup properly?

If LVM wasn't recognized, how would it find the image?

Found linux image: /boot/vmlinuz-4.7-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.7-x86_64.img
Found initrd fallback image: /boot/initramfs-4.7-x86_64-fallback.img
1 Like

@bmoon, it seems like this should be solved already. I just do not have much experience with LVM.

Are you still getting the same error as the OP?
Have you checked your /etc/fstab to see that all the entries make sense? I am not sure that file gets a rewrite when installing a new kernel or grub but it might when dealing with LVM.

As I said (I think) I have no experience on lvm. Since no expert on this is available ..
Those error messages are not fatal.
What is grub current status?
There is an lvm config file in which you may disable lvmetad if you want.
I guess you would know more than me on lvm settings.
One thing I noticed, if it is important is you missed one command (mount run) on your 1st chroot, comparing to the tutorial.
Maybe one day I might install on lvm, out of curiosity ..

This image comes from another universe, way far from Earth.
Your system seems it has been transformed to a zombie?

I am still getting the same error.

My /etc/fstab seems like it makes sense.

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
#
UUID=5da5dba5-d2bd-41c4-94f0-7057443d9124 /boot ext2 defaults 0 0
UUID=13b9ba2c-eef1-43ac-a0f5-97bfe7559a49 /home ext4 defaults 0 0
UUID=868f3df5-8717-4ae2-8c2d-bb27ce09a2bd / ext4 rw,relatime,data=ordered 0 1
UUID=d8bd07d3-cd1a-4b14-8ac8-7c736dd0bdd5 swap swap defaults 0 0

GRUB is working fine. I didn't have any issues with it loading prior to restoring it either.

I didn't use the tutorial you posted above. Mounting /run wasn't part of the one I followed.

Forum kindly sponsored by