agspoon wrote:
> Thanks for the explanation.
>
> The rescan seemed to do the trick. I added it to the boot logic, and
> caught a blade with this error just yesterday. There are 9 LUNs, but
> when this happens it is always LUN-0 that is missing. A "- - -"
> rescan found the missing LUN and crea
Thanks for the explanation.
The rescan seemed to do the trick. I added it to the boot logic, and
caught a blade with this error just yesterday. There are 9 LUNs, but
when this happens it is always LUN-0 that is missing. A "- - -"
rescan found the missing LUN and created the new device (/dev/sd
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
agspoon wrote:
> 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
> d
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 the
re-scan trigger a
On Wed, Mar 25, 2009 at 08:26:46AM +0100, Ulrich Windl wrote:
>
> On 24 Mar 2009 at 19:47, agspoon wrote:
>
> >
> > 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
On 24 Mar 2009 at 19:47, agspoon wrote:
>
> 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,
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 kn
