grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: adrian15 <adrian15sgd@gmail.com>
To: grub-devel@gnu.org
Subject: How to deal with fatal device seeks?
Date: Sun, 16 Mar 2014 06:26:48 +0100	[thread overview]
Message-ID: <53253618.6070702@gmail.com> (raw)

   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
-- 
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-16  5:26 adrian15 [this message]
2014-03-16 16:05 ` How to deal with fatal device seeks? adrian15
2014-03-16 16:43   ` Andrey Borzenkov
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=53253618.6070702@gmail.com \
    --to=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).