All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Gabeler-Lee <cheetah@fastcat.org>
To: NeilBrown <neilb@suse.de>
Cc: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>,
	597563@bugs.debian.org, linux-raid@vger.kernel.org
Subject: Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
Date: Sun, 09 Jan 2011 17:13:10 -0500	[thread overview]
Message-ID: <4D2A32F6.4050304@fastcat.org> (raw)
In-Reply-To: <20110110085735.1c68e425@notabene.brown>

On 1/9/2011 16:57, NeilBrown wrote:
> Simply running
>     mdadm --zero-superblock /dev/sdb
>
> should fix it.
Well, that doesn't work very well: "mdadm: Couldn't open /dev/sdb for write 
- not zeroing" ... strace reveals that mdadm is trying to open it O_EXCL, 
which I presume is why it's not working ... I presume I'd have to reboot to 
single user mode and stop the LVM and possibly MD stuff in order for that to 
work, which might then require booting from a rescue cd to do it.

So I backed up the contents of the end of the disk in case I screwed up, and 
then zerro'd it with dd (nervous nervous).  I double-checked things with 
mdadm --examine to double-check I had cleared the stray superblock and not 
damaged the one in sdb3, and that looks OK

After doing that, the version of grub-probe that was crashing before appears 
to work properly, and the trunk version of grub-probe no longer spits out 
the warning/error.  I then upgraded the debian package to the latest version 
in testing (since I'd been using an old version where I could work around 
the problems), and let it run the grub-install on all 4 disks, and that 
proceeded without errors.  Hooray :)

Thank you folks for your help solving this!

-- 
	-Matt
"Reality is that which, when you stop believing in it, doesn't go away".
                 -- Philip K. Dick
GPG pubkey fingerprint: A57F B354 FD30 A502 795B 9637 3EF1 3F22 A85E 2AD1


  reply	other threads:[~2011-01-09 22:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100920202854.27101.8288.reportbug@cheetah.fastcat.org>
     [not found] ` <4D274FF9.8010004@gmail.com>
     [not found]   ` <alpine.DEB.2.00.1101072241560.25170@cheetah.fastcat.org>
2011-01-08 12:41     ` Bug#597563: grub-common: grub-probe segfaults scanning lvm devices Vladimir 'φ-coder/phcoder' Serbinenko
2011-01-08 22:53       ` Matthew Gabeler-Lee
2011-01-08 23:34         ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-01-08 23:38           ` Matthew Gabeler-Lee
2011-01-08 23:55             ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-01-09  3:09               ` Matthew Gabeler-Lee
2011-01-09 20:55         ` NeilBrown
2011-01-09 21:32           ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-01-09 21:57             ` NeilBrown
2011-01-09 22:13               ` Matthew Gabeler-Lee [this message]
2011-01-09 22:29                 ` NeilBrown

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=4D2A32F6.4050304@fastcat.org \
    --to=cheetah@fastcat.org \
    --cc=597563@bugs.debian.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=phcoder@gmail.com \
    /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.