On 2014-03-04 17:14, Andrey Borzenkov wrote:
В Tue, 04 Mar 2014 17:09:52 +0100 "Carlos E. R." <> пишет:
I can attach that, and also the yast logs while the update run.
Just run os-prober. It does not matter whether it is run as part of RPM or not.
And I can also attach messages log for the much older session, using an older kernel, not tainted, in case that is an issue.
It depends on what interests you, the kernel oops when xfs tries to mount it, of the issue of os-prober to try to mount those partitions.
There is already bug report for XFS (I cannot find it right now). I'm interested in os-prober behavior.
Fair enough. What I have currently are the entries on syslog, from when os-prober was automatically run. If you want the output on the terminal of running os-prober, I'll have to reboot to that partition (see signature: this post is sent from "Telcontar", which has grub 1. Posts sent from the test partition, with grub 2, read "Elessar"). As I have never used os-prober on the terminal, do you want any options on the command line, or none? About the XFE problem, yes, I found many reports on many distributions, searchin for on google for "Internal error xfs_sb_read_verify at line". For instance, at openSUSE: Bug 854646 - Running grub2-mkconfig -o /boot/grub2/grub.cfg crashes some fs kernel modules which has been closed as invalid. «It's from the kernel, but I wouldn't call it a "problem" other than it dropping a stack trace. That's the XFS core corruption handling and we actually want that.» (J.M). Then there is «Bug 849028 - grub2-probe create kernel segfault» and «Bug 849843 - initrd produces insane messages in dmesg», both in "new" state. «Bug 849028» is the same issue as the one on this thread, and I see one comment from you on it. Do you want a new report, or do I simply update that bugzilla with my info? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)