[Bug 2045885] [NEW] RAID1 drive created by mdamd is not persistent

Thu Dec 7 09:01:57 UTC 2023

Public bug reported:

I installed Ubuntu 22.03.3 on a new PC. I installed mdadm and created a
RAID1 drive, /dev/md0 (I created 3 more RAID1 drives, which all have the
same problem). Reboots always fail, because the RAID dricves do not
exist.

I reinstalled Ubuntu, but the problem is still there.

I can get the system to boot by opening maintenance mode and recreating
the RAID device with 'mdadm --create /dev/md0 --level=mirror --raid-
devices=2 /dev/sda /dev/sdb'.

The problem does not occur on my other older PC, which also has 22.04.3,
after upgrades from older versions of Ubuntu.

Problem 1: RAID drives created with mdadm are supposed to be persistent,
but are not.

Problem 2: A missing RAID drive should not cause boot to fail.

I suspect that the problem might be with the order in which actions are
done during boot, due to dependency issues.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mdadm 4.2-0ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec  7 09:40:03 2023
InstallationDate: Installed on 2023-12-01 (5 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: cannot open /dev/sda: Permission denied
MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed with exit code 1: mdadm: cannot open /dev/sdb: Permission denied
MachineType: Micro-Star International Co., Ltd. MS-7D67
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=86a51952-cb53-4ac0-92b0-8fcdcd875d45 ro quiet splash vt.handoff=7
ProcMounts: Error: [Errno 40] Too many levels of symbolic links: '/proc/mounts'
SourcePackage: mdadm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.26
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.A0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: PRO X670-P WIFI (MS-7D67)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.A0:bd08/10/2023:br5.26:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D67:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROX670-PWIFI(MS-7D67):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7D67
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'

** Affects: mdadm (Ubuntu)
     Importance: Undecided
         Status: New

** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/2045885

Title:
  RAID1 drive created by mdamd is not persistent

Status in mdadm package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 22.03.3 on a new PC. I installed mdadm and created
  a RAID1 drive, /dev/md0 (I created 3 more RAID1 drives, which all have
  the same problem). Reboots always fail, because the RAID dricves do
  not exist.

  I reinstalled Ubuntu, but the problem is still there.

  I can get the system to boot by opening maintenance mode and
  recreating the RAID device with 'mdadm --create /dev/md0
  --level=mirror --raid-devices=2 /dev/sda /dev/sdb'.

  The problem does not occur on my other older PC, which also has
  22.04.3, after upgrades from older versions of Ubuntu.

  Problem 1: RAID drives created with mdadm are supposed to be
  persistent, but are not.

  Problem 2: A missing RAID drive should not cause boot to fail.

  I suspect that the problem might be with the order in which actions
  are done during boot, due to dependency issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mdadm 4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  7 09:40:03 2023
  InstallationDate: Installed on 2023-12-01 (5 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
  MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: cannot open /dev/sda: Permission denied
  MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed with exit code 1: mdadm: cannot open /dev/sdb: Permission denied
  MachineType: Micro-Star International Co., Ltd. MS-7D67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=86a51952-cb53-4ac0-92b0-8fcdcd875d45 ro quiet splash vt.handoff=7
  ProcMounts: Error: [Errno 40] Too many levels of symbolic links: '/proc/mounts'
  SourcePackage: mdadm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2023
  dmi.bios.release: 5.26
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.A0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: PRO X670-P WIFI (MS-7D67)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.A0:bd08/10/2023:br5.26:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D67:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROX670-PWIFI(MS-7D67):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7D67
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2045885/+subscriptions