Comment 6 for bug 457767

Clicking the reply button in my email (sorry if this splatters)

I isolated the problem to be something in the init system by adding
break=init to the kernel command line, and then chrooting into /root
chroot root
mount / -o remount,rw
chroot root /sbin/getty 38400 tty2

I can log in and even do a apt-get update

On Sun, Oct 25, 2009 at 3:39 PM, Mathias Gug <email address hidden> wrote:

> Creating a non-root iscsi initiator system (ie client) with open-iscsi:
>
> 1. sudo apt-get install open-iscsi
> 2. Discover the iscsi target:
>
> sudo iscsiadm -m discovery -t sendtargets -p [IP|HOSTNAME]_OF_TARGET
>
> 3. Login into the remote iscsi target:
>
> sudo iscsiadm -m node -T TARGET_NAME -p IP:PORT -l
>
> 4. Set automatic login on boot:
>
> sudo iscsiadm -m node -T TARGET_NAME -p IP:PORT --op update -n
> node.startup -v automatic
>
> This creates a configuration where the iscsi target is considered as a
> normal local block device. It doesn't create a root-on-iscsi system.
>
> This configuration is working correctly (ie on system boot /dev/sda (in
> my environement) is created).
>
> --
> karmic: iSCSI root: boot hangs on starting iscsid
> https://bugs.launchpad.net/bugs/457767
> You received this bug notification because you are a direct subscriber
> of the bug.
>