Hello,
I have the following issue:
● initrd-switch-root.service - Switch Root Loaded: loaded (/usr/lib/systemd/system/initrd-switch-root.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-06-25 13:49:42 UTC; 5min ago Process: 838 ExecStart=/usr/bin/systemctl --no-block switch-root /sysroot (code=exited, status=1/FAILURE) Main PID: 838 (code=exited, status=1/FAILURE)
Jun 25 13:49:42 localhost systemd[1]: Starting Switch Root... Jun 25 13:49:42 localhost systemctl[838]: Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. Jun 25 13:49:42 localhost systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE Jun 25 13:49:42 localhost systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. Jun 25 13:49:42 localhost systemd[1]: Failed to start Switch Root. Jun 25 13:49:42 localhost systemd[1]: initrd-switch-root.service: Triggering OnFailure= dependencies.
I though that it was an issue with the /etc/fstab, but I cannot see. (there is not mtab for example)
Thank.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 ===========================================================================
when I mount the FS, I have cat /mnt/linux/etc/fedora-release Fedora release 30 (Thirty)
This seems to indicate me that the FS which is mounted is wrong. But it is the right one!
This is what is before:
[ 3.971992] localhost systemd[1]: Stopped Create list of required static device nodes for the current kernel. [ 3.974382] localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=kmod-static-nodes comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 3.974470] localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=kmod-static-nodes comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 3.974575] localhost systemd[1]: Closed udev Kernel Socket. [ 3.977803] localhost systemd[1]: Closed udev Control Socket. [ 3.981413] localhost systemd[1]: Starting Cleanup udevd DB... [ 3.989944] localhost systemd[1]: Started Cleanup udevd DB. [ 3.989996] localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=initrd-udevadm-cleanup-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 3.990050] localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=initrd-udevadm-cleanup-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 3.990087] localhost systemd[1]: Reached target Switch Root. [ 3.992132] localhost systemd[1]: Starting Switch Root...
Sent: Wednesday, June 26, 2019 at 3:29 PM From: "Patrick Dupre" pdupre@gmx.com To: fedora users@lists.fedoraproject.org Subject: Failed to switch root
Hello,
I have the following issue:
● initrd-switch-root.service - Switch Root Loaded: loaded (/usr/lib/systemd/system/initrd-switch-root.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-06-25 13:49:42 UTC; 5min ago Process: 838 ExecStart=/usr/bin/systemctl --no-block switch-root /sysroot (code=exited, status=1/FAILURE) Main PID: 838 (code=exited, status=1/FAILURE)
Jun 25 13:49:42 localhost systemd[1]: Starting Switch Root... Jun 25 13:49:42 localhost systemctl[838]: Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. Jun 25 13:49:42 localhost systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE Jun 25 13:49:42 localhost systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. Jun 25 13:49:42 localhost systemd[1]: Failed to start Switch Root. Jun 25 13:49:42 localhost systemd[1]: initrd-switch-root.service: Triggering OnFailure= dependencies.
I though that it was an issue with the /etc/fstab, but I cannot see. (there is not mtab for example)
Thank.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 =========================================================================== _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Hello,
In conclusion "temporally". 1) I could not boot on the first OS installed because linux instead of linuxefi and initrd instead of initrdefi were used in the menuentry If seems that moving from fedora 28 to fedora 30, a) the grub.cfg generated does not keep track b) acually, the new generation of grub.cfg (after the transition) does not manage any menuentry. 2) When a grub.cfg is generate with grub2-mkconfig, even if multi boot are detected (like on 2 different HDs), during the grub menu, it is only possible to choice the boot kernels from the OS which has generated the grub.cfg. 3) How to access to the other entries (ie on the OS sitting on the other HD)? Using efiboofmgr -c Here is efibootmgr
BootCurrent: 000F Timeout: 1 seconds BootOrder: 0008,0007,000F,000B,0000,000A,0011,000C Boot0000 fedora Boot0001* UEFI: SK hynix SC311 SATA 512GB Boot0002* UEFI: General UDisk 5.00 Boot0003* UEFI: General UDisk 5.00 Boot0004 Diskette Drive Boot0005* USB Storage Device Boot0006 Onboard NIC Boot0007 Linux Boot0008* USB Key Boot0009* UEFI: SK hynix SC311 SATA 512GB Boot000A* Diskette Drive Boot000B fedora rescue Boot000C* Onboard NIC Boot000F* Fedora Boot0011* USB Storage Device
My second disk is not bootable? It is not listed here
systemd-boot not installed in ESP. System: Firmware: n/a (n/a) Secure Boot: disabled Setup Mode: user
Current Boot Loader: Product: n/a Features: ✗ Boot counting ✗ Menu timeout control ✗ One-shot menu timeout control ✗ Default entry control ✗ One-shot entry control ESP: n/a File: └─n/a
Available Boot Loaders on ESP: ESP: /boot/efi (/dev/disk/by-partuuid/0fe1d405-6683-456c-a306-140e882> File: └─/EFI/BOOT/BOOTIA32.EFI File: └─/EFI/BOOT/BOOTX64.EFI
Boot Loaders Listed in EFI Variables: Title: Fedora ID: 0x000F Status: active, boot-order Partition: /dev/disk/by-partuuid/0fe1d405-6683-456c-a306-140e882e322c File: └─/EFI/fedora/shimx64.efi
Title: fedora ID: 0x0000 Status: inactive, boot-order Partition: /dev/disk/by-partuuid/0fe1d405-6683-456c-a306-140e882e322c File: └─/EFI/fedora/grubx64.efi
Title: UEFI: SK hynix SC311 SATA 512GB ID: 0x0001 Status: active Partition: /dev/disk/by-partuuid/0fe1d405-6683-456c-a306-140e882e322c File: └─/EFI/Ubuntu/shimx64.efi
Title: UEFI: SK hynix SC311 SATA 512GB ID: 0x0009 Status: active Partition: /dev/disk/by-partuuid/0fe1d405-6683-456c-a306-140e882e322c File: └─/EFI/Ubuntu/shimx64.efi
0 entries, no entry could be determined as default.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 ===========================================================================