All of lore.kernel.org
 help / color / mirror / Atom feed
From: RJ Marquette <rjm1@yahoo.com>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Requesting help recovering my array
Date: Wed, 24 Jan 2024 18:06:21 +0000 (UTC)	[thread overview]
Message-ID: <2058198167.201827.1706119581305@mail.yahoo.com> (raw)
In-Reply-To: <006fe0ca-a2fb-4ccd-b4d4-c01945d72661@penguinpee.nl>

Other than sdc (as you noted), the other array drives come back like this:

root@jackie:/etc/mdadm# mdadm --examine /dev/sda
/dev/sda:
  MBR Magic : aa55
Partition[0] :   4294967295 sectors at            1 (type ee)

root@jackie:/etc/mdadm# mdadm --examine /dev/sda1
mdadm: No md superblock detected on /dev/sda1.


Trying your other suggestion:
root@jackie:/etc/mdadm# mdadm --assemble /dev/md0 /dev/sdb1 /dev/sde1 /dev/sdf1 /dev/sdg1
mdadm: no recogniseable superblock on /dev/sdb1
mdadm: /dev/sdb1 has no superblock - assembly aborted

root@jackie:/etc/mdadm# mdadm --assemble /dev/md0 /dev/sdb /dev/sde /dev/sdf /dev/sdg
mdadm: Cannot assemble mbr metadata on /dev/sdb
mdadm: /dev/sdb has no superblock - assembly aborted


Basically I've tried everything here:  https://raid.wiki.kernel.org/index.php/Linux_Raid

The impression I'm getting here is that we aren't really sure what the issue is.  I think tonight I'll play with some of the BIOS settings and see if there's something in there.  If not I'll swap back to the old motherboard and see what happens.

Thanks.
--RJ





On Wednesday, January 24, 2024 at 12:06:26 PM EST, Sandro <lists@penguinpee.nl> wrote: 





On 24-01-2024 13:17, RJ Marquette wrote:

> When I try the command you suggested below, I get:
> root@jackie:/etc/mdadm# mdadm --assemble /dev/md0 /dev/sd{a,b,e,f,g}1
> mdadm: no recogniseable superblock on /dev/sda1
> mdadm: /dev/sda1 has no superblock - assembly aborted


Try `mdadm --examine` on every partition / drive that is giving you 
trouble. Maybe you are remembering things wrong and the raid device is 
/dev/sda and not /dev/sda1.

You can also go through the entire list (/dev/sd*), you posted earlier. 
There's no harm in running the command. It will look for the superblock 
and tell you what has been found. This could provide the information you 
need to assemble the array.

Alternatively, leave sda1 out of the assembly and see if mdadm will be 
able to partially assemble the array.

-- Sandro

  reply	other threads:[~2024-01-24 18:06 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <432300551.863689.1705953121879.ref@mail.yahoo.com>
2024-01-22 19:52 ` Requesting help recovering my array RJ Marquette
2024-01-22 21:39   ` Reindl Harald
2024-01-22 22:13     ` RJ Marquette
2024-01-22 23:49       ` Reindl Harald
2024-01-23  0:09         ` RJ Marquette
2024-01-23  1:52           ` RJ Marquette
2024-01-23 16:06             ` David Niklas
2024-01-23 16:09               ` RJ Marquette
2024-01-23 16:16               ` RJ Marquette
2024-01-23 22:50                 ` Sandro
2024-01-24  0:59                   ` RJ Marquette
     [not found]                   ` <d051abe3-af97-47a4-a087-432c91beb57e@yahoo.com>
2024-01-24  9:11                     ` Sandro
2024-01-24  3:19                 ` David Niklas
2024-01-24 12:17                   ` RJ Marquette
2024-01-24 17:06                     ` Sandro
2024-01-24 18:06                       ` RJ Marquette [this message]
2024-01-24 21:20                         ` Roger Heflin
2024-01-24 21:31                           ` RJ Marquette
2024-01-24 21:44                             ` Roger Heflin
2024-01-24 22:21                               ` Robin Hill
2024-01-24 22:37                                 ` Roger Heflin
2024-01-25  1:13                               ` RJ Marquette
2024-01-25  1:57                                 ` Roger Heflin
2024-01-25  9:49                                   ` Pascal Hambourg
2024-01-25 11:49                                     ` RJ Marquette
2024-01-25 14:57                                       ` Pascal Hambourg
2024-01-25 15:08                                         ` RJ Marquette
2024-01-25 17:43                                           ` Roger Heflin
2024-01-25 18:33                                             ` RJ Marquette
2024-01-25 22:37                                               ` Roger Heflin
2024-01-25 22:53                                                 ` Roger Heflin
2024-01-25 23:00                                                   ` Roger Heflin
2024-01-26 15:15                                                     ` RJ Marquette
2024-01-26 15:25                                                       ` Reindl Harald
2024-01-26 16:03                                                       ` RJ Marquette
2024-01-26 23:45                                                         ` RJ Marquette
2024-01-27  8:41                                                           ` Pascal Hambourg
2024-01-27 12:30                                                             ` RJ Marquette
2024-02-19 20:48                                                           ` Pascal Hambourg
2024-01-25 17:06                                 ` Reindl Harald

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=2058198167.201827.1706119581305@mail.yahoo.com \
    --to=rjm1@yahoo.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 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.