Update,
So if I hardcode the LUN to 1, matching my Synology target, then
two(?) targets get attached:
sd1 at scsibus2 targ 0 lun 0:
naa.600140577c3262ed829ed4f8fdb787d2
sd1: 512000MB, 512 bytes/sector, 1048576000 sectors, thin
sd2 at scsibus2 targ 0 lun 1:
naa.600140577c3262ed829ed4f8fdb787d2
s
Second try
Hello,
I’m having issues getting iscsid to work with my Synology NAS on
amd64/6.9-beta.
The first issue was that the NAS was returning an error code. Turns out
it didn’t like missing the default SessionType=Normal.
The second issue was that the login sequence never completed. It
On 01.04., Claudio Jeker wrote:
> On Thu, Apr 01, 2021 at 07:27:10AM +0200, Bruno Flueckiger wrote:
> > On 31.03., David Alten wrote:
> > > Hello,
> > >
> > > I???m having issues getting iscsid to work with my Synology NAS.
> > >
> > > The first issue was that the NAS was returning an error code. T
On Thu, Apr 01, 2021 at 07:27:10AM +0200, Bruno Flueckiger wrote:
> On 31.03., David Alten wrote:
> > Hello,
> >
> > I???m having issues getting iscsid to work with my Synology NAS.
> >
> > The first issue was that the NAS was returning an error code. Turns out
> > it didn???t like not?? missing th
On 31.03., David Alten wrote:
> Hello,
>
> I???m having issues getting iscsid to work with my Synology NAS.
>
> The first issue was that the NAS was returning an error code. Turns out
> it didn???t like not?? missing the default SessionType=Normal.
>
> The second issue was that the login sequence n
Hello,
Iâm having issues getting iscsid to work with my Synology NAS.
The first issue was that the NAS was returning an error code. Turns out
it didnât like not missing the default SessionType=Normal.
The second issue was that the login sequence never comleted. It seems we
keep hardcoding
