Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
On Sep 15, 2012, at 8:36 PM, Ben Hutchings wrote: On Thu, 2012-09-13 at 14:58 -0700, Rick Thomas wrote: [...] 1) It seems likely that adding a udeb for fuse-modules will allow os- prober to identify other Linux OS root partitions and get them added to the boot-loader config file... But only as long as those partitions are not LVM partitions. I have not performed definitive experiments to verify either half of this assertion, but the evidence so far does point in that direction. When can I expect the udeb for fuse fix to be included in an upcoming daily iso? I'll be happy to test it when it's available. [...] Will be included in the next linux upload to unstable, hopefully this weekend. I don't know how long that will take to get into a daily installer. Thanks, Ben! I'll be on the lookout for it. Please let me know if you see it appear before I do. Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
On Thu, 2012-09-13 at 14:58 -0700, Rick Thomas wrote: [...] 1) It seems likely that adding a udeb for fuse-modules will allow os- prober to identify other Linux OS root partitions and get them added to the boot-loader config file... But only as long as those partitions are not LVM partitions. I have not performed definitive experiments to verify either half of this assertion, but the evidence so far does point in that direction. When can I expect the udeb for fuse fix to be included in an upcoming daily iso? I'll be happy to test it when it's available. [...] Will be included in the next linux upload to unstable, hopefully this weekend. I don't know how long that will take to get into a daily installer. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Bug#684265: Debian Installer 7.0 Beta2 release bug #684265 -- partial success
On 09/13/12 01:15, Rick Thomas wrote: On 09/12/12 23:22, Rick Thomas wrote: On Sep 12, 2012, at 10:41 PM, Christian PERRIER wrote: Quoting Rick Thomas (rbtho...@pobox.com): On Sep 12, 2012, at 4:21 PM, Rick Thomas wrote: I have not tried running os-prober from the alt-F2 console during the install, to see if it gives different results. I'll do that and report back. Any hints of things I should be looking out for? Here's the stderr/stdout output when os-prober is run in the installer environment: umount: can't umount /var/lib/os-prober/mount: Invalid argument grub-probe: error: no such disk. grub-probe: error: no such disk. grub-probe: error: no such disk. Could be something like #686314. Can you try (in the installer) to do the workaround found there (loading the fuse module)? I'll try the workaround and report back. Sadly, that didn't solve the problem. On the amd64 (with LVM) the fuse workaround wasn't enough... *But*... when I tried it on the PowerPC (Mac G4) machine, where all the relevant partitions are real partitions, no LVM stuff involved, the workaround (insmod ... fuse.ko) *did* fix the problem. I wonder if there's another module that's missing on the LVM machine? Hope this helps! Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
On 09/13/2012 01:41 AM, Christian PERRIER wrote: Quoting Rick Thomas (rbtho...@pobox.com): On Sep 12, 2012, at 4:21 PM, Rick Thomas wrote: I have not tried running os-prober from the alt-F2 console during the install, to see if it gives different results. I'll do that and report back. Any hints of things I should be looking out for? Here's the stderr/stdout output when os-prober is run in the installer environment: umount: can't umount /var/lib/os-prober/mount: Invalid argument grub-probe: error: no such disk. grub-probe: error: no such disk. grub-probe: error: no such disk. Could be something like #686314. Can you try (in the installer) to do the workaround found there (loading the fuse module)? Definitely, os-prober needs fuse module to work properly. D-i is trying to load the fuse module but it is not available in the d-i environment. Here is d-i log extract: Sep 11 02:15:31 anna-install: Installing ufs-modules Sep 11 02:15:31 anna-install: Installing btrfs-modules Sep 11 02:15:31 anna-install: Installing fuse-modules Sep 11 02:15:31 os-prober: unknown udeb fuse-modules When I load the fuse module manually os-prober works fine. Therefore solution for bug reports 684265, 686314, 686631, 687286 is to create fuse-modules udeb package. Patch is available here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684265#35 Other problems related to listing other OS's in grub menu, that may or may not be related to os-prober, are described in bug reports 587397, 603107, 608025, 608219, 609251. If you see similar problems related to LVM please file a separate bug report. Milan signature.asc Description: OpenPGP digital signature
Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
On Sep 13, 2012, at 5:49 AM, Milan Kupcevic wrote: When I load the fuse module manually os-prober works fine. Therefore solution for bug reports 684265, 686314, 686631, 687286 is to create fuse-modules udeb package. Patch is available here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684265#35 Other problems related to listing other OS's in grub menu, that may or may not be related to os-prober, are described in bug reports 587397, 603107, 608025, 608219, 609251. If you see similar problems related to LVM please file a separate bug report. Milan We seem to have solved about a third of the problems uncovered in investigating this bug: 1) It seems likely that adding a udeb for fuse-modules will allow os- prober to identify other Linux OS root partitions and get them added to the boot-loader config file... But only as long as those partitions are not LVM partitions. I have not performed definitive experiments to verify either half of this assertion, but the evidence so far does point in that direction. When can I expect the udeb for fuse fix to be included in an upcoming daily iso? I'll be happy to test it when it's available. 2) We have not yet identified the ingredient that makes the boot- loader installer unable to handle Linux OS root on LVM partitions correctly. I'm willing to pursue the issue thru to its conclusion, if someone who knows the installer internals better will guide me. 3) It would be nice if all boot-loader installers were as vigilant as the current grub installer. The grub installer warns the user if it finds only one OS partition (the one it's installing for) and asks if she wants to go ahead with a process that may have to be re-done after the install completes, due to having missed other OS roots. From my own personal perspective, the one particular boot-loader installer I would like this extra vigilant feature for is the powerpc yaboot installer. I would file a wishlist bugreport on this issue if I only knew which package to file it against. Can anyone suggest a good candidate? Thanks! Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
On Sep 12, 2012, at 10:41 PM, Christian PERRIER wrote: Quoting Rick Thomas (rbtho...@pobox.com): On Sep 12, 2012, at 4:21 PM, Rick Thomas wrote: I have not tried running os-prober from the alt-F2 console during the install, to see if it gives different results. I'll do that and report back. Any hints of things I should be looking out for? Here's the stderr/stdout output when os-prober is run in the installer environment: umount: can't umount /var/lib/os-prober/mount: Invalid argument grub-probe: error: no such disk. grub-probe: error: no such disk. grub-probe: error: no such disk. Could be something like #686314. Can you try (in the installer) to do the workaround found there (loading the fuse module)? It certainly does sound like it! I'll try the workaround and report back. Thanks for caring! Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
On 09/12/12 23:22, Rick Thomas wrote: On Sep 12, 2012, at 10:41 PM, Christian PERRIER wrote: Quoting Rick Thomas (rbtho...@pobox.com): On Sep 12, 2012, at 4:21 PM, Rick Thomas wrote: I have not tried running os-prober from the alt-F2 console during the install, to see if it gives different results. I'll do that and report back. Any hints of things I should be looking out for? Here's the stderr/stdout output when os-prober is run in the installer environment: umount: can't umount /var/lib/os-prober/mount: Invalid argument grub-probe: error: no such disk. grub-probe: error: no such disk. grub-probe: error: no such disk. Could be something like #686314. Can you try (in the installer) to do the workaround found there (loading the fuse module)? I'll try the workaround and report back. Sadly, that didn't solve the problem. The umount: can't umount... error message went away, but the three 'no such disk' messages remained. And grub install still objected because there was only one OS... I've attached the relevant section of /var/log/installer/syslog Hope it helps... Thanks! Rick Sep 13 07:15:48 anna-install: Installing os-prober-udeb Sep 13 07:15:48 os-prober: File descriptor 3 (pipe:[1755]) leaked on lvs invocation. Parent PID 15811: log-output Sep 13 07:15:48 os-prober: File descriptor 4 (/dev/pts/0) leaked on lvs invocation. Parent PID 15811: log-output Sep 13 07:15:48 os-prober: File descriptor 5 (/dev/pts/0) leaked on lvs invocation. Parent PID 15811: log-output Sep 13 07:15:48 os-prober: File descriptor 6 (/dev/pts/0) leaked on lvs invocation. Parent PID 15811: log-output Sep 13 07:15:48 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda1 Sep 13 07:15:48 50mounted-tests: debug: mounted using GRUB ext2 filesystem driver Sep 13 07:15:48 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/10freedos Sep 13 07:15:48 10freedos: debug: /dev/sda1 is not a FAT partition: exiting Sep 13 07:15:48 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/10qnx Sep 13 07:15:48 10qnx: debug: /dev/sda1 is not a QNX4 partition: exiting Sep 13 07:15:48 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/20macosx Sep 13 07:15:48 macosx-prober: debug: /dev/sda1 is not an HFS+ partition: exiting Sep 13 07:15:48 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/20microsoft Sep 13 07:15:48 20microsoft: debug: /dev/sda1 is not a MS partition: exiting Sep 13 07:15:48 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/30utility Sep 13 07:15:48 30utility: debug: /dev/sda1 is not a FAT partition: exiting Sep 13 07:15:48 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/40lsb Sep 13 07:15:48 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/70hurd Sep 13 07:15:48 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/80minix Sep 13 07:15:48 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/83haiku Sep 13 07:15:48 83haiku: debug: /dev/sda1 is not a BeFS partition: exiting Sep 13 07:15:48 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro Sep 13 07:15:48 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90solaris Sep 13 07:15:48 finish-install: rmdir: '/var/lib/os-prober/mount': Device or resource busy Sep 13 07:15:48 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda2 Sep 13 07:15:48 50mounted-tests: debug: /dev/sda2 type not recognised; skipping Sep 13 07:15:48 os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests Sep 13 07:15:48 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda5 Sep 13 07:15:48 finish-install: rmdir: '/var/lib/os-prober/mount': Device or resource busy Sep 13 07:15:48 os-prober: debug: /dev/sdb1: part of software raid array Sep 13 07:15:48 os-prober: debug: /dev/sdc1: part of software raid array Sep 13 07:15:48 os-prober: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/sdd1 Sep 13 07:15:48 10freedos: debug: /dev/sdd1 is not a FAT partition: exiting Sep 13 07:15:48 os-prober: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/sdd1 Sep 13 07:15:48 10qnx: debug: /dev/sdd1 is not a QNX4 partition: exiting Sep 13 07:15:48 os-prober: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/sdd1 Sep 13 07:15:48 macosx-prober: debug: /dev/sdd1 is not an HFS+ partition: exiting Sep 13 07:15:48 os-prober: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/sdd1 Sep 13 07:15:48 20microsoft: debug: /dev/sdd1 is not a MS partition: exiting Sep 13 07:15:48 os-prober: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/sdd1 Sep 13 07:15:48 30utility: debug: /dev/sdd1 is not a FAT partition: exiting Sep 13 07:15:48 os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/sdd1 Sep 13 07:15:48 os-prober: debug: running
Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
On 09/13/12 01:15, Rick Thomas wrote: The umount: can't umount... error message went away, but the three 'no such disk' messages remained. And grub install still objected because there was only one OS... I've attached the relevant section of /var/log/installer/syslog It may be worth noting these error messages in syslog: Sep 13 07:15:49 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/mapper/monk-root Sep 13 07:15:49 finish-install: grub-probe: error: no such disk. Sep 13 07:15:49 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/mapper/monk-root2 Sep 13 07:15:50 finish-install: grub-probe: error: no such disk. It seems to be claiming that /dev/mapper/monk-root and /dev/mapper/monk-root2 don't exist. Those are the two partitions that have the other Linux installed in them -- the two I would have expected os-prober to find. Interestingly, it finds /dev/mapper/monk-home just fine. One difference between the two root partitions and the home partition is that I told the partitioner to mount the home partition on /home, but I never mentioned the two root partitions at all in the partitioner. I wonder if I gave them mount points and told the partitioner to mount them, would os-prober be able to find them? Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
On Sep 10, 2012, at 10:16 PM, Christian PERRIER wrote: Quoting Rick Thomas (rbtho...@pobox.com): I'll be happy to provide installation log files to anyone who wants them. I'd also be happy to look at the relevant code and see if I can figure out what's wrong, but I don't know where to look. I don't have any experience with the insides of the installer. If somebody is willing to mentor me a little I might be able to help. It's likely to be in os-prober. When I run os-prober on the installed system, I get exactly what I expect: /dev/mapper/monk-root:Debian GNU/Linux (6.0.5):Debian:linux /dev/mapper/monk-root2:Debian GNU/Linux (wheezy/sid):Debian1:linux There are three root partitions monk-root, monk-root2, and monk- root3. The last is the active root at the time os-prober was run, so I don't expect it to show. It does find the other two, though. The PowerPC system that shows the bug is not using LVM. On that machine the extra Linux root partitions are real physical partitions. On that machine I also get the expected results from running os-prober in the installed system. So if the problem is in os-prober, it's not in the part of os-prober that gets used in the installed system, it must be in the parts that are unique to the installation system. I have not tried running os-prober from the alt-F2 console during the install, to see if it gives different results. I'll do that and report back. Any hints of things I should be looking out for? Thanks! Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
On Sep 12, 2012, at 4:21 PM, Rick Thomas wrote: I have not tried running os-prober from the alt-F2 console during the install, to see if it gives different results. I'll do that and report back. Any hints of things I should be looking out for? Here's the stderr/stdout output when os-prober is run in the installer environment: umount: can't umount /var/lib/os-prober/mount: Invalid argument grub-probe: error: no such disk. grub-probe: error: no such disk. grub-probe: error: no such disk. I've attached the installer syslog part from when I ran os-prober manually. Hope this helps! Rick os-prober-syslog.out Description: Binary data
Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
Quoting Rick Thomas (rbtho...@pobox.com): On Sep 12, 2012, at 4:21 PM, Rick Thomas wrote: I have not tried running os-prober from the alt-F2 console during the install, to see if it gives different results. I'll do that and report back. Any hints of things I should be looking out for? Here's the stderr/stdout output when os-prober is run in the installer environment: umount: can't umount /var/lib/os-prober/mount: Invalid argument grub-probe: error: no such disk. grub-probe: error: no such disk. grub-probe: error: no such disk. Could be something like #686314. Can you try (in the installer) to do the workaround found there (loading the fuse module)? signature.asc Description: Digital signature
