I've been connecting a few MS iSCSI s/w initiator based hosts to our iSCSI
SAN without problem. Re-connects survive reboots and everything works ok.

I have one host though that has a s/w initiator connection to a 100Gb SAN
volume. It runs the SAN connection over a dedicated NIC, and mounts the
volume fine. While the volume is mounted, all i/o works without fault.
Trouble is, when the server is rebooted, the SAN volume doesn't re-mount,
and always shows as 'failed'. If I re-activate the volume, it re-mounts and
all the data is intact. The volume then performs as usual. The MPIO module
is loaded, and I've tried v2.05 and v2.06 of the initiator. The host is
Windows 2000 SP4.

I've tried setting a persistant mount point, and even set the SERVER service
to be dependant on the MSiSCSI service, just incase something wasn't
starting in time, but it hasn't made any difference.

Any ideas?

Eat dogs, cats and baby look below:

http://z.about.com/d/urbanlegends/1/0/v/7/eating_babies1.jpg

http://z.about.com/d/urbanlegends/1/0/w/7/eating_babies2.jpg

http://888.rockin.net/propaganda-of-baby-eating/rumour.htm#true_story

info@imagiam.com

So many dogs and cats being killed and ate in China, why you still support olympic?

So many dogs and cats being killed and ate in China, why you still support olympic?

Hello all,

I have a Dell with Windows Storage Server 2003 R2, I know that i can't
install applications in WSS.
But can i install a backup application like Arcserve Backup 11.5?

Thanks

Paulo Gonçalves

"Frank Pietersen" discussions.microsoft.com> wrote in
message news:E4653185-60A0-4DCF-9213-ABB532FA1793@microsoft.com...

did you ask your storage vendor if they have a command line utility to mount
?

other than that, I guess you are back to scripting as you are already doing,
and catching variances (volume numbers) during running the script.

rgds,
edwin.

Anyone else an idea to help me out with this problem. I supose that more
people use scripts to connect to snapshots in an SAN environment!?!

Thanks in advance,
Frank

"Frank Pietersen" wrote:

Hello,

I have the following problem:

A few days ago Windows (2003) started to resync my dynamic raid 5 volume,
because I made a mistake (removed a wrong disk, but immediatly putting it
back in). Unfortunately at about 15%% in the synchronization process, windows
crashed. After a reboot all drives are suddenly marked as Offline and I
can't get them back in an Online Mode. I tried both the disk managment snap
in ('reactivate disk') and diskpart ('online' command) without success. I
don't get an error message, but the disk is still in offline mode.

The disk data is still there. I can access them without problems in various
recovery tools, that work directly on the physical device(s). There are also
no physical errors on the disks and the event log shows no errors when I try
to activate a disk. There is also no problem with the controller itself, I
can access other disks on the same controller without problems.

I am quite confident that if I just get windows to accept the disks and put
them in online mode, that they'll work again with no problem. I just can't
figure out how to do that.

Any ideas?

The last time I used my USB pen drive I forgot to click on the "safely remove hardware"
icon in the system tray.
Now it is unreadable, in that when I click on the "removable drive" icon in "My Computer",
it asks me to insert one.
Is there a way to recover the data I have on it, as it is pretty valuable ?
Please help.

Thanks in advance,
Mike

If this is not the right newsgroup, please send me to the right one.
:)

Does MS scandisk work really well, or can it leave bad spots on the
harddrive that it didn't find?

Is there other software that runs under dos that is better than, or
different from, scandisk, that might find problem areas that scandisk
didn't find??

I have run scandisk for about 30 passes, and the last errors I found
were 11 or 12 passes ago.

OTOH, when I try to reinstall Windows, it gets to a certain point (10%%
of files copied) and the computer freezes every time. At 10%%, which
is somewhere between 10 and 11 per cent each time, but maybe at
exactly the same point. By freeze, I mean that the light on the
CD-Rom goes out, and the hard drive light flickers for a while, then
stays on all the time without flickering, and eventually the hard
drive makes noise, buzzing for 3 seconds, silent for 3 seconds (repeat
four times. Then a 6 second pause and it starts again.)