From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] SparesMissing event on /dev/md4:nsa320 (fwd)
Date: Thu, 9 Jul 2020 16:02:33 +0200 [thread overview]
Message-ID: <20200709140232.GA12119@tansi.org> (raw)
In-Reply-To: <nycvar.QRO.7.76.2007090722000.23709@tehzcl5.tehzcl-arg>
Hi,
your array looks fine. But this is not a topic for the
cryptsetup mailing list. Please use Debian support
for this.
Regards,
Arno
On Thu, Jul 09, 2020 at 14:25:05 CEST, grumpy@mailfence.com wrote:
> i upgraded an old nas device from debian 8 to 9 and started get'n this message
> what's the dang deal :)
> i don't have any spares
>
>
> root@nsa320:~# mdadm -D /dev/md4
> /dev/md4:
> Version : 0.90
> Creation Time : Tue Mar 5 13:16:13 2013
> Raid Level : raid1
> Array Size : 1932713920 (1843.18 GiB 1979.10 GB)
> Used Dev Size : 1932713920 (1843.18 GiB 1979.10 GB)
> Raid Devices : 2
> Total Devices : 2
> Preferred Minor : 4
> Persistence : Superblock is persistent
>
> Update Time : Thu Jul 9 06:13:34 2020
> State : clean
> Active Devices : 2
> Working Devices : 2
> Failed Devices : 0
> Spare Devices : 0
>
> UUID : dc6cc046:ef4012cc:ecea512d:0eb28517 (local to host nsa320)
> Events : 0.99097
>
> Number Major Minor RaidDevice State
> 0 8 20 0 active sync /dev/sdb4
> 1 8 4 1 active sync /dev/sda4
>
>
>
> ---------- Forwarded message ----------
> Date: Wed, 8 Jul 2020 18:20:14 -0500
> From: mdadm monitoring <root@localhost.localdomain>
> To: root@nsa320.grumpy-net
> Subject: SparesMissing event on /dev/md4:nsa320
>
> This is an automatically generated mail message from mdadm
> running on nsa320
>
> A SparesMissing event had been detected on md device /dev/md4.
>
> Faithfully yours, etc.
>
> P.S. The /proc/mdstat file currently contains the following:
>
> Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
> md2 : active raid1 sda2[1] sdb2[0]
> 19573696 blocks [2/2] [UU]
>
> md4 : active raid1 sda4[1] sdb4[0]
> 1932713920 blocks [2/2] [UU]
>
> md3 : active raid1 sda3[1] sdb3[0]
> 975808 blocks [2/2] [UU]
>
> unused devices: <none>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> https://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
prev parent reply other threads:[~2020-07-09 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 12:25 [dm-crypt] SparesMissing event on /dev/md4:nsa320 (fwd) grumpy
2020-07-09 14:02 ` Arno Wagner [this message]
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=20200709140232.GA12119@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).