Bug 1873886
| Summary: | Anaconda rescue fails to find linux filesystem where one exists | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Steven Snow <stevensnow> | ||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | rawhide | CC: | anaconda-maint-list, bugzilla, jkonecny, jonathan, kellin, vanmeeuwen+fedora, vponcova, wwoods | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2020-09-10 10:48:41 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
Same problem with simple qemu-kvm. Automatic partition install of Fedora-Silverblue-ostree-x86_64-33-20200830.n.0.iso, followed by rescue boot (inst.rescue), and (1)continue at the menu. I can't tell where it gets confused. This is correct: INFO:program:Running... mount -t btrfs -o subvol=root,ro /dev/vda3 /mnt/sysimage But I don't see evidence it's trying to properly assemble the ostree. In which case how did it even know to mount subvol=root, if it hasn't yet found the deeply buried fstab? 00:44:02,555 INF main: /sbin/anaconda 33.25.2-1.fc33 Created attachment 1713093 [details]
anaconda.log
Created attachment 1713094 [details]
program.log
Created attachment 1713095 [details]
storage.log
This is also a problem with an LVM+xfs installation, so it's not Btrfs specific. I think the rescue is generally not functional for rpm-ostree installs. Might be related to bug 1268237. The support for the rpm-ostree systems is not implemented. *** This bug has been marked as a duplicate of bug 1268237 *** |
Created attachment 1713084 [details] pastebin of logs noted Description of problem: When booting from installation media to rescue a system that won't boot anymore, the installer fails to find a Linux filesystem on the device. Version-Release number of selected component (if applicable):Fedora Rawhide 33 Silverblue. Fedora-Silverblue-ostree-x86_64-33-20200828.n.0.iso How reproducible: Every time since failure began Steps to Reproduce: 1.Boot system with installation media Fedora-Silverblue-ostree-x86_64-33-20200828.n.0.iso 2.Select Troubleshooting 3.Select Continue to rescue installed system Actual results: Fails to find any linux filesystems where there is one. Expected results: Continue to rescue and mount the filesystem Additional info: I have attached the program.log, anaconda.log, and storage.log