public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Neil Bothwick <neil@digimed.co.uk>
Subject: Re: [gentoo-user] New drive devices after install
Date: Sat, 19 Feb 2011 06:25:26 -0800	[thread overview]
Message-ID: <AANLkTikyzyJwASQQNEUAW_H7nBGvQYhsp03nzdRy-HH_@mail.gmail.com> (raw)
In-Reply-To: <20110219100111.00c0577e@digimed.co.uk>

On Sat, Feb 19, 2011 at 2:01 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Fri, 18 Feb 2011 17:54:56 -0700, Mike Diehl wrote:
>
>> I just finished a new (RAID1) installation and most if it is working
>> just fine.
>>
>> However, I don't have any drive device files in /dev/.  I'd expect to
>> see hda, hdb,md{1-3}
>
> Something changed recently, my RAID devices are now md126 and md127.
>
>
> --
> Neil Bothwick
>
> If at first you don't succeed, redefine success.
>

I see the same thing here. I'm in the middle of an install so I create
/dev/md3 to build my RAID1. I build it, install, chroot, do the work,
install grub, reboot and it's md126. The problem is that the machine
name changes between the install and the reboot.

The change apparently has something to do with a decision to only
assemble Version 1.+ superblocks with the right name when the name
field matches something in the superblock.

Apparently you can set up the naming as you wish using

mdadm --update=homehost
mdadm --update=name

but I don't feel confident enough yet to do it.

c2stable ~ # mdadm --detail /dev/md126
/dev/md126:
        Version : 0.90
  Creation Time : Tue Apr 13 09:02:34 2010
     Raid Level : raid1
     Array Size : 52436032 (50.01 GiB 53.69 GB)
  Used Dev Size : 52436032 (50.01 GiB 53.69 GB)
   Raid Devices : 3
  Total Devices : 3
Preferred Minor : 126
    Persistence : Superblock is persistent

    Update Time : Sat Feb 19 06:13:16 2011
          State : clean
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0

           UUID : edb0ed65:6e87b20e:dc0d88ba:780ef6a3
         Events : 0.248829

    Number   Major   Minor   RaidDevice State
       0       8        5        0      active sync   /dev/sda5
       1       8       21        1      active sync   /dev/sdb5
       2       8       37        2      active sync   /dev/sdc5
c2stable ~ #

- Mark



  parent reply	other threads:[~2011-02-19 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-19  0:54 [gentoo-user] New drive devices after install Mike Diehl
     [not found] ` <20110219100111.00c0577e@digimed.co.uk>
2011-02-19 14:25   ` Mark Knecht [this message]
2011-02-19 20:13 ` [gentoo-user] " James

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=AANLkTikyzyJwASQQNEUAW_H7nBGvQYhsp03nzdRy-HH_@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=neil@digimed.co.uk \
    /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