Detect other operating systems with grub #15

Closed
opened 2017-02-11 05:57:54 +00:00 by Chrysostomus · 10 comments
Chrysostomus commented 2017-02-11 05:57:54 +00:00 (Migrated from gitlab2.manjaro.org)

Currently update-grub fails when ran by the installer

Currently update-grub fails when ran by the installer
Chrysostomus commented 2017-02-11 20:30:06 +00:00 (Migrated from gitlab2.manjaro.org)

@oberon2007 Do you know how to get update-grub working in chroot? I am trying https://www.pckr.co.uk/arch-grub-mkconfig-lvmetad-failures-inside-chroot-install/ but I have trouble implementing it in the script.

@oberon2007 Do you know how to get update-grub working in chroot? I am trying https://www.pckr.co.uk/arch-grub-mkconfig-lvmetad-failures-inside-chroot-install/ but I have trouble implementing it in the script.
Chrysostomus commented 2017-02-11 20:40:18 +00:00 (Migrated from gitlab2.manjaro.org)

When done manually, the linked instruction seems to solve the error

/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.

However, I still get multiple

ERROR: mkdir /var/lock/dmraid

and no other systems are detected.

When done manually, the linked instruction seems to solve the error ``` /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. ``` However, I still get multiple ERROR: mkdir /var/lock/dmraid and no other systems are detected.
Chrysostomus commented 2017-02-11 20:41:53 +00:00 (Migrated from gitlab2.manjaro.org)

I think it also works if I use systemd-nspawn instead of chroot, but that would make us depend on systemd...

I think it also works if I use systemd-nspawn instead of chroot, but that would make us depend on systemd...
oberon commented 2017-02-11 21:44:08 +00:00 (Migrated from gitlab2.manjaro.org)

How exactly are you mounting partitions? How did you implement the --bind stuff?

How exactly are you mounting partitions? How did you implement the ``--bind`` stuff?
oberon commented 2017-02-11 21:45:08 +00:00 (Migrated from gitlab2.manjaro.org)

Here's another report of success with this: https://ubuntuforums.org/showthread.php?t=1965163

Here's another report of success with this: https://ubuntuforums.org/showthread.php?t=1965163
Chrysostomus commented 2017-02-11 21:58:35 +00:00 (Migrated from gitlab2.manjaro.org)

The Ubuntu guide seems to work in that it doesn't give any errors. It does not find the other systems either through.

The Ubuntu guide seems to work in that it doesn't give any errors. It does not find the other systems either through.
Chrysostomus commented 2017-02-11 22:07:00 +00:00 (Migrated from gitlab2.manjaro.org)
[root@manjaro matti]# mount --bind /run  /mnt/run
[root@manjaro matti]# manjaro-chroot /mnt/ "update-grub"
Generating grub configuration file ...
Found background: /usr/share/grub/background.png
Found Intel Microcode image
Found linux image: /boot/vmlinuz-4.4-x86_64
Found initrd image: /boot/initramfs-4.4-x86_64.img
Found initrd fallback image: /boot/initramfs-4.4-x86_64-fallback.img
ERROR: mkdir /var/lock/dmraid
ERROR: mkdir /var/lock/dmraid
ERROR: mkdir /var/lock/dmraid
ERROR: mkdir /var/lock/dmraid
ERROR: mkdir /var/lock/dmraid
ERROR: mkdir /var/lock/dmraid
ERROR: mkdir /var/lock/dmraid
ERROR: mkdir /var/lock/dmraid
ERROR: mkdir /var/lock/dmraid
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

Does not seem to be any better actually.

``` [root@manjaro matti]# mount --bind /run /mnt/run [root@manjaro matti]# manjaro-chroot /mnt/ "update-grub" Generating grub configuration file ... Found background: /usr/share/grub/background.png Found Intel Microcode image Found linux image: /boot/vmlinuz-4.4-x86_64 Found initrd image: /boot/initramfs-4.4-x86_64.img Found initrd fallback image: /boot/initramfs-4.4-x86_64-fallback.img ERROR: mkdir /var/lock/dmraid ERROR: mkdir /var/lock/dmraid ERROR: mkdir /var/lock/dmraid ERROR: mkdir /var/lock/dmraid ERROR: mkdir /var/lock/dmraid ERROR: mkdir /var/lock/dmraid ERROR: mkdir /var/lock/dmraid ERROR: mkdir /var/lock/dmraid ERROR: mkdir /var/lock/dmraid WARNING: Failed to connect to lvmetad. Falling back to device scanning. Found memtest86+ image: /boot/memtest86+/memtest.bin done ``` Does not seem to be any better actually.
oberon commented 2017-02-11 23:03:42 +00:00 (Migrated from gitlab2.manjaro.org)

I don't have any foreign OS installed... ;) but for me this works to get rid of the errors:

  • chroot with manjaro-chroot
  • use a new terminal window to mount --bind /run /mnt/run
  • now run update-grub in the first window
I don't have any foreign OS installed... ;) but for me this works to get rid of the errors: - chroot with **manjaro-chroot** - use a new terminal window to ``mount --bind /run /mnt/run`` - now run **update-grub** in the first window
Chrysostomus commented 2017-02-12 03:41:09 +00:00 (Migrated from gitlab2.manjaro.org)

I wonder if the problem might arise of the fact that I install on removable drive. Maybe having --removable flag in grub-install command might help...

I wonder if the problem might arise of the fact that I install on removable drive. Maybe having --removable flag in grub-install command might help...
Chrysostomus commented 2017-02-22 10:02:40 +00:00 (Migrated from gitlab2.manjaro.org)

Issue effects only installations on removable usb keys. Not a major problem then. Maybe we could add a information window that says: "Grub is now installed. If your other systems do not show in the grub menu, do not panic. Just boot and run 'sudo update-grub' in your manjaro installation."

Issue effects only installations on removable usb keys. Not a major problem then. Maybe we could add a information window that says: "Grub is now installed. If your other systems do not show in the grub menu, do not panic. Just boot and run 'sudo update-grub' in your manjaro installation."
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
applications/manjaro-architect#15
No description provided.