From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1WPEAN-00082p-5T for mharc-grub-devel@gnu.org; Sun, 16 Mar 2014 12:44:03 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54332) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPEAD-00081V-QS for grub-devel@gnu.org; Sun, 16 Mar 2014 12:44:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPEA5-0005Uz-EA for grub-devel@gnu.org; Sun, 16 Mar 2014 12:43:53 -0400 Received: from mail-lb0-x233.google.com ([2a00:1450:4010:c04::233]:40534) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPEA4-0005Un-JC for grub-devel@gnu.org; Sun, 16 Mar 2014 12:43:45 -0400 Received: by mail-lb0-f179.google.com with SMTP id p9so3089141lbv.10 for ; Sun, 16 Mar 2014 09:43:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=TWTQMK/RKMPaWpV/Nk12JOYQja3TrsxD3JYBzRnAroA=; b=V5C4bL3hgz/x5WEGFJdSc+Y8tBQD+jjkc2FoXdjHKJ4jokKJfdWocBfhagCBPcnpn0 Qa9UbjLmwTX66timgSFF0fcFSnQH2P/UEs+3DHHJ533ZKMvhq+Vt1F+Y3ULIq5SFShu1 wZhd6hShs00lxgIRgN/DEZzEDuSBWl7InyxpWvbioONhaR1lKJP+0GUOjYTni2z61C20 r/CTDG5xThaK2DIHIO65U9MPV7w6oN0W+Ig8Y9E6WsLfUUIUgMJpnTaMRzbhbZarG0MS wYqiZWmTsqKN8Pm/DtUloTs4mw7SOeTS7iz6NToDAqllQ+UxMJzDFFwca3BHYg10JA07 PbVA== X-Received: by 10.112.97.178 with SMTP id eb18mr12870390lbb.13.1394988223213; Sun, 16 Mar 2014 09:43:43 -0700 (PDT) Received: from opensuse.site (ppp37-190-15-130.pppoe.spdop.ru. [37.190.15.130]) by mx.google.com with ESMTPSA id d9sm11119993laa.17.2014.03.16.09.43.41 for (version=SSLv3 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 16 Mar 2014 09:43:42 -0700 (PDT) Date: Sun, 16 Mar 2014 20:43:41 +0400 From: Andrey Borzenkov To: The development of GNU GRUB Subject: Re: How to deal with fatal device seeks? Message-ID: <20140316204341.46f20ebb@opensuse.site> In-Reply-To: <5325CBE1.5090302@gmail.com> References: <53253618.6070702@gmail.com> <5325CBE1.5090302@gmail.com> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.22; x86_64-suse-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::233 Cc: adrian15sgd@gmail.com X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Mar 2014 16:44:02 -0000 =D0=92 Sun, 16 Mar 2014 17:05:53 +0100 adrian15 =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >=20 > I'm getting the same problem > ( FATAL: int13_cdrom: function 42. Can't use 64bits lba ) >=20 This message does not exist in grub sources, so it likely comes from firmware. 64 bit LBA would mean size over 2TB. So the first question - what size of disks do you have? > with hd0, hd1, hd2, hd3, and worse: >=20 > * hd2,msdos5 >=20 > ls (hd2,msdos5)/ >=20 > Is this a bug? >=20 Hard to tell. Do you actually have working filesystem(s) on these partitions? The message itself simply means that grub attempts to read very high offset. I wonder if it can be somehow byte order related. > adrian15 >=20 > El 16/03/14 06:26, adrian15 escribi=C3=B3: > > I use a for loop for detecting Operating systems like this one: > > > > for dev in (*); do > > > > echo $dev > > > > done > > > > but it hangs !!! > > > > So some clues: > > > > * Using 2.02~beta2-7 from Debian Unstable. > > * The disk is an hybrid one (x86_64_efi + i386_pc). > > * The error only happens when using Virtualbox in a non-EFI setup. > > > > So some questions: > > > > * Is it a bug that a non seekable device like (cd,apple4) or (cd,gpt1) > > is available in non-EFI mode? > > * Is it perhaps a Virtualbox bug? > > * I cannot catch these fatal error as if they were exceptions inside a > > try-catch. Or can I? > > > > I will probably improve my searchindevices functions so that it also > > filters these (cdsomething) devices as a workaround. > > > > Thank you. > > > > > > These are the minimal tests: > > > > --- Using Qemu as EFI gives no problem: > > > > echo (*) > > (fd0) ... (cd) ... (cd,apple2),... (cd,gpt2) > > ls (cd,apple4)/ > > error: unknown filesystem. > > ls (cd,gpt1)/ > > error: unknown filesystem. > > > > --- Using Virtualbox as BIOS (Ex. 1) (Problem): > > > > echo (*) > > (fd0) ... (cd) ... (cd,apple2),... (cd,gpt2) > > ls (cd,apple4)/ > > FATAL: int13_cdrom: function 42. Can't use 64bits lba > > > > --- Using Virtualbox as BIOS (Ex. 2) (No problem): > > > > echo (*) > > (fd0) ... (cd) ... (cd,apple2),... (cd,gpt2) > > ls (cd,gpt4)/ > > error: unknown filesystem. > > > > --- Using Virtualbox as BIOS (Ex. 3) (Problem): > > > > echo (*) > > (fd0) ... (cd) ... (cd,apple2),... (cd,gpt2) > > ls (cd,gpt1)/ > > FATAL: int13_cdrom: function 42. Can't use 64bits lba > > > > > > adrian15 >=20