All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Heflin <rogerheflin@gmail.com>
To: Alexander Shenkin <al@shenkin.org>
Cc: antlists <antlists@youngman.org.uk>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Raid-6 won't boot
Date: Sat, 28 Mar 2020 08:36:32 -0500	[thread overview]
Message-ID: <CAAMCDedj7TQAAGzSfQgAftKSmrjNmzHgQUs-X2mQZyFPG62_-A@mail.gmail.com> (raw)
In-Reply-To: <1f393884-dc48-c03e-f734-f9880d9eed96@shenkin.org>

Try this grep:
dmesg | grep "md/raid", if that returns nothing if you can just send
the entire dmesg.

On Sat, Mar 28, 2020 at 2:47 AM Alexander Shenkin <al@shenkin.org> wrote:
>
> Thanks Roger.  dmesg has nothing in it referring to md126 or md127....
> any other thoughts on how to investigate?
>
> thanks,
> allie
>
> On 3/27/2020 3:55 PM, Roger Heflin wrote:
> > A non-assembled array always reports raid1.
> >
> > I would run "dmesg | grep md126" to start with and see what it reports it saw.
> >
> > On Fri, Mar 27, 2020 at 10:29 AM Alexander Shenkin <al@shenkin.org> wrote:
> >>
> >> Thanks Wol,
> >>
> >> Booting in SystemRescueCD and looking in /proc/mdstat, two arrays are
> >> reported.  The first (md126) in reported as inactive with all 7 disks
> >> listed as spares.  The second (md127) is reported as active
> >> auto-read-only with all 7 disks operational.  Also, the only
> >> "personality" reported is Raid1.  I could go ahead with your suggestion
> >> of mdadm --stop array and then mdadm --assemble, but I thought the
> >> reporting of just the Raid1 personality was a bit strange, so wanted to
> >> check in before doing that...
> >>
> >> Thanks,
> >> Allie
> >>
> >> On 3/26/2020 10:00 PM, antlists wrote:
> >>> On 26/03/2020 17:07, Alexander Shenkin wrote:
> >>>> I surely need to boot with a rescue disk of some sort, but from there,
> >>>> I'm not sure exactly when I should do.  Any suggestions are very welcome!
> >>>
> >>> Okay. Find a liveCD that supports raid (hopefully something like
> >>> SystemRescueCD). Make sure it has a very recent kernel and the latest
> >>> mdadm.
> >>>
> >>> All being well, the resync will restart, and when it's finished your
> >>> system will be fine. If it doesn't restart on its own, do an "mdadm
> >>> --stop array", followed by an "mdadm --assemble"
> >>>
> >>> If that doesn't work, then
> >>>
> >>> https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn
> >>>
> >>> Cheers,
> >>> Wol

  reply	other threads:[~2020-03-28 13:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 17:07 Raid-6 won't boot Alexander Shenkin
2020-03-26 22:00 ` antlists
2020-03-27 15:27   ` Alexander Shenkin
2020-03-27 15:55     ` Roger Heflin
2020-03-28  7:47       ` Alexander Shenkin
2020-03-28 13:36         ` Roger Heflin [this message]
     [not found]           ` <c8185f80-837e-9654-ee19-611a030a0d54@shenkin.org>
2020-03-30 15:53             ` Roger Heflin
2020-03-30 16:13               ` Alexander Shenkin
2020-03-30 17:21                 ` Roger Heflin
2020-03-30 20:05                   ` Alexander Shenkin
2020-03-30 20:45                     ` Roger Heflin
2020-03-31  0:16                       ` antlists
2020-03-31 10:08                       ` Alexander Shenkin
2020-03-31 13:53                         ` Roger Heflin
2020-03-31 14:28                           ` Alexander Shenkin
2020-03-31 14:43                             ` Roger Heflin
2020-03-31 16:03                               ` Alexander Shenkin
2020-03-31 16:13                         ` Alexander Shenkin
2020-03-31 16:16                           ` Roger Heflin
2020-03-31 16:20                             ` Alexander Shenkin
2020-03-31 16:30                               ` Roger Heflin
2020-03-28 10:47     ` antlists

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=CAAMCDedj7TQAAGzSfQgAftKSmrjNmzHgQUs-X2mQZyFPG62_-A@mail.gmail.com \
    --to=rogerheflin@gmail.com \
    --cc=al@shenkin.org \
    --cc=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.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.