I used grub-install --recheck and it totally removed my
/boot/grub/device.map. Then, I re-ran "sudo dpkg-reconfigure grub-pc"
and re-confirmed all 4 drives, which it installed grub on top as normal.
On reboot, grub was happy. \o/
I'll leave the bug status open for the "fix up automatically" part o
Remove hd4 to hd7 from device.map, rerun grub-install, and your problem
will go away. GRUB now consistently interprets an entry in device.map
as meaning that the device is BIOS-accessible, which it was laxer about
before. (This was needed to make DM-RAID work more sanely, IIRC.)
In your case, th
I've traditionally installed grub on all my drives, though only sda and
sdc are really bootable, as members of the /boot md device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690030
Title:
fails
** Attachment added: "sdd-debug.log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/690030/+attachment/1768181/+files/sdd-debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690030
Titl
** Attachment added: "sdc-debug.log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/690030/+attachment/1768180/+files/sdc-debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690030
Titl
** Attachment added: "sdb-debug.log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/690030/+attachment/1768179/+files/sdb-debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690030
Titl
** Attachment added: "sda-debug.log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/690030/+attachment/1768178/+files/sda-debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690030
Titl
Yes, /boot is /dev/md1. (But it has always been there.)
** Attachment added: "device.map"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/690030/+attachment/1768177/+files/device.map
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Also, a copy of /boot/grub/device.map would be useful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690030
Title:
fails to read disk partitions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Is /boot on /dev/md1? If so then that definitely matters - grub needs
to read its own modules from /boot/grub/ before it can get out of rescue
mode and into normal mode.
Can you show me the output of 'grub-install --debug '?
--
You received this bug notification because you are a member of Ubun
Disk layout is extremely standard:
$ grep sd /proc/partitions
80 244198584 sda
81 96358 sda1
823903795 sda2
83 240195847 sda3
8 16 488386584 sdb
8 17 488384001 sdb1
8 32 244198584 sdc
8 33 96358 sdc
I would use apport, but I can't open browsers correctly due to bug
690022. :P
** Tags added: apport-collected
** Description changed:
Binary package hint: grub2
- The latest grub suddenly cannot read my disk partitions and throws me
- into grub rescue. Re-installing grub from the 10.10 live
Doing things like "ls (hd0,1)" results in "no such partition", etc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690030
Title:
fails to read disk partitions
--
ubuntu-bugs mailing list
ubuntu-bug
** Attachment added: "grub.jpg"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/690030/+attachment/1765419/+files/grub.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690030
Title:
fails
14 matches
Mail list logo
