Fedora Account System
Red Hat Associate
Red Hat Customer
fedora 39 on ppc64le installation no problem. Created rear -v mkbackup without problem. But booting from rear iso always [DEPEND] Dependency failed for serial-getty…S0.service - Serial Getty on ttyS0. It doesn't continue. No login. Fedora 38 on ppc64le rear boot works without problem. I tested two fedora 39 lpars on pprc64le. The same problem with boot rear iso. [DEPEND] Dependency failed for serial-getty…S0.service Reproducible: Always Steps to Reproduce: 1.rear -v mkbackup 2.boot iso from sms on hmc 3.no login [DEPEND] Dependency failed for serial-getty…S0.service Actual Results: Dependency failed for serial-getty…S0.service restart to normal mode fedora 39 looks like OK Expected Results: I expect login to rear and recovery the same behaviour as ferdora 38 or rocky-linux or redhat
Hi, the upstream report about this is https://github.com/rear/rear/issues/3017 and I fixed it in the Git devel version. I don't have commit access to the Fedora package unfortunately. https://github.com/rear/rear/pull/3079 is the change that needs to be applied. I can help you with recovering from backup if you have a backup that you need to restore and you can't recreate it.
Hi May I ask ? I will edit boot file, but I don't know find file .packit.yaml on Fedora 39. Can you explain ? Thanks
You don't need .packit.yaml, it is only for tests. Here is the change that should be enough: https://github.com/pcahyna/rear/commit/29c6f3c57727c4c6bb8cbeb0d41baca56145c6b7
So on fedora 39 I edited boot file, rem one line #mount -t sysfs none /sys. Created new rear iso and boot again, login appeared, problem is solved. Thank you very much. Sorry but I don't understand in boot file from fedora 38 are the same lines as were before in fedora 39. Rear iso boot works and worked without problem. lines from boot file in dedora 38 #!/usr/bin/bash # Relax-and-Recover # disable console logging for kernel messages dmesg -n1 # basic mounts mount -t proc -n none /proc mount -t sysfs none /sys if type udevd &>/dev/null && ! type udevinfo &>/dev/null; then
Thanks for the confirmation, glad to have helped. ReaR code in Fedora 38 is the same, but something changed in systemd that now requires this change that was not needed before.
FEDORA-2024-a2f6e5ddb8 (rear-2.7-8.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-a2f6e5ddb8
FEDORA-2024-49ddbf447d (rear-2.7-8.fc38) has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-49ddbf447d
FEDORA-2024-49ddbf447d has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-49ddbf447d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-49ddbf447d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-a2f6e5ddb8 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-a2f6e5ddb8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-a2f6e5ddb8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-a2f6e5ddb8 (rear-2.7-8.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-49ddbf447d (rear-2.7-8.fc38) has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.