hi Colin,
as described into #3 above (previously mounted OS) can built a complete
grub menu, there is no problem on that side.
After watching bug 683355 bug 672177, i think you can consider this bug is
very close and the key-words here are uncleanly-unmounted filesystems too
because:
reboot
Thinking about uncleanly-unmounted issue, i wonder if we can say that a (few)
still running process lock the situation and make the shutdown unclean ?
If an unkilled process have to be blamed, how to know about it and force to
kill it to get a clean unmount ? (maybe something related to
*** This bug is a duplicate of bug 683355 ***
https://bugs.launchpad.net/bugs/683355
If mounting the partition helps, then this is bug 683355 so I'll mark
this as a duplicate. Thanks.
** This bug has been marked a duplicate of bug 683355
os-prober fails to find OSes on
Can you try mounting the filesystem in question, unmounting it straight
away, and then running os-prober? If this works around the problem (I'm
not suggesting it as a permanent solution), then this is the same as bug
683355.
--
You received this bug notification because you are a member of
New output with latest Jan 20th packages updates: some uuid packages and
grub rc1:
- previous grub menu complet (was built bt previouly mounted all the os
partitions
- apply the updates (uuids grub rc1) with only natty partition active, the
others are not mounted and still a minimal fstab
-
Sadly, each time installing packages that make grub menu rebuilt, the
previous good grub menu is lost if all the OS partitions are not
mounted. What is expected: os-prober might be able to scan and find all
the OS installed on all devices, mounted or not.
--
You received this bug notification
** Description changed:
Binary package hint: os-prober
natty i386 updated
- os-prober only find other os when these partitions are monted, otherwise
- its completly blind and dont add them to grub menu. This happen with a
- minimal fstab: active os partition + swap
+ os-prober only
