I'm unable to install F32 Silverblue on a disk that had F31 installed on it. I can start the installation, do the partitioning and then, a few minutes after the installation starts, it exits with error code 32. Description of problem: The installation fails with error code 32. Version-Release number of selected component (if applicable): Fedora 32 Silverblue How reproducible: Everytime Steps to Reproduce: 1.Boot on usb key and select language 2.Select keyboard 3.Select disk and do the partitioning /boot 1025 MiB / 70 GiB swap 12 GiB /home 382 GiB 4.Begin installation Actual results: After message "deployment starting : fedora/32/x86_64/silverblue", installation stops with error code 32 Additional info: https://imgur.com/EAbhRVE https://imgur.com/iw3EhRa https://imgur.com/Ll15bI0 https://imgur.com/pwuAgBd
Hello Fujisan, can you please provide all installation logs, especially the file named syslog? You can find them during the installation in /tmp or on the installed system in /var/log/anaconda/.
Created attachment 1712317 [details] anaconda.log Here are the log files I found in /tmp during the installation.
Created attachment 1712318 [details] dbus.log
Created attachment 1712320 [details] program.log
Created attachment 1712321 [details] storage.log
Created attachment 1712322 [details] X.log
Created attachment 1712323 [details] lvm.log
Created attachment 1712324 [details] sensitive-info.log
It seems like it doesn't like to have a partition mounted on /data. I re-installed it with a partition mounted on /home and it worked.
Can you please find also the journal (journal.log)? That would be very useful.
There is no file named journal.log nowhere under /. Also, I noticed I made a mistake in the description of the first post. I created the following partitions: LVM partitions: / /data swap native partition: /boot (/dev/sda1) I did not create a /home partition and therefore the installation crashes with error: mount ['--bind','/mnt/sysimage/data','/mnt/sysroot/data'] exited with code 32. I re-installed the system with a /home LVM partition instead of a /data LVM partition and it worked.
Thank you for the details. I was able to reproduce this 1:1. Plain old partitions, one for /data, crash at end with mount error 32 and same message: > mount ['--bind', '/mnt/sysimage/data', '/mnt/sysroot/data'] exited with code 32 The interesting thing is that lsblk shows something like this: - /dev/vda1 -> /mnt/sysimage/ostree/deploy/fedora/deploy/<UUID>.0/boot - /dev/vda2 -> /mnt/sysimage/ostree/data - /dev/vdb1 -> /mnt/sysimage - /dev/vdc1 -> /mnt/sysimage/ostree/deploy/fedora/deploy/<UUID>.0/var/home So at least something goes according to the plan. Jirka (jkonecny) thought that we just do not create the directory to mount to. I think the place is in pyanaconda/payload/rpmostreepayload.py , RPMOSTreePayload._prepare_mount_targets(). FWIW, the solution with "systemd-tmpfiles" that we have there is "better than hand-rolling mkdirs" according to log. But it will not solve this problem, because it uses contents of tmpfiles.d to determine what to do, the "prefix" that we have there just limits it to some paths. Asking to have the very same partition under /home/data worked well, so at least there's a workaround.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
On rawhide, this appears to be fixed with a fix for bug 1906735. *** This bug has been marked as a duplicate of bug 1906735 ***
Actually, no, the bug is alive and well. It's the second round of mounting that fails, the bind one. For current traceback, see bug 1977375.
*** Bug 1977375 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
This is correct. The point is that in SilverBlue world you can't write anything to `/data`. You have to create `/var/data` instead. Reason is that rpm-based systems is immutable for more information please see https://docs.fedoraproject.org/en-US/fedora-silverblue/technical-information/#filesystem-layout . What Anaconda should do is to not allow user to shoot themselves to their feet. Anaconda shouldn't allow user to create mount points on `/` and `/usr`.
Hi Colin, I would like to ask you a few things about how Anaconda should behave. The problem we are facing now is that user will create partitioning with /home, / and /data in Anaconda. AFAIK Anaconda will re-mount (bind mount?) / -> / /home -> /var/home /data -> ??? And that is the reason why we are seeing the Permission denied error on the bug 1977375 because Anaconda will try to create a directory (for mount) on /data which is not allowed on ostree based systems. What I would like to know is how we should behave, to know how to properly fix the issue. Should we automatically move the mount to /var/data instead? That could be confusing to people because it will be on other place than they choose to have it but it is consistent with how /home now works. What do you think?
This is basically https://github.com/coreos/rpm-ostree/issues/337 But yes if Anaconda knows we're installing an ostree system, I think the simplest is to disallow mounts outside of `/var` for now.
Thanks for explanation and hint how to solve this. In that case, I wonder what mount-points should be allowed. I know that SB supports: / /home /var/* But I guess there are more optional mount points which we should allow during manual partitioning like /usr as a separate mount point. Am I correct? Could you please give me a list of the supported places which Anaconda should allow on rpm-ostree based installations so we could implement this correctly?
*** Bug 2120772 has been marked as a duplicate of this bug. ***
Reproduced for f36 in bug 2120772.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days