From: joost@antarean.org
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [O/T] RAID help - now won't boot
Date: Sun, 20 Oct 2013 16:31:12 +0200 [thread overview]
Message-ID: <30a1c0c8-79ea-4606-9961-c4c9e95a6d91@email.android.com> (raw)
In-Reply-To: <5263DB18.6020409@hadt.biz>
[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]
Michael Hampicke <mh@hadt.biz> wrote:
>Am 20.10.2013 15:13, schrieb Mick:
>> On Sunday 20 Oct 2013 13:57:34 Michael Hampicke wrote:
>>> Am 20.10.2013 11:54, schrieb Mick:
>>>> Any ideas why the Ubuntu installation won't boot?
>>>
>>> My guess would be, you cannot boot, because if you install grub in
>>> /dev/md0.
>>>
>>> Upon boot the bios cannot find stage1 of the bootloader, which
>normally
>>> lies in the MBR (which also houses the partition table).
>>
>> I see ... so installing the MBR code in the /dev/md0 block device is
>further
>> down the disk than where BIOS is looking for it and that's why it
>errors out?
>>
>
>That would be my guess. Maybe someone more knowledgeable on how mdadm
>writes stuff on the disk can jump in and provide additional info. But
>I'm pretty sure, if you install grub in md0, it's not in that place on
>the disk where the bios is actually looking for.
>
>>
>> It seems to me then that I *have* to create normal partitions on
>/dev/sda &
>> /dev/sdb, or I would need a different boot drive. Is there another
>way to
>> overcome this problem.
>
>Maybe create two mds. md1 (sda1, sdb1) is a small boot partition which
>contains stage2+, the kernel and the initramfs. And md2 (sda2, sdb2)
>which acts as another block device with partition table, etc...
>In this setup you could install grub in the mbr of sda and sdb
>(grub-install /dev/sda...)
>
>A quick google on this subject returned no usable results. But I am off
>now until tomorrow.
I would suggest trying it by usong the older metadata format.
Check the man pages, but I thinl it would be --metadata=0.90 (or similar) during creation.
That might put the metadata at the end, rather then at the front. (Or it's the other way round and new metadata does it at the end.)
--
Joost
Ps. I have never tried it this way (full disk raid for boot device) using linux software raid.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 2852 bytes --]
next prev parent reply other threads:[~2013-10-20 14:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 7:34 [gentoo-user] RAID help Mick
2013-10-15 19:28 ` Paul Hartman
2013-10-15 21:42 ` Mick
2013-10-16 18:10 ` [gentoo-user] " Nicolas Sebrecht
2013-10-16 20:14 ` Nicolas Sebrecht
2013-10-17 5:33 ` Mick
2013-10-20 9:54 ` [gentoo-user] Re: [O/T] RAID help - now won't boot Mick
2013-10-20 12:57 ` Michael Hampicke
2013-10-20 13:13 ` Mick
2013-10-20 13:31 ` Michael Hampicke
2013-10-20 14:31 ` joost [this message]
2013-10-21 5:33 ` Mick
2013-10-21 5:59 ` J. Roeleveld
2013-10-21 8:24 ` Nicolas Sebrecht
2013-10-21 8:55 ` J. Roeleveld
2013-10-21 21:42 ` Mick
2013-10-22 7:10 ` Nicolas Sebrecht
2013-10-24 18:53 ` Mick
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=30a1c0c8-79ea-4606-9961-c4c9e95a6d91@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