Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Hi all,
[root@localhost ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 477G 0 disk
└─sda1 8:1 0 477G 0 part
nvme0n1 259:0 0 119.2G 0 disk
├─nvme0n1p1 259:1 0 1G 0 part /boot
├─nvme0n1p2 259:2 0 11.7G 0 part [SWAP]
├─nvme0n1p3 259:3 0 50G 0 part /
├─nvme0n1p4 259:4 0 1G 0 part <<<<<<<<<<<<<<<<<<
└─nvme0n1p5 259:5 0 2G 0 part <<<<<<<<<<<<<<<<<<
[root@localhost ~]# rpm -q mdadm
mdadm-4.1-10.el8.x86_64
[root@localhost ~]# mdadm --create /dev/md/r0 --level=0 --chunk 128 --raid-devices=2 /dev/nvme0n1p4 /dev/nvme0n1p5 --run --force
mdadm: partition table exists on /dev/nvme0n1p4
mdadm: partition table exists on /dev/nvme0n1p4 but will be lost or
meaningless after creating array
mdadm: Defaulting to version 1.2 metadata
mdadm: RUN_ARRAY failed: Unknown error 524
[root@localhost ~]# mdadm -D /dev/md/r0
mdadm: cannot open /dev/md/r0: No such file or directory
[root@localhost ~]#
----------------------------------------------------------------
[root@localhost ~]# rpm -Uvh mdadm-4.1-12.el8.x86_64.rpm
[root@localhost ~]# rpm -q mdadm
mdadm-4.1-12.el8.x86_64
[root@localhost ~]# mdadm --create /dev/md/r0 --level=0 --chunk 128 --raid-devices=2 /dev/nvme0n1p4 /dev/nvme0n1p5 --run --force
mdadm: /dev/nvme0n1p4 appears to be part of a raid array:
level=raid0 devices=2 ctime=Thu Mar 5 22:25:14 2020
mdadm: partition table exists on /dev/nvme0n1p4 but will be lost or
meaningless after creating array
mdadm: /dev/nvme0n1p5 appears to be part of a raid array:
level=raid0 devices=2 ctime=Thu Mar 5 22:25:14 2020
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md/r0 started.
[root@localhost ~]#
[root@localhost ~]# mdadm -D /dev/md/r0
/dev/md/r0:
Version : 1.2
Creation Time : Thu Mar 5 22:26:09 2020
Raid Level : raid0
Array Size : 3141632 (3.00 GiB 3.22 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Thu Mar 5 22:26:09 2020
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Layout : original
Chunk Size : 128K
Consistency Policy : none
Name : localhost.localdomain:r0 (local to host localhost.localdomain)
UUID : 47360c7b:ad887057:6f28b9c8:ff01e24d
Events : 0
Number Major Minor RaidDevice State
0 259 4 0 active sync /dev/nvme0n1p4
1 259 5 1 active sync /dev/nvme0n1p5
[root@localhost ~]#
I think it's OK now
BR
Fine
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:1890