|
Bugzilla – Full Text Bug Listing |
| Summary: | Upgrade program throws "cannot find /, inst_proposal returned nil" error if / is on btrfs raid1 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Forgotten User Kyx0RzVdrN <forgotten_Kyx0RzVdrN> |
| Component: | Installation | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED FEATURE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aschnell, forgotten_Kyx0RzVdrN |
| Version: | Leap 42.2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 42.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
log extracted from installation environment just after the first error was shown
full logs now |
||
Please attach y2logs. See also https://en.opensuse.org/openSUSE:Report_a_YaST_bug#I_attached_.2Fvar.2Flog.2FYaST2.2Fy2log_to_a_YaST2_bug.2C_and_still_I_am_asked_to_attach_y2logs._Why.3F Created attachment 704236 [details]
full logs now
attaching a tar.gz of the whole YaST2 logs folder from the install media after the error popup appeared, as requested.
Sorry, but YaST does not yet support btrfs RAID setups. Well, it seems it does already, apart from that error message the upgrade went fine. |
Created attachment 702835 [details] log extracted from installation environment just after the first error was shown I was upgrading my PC to Leap 42.2, and the live installer threw up a bad-looking error saying something like "cannot find /, inst_proposal returned nil" or something like that when I was at the review page (the one where when you press "next" the upgrade starts), and also when the upgrade procedure was installing the bootloader. This seems to be easy to reproduce as I also encountered the same issue on my laptop (where also / is on a btrfs volume using 2 different partitions). The error seems mostly harmless as if I press "next" button the upgrade is executed successfully (apart from the bootloader installation, but in most cases the older bootloader will still work fine). But it does look very bad and I don't think most people feel confident after seeing it. I made partition images beforehand so I could afford to try and see what happened anyway. Anyway, I extracted logs from the installation just after the error was thrown, and I'm uploading them now.