We have an occasional problem where one LUN of a target (LUN-0) does
not appear in a connection started by iscsistart. This is in an iscsi-
root scenario where iscsistart is called from within the initrd
ramdisk image. I don't why this happens, but I can detect when it
does. However, I don't
:
agspoon wrote:
Thanks for the tip. Yes, it really is LUN-0 that is missing. All the
other LUNs (1-6) do show up in this error condition, and upon reboot
they all show up. It is only an occasional boot up where I see LUN-0
missing, and I wanted to avoid a reboot to restore it. I'll give
