Re: SID: update-grub ---Warning: os-prober will not be executed to detect other bootable partitions.

On Thu 09 Dec 2021 at 08:28:37 (-0800), Peter Ehlert wrote: > the full error message at the end of update-grub: > > Warning: os-prober will not be executed to detect other bootable partitions. > Systems on them will not be added to the GRUB boot configuration. > Check GRUB_DI

SID: update-grub ---Warning: os-prober will not be executed to detect other bootable partitions.

the full error message at the end of update-grub: Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Question: why would this desirable? it's totally new

Re: update-grub: how to avoid scanning all devices

On 15 Dec 2017 at 13:42, Brian wrote: > Purge os-prober. Thanks, that's exactly what I was looking for. Steve

Re: update-grub: how to avoid scanning all devices

own filesystems include ext4? > > Filesystem instances, not filesystem types. > You can skip filesystems if you know their UUIDs. But e.g. an unreported > filesystem on a removable device won't be skipped. No removable device devices here. A machine with four ext4 partitions; nothing e

Re: update-grub: how to avoid scanning all devices

Le 15/12/2017 à 18:18, Brian a écrit : On Fri 15 Dec 2017 at 17:53:57 +0100, Pascal Hambourg wrote: . ‘GRUB_OS_PROBER_SKIP_LIST’ List of space-separated FS UUIDs of filesystems to be ignored from os-prober output. For efi

Re: update-grub: how to avoid scanning all devices

On Fri 15 Dec 2017 at 17:53:57 +0100, Pascal Hambourg wrote: > Le 15/12/2017 à 17:40, Brian a écrit : > > On Fri 15 Dec 2017 at 16:31:54 +0100, Pascal Hambourg wrote: > > > > > Le 15/12/2017 à 14:42, Richard Owlett a écrit : > > > > > > > > I have 2 similar problems which wouldn't be solved by

Re: update-grub: how to avoid scanning all devices

Le 15/12/2017 à 17:40, Brian a écrit : On Fri 15 Dec 2017 at 16:31:54 +0100, Pascal Hambourg wrote: Le 15/12/2017 à 14:42, Richard Owlett a écrit : I have 2 similar problems which wouldn't be solved by disabling os-prober. The common characteristic is wishing to probe all operating systems

Re: update-grub: how to avoid scanning all devices

On Fri 15 Dec 2017 at 16:31:54 +0100, Pascal Hambourg wrote: > Le 15/12/2017 à 14:42, Richard Owlett a écrit : > > > > I have 2 similar problems which wouldn't be solved by disabling os-prober. > > > > The common characteristic is wishing to probe all operating systems > > residing on on a

Re: update-grub: how to avoid scanning all devices

(intended to be multi-boot) for an unrelated machine. When I install the grub adds all OS from the "host" machine. By default, os-prober is installed and used by GRUB. So, after the installation you must boot the new system, disable os-prober or filter out its output as above and re-

Re: update-grub: how to avoid scanning all devices

On 12/15/2017 06:43 AM, Pascal Hambourg wrote: Le 15/12/2017 à 13:18, Steve Keller a écrit : When calling update-grub, it scans all devices for operating systems to put into the GRUB config. It even mounts all block devices to do the scan. I'd like to avoid this and let it scan only a number

Re: update-grub: how to avoid scanning all devices

Le 15/12/2017 à 13:18, Steve Keller a écrit : When calling update-grub, it scans all devices for operating systems to put into the GRUB config. It even mounts all block devices to do the scan. I'd like to avoid this and let it scan only a number of configured directories, in my case only /boot

Re: update-grub: how to avoid scanning all devices

On Fri 15 Dec 2017 at 13:18:17 +0100, Steve Keller wrote: > When calling update-grub, it scans all devices for operating systems > to put into the GRUB config. It even mounts all block devices to do > the scan. I'd like to avoid this and let it scan only a number of > configured

update-grub: how to avoid scanning all devices

When calling update-grub, it scans all devices for operating systems to put into the GRUB config. It even mounts all block devices to do the scan. I'd like to avoid this and let it scan only a number of configured directories, in my case only /boot. Scanning all devices is annoying because

Re: update-grub : fichier souvent pas adapté

Le 24/08/2015 13:02, andre_deb...@numericable.fr a écrit : On Sunday 23 August 2015 17:41:38 maderios wrote: Le 23/08/2015 16:20, Pascal Hambourg a écrit : maderios a écrit : Si on parle ici de grub2, update-grub se base sur /etc/default/grub pour créer les entrées de démarrage. Pour créer

Re: update-grub : fichier souvent pas adapté

On Sunday 23 August 2015 17:41:38 maderios wrote: Le 23/08/2015 16:20, Pascal Hambourg a écrit : maderios a écrit : Si on parle ici de grub2, update-grub se base sur /etc/default/grub pour créer les entrées de démarrage. Pour créer les entrées des noyaux du système actif. Ici on parle

Re: update-grub : fichier souvent pas adapté

Le 23/08/2015 16:20, Pascal Hambourg a écrit : maderios a écrit : Si on parle ici de grub2, update-grub se base sur /etc/default/grub pour créer les entrées de démarrage. Pour créer les entrées des noyaux du système actif. Ici on parle des entrées générées pour les autres systèmes présents

Re: update-grub : fichier souvent pas adapté

andre_deb...@numericable.fr a écrit : Boot sda7 : UUID de l'option root=... est bien sda5 ce qui ne va pas, il boote alors sur sda5 Quelle(s) ligne(s) de grub.cfg de sda7 dois-je modifier ? Tu n'as pas une petite idée ? Pour l'instant j'ai copié grub.cfg de sda5 vers sda7... qui lui a

Re: update-grub : fichier souvent pas adapté

On Sunday 23 August 2015 11:24:36 Pascal Hambourg wrote: andre_deb...@numericable.fr a écrit : Boot sda7 : UUID de l'option root=... est bien sda5 ce qui ne va pas, il boote alors sur sda5 Quelle(s) ligne(s) de grub.cfg de sda7 dois-je modifier ? Tu n'as pas une petite idée ? :

Re: update-grub : fichier souvent pas adapté

maderios a écrit : Si on parle ici de grub2, update-grub se base sur /etc/default/grub pour créer les entrées de démarrage. Pour créer les entrées des noyaux du système actif. Ici on parle des entrées générées pour les autres systèmes présents. Merci de suivre.

Re: update-grub : fichier souvent pas adapté

andre_deb...@numericable.fr a écrit : On Sunday 23 August 2015 11:24:36 Pascal Hambourg wrote: Quelle(s) ligne(s) de grub.cfg de sda7 dois-je modifier ? Tu n'as pas une petite idée ? : Remettre sda7 avec son bon UUID= et root= Oui. Tu peux aussi regénérer le fichier avec update-grub

Re: update-grub : fichier souvent pas adapté

sda5 ? Je viens de l'écrire : update-grub se base dessus pour créer les entrées de démarrage pour le noyau trouvé sur sda7. Cela lui permet notamment d'importer les paramètres de la ligne de commande du noyau. Quelle(s) ligne(s) de grub.cfg de sda7 dois-je modifier ? Pour l'instant j'ai copié

Re: update-grub : fichier souvent pas adapté

de sda7 a t-il une influence sur grub.cfg créé sous sda5 ? Je viens de l'écrire : update-grub se base dessus pour créer les entrées de démarrage pour le noyau trouvé sur sda7. Cela lui permet notamment d'importer les paramètres de la ligne de commande du noyau. Quelle(s) ligne(s) de grub.cfg de

Re: update-grub : fichier souvent pas adapté

maderios a écrit : Le 23/08/2015 16:20, Pascal Hambourg a écrit : maderios a écrit : Si on parle ici de grub2, update-grub se base sur /etc/default/grub pour créer les entrées de démarrage. Pour créer les entrées des noyaux du système actif. Ici on parle des entrées générées pour les autres

Re: update-grub : fichier souvent pas adapté

On Saturday 22 August 2015 00:14:35 Pascal Hambourg wrote: andre_deb...@numericable.fr a écrit : update-grub n'a pas à mettre une entrée UUID différente, dans set=root ... et root=UUID= Bien sûr que si. Je viens d'expliquer que ce sont deux choses totalement différentes. Typiquement

Re: update-grub : fichier souvent pas adapté

regénéré après avoir amorcé le système avec sda7 comme racine. En quoi le grub.cfg de sda7 a t-il une influence sur grub.cfg créé sous sda5 ? Je viens de l'écrire : update-grub se base dessus pour créer les entrées de démarrage pour le noyau trouvé sur sda7. Cela lui permet notamment d'importer

Re: update-grub : fichier souvent pas adapté

On Friday 21 August 2015 22:23:11 Pascal Hambourg wrote: andre_deb...@numericable.fr a écrit : # update-grub ne créé pas un fichier adapté à la configuration des partitions du ou des disques durs. Exemple, sur une partition de sauvegarde, sda7, clone de sda5=Wheezy, il s'escrime à

Re: update-grub : fichier souvent pas adapté

andre_deb...@numericable.fr a écrit : # update-grub ne créé pas un fichier adapté à la configuration des partitions du ou des disques durs. Exemple, sur une partition de sauvegarde, sda7, clone de sda5=Wheezy, il s'escrime à chaque fois à mettre deux UIDD différents : UUID, pas UIDD

Re: update-grub : fichier souvent pas adapté

volume il doit chercher les fichiers d'amorçage (image du noyau, initrd...) ; la seconde indique au noyau (ou plutôt à l'initramfs de nos jours) le volume à monter comme racine. update-grub n'a pas à mettre une entrée UUID différente, dans set=root ... et root=UUID= Bien sûr que si. Je

Re: update-grub : fichier souvent pas adapté

Le 18/08/2015 19:43, andre_deb...@numericable.fr a écrit : sda7 est un clone de sda5, mais adapté pour être bootable (/etc/fstab), en cas de crash de sda5. Normalement, update-grub devrait mettre correctement les infos pour la partition sda7. tu peux jeter un oeil aux scripts et à

Re: update-grub : fichier souvent pas adapté

On Tuesday 18 August 2015 20:20:52 didier gaumet wrote: Le 18/08/2015 19:43, andre_deb...@numericable.fr a écrit : sda7 est un clone de sda5, mais adapté pour être bootable (/etc/fstab), en cas de crash de sda5. Normalement, update-grub devrait mettre correctement les infos pour la

Re: update-grub : fichier souvent pas adapté

On Tuesday 18 August 2015 17:46:09 didier gaumet wrote: si sda7 est un vrai clone de sda5, le comportement de grub me paraîtrait plutôt logique. sda7 est un clone de sda5, mais adapté pour être bootable (/etc/fstab), en cas de crash de sda5. Normalement, update-grub devrait mettre correctement

Re: update-grub : fichier souvent pas adapté

Hello, Le 18/08/2015 19:43, andre_deb...@numericable.fr a écrit : Voici le contenu de 40_custom : menuentry TOUTOU on /dev/sda2 { insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set

Re: update-grub : fichier souvent pas adapté

On Tuesday 18 August 2015 21:34:13 didier gaumet wrote: désolé d'avoir d'abord répondu en privé, je me suis gourré de bouton :-( : Pas grave. Le 18/08/2015 20:51, andre_deb...@numericable.fr a écrit : Parfois j'utilise Toutou-Linux sur clé USB... ce qui pourrait en expliquer sa présence.

Re: update-grub : fichier souvent pas adapté

désolé d'avoir d'abord répondu en privé, je me suis gourré de bouton :-( Le 18/08/2015 20:51, andre_deb...@numericable.fr a écrit : Parfois j'utilise Toutou-Linux sur clé USB... ce qui pourrait en expliquer sa présence. ça paraît quand même bizarre: la détection automatique d'autres systèmes

Re: update-grub : fichier souvent pas adapté

Le 18/08/2015 22:38, andre_deb...@numericable.fr a écrit : [...] ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### Entre ces deux lignes de grub.cfg = 40_custom ? oui

update-grub : fichier souvent pas adapté

Bonjour à tous, Chez moi, # update-grub ne créé pas un fichier adapté à la configuration des partitions du ou des disques durs. Exemple, sur une partition de sauvegarde, sda7, clone de sda5=Wheezy, il s'escrime à chaque fois à mettre deux UIDD différents : = set=root UIDD de sda7 = OK

Re: update-grub : fichier souvent pas adapté

si sda7 est un vrai clone de sda5, le comportement de grub me paraîtrait plutôt logique. par contre il n'est pas recommandé d'éditer grub.cfg: tu vas perdre tes modifs à chaque fois que le fichier sera automatiquement régénéré. il vaudrait mieux pour ton usage soit modifier éventuelement

Afegir línies a grub.cfg i que al fer update-grub no es casquin

-a0a9-420c-89a9-5164ad86607e ro console=ttyS0,115200n8 quiet el console=ttyS0,115200n8 però al fer update-grub es matxaca. He vist que a /etc/grub.d/ hi ha fitxers, però no tinc clar quin hauria de modificar. Alguna idea? Moltes gràcies [1] http://blackhold.nusepas.com/2015/04/instalar-debian

update-grub

After bending my brains for a day fixing little problems, after upgrading to Jessie, I'm noticing a weird behavior. I have Ubuntu on /dev/sda3 and Debian on /dev/sdb1. When I run update-grub, it notices the Ubuntu partition yet when I boot, the old selection for Ubuntu is no longer

Re: update-grub

On 21/02/14 20:06, Ric Moore wrote: After bending my brains for a day fixing little problems, after upgrading to Jessie, I'm noticing a weird behavior. I have Ubuntu on /dev/sda3 and Debian on /dev/sdb1. When I run update-grub, it notices the Ubuntu partition yet when I boot, the old

Re: update-grub

On 21/02/14 20:27, Scott Ferguson wrote: On 21/02/14 20:06, Ric Moore wrote: After bending my brains for a day fixing little problems, after upgrading to Jessie, I'm noticing a weird behavior. I have Ubuntu on /dev/sda3 and Debian on /dev/sdb1. When I run update-grub, it notices the Ubuntu

Re: update-grub

On Fri, 21 Feb 2014, Ric Moore wrote: After bending my brains for a day fixing little problems, after upgrading to Jessie, I'm noticing a weird behavior. I have Ubuntu on /dev/sda3 and Debian on /dev/sdb1. When I run update-grub, it notices the Ubuntu partition yet when I boot, the old

Re: Understanding output from update-grub with md

device. Or so I thought. After updating installing latest 7.4 kernel and rebooting I noticed it was running an older kernel. Output from update-grub suggested that two unused spares somehow had older versions of the / partition. I added them back as hot spares and then made them mirrors

update-grub hangs when starting with systemd

Anyone know why update-grub would hang when started with systemd? Here is a successful normal run after booting with sysvinit: $ sudo update-grub Generating grub.cfg ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-3.11-2-amd64 Found

Re: how does update-grub choose the root filesystem

/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. I want to achieve the mimimum of downtime on the machine I am trying to make this work

Re: how does update-grub choose the root filesystem

. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. I want to achieve the mimimum of downtime

Re: how does update-grub choose the root filesystem

/sda and /dev/sdb to boot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. I

Re: how does update-grub choose the root filesystem

and /dev/sdb to boot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. grub-install

Re: how does update-grub choose the root filesystem

is to install grub on both /dev/sda and /dev/sdb to boot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about

Re: how does update-grub choose the root filesystem

/sda1 and an empty slot. My desire is to install grub on both /dev/sda and /dev/sdb to boot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused

Re: how does update-grub choose the root filesystem

On Wed, Jul 4, 2012 at 7:22 PM, Alan Chandler a...@chandlerfamily.org.uk wrote: I am trying to figure out how to move my current rootfs to raid1 (its just a partition at the moment). The plan is to make a a raid device, copy the current root fs in to it - but I then need to tell grub to set

how does update-grub choose the root filesystem

I am trying to figure out how to move my current rootfs to raid1 (its just a partition at the moment). The plan is to make a a raid device, copy the current root fs in to it - but I then need to tell grub to set up this up as the root for the boot. How do I do this? -- Alan Chandler

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On 2010-07-13 07:45 +0200, H.S. wrote: On 13/07/10 01:28 AM, Tom H wrote: Yes. The Fedora/RHEL initrd names are not recognized by Debian/Ubuntu's grub... It should work in os-prober 1.39. I see. Could you briefly explain why is that? Because Fedora uses initramfs$something as the name

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On Tue, Jul 13, 2010 at 2:02 AM, Sven Joachim svenj...@gmx.de wrote: On 2010-07-13 07:45 +0200, H.S. wrote: On 13/07/10 01:28 AM, Tom H wrote: Yes. The Fedora/RHEL initrd names are not recognized by Debian/Ubuntu's grub... It should work in os-prober 1.39. Thanks for the info. As I said

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On 13/07/10 01:58 AM, Tom H wrote: Quite frankly, I thought that this had been fixed (I read it on either the Debian or Ubuntu bug reporting system), but I came across this problem last year and the script was looking for initrds of the form initrd.img-... and therefore ignored initramfs...

Re: Why does not update-grub detect Fedora 13 installation?

On Mon, 12 Jul 2010 00:17:53 -0400, H.S. wrote: (...) Now when I do update-grub in Debian, it detects all OSes installed in the hard drives connected to the system, but does not detect Fedora 13. I had to manually add the stanza lines for F13 to get its option in the grub boot list. I am

Re: Why does not update-grub detect Fedora 13 installation?

On 12/07/10 12:15 PM, Camaleón wrote: On Mon, 12 Jul 2010 00:17:53 -0400, H.S. wrote: (...) Now when I do update-grub in Debian, it detects all OSes installed in the hard drives connected to the system, but does not detect Fedora 13. I had to manually add the stanza lines for F13 to get

Re: Why does not update-grub detect Fedora 13 installation?

On Mon, 12 Jul 2010 12:24:44 -0400, H.S. wrote: On 12/07/10 12:15 PM, Camaleón wrote: I don't know so much how the new beast (GRUB2) works, but if man update-grub¹ is right, it will detect all the vmlinuz files that are under the /boot partition, not sure if this condition fits in your case

Re: Why does not update-grub detect Fedora 13 installation?

On 12/07/10 01:09 PM, Camaleón wrote: I think windows OS falls apart (as there are no vmlinuz files to detect) but fedora9 should be the same case than Fedora13, provided that is also located in a different disk. When you run the update-grub command, it writes a bad entry for fedora13

Re: Why does not update-grub detect Fedora 13 installation?

On 2010-07-12 19:09 +0200, Camaleón wrote: Also, take a look into the bugs that have already filled for grub-pc: http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=grub-pc s/grub-pc/os-prober/ Foreign operating systems are (supposed to be) detected by os-prober, so if Fedora 13 does not

Re: Why does not update-grub detect Fedora 13 installation?

On Mon, 12 Jul 2010 19:22:29 +0200, Sven Joachim wrote: On 2010-07-12 19:09 +0200, Camaleón wrote: Also, take a look into the bugs that have already filled for grub-pc: http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=grub-pc s/grub-pc/os-prober/ Foreign operating systems are

Re: Why does not update-grub detect Fedora 13 installation?

On 12/07/10 01:22 PM, Sven Joachim wrote: On 2010-07-12 19:09 +0200, Camaleón wrote: Also, take a look into the bugs that have already filled for grub-pc: http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=grub-pc s/grub-pc/os-prober/ Foreign operating systems are (supposed to be)

Re: Why does not update-grub detect Fedora 13 installation?

On 12/07/10 01:41 PM, Camaleón wrote: On Mon, 12 Jul 2010 19:22:29 +0200, Sven Joachim wrote: On 2010-07-12 19:09 +0200, Camaleón wrote: Also, take a look into the bugs that have already filled for grub-pc: http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=grub-pc s/grub-pc/os-prober/

Re: Why does not update-grub detect Fedora 13 installation?

On 2010-07-12 19:41 +0200, Camaleón wrote: On Mon, 12 Jul 2010 19:22:29 +0200, Sven Joachim wrote: On 2010-07-12 19:09 +0200, Camaleón wrote: Also, take a look into the bugs that have already filled for grub-pc: http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=grub-pc

Re: Why does not update-grub detect Fedora 13 installation?

should be needed/installed. In Squeeze, grub-common therefore recommends os-prober (but not in Lenny due to bug #476184¹). More than recommended it should be required, provided that update- grub will lack some features if not present :-? ¹ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476184

Re: Why does not update-grub detect Fedora 13 installation?

(but not in Lenny due to bug #476184¹). More than recommended it should be required, provided that update- grub will lack some features if not present :-? No, there are people like yours truly who use Debian as their sole operating system. Others might use some other bootloader in the MBR and chainload

[SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

this earlier. Curiously though, update-grub is now detecting Fedora 13! It was not doing so last night. And my bash history shows that I did not install os-prober between then and now. I check my aptitude log and it shows that os-prober was on HOLD three days ago (I supposed when I did the initial

Re: Why does not update-grub detect Fedora 13 installation?

On 07/12/2010 12:17 PM, H.S. wrote: On a newly installed Debian Testing system, I installed Fedora 13 in a partition but chose not to install the boot loaded since I wanted to use Debian's boot loader for all OSes. Now when I do update-grub in Debian, it detects all OSes installed in the hard

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On 12/07/10 03:07 PM, H.S. wrote: Curiously though, update-grub is now detecting Fedora 13! It was not Well, I wrote that too soon. Here is what update-grub puts in /boot/grub /grub.cfg regarding the Fedora 13 installation: ### menuentry

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On Tue, Jul 13, 2010 at 12:37 AM, H.S. hs.sa...@gmail.com wrote: On 12/07/10 03:07 PM, H.S. wrote: Curiously though, update-grub is now detecting Fedora 13! It was not Well, I wrote that too soon. Here is what update-grub puts in /boot/grub /grub.cfg regarding the Fedora 13 installation

Re: Why does not update-grub detect Fedora 13 installation?

be added to grub2's menu after update-grub is run. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktilmnipfuo3yugc519t4ibov2nihtrf5lbryb...@mail.gmail.com

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On 13/07/10 01:28 AM, Tom H wrote: On Tue, Jul 13, 2010 at 12:37 AM, H.S. hs.sa...@gmail.com wrote: It is missing the initrd line. Without that line the kernel does not boot and panics and halts. I have to put the correct stanza myself in /etc/grub.d/40_custom to get the correct grub entry

Re: Why does not update-grub detect Fedora 13 installation?

. Any system that you install after Debian is added (in my experience) or should be added to grub2's menu after update-grub is run. If you have os-prober installed, that is. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On Tue, Jul 13, 2010 at 1:45 AM, H.S. hs.sa...@gmail.com wrote: On 13/07/10 01:28 AM, Tom H wrote: On Tue, Jul 13, 2010 at 12:37 AM, H.S. hs.sa...@gmail.com wrote: It is missing the initrd line. Without that line the kernel does not boot and panics and halts. I have to put the correct

Why does not update-grub detect Fedora 13 installation?

On a newly installed Debian Testing system, I installed Fedora 13 in a partition but chose not to install the boot loaded since I wanted to use Debian's boot loader for all OSes. Now when I do update-grub in Debian, it detects all OSes installed in the hard drives connected to the system

Re: Update GRUB to GRUB2 / Lenny to Squeeze

Tom H wrote: On Sun, Jun 6, 2010 at 5:30 PM, lrhorer lrho...@satx.rr.com wrote: You can't load modules for grub-probe. But you can for grub-install. The default modules that I have in a Sid VM for an install without mdraid or lvm are: minicmd, true, loadenv, extcmd, test, sh, normal,

Re: Update GRUB to GRUB2 / Lenny to Squeeze

On Sun, Jun 6, 2010 at 5:30 PM, lrhorer lrho...@satx.rr.com wrote: You can't load modules for grub-probe. But you can for grub-install. The default modules that I have in a Sid VM for an install without mdraid or lvm are: minicmd, true, loadenv, extcmd, test, sh, normal, charset, terminal,

Re: Update GRUB to GRUB2 / Lenny to Squeeze

/usr/sbin/grub-mkdevicemap /usr/sbin/grub-probe grub-pc /usr/sbin/grub-install /usr/sbin/grub-reboot /usr/sbin/grub-set-default /usr/sbin/grub-setup /usr/sbin/update-grub /usr/sbin/update-grub2 /usr/sbin/upgrade-from-grub-legacy But you can specify modules for grub-install with grub-install

Re: Update GRUB to GRUB2 / Lenny to Squeeze

You can't load modules for grub-probe. But you can for grub-install. The default modules that I have in a Sid VM for an install without mdraid or lvm are: minicmd, true, loadenv, extcmd, test, sh, normal, charset, terminal, crypto, boot, part_msdos, ext2, fshelp, biosdisk I have no idea

Re: Update GRUB to GRUB2 / Lenny to Squeeze

lrhorer wrote: I upgraded a box from Lenny to Squeeze, but the update of GRUB to GRUB2 failed. I've cobbled together a procedure which I think will work and which is (I hope) safe: 1. Comment out the entries for /dev/md1 in /etc/fstab and /etc/mdadm/mdadm.conf,

Re: Update GRUB to GRUB2 / Lenny to Squeeze

You can't load modules for grub-probe. But you can for grub-install. The default modules that I have in a Sid VM for an install without mdraid or lvm are: minicmd, true, loadenv, extcmd, test, sh, normal, charset, terminal, crypto, boot, part_msdos, ext2, fshelp, biosdisk I have no idea

Re: Update GRUB to GRUB2 / Lenny to Squeeze

Tom H wrote: On Sat, May 29, 2010 at 8:56 PM, lrhorer lrho...@satx.rr.com wrote: I upgraded a box from Lenny to Squeeze, but the update of GRUB to GRUB2 failed.  The box is running a pair of IDE hard drives with three partitions each.  Each partition on each drive is a RAID1 mirror of the

Re: Update GRUB to GRUB2 / Lenny to Squeeze

On Sat, May 29, 2010 at 8:56 PM, lrhorer lrho...@satx.rr.com wrote: I upgraded a box from Lenny to Squeeze, but the update of GRUB to GRUB2 failed.  The box is running a pair of IDE hard drives with three partitions each.  Each partition on each drive is a RAID1 mirror of the same partition

Update GRUB to GRUB2 / Lenny to Squeeze

I upgraded a box from Lenny to Squeeze, but the update of GRUB to GRUB2 failed. The box is running a pair of IDE hard drives with three partitions each. Each partition on each drive is a RAID1 mirror of the same partition on the other drive. The first partitions on both drives are

Re: grub2, update-grub, /etc/grub.d

On Sat, Sep 26, 2009 at 11:36:00AM -0400, Hugh Lawson wrote: grub2 (provided by package grub-pc) Suppose you want to add something like vga=791 to the linux line of one of the stanzas auto-configured by update-grub. What is the debian way to do this? Edit GRUB_CMDLINE_LINUX variable

grub2, update-grub, /etc/grub.d

grub2 (provided by package grub-pc) Suppose you want to add something like vga=791 to the linux line of one of the stanzas auto-configured by update-grub. What is the debian way to do this? I know how to edit the grub.cfg file to do this, but won't this file be replaced by the next 'update

Re: update-grub and chroot

Hi, thanks everyone for the reply, On Sat, 18 Oct 2008 10:17:23 +0200, Shams Fantar wrote: I'm wondering if it is possible to update the grub menu.lst in the chroot with update-grub to reflect its appropriate kernel to boot from. . . . You should update your menu.lst outside the chroot

Re: update-grub and chroot

Hi, On Sat, Oct 18, 2008 at 03:05:52AM +, T o n g wrote: Hi, I tried to update my grub menu.lst in the chroot system using update- grub, but it doesn't work. I'm wondering if it is possible to update the grub menu.lst in the chroot to reflect its appropriate kernel to boot from. I

Re: update-grub and chroot

T o n g wrote: Hi, I tried to update my grub menu.lst in the chroot system using update- grub, but it doesn't work. I'm wondering if it is possible to update the grub menu.lst in the chroot to reflect its appropriate kernel to boot from. thanks Show us your error message. What

update-grub and chroot

Hi, I tried to update my grub menu.lst in the chroot system using update- grub, but it doesn't work. I'm wondering if it is possible to update the grub menu.lst in the chroot to reflect its appropriate kernel to boot from. thanks -- Tong (remove underscore(s) to reply) http

Re: Warning before running update-grub (was: Filing bug reports in Debian)

Hal Vaughan wrote: Instead of just calling update-grub, a script could have said, This update will re-write /boot/grub/menu.lst. Press return to continue. That would have been enough (although giving a choice of continuing or not would have been nice, too). [...] I see the point

Re: Warning before running update-grub (was: Filing bug reports in Debian)

On Tuesday 14 October 2008, Eduardo M KALINOWSKI wrote: Hal Vaughan wrote: Instead of just calling update-grub, a script could have said, This update will re-write /boot/grub/menu.lst. Press return to continue. That would have been enough (although giving a choice of continuing

update-grub problem

I'm trying to install linux-image-2.6.18-6-686 using apt-get. I recently made the recommended change in /etc/kernel-img.conf to include: postinst_hook = usr/sbin/update-grub postrm_hook = usr/sbin/update-grub When I run the apt-get install, the configuration fails with the error about

Re: update-grub problem

On Wed May 14 2008 18:43:14 John Fleming wrote: I'm trying to install linux-image-2.6.18-6-686 using apt-get. I recently made the recommended change in /etc/kernel-img.conf to include: postinst_hook = usr/sbin/update-grub postrm_hook = usr/sbin/update-grub When I run the apt-get install

Re: update-grub problem

On Wed, May 14, 2008 at 09:43:14PM -0400, John Fleming wrote: I'm trying to install linux-image-2.6.18-6-686 using apt-get. I recently made the recommended change in /etc/kernel-img.conf to include: postinst_hook = usr/sbin/update-grub postrm_hook = usr/sbin/update-grub When I run

Re: update-grub problem

John Fleming wrote: I'm trying to install linux-image-2.6.18-6-686 using apt-get. I recently made the recommended change in /etc/kernel-img.conf to include: postinst_hook = usr/sbin/update-grub postrm_hook = usr/sbin/update-grub When I run the apt-get install, the configuration fails

Re: update-grub problem

What is the current working directory when this script gets run. You told it usr/sbin/update-grub not /usr/sbin/update-grub Note the difference. I still don't know why this is necessary. During the most recent kernel upgrade in Etch, I watched carefully for the usual warning message about

update-grub problem

I'm trying to install linux-image-2.6.18-6-686 using apt-get. I recently made the recommended change in /etc/kernel-img.conf to include: postinst_hook = usr/sbin/update-grub postrm_hook = usr/sbin/update-grub When I run the apt-get install, the configuration fails with the error about

Re: update-grub problem

However, that script DOES exist in the stated path. So what gives with this? That path (usr/sbin/update-grub) is relative to the current directory of the process using it. You probably want /usr/sbin/update-grub. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Re: update-grub help, menu.lst is not changing

single #initrd /boot/initrd.img-2.6.18-4-686 #savedefault ### END DEBIAN AUTOMAGIC KERNELS LIST And after typing update-grub, that whole line goes back to being UN-commented. How can i edit that permanently? I have tried adding this.. updatedefaultentry=false

  1   2   >