Linux RAID subsystem development
 help / color / mirror / Atom feed
From: David Niklas <simd@vfemail.net>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Ran ./test on mdadm source before running raid6check. Now array is borked.
Date: Mon, 4 Aug 2025 22:21:02 -0400	[thread overview]
Message-ID: <20250804222102.467e1315@Zen-II-x12> (raw)

Hello,
I managed to find the raid6check utility here:
https://salsa.debian.org/debian/mdadm

I downloaded and compiled the code, ran mdadm --stop on my array, and
ran ./test . Many of the tests failed, but more concerning is that I
cannot restart my array.

# mdadm --verbose --assemble /dev/md0
mdadm: looking for devices for /dev/md0
mdadm: /dev/sda has wrong uuid.
mdadm: No super block found on /dev/sdb (Expected magic a92b4efc, got
00000000) mdadm: no RAID superblock on /dev/sdb
mdadm: No super block found on /dev/sdc (Expected magic a92b4efc, got
00000000) mdadm: no RAID superblock on /dev/sdc
mdadm: No super block found on /dev/sdd (Expected magic a92b4efc, got
00000000) mdadm: no RAID superblock on /dev/sdd
mdadm: No super block found on /dev/sde (Expected magic a92b4efc, got
00000000) mdadm: no RAID superblock on /dev/sde

What do I do now?
If the test utility is so dangerous, why is there no warning to pull your
HDDs before you run ./test? Like, make test normally doesn't bork
anything.

Thanks!

             reply	other threads:[~2025-08-05  2:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05  2:21 David Niklas [this message]
2025-08-05  4:57 ` Ran ./test on mdadm source before running raid6check. Now array is borked simd

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=20250804222102.467e1315@Zen-II-x12 \
    --to=simd@vfemail.net \
    --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