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.
I alse encountered this issue on RHEL7.3 with kernel-3.10.0-514.el7,but it prompt that device-mapper target type "raid45" is not in the kernel.
# dmraid -s
*** Group superset isw_degjjibgb
--> Subset
name : isw_degjjibgb_Raid5
size : 3907031296
stride : 128
type : raid5_la
status : ok
subsets: 0
devs : 3
spares : 0
# dmraid -ay
ERROR: device-mapper target type "raid45" is not in the kernel
RAID set "isw_degjjibgb_Raid5" was not activated
ERROR: device "isw_degjjibgb_Raid5" could not be found
# dmraid -tay
isw_degjjibgb_Raid5: 0 3907031296 raid45 core 2 131072 nosync raid5_la 1 128 3 -1 /dev/sdd 0 /dev/sdc 0 /dev/sdb 0
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/
Description of problem: After the reboot, isw dmraid raid1 can't be activated Version-Release number of selected component (if applicable): RHEL6.8 with kernel-2.6.32-642.el6.x86_64 # rpm -qa dmraid* dmraid-events-1.0.0.rc16-11.el6.x86_64 dmraid-1.0.0.rc16-11.el6.x86_64 How reproducible: Always Steps to Reproduce: 1 # dmraid -f isw -C Raid1 --type 1 --disk "/dev/sdb /dev/sdc" Create a RAID set with ISW metadata format RAID name: Raid1 RAID type: RAID1 RAID size: 111G (234432094 blocks) DISKS: /dev/sdb, /dev/sdc, About to create a RAID set with the above settings. Continue ? [y/n] :y # dmraid -s *** Group superset isw_ceggiagge --> Subset name : isw_ceggiagge_Raid1 size : 234432000 stride : 128 type : mirror status : ok subsets: 0 devs : 2 spares : 0 [root@dhcp-12-134 Desktop]# dmraid -r /dev/sdc: isw, "isw_ceggiagge", GROUP, ok, 234441646 sectors, data@ 0 /dev/sdb: isw, "isw_ceggiagge", GROUP, ok, 234441646 sectors, data@ 0 # dmraid -tay isw_ceggiagge_Raid1: 0 234432000 mirror core 2 131072 nosync 2 /dev/sdb 0 /dev/sdc 0 1 handle_errors ======== reboot ============= # dmraid -s *** Group superset isw_ceggiagge --> Subset name : isw_ceggiagge_Raid1 size : 234432000 stride : 128 type : mirror status : ok subsets: 0 devs : 2 spares : 0 # dmraid -ay RAID set "isw_ceggiagge_Raid1" was not activated ERROR: device "isw_ceggiagge_Raid1" could not be found # dmraid -r /dev/sdc: isw, "isw_ceggiagge", GROUP, ok, 234441646 sectors, data@ 0 /dev/sdb: isw, "isw_ceggiagge", GROUP, ok, 234441646 sectors, data@ 0 # dmraid -ay RAID set "isw_ceggiagge_Raid1" was not activated ERROR: device "isw_ceggiagge_Raid1" could not be found Actual results: Expected results: dmraid -ay was activated Additional info: