Bug 2357128 - device /dev/md/raid0p2 does not exist
Summary: device /dev/md/raid0p2 does not exist
Keywords:
Status: CLOSED DUPLICATE of bug 2357214
Alias: None
Product: Fedora
Classification: Fedora
Component: cockpit
Version: 42
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Pitt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F42FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2025-04-03 07:32 UTC by Kamil Páral
Modified: 2025-04-04 06:16 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-04-04 06:16:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda.log (7.03 KB, text/plain)
2025-04-03 07:33 UTC, Kamil Páral
no flags Details
dbus.log (3.91 KB, text/plain)
2025-04-03 07:34 UTC, Kamil Páral
no flags Details
packaging.log (4.35 KB, text/plain)
2025-04-03 07:34 UTC, Kamil Páral
no flags Details
program.log (1.68 KB, text/plain)
2025-04-03 07:34 UTC, Kamil Páral
no flags Details
storage.log (494.46 KB, text/plain)
2025-04-03 07:34 UTC, Kamil Páral
no flags Details
journal.txt (1.47 MB, text/plain)
2025-04-03 07:34 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2025-04-03 07:32:33 UTC
Description of problem:
Anaconda crashed while starting installation with error:
> blivet.errors.FSError: device /dev/md/raid0p2 does not exist

I was trying to verify bug 2354805.


Version-Release number of selected component (if applicable):
anaconda-42.27.11-1.fc42.x86_64
anaconda-webui-32-1.fc42.noarch
cockpit-storaged-336.2-1.fc42.noarch


How reproducible:
unknown

Steps to Reproduce:
I believe I did this:
1. follow the reproducer in bug 2354805 comment 0
2. that was correctly rejected as invalid layout
3. return back to anaconda ("continue installation")
4. return back to storage editor
5. delete MDRAID0 and create MDRAID1 instead (I believe I kept the same "raid0" name for the new device)
6. create /boot and / on MDRAID1
7. go back to anaconda (layout valid)
8. start installation, crashed

Comment 1 Kamil Páral 2025-04-03 07:33:41 UTC
Oh, and I noticed, that at step 7, when validating layout, the partitions under MDRAID1 seemed to disappear from the cockpit view in the background (under the layout validation popup). I considered it just a graphical glitch.

Comment 2 Kamil Páral 2025-04-03 07:33:58 UTC
Created attachment 2083190 [details]
anaconda.log

Comment 3 Kamil Páral 2025-04-03 07:34:01 UTC
Created attachment 2083191 [details]
dbus.log

Comment 4 Kamil Páral 2025-04-03 07:34:05 UTC
Created attachment 2083192 [details]
packaging.log

Comment 5 Kamil Páral 2025-04-03 07:34:08 UTC
Created attachment 2083193 [details]
program.log

Comment 6 Kamil Páral 2025-04-03 07:34:11 UTC
Created attachment 2083194 [details]
storage.log

Comment 7 Kamil Páral 2025-04-03 07:34:15 UTC
Created attachment 2083195 [details]
journal.txt

Comment 8 Kamil Páral 2025-04-03 07:37:15 UTC
Proposing as a blocker:
https://fedoraproject.org/wiki/Fedora_42_Final_Release_Criteria#Disk_layouts

Comment 9 Katerina Koukiou 2025-04-03 15:10:38 UTC
This is caused by https://bugzilla.redhat.com/show_bug.cgi?id=2357214

Comment 10 Adam Williamson 2025-04-03 21:42:06 UTC
Can we close this as a dupe of that, then?

Comment 11 Kamil Páral 2025-04-04 06:16:54 UTC

*** This bug has been marked as a duplicate of bug 2357214 ***


Note You need to log in before you can comment on or make changes to this bug.