Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: bruce.korb+reply@gmail.com, linux-raid@vger.kernel.org
Subject: Re: Trying to rescue a RAID-1 array
Date: Thu, 31 Mar 2022 18:06:53 +0100	[thread overview]
Message-ID: <e3573002-05f3-3110-62a6-e704385f877f@youngman.org.uk> (raw)
In-Reply-To: <CAKRnqN+_=U58dT5bvgWJ1DgyEuhjsbmCuDL+xOLxmcuG1ML4qg@mail.gmail.com>

On 31/03/2022 17:44, Bruce Korb wrote:
> I moved the two disks from a cleanly shut down system that could not
> reboot and could not
> be upgraded to a new OS release. So, I put them in.a new box and did an install.
> The installation recognized them as a RAID and decided that the
> partitions needed a
> new superblock of type RAID-0.

That's worrying, did it really write a superblock?

> Since these data have never been
> remounted since the
> shutdown on the original machine, I am hoping I can change the RAID
> type and mount it
> so as to recover my. .ssh and .thunderbird (email) directories. The
> bulk of the data are
> backed up (assuming no issues with the full backup of my critical
> data), but rebuilding
> and redistributing the .ssh directory would be a particular nuisance.
> 
> SO: what are my options? I can't find any advice on how to tell mdadm
> that the RAID-0 partitions
> really are RAID-1 partitions. Last gasp might be to "mdadm --create"
> the RAID-1 again, but there's
> a lot of advice out there saying that it really is the last gasp
> before giving up. :)
> 

https://raid.wiki.kernel.org/index.php/Asking_for_help

Especially lsdrv. That tells us a LOT about your system.

What was the filesystem on your raid? Hopefully it's as simple as moving 
the "start of partition", breaking the raid completely, and you can just 
mount the filesystem.

What really worries me is how and why it both recognised it as a raid, 
then thought it needed to be converted to raid-0. That just sounds wrong 
on so many levels. Did you let it mess with your superblocks? I hope you 
said "don't touch those drives"?

Cheers,
Wol

  reply	other threads:[~2022-03-31 17:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 16:44 Trying to rescue a RAID-1 array Bruce Korb
2022-03-31 17:06 ` Wols Lists [this message]
2022-03-31 18:14   ` Bruce Korb
2022-03-31 21:34     ` Wols Lists
2022-04-01 17:59       ` Bruce Korb
2022-04-01 18:21         ` Bruce Korb
2022-04-01 19:45           ` Wol
2022-04-01 20:23             ` Bruce Korb
2022-04-01 21:02               ` Wol
2022-04-01 21:24                 ` Bruce Korb
2022-04-01 21:33                   ` Wol
2022-04-20  8:40           ` Need to move RAID1 with mounted partition Leslie Rhorer
2022-04-20  8:55             ` Roman Mamedov
2022-04-20  9:21               ` Leslie Rhorer
2022-04-20 11:08             ` Andy Smith
2022-04-20 12:07               ` Pascal Hambourg
2022-04-20 12:24                 ` Leslie Rhorer
2022-04-20 12:16               ` Leslie Rhorer

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=e3573002-05f3-3110-62a6-e704385f877f@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=bruce.korb+reply@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox