All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: USB3 3TB HDD boot
Date: Mon, 04 Mar 2013 19:46:02 +0100	[thread overview]
Message-ID: <5134EBEA.5030400@gmail.com> (raw)
In-Reply-To: <CAN+r_44uOX0WarOGAu8XhbyZUfEohxzSBScB+it_woKUR0sfoQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]

On 04.03.2013 17:27, Bob Lemar wrote:

> Thank you for your replies.
> 
> 
> Yes, it is definitely BIOS problems as it doesn't allow to boot from
> external drive directly (via BIOS boot order settings). It doesn't
> show this drive at <F10> boot menu even after soft reboot. So BIOS
> doesn't provide access to GRUB like to any other drives or USB
> flashes.
> 
> And I suppose to think that it is not a bug, it is a feature. And
> feature of external drive, not a BIOS.


Wrong. Not supporting 4K disks is simply a lack of support, nothing
else. As for manufacturers producing such drives reasons are several and
partially in an attempt to mitigate msdos partition limitation.

> - BIOS behavior is correct (it power up USB);

It has also to propose the disk to boot from and if chosen, boot from it.
> - Ales, you were absolutely right with floppy for booting CD trick

> example. While MB, HDD firmwares and bootloader have predictable and
> correct behavior some users would like to have bootloader feature
> (GRUB command) that wake up external HDDs and re-detect drives.

BIOS accessing disks is already wakeup enough.> I did: (1) clone linux
to external drive; (2) correct fstab at.
You can access the disk in GRUB using own GRUB modules but you can't
chainload on such drives as it would require BIOS support.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2013-03-04 18:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 15:36 USB3 3TB HDD boot Bob Lemar
2013-02-12 18:59 ` Seth Goldberg
2013-02-12 19:19 ` Aleš Nesrsta
2013-03-04 16:27   ` Bob Lemar
2013-03-04 18:46     ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-03-04 19:19     ` Lennart Sorensen
2013-03-04 19:33       ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-03-04 19:43         ` Lennart Sorensen
2013-03-04 23:16           ` Chris Murphy
2013-03-05  7:22             ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-03-15  2:18               ` Chris Murphy
2013-03-15  2:38                 ` Andrey Borzenkov
2013-03-15  2:56                   ` Chris Murphy
2013-03-15 14:51                     ` Lennart Sorensen
2013-03-15 15:59                       ` Chris Murphy
2013-03-15 16:25                         ` Bruce Dubbs
2013-03-15 17:53                         ` Lennart Sorensen
2013-03-15 18:38                           ` Chris Murphy
2013-03-18 18:34                             ` Bob Lemar
2013-03-18 18:56                               ` Chris Murphy
2013-03-18 19:41                                 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-03-18 21:05                                   ` Chris Murphy
2013-03-18 21:46                                     ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-03-18 22:36                                       ` Chris Murphy
2013-03-18 23:26                                         ` Elliott, Robert (Server Storage)
2013-03-18 22:59                                       ` Chris Murphy
2013-03-20 14:24                                         ` Phillip Susi
2013-03-04 22:39     ` Chris Murphy

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=5134EBEA.5030400@gmail.com \
    --to=phcoder@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.