grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>,
	 Andrei Borzenkov <arvidjaar@gmail.com>
Subject: Re: Switching to another boot device on failure
Date: Fri, 28 Nov 2014 21:24:23 +0200	[thread overview]
Message-ID: <5478CBE7.50001@gmail.com> (raw)
In-Reply-To: <CAFQyPcqOS+tRaDqvGS9FEa10vXFZYJmfQXXsc7fUmibT3DbFzQ@mail.gmail.com>

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

On 20.11.2014 15:38, Venkata Subbarao wrote:
> Once again Thank you Andrei.
> Modified the grub source and added grub_exit (). After this BIOS booted
> from next device.
> 
> I am now working on a solution where if the UUID present in the grub.cfg
> goes bad.
> One way I am thinking is to check the CRC of the grub.cfg and other
> image files required for booting. This may be bit lengthy.
> Let me know if you have suggestions.
> 
What is the scenario you want to protect against? checksums are mainly
useful against hardware failure but if hardware is defective the only
way to surely bring it back is to replace failing components.
The most common way for UUID to go unsync is because of software or
operator error and both are likely to recompute checksum or change
actual disk UUID without changing grub.cfg.
> Thanks,
> Subbarao
> 
> On Wed, Nov 19, 2014 at 8:57 AM, Venkata Subbarao
> <rao.subba.venkata@gmail.com <mailto:rao.subba.venkata@gmail.com>> wrote:
> 
>     Thank you very much Andrei.
>     I will try out this and update.
> 
> 
>     - Subbarao
> 
>     On Wed, Nov 19, 2014 at 8:46 AM, Andrei Borzenkov
>     <arvidjaar@gmail.com <mailto:arvidjaar@gmail.com>> wrote:
> 
>         В Tue, 18 Nov 2014 10:51:00 +0000 (UTC)
>         Venkata Subbarao <rao.subba.venkata@gmail.com
>         <mailto:rao.subba.venkata@gmail.com>> пишет:
> 
>         > Hi All,
>         >
>         > I am working on a task on XUbuntu OS in which due to any
>         reason if booting
>         > fails I would like to switch to another boot device by zeroing
>         the MBR of
>         > current boot disk. Is this possible ?
>         >
>         > For example instead of showing following prompt, I would like
>         to zero out
>         > the MBR so that the BIOS can select next boot device upon reset.
>         >
>         > error: no such partition
>         > grub rescue>
>         >
> 
>         grub supports only very limited and controlled ways to write to
>         device/file. Doing something like this in unattended manner is
>         probably
>         way too dangerous.
> 
>         What would be possible is to optionally exit grub (after timeout) in
>         this case; then BIOS should proceed to next boot device.
> 
> 
> 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 



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

      parent reply	other threads:[~2014-11-28 20:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 10:51 Switching to another boot device on failure Venkata Subbarao
2014-11-19  3:16 ` Andrei Borzenkov
2014-11-19 13:59   ` Arbiel Perlacremaz
     [not found]   ` <CAFQyPcp7XO+Vs+fO-oYSPjvdHdTiB=oj8GCGbOLxmf6vs7YZGA@mail.gmail.com>
2014-11-20 13:38     ` Venkata Subbarao
     [not found]       ` <20141120202316.5afdeaab@opensuse.site>
2014-11-21 13:29         ` Venkata Subbarao
2014-11-28 19:24       ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]

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=5478CBE7.50001@gmail.com \
    --to=phcoder@gmail.com \
    --cc=arvidjaar@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).