On 12/27/23 17:36, Sandro wrote:
I'll try with a F39 live ISO as well. If nothing else, it could confirm the issue to be with/in F39.
I did that. Right after boot only one of the arrays was assembled. In /proc/mdstat is was listed as "active (auto-read-only)" and the component devices matched with what is known on my system as md54.
No entry in the journal regarding any of the other arrays. No attempted assembly. Nothing.
I stopped the array and ran `mdadm --assemble --verbose --scan --no-degraded` and all arrays were assembled without any issues. In the verbose output of the command `mdadm` told me:
mdadm: No super block found on /dev/sda2 (Expected magic a92b4efc, got 6d746962)
That was repeated for all the component devices of md1 and md5. For drives / partitions not being component devices it reported:
mdadm: No super block found on /dev/sda1 (Expected magic a92b4efc, got 00000000)
instead. In contrast, about the component devices of md54, `mdadm` had the following to report:
mdadm: /dev/sda4 is identified as a member of /dev/md/urras.penguinpee.nl:54, slot 0.
This smells very much like something is off with the version 1.1 superblock. This being the only notable difference between arrays md1 and md5 and array md54. Yet, I have no clue as to what or what to do about it. :-\
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
