I hope I'm not out of line posting this here... but here's some more information on this:
Hopefully it will help those who are still having similar issues... Here are some similar issues (or some may be duplicates?) : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550682 http://www.mail-archive.com/debian-bugs-d...@lists.debian.org/msg700122.html http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550704 http://news.gmane.org/find-root.php?message_id=%3c20090908095706.GB31532%40plukwa.net%3e http://article.gmane.org/gmane.linux.debian.devel.bugs.general/611442 The one particular explanation that seems to fit my case the best is one that occurred about a year ago in the grub mailing lists, where the bug was related to grub-probe (or lvm ?) mistaking an element of a RAID device as being an LVM physical volume. In my case one of my physical volumes on my LVM is a 30GB mdadm raid0 device. Of course this was considered resolved a year ago. here's a link to that conversation: http://www.mail-archive.com/grub-de...@gnu.org/msg06056.html Again, something like that makes the most sense in my situation. I am having trouble getting the lvm moved off the mdadm raid0 device, so I can't yet test to see if that fixes it. I'm guessing I have a bit of data corruption on /dev/md0 (I get a no volume label for md0 error on "fdisk -l" . I'm doing some thorough scans on my VolGroup now. If I resolve it I'll try and report back here. ** Bug watch added: Debian Bug tracker #550682 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550682 ** Bug watch added: Debian Bug tracker #550704 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550704 -- grub-setup crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/386802 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
