From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Robert LeBlanc <robert@leblancnet.us>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] disk/mdraid1x: Fix >2TB RAID detection with BIOS
Date: Fri, 18 Nov 2016 21:15:43 +0300 [thread overview]
Message-ID: <d76994da-21f3-c2cb-b824-1041a1153e73@gmail.com> (raw)
In-Reply-To: <CAANLjFpLuJVttcK+ZYr_6NS3KvH2=Vd1zbw06JBe_Z=TPc6DGQ@mail.gmail.com>
18.11.2016 21:06, Robert LeBlanc пишет:
> On Fri, Nov 18, 2016 at 10:31 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
>> 18.11.2016 19:49, Robert LeBlanc пишет:
>>> Based on debug info, GRUB is requesting to read the end of the drive
>>> to read the mdadm 1.0 superblock and gets the following message:
>>>
>>> kern/disk.c:421: Read out of range: sector 0x27fffffc8 (attempt to
>>> read or write outside of disk 'hd0').
>>>
>>
>> Is MD RAID on whole disk or partition? What partition label - MBR or
>> GPT? Could you post fdisk -l from Linux (if your fdisk does not support
>> GPT, use "gdisk -l /dev/sdX")?
>
> # gdisk -l /dev/sda
> GPT fdisk (gdisk) version 1.0.1
>
> Partition table scan:
> MBR: protective
> BSD: not present
> APM: not present
> GPT: present
>
> Found valid GPT with protective MBR; using GPT.
> Disk /dev/sda: 10737418240 sectors, 5.0 TiB
> Logical sector size: 512 bytes
> Disk identifier (GUID): 939F7AAD-AADD-481D-8896-DA0B4033C70C
> Partition table holds up to 128 entries
> First usable sector is 2048, last usable sector is 10737418206
> Partitions will be aligned on 2048-sector boundaries
> Total free space is 0 sectors (0 bytes)
>
> Number Start (sector) End (sector) Size Code Name
> 1 2048 4095 1024.0 KiB EF02
> 2 4096 10737418206 5.0 TiB FD00
>
> partition # is a mdadm RAID 1 member partitioned as follows...
>
> # sgdisk -l /dev/md123
> # parted /dev/md123 print free
> Model: Linux Software RAID Array (md)
> Disk /dev/md123: 5497GB
> Sector size (logical/physical): 512B/512B
> Partition Table: gpt
> Disk Flags:
>
> Number Start End Size File system Name Flags
> 17.4kB 1049kB 1031kB Free Space
> 1 1049kB 2097kB 1049kB bios_grub
> 2 2097kB 5371MB 5369MB linux-swap(v1)
> 3 5371MB 6371MB 1000MB ext2
> 4 6371MB 5497GB 5491GB ext4
> 5497GB 5497GB 966kB Free Space
>
> /dev/sdb is partitioned identically to /dev/sda
>
OK, could you please also show "ls -l" in grub CLI; if you cannot
capture serial console, attach screenshot(s). You may want to "set
pager=1" so output does not scroll off screen.
next prev parent reply other threads:[~2016-11-18 18:15 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 [this message]
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
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=d76994da-21f3-c2cb-b824-1041a1153e73@gmail.com \
--to=arvidjaar@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).