grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: adrian15sgd@gmail.com
Subject: Re: How to deal with fatal device seeks?
Date: Sun, 16 Mar 2014 20:43:41 +0400	[thread overview]
Message-ID: <20140316204341.46f20ebb@opensuse.site> (raw)
In-Reply-To: <5325CBE1.5090302@gmail.com>

В Sun, 16 Mar 2014 17:05:53 +0100
adrian15 <adrian15sgd@gmail.com> пишет:

> 
> I'm getting the same problem
> ( FATAL: int13_cdrom: function 42. Can't use 64bits lba )
> 

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:
> 
> * hd2,msdos5
> 
> ls (hd2,msdos5)/
> 
> Is this a bug?
> 

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
> 
> El 16/03/14 06:26, adrian15 escribió:
> >    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
> 



  reply	other threads:[~2014-03-16 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-16  5:26 How to deal with fatal device seeks? adrian15
2014-03-16 16:05 ` adrian15
2014-03-16 16:43   ` Andrey Borzenkov [this message]
2014-03-16 17:16     ` adrian15
2014-03-16 18:05       ` adrian15
2014-03-16 18:40         ` adrian15
2014-03-16 22:19         ` Vladimir 'φ-coder/phcoder' Serbinenko

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=20140316204341.46f20ebb@opensuse.site \
    --to=arvidjaar@gmail.com \
    --cc=adrian15sgd@gmail.com \
    --cc=grub-devel@gnu.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).