Andrei, I sent a VM that displays the problem. It bounced from the listserv (I kind of expected that), but should have been sent to your email directly as well.
For my own curiosity are you against the patch I submitted? I understand that you are trying to figure out why the sectors can't be accessed as a larger issue. Is there something I can do to help get this resolved? Some more details on the hardware: SuperMicro SYS-6028TP-HTFR BIOS 1.1 American Megatrends Inc 08/03/2015 Intel I350 NIC firmware 1.63 (iSCSI boot) For KVM I'm running Debian stretch with ii qemu-kvm 1:2.7+dfsg-3+b1 amd64 QEMU Full virtualization on x86 hardware ---------------- Robert LeBlanc PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1 On Sat, Nov 19, 2016 at 11:53 PM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > 20.11.2016 05:47, Robert LeBlanc пишет: >> This is on super micro and KVM. You can replicate it on a VM. >> > > I can't without more details. 5TB drive is correctly shown as 5TB in > QEMU KVM 2.5 here. > >> Sent from a mobile device, please excuse any typos. >> >> On Nov 19, 2016 11:40 AM, "Andrei Borzenkov" <arvidj...@gmail.com> wrote: >> >>> 19.11.2016 20:57, Robert LeBlanc пишет: >>>> On Sat, Nov 19, 2016 at 1:59 AM, Andrei Borzenkov <arvidj...@gmail.com> >>> wrote: >>>>> biosdisk mdraid1x >>>> >>>> Here is the screenshot of the output. >>>> >>> >>> >>> So it does not even mask LBA to 32 bit, it really returns 2TB. What >>> system (motherboard) is it? What is disk controller? How drives are >>> connected (directly to motherboard or some external adapter)? >>> >> > _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
