SOLVED Re: F30 last two updates won't boot, kernel 5.3 can't mount RAID0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





OK, after more searching the 'net I have found the answer. It seems RAID0 was unintentionally broken since kernel 5.3.1, but there is a workaround


On 19/10/2019 08:42, Christopher Ross wrote:

There have been two kernel updates this past week:
kernel-core-5.3.5-200.fc30.x86_64
kernel-core-5.3.6-200.fc30.x86_64

Neither of these will boot for me. I get so far as the Fedora splash screen in graphics mode but never the login screen.

Oct 19 07:24:38 snoopy.tebibyte.org systemd[1]: local-fs.target: Triggering OnFailure= dependencies. Oct 19 07:24:38 snoopy.tebibyte.org systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. Oct 19 07:24:38 snoopy.tebibyte.org systemd[1]: Dependency failed for Local File Systems.
...

Under the last kernel that does boot (kernel-core-5.2.18-200.fc30.x86_64), the device it is references looks like this : lrwxrwxrwx. 1 root root 9 Oct 19 07:30 "/dev/disk/by-uuid/a1aaca46-f02d-4407-90ab-1067eecea53d" -> "../../md0"

Where md0 is a RAID0 of 4 x 1TiB discs.



Thanks to a not dissimilar query on the ArchLinux lists:

(https://bbs.archlinux.org/viewtopic.php?pid=1868823#p1868823)
It's a bug, recently discovered, that caused the raid0 layout to change unintentionally a while back, so now they're in a pickle... they have two layouts and the metadata doesn't say which is correct.

If they fix the unintentional change, they corrupt all raid0 using the unintended new layout; if they don't fix it, they corrupt all raid0 using the old layout. Both choices are wrong so they decided instead to make it "stop working entirely" until the sysadmin decides how they want to corrupt their raid0.

so you have to add a kernel paramter: raid0.default_layout=1 for new or =2 for old 3.x kernel raid0s



Regards,
Chris R.



_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux