https://bugzilla.novell.com/show_bug.cgi?id=767272 https://bugzilla.novell.com/show_bug.cgi?id=767272#c6 --- Comment #6 from Agnelo de la Crotche <hippolyte@shaw.ca> 2012-07-06 00:43:47 UTC --- Hi. If you're asking me, you should pass the bug report upstream because it's not fixed and it affects all versions of os-prober on all distros (including the latest one I'm using). I didn't fill a bug report earlier because I couldn't describe clearly why and when it happens. I still don't know the reason but I was able to isolate the cause at least. The question is: why does os-prober believe that a file system is in an unstable state while everything else (meaning fsck and mount) says it is OK. I know that I'm missing something. But answering this question will probably lead to the solution.
Next time I get the issue, I will try to mount the file system read only.
Makes me think I have to remember to do that. The work around is to mount/umount the failing file sytem manually, then run os-prober again. That's what I do every time I notice that a boot entry for an OS is missing. But it requires user intervention, and os-prober is usually executed by another script. As far as I can tell, it has always worked. In any case, the foreign OS - the one os-prober is looking for - is the culprit. I don't think I have seen issues with Ubuntu 12.04 so far, but I have a lot of issues with Ubuntu 11.10 and several with Fedora and openSUSE (no matter which kernel - nothing to do with kernel 3.1.10-1.13, which is known not to always shut down properly.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.