Bug 1873886 - Anaconda rescue fails to find linux filesystem where one exists
Summary: Anaconda rescue fails to find linux filesystem where one exists
Keywords:
Status: CLOSED DUPLICATE of bug 1268237
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-30 19:23 UTC by Steven Snow
Modified: 2020-09-10 10:48 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-09-10 10:48:41 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
pastebin of logs noted (210.30 KB, text/x-matlab)
2020-08-30 19:23 UTC, Steven Snow 		no flags Details
anaconda.log (6.60 KB, text/plain)
2020-08-31 00:56 UTC, Chris Murphy 		no flags Details
program.log (585 bytes, text/plain)
2020-08-31 00:56 UTC, Chris Murphy 		no flags Details
storage.log (124.51 KB, text/plain)
2020-08-31 00:57 UTC, Chris Murphy 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github fedora-silverblue issue-tracker issues 77 0 None open Installer inst.rescue fails to find linux filesystem yet one exists 2020-09-09 12:20:33 UTC

Description Steven Snow 2020-08-30 19:23:43 UTC 
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
Comment 1 Chris Murphy 2020-08-31 00:53:45 UTC 
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?
Comment 2 Chris Murphy 2020-08-31 00:56:10 UTC 
00:44:02,555 INF main: /sbin/anaconda 33.25.2-1.fc33
Comment 3 Chris Murphy 2020-08-31 00:56:38 UTC 
Created attachment 1713093 [details]
anaconda.log
Comment 4 Chris Murphy 2020-08-31 00:56:58 UTC 
Created attachment 1713094 [details]
program.log
Comment 5 Chris Murphy 2020-08-31 00:57:13 UTC 
Created attachment 1713095 [details]
storage.log
Comment 6 Chris Murphy 2020-08-31 01:14:19 UTC 
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.
Comment 7 Vladimír Slávik 2020-09-09 12:21:30 UTC 
Might be related to bug 1268237.
Comment 8 Vendula Poncova 2020-09-10 10:48:41 UTC 
The support for the rpm-ostree systems is not implemented.

*** This bug has been marked as a duplicate of bug 1268237 ***
Note You need to log in before you can comment on or make changes to this bug.