Discussion:
systemd on bios computer
(too old to reply)
Jude DaShiell
2017-07-04 18:52:57 UTC
Permalink
Raw Message
When doing a systemd upgrade I get:
(3/7) Upgrading systemd-boot...
Couldn't find EFI system partition. It is recommended to mount it to
/boot. Alternatively, use --path= to specify path to mount point.
error: command failed to execute correctly
Are either of the above alternatives even viable for a real bios machine?
This one got built when efi was somewhere on the drawing board or maybe
before efi ever got to the drawing board.



--
Michał Zegan
2017-07-05 19:08:16 UTC
Permalink
Raw Message
Just ignore this error, as it is irrelevant to your machine.
Post by Jude DaShiell
(3/7) Upgrading systemd-boot...
Couldn't find EFI system partition. It is recommended to mount it to
/boot. Alternatively, use --path= to specify path to mount point.
error: command failed to execute correctly
Are either of the above alternatives even viable for a real bios
machine? This one got built when efi was somewhere on the drawing board
or maybe before efi ever got to the drawing board.
--
ITwrx.org
2017-07-05 19:16:10 UTC
Permalink
Raw Message
Post by Jude DaShiell
(3/7) Upgrading systemd-boot...
Couldn't find EFI system partition. It is recommended to mount it to
/boot. Alternatively, use --path= to specify path to mount point.
error: command failed to execute correctly
Are either of the above alternatives even viable for a real bios
machine? This one got built when efi was somewhere on the drawing
board or maybe before efi ever got to the drawing board.
--
https://wiki.archlinux.org/index.php/systemd-boot

explains it better than i would have.
Christian Hesse
2017-07-05 19:17:41 UTC
Permalink
Raw Message
Post by Jude DaShiell
(3/7) Upgrading systemd-boot...
Couldn't find EFI system partition. It is recommended to mount it to
/boot. Alternatively, use --path= to specify path to mount point.
error: command failed to execute correctly
Are either of the above alternatives even viable for a real bios machine?
This one got built when efi was somewhere on the drawing board or maybe
before efi ever got to the drawing board.
Just a guess as I have never seen this before... Did you install package
systemd-boot-pacman-hook from AUR? Remove that...
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
Eli Schwartz via arch-general
2017-07-05 19:21:31 UTC
Permalink
Raw Message
Post by Jude DaShiell
(3/7) Upgrading systemd-boot...
Couldn't find EFI system partition. It is recommended to mount it to
/boot. Alternatively, use --path= to specify path to mount point.
error: command failed to execute correctly
Are either of the above alternatives even viable for a real bios machine?
This one got built when efi was somewhere on the drawing board or maybe
before efi ever got to the drawing board.
Sounds like you have the AUR package "systemd-boot-pacman-hook"
installed, which automatically runs `/usr/bin/bootctl update` after
every update of the systed package.

*Why* do you have that installed on a BIOS machine? This command is only
relevant for people who are using systemd-boot as their boot manager on
a computer that uses UEFI, and the error message is quite right in
saying that it cannot find an EFI System Partition for UEFI booting...
on a machine that boots via BIOS rather than UEFI.
--
Eli Schwartz
Jude DaShiell
2017-07-06 01:36:37 UTC
Permalink
Raw Message
That's not a package I specifically installed, but may have been pulled
in by another package dependency. I'll check for the package and remove
it if found.
Date: Wed, 5 Jul 2017 15:21:31
Subject: Re: [arch-general] systemd on bios computer
Post by Jude DaShiell
(3/7) Upgrading systemd-boot...
Couldn't find EFI system partition. It is recommended to mount it to
/boot. Alternatively, use --path= to specify path to mount point.
error: command failed to execute correctly
Are either of the above alternatives even viable for a real bios machine?
This one got built when efi was somewhere on the drawing board or maybe
before efi ever got to the drawing board.
Sounds like you have the AUR package "systemd-boot-pacman-hook"
installed, which automatically runs `/usr/bin/bootctl update` after
every update of the systed package.
*Why* do you have that installed on a BIOS machine? This command is only
relevant for people who are using systemd-boot as their boot manager on
a computer that uses UEFI, and the error message is quite right in
saying that it cannot find an EFI System Partition for UEFI booting...
on a machine that boots via BIOS rather than UEFI.
--
ITwrx.org
2017-07-06 02:07:58 UTC
Permalink
Raw Message
Post by Jude DaShiell
That's not a package I specifically installed, but may have been
pulled in by another package dependency. I'll check for the package
and remove it if found.
since systemd-boot is included with systemd maybe it just complains
whether you're using it or not but doesn't stop the systemd upgrade? i
haven't noticed it in the terminal, but that doesn't mean it didn't happen.
Post by Jude DaShiell
Date: Wed, 5 Jul 2017 15:21:31
Subject: Re: [arch-general] systemd on bios computer
Post by Jude DaShiell
(3/7) Upgrading systemd-boot...
Couldn't find EFI system partition. It is recommended to mount it to
/boot. Alternatively, use --path= to specify path to mount point.
error: command failed to execute correctly
Are either of the above alternatives even viable for a real bios machine?
This one got built when efi was somewhere on the drawing board or maybe
before efi ever got to the drawing board.
Sounds like you have the AUR package "systemd-boot-pacman-hook"
installed, which automatically runs `/usr/bin/bootctl update` after
every update of the systed package.
*Why* do you have that installed on a BIOS machine? This command is only
relevant for people who are using systemd-boot as their boot manager on
a computer that uses UEFI, and the error message is quite right in
saying that it cannot find an EFI System Partition for UEFI booting...
on a machine that boots via BIOS rather than UEFI.
--
Information Technology Works
https://ITwrx.org
@ITwrxorg
Jude DaShiell
2017-07-06 02:19:17 UTC
Permalink
Raw Message
It turns out that package was installed, thanks for the info and help.
Date: Wed, 5 Jul 2017 21:36:37
Subject: Re: [arch-general] systemd on bios computer
That's not a package I specifically installed, but may have been pulled in by
another package dependency. I'll check for the package and remove it if
found.
Date: Wed, 5 Jul 2017 15:21:31
Subject: Re: [arch-general] systemd on bios computer
Post by Jude DaShiell
(3/7) Upgrading systemd-boot...
Couldn't find EFI system partition. It is recommended to mount it to
/boot. Alternatively, use --path= to specify path to mount point.
error: command failed to execute correctly
Are either of the above alternatives even viable for a real bios machine?
This one got built when efi was somewhere on the drawing board or maybe
before efi ever got to the drawing board.
Sounds like you have the AUR package "systemd-boot-pacman-hook"
installed, which automatically runs `/usr/bin/bootctl update` after
every update of the systed package.
*Why* do you have that installed on a BIOS machine? This command is only
relevant for people who are using systemd-boot as their boot manager on
a computer that uses UEFI, and the error message is quite right in
saying that it cannot find an EFI System Partition for UEFI booting...
on a machine that boots via BIOS rather than UEFI.
--

Loading...