From: antlists <antlists@youngman.org.uk>
To: Reindl Harald <h.reindl@thelounge.net>, linux-raid@vger.kernel.org
Subject: Re: “root account locked” after removing one RAID1 hard disc
Date: Mon, 30 Nov 2020 13:47:41 +0000 [thread overview]
Message-ID: <20b1b87d-f20d-81e6-efd7-f95e998471b4@youngman.org.uk> (raw)
In-Reply-To: <2fbc2ed0-9d0b-cbd1-7ec9-435633131d7d@thelounge.net>
On 30/11/2020 13:16, Reindl Harald wrote:
>
>
> Am 30.11.20 um 14:11 schrieb antlists:
>> On 30/11/2020 12:13, Reindl Harald wrote:
>>> but i fail to see the difference and to understand why reality and
>>> superblock disagree,
>>
>> In YOUR case the array was degraded BEFORE shutdown. In the OP's case,
>> the array was degraded AFTER shutdown
>
> no, no and no again!
>
> * the array is full opertional
> * smartd fires a warning
Ahhh ... but you said in your previous post(s) "the disk died". Not that
it was just a warning.
> * the machine is shut down
> * after that the drive is replaced
> * so the array get degraded AFTER shutdown
> * at power-on RAID partitions are missing
>
But we've had a post in the last week or so of someone who's array
behaved exactly as I described. So I wonder what's going on ...
I need to get my test system up so I can play with these sort of things...
Cheers,
Wol
next prev parent reply other threads:[~2020-11-30 13:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 8:44 “root account locked” after removing one RAID1 hard disc c.buhtz
2020-11-30 9:27 ` antlists
2020-11-30 10:29 ` c.buhtz
2020-11-30 11:40 ` Wols Lists
2020-11-30 10:31 ` Reindl Harald
2020-11-30 11:10 ` Rudy Zijlstra
2020-11-30 11:18 ` Reindl Harald
2020-11-30 20:06 ` ???root account locked??? " David T-G
2020-11-30 21:57 ` Reindl Harald
2020-11-30 22:06 ` RAID repair script (was "Re: ???root account locked??? after removing one RAID1 hard disc" David T-G
2020-11-30 12:00 ` “root account locked” after removing one RAID1 hard disc Wols Lists
2020-11-30 12:13 ` Reindl Harald
2020-11-30 13:11 ` antlists
2020-11-30 13:16 ` Reindl Harald
2020-11-30 13:47 ` antlists [this message]
2020-11-30 13:53 ` Reindl Harald
2020-11-30 14:46 ` Rudy Zijlstra
2020-11-30 20:05 ` partitions & filesystems (was "Re: ???root account locked??? after removing one RAID1 hard disc") David T-G
2020-11-30 20:51 ` antlists
2020-11-30 21:03 ` Rudy Zijlstra
2020-11-30 21:49 ` Reindl Harald
2020-11-30 22:31 ` antlists
2020-11-30 23:21 ` Reindl Harald
2020-11-30 23:59 ` antlists
2020-11-30 22:04 ` partitions & filesystems David T-G
2020-12-01 8:45 ` partitions & filesystems (was "Re: ???root account locked??? after removing one RAID1 hard disc") c.buhtz
2020-12-01 9:18 ` Rudy Zijlstra
2020-12-01 10:00 ` Wols Lists
2020-12-01 8:41 ` buhtz
2020-12-01 9:13 ` Reindl Harald
2020-12-01 8:42 ` c.buhtz
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=20b1b87d-f20d-81e6-efd7-f95e998471b4@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=h.reindl@thelounge.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 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.