grub-probe confused by dmraid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
Critical
|
Phillip Susi | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
everything seems to install fine until the very end it says it cannot install bootloader on specified location. It also will not let me choose any of the other options and click ok.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubiquity 2.14.6
ProcVersionSign
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CasperVersion: 1.331
Date: Fri May 24 12:03:39 2013
InstallCmdLine: cdrom-detect/
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Colin Watson: Approve
- Ubuntu branches: Pending requested
-
Diff: 42 lines (+11/-2)3 files modifiedapidebian/changelog (+9/-0)
debian/patches/restore_mkdevicemap.patch (+1/-1)
util/deviceiter.c (+1/-1)
Nate Oglesby (xxxcode) wrote : | #1 |
- Casper.txt Edit (2.6 KiB, text/plain; charset="utf-8")
- Dependencies.txt Edit (7.7 KiB, text/plain; charset="utf-8")
- UbiquityDebug.txt Edit (740 bytes, text/plain; charset="utf-8")
- UbiquityDm.txt Edit (4.3 KiB, text/plain; charset="utf-8")
- UbiquityPartman.txt Edit (343.8 KiB, text/plain; charset="utf-8")
- UbiquitySyslog.txt Edit (224.8 KiB, text/plain; charset="utf-8")
Phillip Susi (psusi) wrote : | #2 |
Changed in grub-installer (Ubuntu): | |
status: | New → Incomplete |
Nate Oglesby (xxxcode) wrote : | #3 |
I get this
ubuntu@ubuntu:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/loop1: LABEL="casper-rw" UUID="a03c39d1-
/dev/sda: TYPE="isw_
/dev/sdb: TYPE="isw_
/dev/mapper/
/dev/mapper/
/dev/sdc1: LABEL="PENDRIVE" UUID="1018-275F" TYPE="vfat"
ubuntu@ubuntu:~$ sudo grub-probe -t partmap -vv /dev/mapper /isw_ccbefggcjh
Unknown extra argument `/isw_ccbefggcj
Usage: grub-probe [OPTION...] [OPTION]... [PATH|DEVICE]
Try `grub-probe --help' or `grub-probe --usage' for more information.
ubuntu@ubuntu:~$
I tried it with RAID_0 and what this one shows RAID-0p1
Phillip Susi (psusi) wrote : | #4 |
Woops, I left out the -d, that should have been:
sudo grub-probe -t partmap -vv -d /dev/mapper/
Nate Oglesby (xxxcode) wrote : Re: [Bug 1183915] Re: cannot install bootloader on specified location | #5 |
Now i get this
ubuntu@ubuntu:~$ sudo grub-probe -t partmap -vv -d
/dev/mapper/
grub-probe: info: cannot open `/boot/
directory.
grub-probe: info: /dev/mapper/
grub-probe: info: Looking for /dev/mapper/
grub-probe: info: /dev/mapper/
grub-probe: info: /dev/mapper/
grub-probe: info: /dev/mapper/
/dev/mapper/
grub-probe: info: /dev/mapper/
grub-probe: info: Looking for /dev/mapper/
grub-probe: info: /dev/mapper/
grub-probe: info: /dev/mapper/
grub-probe: info: /dev/mapper/
/dev/mapper/
grub-probe: info: /dev/mapper/
grub-probe: info: Looking for /dev/mapper/
grub-probe: info: /dev/mapper/
grub-probe: info: /dev/mapper/
grub-probe: info: /dev/mapper/
/dev/mapper/
grub-probe: info: opening hostdisk/
grub-core/
`hostdisk/
grub-probe: info: the size of hostdisk/
625154560.
grub-probe: info: no partition map found for
hostdisk/
grub-core/
`hostdisk/
On Fri, May 24, 2013 at 3:58 PM, Phillip Susi <email address hidden> wrote:
> Woops, I left out the -d, that should have been:
>
> sudo grub-probe -t partmap -vv -d /dev/mapper/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> cannot install bootloader on specified location
>
> Status in “grub-installer” package in Ubuntu:
> Incomplete
>
> Bug description:
> everything seems to install fine until the very end it says it cannot
> install bootloader on specified location. It also will not let me
> choose any of the other options and click ok.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.04
> Package: ubiquity 2.14.6
> ProcVersionSign
> Uname: Linux 3.8.0-19-generic x86_64
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> CasperVersion: 1.331
> Date: Fri May 24 12:03:39 2013
> InstallCmdLine: cdrom-detect/
> file=/cdrom/
> initrd=
> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
> MarkForUpload: True
> ProcEnviron:
> TERM=linux
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about ...
Phillip Susi (psusi) wrote : | #6 |
That doesn't look good. How about sudo grub-probe -t partmap -vv -d /dev/mapper/
summary: |
- cannot install bootloader on specified location + grub-probe confused by dmraid |
Phillip Susi (psusi) wrote : | #7 |
Also sudo dmsetup table isw_ccbefggcjh_
tags: | added: regression-release |
Phillip Susi (psusi) wrote : | #8 |
Ok, I see what's wrong now. grub-probe is looking for the UUID to start with "DMRAID-" to identify the device as a dmraid partition. Since 12.04, kpartx has been used to activate the partitions and it uses the form "partN-
Changed in grub-installer (Ubuntu): | |
importance: | Undecided → Critical |
status: | Incomplete → Triaged |
status: | Triaged → In Progress |
assignee: | nobody → Phillip Susi (psusi) |
affects: | grub-installer (Ubuntu) → grub2 (Ubuntu) |
Phillip Susi (psusi) wrote : | #9 |
Can you test the saucy daily cd and make sure that it also fails please? I should have a fix in a day or two to try again and if you can verify that fixes it, we'll get it applied to 12.04 as well.
Nate Oglesby (xxxcode) wrote : Re: [Bug 1183915] Re: grub-probe confused by dmraid | #10 |
it gave me a massive wall of text so if you have to scan through this whole
thing i thank you so much for doing this and am sorry.
grub-probe: info: Scanning for dmraid_nv devices on disk
hostdisk/
grub-core/
`/dev/mapper/
grub-probe: info: Scanning for ldm devices on disk
hostdisk/
grub-probe: info: scanning hostdisk/
LDM.
grub-core/
`/dev/mapper/
grub-probe: info: no LDM signature found.
grub-probe: info: Scanning for lvm devices on disk
hostdisk/
grub-probe: info: no LVM signature found.
grub-core/
0x80, len 0x23436400
grub-core/
hostdisk/
grub-probe: info: Scanning for DISKFILTER devices on disk
hostdisk/
grub-probe: info: Scanning for mdraid1x devices on disk
hostdisk/
grub-core/
`/dev/mapper/
grub-core/
`/dev/mapper/
grub-probe: info: Scanning for mdraid09 devices on disk
hostdisk/
grub-core/
`/dev/mapper/
grub-probe: info: Scanning for mdraid09_be devices on disk
hostdisk/
grub-probe: info: Scanning for dmraid_nv devices on disk
hostdisk/
grub-probe: info: Scanning for ldm devices on disk
hostdisk/
grub-probe: info: scanning hostdisk/
LDM.
grub-probe: info: no LDM signature found.
grub-probe: info: Scanning for lvm devices on disk
hostdisk/
grub-probe: info: no LVM signature found.
grub-core/
grub-core/
0x234364fe, len 0x1ffb502
grub-core/
len 0x0
grub-core/
len 0x0
grub-core/
`/dev/mapper/
grub-core/
0x23436500, len 0x1ffb500
grub-core/
hostdisk/
grub-probe: info: Scanning for DISKFILTER devices on disk
hostdisk/
grub-probe: info: Scanning for mdraid1x devices on disk
hostdisk/
grub-core/
`/dev/mapper/
grub-core/
`/dev/mapper/
grub-probe: info:...
Nate Oglesby (xxxcode) wrote : | #11 |
What is the saucy daily cd?
On Fri, May 24, 2013 at 7:24 PM, Phillip Susi <email address hidden> wrote:
> Can you test the saucy daily cd and make sure that it also fails please?
> I should have a fix in a day or two to try again and if you can verify
> that fixes it, we'll get it applied to 12.04 as well.
>
>
> ** Branch linked: lp:~psusi/ubuntu/saucy/grub2/fix-dmraid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> grub-probe confused by dmraid
>
> Status in “grub2” package in Ubuntu:
> In Progress
> Status in “grub2” source package in Precise:
> New
>
> Bug description:
> everything seems to install fine until the very end it says it cannot
> install bootloader on specified location. It also will not let me
> choose any of the other options and click ok.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.04
> Package: ubiquity 2.14.6
> ProcVersionSign
> Uname: Linux 3.8.0-19-generic x86_64
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> CasperVersion: 1.331
> Date: Fri May 24 12:03:39 2013
> InstallCmdLine: cdrom-detect/
> file=/cdrom/
> initrd=
> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
> MarkForUpload: True
> ProcEnviron:
> TERM=linux
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https:/
>
Nate Oglesby (xxxcode) wrote : | #12 |
ubuntu@ubuntu:~$ sudo dmsetup table isw_ccbefggcjh_
0 625154560 striped 2 64 8:0 0 8:16 0
On Sat, May 25, 2013 at 1:51 AM, Nate Oglesby <email address hidden> wrote:
> What is the saucy daily cd?
>
>
> On Fri, May 24, 2013 at 7:24 PM, Phillip Susi <email address hidden> wrote:
>
>> Can you test the saucy daily cd and make sure that it also fails please?
>> I should have a fix in a day or two to try again and if you can verify
>> that fixes it, we'll get it applied to 12.04 as well.
>>
>>
>> ** Branch linked: lp:~psusi/ubuntu/saucy/grub2/fix-dmraid
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https:/
>>
>> Title:
>> grub-probe confused by dmraid
>>
>> Status in “grub2” package in Ubuntu:
>> In Progress
>> Status in “grub2” source package in Precise:
>> New
>>
>> Bug description:
>> everything seems to install fine until the very end it says it cannot
>> install bootloader on specified location. It also will not let me
>> choose any of the other options and click ok.
>>
>> ProblemType: Bug
>> DistroRelease: Ubuntu 13.04
>> Package: ubiquity 2.14.6
>> ProcVersionSign
>> Uname: Linux 3.8.0-19-generic x86_64
>> ApportVersion: 2.9.2-0ubuntu8
>> Architecture: amd64
>> CasperVersion: 1.331
>> Date: Fri May 24 12:03:39 2013
>> InstallCmdLine: cdrom-detect/
>> file=/cdrom/
>> initrd=
>> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64
>> (20130424)
>> MarkForUpload: True
>> ProcEnviron:
>> TERM=linux
>> PATH=(custom, no user)
>> LANG=en_US.UTF-8
>> SourcePackage: grub-installer
>> UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>>
>> https:/
>>
>
>
Nate Oglesby (xxxcode) wrote : | #13 |
Ok I tried loading saucy salamander instead and it gives 'me the unable to
find a medium with a live file system' error. What does this mean?
On Sat, May 25, 2013 at 10:19 AM, Nate Oglesby <email address hidden> wrote:
> ubuntu@ubuntu:~$ sudo dmsetup table isw_ccbefggcjh_
> 0 625154560 striped 2 64 8:0 0 8:16 0
>
>
>
> On Sat, May 25, 2013 at 1:51 AM, Nate Oglesby <email address hidden> wrote:
>
>> What is the saucy daily cd?
>>
>>
>> On Fri, May 24, 2013 at 7:24 PM, Phillip Susi <email address hidden> wrote:
>>
>>> Can you test the saucy daily cd and make sure that it also fails please?
>>> I should have a fix in a day or two to try again and if you can verify
>>> that fixes it, we'll get it applied to 12.04 as well.
>>>
>>>
>>> ** Branch linked: lp:~psusi/ubuntu/saucy/grub2/fix-dmraid
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https:/
>>>
>>> Title:
>>> grub-probe confused by dmraid
>>>
>>> Status in “grub2” package in Ubuntu:
>>> In Progress
>>> Status in “grub2” source package in Precise:
>>> New
>>>
>>> Bug description:
>>> everything seems to install fine until the very end it says it cannot
>>> install bootloader on specified location. It also will not let me
>>> choose any of the other options and click ok.
>>>
>>> ProblemType: Bug
>>> DistroRelease: Ubuntu 13.04
>>> Package: ubiquity 2.14.6
>>> ProcVersionSign
>>> Uname: Linux 3.8.0-19-generic x86_64
>>> ApportVersion: 2.9.2-0ubuntu8
>>> Architecture: amd64
>>> CasperVersion: 1.331
>>> Date: Fri May 24 12:03:39 2013
>>> InstallCmdLine: cdrom-detect/
>>> file=/cdrom/
>>> initrd=
>>> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64
>>> (20130424)
>>> MarkForUpload: True
>>> ProcEnviron:
>>> TERM=linux
>>> PATH=(custom, no user)
>>> LANG=en_US.UTF-8
>>> SourcePackage: grub-installer
>>> UpgradeStatus: No upgrade log present (probably fresh install)
>>>
>>> To manage notifications about this bug go to:
>>>
>>> https:/
>>>
>>
>>
>
Phillip Susi (psusi) wrote : | #14 |
Hrm... it means something unrelated to this went wrong, which makes testing this harder. I was hoping you would get the same error you got originally just to establish a baseline so that when I get a fix into saucy, and it worked, that would prove the fix was correct.
Nate Oglesby (xxxcode) wrote : | #15 |
well dang... well what would be the best course of action? I wouldn't mind
continuing to try and get saucy to work if that would be best.
On Sat, May 25, 2013 at 8:42 PM, Phillip Susi <email address hidden> wrote:
> Hrm... it means something unrelated to this went wrong, which makes
> testing this harder. I was hoping you would get the same error you got
> originally just to establish a baseline so that when I get a fix into
> saucy, and it worked, that would prove the fix was correct.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> grub-probe confused by dmraid
>
> Status in “grub2” package in Ubuntu:
> In Progress
> Status in “grub2” source package in Precise:
> New
>
> Bug description:
> everything seems to install fine until the very end it says it cannot
> install bootloader on specified location. It also will not let me
> choose any of the other options and click ok.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.04
> Package: ubiquity 2.14.6
> ProcVersionSign
> Uname: Linux 3.8.0-19-generic x86_64
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> CasperVersion: 1.331
> Date: Fri May 24 12:03:39 2013
> InstallCmdLine: cdrom-detect/
> file=/cdrom/
> initrd=
> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
> MarkForUpload: True
> ProcEnviron:
> TERM=linux
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https:/
>
Nate Oglesby (xxxcode) wrote : | #16 |
ok I think I found the problem. I just tried self testing my hard disks and
the secondary hard disk test froze midway so i'm thinking my secondary
harddrive is bad going to have to figure out what to do about that...
On Sat, May 25, 2013 at 8:57 PM, Nate Oglesby <email address hidden> wrote:
> well dang... well what would be the best course of action? I wouldn't mind
> continuing to try and get saucy to work if that would be best.
>
>
> On Sat, May 25, 2013 at 8:42 PM, Phillip Susi <email address hidden> wrote:
>
>> Hrm... it means something unrelated to this went wrong, which makes
>> testing this harder. I was hoping you would get the same error you got
>> originally just to establish a baseline so that when I get a fix into
>> saucy, and it worked, that would prove the fix was correct.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https:/
>>
>> Title:
>> grub-probe confused by dmraid
>>
>> Status in “grub2” package in Ubuntu:
>> In Progress
>> Status in “grub2” source package in Precise:
>> New
>>
>> Bug description:
>> everything seems to install fine until the very end it says it cannot
>> install bootloader on specified location. It also will not let me
>> choose any of the other options and click ok.
>>
>> ProblemType: Bug
>> DistroRelease: Ubuntu 13.04
>> Package: ubiquity 2.14.6
>> ProcVersionSign
>> Uname: Linux 3.8.0-19-generic x86_64
>> ApportVersion: 2.9.2-0ubuntu8
>> Architecture: amd64
>> CasperVersion: 1.331
>> Date: Fri May 24 12:03:39 2013
>> InstallCmdLine: cdrom-detect/
>> file=/cdrom/
>> initrd=
>> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64
>> (20130424)
>> MarkForUpload: True
>> ProcEnviron:
>> TERM=linux
>> PATH=(custom, no user)
>> LANG=en_US.UTF-8
>> SourcePackage: grub-installer
>> UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>>
>> https:/
>>
>
>
Nate Oglesby (xxxcode) wrote : | #17 |
is there any way I can ignore the secondary harddrive when booting?
On Sat, May 25, 2013 at 10:37 PM, Nate Oglesby <email address hidden> wrote:
> ok I think I found the problem. I just tried self testing my hard disks
> and the secondary hard disk test froze midway so i'm thinking my secondary
> harddrive is bad going to have to figure out what to do about that...
>
>
> On Sat, May 25, 2013 at 8:57 PM, Nate Oglesby <email address hidden> wrote:
>
>> well dang... well what would be the best course of action? I wouldn't
>> mind continuing to try and get saucy to work if that would be best.
>>
>>
>> On Sat, May 25, 2013 at 8:42 PM, Phillip Susi <email address hidden> wrote:
>>
>>> Hrm... it means something unrelated to this went wrong, which makes
>>> testing this harder. I was hoping you would get the same error you got
>>> originally just to establish a baseline so that when I get a fix into
>>> saucy, and it worked, that would prove the fix was correct.
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https:/
>>>
>>> Title:
>>> grub-probe confused by dmraid
>>>
>>> Status in “grub2” package in Ubuntu:
>>> In Progress
>>> Status in “grub2” source package in Precise:
>>> New
>>>
>>> Bug description:
>>> everything seems to install fine until the very end it says it cannot
>>> install bootloader on specified location. It also will not let me
>>> choose any of the other options and click ok.
>>>
>>> ProblemType: Bug
>>> DistroRelease: Ubuntu 13.04
>>> Package: ubiquity 2.14.6
>>> ProcVersionSign
>>> Uname: Linux 3.8.0-19-generic x86_64
>>> ApportVersion: 2.9.2-0ubuntu8
>>> Architecture: amd64
>>> CasperVersion: 1.331
>>> Date: Fri May 24 12:03:39 2013
>>> InstallCmdLine: cdrom-detect/
>>> file=/cdrom/
>>> initrd=
>>> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64
>>> (20130424)
>>> MarkForUpload: True
>>> ProcEnviron:
>>> TERM=linux
>>> PATH=(custom, no user)
>>> LANG=en_US.UTF-8
>>> SourcePackage: grub-installer
>>> UpgradeStatus: No upgrade log present (probably fresh install)
>>>
>>> To manage notifications about this bug go to:
>>>
>>> https:/
>>>
>>
>>
>
Phillip Susi (psusi) wrote : | #18 |
Ok, I have a fix to test in my PPA. Please boot 13.04, but rather than try to install, just run the following:
sudo -s
apt-add-repository ppa:psusi/ppa
apt-get update
apt-get upgrade grub2
grub-probe -t partmap -d /dev/mapper/
It looks like the build queue is rather long right now so it may be several hours before it's ready. I'll let you know when it's done.
Nate Oglesby (xxxcode) wrote : | #19 |
After 3 flash drives, 6 version of ubuntu, taking my computer completely
apart, removing the bad harddrive and repartitioning and mounting the other
I finally successfully installed precise 12.10. Thank you so much for your
help and guidance you were a huge support. I hope they pay you well =)
Nate
On Tue, May 28, 2013 at 9:24 AM, Phillip Susi <email address hidden> wrote:
> Ok, I have a fix to test in my PPA. Please boot 13.04, but rather than
> try to install, just run the following:
>
> sudo -s
> apt-add-repository ppa:psusi/ppa
> apt-get update
> apt-get upgrade grub2
> grub-probe -t partmap -d /dev/mapper/
>
> It looks like the build queue is rather long right now so it may be
> several hours before it's ready. I'll let you know when it's done.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> grub-probe confused by dmraid
>
> Status in “grub2” package in Ubuntu:
> In Progress
> Status in “grub2” source package in Precise:
> New
>
> Bug description:
> everything seems to install fine until the very end it says it cannot
> install bootloader on specified location. It also will not let me
> choose any of the other options and click ok.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.04
> Package: ubiquity 2.14.6
> ProcVersionSign
> Uname: Linux 3.8.0-19-generic x86_64
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> CasperVersion: 1.331
> Date: Fri May 24 12:03:39 2013
> InstallCmdLine: cdrom-detect/
> file=/cdrom/
> initrd=
> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
> MarkForUpload: True
> ProcEnviron:
> TERM=linux
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https:/
>
Phillip Susi (psusi) wrote : | #20 |
Heh, I'm actually just a volunteer. Sorry it took so long to get this fix built; there was a problem with the PPA builders. Anyhow, could you test the build in my ppa and let me know if it works?
Launchpad Janitor (janitor) wrote : | #21 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in grub2 (Ubuntu Precise): | |
status: | New → Confirmed |
Changed in grub2 (Ubuntu): | |
status: | In Progress → Fix Committed |
Launchpad Janitor (janitor) wrote : | #22 |
This bug was fixed in the package grub2 - 2.00-19ubuntu1
---------------
grub2 (2.00-19ubuntu1) saucy; urgency=low
* Resynchronise with Debian. Remaining changes:
- Default to hiding the menu; holding down Shift at boot will show it.
- Add crashkernel option.
- Bypass menu unless other OSes are installed or Shift is pressed.
- Show the boot menu if the previous boot failed.
- Check hardware support before using gfxpayload=keep.
- Set vt.handoff=7 for smooth handoff to kernel graphical mode.
- In recovery mode, add nomodeset to the Linux kernel arguments, and
remove the 'set gfxpayload=keep' command.
- Handle probing striped DM-RAID devices.
grub2 (2.00-19) unstable; urgency=low
[ Colin Watson ]
* Merge from Ubuntu:
- debian/
derived from the EFI Loaded Image Protocol to compute the prefix
(LP: #1097570).
- debian/
prebuilt EFI images (thanks, Steve Langasek).
* Backport from upstream:
- Handle partitions on non-512B EFI disks (LP: #1065281).
[ Phillip Susi ]
* restore_
anywhere instead of only at the start, since kpartx prefixes it with
"partN-" (LP: #1183915).
-- Colin Watson <email address hidden> Wed, 18 Sep 2013 21:20:28 +0100
Changed in grub2 (Ubuntu): | |
status: | Fix Committed → Fix Released |
Steve Langasek (vorlon) wrote : | #23 |
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release
Changed in grub2 (Ubuntu Precise): | |
status: | Confirmed → Won't Fix |
You appear to be trying to install on a fakeraid. You have to install grub to the raid device ( /dev/mapper/ isw_ccbefggcjh_ RAID-0 ) not one of the individual disks ( /dev/sda ). Also please run sudo blkid, and sudo grub-probe -t partmap -vv /dev/mapper/ isw_ccbefggcjh_ RAID-0 and post the output.