From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: linux-raid@vger.kernel.org
Subject: Re: Putting grub back on new mirror disk
Date: Thu, 14 Mar 2013 00:13:49 -0700 [thread overview]
Message-ID: <514178AD.5050305@vorgon.com> (raw)
In-Reply-To: <CAD4F9C5-6A55-421A-BFAD-B23D72662054@colorremedies.com>
When I last checked the grub version was when I got the help in the
#grub channel on freenode irc: (GNU GRUB 1.98~20100115-1)
I may have done an apt-get update/upgrade since, but it would have been
a long time ago. I didn't ask on irc this time because a busy day and
couldn't wait for response. I already am on this list which is why I
checked here. I want to do a full upgrade, and build a new kernel when I
get some time. But wanted to get it back to where it was before the
drive dies first. I'll take a closer look at the replies here tommrow
when I get a chance.
Still trying to figure out why I also lost audio on DVI output for vdr.
I sent the computer to a shop this time thinking they would be able to
take care of things. They replaced a sata cable and the power supply
(said it was dieing which is possible) and reset the cmos :( but missed
the fact that the drive was bad or 3 arrays where down.
On 3/13/2013 8:34 PM, Chris Murphy wrote:
>
> On Mar 13, 2013, at 8:29 PM, Timothy D. Lenz <tlenz@vorgon.com> wrote:
>>
>> x64VDR:/home/vorg# grub-install /dev/sda && grub-install /dev/sdb
>
> What happens when you issue the commands separately?
>
>> /usr/sbin/grub-probe: error: no such disk.
>> Auto-detection of a filesystem of /dev/md0 failed.
>> Please report this together with the output of "/usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub" to <bug-grub@gnu.org>
>
> I'm going to guess an old version of prerelease GRUB2 since device.map isn't used anymore. Dollars to donuts help-grub@ will ask you to upgrade to current upstream GRUB2.
>
> grub-install --version
>
> If installing to sda or sdb fail separately, use --debug flag and put that up on pastebin. Many, many changes are in the final release of 2.00, which is now about 9 months old.
>
>
> Chris Murphy
>
>
>
next prev parent reply other threads:[~2013-03-14 7:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 2:29 Putting grub back on new mirror disk Timothy D. Lenz
[not found] ` <CAD4F9C5-6A55-421A-BFAD-B23D72662054@colorremedies.com>
2013-03-14 7:13 ` Timothy D. Lenz [this message]
2013-03-14 21:01 ` Timothy D. Lenz
2013-03-14 21:07 ` Chris Murphy
[not found] ` <51423CB4.6010803@vorgon.com>
[not found] ` <947D0B46-E42D-41A6-A408-99CB4AAA374C@colorremedies.com>
[not found] ` <514241A2.6020301@vorgon.com>
2013-03-14 21:39 ` Chris Murphy
2013-03-15 0:48 ` Timothy D. Lenz
[not found] ` <A7E78320-768A-43AE-AE1D-1BF9E52D5713@colorremedies.com>
2013-03-15 4:41 ` Timothy D. Lenz
2013-03-15 4:48 ` Chris Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=514178AD.5050305@vorgon.com \
--to=tlenz@vorgon.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox