All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: linux-raid@vger.kernel.org
Subject: Re: Converting system to raid
Date: Sun, 12 Apr 2009 12:55:33 -0700	[thread overview]
Message-ID: <000b01c9bba8$a5b08a40$0a00a8c0@vorg> (raw)
In-Reply-To: 20090412111107.GA19413@cthulhu.home.robinhill.me.uk

While booted on the array I renamed device.map and ran:
sudo grub --no-floppy --device-map=/boot/grub/device.map

But the new map is the same:
(hd0) /dev/hda
(hd1) /dev/sda
(hd2) /dev/sdb

----- Original Message ----- 
From: "Robin Hill" <robin@robinhill.me.uk>
To: <linux-raid@vger.kernel.org>
Sent: Sunday, April 12, 2009 4:11 AM
Subject: Re: Converting system to raid

> Before when at the grub boot menu when booting with the ide moved
> below the sata drives, droping to command line for grub showed that
> the ide drive only moved down 1, not 2. It seemed to have:
>   hd0 = sda
>   hd1 = hda
>   hd2 = sdb
> 
> Now with the array booted, going to the grub command line and using
> auto complete for "root (hd0," it seems to be using the device map at
> this point which is no longer correct:
> (hd0) /dev/hda
> (hd1) /dev/sda
> (hd2) /dev/sdb
> 
> Note that in the other system, because linux was installed with only
> the ide and 1 sata drive, it doesn't even list the other two in it's
> device map. So what is the best/safest way to update/correct this to
> what ever it should be?
>
Just delete/rename the old device map file (/boot/grub/device.map) and
run grub again - it'll rescan the devices and create a new map file.

  reply	other threads:[~2009-04-12 19:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 23:44 Converting system to raid Timothy D. Lenz
2009-04-10  9:10 ` KwangErn Liew
2009-04-10  9:55   ` CoolCold
2009-04-10 19:43     ` Timothy D. Lenz
2009-04-10 19:53   ` Robin Hill
2009-04-10 20:45     ` Timothy D. Lenz
2009-04-10 20:59       ` Robin Hill
2009-04-10 21:26         ` Timothy D. Lenz
2009-04-10 21:51           ` Robin Hill
2009-04-11  5:29             ` Timothy D. Lenz
2009-04-11 14:29               ` CoolCold
2009-04-11 18:47                 ` Timothy D. Lenz
2009-04-12  0:53                   ` Timothy D. Lenz
2009-04-12 11:11                     ` Robin Hill
2009-04-12 19:55                       ` Timothy D. Lenz [this message]
2009-04-14  9:30                         ` Robin Hill
2009-04-17  0:47                           ` Timothy D. Lenz
2009-04-17  7:49                             ` Robin Hill
2009-04-11 14:36               ` Robin Hill
2009-04-11 15:04                 ` jim owens
2009-04-11 15:44                   ` Jeff Garzik
2009-04-11 17:40                     ` jim owens
2009-04-12 11:11                       ` Jeff Garzik
2009-04-12 16:43                         ` jim owens
2009-04-12 17:18                           ` Jeff Garzik
2009-04-10 13:22 ` Robin Hill
2009-04-10 19:22   ` Timothy D. Lenz
2009-04-10 19:50     ` Robin Hill
2009-04-11  4:40       ` Jon Lewis
2009-04-11  7:48         ` Jan Ceuleers
2009-04-11  8:50         ` Goswin von Brederlow

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='000b01c9bba8$a5b08a40$0a00a8c0@vorg' \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.