From: raid <raid@electrons.cloud>
To: Yu Kuai <yukuai1@huaweicloud.com>, Wol <antlists@youngman.org.uk>,
linux-raid@vger.kernel.org
Cc: Phil Turmel <philip@turmel.org>, NeilBrown <neilb@suse.com>,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: RAID5 Phantom Drive Appeared while Reshaping Four Drive Array (HARDLOCK)
Date: Mon, 22 May 2023 01:56:05 -0500 [thread overview]
Message-ID: <b18cfe9f6f8e44285aa4ab4300e0c0e1b863fe08.camel@electrons.cloud> (raw)
In-Reply-To: <9b22d5ce-5f1b-0fc8-acdc-02c2e8cefa55@huaweicloud.com>
Hi,
Thanks for the guidance as the current state has at least changed somewhat.
BTW Sorry about Life getting in the way of tech. =) Reason for my delayed response.
-sudo mdadm -I /dev/sdc1
mdadm: /dev/sdc1 attached to /dev/md480, not enough to start (1).
-sudo mdadm -D /dev/md480
/dev/md480:
Version : 1.2
Raid Level : raid0
Total Devices : 1
Persistence : Superblock is persistent
State : inactive
Working Devices : 1
Delta Devices : 1, (-1->0)
New Level : raid5
New Layout : left-symmetric
New Chunksize : 512K
Name : GRANDSLAM:480
UUID : 20211025:02005a7a:5a7abeef:cafebabe
Events : 78714
Number Major Minor RaidDevice
- 8 33 - /dev/sdc1
-sudo mdadm -I /dev/sdd1
mdadm: /dev/sdd1 attached to /dev/md480, not enough to start (2).
-sudo mdadm -D /dev/md480
/dev/md480:
Version : 1.2
Raid Level : raid0
Total Devices : 2
Persistence : Superblock is persistent
State : inactive
Working Devices : 2
Delta Devices : 1, (-1->0)
New Level : raid5
New Layout : left-symmetric
New Chunksize : 512K
Name : GRANDSLAM:480
UUID : 20211025:02005a7a:5a7abeef:cafebabe
Events : 78714
Number Major Minor RaidDevice
- 8 49 - /dev/sdd1
- 8 33 - /dev/sdc1
-sudo mdadm -I /dev/sde1
mdadm: /dev/sde1 attached to /dev/md480, not enough to start (2).
-sudo mdadm -D /dev/md480
/dev/md480:
Version : 1.2
Raid Level : raid0
Total Devices : 3
Persistence : Superblock is persistent
State : inactive
Working Devices : 3
Delta Devices : 1, (-1->0)
New Level : raid5
New Layout : left-symmetric
New Chunksize : 512K
Name : GRANDSLAM:480
UUID : 20211025:02005a7a:5a7abeef:cafebabe
Events : 78712
Number Major Minor RaidDevice
- 8 65 - /dev/sde1
- 8 49 - /dev/sdd1
- 8 33 - /dev/sdc1
-sudo mdadm -I /dev/sdf1
mdadm: /dev/sdf1 attached to /dev/md480, not enough to start (3).
-sudo mdadm -D /dev/md480
/dev/md480:
Version : 1.2
Raid Level : raid0
Total Devices : 4
Persistence : Superblock is persistent
State : inactive
Working Devices : 4
Delta Devices : 1, (-1->0)
New Level : raid5
New Layout : left-symmetric
New Chunksize : 512K
Name : GRANDSLAM:480
UUID : 20211025:02005a7a:5a7abeef:cafebabe
Events : 78714
Number Major Minor RaidDevice
- 8 81 - /dev/sdf1
- 8 65 - /dev/sde1
- 8 49 - /dev/sdd1
- 8 33 - /dev/sdc1
-sudo mdadm -R /dev/md480
mdadm: failed to start array /dev/md480: Input/output error
---
NOTE: Of additional interest...
---
-sudo mdadm -D /dev/md480
/dev/md480:
Version : 1.2
Creation Time : Tue Oct 26 14:06:53 2021
Raid Level : raid5
Used Dev Size : 18446744073709551615
Raid Devices : 5
Total Devices : 3
Persistence : Superblock is persistent
Update Time : Thu May 4 14:39:03 2023
State : active, FAILED, Not Started
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Consistency Policy : unknown
Delta Devices : 1, (4->5)
Name : GRANDSLAM:480
UUID : 20211025:02005a7a:5a7abeef:cafebabe
Events : 78714
Number Major Minor RaidDevice State
- 0 0 0 removed
- 0 0 1 removed
- 0 0 2 removed
- 0 0 3 removed
- 0 0 4 removed
- 8 81 3 sync /dev/sdf1
- 8 49 1 sync /dev/sdd1
- 8 33 0 sync /dev/sdc1
---
-watch -c -d -n 1 cat /proc/mdstat
---
Every 1.0s: cat /proc/mdstat OAK2023: Mon May 22 01:48:24 2023
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md480 : inactive sdf1[4] sdd1[1] sdc1[0]
46877239294 blocks super 1.2
unused devices: <none>
---
Hopeful that is some progress towards an array start? It's definately unexpected output to me.
I/O Error starting md480
Thanks!
SA
On Thu, 2023-05-18 at 11:15 +0800, Yu Kuai wrote:
> I have no idle why other disk shows that device 2 is missing, and what
> is device 4.
>
> Anyway, can you try the following?
>
> mdadm -I /dev/sdc1
> mdadm -D /dev/mdxxx
>
> mdadm -I /dev/sdd1
> mdadm -D /dev/mdxxx
>
> mdadm -I /dev/sde1
> mdadm -D /dev/mdxxx
>
> mdadm -I /dev/sdf1
> mdadm -D /dev/mdxxx
>
> If above works well, you can try:
>
> mdadm -R /dev/mdxxx, and see if the array can be started.
>
> Thanks,
> Kuai
next prev parent reply other threads:[~2023-05-22 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 13:26 RAID5 Phantom Drive Appeared while Reshaping Four Drive Array (HARDLOCK) raid
2023-05-17 23:45 ` Wol
2023-05-18 3:15 ` Yu Kuai
2023-05-22 6:56 ` raid [this message]
2023-05-22 7:51 ` Yu Kuai
2023-05-22 19:50 ` raid
2023-05-22 23:50 ` Roger Heflin
2023-05-23 5:04 ` raid
2023-05-22 7:20 ` raid
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=b18cfe9f6f8e44285aa4ab4300e0c0e1b863fe08.camel@electrons.cloud \
--to=raid@electrons.cloud \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=philip@turmel.org \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.com \
/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