public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: raid1 grub ext4
Date: Thu, 14 Apr 2011 15:07:09 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110414T165233-851@post.gmane.org> (raw)
In-Reply-To: 4DA7008F.5030303@binarywings.net

Florian Philipp <lists <at> binarywings.net> writes:


> I don't think the missing partition table is your problem.

OK, let's assume you are correct, ignoring .....

> However, you might be onto something with the changed sector offset. But
> I don't know enough of this to help you.

Well if I have to reformat I look everything on the install.
Not ready to start over yet.....
So after a fresh reboot I see:
livecd ~ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
md125 : active (auto-read-only) raid1 sdb3[1] sda3[0]
      1948226512 blocks super 1.2 [2/2] [UU]
md126 : active (auto-read-only) raid1 sda2[0] sdb2[1]
      5022708 blocks super 1.2 [2/2] [UU]
md127 : active (auto-read-only) raid1 sda1[0] sdb1[1]
      262132 blocks super 1.2 [2/2] [UU]

If you look at previous posts of mine on the md<part>
names, and focus on the sized, you'll see something
very troubling...

The minimal CD keeps using the md125-127 names but assigns
them to the different partitions:
NOW
/boot is: md127 : active (auto-read-only) raid1 sda1[0] sdb1[1]
      262132 blocks super 1.2 [2/2] [UU]

/     is md125 : active (auto-read-only) raid1 sdb3[1] sda3[0]
      1948226512 blocks super 1.2 [2/2] [UU]

swap  is md126 : active (auto-read-only) raid1 sda2[0] sdb2[1]
      5022708 blocks super 1.2 [2/2] [UU]

Something is morphing the numbers each time I reboot
with minCD....

So no what I put in /etc/fstab, it's going to be wrong.

grub cannot find the partition with the kernel? OR
is this not a problem? 

Plus, since  I'm never able to write the grub stuffage to the
MBR, grub nor the kernel every run.....

after rebooting I tried this step to correct for the metadata
problem you previously posted about:

mdadm --create /dev/md1 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda1
/dev/sdb1
mdadm: super0.90 cannot open /dev/sda1: Device or resource busy
mdadm: /dev/sda1 is not suitable for this array.
mdadm: super0.90 cannot open /dev/sdb1: Device or resource busy
mdadm: /dev/sdb1 is not suitable for this array.

mdadm --create /dev/md127 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda1
/dev/sdb1
mdadm: super0.90 cannot open /dev/sda1: Device or resource busy
mdadm: /dev/sda1 is not suitable for this array.
mdadm: super0.90 cannot open /dev/sdb1: Device or resource busy
mdadm: /dev/sdb1 is not suitable for this array.






  reply	other threads:[~2011-04-14 15:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 18:12 [gentoo-user] raid1 grub ext4 James
2011-04-11 20:18 ` Mick
2011-04-12  5:57   ` Stroller
2011-04-12 14:10     ` [gentoo-user] " James
2011-04-12 14:31       ` Peter Humphrey
2011-04-12 14:57         ` Dale
2011-04-12 15:16           ` Joost Roeleveld
2011-04-12 15:44           ` Peter Humphrey
2011-04-13 10:14           ` Alex Schuster
2011-04-11 20:49 ` [gentoo-user] " Neil Bothwick
2011-04-12  2:09   ` Mark Shields
2011-04-12  9:11     ` Neil Bothwick
2011-04-12 14:20       ` [gentoo-user] " James
2011-04-12 16:53         ` James
2011-04-13  9:46           ` Florian Philipp
2011-04-14 12:56             ` James
2011-04-14 13:14               ` Florian Philipp
2011-04-14 14:41               ` Paul Hartman
2011-04-14 13:10             ` James
2011-04-14 13:41               ` James
2011-04-14 14:11                 ` Florian Philipp
2011-04-14 15:07                   ` James [this message]
2011-04-14 15:52                     ` Florian Philipp
2011-04-14 16:29                       ` James
2011-04-14 19:49                         ` Florian Philipp
2011-04-14 20:19                           ` James
2011-04-14 21:12                             ` Florian Philipp
2011-04-14 20:24                           ` James
2011-04-14 14:13                 ` Dale
2011-04-14 14:52                   ` James
2011-04-14 16:14                     ` Dale
2011-04-14 16:34                       ` 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=loom.20110414T165233-851@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@lists.gentoo.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