Re: [pve-devel] Grub problems and ZFS
On 05/27/2015 12:15 PM, Dietmar Maurer wrote: IMHO this way of bypassing os-prober is cleaner than adding a 'Conflict' in our zfs-grub package, since it minimizes the packages conflicts when adding our proxmox repo on top of debian's. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701814#10 Should I prepare a patch ? please here a quick patch created with diff -u --- /etc/default/grub.orig 2015-05-28 10:27:29.056896944 +0200 +++ /etc/default/grub 2015-05-28 10:43:07.781829110 +0200 @@ -9,6 +9,10 @@ GRUB_CMDLINE_LINUX_DEFAULT=quiet GRUB_CMDLINE_LINUX= +# Disable os-prober, it might add menu entries for each guest +# root FS on a local partition +GRUB_DISABLE_OS_PROBER=true + # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Grub problems and ZFS
IMHO this way of bypassing os-prober is cleaner than adding a 'Conflict' in our zfs-grub package, since it minimizes the packages conflicts when adding our proxmox repo on top of debian's. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701814#10 Should I prepare a patch ? please ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Grub problems and ZFS
On 05/23/2015 09:19 AM, Dietmar Maurer wrote: As a side note os-prober is completely useless on a bare-metal installer and I think installing proxmox on top of Debian should remove this package too? I remove those 'recommend' line from our grub packages, but someone needs to report that to the debian maintainers. I raised today the topic on the debian-boot mailing list. In the meantime, we could avoid calling os-prober from grub by adding GRUB_DISABLE_OS_PROBER=true in /etc/default/grub as os-prober makes no sense in server environments [1] IMHO this way of bypassing os-prober is cleaner than adding a 'Conflict' in our zfs-grub package, since it minimizes the packages conflicts when adding our proxmox repo on top of debian's. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701814#10 Should I prepare a patch ? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Grub problems and ZFS
As a side note os-prober is completely useless on a bare-metal installer and I think installing proxmox on top of Debian should remove this package too? I remove those 'recommend' line from our grub packages, but someone needs to report that to the debian maintainers. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Grub problems and ZFS
Hi all, I might have found the cause for the sometimes failing grub install. As I updated the grub packages today I discovered very extended install time for the grub package which was related to the post-install script. The script ran for several minuttes and while running consuming a full core 100%. The cause for this was strictly related to the package os-prober which is used to find additional OS's and when you have attached a big number of iSCSI LUNs for KVM and/or CT storage this means that os-prober will scan all available connected LUNs for additional OS's. Could this be the cause for failing grub install? As a side note os-prober is completely useless on a bare-metal installer and I think installing proxmox on top of Debian should remove this package too? Yes os-prober is useless on a server (I have yet to meet a dual boot server ;) and similar problems have been reported in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701814 os-prober has priority extra ( apt-cache show os-prober | grep Priority ) so it is dafe to remove it but grub-common recommends it, which is why it was installed in the first place. IMHO the proper way to fix this, would be to convince the debian grub maintainers to move the dependency in the grub-common package from 'Recommends' to 'Suggest' and maybe add the os-prober as a dependency of the 'desktop' task of the debian installer so that Debian desktop users have it installed. Emmanuel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[pve-devel] Grub problems and ZFS
Hi all, I might have found the cause for the sometimes failing grub install. As I updated the grub packages today I discovered very extended install time for the grub package which was related to the post-install script. The script ran for several minuttes and while running consuming a full core 100%. The cause for this was strictly related to the package os-prober which is used to find additional OS's and when you have attached a big number of iSCSI LUNs for KVM and/or CT storage this means that os-prober will scan all available connected LUNs for additional OS's. Could this be the cause for failing grub install? As a side note os-prober is completely useless on a bare-metal installer and I think installing proxmox on top of Debian should remove this package too? -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen dot cc http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917 -- /usr/games/fortune -es says: For recreational use only. pgpdmsCQAdBzF.pgp Description: OpenPGP digital signature ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
