closing as obsolete
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/386802
Title:
grub-setup crashed with SIGSEGV in __libc_start_ma
does this still affect xenial or later?
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Rolf Leggewie (r0lf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
crash in ubuntu raring as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/386802
Title:
grub-setup crashed with SIGSEGV in __libc_start_main()
To manage notifications about this bug go to:
https
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 21 08:53:05 2013
DistroRelease: Ubuntu 12.10
ExecutablePath: /usr/bin/grub-mount
ExecutableTimestamp: 1350236232
ProcCmdline: grub-mount /dev/sde5 /var/lib/os-prober/mount
ProcCwd: /
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=xterm
error is still there: grub-mount crashed with SIGSEGV in
__libc_start_main()
apt-cache policy grub-common
grub-common:
Installed: 2.00-7ubuntu11
Candidate: 2.00-7ubuntu11
Version table:
*** 2.00-7ubuntu11 0
500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
1
** Attachment added: "crash report"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/386802/+attachment/3539826/+files/_usr_bin_grub-mount.0.crash.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/386802
Title:
grub-setup crashed with SIGSEGV in __libc_start_main()
To manage notificati
It is still the same problem on my Karmic with full updates.
I still need to manually remember to run grub-mkdevicemap before update-
grub or it will just fail. It might be due the fact that I switch and
swap disks quite a few times. Still shouldn't render the system
unbootable on kernel upgrades,
Mine ended up being the RAID-0 mdadm device that was a physical volume in my
LVM2 Volume Group.
again see
When I got everything migrated off of it, the Ubuntu Karmic Alternate CD (Beta)
installed grub2 with no segfaults.
I'm guessing the problem was how grub-probe detected the /dev/md0 segment
The post from Kamilion solved my problem also. +1
This was the diff 'sudo grub-mkdevicemap' explicitely:
s...@karmic:~$ sdiff /home/sehe/oldboot/boot/grub/device.map
/boot/grub/device.map
(hd0) /dev/sda(hd0) /dev/sda
(hd1) /dev/sdb
** Bug watch removed: 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 subscri
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-archiv
That definitely isn't solving mine.
The only thing that has worked for me is to boot into an older OS (or chroot
into it) where I had an older version of grub2 (grub-pc) installed.
That version recognizes my mdadm raid devices and lvm2 devices just fine, and
will actually work.
The only way I c
The post from Kamilion solved my problem also.
--
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@list
Discovered my problem while searching launchpad for similar bugs.
Found some information here:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/190147
Somehow the devicemap was incorrectly generated.
running 'sudo grub-mkdevicemap' and then 'sudo update-grub' fixed my
problems.
Here's a pro
See #423347 for similar segfaulting.
Supermicro X8-series motherboard, 2xE5520, 16GB ram, 2X WD Black with
mpt2sas JBOD LVM.
--
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
removed privacy
** Visibility changed to: Public
--
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@l
17 matches
Mail list logo
