Hi all!
I've prepared an iSCSI target (32 GB) with a small (2GB) ext4 filesystem containing LiveOS/squashfs.img, initrd.img and vmlinuz and configured extlinux to make that partition bootable (root=live:UUID=3aa6fe78-5418-4d86-ba80-bec7d5fff742 rd.live.image netroot=iscsi rd.iscsi.firmware=1) and to boot Fedora-Workstation-Live.
Then I'm using iPXE with iBFT configured to boot LiveOS from this target, all fine.
Now I'd like to install Fedora on the remainder of the same iSCSI target (30GB), for some reason it isn't available as a installation target and when I try to add the iSCSI target the following message is shown:
Failed to call Login method on /org/freedesktop/UDisks2/Manager with ('iqn...') arguments: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Login failed: initiator reported error (15 - session exists).
I guess Anaconda doesn't allow to install on the device where it booted from, is there a way to workaround this?
Thanks for your reply! Dick Marinus
On 6/2/20 11:30 AM, Dick Marinus wrote:
Hi all!
I've prepared an iSCSI target (32 GB) with a small (2GB) ext4 filesystem containing LiveOS/squashfs.img, initrd.img and vmlinuz and configured extlinux to make that partition bootable (root=live:UUID=3aa6fe78-5418-4d86-ba80-bec7d5fff742 rd.live.image netroot=iscsi rd.iscsi.firmware=1) and to boot Fedora-Workstation-Live.
Then I'm using iPXE with iBFT configured to boot LiveOS from this target, all fine.
Now I'd like to install Fedora on the remainder of the same iSCSI target (30GB), for some reason it isn't available as a installation target and when I try to add the iSCSI target the following message is shown:
Failed to call Login method on /org/freedesktop/UDisks2/Manager with ('iqn...') arguments: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Login failed: initiator reported error (15 - session exists).
Yes, I think the target has already been attached automatically by Anaconda because it found it in iBFT.
I guess Anaconda doesn't allow to install on the device where it booted from, is there a way to workaround this?
I think you are right, and I am afraid there is no such way, but I am not yet sure
I fully understand your case.
What is your expected state of the target? It seems to me like
you'd need 2 iSCSI targets (one for live, second for installed system) to
be able to boot both to live and installed system.
Or do you want to overwrite the live?
Attaching /tmp/syslog from installer environment could also help me to better understand your case.
Radek
On Tue, Jun 02, 2020 at 12:48:18PM +0200, Radek Vykydal wrote:
On 6/2/20 11:30 AM, Dick Marinus wrote:
Hi all!
I've prepared an iSCSI target (32 GB) with a small (2GB) ext4 filesystem containing LiveOS/squashfs.img, initrd.img and vmlinuz and configured extlinux to make that partition bootable (root=live:UUID=3aa6fe78-5418-4d86-ba80-bec7d5fff742 rd.live.image netroot=iscsi rd.iscsi.firmware=1) and to boot Fedora-Workstation-Live.
Then I'm using iPXE with iBFT configured to boot LiveOS from this target, all fine.
Now I'd like to install Fedora on the remainder of the same iSCSI target (30GB), for some reason it isn't available as a installation target and when I try to add the iSCSI target the following message is shown:
Failed to call Login method on /org/freedesktop/UDisks2/Manager with ('iqn...') arguments: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Login failed: initiator reported error (15 - session exists).
Yes, I think the target has already been attached automatically by Anaconda because it found it in iBFT.
I guess Anaconda doesn't allow to install on the device where it booted from, is there a way to workaround this?
I think you are right, and I am afraid there is no such way, but I am not yet sure
I fully understand your case.
What is your expected state of the target? It seems to me like
you'd need 2 iSCSI targets (one for live, second for installed system) to
be able to boot both to live and installed system.
Or do you want to overwrite the live?
Attaching /tmp/syslog from installer environment could also help me to better understand your case.
Radek
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
Hi Radek,
My intend is to install Fedora on an iSCSI target using iSCSI only, without using a physical attached DVD/USB stick.
As far as I've found out it's only possible to have one device in iBFT. That's why I'm using a small filesystem for LiveOS on the same iSCSI target so that the remainder of the iSCSI target (30GB) can be used for installing Fedora.
When Fedora is installed the small partition used for live could be removed (or re-used for reinstalling Fedora).
I didn't try to supply the Fedora-Workstation-Live (iso) from another iscsi target, that might work! I'll try that and report back.
Thanks, Dick Marinus
On 6/2/20 1:27 PM, Dick Marinus wrote:
I didn't try to supply the Fedora-Workstation-Live (iso) from another iscsi target, that might work! I'll try that and report back.
In your experimenting you might need to add inst.nonibftiscsiboot [1] installer
boot option if you want to install bootloader on a target that was not attached
automatically from ibft (but manually in GUI or via kickstart).
Radek
[1] https://github.com/rhinstaller/anaconda/blob/master/docs/boot-options.rst#in...
Hi Radek,
Thanks for your suggestion to use inst.nonibftiscsiboot, I didn't need this because I still booted the iSCSI target from where I wanted to install Fedora and used the following arguments:
netroot=iscsi:192.168.0.1::::iqn....:fedora32.iso root=live:CDLABEL=Fedora-WS-Live-32-1-6 rd.live.image quiet This seems to work but I wonder if this is how this was intended to be used. - As Anaconda's default behavior seems to check if the ibft is valid for iSCSI boot Anaconda must be started from a target with iBFT enabled which is only possible when: - using physical DVD/USB install media - by prepping the iSCSI target with something able to load LiveCD from another iSCSI target/source. - by netbooting using different means (I didn't have enough RAM to test using memdisk)
It would have been very helpful to me if inst.nonibftiscsiboot was suggested by Anaconda when it fails/blocks on installing the bootloader.
It would be even more helpful if one could ignore this check interactively.
Anyway, thanks for your help! I guess inst.nonibftiscsiboot was what I was looking for.
Dick Marinus
anaconda-devel@lists.stg.fedoraproject.org