When I reboot my Win7 machine, connected via iSCSI to the DroboPro, it takes forever for the Drobo to reconnect (~ 45 mins), and the server machine is very slow the entire time until it happens - really slow. Apps crash with time out slow.
DroboPro has 5 drives, all 1.5TB, and single disk redundancy. Pretty much vanilla install of Win 7 and the DroboPro. Connected to motherboard NIC (Yukon chipset I think)
Over and over in the event log:
When I say forever I mean about 45 mins before it reconnects from a cold boot of both. The Event Log is full of iSCSI errors:
iSCSI discovery via SendTargets failed with error code 0xefff0003 to target portal *169.254.1.0 0003260 Root\ISCSIPRT\0000_0 .
iSCSI discovery via SendTargets failed with error code 0xefff0003 to target portal *169.254.1.0 0003260 Root\ISCSIPRT\0000_0 .
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
The Server service hung on starting.
Is this normal? I repsume not. Once it is up everything appears to run very well.
How many volume or volumes do you have on ur DP? What are the capacity? We had half a dozen of 16TB Smart Vols created b/f & Windows did take a relatively longer time to mount them but no booting up. So, we striped our DP down to 2 16TB for our W2K3/W2K8 servers, 2 2TB vols for ESXi4 & WinXP and they came up ok. Btw, we are not using any fancy managed L2/L3 switches. Just the unmanged netgear 1Gig.
I recommend you try using a different IP address (for example: ur production LAN) for t-shooting purpose & see whether ur Win7 boots up faster.
I can say that on my WIN7 machine I cannot get isci to connect at all - thou i have to say I have not waited that long either - usually just assuming it will not work…
I still owe tech support a call when i can actually get the time to work on the issue while on he phone with them… I miss iSCSI … it worked well on XP…
I have a 8TB single volume on iScsi (Win7) it doesn’t take more than about 60s or so to connect on a cold boot.
However it often boots, the pro spins up, then the pro crashes, shutting all drives off in a giant ‘ca-khunk’ and then goes through the massively time consuming restart sequence. So far no data loss.
This droboPro crash almost always happens when I wakes from standby and immediately tries to copy data to the drive via a scheduled task using stuff like syncbackpro. I have had to add pre-transfer wake tasks to wake the machine up, let the drobo stabilize then start the transfers.
I reported this problem with Win7 RTM, but their response was not to use Win7.
When Win7 was released, I dutifully did a clean install and update the dashboard and f/w to find the problem still exists. I havn’t rereported the problem yet.
When you reboot, does the Drobo automatically go into standy? My figures were from a cold boot, as I’ve only really done this when I’ve been moving things around so have had to power everything completely off. But I noticed even on a normal reboot it took an inordinate amount of time to come back.
Definitely seems Win7 and the Drobo are not wonderfully friendly to each other yet.
I wonder how far off Fw800 performance is? Might jsut be simpler to get a FW800 card and give up on iSCSI???
Basically the the computer is shut down and powered off, the drobo is left to do it’s power down thing without physically turning off the drobo power switch or unplugging it.
When the computer is turned on again, the drobo will (if it doesn’t crash/reboot) wake up and reconnect somewhat quickly. If it crashes, then it is a loooong cycle of stuff on the drobo before the connect occurs.
Be sure you are using the latest dashboard and firmware in the drobo. It seems like when I first got it it was slower to connect in general. But I’ve messed with stuff so much I could be mis-remembering or could have changed something else in the configuration which helped it mount a bit faster.
@Jeffk, the behavior you are experiencing sounds like a possible issue with one of your drives. I would recommend either reversing the order of your drives or opening up a support case so we can take a look at your drives.
Everything seems to work (Drobo FS), but I keep seeing in my events:
1] iSCSI discovery via SendTargets failed with error code 0x00002afc to target portal *Drobo 0003260 Root\ISCSIPRT\0000_0
2] iSCSI discovery via SendTargets failed with error code 0x00002afc to target portal *drobo-fs 0003260 Root\ISCSIPRT\0000_0
also:
3] The firewall exception to allow Internet Storage Name Server (iSNS) client functionality is not enabled. iSNS client functionality is not available
Any clue and and solution. I think the iSCSI is enabled in my firewall, but further help would be appreciated.
Nope, it’s an FS, connected to the router via ethernet. Which is why I’m confused. Must be some legacy data in the registry… or confusion when the Drobo driver were installed.
The Drobo Dashboard may be incorrectly attempting to contact the FS with iSCSI, but it doesn’t matter - out of the box, the DroboFS doesn’t support iSCSI. You can hack it with some third-party DroboApps, but that’s about it.