grub-mkconfig fails to recognize valid hard drive name

[Joe]

Binary package hint: grub2

When I execute sudo grub-mkconfig -o grub.cfg from /boot/grub, I get the following output:
Generating grub.cfg ...
Found Debian background: moreblue-orbit-grub.tga
Found linux image: /boot/vmlinuz-2.6.31-14-generic
Found initrd image: /boot/initrd.img-2.6.31-14-generic
Found linux image: /boot/vmlinuz-2.6.31-13-generic
Found initrd image: /boot/initrd.img-2.6.31-13-generic
Found linux image: /boot/vmlinuz-2.6.31-12-generic
Found initrd image: /boot/initrd.img-2.6.31-12-generic
Found linux image: /boot/vmlinuz-2.6.31-11-generic
Found initrd image: /boot/initrd.img-2.6.31-11-generic
Found linux image: /boot/vmlinuz-2.6.31-10-generic
Found initrd image: /boot/initrd.img-2.6.31-10-generic
Found memtest86+ image: /boot/memtest86+.bin
ls: cannot access /media/My: No such file or directory
Found Windows Vista (loader) on /dev/sda1
Found Windows Vista (loader) on /dev/sda3
done
The line "ls: cannot access /media/My: No such file or directory" caught my attention since in my system I have an attached external USB hard drive named "My Book" (no quotes). I currently do not have any operating system on this drive, but it is possible that someday I might have. If this were to occur, then grub-mkconfig would not correctly detect the hard drive as having an operating system on it. I traced this failure to grub-mkconfig calling "/usr/bin/os-prober" which in turn calls "/usr/lib/os-prober/newns os-prober". This error could prevent grub-mkconfig to not obtain a complete list of available operating systems on attached ghard drives. On my system, one can run /usr/bin/os-prober directly and obtain the following output:
/dev/sda1:Windows Vista (loader):Windows:chain
/dev/sda3:Windows Vista (loader):Windows1:chain
ls: cannot access /media/My: No such file or directory

1. lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10
2. apt-cache policy grub2
grub2:
  Installed: (none)
  Candidate: 1.97~beta4-1ubuntu1
  Version table:
     1.97~beta4-1ubuntu1 0
        500 http://us.archive.ubuntu.com karmic/universe Packages
3. When generating the grub2 grub,cfg file, it looks for available operating systems on all attached disks. Since my external USB hard drive has a "space" in it turn calls "/usr/lib/os-prober/newns os-prober". This error could prevent grub-mkconfig do not obtain a complete list of available operating systems on attached ghard drives. On my system, one can run /usr/bin/os-prober directly and obtain the following output:
/dev/sda1:Windows Vista (loader):Windows:chain
/dev/sda3:Windows Vista (loader):Windows1:chain
ls: cannot access /media/My: No such file or directory

1. lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10
2. apt-cache policy grub2
grub2:
  Installed: (none)
  Candidate: 1.97~beta4-1ubuntu1
  Version table:
     1.97~beta4-1ubuntu1 0
        500 http://us.archive.ubuntu.com karmic/universe Packages
3. When generating the grub2 grub,cfg file, it looks for available operating systems on all attached disks. Since my external USB hard drive has a "space" in its name "My Book", the detetion of an operating system fails for this drive, and consequently, all such drives that have a space in the name.

ProblemType: Bug
Architecture: amd64
Date: Fri Oct 16 13:57:35 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: grub2 (not installed)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
SourcePackage: grub2
Uname: Linux 2.6.31-14-generic x86_64

[caludo (b-l-e-y)]

See also https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/433910