Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-123746

RHEL 10.1 enters emergency mode when the server replace another 7mm Kit during test

Linking RHIVOS CVEs to...Migration: Automation ...RHELPRIO AssignedTeam ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • None
    • anaconda
    • None
    • None
    • None
    • rhel-anaconda
    • 0
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      What were you trying to do that didn't work?

      we do the raid kit test using RHEL10.1, but os enters emergency mode.

      What is the impact of this issue to you?

      Test failed due to cannot mount home uuid.

      Please provide the package NVR for which the bug is seen:

      How reproducible is this bug?:

      For the 7mm NVMe device, the foreign status should trigger by below step.
      1. Create a VD1 (PD A & B HDD) on Marvell/Broadcom RAID controller 1 and install os.
      2. Power off system, remove all the NVMe M.2 SSD.
      3. Put the VD1 on another Marvell/Broadcom RAID controller 2.
      4. Check the VD will be showed foreign status on uEFI.
      5. Login to XCC -> Server Configuration -> RAID Setup -> Enable edit mode -> Controller Actions -> Manage foreign configuration.
      6. Import foreign configuration, check it can be imported successfully.
      7. Reboot the system.
      8. VD1 will show on XCC and uEFI.

      9.The system enters emergency mode after reboot.

      OS version: RHEL-10.1-20251017.0-x86_64-dvd1.iso/RHEL-10.1-20251009.3-x86_64-dvd1.iso have same issue

      Expected results

      Step 7 reboot the system will enter os successfully

      Actual results

      The os enters emergency mode.

      Additional info:

      1.we test RHEL10 and RHEL10.1, they all have this problem.

      2.Add the "rd.lvm.lv=rhel/home" on grub, os will boot successfully, otherwise it will report follwing timeout message.

      Oct 23 02:13:49 localhost systemd[1]: dev-disk-by\x2duuid-e8970760\x2d08d9\x2d4fe2\x2db1c2\x2d941342045321.device: Job dev-disk-by\x2duuid-e8970760\x2d08d9\x2d4fe2\x2db1c2\x2d941342045321.device/start timed out.
      Oct 23 02:13:49 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-e8970760\x2d08d9\x2d4fe2\x2db1c2\x2d941342045321.device - /dev/disk/by-uuid/e8970760-08d9-4fe2-b1c2-941342045321.

      3.I checked the home uuid under the bad case and good case, the uuid is right, didn't change.

      4.add the timeout parameter on /etc/fstab doesn't work

       

      Could you give some suggestion about how to trace the root cause. I will put the jouranlctl log files on attachment.

              anaconda-maint-list anaconda-maint-list
              wangdong28 wang dong
              Lenovo Confidential Group
              anaconda-maint-list anaconda-maint-list
              Release Test Team Release Test Team
              Sagar Dubewar Sagar Dubewar
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: