From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>,
Robert LeBlanc <robert@leblancnet.us>
Subject: Re: [PATCH] disk/mdraid1x: Fix >2TB RAID detection with BIOS
Date: Tue, 24 Jan 2017 09:57:51 +0000 [thread overview]
Message-ID: <CAEaD8JMhg2aFcRyHcEvXTS2gXNLQqHZLwk3C92eB7UYGA7qiTQ@mail.gmail.com> (raw)
In-Reply-To: <CAANLjFq9K1fJN5ufrfOyY3pbaeRPbShFz=HNTrVE-63zCXNuEw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2341 bytes --]
This fix is buggy as you don't reset grub_errno on this path. Also you
probably want to ignore only a single error type GRUB_ERR_OUT_OF_RANGE as
others are likely still fatal.
On Wed, 11 Jan 2017, 20:26 Robert LeBlanc <robert@leblancnet.us> wrote:
> Can we get this fix merged in?
>
> Thanks
> ----------------
> Robert LeBlanc
> PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1
>
>
> On Thu, Nov 17, 2016 at 1:09 PM, Robert LeBlanc <robert@leblancnet.us>
> wrote:
> > When a mdadm RAID array is on a drive larger than 2TB, the array is not
> > able to be detected and as such even if the array has a partition that
> > holds /boot under the 2TB limit, it is unable to boot the machine. This
> > is caused by metadata 1.0 being tested first which allocates the
> > superblock at the end of the device. When it tries to access the end of
> > the device it throws an error and the code returns without trying to
> > find the superblock at other locations (metadata 1.1 and 1.2). This
> > patch changes the error to not be fatal and allow for the checking for
> > the other metadata versions and allowing the machine to boot as long as
> > /boot is under the 2TB BIOS limit. This won't cause issues with 1.0
> > metadata because GRUB is able to read the partitions from the front of
> > the drive/partition without having to determine the data offset, since
> > the data for metadata 1.0 starts at sector 0.
> >
> > Signed-off-by: Robert LeBlanc <robert@leblancnet.us>
> > ---
> > grub-core/disk/mdraid1x_linux.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/grub-core/disk/mdraid1x_linux.c
> b/grub-core/disk/mdraid1x_linux.c
> > index 7cc80d3..cc7350c 100644
> > --- a/grub-core/disk/mdraid1x_linux.c
> > +++ b/grub-core/disk/mdraid1x_linux.c
> > @@ -148,7 +148,7 @@ grub_mdraid_detect (grub_disk_t disk,
> >
> > if (grub_disk_read (disk, sector, 0, sizeof (struct
> grub_raid_super_1x),
> > &sb))
> > - return NULL;
> > + continue;
> >
> > if (sb.magic != grub_cpu_to_le32_compile_time (SB_MAGIC)
> > || grub_le_to_cpu64 (sb.super_offset) != sector)
> > --
> > 2.10.1
> >
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: Type: text/html, Size: 4100 bytes --]
next prev parent reply other threads:[~2017-01-24 9:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 20:09 [PATCH] disk/mdraid1x: Fix >2TB RAID detection with BIOS Robert LeBlanc
2016-11-18 4:16 ` Andrei Borzenkov
2016-11-18 16:49 ` Robert LeBlanc
2016-11-18 17:31 ` Andrei Borzenkov
2016-11-18 18:06 ` Robert LeBlanc
2016-11-18 18:15 ` Andrei Borzenkov
2016-11-18 18:19 ` Robert LeBlanc
2016-11-18 18:24 ` Andrei Borzenkov
2016-11-18 20:43 ` Robert LeBlanc
2016-11-19 8:59 ` Andrei Borzenkov
2016-11-19 17:57 ` Robert LeBlanc
2016-11-19 18:40 ` Andrei Borzenkov
2016-11-20 2:47 ` Robert LeBlanc
2016-11-20 3:38 ` Robert LeBlanc
2016-11-20 6:53 ` Andrei Borzenkov
2016-11-22 19:00 ` Robert LeBlanc
2016-12-06 16:59 ` Robert LeBlanc
2017-01-11 17:21 ` Robert LeBlanc
2017-01-24 9:57 ` Vladimir 'phcoder' Serbinenko [this message]
2017-01-24 17:22 ` Robert LeBlanc
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=CAEaD8JMhg2aFcRyHcEvXTS2gXNLQqHZLwk3C92eB7UYGA7qiTQ@mail.gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=robert@leblancnet.us \
/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).