Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] grub fails
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Tue Nov 22, 2016 11:50 am    Post subject: [SOLVED] grub fails Reply with quote

Code:
blijevogelrups grub # grub-install /dev/sda
Installing for i386-pc platform.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[258571]) leaked on vgs invocation. Parent PID 14580: grub-install
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[259516]) leaked on vgs invocation. Parent PID 14580: grub-install
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
grub-install: error: disk `lvm/vg0-lvol1' not found.

Code:
blijevogelrups grub # grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/kernel-genkernel-x86_64-4.8.10-gentoo
Found initrd image: /boot/initramfs-genkernel-x86_64-4.8.10-gentoo
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[258705]) leaked on vgs invocation. Parent PID 14741: /usr/sbin/grub-probe
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[259611]) leaked on vgs invocation. Parent PID 14741: /usr/sbin/grub-probe
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
/usr/sbin/grub-probe: error: disk `lvm/vg0-lvol1' not found.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[259617]) leaked on vgs invocation. Parent PID 14800: /usr/sbin/grub-probe
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[257654]) leaked on vgs invocation. Parent PID 14800: /usr/sbin/grub-probe
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
/usr/sbin/grub-probe: error: disk `lvm/vg0-lvol1' not found.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[257658]) leaked on vgs invocation. Parent PID 14850: /usr/sbin/grub-probe
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[260666]) leaked on vgs invocation. Parent PID 14850: /usr/sbin/grub-probe
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
/usr/sbin/grub-probe: error: disk `lvm/vg0-lvol1' not found.
Found linux image: /boot/kernel-genkernel-x86_64-4.8.9-gentoo
Found initrd image: /boot/initramfs-genkernel-x86_64-4.8.9-gentoo
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[258770]) leaked on vgs invocation. Parent PID 14933: /usr/sbin/grub-probe
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[258774]) leaked on vgs invocation. Parent PID 14933: /usr/sbin/grub-probe
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
/usr/sbin/grub-probe: error: disk `lvm/vg0-lvol1' not found.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[259671]) leaked on vgs invocation. Parent PID 14984: /usr/sbin/grub-probe
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[259687]) leaked on vgs invocation. Parent PID 14984: /usr/sbin/grub-probe
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
/usr/sbin/grub-probe: error: disk `lvm/vg0-lvol1' not found.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[259701]) leaked on vgs invocation. Parent PID 15020: /usr/sbin/grub-probe
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
File descriptor 3 (pipe:[258808]) leaked on vgs invocation. Parent PID 15020: /usr/sbin/grub-probe
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "root_sda3" not found
  Cannot process volume group root_sda3
/usr/sbin/grub-probe: error: disk `lvm/vg0-lvol1' not found.
done

Code:
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed); notail increases performance of ReiserFS (at the expense of storage
# efficiency).  It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#

# <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/BOOT               /boot           ext2            noauto,noatime  1 2
/dev/ROOT               /               ext3            noatime         0 1
/dev/SWAP               none            swap            sw              0 0
/dev/cdrom              /mnt/cdrom   auto            noauto,ro   0 0
/dev/fd0                /mnt/floppy     auto            noauto          0 0

/dev/sda2               /boot           ext2            defaults,noatime   0 2
/dev/sda4               /               ext4            noatime         0 1
/dev/sda3               none            swap            sw              0 0


Last edited by farmer.ro on Tue Nov 22, 2016 4:11 pm; edited 1 time in total
Back to top
View user's profile Send private message
guitou
Guru
Guru


Joined: 02 Oct 2003
Posts: 534
Location: France

PostPosted: Tue Nov 22, 2016 12:03 pm    Post subject: Reply with quote

Hello.

There is a "device-mapper" use flag for grub to deal with logical volumes. Did you enable it?

++
Gi)
Back to top
View user's profile Send private message
farmer.ro
Apprentice
Apprentice


Joined: 20 Aug 2016
Posts: 179

PostPosted: Tue Nov 22, 2016 12:28 pm    Post subject: Reply with quote

i have the default /etc/default/grub and added:
Code:
# Append parameters to the linux kernel command line
GRUB_CMDLINE_LINUX="crypt_root=UUID=5c41bab7-1ea8-4962-b6e6-d7bf7a3d0a1c real_init=/usr/lib/systemd/systemd dolvm"


grub seems to work and pick ups my old kernel but after "grub-mkconfig -o /boot/grub/grub.cfg" grub does not seem to pick up my newest kernel upgrade, and only shows the old kernel when booting into the grub menu

SOLVED it seems grub did not pick up the new kernel because the new genkernel-next was missing some kernel modules (for file system)

after reading the systemd wiki and compile the kernel modules for systemd that wiki told me, after grub-mkconfig -o /boot/grub/grub.cfg the new genkernel-next 4.8.10 got picked up by grub.
Back to top
View user's profile Send private message
quazgar
n00b
n00b


Joined: 09 Feb 2017
Posts: 9

PostPosted: Thu Feb 09, 2017 8:56 am    Post subject: Reply with quote

guitou wrote:
There is a "device-mapper" use flag for grub to deal with logical volumes. Did you enable it?

I had a similar problem and that USE flag removed the error. Thanks! :)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum