From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS with RAID1 cannot boot when removing drive
Date: Tue, 11 Feb 2014 06:59:34 +0000 (UTC) [thread overview]
Message-ID: <pan$e606d$929b6b8a$283bf1a2$38f7ec5@cox.net> (raw)
In-Reply-To: 20140211041527.57ef96c4@system
Saint Germain posted on Tue, 11 Feb 2014 04:15:27 +0100 as excerpted:
> Ok I need to really understand how my motherboard works (new Z87E-ITX).
> It is written "64Mb AMI UEFI Legal BIOS", so I thought it was really
> UEFI.
I expect it's truly UEFI. But from what I've read most UEFI based
firmware(possibly all in theory, with the caveat that there's bugs and
some might not actually work as intended due to bugs) on x86/amd64 (as
opposed to arm) has a legacy-BIOS mode fallback. Provided it's not in
secure-boot mode, if the storage devices it is presented don't have a
valid UEFI config, it'll fall back to legacy-BIOS mode and try to detect
and boot that.
Which may or may not be what your system is actually doing. As I said,
since I've not actually experimented with UEFI here, my practical
knowledge on it is virtually nil, and I don't claim to have studied the
theory well enough to deduce in that level of detail what your system is
doing. But I know that's how it's /supposed/ to be able to work. =:^)
(FWIW, what I /have/ done, deliberately, is read enough about UEFI to
have a general feel for it, and to have been previously exposed to the
ideas for some time, so that once I /do/ have it available and decide
it's time, I'll be able to come up to speed relatively quickly as I've
had the general ideas turning over in my head for quite some time
already, so in effect I'll simply be reviewing the theory and doing the
lab work, while concurrently making logical connections about how it all
fits together that only happen once one actually does that lab work.
I've discovered over the years that this is perhaps my most effective way
to learn, read about the general principles while not really
understanding it the first time thru, then come back to it some months or
years later, and I pick it up real fast, because my subconscious has been
working on the problem the whole time! Come to think of it, that's
actually how I handled btrfs, too, trying it at one point and deciding it
didn't fit my needs at the time, leaving it for awhile, then coming back
to it later when my needs had changed, but I already had an idea what I
was doing from the previous try, with the result being I really took to
it fast, the second time! =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-02-11 7:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 21:40 BTRFS with RAID1 cannot boot when removing drive Saint Germain
2014-02-10 3:34 ` Duncan
2014-02-11 2:30 ` Saint Germain
2014-02-14 14:33 ` Saint Germain
2014-02-16 15:30 ` Saint Germain
2014-02-11 2:18 ` Chris Murphy
2014-02-11 3:15 ` Saint Germain
2014-02-11 6:59 ` Duncan [this message]
2014-02-11 10:04 ` Saint Germain
2014-02-11 20:35 ` Duncan
2014-02-12 17:16 ` Saint Germain
2014-02-11 17:33 ` UEFI/BIOS, was: " Chris Murphy
2014-02-11 7:47 ` Duncan
2014-02-11 17:21 ` Chris Murphy
2014-02-11 17:36 ` Saint Germain
2014-02-11 18:19 ` Chris Murphy
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='pan$e606d$929b6b8a$283bf1a2$38f7ec5@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).