The installer intentionally refuses to run on a disk with mounted
partitions. This is a safety check to make sure you don't wipe your
running system.
I'm not sure I understand the reinstallation flow you're proposing. You
have a running Fedora CoreOS system, with a data partition containing an
FCC and an ISO live image. When you want to reprovision the machine, how
do you plan to boot into the ISO? How are you running FCCT to convert the
FCC to an Ignition config?
--Benjamin Gilbert
On Mon, Feb 24, 2020 at 3:41 AM Joel Kessler <joel(a)kessler.family> wrote:
When I run the following command, on my bare metal installation
(meaning
coreos has been installed and is currently up and running): sudo
coreos-installer install /dev/nvme0n1 --image-file
/mnt/insdev/fedora_coreos.raw.xz --ignition /mnt/insdev/ignition.ign
--insecure
The following error will occour, is there any way to resolve this, or is
this not supported at all? (I have to run it on the running os)
Error: checking for exclusive access to /dev/nvme0n1
Caused by: couldn't reread partition table: device is in use
Caused by: EBUSY: Device or resource busy
_______________________________________________
CoreOS mailing list -- coreos(a)lists.fedoraproject.org
To unsubscribe send an email to coreos-leave(a)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/coreos@lists.fedoraproject.org