Bugzilla – Bug 1212678
[MicroOS] YaST2 Storage::Exception: "Cannot delete MdContainer"
Last modified: 2023-06-26 09:13:54 UTC
Created attachment 867804 [details] y2logs I was installing openSUSE Aeon (MicroOS Desktop) and got an internal error after typing in my root password and clicking on the button to continue: --- Internal error: Please report a bug with logs. Run save_y2logs to get complete logs. Caller: /mounts/mp_0001/usr/share/YaST2/lib/y2storage/devicegraph.rb:193:in initialize Details: Storage::Exception --- I was able to resolve it by Googling for "cannot delete MdContainer" which appears in the attached logs. The situation is this: my PC was running Windows 10 and has an HDD and Intel Optane (which I believe is essentially an SSD). I replaced Windows with Fedora Workstation a few days ago, repartitioning the HDD but leaving the SSD alone, which GParted said has file system ataraid. I used gdisk to repartition it to be a linux filesystem (8300). That solved the problem and I was able to finish the installation. I guess YaST2 couldn't handle that drive for some reason. This bug may be related but I don't know the tech well enough to say if it's a duplicate: https://bugzilla.opensuse.org/show_bug.cgi?id=1100537
Exact backtrace, reformatted for readability: 2023-06-24 18:51:51 <3> install(4333) [libstorage] MdContainerImpl.cc(add_delete_actions):101 THROW: cannot delete MdContainer 2023-06-24 18:51:51 <3> install(4333) [Ruby] yast/wfm.rb(handle_exception):271 Client /mounts/mp_0001/usr/share/YaST2/clients/partitions_proposal.rb failed with 'Storage::Exception' (Storage::Exception). Backtrace: > ...lib/y2storage/devicegraph.rb:193:in `initialize' > ...lib/y2storage/devicegraph.rb:193:in `new' > ...lib/y2storage/devicegraph.rb:193:in `actiongraph' > ...lib/y2storage/clients/partitions_proposal.rb:117:in `update_state' > ...lib/y2storage/clients/partitions_proposal.rb:56:in `initialize' > ...clients/partitions_proposal.rb:23:in `new' > ...clients/partitions_proposal.rb:23:in `<top (required)>' > .../vendor_ruby/3.2.0/yast/wfm.rb:345:in `eval' > .../vendor_ruby/3.2.0/yast/wfm.rb:345:in `run_client' > .../vendor_ruby/3.2.0/yast/wfm.rb:206:in `call_builtin' > .../vendor_ruby/3.2.0/yast/wfm.rb:206:in `call_builtin_wrapper' > .../vendor_ruby/3.2.0/yast/wfm.rb:195:in `CallFunction' > ...lib/installation/proposal_store.rb:194:in `description_for' > ...lib/installation/proposal_store.rb:622:in `block in modules_help' > ...lib/installation/proposal_store.rb:621:in `each' > ...lib/installation/proposal_store.rb:621:in `each_with_object' > ...lib/installation/proposal_store.rb:621:in `modules_help' > ...lib/installation/proposal_store.rb:82:in `help_text' > ...lib/installation/proposal_runner.rb:779:in `build_dialog' > ...lib/installation/proposal_runner.rb:113:in `run' > ...lib/installation/proposal_runner.rb:39:in `run' > ...clients/inst_proposal.rb:22:in `<top (required)>' > .../vendor_ruby/3.2.0/yast/wfm.rb:345:in `eval' > .../vendor_ruby/3.2.0/yast/wfm.rb:345:in `run_client' > .../vendor_ruby/3.2.0/yast/wfm.rb:206:in `call_builtin' > .../vendor_ruby/3.2.0/yast/wfm.rb:206:in `call_builtin_wrapper' > .../vendor_ruby/3.2.0/yast/wfm.rb:195:in `CallFunction' > ...modules/ProductControl.rb:1306:in `block in RunFrom' > .../vendor_ruby/3.2.0/yast/y2logger.rb:98:in `group' > ...modules/ProductControl.rb:1276:in `RunFrom' > ...modules/ProductControl.rb:1501:in `Run' > ...lib/installation/clients/inst_worker_initial.rb:99:in `main' > ...clients/inst_worker_initial.rb:2:in `<top (required)>' > .../vendor_ruby/3.2.0/yast/wfm.rb:345:in `eval' > .../vendor_ruby/3.2.0/yast/wfm.rb:345:in `run_client' > .../vendor_ruby/3.2.0/yast/wfm.rb:206:in `call_builtin' > .../vendor_ruby/3.2.0/yast/wfm.rb:206:in `call_builtin_wrapper' > .../vendor_ruby/3.2.0/yast/wfm.rb:195:in `CallFunction' > ...lib/installation/clients/installation.rb:92:in `block in main' > ...lib/ui/wizards/layout.rb:186:in `open_wizard' > ...lib/installation/clients/installation.rb:60:in `main' > ...clients/installation.rb:2:in `<top (required)>' > .../vendor_ruby/3.2.0/yast/wfm.rb:345:in `eval' > .../vendor_ruby/3.2.0/yast/wfm.rb:345:in `run_client' > .../vendor_ruby/3.2.0/yast/wfm.rb:206:in `call_builtin' > .../vendor_ruby/3.2.0/yast/wfm.rb:206:in `call_builtin_wrapper' > .../vendor_ruby/3.2.0/yast/wfm.rb:195:in `CallFunction' > /usr/lib/YaST2/bin/y2start:68:in `<main>'
Snippet from storage-inst/01-probed.xml: > <MdContainer> > <sid>45</sid> > <name>/dev/md/imsm0</name> > <sysfs-name>md127</sysfs-name> > <sysfs-path>/devices/virtual/block/md127</sysfs-path> > <region> > <length>0</length> > <block-size>512</block-size> > </region> > <udev-id>md-uuid-4f3f56f7:fd0acf3b:69186c1d:5e3ba31b</udev-id> > <range>256</range> > <md-level>CONTAINER</md-level> > <uuid>4f3f56f7:fd0acf3b:69186c1d:5e3ba31b</uuid> > <metadata>imsm</metadata> > <in-etc-mdadm>false</in-etc-mdadm> > </MdContainer>
2023-06-24 14:49:35 <1> install(4333) [libstorage] MdImpl.cc(activate_mds):395 activate_mds 2023-06-24 14:49:35 <1> install(4333) [libstorage] SystemCmd.cc(execute):203 SystemCmd Executing: /sbin/mdadm --assemble --scan > mdadm: Container /dev/md/imsm0 has been assembled with 1 drive > mdadm: (IMSM): Unsupported attributes : 3000000 > mdadm: Unsupported attributes in IMSM metadata.Arrays activation is blocked. > mdadm: Cannot activate member /md127/1 in /dev/md/imsm0. > mdadm: Cannot activate member /md127/0 in /dev/md/imsm0.
This does not look like a YaST problem: The underlying tools (mdadm) or the kernel do not support that hardware.
Arvin, please have a look. I'd say this problem is on the kernel side.
The problem that the RAIDs cannot be activated looks like a known problem of mdadm (see bug #1194355). *** This bug has been marked as a duplicate of bug 1194355 ***