All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: "Dale Carstensen" <dlc@lampinc.com>
Cc: grub-devel@gnu.org
Subject: Re: grub rescue read or write sector outside of partition
Date: Fri, 26 Jun 2015 11:11:14 +0300	[thread overview]
Message-ID: <20150626111114.247a6e3a@opensuse.site> (raw)
In-Reply-To: <20150626000953.M20169@lampinc.com>

В Thu, 25 Jun 2015 17:33:25 -0700
"Dale Carstensen" <dlc@lampinc.com> пишет:

> I had a drive fail, and it is the one that had grub on it.
> It had parts of two RAID-6 partitions, too.  So I bought a
> new drive and added partitions on it to replace the failed
> RAID-6 parts.  That was still booting OK from the failed
> drive, but then I updated the kernel, and I decided to also
> install a new grub on the new drive.
> 

How? Please show exact commands you used as well as your disk
configuration.

> That seemed to go OK until I tried to reboot.  I landed in
> grub rescue.  Fortunately I have several computers, so I can
> look up documentation, etc. without my main desktop functioning.
> Somewhere I found that grub rescue has only a few commands, none
> of them "help" or a list of commands, and no TAB-expansions.
> Well, they seem to be ls, set, unset and insmod.  Supposedly,
> running insmod normal, then normal, will get back to the
> fuller set of commands with help, but that's where it gets
> the "outside of partition" error, it seems.
> 
> I can ls the /boot/grub/i386-pc/ directory, where normal.mod
> is, so I would think grub rescue could find and read normal.mod,
> too, but, I guess not.
> 

Please show output of "set" command at this point.

> So, set debug=all helped a little, expanding the message
> from just something like (I'd have to keep trying to
> reboot to get it verbatim) read or write bad, to
> the specific size of the partition (in decimal, around
> 175 million 512-byte blocks) and the sector it is trying
> to read (read.c:461) (in hexadecimal), around 10 million.
> But 10 million hex really is larger than 175 million
> decimal.
> 
> So maybe my BIOS has some limitation on how deep it can
> read into this 2 TB drive, or maybe the drive having
> hardware sectors of 4096 bytes replacing one with
> 512 confuses grub.  But the old drive with the failures
> gets the same problem.
> 
> It's gentoo, grub2 (I could look up the version once it's
> running again), 64-bit (although grub seems not to really
> notice 32- vs 64-bit, or the kernel, so I'm not sure it's
> just smart or really dumb), and, like I say, the / partition
> is RAID-6, including /boot.  I'm going to try making a
> non-RAID /boot, maybe later I'll try making it RAID-1,
> to see if that helps.
> 
> Any advise?
> 
> Thanks.
> 
> --
> Open WebMail Project (http://openwebmail.org)
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel



  reply	other threads:[~2015-06-26  8:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  0:33 grub rescue read or write sector outside of partition Dale Carstensen
2015-06-26  8:11 ` Andrei Borzenkov [this message]
2015-06-27 22:17   ` Dale Carstensen
2015-06-28  6:01     ` Andrei Borzenkov
2015-06-28 22:54       ` Dale Carstensen
2015-06-26  8:21 ` Fajar A. Nugraha

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=20150626111114.247a6e3a@opensuse.site \
    --to=arvidjaar@gmail.com \
    --cc=dlc@lampinc.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.