From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] boot failure using root=LABEL=RAID1root but not LABEL=RAID6root
Date: Mon, 31 Dec 2012 21:53:52 +0100 [thread overview]
Message-ID: <ad7a8871-b659-4a41-8fe8-4299de316f3d@email.android.com> (raw)
In-Reply-To: <CAK2H+eemy9qT5QcNwmJMGq-ohf8ahvisa=dFSxb9GxsqcQ=4gw@mail.gmail.com>
Mark Knecht <markknecht@gmail.com> wrote:
>Hi,
> I don't think this is likely to be a Gentoo issue but I figured I'd
>ask here first before going elsewhere. (LKML, linux-raid, elsewhere)
>Additionally it's not a critical problem at all but rather something
>I'd like to try and understand and then report if appropriate.
>
> On my main i7-980x machine I've been wanting to move root away from
>an old 3-disk 50GB RAID1 that I built first built the machine with to
>a newer 150GB RAID6. Toward this end the machine has two complete
>Gentoo builds on it:
>
>c2stable ~ # cat /proc/mdstat
><SNIP>
>
>md3 : active raid6 sdc3[1] sdd3[2] sdb3[0] sde3[3] sdf3[5]
>157305168 blocks super 1.2 level 6, 16k chunk, algorithm 2 [5/5]
>[UUUUU]
>
>md126 : active raid1 sdd5[2] sdc5[1] sdb5[0]
> 52436032 blocks [3/3] [UUU]
>
>unused devices: <none>
>c2stable ~ #
>
>md126 is the older RAID1, md3 is the newer RAID6. The are both built
>on parts of the 5 hard drives in the box.
>
>The two builds are intended to be identical. Same packages installed,
>same kernel with the only exception being the RAID6 uses an initramfs
>built into it. A diff of the two kernel configs shows only that
>difference:
>
>c2stable ~ # diff /usr/src/linux/.config
>/mnt/newRAID6/usr/src/linux/.config
>137c137,139
>< CONFIG_INITRAMFS_SOURCE=""
>---
>> CONFIG_INITRAMFS_SOURCE="/usr/src/initramfs.config"
>> CONFIG_INITRAMFS_ROOT_UID=0
>> CONFIG_INITRAMFS_ROOT_GID=0
>142a145,146
>> CONFIG_INITRAMFS_COMPRESSION_NONE=y
>> # CONFIG_INITRAMFS_COMPRESSION_GZIP is not set
>c2stable ~ #
>
> In my grub.conf file I have three methods of booting the machine.
>There are two methods of booting the RAID1 config, using the device
>name and using the label. For the RAID6 I have only the label method:
>
>(NOTE: Snipped out backup kernels just to clarify)
>
>c2stable ~ # cat /boot/grub/grub.conf
>default 0
>timeout 15
>splashimage=(hd0,0)/boot/grub/splash.xpm.gz
>
>title RAID1 3.6.11-gentoo
>root (hd0,0)
>kernel (hd0,0)/boot/bzImage-3.6.11-gentoo root=/dev/md126
>
>title RAID1 3.6.11-gentoo using LABEL
>root (hd0,0)
>kernel (hd0,0)/boot/bzImage-3.6.11-gentoo root=LABEL=RAID1root
>
>title RAID6 3.6.11-gentoo using LABEL
>root (hd0,0)
>kernel (hd0,0)/boot/bzImage-RAID6-3.6.11-gentoo root=LABEL=RAID6root
>
>c2stable ~ #
>
>c2stable ~ # e2label /dev/md126
>RAID1root
>c2stable ~ # e2label /dev/md3
>RAID6root
>c2stable ~ #
>
>
>The results are:
>
>1) RAID1 using md126 boots fine
>2) RAID1 using label of RAID1root fails
>3) RAID6 using label of RAID6root boots fine
>
> The failure is a kernel crash before the machine gets very far so
>the only capture I might be able to try is with a camera and then post
>that on line, but the screen is 80x25 and it's just a kernel crash so
>there's very little data on the screen when the machine dies.
>
> I've been Googling around for a couple of days but haven't found
>anything very interesting. I figured I'd ask here first just to see
>what ideas come up.
>
>Thanks,
>Mark
Mark.
I seem to remember that to be able to use LABEL for the root= line requires an init* as you need userspace utilities to read the labels.
You could try the UUIDs instead. But I am not sure if that might work.
HTH
Joost
PS. All the best for 2013!
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2012-12-31 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 17:31 [gentoo-user] boot failure using root=LABEL=RAID1root but not LABEL=RAID6root Mark Knecht
2012-12-31 20:53 ` J. Roeleveld [this message]
2012-12-31 22:09 ` Mark Knecht
2012-12-31 22:23 ` J. Roeleveld
2012-12-31 22:28 ` Bruce Hill
2012-12-31 22:38 ` Mark Knecht
2012-12-31 22:59 ` J. Roeleveld
2012-12-31 23:10 ` Mark Knecht
2013-01-01 15:23 ` Dustin C. Hatch
2013-01-01 17:26 ` Mark Knecht
2012-12-31 23:07 ` covici
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=ad7a8871-b659-4a41-8fe8-4299de316f3d@email.android.com \
--to=joost@antarean.org \
--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