Talk:ISCSI Boot

From ArchWiki
Jump to: navigation, search

Target

What really is missing here is a description of creating a Target only archlinux. Assume there is an non Arch installation that needs access to an iscsi target. Is there a need to create a new kernel? unclear.

iSCSI Target discusses the target-only part now. --JonnyJD 22:11, 9 October 2011 (EDT)

I created AUR packages for the LIO target, which is in the kernel since 2.6.38. This might help somebody. The administration tool is called targetcli/rtsadmin: https://aur.archlinux.org/packages.php?ID=52905 --JonnyJD 08:12, 4 October 2011 (EDT)

No Summary or explanations

I marked this article for expansion. There is no summary what is actually done in detail. There is especially some explanation missing in where the bootloader is installed now ((hd0,0) is what? iSCSI?). I personally think (hd0) is still some local device. (This should be specified) Maybe /boot is local, too. Even if not, this should be explicitly told. --JonnyJD

There might be more information in here: https://bbs.archlinux.org/viewtopic.php?id=99585 --JonnyJD 23:27, 9 October 2011 (EDT)

No, the bootloader is installed to the iSCSI disk. No local disk is needed. For simplicity it is advised to setup the iscsi disk with a single root partition. --lrusak

Effects of doing this on the systemd open-iscsi.service

I'm trying to develop an equivalent to this for SRP booting. It's a remote DMA over InfiniBand (very high speed network) protocol. It's faster than iSCSI, even running across InfiniBand. iPXE supports it. I've gotten as far as loading the kernel and initramfs, but then it doesn't go much further. SRP is done with a LIO Target, using targetcli-fb. It will be a very similar process to this.

Trying to wrap my head around iSCSI booting, first.

Obviously the iSCSI target has to be connected to in the initramfs. But, it's not making any sense to me if it happens there and open-iscsi is installed on the system, what happens with the systemd open-iscsi.service? If you only have the one iSCSI target that you're having the initramfs load, do you leave the open-iscsi systemd service disabled? If you have multiples, do you enable the systemd service, and just not configure it to connect to any targets the initramfs loaded? Or, does the initramfs iSCSI connection get undone somehow, and does the systemd service need to do it again? (Yes, this is my first time working with the internals of the initramfs/mkinitcpio.) Jamespharvey20 (talk) 06:33, 8 January 2016 (UTC)