DS209: iSCSI Target will not reconnect on reboot

[maschoff]

Every time I reboot my computer, I have to manually reactivate the iSCSI Target within Disk Management.

I've tried everything possible configuration but no dice.

Anyone else experiencing this?

I have to manually log the Target on in MS iSCSI initiator.

Not sure if this is a network issue; using kaspersky antivirus; any firewall settings that need to be made before the iSCSI target will be able to communicate with my computer?

Any help would be much appreciated.

[vm.franklin]

Greetings maschoff

Please note that one of your links is not functioning, so, I cannot reference that information. In any case please refer to the iSCSI Wiki and refer to step seven.

Hope this helps.

[fpv]

I have a DS1010+ and I'm experiencing the same problem. I use DSM 2.3-1161 and the MS iSCSI initiator shipped with Windows 7 x64. It doesn't matter if I enable CHAP or not, after a reboot the reconnect fails and events 10 (iScsiPrt) and 103 (MSiSCSI) are logged. I tried setting up the initiator as Administrator, but that doesn't change anything. Although the errors point to network problems, that doesn't seem to be the case, as the machine is available on the network at the usual time after reboot, just as it's supposed to be.

I think it's a Windows problem, still if anybody could help I'd be grateful. In the meantime I'll maybe try a different initiator.

EDIT: I tried the StarPort iSCSI initiator from StarWind Software, and it restores the connection after reboot, although only without CHAP (when using CHAP, the automount option stay greyed out).

[maschoff]

@vm.franklin: Thanks but I've tried everything. Am going to try fpvs's solution.

Thanks fpv!

[maschoff]

I have a DS1010+ and I'm experiencing the same problem. I use DSM 2.3-1161 and the MS iSCSI initiator shipped with Windows 7 x64. It doesn't matter if I enable CHAP or not, after a reboot the reconnect fails and events 10 (iScsiPrt) and 103 (MSiSCSI) are logged. I tried setting up the initiator as Administrator, but that doesn't change anything. Although the errors point to network problems, that doesn't seem to be the case, as the machine is available on the network at the usual time after reboot, just as it's supposed to be.

I think it's a Windows problem, still if anybody could help I'd be grateful. In the meantime I'll maybe try a different initiator.

EDIT: I tried the StarPort iSCSI initiator from StarWind Software, and it restores the connection after reboot, although only without CHAP (when using CHAP, the automount option stay greyed out).

Thank you fvp! It worked and CHAP is not grayed out in my version.

[fpv]

You're very welcome, maschoff.

What OS are you using? Maybe the available options are OS dependent.

[maschoff]

You're very welcome, maschoff.

What OS are you using? Maybe the available options are OS dependent.

I'm using Windows XP Pro Service Pack III ... on two desktops and one laptop, and all reacted the same to MS initiator, across the board.

I've been banging my head against this problem for weeks. I so appreciate you responding to this message. I hadn't checked back because I was starting to give up hope. Synology tech support tried their best but this is obviously a Windows Microsoft issue.

Best!

[system32]

I implemented a DS209 in our network for using it as an iSCSI Target for our Windows 2003 Small Business Server.

I have the same Problem with the DS209. Every time our server reboots, it doesn't reconnect the iSCSI Connection on boot.
After a reboot of the server, I have to manually login to the Target in MS iSCSI initiator 2.08.

Our Environment:
- 1 x Windows 2003 Small Business Server with MS iSCSI Initiator 2.08 installed (connected to a 1 GBit/48 Port Linksys Switch). The drivers, firmwares and Windows Updates on
the server are on the latest version
- 1 x Synology DS209 (connected to the same 1 Gbit/48 Port Linksys Switch). On the DS209 there is the latest firmware with version DSM 2.3-1157 installed.

I've configured the iSCSI Initiator like from your iSCSI Wiki. It works great until a reboot of the server.

I've tried everything possible configuration but no success.

I think it is a problem in combination of MS iSCSI and the Synology DS209.

With the free iSCSI Initiator from Starport (http://www.starwindsoftware.com/iscsi-initiator) it works correct
after a reboot. But with the iSCSI Initiator from Starport, we have another problem, that freezes our server when
high Disk I/O (ie. write the Backup to the iSCSI Volume) is on the iSCSI Volume...

So we went back to the MS iSCSI Initiator with the reconnect problem.

Anyone else experiencing this?

Thank you in advance for any help.

[system32]

Anyone else who has this problem? Is there no fix available?

[KennKong]

I have a DS1010+ and I'm experiencing the same problem. I use DSM 2.3-1161 and the MS iSCSI initiator shipped with Windows 7 x64. It doesn't matter if I enable CHAP or not, after a reboot the reconnect fails and events 10 (iScsiPrt) and 103 (MSiSCSI) are logged.

I have a DS410j running DSM 2.3-1157, and am connecting to the target from a Win 7 Pro x86 box. I was getting the same errors in the log, so it gave me the idea to try triggering a command in task scheduler.

When I use the command iscsicli qlogintarget <target name> from the command line, it immediately connects the target, and the drive letter it maps to appears.

I tried setting up a task to run this command when it saw either event 10 or 103, but it never triggered. I thought perhaps the errors were happening before the task scheduler started. So I set the task to run every 5 minutes after startup, since running the command multiple times doesn't seem to cause a problem. However, even though the task scheduler was running the command, it never made the connection appear.

Fortunately for me, this system stays up most of the time, so I don't have to remember to manually reconnect often.

Can anyone think of another way to force the system to reconnect?

[system32]

Hi all

For me the problem is solved, after I installed the latest DSM 3.0 Firmware on the Synology DS209 Diskstation.
Since I installed the latest Firmware on the Diskstation, anything works fine and the Server reconnects the
iSCSI Target after a reboot. For other people who have this problem, install the latest DSM 3.0 Firmware on
the DS209 Diskstation and the reconnect problem is gone.